On Sat, Oct 26, 2013 at 4:15 PM, Imesh Gunaratne <[email protected]> wrote:
> Yes my mistake, it should be 4.0.0-SNAPSHOT. > I have now changed the version to 4.0.0-SNAPSHOT in trunk (not pushed) and > performing a clean repo build to identify the issues. > > Nirmal: Will you be able to setup CEP in the EC2 instance we created for > M1? > Imesh, I've provided the CEP pack, let me know when you all trying to configure it, I gave some tips to Lahiru too. Unfortunately, I'm keeping busy with some other work these days. But let's synch up and do, I'll help if you got issues. > Thanks > > > On Sat, Oct 26, 2013 at 2:45 PM, Nirmal Fernando > <[email protected]>wrote: > >> >> On Oct 26, 2013 12:16 PM, "Imesh Gunaratne" <[email protected]> wrote: >> > >> > Correction: Please update if I have missed any other points. >> > >> > Thanks Lahiru for adding detailed information on Auto-Scaler status. I >> think we need to update the product versions to 4.0.0-M1 in pom.xml files. >> >> Imesh, it's always x.x.x-SNAPSHOT in trunk and in branches only, you >> normally change the versions. >> >> And we don't change pom versions for every milestone. >> >> I will do that next. >> > >> > Thanks >> > >> > >> > On Sat, Oct 26, 2013 at 8:38 AM, Lahiru Sandaruwan <[email protected]> >> wrote: >> >> >> >> Hi Imesh, >> >> >> >> Small addition from autoscaler side as per the yesterday state, >> >> >> >> We can deploy/ hot deploy autoscale policy as a xml filr >> >> Autoscaler receives cluster created event sent from Cloud controller >> when the subscription happens >> >> It process the request using rules engine(drools) and calls the Cloud >> controller to spawn minimum number of instance in all Cloud partitions. >> >> Cloud controller spawned the requested instances >> >> I will send a detailed description to Autoscaler discussion thread. >> >> >> >> Thanks. >> >> >> >> >> >> On Sat, Oct 26, 2013 at 8:27 AM, Imesh Gunaratne <[email protected]> >> wrote: >> >>> >> >>> Hi All, >> >>> >> >>> We have now created an Amazon EC2 instance with all the latest binary >> packages of Load Balancer, Cloud Controller, Auto-Scaler and CEP Extension. >> A PHP cartridge was created using the new Cartridge Agent. >> >>> >> >>> At the moment we are going through the complete flow by fixing >> integration issues being found. >> >>> >> >>> Work Flow Items Done: >> >>> - All modules are now communicating properly via the message broker. >> >>> - Cartridge definitions get deployed properly. >> >>> - Stratos Controller is working as expected. A tenant user could >> subscribe to a cartridge using this. >> >>> - Cartridge Agent is properly publishing instance status events to >> the message broker. >> >>> - Cloud Controller is properly publishing topology events to the >> message broker. >> >>> - Load Balancer is receiving topology events and updating its >> topology data structure. >> >>> >> >>> Work Flow Items Missing: >> >>> - Real-time Event Processing Engine integration is not done. >> >>> - Cartridge Agent is not deploying the artifacts. We need to update >> the payload.zip. >> >>> - Auto-Scaler is not spinning up instances since Real-time Event >> Processing Engine integration is missing. >> >>> >> >>> Team: Please update if I have missing any other points. >> >>> >> >>> Thanks >> >>> Imesh >> >> >> >> >> >> >> >> >> >> -- >> >> -- >> >> Lahiru Sandaruwan >> >> Software Engineer, >> >> Platform Technologies, >> >> WSO2 Inc., http://wso2.com >> >> lean.enterprise.middleware >> >> >> >> email: [email protected] cell: (+94) 773 325 954 >> >> blog: http://lahiruwrites.blogspot.com/ >> >> twitter: http://twitter.com/lahirus >> >> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >> >> >> > >> > > -- Best Regards, Nirmal Nirmal Fernando. PPMC Member & Committer of Apache Stratos, Senior Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/
