[JBoss JIRA] (ISPN-11624) Server patching tool
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-11624?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-11624:
------------------------------------------
Fix Version/s: 11.0.0.Dev05
> Server patching tool
> --------------------
>
> Key: ISPN-11624
> URL: https://issues.redhat.com/browse/ISPN-11624
> Project: Infinispan
> Issue Type: Feature Request
> Components: CLI, Server
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Labels: supportability
> Fix For: 11.0.0.Dev05
>
>
> Add patching commands to the CLI:
> * *patch create* to create patch archives (zips)
> * *patch ls* to list the patches applied to a server
> * *patch describe* to describe the contents of a patch archive
> * *patch install* to install a patch on a server
> * *patch rollback* to roll back the server to the previous patch
> The patch zip should contain all the artifacts to upgrade from any number of source versions to a target version and a series of json patch descriptor with instructions (ADD, REMOVE, REPLACE, UPGRADE) on how to apply those artifacts
> The installation process will back up any artifacts that will be replaced/upgraded/removed so that they can be rolled back.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 12 months
[JBoss JIRA] (ISPN-11625) CLI commands to interact with Operator
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-11625?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-11625:
------------------------------------------
Fix Version/s: 12.0.0.Final
> CLI commands to interact with Operator
> --------------------------------------
>
> Key: ISPN-11625
> URL: https://issues.redhat.com/browse/ISPN-11625
> Project: Infinispan
> Issue Type: Feature Request
> Components: CLI, Operator
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> The Infinispan Server CLI should be extended so that it can be used to control/configure the operator and custom resource definitions.
> The CLI should act as a `kubectl` plugin, i.e. installed as `kubectl-infinispan` so that it can be invoked as `kubectl infinispan ...` or `oc infinispan ...`
> The CLI should be able to perform the following operations:
> * install the operator CRD
> * create CRs (cache service, caches, etc)
> * transparently connect to a running cluster to perform interactive operations
> Investigate the possibility of building/shipping a native binary.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 12 months
[JBoss JIRA] (ISPN-11646) Drop Elasticsearch support
by Gustavo Fernandes (Jira)
Gustavo Fernandes created ISPN-11646:
----------------------------------------
Summary: Drop Elasticsearch support
Key: ISPN-11646
URL: https://issues.redhat.com/browse/ISPN-11646
Project: Infinispan
Issue Type: Enhancement
Components: Embedded Querying, Remote Querying
Affects Versions: 11.0.0.Dev04
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
Fix For: 11.0.0.Final, 11.0.0.Dev05
This integration hasn't been maintained for a while and doesn't support all aspects of query/indexing
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 12 months
[JBoss JIRA] (ISPN-11642) Remote JCacheManager doesn't apply configuration from URI
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-11642?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-11642:
------------------------------------------
Fix Version/s: 10.1.7.Final
11.0.0.Dev05
> Remote JCacheManager doesn't apply configuration from URI
> ---------------------------------------------------------
>
> Key: ISPN-11642
> URL: https://issues.redhat.com/browse/ISPN-11642
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 10.1.6.Final
> Reporter: Nathan Mittlestat
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.1.7.Final, 11.0.0.Dev05
>
>
> Our project is using JCache API's backed by Infinspan. This is a client-server scenario where we are configuring the Hot Rod Java Client to connect to an Infinispan server.
> We are using _javax.cache.spi.CachingProvider.getCacheManager(URI, ClassLoader, Properties)_ to obtain a _CacheManager_. The URI passed points to an infinispan XML that specifies replicated-cache-configuration as part of the configuration. However the cache created from _CacheManager.createCache()_ ends up being a local cache. This proves to be a problem when connecting to a cluster of Infinispan servers, as when other connections attempt to utilize the cached data, they connect to a different Infinispn sever that doesn't have the cached data. We have verified the XML file pointed to by the URI is on the ClassLoader passed to the _CacheManager_, and still see the same results.
> When we attempt this same scenario using embedded mode instead of client server mode, the configuration in the URI is applied correctly. We have even been able to create a cluster of embedded Infinispan servers via JGroups and confirmed the caches are replicated and not local.
> We have also attempted this scenario using Infinispan's proprietary APIs:
> _RemoteCacheManager.administration().getOrCreateCache(String name, BasicConfiguration configuration)_
> The configuration object passed to _RemoteCacheManagerAdmin.getOrCreateCache()_ loads the same Infinispan XML configuration used in the failing remote JCache scenario (as a _XMlStringConfiguration_ object).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 12 months
[JBoss JIRA] (ISPN-11642) Remote JCacheManager doesn't apply configuration from URI
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-11642?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez reassigned ISPN-11642:
---------------------------------------------
Assignee: Tristan Tarrant (was: Dan Berindei)
> Remote JCacheManager doesn't apply configuration from URI
> ---------------------------------------------------------
>
> Key: ISPN-11642
> URL: https://issues.redhat.com/browse/ISPN-11642
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 10.1.6.Final
> Reporter: Nathan Mittlestat
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.1.7.Final, 11.0.0.Dev05
>
>
> Our project is using JCache API's backed by Infinspan. This is a client-server scenario where we are configuring the Hot Rod Java Client to connect to an Infinispan server.
> We are using _javax.cache.spi.CachingProvider.getCacheManager(URI, ClassLoader, Properties)_ to obtain a _CacheManager_. The URI passed points to an infinispan XML that specifies replicated-cache-configuration as part of the configuration. However the cache created from _CacheManager.createCache()_ ends up being a local cache. This proves to be a problem when connecting to a cluster of Infinispan servers, as when other connections attempt to utilize the cached data, they connect to a different Infinispn sever that doesn't have the cached data. We have verified the XML file pointed to by the URI is on the ClassLoader passed to the _CacheManager_, and still see the same results.
> When we attempt this same scenario using embedded mode instead of client server mode, the configuration in the URI is applied correctly. We have even been able to create a cluster of embedded Infinispan servers via JGroups and confirmed the caches are replicated and not local.
> We have also attempted this scenario using Infinispan's proprietary APIs:
> _RemoteCacheManager.administration().getOrCreateCache(String name, BasicConfiguration configuration)_
> The configuration object passed to _RemoteCacheManagerAdmin.getOrCreateCache()_ loads the same Infinispan XML configuration used in the failing remote JCache scenario (as a _XMlStringConfiguration_ object).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 12 months