Hi Gayan, Please see my comments inline:
On Sat, Oct 24, 2015 at 12:49 AM, Gayan Gunarathne <[email protected]> wrote: > > > If we use the Kubernetes service to identify the members of the cluster, > set of pods need to be created with label selector.So if we need to use > this we need to create each pods with the label selector. Isn't? > Yes that's the idea. I'm creating a set of K8S artifacts to deploy Carbon products on K8S. > >> Similar to the AWS and Private PaaS membership schemes, the new K8D >> membership scheme is being implemented to add all existing members of the >> cluster to Hazelcast network config before the Hazelcast instance is >> initialized. This would happen automatically whenever a carbon server is >> started. >> > > For the Private PaaS membership schema we have a Priavte PaaS messaging > model dependency.With this K8D membership scheme, it seems we may not > need such a dependency. > Correct, K8S membership scheme has no dependencies to Private PaaS components. > > Thanks -- *Imesh Gunaratne* Senior Technical Lead WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: http://imesh.gunaratne.org Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
