I think cartridge re-usability has another aspect, an internal meaning. Suppose a tenant subscribe for a PHP cartridge and then a cartridge instance is spawned for him. I think it should be possible to pool this cartridge instance after a timeout threshold and re-used when another PHP cartridge instance requested, possibly by another tenant. I am not sure how this requirement would match with current Stratos architecture.
Implementation of such pools depend on underlying IaaS. For example in Openstack we need to use suspend/resume functionality(which is not possible with Docker or lxc currently, but possible with xen, qemu, kvm) Damitha On Sun, Apr 20, 2014 at 10:47 PM, chris snow <chsnow...@gmail.com> wrote: > Hi Udara, > > At the moment, everyone who wants to run stratos has to also create > cartridges that point to their specific puppet master instance. > > Wouldn't it be better if a cartridge could be created just once and > that cartridge image shared for other Stratos users? > > E.g. just like you can download a generic Ubuntu EC cloud image [1] > which is ready to use on OpenStack, it may be convenient for users if > cartridge images could too be shared? > > Many thanks, > > Chris > > --- > [1] > http://uec-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img > > On Sun, Apr 20, 2014 at 3:38 PM, Udara Liyanage <ud...@wso2.com> wrote: > > Hi Chris, > > > > If you can explain more about what you want to achieve it is better. As > > Lakmal mentioned we have a single cartridge which is is reused for every > > service type PHP, MySQL etc. Do you want to use the same cartridge for > > multiple Stratos environment? > > > > > > > > Touched, not typed. Erroneous words are a feature, not a typo. > > > > On Apr 20, 2014 7:58 PM, "Lakmal Warusawithana" <lak...@wso2.com> wrote: > >> > >> > >> On Sun, Apr 20, 2014 at 1:04 PM, chris snow <chsnow...@gmail.com> > wrote: > >>> > >>> When we create a cartridge, we provide it with the puppet master IP > >>> address. > >>> > >>> Does the cartridge periodically sync with the puppet master to > >>> retrieve updated definitions? Or, does it just sync up at cartidge > >>> creation time? > >> > >> > >> Currently we are use (generic case) puppet master at cartridge creation > >> time well as cartridge start time to retrieve updates. ( we can use > periodic > >> updates, but it depend on the use case) > >> > >>> > >>> > >>> After a cartridge has been created, is it possible to point the > >>> cartridge to a different puppet master? If not, cartridges are tied > >>> to the puppet master they were originally configured with and aren't > >>> reusable. > >>> > >> > >> I did not get what you mean by re-useable? And why we need to point any > >> other puppet master > >> > >>> > >>> Should we think about providing the puppet master hostname and ip (and > >>> maybe even the service type) as user data information, thus making our > >>> cartridges reusable? > >> > >> > >> Actually we are binding puppet master hostname with provided IP address > >> (adding host entry) to communicate with puppet master. > >> > >>> > >>> > >>> Many thanks, > >>> > >>> Chris > >> > >> > >> > >> > >> -- > >> Lakmal Warusawithana > >> Director - Cloud Architecture; WSO2 Inc. > >> Mobile : +94714289692 > >> Blog : http://lakmalsview.blogspot.com/ > >> > > > > > > -- > Check out my professional profile and connect with me on LinkedIn. > http://lnkd.in/cw5k69 > -- __________________________________________________________________ Damitha Kumarage http://people.apache.org/ __________________________________________________________________
