You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Sajith Kariyawasam <sa...@wso2.com> on 2013/11/28 22:11:21 UTC
Using Puppet for Cartridge configuration
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 <%2B94772269575>*
Re: Using Puppet for Cartridge configuration
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
Hi
+1. This will be best approach for minimizing the stuffs that we pushed
inside cartridge. If we could make a generic cartridge and if we could pass
the relevant parameters to make it as a specific cartridge through
user-data, then for all the cartridges, we can use the same image. This is
just a thought on minimizing the work that we have to do when customizing
the cartridge.
Thanks,
Reka
On Fri, Nov 29, 2013 at 4:31 AM, Jason Daly <ja...@systembind.com>wrote:
> 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 DalyVP, Product Development*
> *SystemBind Consulting & IT Services Inc.*
>
>
>
>
> *5115 Maingate Drive, Unit #1 | Mississauga | OntarioTel: 416.848.0980 x
> 850 <416.848.0980;850> Mobile: 416.388.4070 <416.388.4070>Toll:
> 1.877.SYS.BINDwww.systembind.com <http://www.systembind.com/>*
>
> On Nov 28, 2013, at 4:11 PM, "Sajith Kariyawasam" <sa...@wso2.com> 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 <%2B94772269575>*
>
>
--
Reka Thirunavukkarasu
Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
Re: Using Puppet for Cartridge configuration
Posted by Jason Daly <ja...@systembind.com>.
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" <sajith@wso2.com <ma...@wso2.com> > 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
Re: Using Puppet for Cartridge configuration
Posted by Sajith Kariyawasam <sa...@wso2.com>.
Hi Alejandro,
Thanks for the feedback. I'm familiar with Puppet only, if you can help
with CFengine related stuff and contribute, you are welcome to do so..!
Thanks
Sajith
On Sun, Dec 1, 2013 at 9:54 AM, Alejandro Bonilla <
abonilla@linuxwireless.org> wrote:
> Have you considered CFengine instead of Puppet? This due to the
> dependencies, footprint and resources that puppet requires...
>
>
> On Thu, Nov 28, 2013 at 4:11 PM, Sajith Kariyawasam <sa...@wso2.com>
> 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/
> > Mobile: +94772269575
>
--
*Sajith Kariyawasam*
*Senior Software Engineer; WSO2, Inc.*
*AMIE (SL)*
*Blog: http://sajithblogs.blogspot.com/ <http://sajithblogs.blogspot.com/>*
*Mobile: +94772269575*
Re: Using Puppet for Cartridge configuration
Posted by Alejandro Bonilla <ab...@linuxwireless.org>.
Have you considered CFengine instead of Puppet? This due to the
dependencies, footprint and resources that puppet requires...
On Thu, Nov 28, 2013 at 4:11 PM, Sajith Kariyawasam <sa...@wso2.com> 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/
> Mobile: +94772269575