On Tue, Sep 16, 2014 at 2:58 PM, Lahiru Sandaruwan <lahi...@wso2.com> wrote:
> > > On Tue, Sep 16, 2014 at 2:54 PM, Lakmal Warusawithana <lak...@wso2.com> > wrote: > >> >> >> On Tue, Sep 16, 2014 at 12:49 PM, Akila Ravihansa Perera < >> raviha...@wso2.com> wrote: >> >>> Hi Raj, >>> >>> We can use the same CEP stream to publish cartridge agent health stats. >>> We can identify the instance type (container or VM type) by retrieving >>> member properties from the topology. But I don't think we should be doing >>> that. >>> >>> IMO, we should not publish cartridge agent health stats from each and >>> every container. It's better if we can have a global agent per Kubernetes >>> host instance to monitor the health of every container and also in host >>> instance itself. We can use a container monitoring agent like cAdvisor to >>> collect container health stats. >>> >> >> For all time we may not get health stats from host level. Sometime we may >> need to have owned logic to get application heath, which is needed by >> extending cartridge agent. IMO, we can't fully get rid of publishing heath >> status from the agent. >> >> > > hmm.. If we do not get rid of agent of container, better to have the stats > from that agent. It would be simple. > Yes, we need to have agent inside container. If docker running inside a VM, anyway we need to monitor heath of that, for VM level monitoring. > >>> +1 for having a separate CEP execution plan for handling Docker >>> containers scenario. >>> >>> As for the ContainerClusterMonitor, we should clearly outline the >>> responsibilities of container monitor and VM monitor. Because since we are >>> using Kubernetes for managing the life-cycle of containers, most of the >>> tasks are already taken care of. For eg - we don't need to start a new >>> container if an existing containers fails since Kubernetes will handle that >>> failure. >>> >>> WDYT? >>> >> >> >> >> -- >> Lakmal Warusawithana >> Vice President, Apache Stratos >> Director - Cloud Architecture; WSO2 Inc. >> Mobile : +94714289692 >> Blog : http://lakmalsview.blogspot.com/ >> >> > > > -- > -- > Lahiru Sandaruwan > Committer and PMC member, Apache Stratos, > Senior Software Engineer, > WSO2 Inc., http://wso2.com > lean.enterprise.middleware > > email: lahi...@wso2.com cell: (+94) 773 325 954 > blog: http://lahiruwrites.blogspot.com/ > twitter: http://twitter.com/lahirus > linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 > > -- Lakmal Warusawithana Vice President, Apache Stratos Director - Cloud Architecture; WSO2 Inc. Mobile : +94714289692 Blog : http://lakmalsview.blogspot.com/
