[
https://issues.apache.org/jira/browse/STRATOS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1012:
-------------------------------------
Affects Version/s: (was: 4.1.0 RC1)
4.1.0 Alpha
> Clustering support for Cloud Controller
> ---------------------------------------
>
> Key: STRATOS-1012
> URL: https://issues.apache.org/jira/browse/STRATOS-1012
> Project: Stratos
> Issue Type: Improvement
> Components: Cloud Controller
> Affects Versions: 4.1.0 Alpha
> Reporter: Imesh Gunaratne
> Assignee: Imesh Gunaratne
> Fix For: 4.1.0 Alpha
>
> Attachments: Cloud Controller - Clustering Model.png
>
>
> Currently cloud controller does not support clustering for providing high
> availability. At present it has two in memory data structures which manages
> its state; Data Holder, Topology.
> The idea is to have a coordinator node to handle data persistence logic and
> message publishing (topology, instance status, etc). The coordinator will be
> selected randomly and at a given time there will be only one coordinator. If
> the existing coordinator node goes down, another member will become the
> coordinator automatically (similar to carbon clustering agent).
> According to this design Autoscaler (AS)/Stratos Manager (SM) will talk to
> Cloud Controller (CC) via the Cloud Controller Service endpoint exposed via
> the load balancer.
> Data Replication
> When a request comes into one of the CC instances it will execute the
> necessary actions and update the data holder and/or topology which is in
> memory. At this point the data holder and topology changes will be replicated
> to other instances using a distributed map. Once the coordinator receives the
> above updates it will persist the changes to the registry database.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
