On Sun, May 6, 2012 at 6:28 AM, <[email protected]> wrote: > Hi, > > -original message- > Subject: Re: [Dev] Autoscaling with LXCs demo -2 > From: Sajith Kariyawasam <[email protected]> > Date: 06/05/2012 1:43 am > > Further, we will need to investigate as to why it takes more than expected > time for the LB to receive the 'Join' message when an app server is started > inside a container > > Ahhh.. yes! We need to test without using LXCs and see whether the issue > remains. > > Also, it was suggested that we should test this with multiple domains (not > only AS, but also ESB.. etc) > > For this we need to fix the issue i mentioned above regarding in-mediator. > And I see that Sanjeewa is in the process. > > Regarding the introductory presentation, I think its better to add Agent > registration part and some of the controller's functionalities > (persistence) so that the overall picture gets more clearer. > > Yes, it needs to cover whole picture, i'll try ma best to do it despite > i'm on a pilgrimage :) >
We can update and use attached architecture diagram developed by Damitha to see the whole picture in one. May be Sanjeewa can re-draw it with his attractive graphics :) > > On Fri, May 4, 2012 at 8:52 PM, Nirmal Fernando <[email protected]> wrote: > > > Hi All, > > > > Today we had another demo. > > > > Participants were: Azeez, Srinath, Dimuthu, Damitha, Sameera, Pradeep, > > Ranga, Lahiru, Sajith and myself. > > > > First we gave a brief overview of the autoscaling architecture. Then we > > started the demo. > > > > We were able to demo end-end (LB -> Controller --> Agent) scenario for > > spawning an instance (through LB sanity check) and termination of an > > instance (through scaling down call) within a LXC container. > > > > Few suggestions came up: > > > > 1. Create separate carbon instances (rather than using Appservers) for > > controller and agent. > > 2. Create a simple UI for controller to show instances spawned in each > > adapter, instances belong to a particular domain etc. > > 3. Fixing the domain related issue in AutoscaleInMediator (This arose > with > > the changes in loadbalancer.conf to reflect tenant aware load balancing). > > 4. Fixing the routing issue using Azeez's fix to Axis2. > > 5. Make scaling up demonstrable using a back-end service which has some > > processing (or having a Thread.sleep(..) call). > > > > Please add anything I've missed! > > > > PS: We'll repeat the demo next week (hopefully with some more > improvements > > next week, for Sanjiva, Paul and anyone interested). > > > > > > -- > > > > Thanks & regards, > > Nirmal > > > > Software Engineer- Platform Technologies Team, WSO2 Inc. > > Mobile: +94715779733 > > Blog: http://nirmalfdo.blogspot.com/ > > > > _______________________________________________ > > Dev mailing list > > [email protected] > > http://wso2.org/cgi-bin/mailman/listinfo/dev > > > > > > > -- > *Sajith Kariyawasam* > *Senior Software Engineer; WSO2, Inc.; http://wso2.com* > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- -- Lahiru Sandaruwan Software Engineer, Cloud Team, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: [email protected] 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
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
