[JBoss JIRA] (SWSQE-732) Migrate Off Of The Blade Center
by Matthew Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-732?page=com.atlassian.jira.plugin.... ]
Matthew Mahoney updated SWSQE-732:
----------------------------------
Summary: Migrate Off Of The Blade Center (was: Mograte Off Of The Blade Center)
> Migrate Off Of The Blade Center
> -------------------------------
>
> Key: SWSQE-732
> URL: https://issues.jboss.org/browse/SWSQE-732
> Project: Kiali QE
> Issue Type: Story
> Reporter: Matthew Mahoney
> Priority: Critical
> Labels: infrastructure
>
> Background information causing this Jira:
> _Embrace 2019 MW QE infrastructure vision
> During the QE camp, we (MW infrastructure folks) were approached by DevOps lead architect sharing their interests around evolving MW QE infrastructure in Boston for upcoming years. I would like to reiterate what was suggested to keep MW QE part of the conversation.
> Where we are?
> Boston hardware lab is going to be consolidated into 3rd party collocation center within a year or so. Nontrivial outage is expected because of that.
> Current MW QE hardware in Boston is getting underutilized as majority of workload was moved to central CI.
> Baremetal systems (exotic architectures, performance labs, messaging labs) are getting obsolete and unreliable.
> _
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (SWSQE-732) Migrate Off Of The Blade Center
by Matthew Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-732?page=com.atlassian.jira.plugin.... ]
Matthew Mahoney updated SWSQE-732:
----------------------------------
Description:
Background information causing this Jira:
_
Embrace 2019 MW QE infrastructure vision
During the QE camp, we (MW infrastructure folks) were approached by DevOps lead architect sharing their interests around evolving MW QE infrastructure in Boston for upcoming years. I would like to reiterate what was suggested to keep MW QE part of the conversation.
Where we are?
Boston hardware lab is going to be consolidated into 3rd party collocation center within a year or so. Nontrivial outage is expected because of that.
Current MW QE hardware in Boston is getting underutilized as majority of workload was moved to central CI.
Baremetal systems (exotic architectures, performance labs, messaging labs) are getting obsolete and unreliable._
was:
Background information causing this Jira:
_Embrace 2019 MW QE infrastructure vision
During the QE camp, we (MW infrastructure folks) were approached by DevOps lead architect sharing their interests around evolving MW QE infrastructure in Boston for upcoming years. I would like to reiterate what was suggested to keep MW QE part of the conversation.
Where we are?
Boston hardware lab is going to be consolidated into 3rd party collocation center within a year or so. Nontrivial outage is expected because of that.
Current MW QE hardware in Boston is getting underutilized as majority of workload was moved to central CI.
Baremetal systems (exotic architectures, performance labs, messaging labs) are getting obsolete and unreliable.
_
> Migrate Off Of The Blade Center
> -------------------------------
>
> Key: SWSQE-732
> URL: https://issues.jboss.org/browse/SWSQE-732
> Project: Kiali QE
> Issue Type: Story
> Reporter: Matthew Mahoney
> Priority: Critical
> Labels: infrastructure
>
> Background information causing this Jira:
> _
> Embrace 2019 MW QE infrastructure vision
> During the QE camp, we (MW infrastructure folks) were approached by DevOps lead architect sharing their interests around evolving MW QE infrastructure in Boston for upcoming years. I would like to reiterate what was suggested to keep MW QE part of the conversation.
> Where we are?
> Boston hardware lab is going to be consolidated into 3rd party collocation center within a year or so. Nontrivial outage is expected because of that.
> Current MW QE hardware in Boston is getting underutilized as majority of workload was moved to central CI.
> Baremetal systems (exotic architectures, performance labs, messaging labs) are getting obsolete and unreliable._
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (SWSQE-732) Migrate Off Of The Blade Center
by Matthew Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-732?page=com.atlassian.jira.plugin.... ]
Matthew Mahoney updated SWSQE-732:
----------------------------------
Description:
Background information causing this Jira:
Embrace 2019 MW QE infrastructure vision
During the QE camp, we (MW infrastructure folks) were approached by DevOps lead architect sharing their interests around evolving MW QE infrastructure in Boston for upcoming years. I would like to reiterate what was suggested to keep MW QE part of the conversation.
Where we are?
Boston hardware lab is going to be consolidated into 3rd party collocation center within a year or so. Nontrivial outage is expected because of that.
Current MW QE hardware in Boston is getting underutilized as majority of workload was moved to central CI.
Baremetal systems (exotic architectures, performance labs, messaging labs) are getting obsolete and unreliable.
was:
Background information causing this Jira:
_
Embrace 2019 MW QE infrastructure vision
During the QE camp, we (MW infrastructure folks) were approached by DevOps lead architect sharing their interests around evolving MW QE infrastructure in Boston for upcoming years. I would like to reiterate what was suggested to keep MW QE part of the conversation.
Where we are?
Boston hardware lab is going to be consolidated into 3rd party collocation center within a year or so. Nontrivial outage is expected because of that.
Current MW QE hardware in Boston is getting underutilized as majority of workload was moved to central CI.
Baremetal systems (exotic architectures, performance labs, messaging labs) are getting obsolete and unreliable._
> Migrate Off Of The Blade Center
> -------------------------------
>
> Key: SWSQE-732
> URL: https://issues.jboss.org/browse/SWSQE-732
> Project: Kiali QE
> Issue Type: Story
> Reporter: Matthew Mahoney
> Priority: Critical
> Labels: infrastructure
>
> Background information causing this Jira:
> Embrace 2019 MW QE infrastructure vision
> During the QE camp, we (MW infrastructure folks) were approached by DevOps lead architect sharing their interests around evolving MW QE infrastructure in Boston for upcoming years. I would like to reiterate what was suggested to keep MW QE part of the conversation.
> Where we are?
> Boston hardware lab is going to be consolidated into 3rd party collocation center within a year or so. Nontrivial outage is expected because of that.
> Current MW QE hardware in Boston is getting underutilized as majority of workload was moved to central CI.
> Baremetal systems (exotic architectures, performance labs, messaging labs) are getting obsolete and unreliable.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (SWSQE-732) Mograte Off Of The Blade Center
by Matthew Mahoney (Jira)
Matthew Mahoney created SWSQE-732:
-------------------------------------
Summary: Mograte Off Of The Blade Center
Key: SWSQE-732
URL: https://issues.jboss.org/browse/SWSQE-732
Project: Kiali QE
Issue Type: Story
Reporter: Matthew Mahoney
Background information causing this Jira:
_Embrace 2019 MW QE infrastructure vision
During the QE camp, we (MW infrastructure folks) were approached by DevOps lead architect sharing their interests around evolving MW QE infrastructure in Boston for upcoming years. I would like to reiterate what was suggested to keep MW QE part of the conversation.
Where we are?
Boston hardware lab is going to be consolidated into 3rd party collocation center within a year or so. Nontrivial outage is expected because of that.
Current MW QE hardware in Boston is getting underutilized as majority of workload was moved to central CI.
Baremetal systems (exotic architectures, performance labs, messaging labs) are getting obsolete and unreliable.
_
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFWIP-161) OCSP configuration does not work
by Jan Stourac (Jira)
Jan Stourac created WFWIP-161:
---------------------------------
Summary: OCSP configuration does not work
Key: WFWIP-161
URL: https://issues.jboss.org/browse/WFWIP-161
Project: WildFly WIP
Issue Type: Bug
Components: Security
Environment: WildFly built with following branches in use:
{code}
https://github.com/nekdozjam/wildfly-elytron/tree/ELY-1617
https://github.com/nekdozjam/wildfly-core/tree/WFCORE-3947
{code}
Reporter: Jan Stourac
Assignee: Martin Mazanek
I tried to configure OCSP support in WildFly trust-manager, although it looks like I am not able to configure it properly. After all my steps (see in 'steps to reproduce' section), my WildFly server accepts clients both with valid and revoked certificates. Although expected behavior is to accept only the one with the valid certificate.
Looking in the OCSP responder log (OpenSSL used for this), it looks like there is even no request to it. Checked also Wireshark with same result - no request to OCSP responder on my machine.
As such, there is probably some problem in implementation or my actual configuration is buggy. Could you please check and give some advice?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3868) Upgrade antlr4-runtime version to 4.7.2
by Matteo Mortari (Jira)
[ https://issues.jboss.org/browse/DROOLS-3868?page=com.atlassian.jira.plugi... ]
Matteo Mortari updated DROOLS-3868:
-----------------------------------
Story Points: 5
Sprint: 2019 Week 17-19
> Upgrade antlr4-runtime version to 4.7.2
> ---------------------------------------
>
> Key: DROOLS-3868
> URL: https://issues.jboss.org/browse/DROOLS-3868
> Project: Drools
> Issue Type: Task
> Components: dmn engine
> Affects Versions: 7.20.0.Final
> Reporter: Dominik Hanak
> Assignee: Matteo Mortari
> Priority: Major
>
> There is a new version of antlr4-runtime - 4.7.2. We use 4.5.3 in community.
> It would be nice to upgrade to version 4.7.2.
> NOTE: This is also needed for - https://issues.jboss.org/browse/JBPM-8195
> I prepared a PR - https://github.com/kiegroup/droolsjbpm-build-bootstrap/pull/946
> Running FDB shows that 9 tests started to fail.
> These are the failed tests:
> {code:java}
> org.kie.dmn.core.DMNRuntimeTest.testInvalidVariableNames[true]
> org.kie.dmn.core.DMNRuntimeTest.testInvalidVariableNames[false]
> org.kie.dmn.feel.parser.feel11.FEELParserTest.testVariableNameWithInvalidCharacterPercent
> org.kie.dmn.feel.parser.feel11.FEELParserTest.testVariableNameWithInvalidCharacterAt
> org.kie.dmn.validation.ValidatorTest.testVALIDATION
> org.kie.dmn.validation.ValidatorTypeRefTest.testTYPEREF_NOT_FEEL_NOT_DEF_DefinitionsInput
> org.kie.dmn.validation.ValidatorTypeRefTest.testTYPEREF_NOT_FEEL_NOT_DEF_FileInput
> org.kie.dmn.validation.ValidatorTypeRefTest.testTYPEREF_NOT_FEEL_NOT_DEF_ReaderInput
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3868) Upgrade antlr4-runtime version to 4.7.2
by Matteo Mortari (Jira)
[ https://issues.jboss.org/browse/DROOLS-3868?page=com.atlassian.jira.plugi... ]
Matteo Mortari reassigned DROOLS-3868:
--------------------------------------
Assignee: Matteo Mortari (was: Dominik Hanak)
> Upgrade antlr4-runtime version to 4.7.2
> ---------------------------------------
>
> Key: DROOLS-3868
> URL: https://issues.jboss.org/browse/DROOLS-3868
> Project: Drools
> Issue Type: Task
> Components: dmn engine
> Affects Versions: 7.20.0.Final
> Reporter: Dominik Hanak
> Assignee: Matteo Mortari
> Priority: Major
>
> There is a new version of antlr4-runtime - 4.7.2. We use 4.5.3 in community.
> It would be nice to upgrade to version 4.7.2.
> NOTE: This is also needed for - https://issues.jboss.org/browse/JBPM-8195
> I prepared a PR - https://github.com/kiegroup/droolsjbpm-build-bootstrap/pull/946
> Running FDB shows that 9 tests started to fail.
> These are the failed tests:
> {code:java}
> org.kie.dmn.core.DMNRuntimeTest.testInvalidVariableNames[true]
> org.kie.dmn.core.DMNRuntimeTest.testInvalidVariableNames[false]
> org.kie.dmn.feel.parser.feel11.FEELParserTest.testVariableNameWithInvalidCharacterPercent
> org.kie.dmn.feel.parser.feel11.FEELParserTest.testVariableNameWithInvalidCharacterAt
> org.kie.dmn.validation.ValidatorTest.testVALIDATION
> org.kie.dmn.validation.ValidatorTypeRefTest.testTYPEREF_NOT_FEEL_NOT_DEF_DefinitionsInput
> org.kie.dmn.validation.ValidatorTypeRefTest.testTYPEREF_NOT_FEEL_NOT_DEF_FileInput
> org.kie.dmn.validation.ValidatorTypeRefTest.testTYPEREF_NOT_FEEL_NOT_DEF_ReaderInput
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton commented on DROOLS-3731:
-------------------------------------------
callouts got clipped, here's another pic in case it helps. !with_some_callouts.png|thumbnail!
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Test-error.png, Test-errorB.png, download (1).png, download.png, graph-test-click.png, graph-test-hover.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-3731:
--------------------------------------
Attachment: with_some_callouts.png
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Test-error.png, Test-errorB.png, download (1).png, download.png, graph-test-click.png, graph-test-hover.png, with_some_callouts.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton commented on DROOLS-3731:
-------------------------------------------
and !graph-test-click.png|thumbnail!
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Test-error.png, Test-errorB.png, download (1).png, download.png, graph-test-hover.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months