You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by "Imesh Gunaratne (JIRA)" <ji...@apache.org> on 2014/04/04 20:08:16 UTC
[jira] [Updated] (STRATOS-319) Refactor Cartridge Agent as a Standalone Product

     [ https://issues.apache.org/jira/browse/STRATOS-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Imesh Gunaratne updated STRATOS-319:
------------------------------------

    Description: 
Currently cartridge agent consists of several modules: event-publisher, event-subscriber and health-publisher. In this model it is difficult to synchronize the work-flow among different products. Therefore it would be better to implement a single product which could handle all the features.

Work Flow:

1. Configure Cartridge Agent, provide mb-ip, mb-port, cep-ip, cep-port, payload-file-path.
2. Start Cartridge Agent.
3. Publish instance started event.
4. Wait for application ports to be active.
5. If no artifact repository given send instance activated event.
6. If artifact repository given, wait for artifact update event sent by Stratos Manager.
7. Once artifact update event is received, checkout artifacts.
8. Once artifacts are checked out send instance activated event.
9. If another artifact update event is received, checkout artifacts.

  was:Currently cartridge agent consists of several modules: event-publisher, event-subscriber and health-publisher. In this model it is difficult to synchronize the work-flow among different products. Therefore it would be better to implement a single product which could handle all the features.


> Refactor Cartridge Agent as a Standalone Product
> ------------------------------------------------
>
>                 Key: STRATOS-319
>                 URL: https://issues.apache.org/jira/browse/STRATOS-319
>             Project: Stratos
>          Issue Type: Sub-task
>          Components: Cartridge Agent
>            Reporter: Imesh Gunaratne
>            Assignee: Imesh Gunaratne
>
> Currently cartridge agent consists of several modules: event-publisher, event-subscriber and health-publisher. In this model it is difficult to synchronize the work-flow among different products. Therefore it would be better to implement a single product which could handle all the features.
> Work Flow:
> 1. Configure Cartridge Agent, provide mb-ip, mb-port, cep-ip, cep-port, payload-file-path.
> 2. Start Cartridge Agent.
> 3. Publish instance started event.
> 4. Wait for application ports to be active.
> 5. If no artifact repository given send instance activated event.
> 6. If artifact repository given, wait for artifact update event sent by Stratos Manager.
> 7. Once artifact update event is received, checkout artifacts.
> 8. Once artifacts are checked out send instance activated event.
> 9. If another artifact update event is received, checkout artifacts.



--
This message was sent by Atlassian JIRA
(v6.2#6252)