November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-210) Operator missing way to configure multiple containers inside pod

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-210?page=com.atlassian.jira.plugin.... ] Petr Kremensky reopened WFWIP-210: ---------------------------------- > Operator missing way to configure multiple containers inside pod > ---------------------------------------------------------------- > > Key: WFWIP-210 > URL: https://issues.jboss.org/browse/WFWIP-210 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Critical > Labels: operator > > User scenario: As a user I am able to run multiple containers under pod > - init container pattern [1] > - side car container pattern [1] > Note, this is pattern which {{istio}} use. > [1] https://matthewpalmer.net/kubernetes-app-developer/articles/multi-contain... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-210) Operator missing way to configure multiple containers inside pod

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-210?page=com.atlassian.jira.plugin.... ] Petr Kremensky closed WFWIP-210. -------------------------------- Resolution: Deferred > Operator missing way to configure multiple containers inside pod > ---------------------------------------------------------------- > > Key: WFWIP-210 > URL: https://issues.jboss.org/browse/WFWIP-210 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Critical > Labels: operator > > User scenario: As a user I am able to run multiple containers under pod > - init container pattern [1] > - side car container pattern [1] > Note, this is pattern which {{istio}} use. > [1] https://matthewpalmer.net/kubernetes-app-developer/articles/multi-contain... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-220) Operator is missing pod network settings

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-220?page=com.atlassian.jira.plugin.... ] Petr Kremensky closed WFWIP-220. -------------------------------- Resolution: Deferred > Operator is missing pod network settings > ---------------------------------------- > > Key: WFWIP-220 > URL: https://issues.jboss.org/browse/WFWIP-220 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Critical > Labels: operator > > As a user I am able to tweak network configuration > {code:yaml} > dnsPolicy: > hostAliases: > hostIPC: > hostNetwork: > hostPID: > hostname: > subdomain: > {code} > [1] https://docs.openshift.com/container-platform/3.11/rest_api/apis-apps/v1b... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-230) no way how to force scale down

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-230?page=com.atlassian.jira.plugin.... ] Petr Kremensky reopened WFWIP-230: ---------------------------------- > no way how to force scale down > ------------------------------ > > Key: WFWIP-230 > URL: https://issues.jboss.org/browse/WFWIP-230 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Simka > Assignee: Ondrej Chaloupka > Priority: Critical > Labels: operator > > inspired by upstream issue https://github.com/wildfly/wildfly-operator/issues/100. I take part of description from it > {quote} > When transaction scale down process reviews the state of transactions in the pods it checks if there are no unfinished prepared transactions. If there are found some then it does not permit the pod being terminated and the pod is moved to state SCALING_DOWN_RECOVERY_DIRTY. It's left there until all transactions are safely recovered. > There are cases when transaction is never recovered in automated manner. It's time when transaction is in heuristic state. Such transaction needs to be handled manually by administrator and he is expected to connect to the app server with jboss-cli.sh and verify the transaction state. > {quote} > There is no way how to ignore status of tx processing (tx in this case, I guess there will be more cases in future) and force scale down. > Users might want it during development, where data integrity doesn't matter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-230) no way how to force scale down

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-230?page=com.atlassian.jira.plugin.... ] Petr Kremensky closed WFWIP-230. -------------------------------- Resolution: Deferred > no way how to force scale down > ------------------------------ > > Key: WFWIP-230 > URL: https://issues.jboss.org/browse/WFWIP-230 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Simka > Assignee: Ondrej Chaloupka > Priority: Critical > Labels: operator > > inspired by upstream issue https://github.com/wildfly/wildfly-operator/issues/100. I take part of description from it > {quote} > When transaction scale down process reviews the state of transactions in the pods it checks if there are no unfinished prepared transactions. If there are found some then it does not permit the pod being terminated and the pod is moved to state SCALING_DOWN_RECOVERY_DIRTY. It's left there until all transactions are safely recovered. > There are cases when transaction is never recovered in automated manner. It's time when transaction is in heuristic state. Such transaction needs to be handled manually by administrator and he is expected to connect to the app server with jboss-cli.sh and verify the transaction state. > {quote} > There is no way how to ignore status of tx processing (tx in this case, I guess there will be more cases in future) and force scale down. > Users might want it during development, where data integrity doesn't matter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-230) no way how to force scale down

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-230?page=com.atlassian.jira.plugin.... ] Petr Kremensky closed WFWIP-230. -------------------------------- Resolution: Done Now tracked as EAP7-1394 > no way how to force scale down > ------------------------------ > > Key: WFWIP-230 > URL: https://issues.jboss.org/browse/WFWIP-230 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Simka > Assignee: Ondrej Chaloupka > Priority: Critical > Labels: operator > > inspired by upstream issue https://github.com/wildfly/wildfly-operator/issues/100. I take part of description from it > {quote} > When transaction scale down process reviews the state of transactions in the pods it checks if there are no unfinished prepared transactions. If there are found some then it does not permit the pod being terminated and the pod is moved to state SCALING_DOWN_RECOVERY_DIRTY. It's left there until all transactions are safely recovered. > There are cases when transaction is never recovered in automated manner. It's time when transaction is in heuristic state. Such transaction needs to be handled manually by administrator and he is expected to connect to the app server with jboss-cli.sh and verify the transaction state. > {quote} > There is no way how to ignore status of tx processing (tx in this case, I guess there will be more cases in future) and force scale down. > Users might want it during development, where data integrity doesn't matter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-219) Operator is missing node/pod affinity setting

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-219?page=com.atlassian.jira.plugin.... ] Petr Kremensky reopened WFWIP-219: ---------------------------------- > Operator is missing node/pod affinity setting > --------------------------------------------- > > Key: WFWIP-219 > URL: https://issues.jboss.org/browse/WFWIP-219 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Critical > Labels: operator > > As a user I am able to configure pod/node affinity > {code:yaml} > affinity: > nodeAffinity: > preferredDuringSchedulingIgnoredDuringExecution: > requiredDuringSchedulingIgnoredDuringExecution: > podAffinity: > preferredDuringSchedulingIgnoredDuringExecution: > requiredDuringSchedulingIgnoredDuringExecution: > podAntiAffinity: > preferredDuringSchedulingIgnoredDuringExecution: > requiredDuringSchedulingIgnoredDuringExecution: > nodeName: > nodeSelector: > schedulerName > tolerations" > {code} > [1] https://docs.openshift.com/container-platform/3.11/rest_api/apis-apps/v1b... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-220) Operator is missing pod network settings

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-220?page=com.atlassian.jira.plugin.... ] Petr Kremensky reopened WFWIP-220: ---------------------------------- > Operator is missing pod network settings > ---------------------------------------- > > Key: WFWIP-220 > URL: https://issues.jboss.org/browse/WFWIP-220 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Critical > Labels: operator > > As a user I am able to tweak network configuration > {code:yaml} > dnsPolicy: > hostAliases: > hostIPC: > hostNetwork: > hostPID: > hostname: > subdomain: > {code} > [1] https://docs.openshift.com/container-platform/3.11/rest_api/apis-apps/v1b... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-219) Operator is missing node/pod affinity setting

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-219?page=com.atlassian.jira.plugin.... ] Petr Kremensky closed WFWIP-219. -------------------------------- Resolution: Deferred > Operator is missing node/pod affinity setting > --------------------------------------------- > > Key: WFWIP-219 > URL: https://issues.jboss.org/browse/WFWIP-219 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Critical > Labels: operator > > As a user I am able to configure pod/node affinity > {code:yaml} > affinity: > nodeAffinity: > preferredDuringSchedulingIgnoredDuringExecution: > requiredDuringSchedulingIgnoredDuringExecution: > podAffinity: > preferredDuringSchedulingIgnoredDuringExecution: > requiredDuringSchedulingIgnoredDuringExecution: > podAntiAffinity: > preferredDuringSchedulingIgnoredDuringExecution: > requiredDuringSchedulingIgnoredDuringExecution: > nodeName: > nodeSelector: > schedulerName > tolerations" > {code} > [1] https://docs.openshift.com/container-platform/3.11/rest_api/apis-apps/v1b... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-220) Operator is missing pod network settings

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-220?page=com.atlassian.jira.plugin.... ] Petr Kremensky closed WFWIP-220. -------------------------------- Resolution: Done Now tracked as EAP7-1391 > Operator is missing pod network settings > ---------------------------------------- > > Key: WFWIP-220 > URL: https://issues.jboss.org/browse/WFWIP-220 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Critical > Labels: operator > > As a user I am able to tweak network configuration > {code:yaml} > dnsPolicy: > hostAliases: > hostIPC: > hostNetwork: > hostPID: > hostname: > subdomain: > {code} > [1] https://docs.openshift.com/container-platform/3.11/rest_api/apis-apps/v1b... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 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 November 2019