April 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-382) Support EAP 6.3

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/SRAMP-382?page=com.atlassian.jira.plugin.... ] Gary Brown updated SRAMP-382: ----------------------------- Summary: Support EAP 6.3 (was: Support EAP 6.2) Description: Add support for EAP 6.3. (was: Add support for EAP 6..) Assignee: Eric Wittmann (was: Kurt Stam) > Support EAP 6.3 > --------------- > > Key: SRAMP-382 > URL: https://issues.jboss.org/browse/SRAMP-382 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Eric Wittmann > Fix For: 0.5.0 - API Management > > > Add support for EAP 6.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-431) Upgrade to EAP 6.3

by Gary Brown (JIRA)

Gary Brown created RTGOV-431: -------------------------------- Summary: Upgrade to EAP 6.3 Key: RTGOV-431 URL: https://issues.jboss.org/browse/RTGOV-431 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-89) Create Policy derived artifact handler

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-89?page=com.atlassian.jira.plugin.s... ] Eric Wittmann commented on SRAMP-89: ------------------------------------ http://www.ibm.com/developerworks/webservices/tutorials/ws-understand-web... > Create Policy derived artifact handler > -------------------------------------- > > Key: SRAMP-89 > URL: https://issues.jboss.org/browse/SRAMP-89 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0 - API Management > > > Create the handler that will produce the Derived Artifacts for ws-policy artifacts. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-415) ElasticSearch Activity Store implementation

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-415: ---------------------------------- The implementation of the activity store may use the ElasticSearch KeyValueStore - or atleast reuse the bulk storage approach - so added a dependency on that task. > ElasticSearch Activity Store implementation > ------------------------------------------- > > Key: RTGOV-415 > URL: https://issues.jboss.org/browse/RTGOV-415 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Although it is not currently clear whether organisations would rely on ElasticSearch as a database for their activity information, it will be good to be able to offer it as an alternative. > If configured, then it will store the ActivityUnit, and any subsequent EPN can be used to store the derived information (e.g. situations and response times). > ElasticSearch has improved its support for backup/restore, so could potentially be used as a primary db for this type of information - although it is not transactional. > The module should be defined in modules/activity-management/activity-store-es (or elasticsearch - whatever is consistent with RTGOV-342). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-415) ElasticSearch Activity Store implementation

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin.... ] Gary Brown reassigned RTGOV-415: -------------------------------- Assignee: Gary Brown (was: ivan mckinley) > ElasticSearch Activity Store implementation > ------------------------------------------- > > Key: RTGOV-415 > URL: https://issues.jboss.org/browse/RTGOV-415 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Although it is not currently clear whether organisations would rely on ElasticSearch as a database for their activity information, it will be good to be able to offer it as an alternative. > If configured, then it will store the ActivityUnit, and any subsequent EPN can be used to store the derived information (e.g. situations and response times). > ElasticSearch has improved its support for backup/restore, so could potentially be used as a primary db for this type of information - although it is not transactional. > The module should be defined in modules/activity-management/activity-store-es (or elasticsearch - whatever is consistent with RTGOV-342). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-430) Remove gadget server from RTGov deployment and install RTGov-UI instead

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-430?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-430: ---------------------------------- Fixed - pending PR merge. > Remove gadget server from RTGov deployment and install RTGov-UI instead > ----------------------------------------------------------------------- > > Key: RTGOV-430 > URL: https://issues.jboss.org/browse/RTGOV-430 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Remove gadget server from the rtgov deployment and instead deploy the new rtgov-ui. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-430) Remove gadget server from RTGov deployment and install RTGov-UI instead

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-430?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-430: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/55 > Remove gadget server from RTGov deployment and install RTGov-UI instead > ----------------------------------------------------------------------- > > Key: RTGOV-430 > URL: https://issues.jboss.org/browse/RTGOV-430 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Remove gadget server from the rtgov deployment and instead deploy the new rtgov-ui. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-342) ElasticSearch Event Processor implementation

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-342?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-342. ------------------------------ Resolution: Done > ElasticSearch Event Processor implementation > -------------------------------------------- > > Key: RTGOV-342 > URL: https://issues.jboss.org/browse/RTGOV-342 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Reporter: Gary Brown > Assignee: ivan mckinley > Fix For: 2.0.0.Final > > > The EventProcessor configuration should be provided with: > a) Index name > b) Type name > c) MVEL expression for obtaining id from the event > NOTE: Also need to be able to indicate that a random id should be used - possibly if mvel expression is not defined? > If REST call does not succeed, then throw exception to prompt a retry of the event. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-420) Avoid having host location details in ElasticSearch EPNs

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-420?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-420. ------------------------------ Resolution: Done Fixed as part of the commit for RTGOV-422. > Avoid having host location details in ElasticSearch EPNs > -------------------------------------------------------- > > Key: RTGOV-420 > URL: https://issues.jboss.org/browse/RTGOV-420 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Reporter: Gary Brown > Assignee: ivan mckinley > Fix For: 2.0.0.Final > > > Discussion from forum post > " Hosts should be retrieved from RTGovProperties so that can be independently configured by administrator, rather than having to redeploy EPN if a change is required. If not defined, then use default value. Potentially the installer can be updated to ask if ES is used, and install epns and optional hosts configuration. > > I’m not sure of this. it may be desired to have certain Stores to connect directly to a specific set of nodes as we know data is stored there. Other wise ES will lookup where the data resides. Further investigated is need into how elastic searches clustering works before a anything is done here. " > As a compromise, was wondering whether the ESKeyValueStore could have an optional 'server group' name, which could then be located in the RTGovProperties to obtain the actual host detail(s). If the defined server group does not exist, or is not defined, then a default host value will be checked. And if that does not exist, then a default localhost location will be used. > Aim is to move administrator related information outside the EPN which is more in the realm of the business/app developers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-343) EPN to store activity events, response times and situations in ElasticSearch

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-343?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-343. ------------------------------ Resolution: Done Fixed as part of the commit for RTGOV-422. > EPN to store activity events, response times and situations in ElasticSearch > ---------------------------------------------------------------------------- > > Key: RTGOV-343 > URL: https://issues.jboss.org/browse/RTGOV-343 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Reporter: Gary Brown > Assignee: ivan mckinley > Fix For: 2.0.0.Final > > > Standard EPN deployment for storing activity events and situations in ElasticSearch. > The ActivityUnit (possibly minus the events, although would provide efficient retrieval of the whole unit) should be stored as one type, the ActivityType derived objects as another, response times and the situations as their own type. > Build the EPN, but it shouldn't be included in the standard deployment - possibly have an 'extension' folder in the distribution for optional deployable artifacts with relevant notes - i.e. so they don't all need to be discussed in the main docs? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

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 April 2014