Hi Damitha, This is still on my list. I will probably focus on this after completing the first version of a scripted vagrant cloudstack + stratos environment. The first version of the environment will probably require a lot of memory (approx 10+ gb for the vagrant guest) which will make it inaccessible for a lot of people, so I expect the next focus will be to optimise that environment.
As for timescales, that's a tough one to answer as I'm working on it in my free time :) What is the reason for your question? Are you finding the whole setup too heavyweight at the moment? Cheers, Chris On Wed, Mar 12, 2014 at 1:30 PM, damitha kumarage <damith...@gmail.com> wrote: > Are there any plans on getting this done soon? > > Damitha > > > On Sun, Jan 5, 2014 at 9:14 AM, Lakmal Warusawithana <lak...@wso2.com> > wrote: >> >> IMO, we should optimize Stratos products to consume low memory footprint. >> Now we are using vanilla carbon kernel and bundle features. We (in WSO2) did >> this to some extend in past, run stratos2 in raspberry pi cluster. >> [1][2][3]. We can do the same to Stratos 4.0 since Stratos committer/ppmc >> already has couple of geeks involved to that project. :). Chris you lead >> this, if you have some time :) >> >> [1]http://blog.afkham.org/2013/01/raspberry-pi-control-center.html >> >> [2]http://blog.afkham.org/2013/02/building-raspberry-pi-cluster-part-2.html >> [3]http://blog.afkham.org/2013/01/why-we-built-raspberry-pi-cluster.html >> >> >> >> On Sun, Jan 5, 2014 at 8:05 AM, Lahiru Sandaruwan <lahi...@wso2.com> >> wrote: >>> >>> Hi Chris, >>> >>> Sorry for the late replies. >>> >>> Yes, the recommendation was due to number of JVMs. It is recommended to >>> have 2 gb per carbon server, but it can be less if the load is less. >>> You might get a small idea on standard recommendations if you want >>> further information from my answer to [1]. >>> >>> If you need to try out the products in single jvm, I'd recommend to >>> assemble following 3 Stratos servers first and see. >>> >>> Stratos Manager(Stratos Controller) >>> Cloud Controller >>> Autoscaler >>> >>> Because above 3 are based on same carbon Kernal always, but WSO2 >>> servers(MB and CEP) cannot be guaranteed to be based on same Kernal version. >>> >>> We run load balancers as cartridges at the latest milestones. So you do >>> not need to worry about installing them in the system. >>> >>> [1] >>> http://stackoverflow.com/questions/18746437/wso2-api-manager-requirements >>> >>> Thanks. >>> >>> >>> >>> On Sun, Jan 5, 2014 at 1:05 AM, Udara Liyanage <ud...@wso2.com> wrote: >>>> >>>> Hi, >>>> >>>> Carbon servers min/max memory consumption can be configured using the >>>> jvm parameters in stratos.sh file. Could you have a look. >>>> >>>> Touched, not typed. Erroneous words are a feature, not a typo. >>> >>> >>> >>> >>> -- >>> -- >>> Lahiru Sandaruwan >>> Software Engineer, >>> Platform Technologies, >>> 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 >> Software Architect; WSO2 Inc. >> Mobile : +94714289692 >> Blog : http://lakmalsview.blogspot.com/ >> > > > > -- > __________________________________________________________________ > Damitha Kumarage > http://people.apache.org/ > __________________________________________________________________ -- Check out my professional profile and connect with me on LinkedIn. http://lnkd.in/cw5k69
