[JBoss JIRA] (RTGOV-421) Make ElasticSearch EventProcessor more generic
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-421?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-421.
------------------------------
Resolution: Done
> Make ElasticSearch EventProcessor more generic
> ----------------------------------------------
>
> Key: RTGOV-421
> URL: https://issues.jboss.org/browse/RTGOV-421
> Project: RTGov (Run Time Governance)
> Issue Type: Sub-task
> Reporter: Gary Brown
> Assignee: ivan mckinley
> Fix For: 2.0.0.Final
>
>
> As discussed in forum post (point 3), as the ElasticSearch capabilities are now encapsulated in the KeyValueStore implementation, it makes sense to make the EventProcessor more generic to cater for any key/store implementation.
> As pointed out by Ivan, some custom capabilities may be required by particular KeyValueStore implementations (e.g. MongoDB, Cassandra), but these can be added later as extensions to the generic event processor.
--
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, 6 months
[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:
----------------------------------
No haven't started, so that is fine.
> 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: ivan mckinley
> 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, 6 months
[JBoss JIRA] (SRAMP-384) Add validation for password in overlord commons installer
by David virgil naranjo (JIRA)
[ https://issues.jboss.org/browse/SRAMP-384?page=com.atlassian.jira.plugin.... ]
David virgil naranjo commented on SRAMP-384:
--------------------------------------------
I included the confirmation password. Also I created a do while, until the user prompt a password that would pass the jboss user validations.
> Add validation for password in overlord commons installer
> ---------------------------------------------------------
>
> Key: SRAMP-384
> URL: https://issues.jboss.org/browse/SRAMP-384
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
> Fix For: 0.5.0 - API Management
>
>
> Currently the overlord commons installer is responsible for doing all security related work. This includes creating the overlord 'admin' user and configured a password for this user. The installer prompts the user for this password and then passes whatever the user entered to the JBoss EAP add-user utility. This utility will fail if the password does not meet certain standards. However, the utility fails without failing the overall install.
> The installer should do its own validation of the password entered by the user so that this silent failure doesn't happen. Also note that the password input and validation should happen before anything else security related gets installed.
--
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, 6 months
[JBoss JIRA] (SRAMP-403) S-RAMP On complete show required parameters with bold style
by David virgil naranjo (JIRA)
David virgil naranjo created SRAMP-403:
------------------------------------------
Summary: S-RAMP On complete show required parameters with bold style
Key: SRAMP-403
URL: https://issues.jboss.org/browse/SRAMP-403
Project: S-RAMP
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: David virgil naranjo
Assignee: David virgil naranjo
Add a custom OptionRenderer for all the required options. That will allow the user to distinguish when clicking tab button, if an option is required or not.
--
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, 6 months
[JBoss JIRA] (SRAMP-397) SRAMP Shell Create custom aesh help format
by David virgil naranjo (JIRA)
[ https://issues.jboss.org/browse/SRAMP-397?page=com.atlassian.jira.plugin.... ]
David virgil naranjo commented on SRAMP-397:
--------------------------------------------
Not possible to implement right now, because Aesh functionality does not contain this functionality. I have informed them and they created a jira associated and will implement in a new version of aesh.
> SRAMP Shell Create custom aesh help format
> ------------------------------------------
>
> Key: SRAMP-397
> URL: https://issues.jboss.org/browse/SRAMP-397
> Project: S-RAMP
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: David virgil naranjo
> Assignee: David virgil naranjo
>
> The basic Aesh settings display all the options when --help is set as argument. It is not displayed in good style and also is not displayed which of the options are required and which are optional.
> Create our own s-ramp options renderer.
--
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, 6 months
[JBoss JIRA] (RTGOV-415) ElasticSearch Activity Store implementation
by ivan mckinley (JIRA)
[ https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin.... ]
ivan mckinley commented on RTGOV-415:
-------------------------------------
Hey, I've started work on this. I'll take this over if you haven't done anything on it already
> 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: ivan mckinley
> 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, 6 months
[JBoss JIRA] (RTGOV-415) ElasticSearch Activity Store implementation
by ivan mckinley (JIRA)
[ https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin.... ]
Work on RTGOV-415 started by 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: ivan mckinley
> 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, 6 months