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 <lak...@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

Reply via email to