[JBoss JIRA] (RTGOV-272) Activity store implementation for Cassandra
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-272?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-272:
----------------------------------
There are a number of steps to this task:
1) Implement the Apache Cassandra version of the ActivityStore API. This module should be created in the $rtgov/modules/activity-management location
2) Identify best way to initialize the schema in the Cassandra db.
a) In EAP(JBossAS): For JPA, the rtgov install procedure initializes a H2 db. The FSW product has a more comprehensive configuration to support multiple relational databases. Need to consider whether the user should be offered the option of using Cassandra during the install, and if so perform the necessary steps there?
b) In Karaf: currently the activity store impl is installed as a separate feature. This may be the way to go in OSGi, so the user would select the activity store impl based on the feature they install. So need to add a cassandra based feature into the $rtgov/release/karaf/features/pom.xml - however this does not result in an initialized db - so this may need to be performed outside the installation of rtgov in karaf/fuse.
3) In the release/jbossas/war-server - include the CassandraActivityStore artifact, so the jar is packaged in the war. However this won't automatically use this implementation on deployment, the "ActivityStore.class" property needs to be defined in the $eap/standalone/config/overlord-rtgov.properties file, to define the class name of the activity store to use, if no the default JPA implementation.
4) Integration testing:
a) EAP/JBossAS - uses arquillian to automate startup of the server, deployment of tests, etc. These tests are in $rtgov/release/jbossas/tests. The tests under the 'platform' sub folder install a full version of rtgov into the test EAP environment, which by default will use the JPA activity store. Not sure currently how the tests can override the overlord-rtgov.properties, before the components are initialized. So the alternative would be to install just the required components, as performed in tests/activity-management/activity-server-rest, which uses the inmemory implementation of the activity store.
b) Karaf/Fuse - no integration test mechanism currently provided, so will need to add this in the future.
5) Documentation - initially record any new usage information in this jira, but then can be added to the documentation located here: https://github.com/Governance/rtgov/wiki/_pages (see instructions on how to update the docs here: https://github.com/Governance/rtgov/wiki/DocsReadme)
> Activity store implementation for Cassandra
> -------------------------------------------
>
> Key: RTGOV-272
> URL: https://issues.jboss.org/browse/RTGOV-272
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.M1
>
>
> Provide a Cassandra implementation of the ActivityStore.
--
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, 9 months
[JBoss JIRA] (RTGOV-376) Migrate RESTful services from CXF to RESTEasy
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-376?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-376.
------------------------------
Resolution: Done
REST services are now at the same URLs on Karaf and EAP. Only difference is the default port (8080 on EAP and 8181 on Karaf).
> Migrate RESTful services from CXF to RESTEasy
> ---------------------------------------------
>
> Key: RTGOV-376
> URL: https://issues.jboss.org/browse/RTGOV-376
> Project: RTGov (Run Time Governance)
> Issue Type: Sub-task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.M1
>
>
> Initial work in RTGOV-274 created a set of RESTful services using cxf. However this causes the services to have a context of 'cxf'.
> Porting to RESTEasy enables the overlord-rtgov context to be used across EAP and Fuse, and may provide other benefits from using a consistent REST library (e.g. security).
--
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, 9 months
[JBoss JIRA] (RTGOV-404) Role-based access control for various action
by Michael Clay (JIRA)
Michael Clay created RTGOV-404:
----------------------------------
Summary: Role-based access control for various action
Key: RTGOV-404
URL: https://issues.jboss.org/browse/RTGOV-404
Project: RTGov (Run Time Governance)
Issue Type: Feature Request
Components: User Interface
Reporter: Michael Clay
Assignee: Gary Brown
we need to control the following actions based on the current role of the user
- filtering of situations i.e. situations visibility based on roles
- assignment, retry and export
--
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, 9 months
[JBoss JIRA] (RTGOV-371) ElasticSearch implementation of the Metrics Provider API
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-371?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-371:
-----------------------------
Component/s: User Interface
> ElasticSearch implementation of the Metrics Provider API
> --------------------------------------------------------
>
> Key: RTGOV-371
> URL: https://issues.jboss.org/browse/RTGOV-371
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Components: User Interface
> Reporter: Gary Brown
> Assignee: Gary Brown
>
> Implement an ElasticSearch based MetricsProvider to obtain information about a service.
> Additional (optional) configuration information should be used to define a time window for the queries - so (for example) an administrator could indicate that the summary metric information should only be related to the past 24 hours.
> Use the ElasticSearch Java library. Optional config property (obtained from RTGovProperties) to obtain the URL of the ElasticSearch server - otherwise assume running locally.
> Use the 'responsetime' mapping information from the 'rtgov' index, based on the instructions for setting up a demo environment (https://community.jboss.org/thread/237948).
--
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, 9 months