Hi Azeez, Thanks for bringing this up. According to my understanding there were no HA features planned up to the last milestone for any of the components.
May be we could discuss the features in different components that may need attention when clustering: 1. Message Broker - Here the requirement is to have a AMQP based message broker. Therefore it might not depend on Stratos. 2. Stratos Manager - Stratos manager would be the central point of access to Stratos environment. - Stratos web client, CLI or any other client would connect to Stratos Manager via the REST API. - Communicates with cartridge instances for Artifact Distribution. - I could not think of any specific features that may get affected by clustering in Stratos Manager. - However we might need to verify any in memory contexts that may require distribution. 3. Cloud Controller - Cloud controller would be the interface to the IaaS layer. - Autoscaler communicates to Cloud Controller for managing the cartridge instances. - I could not think of any specific features that may get affected by clustering in Cloud Controller. - However we might need to verify any in memory contexts that may require distribution. 4. Autoscaler - This might be the most critical component when it comes to clustering. - It has a set of in memory contexts that require distribution when implementing a cluster. - More importantly the auto-scaling decision making process might need to be synchronized. 5. Complex Event Processor - Complex event processor is also a separate product. - Should be able to cluster without a problem. 6. Load Balancer - Load balancer is now deployed as a cartridge. - The load balancing algorithm contexts and session information require distribution when implementing a cluster. - There was a separate discussion regarding this requirement. Thanks Imesh On Mon, Jan 27, 2014 at 12:18 PM, Afkham Azeez <[email protected]> wrote: > Folks, > Have we looked into making Stratos components (CC, SC, MB etc.) highly > available? If so, can you point me to any mail archives? > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com, > *Member; Apache Software Foundation; > **http://www.apache.org/*<http://www.apache.org/> > > *email: **[email protected]* <[email protected]> > * cell: +94 77 3320919 <%2B94%2077%203320919> blog: * > *http://blog.afkham.org* <http://blog.afkham.org> > * twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * linked-in: **http://lk.linkedin.com/in/afkhamazeez > <http://lk.linkedin.com/in/afkhamazeez>* > > *Lean . Enterprise . Middleware* > >
