You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Lakmal Warusawithana <la...@wso2.com> on 2014/05/29 12:46:03 UTC
Cartridge Store for Apache Straos
Hi,
As I mention in [1] mail thread, we need to create and host $subject.
WSO2 has some internal employee training program and I have proposed a
group project for create cartridge store and connect it from the Stratos
Manager. And there are 3 volunteers accept this project. I have encouraged
them to start their project proposal in dev list.
Brief description of the project:
Need to have Public Cartridge Store. (we have to host it). For this store
any contributors can submit their cartridges. There should be some test and
approved process. PMC can do the approval. Stratos Manager interface should
extent to connect to this store and get latest community created
cartridges. As the first step, these cartridges can be puppet models. Later
we can extent it to docker, cheft, ami etc. Manager automatically deploy
this into puppet master and also deploy as cartridges.
Please share your thoughts, what else we need to consider on this. And we
can take this as first step, but we may need to continue develop this.
[1][DISCUSS] Apache Stratos 4.1.0 Features
--
Lakmal Warusawithana
Vice President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
Re: Cartridge Store for Apache Straos
Posted by Ayesha Dissanayaka <ay...@wso2.com>.
Hi Imesh,
Cartridge store feature is definitely an additional and optional feature to
current Apache Stratos features, a value addition as Isuru mentioned.
If you look into the UI mockups [see attachment], you will find a separate
tab named "Cartrige Stratos" [Figure01]. That's where you will access and
deploy cartridges from remote server.
[image: Inline image 1]
[Figure01]
On Sun, Jun 1, 2014 at 7:41 PM, Isuru Haththotuwa <is...@apache.org> wrote:
> Hi Chris,
>
> Agree with your view. However AFAIU, its not mandatory that a developer
> use this store, and it should be optional as Imesh mentioned above. This is
> kind of a value addition.
>
>
> On Sun, Jun 1, 2014 at 7:33 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Hi,
>>
>> A good point Chris, may be cartridge store feature needs to be loosely
>> coupled with Stratos and be optional for default configuration.
>>
>> Thanks
>>
>>
>> On Sun, Jun 1, 2014 at 5:54 PM, chris snow <ch...@gmail.com> wrote:
>>
>>> Hi Lakmal,
>>>
>>> The main principles from my perspective is that Stratos developers:
>>>
>>> - should not need an internet connection to a remote cartridge store
>>> to be able to develop Stratos, and
>>> - should not need to install a local cartridge store if:
>>> - it is heavy weight (CPU, memory, etc), or
>>> - makes Stratos environments more complex to set up
>>>
>>> I.e. Stratos development environments should be self-contained and
>>> light weight enough to run on an average laptop.
>>>
>>> Cheers,
>>>
>>> Chris
>>>
>>>
>>> On Thu, May 29, 2014 at 11:46 AM, Lakmal Warusawithana <la...@wso2.com>
>>> wrote:
>>> > Hi,
>>> >
>>> > As I mention in [1] mail thread, we need to create and host $subject.
>>> >
>>> > WSO2 has some internal employee training program and I have proposed a
>>> group
>>> > project for create cartridge store and connect it from the Stratos
>>> Manager.
>>> > And there are 3 volunteers accept this project. I have encouraged them
>>> to
>>> > start their project proposal in dev list.
>>> >
>>> > Brief description of the project:
>>> >
>>> > Need to have Public Cartridge Store. (we have to host it). For this
>>> store
>>> > any contributors can submit their cartridges. There should be some
>>> test and
>>> > approved process. PMC can do the approval. Stratos Manager interface
>>> should
>>> > extent to connect to this store and get latest community created
>>> cartridges.
>>> > As the first step, these cartridges can be puppet models. Later we can
>>> > extent it to docker, cheft, ami etc. Manager automatically deploy this
>>> into
>>> > puppet master and also deploy as cartridges.
>>> >
>>> > Please share your thoughts, what else we need to consider on this. And
>>> we
>>> > can take this as first step, but we may need to continue develop this.
>>> >
>>> >
>>> > [1][DISCUSS] Apache Stratos 4.1.0 Features
>>> >
>>> > --
>>> > Lakmal Warusawithana
>>> > Vice President, Apache Stratos
>>> > 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
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PPMC Member, Apache Stratos
>>
>
>
--
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
20, Palmgrove Avenue, Colombo 3
E-Mail: ayesha@wso2.com <ay...@gmail.com>
Re: Cartridge Store for Apache Straos
Posted by Isuru Haththotuwa <is...@apache.org>.
Hi Chris,
Agree with your view. However AFAIU, its not mandatory that a developer use
this store, and it should be optional as Imesh mentioned above. This is
kind of a value addition.
On Sun, Jun 1, 2014 at 7:33 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi,
>
> A good point Chris, may be cartridge store feature needs to be loosely
> coupled with Stratos and be optional for default configuration.
>
> Thanks
>
>
> On Sun, Jun 1, 2014 at 5:54 PM, chris snow <ch...@gmail.com> wrote:
>
>> Hi Lakmal,
>>
>> The main principles from my perspective is that Stratos developers:
>>
>> - should not need an internet connection to a remote cartridge store
>> to be able to develop Stratos, and
>> - should not need to install a local cartridge store if:
>> - it is heavy weight (CPU, memory, etc), or
>> - makes Stratos environments more complex to set up
>>
>> I.e. Stratos development environments should be self-contained and
>> light weight enough to run on an average laptop.
>>
>> Cheers,
>>
>> Chris
>>
>>
>> On Thu, May 29, 2014 at 11:46 AM, Lakmal Warusawithana <la...@wso2.com>
>> wrote:
>> > Hi,
>> >
>> > As I mention in [1] mail thread, we need to create and host $subject.
>> >
>> > WSO2 has some internal employee training program and I have proposed a
>> group
>> > project for create cartridge store and connect it from the Stratos
>> Manager.
>> > And there are 3 volunteers accept this project. I have encouraged them
>> to
>> > start their project proposal in dev list.
>> >
>> > Brief description of the project:
>> >
>> > Need to have Public Cartridge Store. (we have to host it). For this
>> store
>> > any contributors can submit their cartridges. There should be some test
>> and
>> > approved process. PMC can do the approval. Stratos Manager interface
>> should
>> > extent to connect to this store and get latest community created
>> cartridges.
>> > As the first step, these cartridges can be puppet models. Later we can
>> > extent it to docker, cheft, ami etc. Manager automatically deploy this
>> into
>> > puppet master and also deploy as cartridges.
>> >
>> > Please share your thoughts, what else we need to consider on this. And
>> we
>> > can take this as first step, but we may need to continue develop this.
>> >
>> >
>> > [1][DISCUSS] Apache Stratos 4.1.0 Features
>> >
>> > --
>> > Lakmal Warusawithana
>> > Vice President, Apache Stratos
>> > 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
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PPMC Member, Apache Stratos
>
Re: Cartridge Store for Apache Straos
Posted by Lakmal Warusawithana <la...@wso2.com>.
On Sun, Jun 1, 2014 at 7:33 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi,
>
> A good point Chris, may be cartridge store feature needs to be loosely
> coupled with Stratos and be optional for default configuration.
>
>
It is loosely coupled
> Thanks
>
>
> On Sun, Jun 1, 2014 at 5:54 PM, chris snow <ch...@gmail.com> wrote:
>
>> Hi Lakmal,
>>
>> The main principles from my perspective is that Stratos developers:
>>
>> - should not need an internet connection to a remote cartridge store
>> to be able to develop Stratos, and
>> - should not need to install a local cartridge store if:
>> - it is heavy weight (CPU, memory, etc), or
>> - makes Stratos environments more complex to set up
>>
>> I.e. Stratos development environments should be self-contained and
>> light weight enough to run on an average laptop.
>>
>> Cheers,
>>
>> Chris
>>
>>
>> On Thu, May 29, 2014 at 11:46 AM, Lakmal Warusawithana <la...@wso2.com>
>> wrote:
>> > Hi,
>> >
>> > As I mention in [1] mail thread, we need to create and host $subject.
>> >
>> > WSO2 has some internal employee training program and I have proposed a
>> group
>> > project for create cartridge store and connect it from the Stratos
>> Manager.
>> > And there are 3 volunteers accept this project. I have encouraged them
>> to
>> > start their project proposal in dev list.
>> >
>> > Brief description of the project:
>> >
>> > Need to have Public Cartridge Store. (we have to host it). For this
>> store
>> > any contributors can submit their cartridges. There should be some test
>> and
>> > approved process. PMC can do the approval. Stratos Manager interface
>> should
>> > extent to connect to this store and get latest community created
>> cartridges.
>> > As the first step, these cartridges can be puppet models. Later we can
>> > extent it to docker, cheft, ami etc. Manager automatically deploy this
>> into
>> > puppet master and also deploy as cartridges.
>> >
>> > Please share your thoughts, what else we need to consider on this. And
>> we
>> > can take this as first step, but we may need to continue develop this.
>> >
>> >
>> > [1][DISCUSS] Apache Stratos 4.1.0 Features
>> >
>> > --
>> > Lakmal Warusawithana
>> > Vice President, Apache Stratos
>> > 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
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PPMC Member, Apache Stratos
>
--
Lakmal Warusawithana
Vice President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
Re: Cartridge Store for Apache Straos
Posted by Imesh Gunaratne <im...@apache.org>.
Hi,
A good point Chris, may be cartridge store feature needs to be loosely
coupled with Stratos and be optional for default configuration.
Thanks
On Sun, Jun 1, 2014 at 5:54 PM, chris snow <ch...@gmail.com> wrote:
> Hi Lakmal,
>
> The main principles from my perspective is that Stratos developers:
>
> - should not need an internet connection to a remote cartridge store
> to be able to develop Stratos, and
> - should not need to install a local cartridge store if:
> - it is heavy weight (CPU, memory, etc), or
> - makes Stratos environments more complex to set up
>
> I.e. Stratos development environments should be self-contained and
> light weight enough to run on an average laptop.
>
> Cheers,
>
> Chris
>
>
> On Thu, May 29, 2014 at 11:46 AM, Lakmal Warusawithana <la...@wso2.com>
> wrote:
> > Hi,
> >
> > As I mention in [1] mail thread, we need to create and host $subject.
> >
> > WSO2 has some internal employee training program and I have proposed a
> group
> > project for create cartridge store and connect it from the Stratos
> Manager.
> > And there are 3 volunteers accept this project. I have encouraged them to
> > start their project proposal in dev list.
> >
> > Brief description of the project:
> >
> > Need to have Public Cartridge Store. (we have to host it). For this store
> > any contributors can submit their cartridges. There should be some test
> and
> > approved process. PMC can do the approval. Stratos Manager interface
> should
> > extent to connect to this store and get latest community created
> cartridges.
> > As the first step, these cartridges can be puppet models. Later we can
> > extent it to docker, cheft, ami etc. Manager automatically deploy this
> into
> > puppet master and also deploy as cartridges.
> >
> > Please share your thoughts, what else we need to consider on this. And we
> > can take this as first step, but we may need to continue develop this.
> >
> >
> > [1][DISCUSS] Apache Stratos 4.1.0 Features
> >
> > --
> > Lakmal Warusawithana
> > Vice President, Apache Stratos
> > 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
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PPMC Member, Apache Stratos
Re: Cartridge Store for Apache Straos
Posted by chris snow <ch...@gmail.com>.
Yep, makes sense. Thanks for confirming.
On Sun, Jun 1, 2014 at 4:16 PM, Lakmal Warusawithana <la...@wso2.com> wrote:
> Hi Chris,
>
> Totally agree. This is not mandatory for deploying, creating ..etc
> cartridges. This is an optional, and it give some ease for getting new
> cartridges, who has connectivity for the store.
>
> Also users can download cartridges manually from the store and can install
> into their Stratos deployment. Cartridge store is single location for
> finding community develop cartridges.
>
> Is now make sense?
>
> On Sun, Jun 1, 2014 at 5:54 PM, chris snow <ch...@gmail.com> wrote:
>>
>> Hi Lakmal,
>>
>> The main principles from my perspective is that Stratos developers:
>>
>> - should not need an internet connection to a remote cartridge store
>> to be able to develop Stratos, and
>> - should not need to install a local cartridge store if:
>> - it is heavy weight (CPU, memory, etc), or
>> - makes Stratos environments more complex to set up
>>
>> I.e. Stratos development environments should be self-contained and
>> light weight enough to run on an average laptop.
>>
>> Cheers,
>>
>> Chris
>>
>>
>> On Thu, May 29, 2014 at 11:46 AM, Lakmal Warusawithana <la...@wso2.com>
>> wrote:
>> > Hi,
>> >
>> > As I mention in [1] mail thread, we need to create and host $subject.
>> >
>> > WSO2 has some internal employee training program and I have proposed a
>> > group
>> > project for create cartridge store and connect it from the Stratos
>> > Manager.
>> > And there are 3 volunteers accept this project. I have encouraged them
>> > to
>> > start their project proposal in dev list.
>> >
>> > Brief description of the project:
>> >
>> > Need to have Public Cartridge Store. (we have to host it). For this
>> > store
>> > any contributors can submit their cartridges. There should be some test
>> > and
>> > approved process. PMC can do the approval. Stratos Manager interface
>> > should
>> > extent to connect to this store and get latest community created
>> > cartridges.
>> > As the first step, these cartridges can be puppet models. Later we can
>> > extent it to docker, cheft, ami etc. Manager automatically deploy this
>> > into
>> > puppet master and also deploy as cartridges.
>> >
>> > Please share your thoughts, what else we need to consider on this. And
>> > we
>> > can take this as first step, but we may need to continue develop this.
>> >
>> >
>> > [1][DISCUSS] Apache Stratos 4.1.0 Features
>> >
>> > --
>> > Lakmal Warusawithana
>> > Vice President, Apache Stratos
>> > 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
>
>
>
>
> --
> Lakmal Warusawithana
> Vice President, Apache Stratos
> 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 Store for Apache Straos
Posted by Lakmal Warusawithana <la...@wso2.com>.
Hi Chris,
Totally agree. This is not mandatory for deploying, creating ..etc
cartridges. This is an optional, and it give some ease for getting new
cartridges, who has connectivity for the store.
Also users can download cartridges manually from the store and can install
into their Stratos deployment. Cartridge store is single location for
finding community develop cartridges.
Is now make sense?
On Sun, Jun 1, 2014 at 5:54 PM, chris snow <ch...@gmail.com> wrote:
> Hi Lakmal,
>
> The main principles from my perspective is that Stratos developers:
>
> - should not need an internet connection to a remote cartridge store
> to be able to develop Stratos, and
> - should not need to install a local cartridge store if:
> - it is heavy weight (CPU, memory, etc), or
> - makes Stratos environments more complex to set up
>
> I.e. Stratos development environments should be self-contained and
> light weight enough to run on an average laptop.
>
> Cheers,
>
> Chris
>
>
> On Thu, May 29, 2014 at 11:46 AM, Lakmal Warusawithana <la...@wso2.com>
> wrote:
> > Hi,
> >
> > As I mention in [1] mail thread, we need to create and host $subject.
> >
> > WSO2 has some internal employee training program and I have proposed a
> group
> > project for create cartridge store and connect it from the Stratos
> Manager.
> > And there are 3 volunteers accept this project. I have encouraged them to
> > start their project proposal in dev list.
> >
> > Brief description of the project:
> >
> > Need to have Public Cartridge Store. (we have to host it). For this store
> > any contributors can submit their cartridges. There should be some test
> and
> > approved process. PMC can do the approval. Stratos Manager interface
> should
> > extent to connect to this store and get latest community created
> cartridges.
> > As the first step, these cartridges can be puppet models. Later we can
> > extent it to docker, cheft, ami etc. Manager automatically deploy this
> into
> > puppet master and also deploy as cartridges.
> >
> > Please share your thoughts, what else we need to consider on this. And we
> > can take this as first step, but we may need to continue develop this.
> >
> >
> > [1][DISCUSS] Apache Stratos 4.1.0 Features
> >
> > --
> > Lakmal Warusawithana
> > Vice President, Apache Stratos
> > 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
>
--
Lakmal Warusawithana
Vice President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
Re: Cartridge Store for Apache Straos
Posted by chris snow <ch...@gmail.com>.
Hi Lakmal,
The main principles from my perspective is that Stratos developers:
- should not need an internet connection to a remote cartridge store
to be able to develop Stratos, and
- should not need to install a local cartridge store if:
- it is heavy weight (CPU, memory, etc), or
- makes Stratos environments more complex to set up
I.e. Stratos development environments should be self-contained and
light weight enough to run on an average laptop.
Cheers,
Chris
On Thu, May 29, 2014 at 11:46 AM, Lakmal Warusawithana <la...@wso2.com> wrote:
> Hi,
>
> As I mention in [1] mail thread, we need to create and host $subject.
>
> WSO2 has some internal employee training program and I have proposed a group
> project for create cartridge store and connect it from the Stratos Manager.
> And there are 3 volunteers accept this project. I have encouraged them to
> start their project proposal in dev list.
>
> Brief description of the project:
>
> Need to have Public Cartridge Store. (we have to host it). For this store
> any contributors can submit their cartridges. There should be some test and
> approved process. PMC can do the approval. Stratos Manager interface should
> extent to connect to this store and get latest community created cartridges.
> As the first step, these cartridges can be puppet models. Later we can
> extent it to docker, cheft, ami etc. Manager automatically deploy this into
> puppet master and also deploy as cartridges.
>
> Please share your thoughts, what else we need to consider on this. And we
> can take this as first step, but we may need to continue develop this.
>
>
> [1][DISCUSS] Apache Stratos 4.1.0 Features
>
> --
> Lakmal Warusawithana
> Vice President, Apache Stratos
> 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 Store for Apache Straos
Posted by Dakshika Jayathilaka <da...@wso2.com>.
Hi,
We have developed initial UI mockups for above Cartridge store integration.
https://moqups.com/dakshika@wso2.com/ySOdjAdA
Thank you
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Fri, May 30, 2014 at 8:19 AM, Dakshika Jayathilaka <da...@wso2.com>
wrote:
> Hi,
>
> I'm Dakshika Jayathilaka, training employee at WSO2. I'm
> writing this on behalf of our voluntary team, who like to contribute to
> above mentioned project. Our team members as follows.
>
> Ayesha Dissanayaka <ay...@wso2.com>
> Roshan Wijesena <ro...@wso2.com>
> Dakshika Jayathilaka <da...@wso2.com>
>
>
> As Lakmal mentioned, We are suppose to develop cartridge store for Apache
> Stratos[1
> <http://mail-archives.eu.apache.org/mod_mbox/incubator-stratos-dev/201405.mbox/browser>
> ].
>
>
> *Cartridge Store for Stratos proposal *
>
> *Abstract*
>
> Develop a cartridge store and Apache Stratos management module to manage
> those cartridges within Apache Stratos manager.
>
> *Proposal*
>
> Apache Stratos supports polyglot environments where multiple languages are
> used simultaneously. The Cartridge concept allows the users of Apache
> Stratos to develop and run their own Cartridges using any language or
> framework. Currently Stratos bundles with few prefabricated cartridges.
>
> Apache stratos doesn't have capability of getting community
> cartridges to stratos manager. Our target is to develop mechanism to get
> more community support from publishing public cartridge store and
> incorporate store with stratos manager. Then Devops can easily get publicly
> rated cartridges into their stratos deployment via stratos store manager
> component.
>
> *Proposed Architecture*
>
> There are three main components consist within our proposed
> architecture.
>
> 1. Public Cartridge store
> 2. Stratos manager cartridge component
> 3. Puppet master module deployment agent
>
> *Rationale*
>
> Public users, community can publish cartridges by registering with store
> and Public store cartridges are accessible via store Front-Office.
> Cartridge submission and life-cycle management can be handled at the
> Back-Office who has authorization. REST based API
> used to get store cartridge information to Stratos management component.
> We plan to use WSO2 Enterprise Store to develop cartridge store component. [
> 2 <http://wso2.com/products/enterprise-store/>] justification may discuss
> under title "justification".
>
> Stratos Manager(SM) Cartridge Component consist with six modules.
>
>
> - REST Client: interact with the public Cartridge store to get
> published cartridge information
> - JSON Validator: validate JSON replies from the Cartridge store
> before forward into next module
> - Cartridge Sort/search/setting and Paging module: manage DevOps
> interaction with public Cartridges which available to download
> - Cartridge Loader: will helps to list up already deployed cartridges
> within puppet maser
> - Cartridge Validator : validate the availability of Cartridges with
> current puppet master modules
> - Stratos Cartridge Connector: Download Cartridge artifacts from the
> store to puppet master and manage their deployment.
>
> Puppet Master module deployment agent will communicate with SM cartridge
> component using secure mechanism and deploy relevant artifacts to puppet
> master.
>
> *Justification*
>
> Above mentioned store component needs most of the standard store features
> including API support. There are many store building systems and we
> evaluate highly demanded store systems Magento Community[3], Opencart[4],
> WooCommerce[5] and WSO2ES[2]. We mainly focused on features, future trends
> and license which can be easily integrated on this environment.
>
> According to our analysis we decide to use WSO2ES with higher rapid growth
> ratio.
>
> *Proposed Architectural Design*
>
>
>
>
> * *
>
>
>
> *Initial Goals*
>
> ** *Develop public cartridge store
> * Stratos manager store supportability
> * Create deployment method on puppet master
> * Supports to puppet based cartridge
>
> *Future Goals*
>
> * Supports for chef and Docker
>
>
> Thank you.
>
>
> [1] [DISCUSS] "Apache Stratos 4.1.0 Features" mail archive
> <http://mail-archives.eu.apache.org/mod_mbox/incubator-stratos-dev/201405.mbox/browser>
> [2] http://wso2.com/products/enterprise-store/
> [3] http://magento.com/products/overview#community
> [4] http://www.opencart.com/
> [5] http://wordpress.org/plugins/woocommerce/
>
>
> *Dakshika Jayathilaka*
> Software Engineer
> WSO2, Inc.
> lean.enterprise.middleware
> 0771100911
>
>
> On Thu, May 29, 2014 at 10:46 AM, Lakmal Warusawithana <la...@wso2.com>
> wrote:
>
>> Hi,
>>
>> As I mention in [1] mail thread, we need to create and host $subject.
>>
>> WSO2 has some internal employee training program and I have proposed a
>> group project for create cartridge store and connect it from the Stratos
>> Manager. And there are 3 volunteers accept this project. I have encouraged
>> them to start their project proposal in dev list.
>>
>> Brief description of the project:
>>
>> Need to have Public Cartridge Store. (we have to host it). For this store
>> any contributors can submit their cartridges. There should be some test and
>> approved process. PMC can do the approval. Stratos Manager interface should
>> extent to connect to this store and get latest community created
>> cartridges. As the first step, these cartridges can be puppet models. Later
>> we can extent it to docker, cheft, ami etc. Manager automatically deploy
>> this into puppet master and also deploy as cartridges.
>>
>> Please share your thoughts, what else we need to consider on this. And we
>> can take this as first step, but we may need to continue develop this.
>>
>>
>> [1][DISCUSS] Apache Stratos 4.1.0 Features
>>
>> --
>> Lakmal Warusawithana
>> Vice President, Apache Stratos
>> Director - Cloud Architecture; WSO2 Inc.
>> Mobile : +94714289692
>> Blog : http://lakmalsview.blogspot.com/
>>
>>
>
Re: Cartridge Store for Apache Straos
Posted by Dakshika Jayathilaka <da...@wso2.com>.
Hi,
I'm Dakshika Jayathilaka, training employee at WSO2. I'm
writing this on behalf of our voluntary team, who like to contribute to
above mentioned project. Our team members as follows.
Ayesha Dissanayaka <ay...@wso2.com>
Roshan Wijesena <ro...@wso2.com>
Dakshika Jayathilaka <da...@wso2.com>
As Lakmal mentioned, We are suppose to develop cartridge store for Apache
Stratos[1
<http://mail-archives.eu.apache.org/mod_mbox/incubator-stratos-dev/201405.mbox/browser>
].
*Cartridge Store for Stratos proposal *
*Abstract*
Develop a cartridge store and Apache Stratos management module to manage
those cartridges within Apache Stratos manager.
*Proposal*
Apache Stratos supports polyglot environments where multiple languages are
used simultaneously. The Cartridge concept allows the users of Apache
Stratos to develop and run their own Cartridges using any language or
framework. Currently Stratos bundles with few prefabricated cartridges.
Apache stratos doesn't have capability of getting community cartridges
to stratos manager. Our target is to develop mechanism to get more
community support from publishing public cartridge store and incorporate
store with stratos manager. Then Devops can easily get publicly rated
cartridges into their stratos deployment via stratos store manager
component.
*Proposed Architecture*
There are three main components consist within our proposed
architecture.
1. Public Cartridge store
2. Stratos manager cartridge component
3. Puppet master module deployment agent
*Rationale*
Public users, community can publish cartridges by registering with store
and Public store cartridges are accessible via store Front-Office.
Cartridge submission and life-cycle management can be handled at the
Back-Office who has authorization. REST based API
used to get store cartridge information to Stratos management component. We
plan to use WSO2 Enterprise Store to develop cartridge store component. [2
<http://wso2.com/products/enterprise-store/>] justification may discuss
under title "justification".
Stratos Manager(SM) Cartridge Component consist with six modules.
- REST Client: interact with the public Cartridge store to get
published cartridge information
- JSON Validator: validate JSON replies from the Cartridge store before
forward into next module
- Cartridge Sort/search/setting and Paging module: manage DevOps
interaction with public Cartridges which available to download
- Cartridge Loader: will helps to list up already deployed cartridges
within puppet maser
- Cartridge Validator : validate the availability of Cartridges with
current puppet master modules
- Stratos Cartridge Connector: Download Cartridge artifacts from the
store to puppet master and manage their deployment.
Puppet Master module deployment agent will communicate with SM cartridge
component using secure mechanism and deploy relevant artifacts to puppet
master.
*Justification*
Above mentioned store component needs most of the standard store features
including API support. There are many store building systems and we
evaluate highly demanded store systems Magento Community[3], Opencart[4],
WooCommerce[5] and WSO2ES[2]. We mainly focused on features, future trends
and license which can be easily integrated on this environment.
According to our analysis we decide to use WSO2ES with higher rapid growth
ratio.
*Proposed Architectural Design*
* *
*Initial Goals*
** *Develop public cartridge store
* Stratos manager store supportability
* Create deployment method on puppet master
* Supports to puppet based cartridge
*Future Goals*
* Supports for chef and Docker
Thank you.
[1] [DISCUSS] "Apache Stratos 4.1.0 Features" mail archive
<http://mail-archives.eu.apache.org/mod_mbox/incubator-stratos-dev/201405.mbox/browser>
[2] http://wso2.com/products/enterprise-store/
[3] http://magento.com/products/overview#community
[4] http://www.opencart.com/
[5] http://wordpress.org/plugins/woocommerce/
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Thu, May 29, 2014 at 10:46 AM, Lakmal Warusawithana <la...@wso2.com>
wrote:
> Hi,
>
> As I mention in [1] mail thread, we need to create and host $subject.
>
> WSO2 has some internal employee training program and I have proposed a
> group project for create cartridge store and connect it from the Stratos
> Manager. And there are 3 volunteers accept this project. I have encouraged
> them to start their project proposal in dev list.
>
> Brief description of the project:
>
> Need to have Public Cartridge Store. (we have to host it). For this store
> any contributors can submit their cartridges. There should be some test and
> approved process. PMC can do the approval. Stratos Manager interface should
> extent to connect to this store and get latest community created
> cartridges. As the first step, these cartridges can be puppet models. Later
> we can extent it to docker, cheft, ami etc. Manager automatically deploy
> this into puppet master and also deploy as cartridges.
>
> Please share your thoughts, what else we need to consider on this. And we
> can take this as first step, but we may need to continue develop this.
>
>
> [1][DISCUSS] Apache Stratos 4.1.0 Features
>
> --
> Lakmal Warusawithana
> Vice President, Apache Stratos
> Director - Cloud Architecture; WSO2 Inc.
> Mobile : +94714289692
> Blog : http://lakmalsview.blogspot.com/
>
>