Thanks Lakmal for the clarification. Sorry, I was not up-to-date. Thanks.
On Tue, Jan 6, 2015 at 1:28 PM, Lakmal Warusawithana <lak...@wso2.com> wrote: > > > On Tue, Jan 6, 2015 at 1:17 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > >> Hi, >> >> Seems replication controller id is same as member id. >> >> core@master ~ $ kubecfg list replicationControllers >> Name >> Image(s) >> Selector >> Replicas >> ---------- >> >> ---------- >> ---------- >> ---------- >> php-php-domain7dd60909-45a3-425f-820e-9703237e6d90 >> stratos/php:4.1.0-alpha >> name=php-php-domain7dd60909-45a3-425f-820e-9703237e6d90 1 >> php-php-domain6d05ba1b-f67c-4d06-987e-dfdc3b62ec55 >> stratos/php:4.1.0-alpha >> name=php-php-domain6d05ba1b-f67c-4d06-987e-dfdc3b62ec55 1 >> php-php-domainab81daa2-5bec-42e1-88b7-6cdc1f78d90a >> stratos/php:4.1.0-alpha >> name=php-php-domainab81daa2-5bec-42e1-88b7-6cdc1f78d90a 1 >> php-php-domain493060b3-85bb-4cb9-ae46-b25555d5f262 >> stratos/php:4.1.0-alpha >> name=php-php-domain493060b3-85bb-4cb9-ae46-b25555d5f262 1 >> >> There is only one cluster. But there are four replication controllers, >> each with one replicas. >> >> So are we creating a new replication controller for each member of the >> cluster, rather than updating existing replication controller of the >> cluster? >> >> > Yes, we are creating replication controllers per member to get more > controllability until we can get some APIs from kubernetes to get more > controllability for members. > > > >> Thanks. >> >> -- >> Rajkumar Rajaratnam >> Committer & PMC Member, Apache Stratos >> Software Engineer, WSO2 >> >> Mobile : +94777568639 >> Blog : rajkumarr.com >> > > > > -- > Lakmal Warusawithana > Vice President, Apache Stratos > Director - Cloud Architecture; WSO2 Inc. > Mobile : +94714289692 > Blog : http://lakmalsview.blogspot.com/ > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com
