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 B818711CEC for ; Sat, 26 Apr 2014 10:22:18 +0000 (UTC) Received: (qmail 54406 invoked by uid 500); 26 Apr 2014 10:22:17 -0000 Delivered-To: apmail-stratos-dev-archive@stratos.apache.org Received: (qmail 54191 invoked by uid 500); 26 Apr 2014 10:22:13 -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 54184 invoked by uid 99); 26 Apr 2014 10:22:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Apr 2014 10:22:12 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of isuruh@wso2.com designates 209.85.217.170 as permitted sender) Received: from [209.85.217.170] (HELO mail-lb0-f170.google.com) (209.85.217.170) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Apr 2014 10:22:08 +0000 Received: by mail-lb0-f170.google.com with SMTP id s7so3839118lbd.1 for ; Sat, 26 Apr 2014 03:21:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wso2.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=H0C1DCPNwTlFzBuzxO7rDunO1RQlp+Hjbv6ey4C9t9Q=; b=AaFDeHD5l8J5JnjFSfc8YX4ThF+3kokF5OWoacVHpU8esECrW87OhChOo53gIUJ8mH TVbwU1Z1wkilwZ4yPZrjQkgpK/3R0nXgxglZe5E5qPmiFdTkmuFEQmvMckG2yKKcstP3 4m380pCi1i6OWsoR7q4Ib8o0Es3xz4lQ3tjFc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=H0C1DCPNwTlFzBuzxO7rDunO1RQlp+Hjbv6ey4C9t9Q=; b=FpZDulneeHUeKSdsshgLFVO1dsoxdkyb7ke3oaCZSeRifLnNlfAp8PM4NZbhuxjucd p7EE2kq+w81fGE9elaVxBObmH67a7UekJgBO3KGUYLbtqmBlL+v/wgGauqCJ5NE+0f75 PpuwAXdOp7/6LCMT7Wefptlv5ohEcUbEIqr1ybUOLJ2Zm/1QMvKubSbE3N0l1Zf1Kx0K MHV1Az6jddGViJ4ru6wL5oI+nKuy3Npxkc+nu2BePlCijFI/Z24rveHPFivao/CEWOBG AT4qoYHqZPO0MHTJp0rvdI1GVZwc5xmoPLaDCDiokWMohywCfC7pcHt2K+Zmq5GR0NX8 vN7w== X-Gm-Message-State: ALoCoQl5W8eIiDQaRDL8krGuG+mJS7yjJnLIALjmY0et++diMv69XUOM3Xk9swh+QvE7lOiAAJWG MIME-Version: 1.0 X-Received: by 10.112.135.106 with SMTP id pr10mr9151230lbb.24.1398507706028; Sat, 26 Apr 2014 03:21:46 -0700 (PDT) Received: by 10.112.135.162 with HTTP; Sat, 26 Apr 2014 03:21:45 -0700 (PDT) In-Reply-To: <535ADA24.1050706@cisco.com> References: <535A9044.1000209@cisco.com> <535ADA24.1050706@cisco.com> Date: Sat, 26 Apr 2014 15:51:45 +0530 Message-ID: Subject: Re: Cartridge Events Diagram From: Isuru Haththotuwa To: "dev@stratos.incubator.apache.org" Content-Type: multipart/alternative; boundary=089e012292f808a60904f7ef7306 X-Virus-Checked: Checked by ClamAV on apache.org --089e012292f808a60904f7ef7306 Content-Type: text/plain; charset=UTF-8 On Sat, Apr 26, 2014 at 3:26 AM, Vanson Lim wrote: > On 4/25/14, 1:23 PM, Isuru Haththotuwa wrote: > >> Hi Vanson, >> >> On Fri, Apr 25, 2014 at 10:11 PM, Vanson Lim wrote: >> >> I had a question after looking at the revised diagram. >>> >>> Between the events "publish instance started event to Cloud Controller" >>> ->"start servers" >>> >>> Is the git repo pulled down and available to use to derive config used to >>> start server? This could be useful for delivering configuration using >>> the >>> ADC that is used to configure the server before starting it. This is a >>> little bit different from the model I've seen where artifacts are hot >>> deployed into servers after it starts. >>> >>> The ADC artifacts could be used during the start server event to >>> >>> 1) provide config for bootstrapping the install ou f the server binaries >>> >>> 2) Post install configure to complete server setup >>> 3) deploying server run time config, like application policies >>> >>> Interesting thought. >>> >> Currently, the server startup configuration is provided through an >> instance >> acting as a Puppet Master [1], at the time of instance start up. The git >> repository is used to synchronize application artifacts (a php application >> in case of a php instance, etc.) across a cluster. A user can upload the >> artifacts to the git repository, configure a git hook so that artifacts >> are >> updated on the fly, across the cluster [2]. >> > > So in some cases where installing puppet into the cartridge is not > practical or used, a cartridge should rely on its own artifact fetching > mechanism for package config as the current "application artifact > synchronization" mechanism as implemented can't be used for server > bootstrapping and post install config. > > Just wanted to point out that moving the code that perform a git pull > before the start server phase, preserves the ability to perform application > artifact deployment but would also allow the artifact repository to be also > used for other types of artifacts distribution. > Good thought Vanson. This is a way of using the same git repository to sync initial server configs as well as application artifacts. However, Puppet/Chef are specifically designed to cater the problem of getting initial configs/artifacts and periodic updates from a single place, and are widely used in large deployments. Maybe we can use a git repository for simpler scenarios. WDYT? > > Thanks, > > -Vanson > >> [1]. >> https://cwiki.apache.org/confluence/display/STRATOS/4. >> 0.0+Configuring+Puppet+Master >> >> [2]. >> https://cwiki.apache.org/confluence/display/STRATOS/4. >> 0.0+Automated+Deployment+Synchronization >> >> -Vanson >>> >>> >>> >>> >>> >>> On 4/24/14, 4:58 AM, Praneesha Chandrasiri wrote: >>> >>> Did a correction in adding the recursion for "publish stats to CEP". >>> >>> Please find the revised diagram attached. >>> >>> >>> On Thu, Apr 24, 2014 at 2:04 PM, Praneesha Chandrasiri< >>> praneesha@wso2.com> wrote: >>> >>> >>> >>> Hi Rekha, >>> >>> Thanks for reviewing. >>> >>> Attached is the revised diagram with the changes included as discussed. >>> >>> >>> On Thu, Apr 24, 2014 at 10:32 AM, Reka Thirunavukkarasu >>> wrote: >>> >>> >>> >>> Hi >>> >>> I have gone through it..It needs few modification as following after the >>> Member started Event to Instance Status topic. >>> >>> Member Started Event --> start servers --> wait for port Active --> >>> publish instance activated event >>> | >>> | >>> --> artifact updated event >>> --> start health checker >>> >>> Thanks, >>> Reka >>> >>> >>> On Thu, Apr 24, 2014 at 9:57 AM, Mariangela Hills >>> wrote: >>> >>> >>> >>> Thanks, Praneesha! >>> >>> Can someone please let us know whether this diagram is ok. >>> >>> Regards, >>> Mariangela >>> >>> >>> >>> >>> *--* >>> Mariangela Hills >>> Senior Technical Writer >>> >>> *WSO2, Inc.*lean.enterprise.middleware. >>> m: +94 773 500185 >>> w: http://wso2.com >>> >>> >>> >>> >>> >>> On Thu, Apr 24, 2014 at 9:02 AM, Praneesha Chandrasiri < >>> praneesha@wso2.com> wrote: >>> >>> >>> Hi Mari, >>> >>> Please find the $subject attached. >>> >>> Also please let me know if any improvements are required. >>> >>> -- >>> Thanks & Best Regards, >>> *Praneesha Chandrasiri* >>> *Technical Writer* >>> *WSO2 Inc. * >>> *Mobile: +(94) 718156888 <%2B%2894%29%20718156888>* >>> *E-mail: praneesha@wso2.com * >>> >>> >>> >>> >>> -- >>> Reka Thirunavukkarasu >>> Software Engineer, >>> WSO2, Inc.:http://wso2.com, >>> Mobile: +94776442007 >>> >>> >>> -- >>> Thanks & Best Regards, >>> *Praneesha Chandrasiri* >>> *Technical Writer* >>> *WSO2 Inc. * >>> *Mobile: +(94) 718156888 <%2B%2894%29%20718156888>* >>> *E-mail: praneesha@wso2.com * >>> >>> >>> >>> >>> >>> > -- Thanks and Regards, Isuru H. +94 716 358 048* * --089e012292f808a60904f7ef7306 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Sat, Apr 26, 2014 at 3:2= 6 AM, Vanson Lim <vlim@cisco.com> wrote:
On 4/25/14, 1:23 PM, Isuru Haththotuwa wrote:
Hi Vanson,

