June 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-462) Explore whether ElasticSearch server can be embedded into container (EAP)

by ivan mckinley (JIRA)

[ https://issues.jboss.org/browse/RTGOV-462?page=com.atlassian.jira.plugin.... ] ivan mckinley commented on RTGOV-462: ------------------------------------- 1) If we are starting a full server for production use, this would also require the full stack, wouldn't it? So this would be the same for both production and test/integration requirements? - correct. but perhaps in remote client mode there will be no need to pull in the full stack 2) Singleton - yes, although the ElasticsearchClient is not a singleton, it could manage a 'singleton' for the embedded server, in cases where the specific ElasticsearchClient instance has referenced it (or possibly where the host is unspecified). If the embedded node's config is obtained from the overlord-rtgov.properties, this should enable clustering to be supported/updated as appropriate, without impacting the individual components using ES. Unique config per instance - this could be more complex. It may be possible via the overlord-rtgov.properties when running in standalone mode, but (as I understand it) when we use domain mode, this info will be obtained from the xml - which will be common across a cluster of servers (I assume). So we may need the embedded nodes (in this scenario) to use a common general config, and potentially the more specific config is applied to ES nodes outside of EAP? > Perhaps the best approach in the this case would be. - Domain mode. All ES nodes form a cluster based on config in xml(assumption). ES Configuration by default. Perhaps taking config from EAP clustering(if clustering in use). if another ES cluster or shard is required then a separate domain could be defined. what do you think? - Standalone. Flexible configuration using RTGov.properties. This is straight forward. > Explore whether ElasticSearch server can be embedded into container (EAP) > ------------------------------------------------------------------------- > > Key: RTGOV-462 > URL: https://issues.jboss.org/browse/RTGOV-462 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: ivan mckinley > Fix For: 2.0.0.Final > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Determine whether ElasticSearch could be embedded within EAP/Karaf. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-462) Explore whether ElasticSearch server can be embedded into container (EAP)

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-462?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-462: ---------------------------------- 1) If we are starting a full server for production use, this would also require the full stack, wouldn't it? So this would be the same for both production and test/integration requirements? 2) Singleton - yes, although the ElasticsearchClient is not a singleton, it could manage a 'singleton' for the embedded server, in cases where the specific ElasticsearchClient instance has referenced it (or possibly where the host is unspecified). If the embedded node's config is obtained from the overlord-rtgov.properties, this should enable clustering to be supported/updated as appropriate, without impacting the individual components using ES. Unique config per instance - this could be more complex. It may be possible via the overlord-rtgov.properties when running in standalone mode, but (as I understand it) when we use domain mode, this info will be obtained from the xml - which will be common across a cluster of servers (I assume). So we may need the embedded nodes (in this scenario) to use a common general config, and potentially the more specific config is applied to ES nodes outside of EAP? > Explore whether ElasticSearch server can be embedded into container (EAP) > ------------------------------------------------------------------------- > > Key: RTGOV-462 > URL: https://issues.jboss.org/browse/RTGOV-462 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: ivan mckinley > Fix For: 2.0.0.Final > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Determine whether ElasticSearch could be embedded within EAP/Karaf. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-462) Explore whether ElasticSearch server can be embedded into container (EAP)

by ivan mckinley (JIRA)

