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 <im...@apache.org> on 2013/10/26 04:57:10 UTC
Apache Stratos (incubating) 4.0.0-M1 Status
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
Re: Apache Stratos (incubating) 4.0.0-M1 Status
Posted by Imesh Gunaratne <im...@apache.org>.
Thanks Nirmal, no problem.
On Sun, Oct 27, 2013 at 12:18 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>
>
> On Sat, Oct 26, 2013 at 4:15 PM, Imesh Gunaratne <im...@apache.org> 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 <ni...@gmail.com>wrote:
>>
>>>
>>> On Oct 26, 2013 12:16 PM, "Imesh Gunaratne" <im...@apache.org> 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 <la...@wso2.com>
>>> 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 <im...@apache.org>
>>> 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: lahirus@wso2.com 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/
>
Re: Apache Stratos (incubating) 4.0.0-M1 Status
Posted by Nirmal Fernando <ni...@gmail.com>.
On Sat, Oct 26, 2013 at 4:15 PM, Imesh Gunaratne <im...@apache.org> 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 <ni...@gmail.com>wrote:
>
>>
>> On Oct 26, 2013 12:16 PM, "Imesh Gunaratne" <im...@apache.org> 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 <la...@wso2.com>
>> 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 <im...@apache.org>
>> 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: lahirus@wso2.com 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/
Re: Apache Stratos (incubating) 4.0.0-M1 Status
Posted by Imesh Gunaratne <im...@apache.org>.
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?
Thanks
On Sat, Oct 26, 2013 at 2:45 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>
> On Oct 26, 2013 12:16 PM, "Imesh Gunaratne" <im...@apache.org> 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 <la...@wso2.com>
> 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 <im...@apache.org>
> 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: lahirus@wso2.com 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
> >>
> >
>
Re: Apache Stratos (incubating) 4.0.0-M1 Status
Posted by Nirmal Fernando <ni...@gmail.com>.
On Oct 26, 2013 12:16 PM, "Imesh Gunaratne" <im...@apache.org> 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 <la...@wso2.com>
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 <im...@apache.org>
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: lahirus@wso2.com 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
>>
>
Re: Apache Stratos (incubating) 4.0.0-M1 Status
Posted by Imesh Gunaratne <im...@apache.org>.
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.
I will do that next.
Thanks
On Sat, Oct 26, 2013 at 8:38 AM, Lahiru Sandaruwan <la...@wso2.com> 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 <im...@apache.org> 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: lahirus@wso2.com 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
>
>
Re: Apache Stratos (incubating) 4.0.0-M1 Status
Posted by Lahiru Sandaruwan <la...@wso2.com>.
Hi Luca,
Thanks for bringing this up.
Hope you mean a connection like database cartridge for an application
cartridge.
E.g. PHP cartridge depends on Mysql cartridge.
If the PHP cartridge connect Mysql cartridge directly(not though LB) we
will not receive LB statistics to Autoscaler. But it receive load average
and memory consumption though cartridge agent placed inside instance.
So the Autoscaler knows the load of both PHP and Mysql cartridges and
handles it.
Do we still consider this dependency at rules(i might missing some points)?
Thanks.
On Mon, Oct 28, 2013 at 9:45 PM, Luca Martini <lm...@cisco.com> wrote:
> Lahiru,
>
> One more thing we need to have a way to defines dependencies between
> VM/processes.
> For example: Ae have a VM-A that depends on a VM-B with a rule of 10
> VM-A for each VM-B. The autoscaler needs to have a rule to handle
> scaling a VM-A, which might result in a second request to autoscale VM-B.
>
>
> Thanks.
> Luca
>
> On 10/25/2013 09:08 PM, Lahiru Sandaruwan 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 <imesh@apache.org
> > <ma...@apache.org>> 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: lahirus@wso2.com <ma...@wso2.com> 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
> >
>
>
--
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com 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
Re: Apache Stratos (incubating) 4.0.0-M1 Status
Posted by Luca Martini <lm...@cisco.com>.
Lahiru,
One more thing we need to have a way to defines dependencies between
VM/processes.
For example: Ae have a VM-A that depends on a VM-B with a rule of 10
VM-A for each VM-B. The autoscaler needs to have a rule to handle
scaling a VM-A, which might result in a second request to autoscale VM-B.
Thanks.
Luca
On 10/25/2013 09:08 PM, Lahiru Sandaruwan 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 <imesh@apache.org
> <ma...@apache.org>> 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: lahirus@wso2.com <ma...@wso2.com> 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
>
Re: Apache Stratos (incubating) 4.0.0-M1 Status
Posted by Lahiru Sandaruwan <la...@wso2.com>.
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 <im...@apache.org> 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: lahirus@wso2.com 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