Yep, makes sense. Thanks for confirming. On Sun, Jun 1, 2014 at 4:16 PM, Lakmal Warusawithana <lak...@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 <chsnow...@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 <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 > > > > > -- > 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
