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 2013/10/26 16:11:30 UTC
[jira] [Updated] (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 updated STRATOS-127:
------------------------------------
Summary: Cartridge Agent Implementation for Stratos 4.0.0 (was: Cartridge Agent Implementation for 4.0.0 Release)
> 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 Alpha 1
> Reporter: Imesh Gunaratne
> Assignee: Imesh Gunaratne
>
> 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.1#6144)