On Fri, Apr 25, 2014 at 10:11 PM, Vanson Lim <vlim@cisco.com> wrote:

=C2=A0 I had a question after looking at the revised diagram.

Between the events =C2=A0 "publish instance started event to Cloud Con= troller"
->"start servers"

Is the git repo pulled down and available to use to derive config used to start server? =C2=A0This could be useful for delivering configuration using= the
ADC that is used to configure the server before starting it. =C2=A0This is = a
little bit different from the model I've seen where artifacts are hot deployed into servers after it starts.

The ADC artifacts could be used during the start server event to

1) provide config for bootstrapping the install ou f the server binaries
2) Post install configure to complete server setup
3) deploying server run time config, =C2=A0like application policies

Interesting thought.
Currently, the server startup configuration is provided through an instance=
acting as a Puppet Master [1], at the time of instance start up. The git repository is used to synchronize application artifacts (a php application<= br> in case of a php instance, etc.) across a cluster. A user can upload the artifacts to the git repository, configure a git hook so that artifacts are=
updated on the fly, across the cluster [2].

So in some cases where installing puppet into the cartridge is not practica= l or used, a cartridge should rely on its own artifact fetching mechanism f= or package config as the current "application artifact synchronization= " mechanism as implemented can't be used for server bootstrapping = and post install config.

