[
https://issues.apache.org/jira/browse/STRATOS-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-326:
------------------------------------
Affects Version/s: (was: 4.0.0 Alpha)
> Implement Cartridge Agent Extension Points
> ------------------------------------------
>
> Key: STRATOS-326
> URL: https://issues.apache.org/jira/browse/STRATOS-326
> Project: Stratos
> Issue Type: Task
> Components: Cartridge Instance Agent
> Reporter: Imesh Gunaratne
> Assignee: Imesh Gunaratne
> Fix For: 4.0.0 Alpha
>
>
> This is a suggestion made by Lakmal. In Cartridge Agent it would be great if
> we could keep extension points to allow users to capture events and execute
> any cartridge specific logic.
> Cartridge Agent Work Flow:
> 1. Start VM Instance.
> 2. Start Cartridge Agent.
> 3. Publish Instance Started event to Instance Status topic.
> 4. Execute extension script to start the server(s). May be this could be
> called extensions/instance-started.sh
> 5. If no artifact Git repository found wait for the application ports to be
> active.
> 6. Once ports are active publish Instance Activated event to Instance Status
> topic.
> 7. Execute extension script to notify Instance Activated event. May be this
> could be called extensions/instance-activated.sh
> 6. If artifact Git repository found, wait for the Update Artifacts event on
> Instance Notifier topic.
> 7. Once Artifact Update event received checkout artifacts.
> 8. Copy artifacts to the given application path.
> 9. Execute extension script to notify Artifacts Updated event. May be this
> could be called extensions/artifacts-updated.sh
> 10. Wait for the application ports to be active.
> 11. Repeat from step 6 until stopped.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
