January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11578) Distinguish type of WildFly metrics

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-11578: ---------------------------------- Summary: Distinguish type of WildFly metrics Key: WFLY-11578 URL: https://issues.jboss.org/browse/WFLY-11578 Project: WildFly Issue Type: Enhancement Reporter: Jeff Mesnil Assignee: Jeff Mesnil Following WFCORE-4238, annotate WildFly attributes that corresponds to metrics with COUNTER_METRIC flag when appropriate. Update the microprofile-metrics-smallrye extension to check the presence of this flag in order to create appropriate metrics for its Prometheus output. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3475) [DMN Designer] Ensure integrity of DecisionService node

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3475?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3475: ----------------------------------- Description: The {{DecisionService}} node contains lists of {{DMNElementReference}} for "Output Decisions", "Encapsulated Decisions", "Input Decision" and "Input Data". These are currently only populated when unmarshalling a DMN XML file to Stunner model. Their members are not maintained as and when Users add, delete etc nodes that could affect them. They are used as reference when marshalling back from Stunner to DML XML to maintain the positional information \[*\] of such references. The {{DecisionService}} node reference lists should be updated as and when the User interacts with the diagram (e.g. add/remove "Output Decision" to/from the "Decision Service", add/remove "Encapsulated Decision" to/from the "Decision Service", add/remove an "Input Data" or "Input Decision" reference to/from the "Decision Service" or move the "splitter" in such a way that could affect the "Output/Encapsulated" Decisions. This will require (at least) custom commands for add/remove child, add connection and update property (splitter location). \[*\] See [here|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-...] that uses the order of the references set-up during marshalling from XML to Stunner to ensure identical references maintain the same index in the list marshalled from Stunner to XML. This is a DMN Specification requirement that "positional information" is preserved (without using this transient mechanism it would otherwise be impossible to preserve the index order as XML->Stunner looses the lists and Stunner->XML walks the graph to add element references to the Decision Service. The original ordering is lost by the conversion from {{List}} to _Graph_ to {{List}}. This "workaround" to preserve ordering should NOT be required when the integrity of {{DecisionService}} Node's element references is maintained by custom commands. was: The {{DecisionService}} node contains lists of {{DMNElementReference}} for "Output Decisions", "Encapsulated Decisions", "Input Decision" and "Input Data". These are currently only populated when unmarshalling a DMN XML file to Stunner model. Their members are not maintained as and when Users add, delete etc nodes that could affect them. They are used as reference when marshalling back from Stunner to DML XML to maintain the positional information \[*\] of such references. The {{DecisionService}} node reference lists should be updated as and when the User interacts with the diagram (e.g. add/remove "Output Decision" to/from the "Decision Service", add/remove "Encapsulated Decision" to/from the "Decision Service", add/remove an "Input Data" or "Input Decision" reference to/from the "Decision Service" or move the "splitter" in such a way that could affect the "Output/Encapsulated" Decisions. This will require (at least) custom commands for add/remove child, add connection and update property (splitter location). \[*\] See [here|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-...] that uses the order of the references set-up during marshalling from XML to Stunner to ensure identical references maintain the same index in the list marshalled from Stunner to XML. This is a DMN Specification requirement that "positional information" is preserved (without using this transient mechanism it would otherwise be impossible to preserve the index order as XML->Stunner looses the lists and Stunner->XML walks the graph to add element references to the Decision Service. The original ordering is lost by the conversion from {{List}}->_Graph_->{{List}}. This "workaround" to preserve ordering should NOT be required when the integrity of {{DecisionService}} Node's element references is maintained by custom commands. > [DMN Designer] Ensure integrity of DecisionService node > ------------------------------------------------------- > > Key: DROOLS-3475 > URL: https://issues.jboss.org/browse/DROOLS-3475 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.15.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > The {{DecisionService}} node contains lists of {{DMNElementReference}} for "Output Decisions", "Encapsulated Decisions", "Input Decision" and "Input Data". These are currently only populated when unmarshalling a DMN XML file to Stunner model. Their members are not maintained as and when Users add, delete etc nodes that could affect them. They are used as reference when marshalling back from Stunner to DML XML to maintain the positional information \[*\] of such references. > The {{DecisionService}} node reference lists should be updated as and when the User interacts with the diagram (e.g. add/remove "Output Decision" to/from the "Decision Service", add/remove "Encapsulated Decision" to/from the "Decision Service", add/remove an "Input Data" or "Input Decision" reference to/from the "Decision Service" or move the "splitter" in such a way that could affect the "Output/Encapsulated" Decisions. This will require (at least) custom commands for add/remove child, add connection and update property (splitter location). > \[*\] See [here|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-...] that uses the order of the references set-up during marshalling from XML to Stunner to ensure identical references maintain the same index in the list marshalled from Stunner to XML. This is a DMN Specification requirement that "positional information" is preserved (without using this transient mechanism it would otherwise be impossible to preserve the index order as XML->Stunner looses the lists and Stunner->XML walks the graph to add element references to the Decision Service. The original ordering is lost by the conversion from {{List}} to _Graph_ to {{List}}. > This "workaround" to preserve ordering should NOT be required when the integrity of {{DecisionService}} Node's element references is maintained by custom commands. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-471) Kiali Python Client 0.12

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-471?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-471. ------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) Resolution: Done > Kiali Python Client 0.12 > ------------------------ > > Key: SWSQE-471 > URL: https://issues.jboss.org/browse/SWSQE-471 > Project: Kiali QE > Issue Type: Story > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Major > Labels: kiali-python-client > > Currently there are no tests to validate that the Kiali Python Client is working properly with the Kiali REST API. The purpose of this Story is to get into place a set of tests that validate each of the supported Python Client API methods. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-539) Negative Tests Cases around the Kiali API

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-539?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-539. ------------------------------------------- Resolution: Done Negative Test cases were merged > Negative Tests Cases around the Kiali API > ----------------------------------------- > > Key: SWSQE-539 > URL: https://issues.jboss.org/browse/SWSQE-539 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Sunil kondkar > Priority: Major > > [~skondkar] > The swagger (https://github.com/kiali/kiali/blob/master/swagger.json) specifies the happy path and what happens when the request is not correct. > I think we need cover these unhappy paths for Kiali API -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3475) [DMN Designer] Ensure integrity of DecisionService node

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3475?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3475: ----------------------------------- Sprint: 2019 Week 02-04 > [DMN Designer] Ensure integrity of DecisionService node > ------------------------------------------------------- > > Key: DROOLS-3475 > URL: https://issues.jboss.org/browse/DROOLS-3475 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.15.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > The {{DecisionService}} node contains lists of {{DMNElementReference}} for "Output Decisions", "Encapsulated Decisions", "Input Decision" and "Input Data". These are currently only populated when unmarshalling a DMN XML file to Stunner model. Their members are not maintained as and when Users add, delete etc nodes that could affect them. They are used as reference when marshalling back from Stunner to DML XML to maintain the positional information \[*\] of such references. > The {{DecisionService}} node reference lists should be updated as and when the User interacts with the diagram (e.g. add/remove "Output Decision" to/from the "Decision Service", add/remove "Encapsulated Decision" to/from the "Decision Service", add/remove an "Input Data" or "Input Decision" reference to/from the "Decision Service" or move the "splitter" in such a way that could affect the "Output/Encapsulated" Decisions. This will require (at least) custom commands for add/remove child, add connection and update property (splitter location). > \[*\] See [here|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-...] that uses the order of the references set-up during marshalling from XML to Stunner to ensure identical references maintain the same index in the list marshalled from Stunner to XML. This is a DMN Specification requirement that "positional information" is preserved (without using this transient mechanism it would otherwise be impossible to preserve the index order as XML->Stunner looses the lists and Stunner->XML walks the graph to add element references to the Decision Service. The original ordering is lost by the conversion from {{List}}->_Graph_->{{List}}. > This "workaround" to preserve ordering should NOT be required when the integrity of {{DecisionService}} Node's element references is maintained by custom commands. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-542) Bookinfo Deploy Failure

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-542?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-542. ------------------------------------------- Resolution: Done > Bookinfo Deploy Failure > ----------------------- > > Key: SWSQE-542 > URL: https://issues.jboss.org/browse/SWSQE-542 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Please take a look at this book info deploy failure: > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Istio-and-Kiali-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-239) Establish Hardware Scenarios to Test (Footprints)

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-239?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-239: ------------------------------------------ Sprint: Kiali QE Sprint 7, Kiali Sprint #16 (was: Kiali QE Sprint 7) > Establish Hardware Scenarios to Test (Footprints) > -------------------------------------------------- > > Key: SWSQE-239 > URL: https://issues.jboss.org/browse/SWSQE-239 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > As an administrator, I want to know what is minimum requirements to run Kiali > As a Kiali Tester, I want to know what is the recommend testing hardware that tests are going to simulate. > Some notes: > Minimum requirements to run Kiali (~ 16gb?) > Action Item: Ask Kevin Corner about customer environment size > On small openshift cluster? > One Namespace with Hundreds Services > Multiple Namespace with Hundreds and 5 Services -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-312) Test Bookinfo with High Load Traffic

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-312?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-312: ------------------------------------------ Sprint: Kiali QE Sprint 7, Kiali Sprint #16 (was: Kiali QE Sprint 7) > Test Bookinfo with High Load Traffic > ------------------------------------ > > Key: SWSQE-312 > URL: https://issues.jboss.org/browse/SWSQE-312 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Test Bookinfo in order to see how kiali behaves when a mesh has high load traffic. > - This test will allow seeing if traffic animation will behave right -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-552) Checker Fails With Maistra Deploy

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-552?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-552: ------------------------------------------ Sprint: Kiali Sprint #16 (was: Kiali Sprint #16) > Checker Fails With Maistra Deploy > --------------------------------- > > Key: SWSQE-552 > URL: https://issues.jboss.org/browse/SWSQE-552 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-234) Scalability Testing on Configurations (Number of Services on Mesh)

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-234?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-234: ------------------------------------------ Sprint: Kiali QE Sprint 7, Kiali Sprint #16 (was: Kiali QE Sprint 7) > Scalability Testing on Configurations (Number of Services on Mesh) > ------------------------------------------------------------------ > > Key: SWSQE-234 > URL: https://issues.jboss.org/browse/SWSQE-234 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > As an administrator, I want to know what is "theoretical" limit of test meshes configurations (number of services, versions) that can be displayed on Kiali UI. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 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 January 2019