Just wanted to point out that moving the code that perform a git pull befor= e the start server phase, preserves the ability to perform application arti= fact deployment but would also allow the artifact repository to be also use= d for other types of artifacts distribution.

Good thought Vanson. This is a way of usin= g the same git repository to sync initial server configs as well as applica= tion artifacts. However, Puppet/Chef are specifically designed to cater the= problem of getting initial configs/artifacts and periodic updates from a s= ingle place, and are widely used in large deployments. Maybe we can use a g= it repository for simpler scenarios. WDYT?

Thanks,

-Vanson
[1].
https://cwiki.apache.org/conf= luence/display/STRATOS/4.0.0+Configuring+Puppet+Master

[2].
https://cwiki.apache.org/= confluence/display/STRATOS/4.0.0+Automated+Deployment+= Synchronization

-Vanson





On 4/24/14, 4:58 AM, Praneesha Chandrasiri wrote:

Did a correction in adding the recursion for "publish stats to CEP&quo= t;.

Please find the revised diagram attached.


On Thu, Apr 24, 2014 at 2:04 PM, Praneesha Chandrasiri<praneesha@wso2.com> &l= t;praneesha@wso2.co= m>wrote:



=C2=A0 Hi Rekha,

Thanks for reviewing.

Attached is the revised diagram with the changes included as discussed.


On Thu, Apr 24, 2014 at 10:32 AM, Reka Thirunavukkarasu <reka@wso2.com> <reka@wso2.com>wrote:



=C2=A0 Hi

I have gone through it..It needs few modification as following after the Member started Event to Instance Status topic.

=C2=A0 Member Started Event --> start servers --> wait for port Activ= e -->
publish instance activated event
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0--> artifact = updated event
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0--> start health checker

Thanks,
Reka


On Thu, Apr 24, 2014 at 9:57 AM, Mariangela Hills <mariangela@wso2.com> <mariangela@wso2.com&g= t;wrote:



=C2=A0 Thanks, Praneesha!

Can someone please let us know whether this diagram is ok.

Regards,
Mariangela




*--*
Mariangela Hills
Senior Technical Writer

*WSO2, Inc.*lean.enterprise.middleware.
m: +94 773 500185
w: http://wso2.com
=C2=A0 <http://wso= 2.com/events/> <http://wso2.com/events/>




On Thu, Apr 24, 2014 at 9:02 AM, Praneesha Chandrasiri <praneesha@wso2.com> wrote:

=C2=A0 Hi Mari,

Please find the $subject attached.

Also please let me know if any improvements are required.

--
Thanks & Best Regards,
*Praneesha Chandrasiri*
*Technical Writer*
=C2=A0 *WSO2 Inc. *
*Mobile: +(94) 718156888 <%2B%2894%29%20718156888>*
*E-mail: praneesha@= wso2.com <pr= aneesha@wso2.com> <praneesha@wso2.com>*




=C2=A0 =C2=A0--
Reka Thirunavukkarasu
Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007


=C2=A0 --
Thanks & Best Regards,
*Praneesha Chandrasiri*
*Technical Writer*
*WSO2 Inc. *
*Mobile: +(94) 718156888 <%2B%2894%29%20718156888>*
*E-mail: praneesha@= wso2.com <pr= aneesha@wso2.com> <praneesha@wso2.com>*









--
T= hanks and Regards,

Isuru H.
+94 716 358 048

--089e012292f808a60904f7ef7306--