[ https://issues.jboss.org/browse/RTGOV-462?page=com.atlassian.jira.plugin.... ] ivan mckinley commented on RTGOV-462: ------------------------------------- I see cases that have to be addressed. Its a trickier topic than simply starting a ES node First the easy one. 1) Test and Integration : A lightweight local jvm ES is started using the local node feature from the ES java api. This would require the entire ES dependency stack for our module. As opposed to currently where we only have the client api 2) Embedded out of the box. - Should start a single ES node - Should be singleton in the JVM. I have not reviewed the ElasticsearchClient but we need to ensure that only one ES instance is started per vm. Is ElasticsearchClient "singleton" or is it shared amongst Keyvalue stores. Starting additional embedded nodes in 1 jvm should not be allowed (hence singleton or static as you mentioned ) - Should be capable of joining a ES cluster(or any). This would allow us to scale horizontally by adding additional FSW or ES nodes as data/load grows. - Allow unique configuration per instance. Once again would support scalability as perhaps certain jboss nodes with embedded ES would be designated as been responsible for a particular model. for example in multiple node we store all situations objects on dedicated nodes(sharding etc). > Explore whether ElasticSearch server can be embedded into container (EAP) > ------------------------------------------------------------------------- > > Key: RTGOV-462 > URL: https://issues.jboss.org/browse/RTGOV-462 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: ivan mckinley > Fix For: 2.0.0.Final > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Determine whether ElasticSearch could be embedded within EAP/Karaf. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-346) Explore whether ElasticSearch server can be embedded into container (Karaf)

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-346?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-346: ---------------------------------- The comment above is more relevant for the EAP embedded server, which is now in RTGOV-462. The profile could be bundled with a property file containing the config details for the server. Alternatively it may be best to initially reuse the same 'embedded' ES server properties used in RTGOV-462, and just include starting the server as part of the rtgov-all profile. Issues: if multiple rtgov-all profiles are started on the same machine, then the ports will conflict. Only solution to this would be to use dynamic ports somehow, which also means the other properties referencing ES would need to be dynamic. > Explore whether ElasticSearch server can be embedded into container (Karaf) > --------------------------------------------------------------------------- > > Key: RTGOV-346 > URL: https://issues.jboss.org/browse/RTGOV-346 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: ivan mckinley > Fix For: 2.0.0.Final > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Determine whether ElasticSearch could be embedded within EAP/Karaf. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-462) Explore whether ElasticSearch server can be embedded into container (EAP)

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-462?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-462: ---------------------------------- Previously discussed options for creating the server - possibly triggered by an EJB to leverage its lifecycle. However any Elasticsearch client will be dependent upon this being started. Wondering whether it is better to simplify this for now - for example in the ElasticsearchClient (https://github.com/Governance/rtgov/blob/master/modules/common/rtgov-elas...) the 'embedded' host value is creating an instance for use in testing - but can this be enhanced to start a properly configured (and potentially clustered) local node? Statically stored in this ElasticsearchClient to avoid multiple embedded servers being started up? Issues would be, where it obtains the configuration from - probably best in overlord-rtgov.properties - so that the individual components using Elasticsearch don't need to provide this config details, which may end up varying across components - so they just provide host name "embedded" and the common details are obtained from the properties file. Could change the current 'embedded' entry to 'test' - if a lightweight server is required for test purposes? > Explore whether ElasticSearch server can be embedded into container (EAP) > ------------------------------------------------------------------------- > > Key: RTGOV-462 > URL: https://issues.jboss.org/browse/RTGOV-462 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: ivan mckinley > Fix For: 2.0.0.Final > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Determine whether ElasticSearch could be embedded within EAP/Karaf. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-451) S-ramp maven facade for fuse fabric

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/SRAMP-451?page=com.atlassian.jira.plugin.... ] Gary Brown updated SRAMP-451: ----------------------------- Original Estimate: 1 week Remaining Estimate: 1 week > S-ramp maven facade for fuse fabric > ----------------------------------- > > Key: SRAMP-451 > URL: https://issues.jboss.org/browse/SRAMP-451 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Original Estimate: 1 week > Remaining Estimate: 1 week > > Create a mvn-http facade component that will act as a intermediate between fuse fabric and s-ramp.. It should be just a servlet that dissects the inbound request's path to extract the GAV information. Then does a s-ramp repository query to find the appropriate artifact > The GET side of that is very easy (pulling artifacts *from* s-ramp) > The servlet would have to take a URL path like this: org/overlord/sramp/s-ramp-api/0.4.0.Final/s-ramp-api-0.4.0.Final.jar and parse that to get the GAV info of: org.overlord.sramp:s-ramp-api:0.4.0.Final:jar -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-346) Explore whether ElasticSearch server can be embedded into container (Karaf)

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-346?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-346: ----------------------------- Parent: (was: RTGOV-419) Issue Type: Feature Request (was: Sub-task) > Explore whether ElasticSearch server can be embedded into container (Karaf) > --------------------------------------------------------------------------- > > Key: RTGOV-346 > URL: https://issues.jboss.org/browse/RTGOV-346 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: ivan mckinley > Fix For: 2.0.0.Final > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Determine whether ElasticSearch could be embedded within EAP/Karaf. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-419) ElasticSearch support

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-419?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-419. ------------------------------ Resolution: Done > ElasticSearch support > --------------------- > > Key: RTGOV-419 > URL: https://issues.jboss.org/browse/RTGOV-419 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-454) Unify ElasticSearch sever configuration across proxy REST service and keyvalue store

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-454?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-454: ----------------------------- Parent: (was: RTGOV-419) Issue Type: Task (was: Sub-task) > Unify ElasticSearch sever configuration across proxy REST service and keyvalue store > ------------------------------------------------------------------------------------ > > Key: RTGOV-454 > URL: https://issues.jboss.org/browse/RTGOV-454 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Currently the Elasticsearch.hosts property is a list of <host>:<port> values, while the REST service uses a single URL property. > See if ES client can take a URL rather than just host:port - and if so, have a single property that takes a list of URLs. > If possible, then need to see if REST service can use a list of URLs (failover). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-488) Revert to drools 6.0.1

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-488?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-488: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/109 > Revert to drools 6.0.1 > ---------------------- > > Key: RTGOV-488 > URL: https://issues.jboss.org/browse/RTGOV-488 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues June 2014