April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-84) Remove openstack cluster and reinstall vanila RHEL 7.4 there

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-84?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo resolved SWSQE-84. ------------------------------------------ Resolution: Done > Remove openstack cluster and reinstall vanila RHEL 7.4 there > ------------------------------------------------------------ > > Key: SWSQE-84 > URL: https://issues.jboss.org/browse/SWSQE-84 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Guilherme Baufaker Rêgo > > According to https://mojo.redhat.com/docs/DOC-1013097 there are 4 blades reserved for openstack cluster. During infra call we agreed that those will be reinstalled and used for openshift cluster. This task is to remove openstack and install RHEL 7.4 there -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-185) Add B14 to Openshift Cluster 3

by Guilherme Baufaker Rêgo (JIRA)

Guilherme Baufaker Rêgo created SWSQE-185: --------------------------------------------- Summary: Add B14 to Openshift Cluster 3 Key: SWSQE-185 URL: https://issues.jboss.org/browse/SWSQE-185 Project: Kiali QE Issue Type: Sub-task Reporter: Guilherme Baufaker Rêgo Assignee: Guilherme Baufaker Rêgo -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-84) Remove openstack cluster and reinstall vanila RHEL 7.4 there

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-84?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo commented on SWSQE-84: ---------------------------------------------- b19 (added to openshift cluster2) b14 (added to openshift cluster 3) and b13 (added to openshift cluster 1) B17 drac is not accessible. > Remove openstack cluster and reinstall vanila RHEL 7.4 there > ------------------------------------------------------------ > > Key: SWSQE-84 > URL: https://issues.jboss.org/browse/SWSQE-84 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Guilherme Baufaker Rêgo > > According to https://mojo.redhat.com/docs/DOC-1013097 there are 4 blades reserved for openstack cluster. During infra call we agreed that those will be reinstalled and used for openshift cluster. This task is to remove openstack and install RHEL 7.4 there -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-84) Remove openstack cluster and reinstall vanila RHEL 7.4 there

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-84?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo reassigned SWSQE-84: -------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Filip Brychta) > Remove openstack cluster and reinstall vanila RHEL 7.4 there > ------------------------------------------------------------ > > Key: SWSQE-84 > URL: https://issues.jboss.org/browse/SWSQE-84 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Guilherme Baufaker Rêgo > > According to https://mojo.redhat.com/docs/DOC-1013097 there are 4 blades reserved for openstack cluster. During infra call we agreed that those will be reinstalled and used for openshift cluster. This task is to remove openstack and install RHEL 7.4 there -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10302) Quickstarts Java EE 8 Update

by Eduardo Martins (JIRA)

Eduardo Martins created WFLY-10302: -------------------------------------- Summary: Quickstarts Java EE 8 Update Key: WFLY-10302 URL: https://issues.jboss.org/browse/WFLY-10302 Project: WildFly Issue Type: Task Components: Quickstarts Reporter: Eduardo Martins Assignee: Eduardo Martins Existent quickstarts should be compatible with Java EE 8, i.e. quickstarts should build and work as expected with Java EE 8 BOM dependencies. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10301) Java EE 8 BOMs

by Eduardo Martins (JIRA)

