Hi Devs, I have now completed this modification and pushed to master branch. I verified this with single-cartridge and tomcat sample applications.
Now we only create Kubernetes Services and Pods. For each port mapping there will be a Kubernetes service created. For each member there will be a pod created. Thanks On Sun, Feb 22, 2015 at 10:39 AM, Imesh Gunaratne <im...@apache.org> wrote: > Thanks for the feedback Lakmal. I will make this change. > > Thanks > > On Sun, Feb 22, 2015 at 10:15 AM, Lakmal Warusawithana <lak...@wso2.com> > wrote: > >> Yes, I think we should create pods directly until we can have call back >> methods for get pod information from Kubernetes. >> >> On Sun, Feb 22, 2015 at 10:10 AM, Imesh Gunaratne <im...@apache.org> >> wrote: >> >>> Hi Devs, >>> >>> Currently we create a replication controller for each member in >>> Kubernetes. As a result if the pod stop responding the replication >>> controller will remove the existing pod and create a new one. Then the new >>> pod will get a new pod id. >>> >>> Once this happens Stratos will not be able to manage this pod because we >>> have no information about this process. Therefore I think we may need to do >>> $subject and directly create pods. >>> >>> Thanks >>> >>> >>> -- >>> Imesh Gunaratne >>> >>> Technical Lead, WSO2 >>> Committer & PMC Member, Apache Stratos >>> >> >> >> >> -- >> Lakmal Warusawithana >> Vice President, Apache Stratos >> Director - Cloud Architecture; WSO2 Inc. >> Mobile : +94714289692 >> Blog : http://lakmalsview.blogspot.com/ >> >> > > > -- > Imesh Gunaratne > > Technical Lead, WSO2 > Committer & PMC Member, Apache Stratos > -- Imesh Gunaratne Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
