Indeed, this is an awesome thought! +1 I think we should be able to write the LXC wrapper using the compute API [1]. I will also look into this and add more details.
[1] http://jclouds.apache.org/documentation/userguide/compute/ Thanks On Sun, Jan 12, 2014 at 11:33 PM, Lahiru Sandaruwan <[email protected]>wrote: > Hi all, > > I see two important aspects in this thread. > > 1. Light weight development environment with light weight IaaS > 2. Complete integration test with mocked external services(This does not > require an IaaS) > > +1 for a LXC based environment for #1. > > We have already started #2 for Autoscaler, may be we can extended it to > other products as well. > > Thanks. > > > On Mon, Jan 13, 2014 at 9:53 AM, Pradeep Fernando <[email protected]>wrote: > >> >> Hi, >> >> On Mon, Jan 13, 2014 at 4:55 AM, Sanjiva Weerawarana <[email protected]>wrote: >> >>> Pradeep lets chat a bit .. >>> >> >> Sure.. >> >> >>> yes we should implement a jClouds wrapper for sure. The runtime bits are >>> quite straightforward IMO .. we use different ports and bring up LXCs and >>> have them communicate to the LB. Basically we're doing the work that the >>> LXC agent does in a machine underneath OpenStack right now. >>> >> To be honest i didnt think with LXC stuff in mind. I was thinking >> mocking the environment with pure java based mechanisms. (service >> calls/java reflection/etc). - my comfort zone i guess. So looks good and >> seems to be an interesting task. Will collaborate with Lakmal on this. >> >> --Pradeep >> >> >>> If you have time to start on this that'll be great - shouldn't take too >>> long to get to 80% aka working state! >>> >>> Sanjiva. >>> >>> >>> On Mon, Jan 13, 2014 at 12:43 AM, Pradeep Fernando >>> <[email protected]>wrote: >>> >>>> Hi, >>>> >>>> I was discussing this with the team on friday and was going to send a >>>> mail. Never knew you had this in your mind. :) >>>> >>>> Since our IAAS abstraction is Jclouds, we should consider the >>>> possibitily of implementing the mock IAAS on top jclouds. >>>> >>>> Right now we test autoscaling and other fundamental stuff using EC2. It >>>> is quite painful and waste of money. I couldnt figure out how to mockup the >>>> runtime bits, like cartridge serving a request, but we can figure out those >>>> bits.. >>>> >>>> --Pradeep >>>> >>>> >>>> >>>> >>>> On Sun, Jan 12, 2014 at 5:04 PM, Lakmal Warusawithana >>>> <[email protected]>wrote: >>>> >>>>> Thanks Chris, will see how we can use jclouds mocks into this. >>>>> >>>>> >>>>> On Sun, Jan 12, 2014 at 4:29 PM, chris snow <[email protected]>wrote: >>>>> >>>>>> This would be awesome. >>>>>> >>>>>> If I remember correctly, jclouds has some mocks already - I had a >>>>>> brief look into this before, but haven't had time to thoroughly >>>>>> investigate. >>>>>> On 12 Jan 2014 10:43, "Lakmal Warusawithana" <[email protected]> wrote: >>>>>> >>>>>>> Hi devs, >>>>>>> >>>>>>> Initially this idea is came from Sanjiva, to minimize the barriers >>>>>>> to contribution to Stratos. After chat I had with Sanjiva, I have >>>>>>> thought >>>>>>> about what scenarios do we need to cover from this. Here is some points >>>>>>> I >>>>>>> like to discuss. For a time being will call it "Stratos Dev IaaS" :) >>>>>>> >>>>>>> - get rid of complexity of the current IaaS setup which required >>>>>>> in Stratos. for a example even setting up OpenStack in single node, >>>>>>> required lot of resources, well as some deeper networking knowledge. >>>>>>> - this should easy to setup. >>>>>>> - should run with low resource. For achieve this, I am thinking >>>>>>> of directly create LXC as Cartridges. >>>>>>> - when developer need to do testing on some smart deployments >>>>>>> policies, it required, multi regions, zones ..etc IaaS environments >>>>>>> which >>>>>>> is very hard to set it up or its very costly. So with this, we should >>>>>>> create mockups regions, zones ..etc. >>>>>>> - support mockup private IP and public IP >>>>>>> - support mockup multi network interfaces >>>>>>> - support mockup persistence volume for instances >>>>>>> - support API, which can call from jclouds >>>>>>> >>>>>>> >>>>>>> We can complete above features one by one but we should have proper >>>>>>> design to start up. I can take the ownership of developing this, since I >>>>>>> have done similar kind of IaaS in some times back [1]. But until mid >>>>>>> feb I >>>>>>> have full my calendar with multiple engagement, but will try to kickoff >>>>>>> this. Thoughts , help appreciate on this. >>>>>>> >>>>>>> [1]http://wso2.com/projects/ozone/ >>>>>>> >>>>>>> >>>>>>> thanks >>>>>>> -- >>>>>>> Lakmal Warusawithana >>>>>>> Software Architect; WSO2 Inc. >>>>>>> Mobile : +94714289692 >>>>>>> Blog : http://lakmalsview.blogspot.com/ >>>>>>> >>>>>>> >>>>> >>>>> >>>>> -- >>>>> Lakmal Warusawithana >>>>> Software Architect; WSO2 Inc. >>>>> Mobile : +94714289692 >>>>> Blog : http://lakmalsview.blogspot.com/ >>>>> >>>>> >>>> >>>> >>>> -- >>>> Pradeep Fernando. >>>> http://pradeepfernando.blogspot.com/ >>>> >>> >>> >>> >>> -- >>> Sanjiva Weerawarana, Ph.D. >>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ >>> email: [email protected]; office: +1 650 745 4499 x5700; cell: +94 77 >>> 787 6880 | +1 650 265 8311 >>> blog: http://sanjiva.weerawarana.org/ >>> Lean . Enterprise . Middleware >>> >> >> >> >> -- >> Pradeep Fernando. >> http://pradeepfernando.blogspot.com/ >> > > > > -- > -- > Lahiru Sandaruwan > Software Engineer, > Platform Technologies, > 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 > >
