January 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (HRJS-30) Move testsuite server orchestration to a domain

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-30?page=com.atlassian.jira.plugin.sy... ] Work on HRJS-30 started by Galder Zamarreño. -------------------------------------------- > Move testsuite server orchestration to a domain > ----------------------------------------------- > > Key: HRJS-30 > URL: https://issues.jboss.org/browse/HRJS-30 > Project: Infinispan Javascript client > Issue Type: Enhancement > Affects Versions: 0.3.0 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.4.0 > > > As more tests have been added to the Infinispan JS testsuite, the existing simple server orchestration script/environment are turning out to be a bit painful to deal with. > On one hand, Haskell's {{stack}} can be sometimes difficult to install in some envs, e.g. Ubuntu. I've also seen issues with Turtle library used in Haskell and copying contents inside symbolic links in Red Hat Linux. > On top of that, as security and cross-site tests were added, more configurations were added and more servers need to be added, making it track the configs a bit more confusing. > Finally, the methods used to start/stop servers in self-contained tests, e.g. xsite and cluster failover, a little bit clunky. > So, with this in mind, we thought of using more suitable orchestration techniques for Infinispan servers. We considered docker compose and kubernetes, but since the servers just simply need to run in a single machine and there's not a huge need to have clean environments, we decided to use a single Infinispan server domain to orchestrate all servers. > The advantages of domain is that is easy to start all servers with the right configuration very quickly, and start/stop servers from tests is very easy and quick compared with current approach. On top of that, having domain based orchestration will make it easy to port over the servers, their configs and script over to testsuites of other langs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HRJS-31) Old connections not disconnected when switching sites

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-31?page=com.atlassian.jira.plugin.sy... ] Work on HRJS-31 started by Galder Zamarreño. -------------------------------------------- > Old connections not disconnected when switching sites > ----------------------------------------------------- > > Key: HRJS-31 > URL: https://issues.jboss.org/browse/HRJS-31 > Project: Infinispan Javascript client > Issue Type: Bug > Affects Versions: 0.3.0 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.4.0 > > > When a site change happens in the client, old connections are left lingering and they're not disconnected. Before installing any new routers for any sites, irrespective of whether the switch was manual or a as a result of a failover, old connections need to be disconnected. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HRJS-30) Move testsuite server orchestration to a domain

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-30?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-30: --------------------------------- Status: Open (was: New) > Move testsuite server orchestration to a domain > ----------------------------------------------- > > Key: HRJS-30 > URL: https://issues.jboss.org/browse/HRJS-30 > Project: Infinispan Javascript client > Issue Type: Enhancement > Affects Versions: 0.3.0 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.4.0 > > > As more tests have been added to the Infinispan JS testsuite, the existing simple server orchestration script/environment are turning out to be a bit painful to deal with. > On one hand, Haskell's {{stack}} can be sometimes difficult to install in some envs, e.g. Ubuntu. I've also seen issues with Turtle library used in Haskell and copying contents inside symbolic links in Red Hat Linux. > On top of that, as security and cross-site tests were added, more configurations were added and more servers need to be added, making it track the configs a bit more confusing. > Finally, the methods used to start/stop servers in self-contained tests, e.g. xsite and cluster failover, a little bit clunky. > So, with this in mind, we thought of using more suitable orchestration techniques for Infinispan servers. We considered docker compose and kubernetes, but since the servers just simply need to run in a single machine and there's not a huge need to have clean environments, we decided to use a single Infinispan server domain to orchestrate all servers. > The advantages of domain is that is easy to start all servers with the right configuration very quickly, and start/stop servers from tests is very easy and quick compared with current approach. On top of that, having domain based orchestration will make it easy to port over the servers, their configs and script over to testsuites of other langs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HRJS-31) Old connections not disconnected when switching sites

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-31?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño reassigned HRJS-31: ------------------------------------ Assignee: Galder Zamarreño > Old connections not disconnected when switching sites > ----------------------------------------------------- > > Key: HRJS-31 > URL: https://issues.jboss.org/browse/HRJS-31 > Project: Infinispan Javascript client > Issue Type: Bug > Affects Versions: 0.3.0 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.4.0 > > > When a site change happens in the client, old connections are left lingering and they're not disconnected. Before installing any new routers for any sites, irrespective of whether the switch was manual or a as a result of a failover, old connections need to be disconnected. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HRJS-31) Old connections not disconnected when switching sites

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-31?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-31: --------------------------------- Fix Version/s: 0.4.0 > Old connections not disconnected when switching sites > ----------------------------------------------------- > > Key: HRJS-31 > URL: https://issues.jboss.org/browse/HRJS-31 > Project: Infinispan Javascript client > Issue Type: Bug > Affects Versions: 0.3.0 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.4.0 > > > When a site change happens in the client, old connections are left lingering and they're not disconnected. Before installing any new routers for any sites, irrespective of whether the switch was manual or a as a result of a failover, old connections need to be disconnected. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HRJS-31) Old connections not disconnected when switching sites

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-31?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño commented on HRJS-31: -------------------------------------- The issue was discovered while addressing HRJS-30 > Old connections not disconnected when switching sites > ----------------------------------------------------- > > Key: HRJS-31 > URL: https://issues.jboss.org/browse/HRJS-31 > Project: Infinispan Javascript client > Issue Type: Bug > Affects Versions: 0.3.0 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.4.0 > > > When a site change happens in the client, old connections are left lingering and they're not disconnected. Before installing any new routers for any sites, irrespective of whether the switch was manual or a as a result of a failover, old connections need to be disconnected. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HRJS-31) Old connections not disconnected when switching sites

