[
https://issues.apache.org/jira/browse/STRATOS-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810179#comment-13810179
]
Pradeep Fernando commented on STRATOS-143:
------------------------------------------
Created an new cartridge using the base agent scripts. Below are the steps
followed..
- created new cartridge instance cloning the already existing stratos 2.0 AMI.
- replaced them with new agent scripts found in apache stratos trunk.
(/produts/cartridge-agent)
- Tested the new system in Stratos 4.0 environment.
- Used the same cartridge definition file used in Stratos 2.0 after minor edits
- Found an issue with file copying in the new cartridge. Fixed it (patch
attached)
- Created a new AMI with fixes.
- Re-ran the tests.
- Made the AMI image public; details..
id: ami-c845109a
region: Asia Pacific (Singapore)
name: apache-stratos-4.0.0-M1-tomcat-cartridge-r2
Please review and commit the patch.
> Create EC2 Tomcat Cartridge for Stratos 4.0.0-M1
> ------------------------------------------------
>
> Key: STRATOS-143
> URL: https://issues.apache.org/jira/browse/STRATOS-143
> Project: Stratos
> Issue Type: Sub-task
> Affects Versions: 4.0.0 M2
> Reporter: Imesh Gunaratne
> Assignee: Imesh Gunaratne
> Fix For: 4.0.0 M2
>
>
> We need to create a new EC2 Tomcat Cartridge using the new Catridge Agent.
> This will make use of the previous stratos-init.sh, get-launch-params.rb
> written for EC2/Tomcat and add relevant logic to send Member Started and
> Member Activated events to the message broker. Message broker ip-address,
> port, service name, cluster id and member id will be read from the user data
> parameters.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
