[
https://issues.jboss.org/browse/ISPN-6489?page=com.atlassian.jira.plugin....
]
Sebastian Łaskawiec commented on ISPN-6489:
-------------------------------------------
[Kubernetes 1.2 adds alpha support for custom
metrics|http://kubernetes.io/docs/user-guide/horizontal-pod-autoscaling]. An Autoscaler
component can scale out/in based on exposed metrics.
Things to do in order to support this:
- Expose
[
cAdvisor|https://github.com/google/cadvisor/blob/master/docs/application_...]
configuration. There are at least two options here - colocate them in the same Docker
image (a simple Docker Label might be used: {{LABEL
io.cadvisor.metric.redis="/var/cadvisor/redis_config.json"}}) or create another
container only for exposing the configuration.
- Expose metrics. Even though cAdvisor has been written to be metric format agnostic, it
prefers Prometheus metrics. We could use [JMX/Prometheus
bridge|https://github.com/prometheus/jmx_exporter].
- [Optional] Add JMX/Prometheus bridge to the library mode.
- Create an autoscaler template and instruction for the users.
Create (or adjust) autoscaling policies in Openshift
----------------------------------------------------
Key: ISPN-6489
URL:
https://issues.jboss.org/browse/ISPN-6489
Project: Infinispan
Issue Type: Feature Request
Components: Cloud Integrations
Reporter: Sebastian Łaskawiec
Assignee: Sebastian Łaskawiec
During the conference [
Ray|https://twitter.com/saturnism] mentioned that it would be
really nice to have Openshift autoscaling policies for Infinispan based on:
* number of entries (and/or)
* memory usage
Some examples might be found in his repos
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)