May 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-421) S-ramp shell UploadArtifactCommand Add name and description

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-421?page=com.atlassian.jira.plugin.... ] David virgil naranjo commented on SRAMP-421: -------------------------------------------- The description is not possible to be set, because there is another optional arg, the artifact type. > S-ramp shell UploadArtifactCommand Add name and description > ----------------------------------------------------------- > > Key: SRAMP-421 > URL: https://issues.jboss.org/browse/SRAMP-421 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > S-ramp shell UploadArtifactCommand Add name and description as optional parameters. It should work like the createArtifactCommand. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-447) Change SituationStore EPN node to use SituationStore API

by Gary Brown (JIRA)

Gary Brown created RTGOV-447: -------------------------------- Summary: Change SituationStore EPN node to use SituationStore API Key: RTGOV-447 URL: https://issues.jboss.org/browse/RTGOV-447 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final Currently situations are persisted from the Event Processor Network node 'SituationStore' using the JPAEventProcessor. This implies the store will be a relational db, making it more difficult to change to an alternative implementation (e.g. ElasticSearch). Change this node to use Java code that will persist the Situation using the SituationStore API. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-419) UI Feature: Export/Download ontology

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-419?page=com.atlassian.jira.plugin.... ] Work on SRAMP-419 started by David virgil naranjo. > UI Feature: Export/Download ontology > ------------------------------------ > > Key: SRAMP-419 > URL: https://issues.jboss.org/browse/SRAMP-419 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: UI > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: 0.5.0 - API Management > > > The new Onotology Management UI should have the ability to download/export an ontology to disk. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[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: ------------------------------------- If (3) is possible - then the ESActivityStore could have a mapping file for index rtgov and type activity. The datastore EPN could then have then mapping file for index rtgov and types 'responsetime' and 'situation'. > it does this already. for instance. If i define a store with index= rtgov , type = actvity and there a multiple type mappings in the rtgov-mapping.json file. it will only initialize the mapping for activity. this functionality is available in the current src. Note: I'm re-evaluting and testing another approach. for instance, what happens when your activity is derived of more complex mappings, like children etc. needs to be able to initializes the child mappings. > 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 was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[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: ------------------------------------- 2) Some central location for all rtgov related mappings, and then act store and our EPNs just rely on it already being initialised. Then the local EPN mapping file mechanism would just be used by users who want to store their own info. > this is how i imagined it. The ootb epn for activities, situations and responses would be initialize the core rtgov index. the EPNs and ACT store reference these indexes. it does not make sense to have a separate index for the act store and the activity epn. this would be duplication of data.(your 1st point) The current central location is the EPN at the moment, so it would be initialized the first time the epn is activated. or should the act store be referenced first the actstore would then initialize it. (first come first serve). Currently it doesn't matter when it gets initialized but it would be clean if we had a central location for this. Local epn mappings would then define their own mapping files(rtgov-mapping, <myindex>-mapping.json). the mapping file can either define own index or append the rtgov index (this is how it works at the moment). I seriously need to document this stuff soon :) > 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 was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 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: ---------------------------------- 3) Make the 'prepareIndex' method check for both index and type? That way, different deployment units could use the same index but define the mapping for just the type they deal with. If (3) is possible - then the ESActivityStore could have a mapping file for index rtgov and type activity. The datastore EPN could then have then mapping file for index rtgov and types 'responsetime' and 'situation'. > 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 was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 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: ---------------------------------- [~imckinle] Was wondering how you planned to handle the ES mapping for activities, when the activity store is used? Will we just ship a preconfigured mapping file in the ESActivityStore jar? If so, then the problem will be using the same index for activities and other things (e.g. response time, situations) - as from the code it looks like the index can only be initialised once. Solutions I can see: 1) Use separate indexes for each deployable unit - i.e. the activity store, and any EPNs have their own index - so index per EPN, so one mapping file per EPN? 2) Some central location for all rtgov related mappings, and then act store and our EPNs just rely on it already being initialised. Then the local EPN mapping file mechanism would just be used by users who want to store their own info. > 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 was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-442) Upgrade to Picketlink 2.5.3.SP1

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-442?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-442. ------------------------------ Fix Version/s: 2.0.0.Final Resolution: Done > Upgrade to Picketlink 2.5.3.SP1 > ------------------------------- > > Key: RTGOV-442 > URL: https://issues.jboss.org/browse/RTGOV-442 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Brett Meyer > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > EAP 6.3 upgraded to Picketlink 2.5.3.SP1. First runs on EAP 6.3 showing breaking package changes. Ex: > java.lang.ClassNotFoundException:org.picketlink.identity.federation.core.exceptions.ConfigurationException -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-442) Upgrade to Picketlink 2.5.3.SP1

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/RTGOV-442?page=com.atlassian.jira.plugin.... ] Brett Meyer updated RTGOV-442: ------------------------------ Git Pull Request: https://github.com/Governance/rtgov/pull/80 Done -- take a look? > Upgrade to Picketlink 2.5.3.SP1 > ------------------------------- > > Key: RTGOV-442 > URL: https://issues.jboss.org/browse/RTGOV-442 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Brett Meyer > Assignee: Gary Brown > > EAP 6.3 upgraded to Picketlink 2.5.3.SP1. First runs on EAP 6.3 showing breaking package changes. Ex: > java.lang.ClassNotFoundException:org.picketlink.identity.federation.core.exceptions.ConfigurationException -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

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

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-382?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-382: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/399, https://github.com/Governance/overlord-commons/pull/58, https://github.com/Governance/apiman/pull/5, https://github.com/Governance/overlord/pull/7, https://github.com/Governance/s-ramp/pull/410 (was: https://github.com/Governance/s-ramp/pull/399, https://github.com/Governance/overlord-commons/pull/58, https://github.com/Governance/apiman/pull/5, https://github.com/Governance/overlord/pull/7) > 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: Brett Meyer > Fix For: 0.5.0 - API Management > > > Add support for EAP 6.3. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues May 2014