On Tue, Nov 4, 2014 at 11:54 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.
>

+1 for separation of these actions. It will increase the usability.

>
> *Stop an Application*
> Remove the application instance and clusters created in application
> startup process.
>
> *Un-Deploy an Application*
> Remove an application definition from Stratos
>
> 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.
>
> Thanks
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>



-- 
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

email: [email protected] blog: http://lahiruwrites.blogspot.com/
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146

Reply via email to