July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-651) Refactor Kiali Performance Job

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-651?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-651: ------------------------------------------ Labels: performance (was: ) Sprint: Kiali Sprint #25 > Refactor Kiali Performance Job > ------------------------------- > > Key: SWSQE-651 > URL: https://issues.jboss.org/browse/SWSQE-651 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > Labels: performance > > Kiali Performance Job needs to be refactored to reflect changes (https://github.com/kiali/kiali-performance-testing/pull/1) and (https://github.com/kiali/kiali-performance-testing/pull/2) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-829) Prepare for Middleware Infra Upgrade

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-829?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-829: ------------------------------------- Added planning document - https://docs.google.com/document/d/1QRABnGYjgG9J0_QImiMPA78uL8NXmjLJbV864... > Prepare for Middleware Infra Upgrade > ------------------------------------ > > Key: SWSQE-829 > URL: https://issues.jboss.org/browse/SWSQE-829 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > There is outage scheduled for MW Lab. We need to prepare plan for that. > More info: > Hi, > You are receiving this email as a stakeholder of the Middleware lab environment which will be impacted by the following lab work. > We are working on a project to upgrade the old Cisco networking infrastructure in the labs to new Juniper hardware. > This work will impact all Middleware systems which are in Westford Lab 3. That is, anything with an IP address starting with 10.16.x.x, things with 10.19.x.x addresses will not be impacted. > A spreadsheet listing the systems including all hardware can be found here: https://docs.google.com/spreadsheets/d/1lSB0cAfX2Jvp0iCJn4gsuArw8mlyqZnG4... > Note that this may not show all virtual systems. > The main work will be done in two parts: > First, we will swap out switches for all the system listed on the "Row E" tab of the spreadsheet. This is scheduled to be done on Monday, August 12th and Tuesday the 13th. > After that we will swap out switches for everything else listed on "Row D" and "Row C". This is scheduled to be done on Tuesday, August 20th and Wednesday the 21st. > Please expect the noted systems to be unavailable during these days. > These dates were scheduled to try to accommodate product releases, though it looks like a couple things were pushed back so it shouldn't be a problem. > In preparation for this we will also need to migrate the routing instance for all the affected networks. This will be a much shorter maintenance, no more than an hour should be needed. > I was advised that this should just be done outside of BRQ working hours, so will probably be done on a Friday evening or over the weekend. I will update when we have a solid timeframe for that. > Additionally, there are a few systems that will need to get moved to the middleware network, and some things which should be physically moved. I will send a separate email to people regarding those. > Most things, however, will not be getting new addresses and will simply be inaccessible for the duration of the work. > Following each maintenance window the systems should be back online and otherwise unaffected. However, if you do encounter any problems please feel free to respond directly to this email. > If you experience issues outside of business hours please refer to the escalation procedures found here: https://mojo.redhat.com/docs/DOC-1049381 > Let me know if you have any questions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Klara Kufova reopened DROOLS-4161: ---------------------------------- Reopening just to make sure [~aglass]' comment is addressed. > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4255) Add KIE server support for deploying custom Prometheus metrics

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-4255?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-4255: --------------------------------- Story Points: 5 > Add KIE server support for deploying custom Prometheus metrics > -------------------------------------------------------------- > > Key: DROOLS-4255 > URL: https://issues.jboss.org/browse/DROOLS-4255 > Project: Drools > Issue Type: Enhancement > Components: kie server > Affects Versions: 7.24.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Major > Labels: CustomerFocus > Fix For: 7.25.0.Final > > > The first implementation of Prometheus support in Kie provided default Prometheus metrics. We should enable our users to deploy their custom Prometheus metrics in addition to default Prometheus metrics already published. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-812) Kiali - Create TP12 Polarion PQI reports

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-812?page=com.atlassian.jira.plugin.... ] Sunil Kondkar commented on SWSQE-812: ------------------------------------- Linked below test runs to the Kiali iteration plan for TP12: https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... PQI Report: https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... > Kiali - Create TP12 Polarion PQI reports > ---------------------------------------- > > Key: SWSQE-812 > URL: https://issues.jboss.org/browse/SWSQE-812 > Project: Kiali QE > Issue Type: QE Task > Reporter: Sunil Kondkar > Assignee: Sunil Kondkar > Priority: Major > Labels: pqi > > Get PQI reports for Kiali: > 1) Check Test case Quality Audit report(No missing data) > 2) PQI reports - Create TP12 test iteration, link this iteration to Kiali TP12 test runs -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-811) Jaeger - Create TP12 Polarion PQI reports

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-811?page=com.atlassian.jira.plugin.... ] Sunil Kondkar commented on SWSQE-811: ------------------------------------- Linked below test run to the Jaeger iteration plan for TP12: https://polarion.engineering.redhat.com/polarion/#/project/Jaeger/testrun... PQI report in Polarion: https://polarion.engineering.redhat.com/polarion/#/project/Jaeger/wiki/Re... > Jaeger - Create TP12 Polarion PQI reports > ----------------------------------------- > > Key: SWSQE-811 > URL: https://issues.jboss.org/browse/SWSQE-811 > Project: Kiali QE > Issue Type: QE Task > Reporter: Sunil Kondkar > Assignee: Sunil Kondkar > Priority: Major > Labels: pqi > > Get PQI reports for Jaeger: > 1) Check Test case Quality Audit report(No missing data) > 2) PQI reports - Create TP12 test iteration, link this iteration to Jaeger TP12 test runs -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-829) Prepare for Middleware Infra Upgrade

