Hi Lamkal and Manula, Thanks for the clarification.
On Wed, Nov 5, 2014 at 8:09 AM, Manula Chathurika Thantriwatte < [email protected]> wrote: > Hi Udara, > > Single cartridge subscription goes through the application deployment and > start it. So we can omit the subscription terminology. > > Thanks ! > > On Wed, Nov 5, 2014 at 12:54 AM, Lakmal Warusawithana <[email protected]> > wrote: > >> >> >> On Wed, Nov 5, 2014 at 12:12 AM, Udara Liyanage <[email protected]> wrote: >> >>> >>> >>> >>> >>> Touched, not typed. Erroneous words are a feature, not a typo. >>> On Nov 4, 2014 11:55 PM, "Imesh Gunaratne" <[email protected]> wrote: >>> > >>> > Hi Devs, >>> > >>> > In Stratos 4.0.0 release we used following terminology: >>> > >>> > Create a Cartridge >>> > Create a VM/docker image, configuration management (puppet) module and >>> specify cartridge definition >>> > >>> > Deploy a Cartridge >>> > Upload a cartridge definition to Stratos. >>> > >>> > Subscribe to a Cartridge >>> > Create an instance/cluster of above cartridge >>> > >>> > Un-Subscribe from a Cartridge >>> > Remove the instance/cluster created in the subscription >>> > >>> > Un-Deploy a Cartridge >>> > Remove a cartridge definition from Stratos >>> > >>> > Now with service grouping things have been changed slightly and we may >>> need to consider using new terminology for this process. How do you like >>> following terminology: >>> > >>> > Create an Application >>> > Create VM/docker images, configuration management (puppet) modules, >>> specify cartridge definitions, dependencies and application definition >>> > >>> > Deploy an Application >>> > Upload an application definition to Stratos >>> > >>> > Start an Application >>> > Create an instance of the application and create clusters for the >>> corrosponding cartridges. >>> > >>> >>> When an application is deployed, instances are also spawned. So >>> Application Start terminology is not needed IMO. >>> > Stop an Application >>> > Remove the application instance and clusters created in application >>> startup process. >>> > >>> > Un-Deploy an Application >>> > Remove an application definition from Stratos >>> >>> Same as above, application undeployment remove the instances and >>> application definition. >>> > >>> > In addition to these we may still use the terms: >>> Create/Deploy/Undeploy Cartridge. >>> > >>> > I noticed that with the latest grouping changes we have removed the >>> concept of subscription and included it in the deployment phase. IMO it >>> would be better to have a separation between these two steps because >>> otherwise all applications deployed in Stratos will be up and running all >>> the time. >>> >>> Still we can subscribe to a single cartridge as we did early without >>> application deployment, right? >>> >> >> No, it should through the application deploy. If its a single cartridge, >> then application json has single cartridge info. >> >> >>> >>> > >>> > Thanks >>> > >>> > >>> > >>> > -- >>> > Imesh Gunaratne >>> > >>> > Technical Lead, WSO2 >>> > Committer & PMC Member, Apache Stratos >>> >> >> >> >> -- >> Lakmal Warusawithana >> Vice President, Apache Stratos >> Director - Cloud Architecture; WSO2 Inc. >> Mobile : +94714289692 >> Blog : http://lakmalsview.blogspot.com/ >> >> > > > -- > Regards, > Manula Chathurika Thantriwatte > Software Engineer > WSO2 Inc. : http://wso2.com > lean . enterprise . middleware > > email : [email protected] / [email protected] > phone : +94 772492511 > blog : http://manulachathurika.blogspot.com/ > > > > -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897
