September 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-562) Docs: reporting activity info needs to be updated

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-562?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-562: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/205 > Docs: reporting activity info needs to be updated > ------------------------------------------------- > > Key: RTGOV-562 > URL: https://issues.jboss.org/browse/RTGOV-562 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Need to update dev guide reporting activity section. Direct injection no longer used, instead use the overlord-commons ServiceRegistry. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-564) Discriminate between Service Responsetime and component Responsetime in Kibana dashboard

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-564?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-564: ---------------------------------- I'm not entirely clear what representation you are looking for, although I understand the goal of trying to hide component services. Currently response times associated with promoted services have a 'gateway' property, so would you be able to create a dashboard of the style you are looking for, distinguishing the response information for promoted and component services using 'properties.gateway' field? If so, can you attach the modified dashboard on this jira and I'll try it out. Thanks. > Discriminate between Service Responsetime and component Responsetime in Kibana dashboard > ------------------------------------------------------------------------------------------ > > Key: RTGOV-564 > URL: https://issues.jboss.org/browse/RTGOV-564 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Affects Versions: 2.0.0.Final > Reporter: ivan mckinley > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Kibana ui > The current kibana dashboard shows the response times for all component response times. It was observed that this is not optimal and clear to end-users. Endusers would initially be most interested in the response times on the promoted interface “soap binding” for example. Independent to the switchyard world, this would mean only displaying the response time for the entire serviceTX (and ignoring the components response times) or as its know the activityUnit > Proposal, > that the landing kibana dashboard shows the response times for the entire serviceTX in a dedicated table and the response times for the components in another. > View the response of components could be another widget. i would not suggest another dashboard as this would mean users could not drill down into a service’s components > Example, in the default dashboard, the table LIST OF SERVICES TABLE. > This table displays the service tx response time but also the component response time. to the end user this not exactly clear > {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService > {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService/FundsService > {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService/InventoryService > {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService/LogisticsService > howto, > Perhaps a flag will be required on the response time object to discriminate component response time and service tx response times > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-570) Document Elasticsearch cluster configuration options

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-570?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-570. ------------------------------ Resolution: Done > Document Elasticsearch cluster configuration options > ---------------------------------------------------- > > Key: RTGOV-570 > URL: https://issues.jboss.org/browse/RTGOV-570 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Incorporate Ivan's information on clustering Elasticsearch into rtgov docs: > "Quick doc outline how Elasticsearch for FSW can be configured to > - become part of a ES cluster (default) > - act a a simple client but saving data a remote ES cluster > - INVM mode. when ES node is started in jboss jvm > https://mojo.redhat.com/groups/jboss-integration-sme/blog/2014/09/10/conf..." -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-570) Document Elasticsearch cluster configuration options

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-570?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-570: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/204 > Document Elasticsearch cluster configuration options > ---------------------------------------------------- > > Key: RTGOV-570 > URL: https://issues.jboss.org/browse/RTGOV-570 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Incorporate Ivan's information on clustering Elasticsearch into rtgov docs: > "Quick doc outline how Elasticsearch for FSW can be configured to > - become part of a ES cluster (default) > - act a a simple client but saving data a remote ES cluster > - INVM mode. when ES node is started in jboss jvm > https://mojo.redhat.com/groups/jboss-integration-sme/blog/2014/09/10/conf..." -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.s... ] Brett Meyer updated SRAMP-16: ----------------------------- Description: Introducing IDE-based tooling, interacting with the S-RAMP repo, brings up several interesting use cases. For instance, allowing an app developer to search for a WSDL in S-RAMP, then pull it down into his/her project (all from within the IDE) would be powerful. One idea would be to look into writing this as a JBoss Forge plugin. Not only would we gain Eclipse support, but also any other Forge-supported environment. The unknown is how to integrate that plugin with an Eclipse view UI, as opposed to simply relying on the Forge shell. was:Introducing IDE-based tooling, interacting with the S-RAMP repo, brings up several interesting use cases. > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: SRAMP-16 > URL: https://issues.jboss.org/browse/SRAMP-16 > Project: S-RAMP > Issue Type: Task > Components: IDE Integration > Affects Versions: 0.6.0 > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.6.0 > > > Introducing IDE-based tooling, interacting with the S-RAMP repo, brings up several interesting use cases. For instance, allowing an app developer to search for a WSDL in S-RAMP, then pull it down into his/her project (all from within the IDE) would be powerful. > One idea would be to look into writing this as a JBoss Forge plugin. Not only would we gain Eclipse support, but also any other Forge-supported environment. The unknown is how to integrate that plugin with an Eclipse view UI, as opposed to simply relying on the Forge shell. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.s... ] Brett Meyer updated SRAMP-16: ----------------------------- Description: Introducing IDE-based tooling, interacting with the S-RAMP repo, brings up several interesting use cases. (was: This issue is similar to the WebBased browser, but it should run inside the IDE. Maybe we can run it in Eclipse's WebContainer.) > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: SRAMP-16 > URL: https://issues.jboss.org/browse/SRAMP-16 > Project: S-RAMP > Issue Type: Task > Components: IDE Integration > Affects Versions: 0.6.0 > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.6.0 > > > Introducing IDE-based tooling, interacting with the S-RAMP repo, brings up several interesting use cases. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.s... ] Brett Meyer updated SRAMP-16: ----------------------------- Summary: Eclipse IDE: S-RAMP tooling (was: Browse the S-RAMP repository from within the IDE) > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: SRAMP-16 > URL: https://issues.jboss.org/browse/SRAMP-16 > Project: S-RAMP > Issue Type: Task > Components: IDE Integration > Affects Versions: 0.6.0 > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.6.0 > > > This issue is similar to the WebBased browser, but it should run inside the IDE. Maybe we can run it in Eclipse's WebContainer. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-574) Investigate 'index already exists' exception when previous command indicates does not exist

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-574?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-574: ---------------------------------- Thanks for the clarification - could you raise a bug regarding the context classloader and we can see whether this can be addressed and still support fuse :) > Investigate 'index already exists' exception when previous command indicates does not exist > ------------------------------------------------------------------------------------------- > > Key: RTGOV-574 > URL: https://issues.jboss.org/browse/RTGOV-574 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > > When updating to Elasticsearch 1.3.2 (RTGOV-568), noticed that when the EAP server was restarted, it resulted in an IndexAlreadyExistsException from ES. > However this exception was generated from code called to create the indexes - however prior to that call it checks with the ES node whether the indexes already exist. > Ivan McKinley found the following reference that may be relevant: http://stackoverflow.com/questions/23883110/elasticsearch-index-exists-no... > He also suggests: > "If this is the problem then we may have an impact from running “embedded” mode. The more data we have the longer response from the async process perhaps. > externalising the es process may resolve this.. and another test is to remove the entire contents of the index/type/ to further prove that we are affect the amount of data. > The various scenarios here are definitely interesting for us regarding documentation" -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-574) Investigate 'index already exists' exception when previous command indicates does not exist

