Hi Dinesh, Yes, understood, after cartridge initialization happened through puppet master, puppet master related(and some other) information are erased and a re-usable image is created. Then cartridges created through this image in another environment(with new puppet master), get puppet master information from payload and can get updates and patches through this new puppet master.
Thanks, Damitha On Wed, Apr 23, 2014 at 4:23 PM, Dinesh Bandara <dine...@wso2.com> wrote: > Hi Damitha, > > On Wed, Apr 23, 2014 at 3:45 PM, damitha kumarage <damith...@gmail.com>wrote: > >> Hi Dinesh, >> >> Please see my inline comment. >> On Mon, Apr 21, 2014 at 8:36 AM, Dinesh Bandara <dine...@wso2.com> wrote: >> >>> Hi Chris, >>> >>> >>> 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? >>>> >>> >>> Yes. you can share the cartridge image for other stratos user. Let me >>> explain this in detail. >>> when creating cartridge by running config script, simply you have to >>> provide puppetmaster ip, hostname and service type. Those data are used >>> only for cartridge configuration (initialization) and those data are erased >>> once configuration process completed. Then you can create a image form that >>> configured instance and it is just like a generic cloud image[1] with >>> specific service type (Genaric, PHP, MySQL, etc). It is not bound to any >>> puppet master. This image can be shared among other stratos users. >>> >> >> I am not sure if my understanding is correct, but cartridges depend on >> the puppet master on updates, patches etc. To complete the Ubuntu analogy, >> Ubuntu cloud images can update from apt repositories, likewise the >> cartridges should be able to update from some public puppet master. >> > > Once cartridge deployed in startos environment it will bind to puppet > master in that environment. As an example mb ip and port are specific to > that environment and then relevant data will be updated through puppet > master. > >> >>> >>>> 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 >>>> >>> >>> >>> >>> -- >>> *Dinesh Bandara* >>> Software Engineer >>> WSO2 Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> >> >> >> -- >> __________________________________________________________________ >> Damitha Kumarage >> http://people.apache.org/ >> __________________________________________________________________ >> > > > > -- > *Dinesh Bandara* > Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > -- __________________________________________________________________ Damitha Kumarage http://people.apache.org/ __________________________________________________________________
