Hi Nirmal,
On Wed, Jan 22, 2014 at 7:19 PM, Nirmal Fernando <[email protected]>wrote: > Hi All, > > While reading this again, following question popped out. If the proposed > IaaS is to easily test the basic flow of Stratos core components (IaaS > independent tasks) this would certainly worth to have, but if the intention > is to test IaaS specific stuff (eg: attaching volumes, handling multiple > networks) can we come to any conclusion after testing with this mock IaaS? > To test the flow without IaaS specific stuff, we should have a strong integration test suit as i mentioned earlier as well. IMO testing basic flow should be the intention of mock IaaS. Then a developer can run end to end flow in his/her machine itself when developing. This will help testing cartridge agent, puppet based stuff etc. Third level of testing is the real testing in a real IaaS. There we can test attaching volumes, long running tests, and load testing. Thanks. > > On Sun, Jan 12, 2014 at 4:13 PM, 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/ >> >> > > > -- > Best Regards, > Nirmal > > Nirmal Fernando. > PPMC Member & Committer of Apache Stratos, > Senior Software Engineer, WSO2 Inc. > > Blog: http://nirmalfdo.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