by Galder Zamarreño (JIRA)

Galder Zamarreño created HRJS-31: ------------------------------------ Summary: Old connections not disconnected when switching sites Key: HRJS-31 URL: https://issues.jboss.org/browse/HRJS-31 Project: Infinispan Javascript client Issue Type: Bug Affects Versions: 0.3.0 Reporter: Galder Zamarreño When a site change happens in the client, old connections are left lingering and they're not disconnected. Before installing any new routers for any sites, irrespective of whether the switch was manual or a as a result of a failover, old connections need to be disconnected. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HRJS-30) Move testsuite server orchestration to a domain

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-30?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño reassigned HRJS-30: ------------------------------------ Assignee: Galder Zamarreño > Move testsuite server orchestration to a domain > ----------------------------------------------- > > Key: HRJS-30 > URL: https://issues.jboss.org/browse/HRJS-30 > Project: Infinispan Javascript client > Issue Type: Enhancement > Affects Versions: 0.3.0 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.4.0 > > > As more tests have been added to the Infinispan JS testsuite, the existing simple server orchestration script/environment are turning out to be a bit painful to deal with. > On one hand, Haskell's {{stack}} can be sometimes difficult to install in some envs, e.g. Ubuntu. I've also seen issues with Turtle library used in Haskell and copying contents inside symbolic links in Red Hat Linux. > On top of that, as security and cross-site tests were added, more configurations were added and more servers need to be added, making it track the configs a bit more confusing. > Finally, the methods used to start/stop servers in self-contained tests, e.g. xsite and cluster failover, a little bit clunky. > So, with this in mind, we thought of using more suitable orchestration techniques for Infinispan servers. We considered docker compose and kubernetes, but since the servers just simply need to run in a single machine and there's not a huge need to have clean environments, we decided to use a single Infinispan server domain to orchestrate all servers. > The advantages of domain is that is easy to start all servers with the right configuration very quickly, and start/stop servers from tests is very easy and quick compared with current approach. On top of that, having domain based orchestration will make it easy to port over the servers, their configs and script over to testsuites of other langs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[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 reassigned ISPN-7326: -------------------------------------- Assignee: 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)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7326) Enable domain sites to be created from a single profile

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-7326: -------------------------------------- Summary: 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 Reporter: 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)

9 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2017