[JBoss JIRA] (ISPN-6777) Improve Cache Stores configuration screen
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-6777?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-6777:
-------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/116
> Improve Cache Stores configuration screen
> -----------------------------------------
>
> Key: ISPN-6777
> URL: https://issues.jboss.org/browse/ISPN-6777
> Project: Infinispan
> Issue Type: Feature Request
> Components: Console
> Reporter: Pedro Zapata
> Assignee: Ryan Emerson
> Fix For: 9.0.0.Beta2
>
>
> Infinispan administrators should be able to select and configure any cache store easily, without having to enter class names and other free-form properties.
> Only one tab ‘Cache store’ will be displayed in the cache configuration options
> The user will have the option to select a type of store from the list (Single File, LevelDB, …) + the option ‘NONE’
> When the option is changed, all the generic + specific properties will be shown below.
> Properties should be presented as combos, if they are enumerable. For example, class (if there’s a way of filtering all implementing classes in classpath).
> Sensible defaults should be set.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ISPN-6673) Implement Rolling Upgrades with Kubernetes
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-6673?page=com.atlassian.jira.plugin.... ]
Work on ISPN-6673 started by Sebastian Łaskawiec.
-------------------------------------------------
> Implement Rolling Upgrades with Kubernetes
> ------------------------------------------
>
> Key: ISPN-6673
> URL: https://issues.jboss.org/browse/ISPN-6673
> Project: Infinispan
> Issue Type: Feature Request
> Components: Cloud Integrations
> Reporter: Sebastian Łaskawiec
> Assignee: Sebastian Łaskawiec
>
> There are 2 mechanisms which seems to do the same but are totally different:
> * [Kubernetes Rolling Update|http://kubernetes.io/docs/user-guide/rolling-updates/] - replaces Pods in controllable fashon
> * [Infinispan Rolling Updgrate|http://infinispan.org/docs/stable/user_guide/user_guide.html#_Ro...] - a procedure for upgrading Infinispan or changing the configuration
> Kubernetes Rolling Updates can be used very easily for changing the configuration however if changes are not runtime-compatible, one might loss data. Potential way to avoid this is to use a Cache Store. All other changes must be propagated using Infinispan Rolling Upgrade procedure.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months