by Filip Brychta (Jira)

Filip Brychta created SWSQE-829: ----------------------------------- Summary: Prepare for Middleware Infra Upgrade Key: SWSQE-829 URL: https://issues.jboss.org/browse/SWSQE-829 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta There is outage scheduled for MW Lab. We need to prepare plan for that. More info: Hi, You are receiving this email as a stakeholder of the Middleware lab environment which will be impacted by the following lab work. We are working on a project to upgrade the old Cisco networking infrastructure in the labs to new Juniper hardware. This work will impact all Middleware systems which are in Westford Lab 3. That is, anything with an IP address starting with 10.16.x.x, things with 10.19.x.x addresses will not be impacted. A spreadsheet listing the systems including all hardware can be found here: https://docs.google.com/spreadsheets/d/1lSB0cAfX2Jvp0iCJn4gsuArw8mlyqZnG4... Note that this may not show all virtual systems. The main work will be done in two parts: First, we will swap out switches for all the system listed on the "Row E" tab of the spreadsheet. This is scheduled to be done on Monday, August 12th and Tuesday the 13th. After that we will swap out switches for everything else listed on "Row D" and "Row C". This is scheduled to be done on Tuesday, August 20th and Wednesday the 21st. Please expect the noted systems to be unavailable during these days. These dates were scheduled to try to accommodate product releases, though it looks like a couple things were pushed back so it shouldn't be a problem. In preparation for this we will also need to migrate the routing instance for all the affected networks. This will be a much shorter maintenance, no more than an hour should be needed. I was advised that this should just be done outside of BRQ working hours, so will probably be done on a Friday evening or over the weekend. I will update when we have a solid timeframe for that. Additionally, there are a few systems that will need to get moved to the middleware network, and some things which should be physically moved. I will send a separate email to people regarding those. Most things, however, will not be getting new addresses and will simply be inaccessible for the duration of the work. Following each maintenance window the systems should be back online and otherwise unaffected. However, if you do encounter any problems please feel free to respond directly to this email. If you experience issues outside of business hours please refer to the escalation procedures found here: https://mojo.redhat.com/docs/DOC-1049381 Let me know if you have any questions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-3879) Create Kogito version of Test Scenarios designer

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3879?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3879: --------------------------------- Story Points: 3 (was: 13) > Create Kogito version of Test Scenarios designer > ------------------------------------------------ > > Key: DROOLS-3879 > URL: https://issues.jboss.org/browse/DROOLS-3879 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > > Create the *Kogito* versions of scesim editor. > No Home Page, no Library, No preferences, no other editors. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Amy Glass (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Amy Glass commented on DROOLS-4161: ----------------------------------- I added one comment to the Marvel just now, fyi. Proposing a small change [~zhutaojiajia] > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Klara Kufova resolved DROOLS-4161. ---------------------------------- Resolution: Done > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

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 July 2019