Eduardo Martins created WFLY-10301: -------------------------------------- Summary: Java EE 8 BOMs Key: WFLY-10301 URL: https://issues.jboss.org/browse/WFLY-10301 Project: WildFly Issue Type: Task Reporter: Eduardo Martins Assignee: Eduardo Martins BOMs with Java EE 8 APIs must be added to https://github.com/wildfly/boms -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10300) Mark deployment subsystem resources as runtime-only

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10300?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-10300: ------------------------------------ Description: Any /deployment=*/subsystem=xyx resource should be declared as runtime only. The integration suite should include a check of this, at least for the standalone server profile we cover in the main part of the testsuite. If it can easily be covered for all profiles even better. (We test all profiles in admin-only, but subsystems may not register their /deployment=*/subsystem=x definition in an admin-only server.) Part of this task should be verifying that the setFeature(false) changes for WFLY-10299 are no longer needed once this is corrected, and if so removing them. (If they are still needed then why needs investigation.) Note that WFCORE-3432 eliminates the need to add setRuntimeOnly to children of /deployment=*/subsystem=xyx as it automatically ensures that a runtime-only parent only has runtime-only children. was: Any /deployment=*/subsystem=xyx resource should be declared as runtime only. The integration suite should include a check of this, at least for the standalone server profiles where we create non-admin-only servers. Part of this task should be verifying that the setFeature(false) changes for WFLY-10299 are no longer needed once this is corrected, and if so removing them. (If they are still needed then why needs investigation.) Note that WFCORE-3432 eliminates the need to add setRuntimeOnly to children of /deployment=*/subsystem=xyx as it automatically ensures that a runtime-only parent only has runtime-only children. > Mark deployment subsystem resources as runtime-only > --------------------------------------------------- > > Key: WFLY-10300 > URL: https://issues.jboss.org/browse/WFLY-10300 > Project: WildFly > Issue Type: Task > Components: Management > Reporter: Brian Stansberry > Fix For: 13.0.0.Beta1 > > > Any /deployment=*/subsystem=xyx resource should be declared as runtime only. > The integration suite should include a check of this, at least for the standalone server profile we cover in the main part of the testsuite. If it can easily be covered for all profiles even better. (We test all profiles in admin-only, but subsystems may not register their /deployment=*/subsystem=x definition in an admin-only server.) > Part of this task should be verifying that the setFeature(false) changes for WFLY-10299 are no longer needed once this is corrected, and if so removing them. (If they are still needed then why needs investigation.) > Note that WFCORE-3432 eliminates the need to add setRuntimeOnly to children of /deployment=*/subsystem=xyx as it automatically ensures that a runtime-only parent only has runtime-only children. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10300) Mark deployment subsystem resources as runtime-only

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10300?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-10300: ------------------------------------ Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/11157) > Mark deployment subsystem resources as runtime-only > --------------------------------------------------- > > Key: WFLY-10300 > URL: https://issues.jboss.org/browse/WFLY-10300 > Project: WildFly > Issue Type: Task > Components: Management > Reporter: Brian Stansberry > Fix For: 13.0.0.Beta1 > > > Any /deployment=*/subsystem=xyx resource should be declared as runtime only. > The integration suite should include a check of this, at least for the standalone server profiles where we create non-admin-only servers. > Part of this task should be verifying that the setFeature(false) changes for WFLY-10299 are no longer needed once this is corrected, and if so removing them. (If they are still needed then why needs investigation.) > Note that WFCORE-3432 eliminates the need to add setRuntimeOnly to children of /deployment=*/subsystem=xyx as it automatically ensures that a runtime-only parent only has runtime-only children. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10300) Mark deployment subsystem resources as runtime-only

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10300?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-10300: --------------------------------------- Assignee: (was: Brian Stansberry) > Mark deployment subsystem resources as runtime-only > --------------------------------------------------- > > Key: WFLY-10300 > URL: https://issues.jboss.org/browse/WFLY-10300 > Project: WildFly > Issue Type: Task > Components: Management > Reporter: Alexey Loubyansky > Fix For: 13.0.0.Beta1 > > > Any /deployment=*/subsystem=xyx resource should be declared as runtime only. > The integration suite should include a check of this, at least for the standalone server profiles where we create non-admin-only servers. > Part of this task should be verifying that the setFeature(false) changes for WFLY-10299 are no longer needed once this is corrected, and if so removing them. (If they are still needed then why needs investigation.) > Note that WFCORE-3432 eliminates the need to add setRuntimeOnly to children of /deployment=*/subsystem=xyx as it automatically ensures that a runtime-only parent only has runtime-only children. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10300) Mark deployment subsystem resources as runtime-only

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10300?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-10300: ------------------------------------ Reporter: Brian Stansberry (was: Alexey Loubyansky) > Mark deployment subsystem resources as runtime-only > --------------------------------------------------- > > Key: WFLY-10300 > URL: https://issues.jboss.org/browse/WFLY-10300 > Project: WildFly > Issue Type: Task > Components: Management > Reporter: Brian Stansberry > Fix For: 13.0.0.Beta1 > > > Any /deployment=*/subsystem=xyx resource should be declared as runtime only. > The integration suite should include a check of this, at least for the standalone server profiles where we create non-admin-only servers. > Part of this task should be verifying that the setFeature(false) changes for WFLY-10299 are no longer needed once this is corrected, and if so removing them. (If they are still needed then why needs investigation.) > Note that WFCORE-3432 eliminates the need to add setRuntimeOnly to children of /deployment=*/subsystem=xyx as it automatically ensures that a runtime-only parent only has runtime-only children. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2018