October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-229) Configuring JGroups encryption protocols produces deprecated configuration

by Michal Jurc (Jira)

[ https://issues.jboss.org/browse/WFWIP-229?page=com.atlassian.jira.plugin.... ] Michal Jurc updated WFWIP-229: ------------------------------ Environment: The example has been produced with the following S2I environment variables: {{OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT JGROUPS_CLUSTER_PASSWORD=foobar123 OPENSHIFT_DNS_PING_SERVICE_PORT=8888 JGROUPS_PING_PROTOCOL=dns.DNS_PING SCRIPT_DEBUG=true}} was: The example has been produced with the following S2I environment variables: {code} OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT JGROUPS_CLUSTER_PASSWORD=foobar123 OPENSHIFT_DNS_PING_SERVICE_PORT=8888 JGROUPS_PING_PROTOCOL=dns.DNS_PING SCRIPT_DEBUG=true {code} > Configuring JGroups encryption protocols produces deprecated configuration > -------------------------------------------------------------------------- > > Key: WFWIP-229 > URL: https://issues.jboss.org/browse/WFWIP-229 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Environment: The example has been produced with the following S2I environment variables: > {{OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service > JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT > JGROUPS_CLUSTER_PASSWORD=foobar123 > OPENSHIFT_DNS_PING_SERVICE_PORT=8888 > JGROUPS_PING_PROTOCOL=dns.DNS_PING > SCRIPT_DEBUG=true}} > Reporter: Michal Jurc > Assignee: Jean Francois Denise > Priority: Critical > > Any JGroups configuration utilising encryption for protocols will result in deprecated configuration. S2I should not configure runtime to deprecated configuration by default, unless the user chooses to. > {code:title="Example JGroups ASYM_ENCRYPT configuration"} > [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=org.jgroups.protocols.ASYM_ENCRYPT:read-resource-description > { > "outcome" => "success", > "result" => { > "description" => "The configuration of a protocol within a protocol stac > k.", > "capabilities" => [{ > "name" => "org.wildfly.clustering.jgroups.protocol", > "dynamic" => true, > "dynamic-elements" => [ > "stack", > "protocol" > ] > }], > "deprecated" => { > "since" => "5.0.0", > "reason" => "Deprecated. Use protocol=ASYM_ENCRYPT instead." > }, > "attributes" => { > "module" => { > "type" => STRING, > "description" => "The module with which to resolve the protocol > type.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => "org.jgroups", > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > "properties" => { > "type" => OBJECT, > "description" => "The properties of this protocol.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "value-type" => STRING, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > "socket-binding" => { > "type" => STRING, > "description" => "Defines the bind address/port used of the serv > er socket used to receive messages from other cluster members.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "deprecated" => { > "since" => "5.0.0", > "reason" => "Deprecated. Supports EAP 7.0 slaves." > }, > "access-type" => "read-only", > "storage" => "configuration" > }, > "statistics-enabled" => { > "type" => BOOLEAN, > "description" => "Indicates whether or not this protocol will co > llect statistics overriding stack configuration.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > } > }, > "operations" => undefined, > "notifications" => undefined, > "children" => {"property" => { > "description" => "A JGroups protocol property.", > "model-description" => undefined > }} > } > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-229) Configuring JGroups encryption protocols produces deprecated configuration

by Michal Jurc (Jira)

[ https://issues.jboss.org/browse/WFWIP-229?page=com.atlassian.jira.plugin.... ] Michal Jurc updated WFWIP-229: ------------------------------ Environment: The example has been produced with the following S2I environment variables: OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT JGROUPS_CLUSTER_PASSWORD=foobar123 OPENSHIFT_DNS_PING_SERVICE_PORT=8888 JGROUPS_PING_PROTOCOL=dns.DNS_PING SCRIPT_DEBUG=true was: The example has been produced with the following S2I environment variables: {{OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT JGROUPS_CLUSTER_PASSWORD=foobar123 OPENSHIFT_DNS_PING_SERVICE_PORT=8888 JGROUPS_PING_PROTOCOL=dns.DNS_PING SCRIPT_DEBUG=true}} > Configuring JGroups encryption protocols produces deprecated configuration > -------------------------------------------------------------------------- > > Key: WFWIP-229 > URL: https://issues.jboss.org/browse/WFWIP-229 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Environment: The example has been produced with the following S2I environment variables: > OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service > JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT > JGROUPS_CLUSTER_PASSWORD=foobar123 > OPENSHIFT_DNS_PING_SERVICE_PORT=8888 > JGROUPS_PING_PROTOCOL=dns.DNS_PING > SCRIPT_DEBUG=true > Reporter: Michal Jurc > Assignee: Jean Francois Denise > Priority: Critical > > Any JGroups configuration utilising encryption for protocols will result in deprecated configuration. S2I should not configure runtime to deprecated configuration by default, unless the user chooses to. > {code:title="Example JGroups ASYM_ENCRYPT configuration"} > [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=org.jgroups.protocols.ASYM_ENCRYPT:read-resource-description > { > "outcome" => "success", > "result" => { > "description" => "The configuration of a protocol within a protocol stac > k.", > "capabilities" => [{ > "name" => "org.wildfly.clustering.jgroups.protocol", > "dynamic" => true, > "dynamic-elements" => [ > "stack", > "protocol" > ] > }], > "deprecated" => { > "since" => "5.0.0", > "reason" => "Deprecated. Use protocol=ASYM_ENCRYPT instead." > }, > "attributes" => { > "module" => { > "type" => STRING, > "description" => "The module with which to resolve the protocol > type.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => "org.jgroups", > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > "properties" => { > "type" => OBJECT, > "description" => "The properties of this protocol.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "value-type" => STRING, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > "socket-binding" => { > "type" => STRING, > "description" => "Defines the bind address/port used of the serv > er socket used to receive messages from other cluster members.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "deprecated" => { > "since" => "5.0.0", > "reason" => "Deprecated. Supports EAP 7.0 slaves." > }, > "access-type" => "read-only", > "storage" => "configuration" > }, > "statistics-enabled" => { > "type" => BOOLEAN, > "description" => "Indicates whether or not this protocol will co > llect statistics overriding stack configuration.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > } > }, > "operations" => undefined, > "notifications" => undefined, > "children" => {"property" => { > "description" => "A JGroups protocol property.", > "model-description" => undefined > }} > } > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-187) Changes to PVC are not reflected in Operator

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-187?page=com.atlassian.jira.plugin.... ] Martin Choma closed WFWIP-187. ------------------------------ Resolution: Explained I agree with explanation. I am closing the issue. > Changes to PVC are not reflected in Operator > -------------------------------------------- > > Key: WFWIP-187 > URL: https://issues.jboss.org/browse/WFWIP-187 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Any chnages (adding, removing or updating) made to PVC after WildFlyServer CR was created are not reflected in underlying PVC kubernetes object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-228) Move 'galleon-m2-repository' from '/home/jboss' to opt

by Michal Jurc (Jira)

[ https://issues.jboss.org/browse/WFWIP-228?page=com.atlassian.jira.plugin.... ] Michal Jurc reassigned WFWIP-228: --------------------------------- Assignee: Jean Francois Denise (was: Brian Stansberry) > Move 'galleon-m2-repository' from '/home/jboss' to opt > ------------------------------------------------------ > > Key: WFWIP-228 > URL: https://issues.jboss.org/browse/WFWIP-228 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Michal Jurc > Assignee: Jean Francois Denise > Priority: Major > > I would recommend moving the {{galleon-m2-repository}} from {{/home/jboss}} in the EAP/WF Galleon builder image from {{~}} to {{/opt}}. As a user, I'd expect the home to be clean after a fresh initialization :) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-228) Move 'galleon-m2-repository' from '/home/jboss' to opt

by Michal Jurc (Jira)

Michal Jurc created WFWIP-228: --------------------------------- Summary: Move 'galleon-m2-repository' from '/home/jboss' to opt Key: WFWIP-228 URL: https://issues.jboss.org/browse/WFWIP-228 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Michal Jurc Assignee: Brian Stansberry I would recommend moving the {{galleon-m2-repository}} from {{/home/jboss}} in the EAP/WF Galleon builder image from {{~}} to {{/opt}}. As a user, I'd expect the home to be clean after a fresh initialization :) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-187) Changes to PVC are not reflected in Operator

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-187?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-187: ----------------------------------- [~mchoma] PCV is not created directly by the operator. The operator creates a statefulset and in its spec, it configures *volumeClaimTemplates*[1]. When and how the StatefulSet updates the PVC based on these templates is out of scope of the operator. So if you update the operator storageSpec, you will see that the statefulset.spec.volumeClaimTemplates is updated but the corresponding PVC is not. This seems correct to me as persistent volume are tightly bound to the statefulset. [1] https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.16/#stat... > Changes to PVC are not reflected in Operator > -------------------------------------------- > > Key: WFWIP-187 > URL: https://issues.jboss.org/browse/WFWIP-187 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Any chnages (adding, removing or updating) made to PVC after WildFlyServer CR was created are not reflected in underlying PVC kubernetes object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-211) emptyDir.sizeLimit not propagated to Pod Spec

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-211?page=com.atlassian.jira.plugin.... ] Martin Choma closed WFWIP-211. ------------------------------ I have created OpenShift bug https://bugzilla.redhat.com/show_bug.cgi?id=1758434. Closing this as nothing to be done in Operator. > emptyDir.sizeLimit not propagated to Pod Spec > --------------------------------------------- > > Key: WFWIP-211 > URL: https://issues.jboss.org/browse/WFWIP-211 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > # {code:yaml} > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > name: operator-empty-dir > namespace: mchoma > spec: > applicationImage: 'registry.access.redhat.com/jboss-eap-7/eap72-openshift:1.1' > size: 1 > storage: > emptyDir: > medium: Memory > sizeLimit: 1Mi > {code} > # wait until pod are started and look into pod yaml definition "1 Mi" is not there > {code:yaml} > ... > serviceAccount: default > serviceAccountName: default > subdomain: operator-empty-dir-headless > terminationGracePeriodSeconds: 30 > volumes: > - emptyDir: > medium: Memory > name: operator-empty-dir-volume > - name: default-token-j2grg > secret: > defaultMode: 420 > secretName: default-token-j2grg > status: > conditions: > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-211) emptyDir.sizeLimit not propagated to Pod Spec

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-211?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFWIP-211: ------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1758434 > emptyDir.sizeLimit not propagated to Pod Spec > --------------------------------------------- > > Key: WFWIP-211 > URL: https://issues.jboss.org/browse/WFWIP-211 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > # {code:yaml} > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > name: operator-empty-dir > namespace: mchoma > spec: > applicationImage: 'registry.access.redhat.com/jboss-eap-7/eap72-openshift:1.1' > size: 1 > storage: > emptyDir: > medium: Memory > sizeLimit: 1Mi > {code} > # wait until pod are started and look into pod yaml definition "1 Mi" is not there > {code:yaml} > ... > serviceAccount: default > serviceAccountName: default > subdomain: operator-empty-dir-headless > terminationGracePeriodSeconds: 30 > volumes: > - emptyDir: > medium: Memory > name: operator-empty-dir-volume > - name: default-token-j2grg > secret: > defaultMode: 420 > secretName: default-token-j2grg > status: > conditions: > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-187) Changes to PVC are not reflected in Operator

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-187?page=com.atlassian.jira.plugin.... ] Martin Choma edited comment on WFWIP-187 at 10/4/19 2:27 AM: ------------------------------------------------------------- [~jmesnil] Question is if kubernetes PVC object should be updated on Operator change. Operator does not do that now for PVC, but does for StatefulSet and Service, so we are at least inconsistent here regarding operator managing kubernetes objects. In case resizing is by default off now (in future can be on), doesn't mean operator cant update PVC. There can be other data changed on PVC (label, annotation, selectros...[1]). I can change reproducer to them if this is necessary. But the point is should be PVC object updated with Operator update? I don't see reason why shouldn't. [1] https://docs.openshift.com/container-platform/3.11/rest_api/api/v1.Persis... was (Author: mchoma): Question is if kubernetes PVC object should be updated on Operator change. Operator does not do that now for PVC, but does for StatefulSet and Service, so we are at least inconsistent here regarding operator managing kubernetes objects. In case resizing is by default off now (in future can be on), doesn't mean operator cant update PVC. There can be other data changed on PVC (label, annotation, selectros...[1]). I can change reproducer to them if this is necessary. But the point is should be PVC object updated with Operator update? I don't see reason why shouldn't. [1] https://docs.openshift.com/container-platform/3.11/rest_api/api/v1.Persis... > Changes to PVC are not reflected in Operator > -------------------------------------------- > > Key: WFWIP-187 > URL: https://issues.jboss.org/browse/WFWIP-187 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Any chnages (adding, removing or updating) made to PVC after WildFlyServer CR was created are not reflected in underlying PVC kubernetes object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-187) Changes to PVC are not reflected in Operator

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-187?page=com.atlassian.jira.plugin.... ] Martin Choma reopened WFWIP-187: -------------------------------- Question is if kubernetes PVC object should be updated on Operator change. Operator does not do that now for PVC, but does for StatefulSet and Service, so we are at least inconsistent here regarding operator managing kubernetes objects. In case resizing is by default off now (in future can be on), doesn't mean operator cant update PVC. There can be other data changed on PVC (label, annotation, selectros...[1]). I can change reproducer to them if this is necessary. But the point is should be PVC object updated with Operator update? I don't see reason why shouldn't. [1] https://docs.openshift.com/container-platform/3.11/rest_api/api/v1.Persis... > Changes to PVC are not reflected in Operator > -------------------------------------------- > > Key: WFWIP-187 > URL: https://issues.jboss.org/browse/WFWIP-187 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Any chnages (adding, removing or updating) made to PVC after WildFlyServer CR was created are not reflected in underlying PVC kubernetes object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019