Return-Path: X-Original-To: apmail-stratos-dev-archive@minotaur.apache.org Delivered-To: apmail-stratos-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BBEBB103E5 for ; Sun, 27 Oct 2013 06:49:04 +0000 (UTC) Received: (qmail 11313 invoked by uid 500); 27 Oct 2013 06:48:57 -0000 Delivered-To: apmail-stratos-dev-archive@stratos.apache.org Received: (qmail 11238 invoked by uid 500); 27 Oct 2013 06:48:56 -0000 Mailing-List: contact dev-help@stratos.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stratos.incubator.apache.org Delivered-To: mailing list dev@stratos.incubator.apache.org Received: (qmail 11227 invoked by uid 99); 27 Oct 2013 06:48:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Oct 2013 06:48:53 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of nirmal070125@gmail.com designates 209.85.223.174 as permitted sender) Received: from [209.85.223.174] (HELO mail-ie0-f174.google.com) (209.85.223.174) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Oct 2013 06:48:49 +0000 Received: by mail-ie0-f174.google.com with SMTP id qd12so8992607ieb.19 for ; Sat, 26 Oct 2013 23:48:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=xsLaCbT09g9ViuwkeBQqI8di5rbRmZJIwfIP/scIOpA=; b=lC9nfq8ohACtMlHj7IztVNnuBKIs+dTqDLZSxlMLQFTgZ4nnTFFsglqJek4QCI/xZZ HYDgIojlwsrS0BHfGd0ROkIiGQhopJtq/Pq3EmrR9uxsDKvG+zFqEnemM6njZI4vDWYa 4aSSGQl4YouBmRqpURDLxXI4V+vnEdbfsuQj92QZjIIp1fQFbu5W29noPTsiTdHk4rr7 2KSLoLdEyOo4HDIUPtQqiqJnP//H800q+rwoJJ26odvyS6WcxjoEqegl8K3yFwAPzj5s HIU3gNshMLVq63HfyHH0kpdvLi4DVl6r3nuLMIt9oOHCxgo7Px26Ma+xB5pqk2H+0h2z jHTA== MIME-Version: 1.0 X-Received: by 10.43.172.4 with SMTP id nw4mr10028170icc.25.1382856508777; Sat, 26 Oct 2013 23:48:28 -0700 (PDT) Received: by 10.64.63.195 with HTTP; Sat, 26 Oct 2013 23:48:28 -0700 (PDT) In-Reply-To: References: Date: Sun, 27 Oct 2013 12:18:28 +0530 Message-ID: Subject: Re: Apache Stratos (incubating) 4.0.0-M1 Status From: Nirmal Fernando To: dev@stratos.incubator.apache.org Content-Type: multipart/alternative; boundary=001a11c2fe3cfb309104e9b35e20 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2fe3cfb309104e9b35e20 Content-Type: text/plain; charset=ISO-8859-1 On Sat, Oct 26, 2013 at 4:15 PM, Imesh Gunaratne 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 wrote: > >> >> On Oct 26, 2013 12:16 PM, "Imesh Gunaratne" 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 >> 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 >> 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/ --001a11c2fe3cfb309104e9b35e20 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Sat, Oct 26, 2013 at 4:15 PM, Imesh Gunaratne = <imesh@apache.org<= /a>> wrote:
Yes my mistake, it should b= e 4.0.0-SNAPSHOT.
I have now changed the version to 4.0.0-SNAPSHOT in t= runk (not pushed) and performing a clean repo build to identify the issues.=

Nirmal: Will you be able to setup CEP in the EC2 instan= ce 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 oth= er work these days. But let's synch up and do, I'll help if you got= issues.


Thanks


On Sat, Oc= t 26, 2013 at 2:45 PM, Nirmal Fernando <nirmal070125@gmail.com>= ; wrote:


On Oct 26, 2013 12:16 PM, "Imesh Gunaratne" <imesh@apache.org> wrote:
>
> Correction:=A0Please 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 <lahirus@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 controll= er when the subscription happens
>> It process the request using rules engine(drools) and calls the Cl= oud 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> 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 Ex= tension. 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.=A0
>>>
>>> Work Flow Items Done:
>>> - All modules are now communicating properly via the message b= roker.
>>> - Cartridge definitions get deployed properly.
>>> - Stratos Controller is working as expected. A tenant user cou= ld subscribe to a cartridge using this.
>>> - Cartridge Agent is properly publishing instance status event= s to the message broker.
>>> - Cloud Controller is properly publishing topology events to t= he 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 u= pdate the payload.zip.
>>> - Auto-Scaler is not spinning up instances since Real-time Eve= nt 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://ws= o2.com
>> lean.enterprise.middleware
>>
>> email: lahir= us@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.

--001a11c2fe3cfb309104e9b35e20--