You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by chris snow <ch...@gmail.com> on 2014/04/20 09:34:37 UTC
cartridge reusability
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?
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.
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?
Many thanks,
Chris
Re: cartridge reusability
Posted by damitha kumarage <da...@gmail.com>.
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 <di...@wso2.com> wrote:
> Hi Damitha,
>
> On Wed, Apr 23, 2014 at 3:45 PM, damitha kumarage <da...@gmail.com>wrote:
>
>> Hi Dinesh,
>>
>> Please see my inline comment.
>> On Mon, Apr 21, 2014 at 8:36 AM, Dinesh Bandara <di...@wso2.com> wrote:
>>
>>> Hi Chris,
>>>
>>>
>>> On Sun, Apr 20, 2014 at 10:47 PM, chris snow <ch...@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" <la...@wso2.com>
>>>> wrote:
>>>> >>
>>>> >>
>>>> >> On Sun, Apr 20, 2014 at 1:04 PM, chris snow <ch...@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/
__________________________________________________________________
Re: cartridge reusability
Posted by Dinesh Bandara <di...@wso2.com>.
Hi Damitha,
On Wed, Apr 23, 2014 at 3:45 PM, damitha kumarage <da...@gmail.com>wrote:
> Hi Dinesh,
>
> Please see my inline comment.
> On Mon, Apr 21, 2014 at 8:36 AM, Dinesh Bandara <di...@wso2.com> wrote:
>
>> Hi Chris,
>>
>>
>> On Sun, Apr 20, 2014 at 10:47 PM, chris snow <ch...@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" <la...@wso2.com>
>>> wrote:
>>> >>
>>> >>
>>> >> On Sun, Apr 20, 2014 at 1:04 PM, chris snow <ch...@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
Re: cartridge reusability
Posted by damitha kumarage <da...@gmail.com>.
Hi Dinesh,
Please see my inline comment.
On Mon, Apr 21, 2014 at 8:36 AM, Dinesh Bandara <di...@wso2.com> wrote:
> Hi Chris,
>
>
> On Sun, Apr 20, 2014 at 10:47 PM, chris snow <ch...@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.
>
>
>> 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" <la...@wso2.com>
>> wrote:
>> >>
>> >>
>> >> On Sun, Apr 20, 2014 at 1:04 PM, chris snow <ch...@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/
__________________________________________________________________
Re: cartridge reusability
Posted by chris snow <ch...@gmail.com>.
Perfect. Thanks Dinesh!
On Mon, Apr 21, 2014 at 4:06 AM, Dinesh Bandara <di...@wso2.com> wrote:
> Hi Chris,
>
>
> On Sun, Apr 20, 2014 at 10:47 PM, chris snow <ch...@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.
>
>>
>> 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" <la...@wso2.com> wrote:
>> >>
>> >>
>> >> On Sun, Apr 20, 2014 at 1:04 PM, chris snow <ch...@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
>
--
Check out my professional profile and connect with me on LinkedIn.
http://lnkd.in/cw5k69
Re: cartridge reusability
Posted by Akila Ravihansa Perera <ra...@wso2.com>.
Hi all,
Correct me if I'm wrong, isn't Stratos sending the Puppet master IP in the
payload to the spawned instance?
As I understood, spawned instance when executing init.sh script (at boot
time) use this Puppet master IP in the payload to initialize the cartridge.
In effect, if we change this Puppet master IP in cloud controller
configuration , we are changing the Puppet master for the spawned
insurance.
Thanks.
On 21 Apr 2014 08:37, "Dinesh Bandara" <di...@wso2.com> wrote:
> Hi Chris,
>
>
> On Sun, Apr 20, 2014 at 10:47 PM, chris snow <ch...@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.
>
>
>> 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" <la...@wso2.com>
>> wrote:
>> >>
>> >>
>> >> On Sun, Apr 20, 2014 at 1:04 PM, chris snow <ch...@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
>
>
Re: cartridge reusability
Posted by Dinesh Bandara <di...@wso2.com>.
Hi Chris,
On Sun, Apr 20, 2014 at 10:47 PM, chris snow <ch...@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.
> 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" <la...@wso2.com> wrote:
> >>
> >>
> >> On Sun, Apr 20, 2014 at 1:04 PM, chris snow <ch...@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
Re: cartridge reusability
Posted by Lakmal Warusawithana <la...@wso2.com>.
On Sun, Apr 20, 2014 at 11:50 PM, chris snow <ch...@gmail.com> wrote:
> 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?
>
>
+1, yes we should build cartridge store. will target this with next release.
>
>
> On Sun, Apr 20, 2014 at 6:30 PM, Isuru Haththotuwa <is...@wso2.com>
> 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 <ch...@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" <la...@wso2.com>
> wrote:
> >> >>
> >> >>
> >> >> On Sun, Apr 20, 2014 at 1:04 PM, chris snow <ch...@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
> >
> >
> >
> >
> > --
> > Thanks and Regards,
> >
> > Isuru H.
> > +94 716 358 048
> >
> >
>
>
>
> --
> Check out my professional profile and connect with me on LinkedIn.
> http://lnkd.in/cw5k69
>
--
Lakmal Warusawithana
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
Re: cartridge reusability
Posted by Nirmal Fernando <ni...@gmail.com>.
Hi Chris,
I think we're not bound to the puppet master hostname/IP which got created
at the time of initialization. see
https://github.com/apache/incubator-stratos/blob/master/tools/puppet3-agent/init.shwe're
taking them from the payload.
On Sun, Apr 20, 2014 at 11:50 PM, chris snow <ch...@gmail.com> wrote:
> 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 <is...@wso2.com>
> 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 <ch...@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" <la...@wso2.com>
> wrote:
> >> >>
> >> >>
> >> >> On Sun, Apr 20, 2014 at 1:04 PM, chris snow <ch...@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
> >
> >
> >
> >
> > --
> > Thanks and Regards,
> >
> > Isuru H.
> > +94 716 358 048
> >
> >
>
>
>
> --
> Check out my professional profile and connect with me on LinkedIn.
> http://lnkd.in/cw5k69
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: cartridge reusability
Posted by chris snow <ch...@gmail.com>.
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 <is...@wso2.com> 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 <ch...@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" <la...@wso2.com> wrote:
>> >>
>> >>
>> >> On Sun, Apr 20, 2014 at 1:04 PM, chris snow <ch...@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
>
>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048
>
>
--
Check out my professional profile and connect with me on LinkedIn.
http://lnkd.in/cw5k69
Re: cartridge reusability
Posted by Isuru Haththotuwa <is...@wso2.com>.
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 <ch...@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" <la...@wso2.com> wrote:
> >>
> >>
> >> On Sun, Apr 20, 2014 at 1:04 PM, chris snow <ch...@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
>
--
Thanks and Regards,
Isuru H.
+94 716 358 048* <http://wso2.com/>*
Re: cartridge reusability
Posted by damitha kumarage <da...@gmail.com>.
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 <ch...@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" <la...@wso2.com> wrote:
> >>
> >>
> >> On Sun, Apr 20, 2014 at 1:04 PM, chris snow <ch...@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/
__________________________________________________________________
Re: cartridge reusability
Posted by chris snow <ch...@gmail.com>.
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" <la...@wso2.com> wrote:
>>
>>
>> On Sun, Apr 20, 2014 at 1:04 PM, chris snow <ch...@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
Re: cartridge reusability
Posted by Udara Liyanage <ud...@wso2.com>.
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" <la...@wso2.com> wrote:
>
> On Sun, Apr 20, 2014 at 1:04 PM, chris snow <ch...@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/
>
>
Re: cartridge reusability
Posted by Lakmal Warusawithana <la...@wso2.com>.
On Sun, Apr 20, 2014 at 1:04 PM, chris snow <ch...@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/