I think that this is a great approach: this allows for management of cartridges to be more dynamic and opens up the possibility of integrating a Puppet management API (such as the Foreman for example).
Jason Daly VP, Product Development SystemBind Consulting & IT Services Inc. 5115 Maingate Drive, Unit #1 | Mississauga | Ontario Tel: 416.848.0980 x 850 Mobile: 416.388.4070 Toll: 1.877.SYS.BIND www.systembind.com <http://www.systembind.com/> On Nov 28, 2013, at 4:11 PM, "Sajith Kariyawasam" <[email protected] <mailto:[email protected]> > wrote: Hi all, In current Stratos architecture, configurations of a cartridge instance are kept inside the cartridge image (AMI), and if configuration needs to modify later, AMI need to be recreated with the new configs. I think using a Puppet based model, this can be optimized. Configuration can be kept in a puppet master node, and puppet agent need to be installed in the cartridge so that it retrieves the relevant configuration from puppet master at the instance bootup. Also, it eases the patching process and easy to ship AMIs ( Need to install puppet related packages only) Further a puppet based model can be used for cartridge creation as well. Appreciate your thoughts on this. Thanks Sajith -- Sajith Kariyawasam Senior Software Engineer; WSO2, Inc. AMIE (SL) Blog: http://sajithblogs.blogspot.com/ <http://sajithblogs.blogspot.com/> Mobile: +94772269575