by ivan mckinley (JIRA)

[ https://issues.jboss.org/browse/RTGOV-574?page=com.atlassian.jira.plugin.... ] ivan mckinley commented on RTGOV-574: ------------------------------------- yes theres a reason, the rtgov index and types do not change. but in the event we need to add attributes applying mappings at each start allows us to do this. If a mapping configuration already exist then no changes occur on the ES backend. this is only concerned with additional attributes. The reasoning behind such a setup was to allow users to apply their ES types and indexes and add attributes as their project develops FYI: this feature no longer works since this line has been added from the karaf support. "Thread.currentThread().setContextClassLoader(TransportClient.class.getClassLoader());" the classcontext mean it cannot find any customer mapping files supplied by the end-users. > Investigate 'index already exists' exception when previous command indicates does not exist > ------------------------------------------------------------------------------------------- > > Key: RTGOV-574 > URL: https://issues.jboss.org/browse/RTGOV-574 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > > When updating to Elasticsearch 1.3.2 (RTGOV-568), noticed that when the EAP server was restarted, it resulted in an IndexAlreadyExistsException from ES. > However this exception was generated from code called to create the indexes - however prior to that call it checks with the ES node whether the indexes already exist. > Ivan McKinley found the following reference that may be relevant: http://stackoverflow.com/questions/23883110/elasticsearch-index-exists-no... > He also suggests: > "If this is the problem then we may have an impact from running “embedded” mode. The more data we have the longer response from the async process perhaps. > externalising the es process may resolve this.. and another test is to remove the entire contents of the index/type/ to further prove that we are affect the amount of data. > The various scenarios here are definitely interesting for us regarding documentation" -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-539) Change pom.xml version property format to "version.x.y.x"

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-539?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-539. ------------------------------ Resolution: Done Assume this issue can now be closed. If not, please reopen. Thanks Brett. > Change pom.xml version property format to "version.x.y.x" > --------------------------------------------------------- > > Key: RTGOV-539 > URL: https://issues.jboss.org/browse/RTGOV-539 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 2.0.0.Final > > > Currently we use x.y.z.version in the overlord projects. > We need to change this in all Overlord projects, not just S-RAMP. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues September 2014