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/10/12 05:47:33 UTC

[jira] [Resolved] (STRATOS-127) Cartridge Agent Implementation for Stratos 4.0.0

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

Imesh Gunaratne resolved STRATOS-127.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 4.0.0

> Cartridge Agent Implementation for Stratos 4.0.0
> ------------------------------------------------
>
>                 Key: STRATOS-127
>                 URL: https://issues.apache.org/jira/browse/STRATOS-127
>             Project: Stratos
>          Issue Type: New Feature
>    Affects Versions: 4.0.0 M5
>            Reporter: Imesh Gunaratne
>            Assignee: Imesh Gunaratne
>             Fix For: 4.0.0
>
>
> According to the new architecture of Stratos we need to have an agent running in each cartridge instance (VM instance). The responsibilities of the agent would be following:
> 1. Retrieve meta data via instance user-data (payload).
> 2. Process user-data and retrieve required information.
> 3. Send member started event to message broker topic "instance-status".
> 4. Start the application.
> 5. Check the health of the application.
> 6. Send member activated event once the application is ready to serve incoming requests.
> 7. Send health stats periodically to CEP.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)