[JBoss JIRA] (ISPN-7326) Enable domain sites to be created from a single profile
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7326?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño edited comment on ISPN-7326 at 1/9/17 8:18 AM:
----------------------------------------------------------------
After careful investigation, it turns out that {{remote-site}}'s name is resolve correctly thanks to the fact that the name is only resolved when the node is started up, e.g. from StackAddHandler.java
{code}
String siteName = RelayResourceDefinition.SITE.resolveModelAttribute(context, relay).asString();
RelayConfigurationBuilder relayBuilder = builder.setRelay(siteName);
{code}
On the other hand, {{backup}}'s site attribute and {{remote-site}}'s name attributes are not resolved.
So, similar pattern should be applied here.
However, a problem present for {{backup}}'s site and {{remote-site}}'s name attributes is that their names seem to form part of addresses, so there's no attributes for them per-se and since they are part of addresses, the resolution might need to happen when XML is read but that would not work since it's the host controller that does that?
was (Author: galder.zamarreno):
After careful investigation, it turns out that {{remote-site}}'s name is resolve correctly thanks to the fact that the name is only resolved when the node is started up, e.g. from StackAddHandler.java
{code}
String siteName = RelayResourceDefinition.SITE.resolveModelAttribute(context, relay).asString();
RelayConfigurationBuilder relayBuilder = builder.setRelay(siteName);
{code}
On the other hand, {{backup}}'s site attribute and {{remote-site}}'s name attributes are not resolved.
So, similar pattern should be applied here.
However, a problem present for {{backup}}'s site and {{remote-site}}'s name attributes is that their names seem to form part of addresses, so there's no attributes for them per-se and since they are part of addresses, the resolution might need to happen when XML is read but that would not work since it's the host controller that does that?
> Enable domain sites to be created from a single profile
> -------------------------------------------------------
>
> Key: ISPN-7326
> URL: https://issues.jboss.org/browse/ISPN-7326
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
>
> In domain mode, it should be possible to start two nodes, each belonging to a different site and get them to join the inter-site cluster providing a single profile.
> To be able to do that, the following needs to happen:
> * A cache's backup site name needs to be able to be defined via a system property, e.g.
> {code}
> <backups>
> <backup site="${test.site.local.name:NA}" strategy="SYNC"/>
> </backups>
> {code}
> * A jgroup stack's relay remote site name needs to be able to be defined via a system property, e.g.
> {code}
> <relay site="${test.site.local.name:NA}">
> <remote-site name="${test.site.remote.name:NA}" channel="xsite"/>
> </relay>
> {code}
> With these changes, it should be possible to define a single profile, and then override site local and remote names via system properties, e.g.
> {code}
> <server-group name="site-earth" profile="clustered">
> <jvm name="default">
> <heap size="64m" max-size="512m"/>
> <jvm-options>
> <option value="-Djgroups.join_timeout=1000"/>
> <option value="-Djboss.default.multicast.address=234.99.74.14"/>
> <option value="-Dtest.site.local.name=EARTH"/>
> <option value="-Dtest.site.remote.name=MOON"/>
> </jvm-options>
> </jvm>
> <socket-binding-group ref="xsite-sockets"/>
> </server-group>
> <server-group name="site-moon" profile="clustered">
> <jvm name="default">
> <heap size="64m" max-size="512m"/>
> <jvm-options>
> <option value="-Djgroups.join_timeout=1000"/>
> <option value="-Djboss.default.multicast.address=234.99.74.24"/>
> <option value="-Dtest.site.local.name=MOON"/>
> <option value="-Dtest.site.remote.name=EARTH"/>
> </jvm-options>
> </jvm>
> <socket-binding-group ref="xsite-sockets"/>
> </server-group>
> {code}
> Right now no system property substitution happens for the elements above and hence it's not possible to achieve this with a single profile. Instead, profiles need to be duplicated making it hard to maintain.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7326) Enable domain sites to be created from a single profile
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7326?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño commented on ISPN-7326:
----------------------------------------
After careful investigation, it turns out that {{remote-site}}'s name is resolve correctly thanks to the fact that the name is only resolved when the node is started up, e.g. from StackAddHandler.java
{code}
String siteName = RelayResourceDefinition.SITE.resolveModelAttribute(context, relay).asString();
RelayConfigurationBuilder relayBuilder = builder.setRelay(siteName);
{code}
On the other hand, {{backup}}'s site attribute and {{remote-site}}'s name attributes are not resolved.
So, similar pattern should be applied here.
However, a problem present for {{backup}}'s site and {{remote-site}}'s name attributes is that their names seem to form part of addresses, so there's no attributes for them per-se and since they are part of addresses, the resolution might need to happen when XML is read but that would not work since it's the host controller that does that?
> Enable domain sites to be created from a single profile
> -------------------------------------------------------
>
> Key: ISPN-7326
> URL: https://issues.jboss.org/browse/ISPN-7326
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
>
> In domain mode, it should be possible to start two nodes, each belonging to a different site and get them to join the inter-site cluster providing a single profile.
> To be able to do that, the following needs to happen:
> * A cache's backup site name needs to be able to be defined via a system property, e.g.
> {code}
> <backups>
> <backup site="${test.site.local.name:NA}" strategy="SYNC"/>
> </backups>
> {code}
> * A jgroup stack's relay remote site name needs to be able to be defined via a system property, e.g.
> {code}
> <relay site="${test.site.local.name:NA}">
> <remote-site name="${test.site.remote.name:NA}" channel="xsite"/>
> </relay>
> {code}
> With these changes, it should be possible to define a single profile, and then override site local and remote names via system properties, e.g.
> {code}
> <server-group name="site-earth" profile="clustered">
> <jvm name="default">
> <heap size="64m" max-size="512m"/>
> <jvm-options>
> <option value="-Djgroups.join_timeout=1000"/>
> <option value="-Djboss.default.multicast.address=234.99.74.14"/>
> <option value="-Dtest.site.local.name=EARTH"/>
> <option value="-Dtest.site.remote.name=MOON"/>
> </jvm-options>
> </jvm>
> <socket-binding-group ref="xsite-sockets"/>
> </server-group>
> <server-group name="site-moon" profile="clustered">
> <jvm name="default">
> <heap size="64m" max-size="512m"/>
> <jvm-options>
> <option value="-Djgroups.join_timeout=1000"/>
> <option value="-Djboss.default.multicast.address=234.99.74.24"/>
> <option value="-Dtest.site.local.name=MOON"/>
> <option value="-Dtest.site.remote.name=EARTH"/>
> </jvm-options>
> </jvm>
> <socket-binding-group ref="xsite-sockets"/>
> </server-group>
> {code}
> Right now no system property substitution happens for the elements above and hence it's not possible to achieve this with a single profile. Instead, profiles need to be duplicated making it hard to maintain.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7326) Enable domain sites to be created from a single profile
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7326?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-7326:
-----------------------------------
Status: Open (was: New)
> Enable domain sites to be created from a single profile
> -------------------------------------------------------
>
> Key: ISPN-7326
> URL: https://issues.jboss.org/browse/ISPN-7326
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
>
> In domain mode, it should be possible to start two nodes, each belonging to a different site and get them to join the inter-site cluster providing a single profile.
> To be able to do that, the following needs to happen:
> * A cache's backup site name needs to be able to be defined via a system property, e.g.
> {code}
> <backups>
> <backup site="${test.site.local.name:NA}" strategy="SYNC"/>
> </backups>
> {code}
> * A jgroup stack's relay remote site name needs to be able to be defined via a system property, e.g.
> {code}
> <relay site="${test.site.local.name:NA}">
> <remote-site name="${test.site.remote.name:NA}" channel="xsite"/>
> </relay>
> {code}
> With these changes, it should be possible to define a single profile, and then override site local and remote names via system properties, e.g.
> {code}
> <server-group name="site-earth" profile="clustered">
> <jvm name="default">
> <heap size="64m" max-size="512m"/>
> <jvm-options>
> <option value="-Djgroups.join_timeout=1000"/>
> <option value="-Djboss.default.multicast.address=234.99.74.14"/>
> <option value="-Dtest.site.local.name=EARTH"/>
> <option value="-Dtest.site.remote.name=MOON"/>
> </jvm-options>
> </jvm>
> <socket-binding-group ref="xsite-sockets"/>
> </server-group>
> <server-group name="site-moon" profile="clustered">
> <jvm name="default">
> <heap size="64m" max-size="512m"/>
> <jvm-options>
> <option value="-Djgroups.join_timeout=1000"/>
> <option value="-Djboss.default.multicast.address=234.99.74.24"/>
> <option value="-Dtest.site.local.name=MOON"/>
> <option value="-Dtest.site.remote.name=EARTH"/>
> </jvm-options>
> </jvm>
> <socket-binding-group ref="xsite-sockets"/>
> </server-group>
> {code}
> Right now no system property substitution happens for the elements above and hence it's not possible to achieve this with a single profile. Instead, profiles need to be duplicated making it hard to maintain.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7326) Enable domain sites to be created from a single profile
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7326?page=com.atlassian.jira.plugin.... ]
Work on ISPN-7326 started by Galder Zamarreño.
----------------------------------------------
> Enable domain sites to be created from a single profile
> -------------------------------------------------------
>
> Key: ISPN-7326
> URL: https://issues.jboss.org/browse/ISPN-7326
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
>
> In domain mode, it should be possible to start two nodes, each belonging to a different site and get them to join the inter-site cluster providing a single profile.
> To be able to do that, the following needs to happen:
> * A cache's backup site name needs to be able to be defined via a system property, e.g.
> {code}
> <backups>
> <backup site="${test.site.local.name:NA}" strategy="SYNC"/>
> </backups>
> {code}
> * A jgroup stack's relay remote site name needs to be able to be defined via a system property, e.g.
> {code}
> <relay site="${test.site.local.name:NA}">
> <remote-site name="${test.site.remote.name:NA}" channel="xsite"/>
> </relay>
> {code}
> With these changes, it should be possible to define a single profile, and then override site local and remote names via system properties, e.g.
> {code}
> <server-group name="site-earth" profile="clustered">
> <jvm name="default">
> <heap size="64m" max-size="512m"/>
> <jvm-options>
> <option value="-Djgroups.join_timeout=1000"/>
> <option value="-Djboss.default.multicast.address=234.99.74.14"/>
> <option value="-Dtest.site.local.name=EARTH"/>
> <option value="-Dtest.site.remote.name=MOON"/>
> </jvm-options>
> </jvm>
> <socket-binding-group ref="xsite-sockets"/>
> </server-group>
> <server-group name="site-moon" profile="clustered">
> <jvm name="default">
> <heap size="64m" max-size="512m"/>
> <jvm-options>
> <option value="-Djgroups.join_timeout=1000"/>
> <option value="-Djboss.default.multicast.address=234.99.74.24"/>
> <option value="-Dtest.site.local.name=MOON"/>
> <option value="-Dtest.site.remote.name=EARTH"/>
> </jvm-options>
> </jvm>
> <socket-binding-group ref="xsite-sockets"/>
> </server-group>
> {code}
> Right now no system property substitution happens for the elements above and hence it's not possible to achieve this with a single profile. Instead, profiles need to be duplicated making it hard to maintain.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7345) Administration console - missing name of cluster in stop/start confirmation dialog
by Roman Macor (JIRA)
Roman Macor created ISPN-7345:
---------------------------------
Summary: Administration console - missing name of cluster in stop/start confirmation dialog
Key: ISPN-7345
URL: https://issues.jboss.org/browse/ISPN-7345
Project: Infinispan
Issue Type: Bug
Components: JMX, reporting and management
Affects Versions: 9.0.0.Beta1
Reporter: Roman Macor
Click on clusters tab, click on cluster, actions -> start/stop
Confirmation pop up says:
Starting will start all previously running servers in this cluster. Start ?
It should say (it used to say):
Starting cluster_name will start all previously running servers in this cluster. Start cluster_name?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7343) Allow using Hibernate Search, Hibernate ORM, Hibernate OGM and Infinispan + Infinispan Query in the same app in Wildfly
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/ISPN-7343?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero updated ISPN-7343:
----------------------------------
Reporter: Sanne Grinovero (was: Sebastian Łaskawiec)
> Allow using Hibernate Search, Hibernate ORM, Hibernate OGM and Infinispan + Infinispan Query in the same app in Wildfly
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-7343
> URL: https://issues.jboss.org/browse/ISPN-7343
> Project: Infinispan
> Issue Type: Feature Request
> Components: Embedded Querying, WildFly modules
> Reporter: Sanne Grinovero
> Priority: Minor
>
> We should make it easier to use all those libraries in a single app on WildFly.
> This is a tricky request, as Infinispan Query exposes its own version of Hibernate Search as public API: people need to use it directly to use embedded query.
> Not least it requires exposing:
> * index mapping annotations from Hibernate Search
> * Usage of the Hibernate Search querybuilder helpers (optional)
> * Direct usage of the Apache Lucene classes, in turn exposed as well as public API by Hibernate Search
> When wanting to use Hibernate Search directly as well (with Hibernate ORM), one needs not only to choose a version which is compatible with both, but one also needs to make sure that the WildFly modules are all using the same module id; the problem being one should not use multiple copies of the module, as the Infinispan project re-distributes its own copy of such modules.
> Picking a compatible version is limiting but not hard; editing all module XML definitions is not very nice though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7343) Allow using Hibernate Search, Hibernate ORM, Hibernate OGM and Infinispan + Infinispan Query in the same app in Wildfly
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/ISPN-7343?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero reassigned ISPN-7343:
-------------------------------------
Issue Type: Feature Request (was: Bug)
Component/s: Embedded Querying
WildFly modules
Description:
We should make it easier to use all those libraries in a single app on WildFly.
This is a tricky request, as Infinispan Query exposes its own version of Hibernate Search as public API: people need to use it directly to use embedded query.
Not least it requires exposing:
* index mapping annotations from Hibernate Search
* Usage of the Hibernate Search querybuilder helpers (optional)
* Direct usage of the Apache Lucene classes, in turn exposed as well as public API by Hibernate Search
When wanting to use Hibernate Search directly as well (with Hibernate ORM), one needs not only to choose a version which is compatible with both, but one also needs to make sure that the WildFly modules are all using the same module id; the problem being one should not use multiple copies of the module, as the Infinispan project re-distributes its own copy of such modules.
Picking a compatible version is limiting but not hard; editing all module XML definitions is not very nice though.
was:We should allow to use all those libraries in a single app on WildFly.
Affects Version/s: (was: 8.2.5.Final)
Assignee: (was: Sanne Grinovero)
> Allow using Hibernate Search, Hibernate ORM, Hibernate OGM and Infinispan + Infinispan Query in the same app in Wildfly
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-7343
> URL: https://issues.jboss.org/browse/ISPN-7343
> Project: Infinispan
> Issue Type: Feature Request
> Components: Embedded Querying, WildFly modules
> Reporter: Sebastian Łaskawiec
> Priority: Minor
>
> We should make it easier to use all those libraries in a single app on WildFly.
> This is a tricky request, as Infinispan Query exposes its own version of Hibernate Search as public API: people need to use it directly to use embedded query.
> Not least it requires exposing:
> * index mapping annotations from Hibernate Search
> * Usage of the Hibernate Search querybuilder helpers (optional)
> * Direct usage of the Apache Lucene classes, in turn exposed as well as public API by Hibernate Search
> When wanting to use Hibernate Search directly as well (with Hibernate ORM), one needs not only to choose a version which is compatible with both, but one also needs to make sure that the WildFly modules are all using the same module id; the problem being one should not use multiple copies of the module, as the Infinispan project re-distributes its own copy of such modules.
> Picking a compatible version is limiting but not hard; editing all module XML definitions is not very nice though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months