[STRATOS-127] Cartridge Agent Implementation for Stratos 4.0.0

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.0 M5
• Fix Version/s: 4.0.0
• Assignee: Imesh Gunaratne
• Reporter: Imesh Gunaratne
• Created: 24/Oct/13 11:40
• Updated: 12/Oct/14 03:47
• Resolved: 12/Oct/14 03:47

Description

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.

Sub-Tasks

• Implement a Java based Cartridge Agent Event Publisher: Resolved
• Create EC2 PHP Cartridge for Stratos 4.0.0-M1: Resolved
• Create EC2 MySQL Cartridge for Stratos 4.0.0-M1: Resolved
• Create EC2 Tomcat Cartridge for Stratos 4.0.0-M1: Resolved
• STRATOS-127 / Send health stats periodically to CEP: Resolved
• Member Fault Event Generation Process is Not Valid: Closed
• Move CEP Statistics Publisher to Stratos Common: Resolved
• Refactor Cartridge Agent as a Standalone Product: Resolved