Hi Isuru, I'm just wondering whether we could bypass the step of users having to create their own cartridges and instead allowing a market place where users can download a pre-made cartridge which the user would just need to configure to point to their own puppet master?
On Sun, Apr 20, 2014 at 6:30 PM, Isuru Haththotuwa <[email protected]> wrote: > Hi Chris, > > First of all, my apologies if this answer is not what you are looking for. > > You can provide the puppet master IP and hostname in the > repository/conf/cartridge-config.properties of Stratos distribution, using > the puppet.ip parameter. By doing this, different users can point to > different puppet master instances, while using the same cartridge image. > > > On Sun, Apr 20, 2014 at 10:47 PM, chris snow <[email protected]> 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 <[email protected]> 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" <[email protected]> wrote: >> >> >> >> >> >> On Sun, Apr 20, 2014 at 1:04 PM, chris snow <[email protected]> >> >> 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 > > > > > -- > Thanks and Regards, > > Isuru H. > +94 716 358 048 > > -- Check out my professional profile and connect with me on LinkedIn. http://lnkd.in/cw5k69
