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 84E29102F4 for ; Mon, 18 Nov 2013 07:24:16 +0000 (UTC) Received: (qmail 56988 invoked by uid 500); 18 Nov 2013 07:24:14 -0000 Delivered-To: apmail-stratos-dev-archive@stratos.apache.org Received: (qmail 56808 invoked by uid 500); 18 Nov 2013 07:24:12 -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 56795 invoked by uid 99); 18 Nov 2013 07:24:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Nov 2013 07:24:11 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of udara@wso2.com designates 209.85.192.172 as permitted sender) Received: from [209.85.192.172] (HELO mail-pd0-f172.google.com) (209.85.192.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Nov 2013 07:24:06 +0000 Received: by mail-pd0-f172.google.com with SMTP id g10so1842319pdj.17 for ; Sun, 17 Nov 2013 23:23:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wso2.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=wM5nnWTOVFvSbgXZao5tpb/Q/TyIscAbnA2R3IjK2Jw=; b=gUEtQcW/V6UbaP4TF+zd7kkTiHSYvEixkBFfOYHLFqqgwm4vMib17PypD4sCDvWZpg IybtAlpomoBPISZXfR7vwTycabyCiLYUVge2ws5rsGYYKh0YjQQWtMXXQg3Wrjw/wgky SBi/8QPalS/+kfvRZj2B+03do4fgSIxoLf9uc= 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:from:date :message-id:subject:to:content-type; bh=wM5nnWTOVFvSbgXZao5tpb/Q/TyIscAbnA2R3IjK2Jw=; b=TfQ8EoKNW9mVChqhGYfYYVfzq10c68q5CpNfb3quNJRprkGKxhiXxrU8rwp5zGQsfY /7XS0cxHbGaqMBqEJsva7cMB10U5/GCX9CCoU5EezWxC++WOaUj5sRRHo+wP6qFXNvIq MHeFjONEzO+oVQZJnZpOWZKPZX2wFdEeCvfibiwkpyKMDxBs9afl3xioGp8nzszK1fzu jHNBEiA2HK8LnIXnToRYdTd+W92Jpo2RIcEfGH4L9aSVKQjevUJ0msWaSUIRDK+I8i/n ktRNnugQW08H3Dvhr0rGu2llwwdfEPpdizV7hMo7KBBmMR2V1L5BonxxadRH7YIsCy/y S/ZA== X-Gm-Message-State: ALoCoQm2eSlX2mZkQLvr6QcO733qtug8nRK2psTdjs+9JQ6F4Dbm+sgcrjAybKLS09IWo3lZJkG5 X-Received: by 10.68.225.232 with SMTP id rn8mr19388744pbc.32.1384759424723; Sun, 17 Nov 2013 23:23:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.70.83.8 with HTTP; Sun, 17 Nov 2013 23:23:24 -0800 (PST) In-Reply-To: References: From: Udara Liyanage Date: Mon, 18 Nov 2013 02:23:24 -0500 Message-ID: Subject: Re: Define Order of the partition groups To: dev@stratos.incubator.apache.org Content-Type: multipart/alternative; boundary=047d7b2ee2839c340904eb6e6dfc X-Virus-Checked: Checked by ClamAV on apache.org --047d7b2ee2839c340904eb6e6dfc Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi All, The content of the above document is not shared. Sorry about the inconvenience. I will paste a sample deployment policy inline. OneAfterAnother 3 1 5 1 RoundRobin 3 1 5 1 On Mon, Nov 18, 2013 at 2:14 AM, Lahiru Sandaruwan wrote= : > Hi Udara, > > Please find my comments inline. > > > On Mon, Nov 18, 2013 at 12:28 PM, Udara Liyanage wrote: > >> Hi, >> >> As described in [1] we can specify partitions groups in the deployment >> policy. The deployment policy has multiple partition groups and each >> partition group has multiple partitions. >> >> >> >> >> >> >> >> We define the partition algorithm for each partition group which >> specifies the order of instance spawning. That is clear. My concern is w= hen >> there are multiple partition groups, how do we define the order of the >> partition groups. Do we specify an algorithm for partition group order o= r >> go one after the other (the order partition groups are defined in the >> policy) ? >> > > Idea of the partition groups is to give the user(may be dev-op) the > flexibility of changing algorithms among partition sets. > > So here we can simply have a fixed algorithm "One after Another" among > partition groups. We can get the order which defined in deployment policy > itself as the order. > > IMO this flexibility is enough and we do not need to complicate this > defining an algorithm for groups. > > Thanks > >> >> Appreciate your ideas. >> >> [1] >> https://docs.google.com/a/wso2.com/document/d/1tEexlFLalOATHxHvtnRgUfosu= QY_9UDiV4q--SQLfhU/edit >> >> -- >> Udara Liyanage >> Software Engineer >> WSO2, Inc.: http://wso2.com >> lean. enterprise. middleware >> >> web: http://udaraliyanage.wordpress.com >> phone: +94 71 443 6897 >> > > > > -- > -- > 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 > > --=20 Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 --047d7b2ee2839c340904eb6e6dfc Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Hi All,

The content of the above docume= nt is not shared. Sorry about the inconvenience. I will paste a sample depl= oyment policy inline.

<deploymentPolicy id =3D=94economyPolicy=94>

= <partitionGroups>

= <partitionGroup id=3D=94gr= oup1=94 >

= <partitionAlgo>OneAfterAnother</partitionAlg= o>

<partitio= n id=3D"partition1" >

<max>3</max>

<min>1</min>

</partiti= on>

<partitio= n id=3D"partition2" >

<max>5</max>

<min>1</min>

</partiti= on>

</partitionGroup>

<partitionGroup id=3D=94gr= oup2=94 >

= <partitionAlgo>RoundRobin</partitionAlgo>=

<partitio= n id=3D"partition4" >

<max>3</max>

<min>1</min>

</partiti= on>

<partitio= n id=3D"partition5" >

<max>5</max>

<min>1</min>

</partiti= on>

</partitionGroup>

</= partitionGroups>

</deploymentPolicy><= /span>


On Mon,= Nov 18, 2013 at 2:14 AM, Lahiru Sandaruwan <lahirus@wso2.com> wrote:
Hi Udara,

Please find my comments inline.


<= div class=3D"gmail_quote">
On Mon, Nov 18, 2013 at 12:28 PM, Udara Liyanage <udara@wso= 2.com> wrote:
Hi,

As d= escribed in [1] we can specify partitions groups in the deployment policy. = The deployment policy has multiple partition groups and each partition grou= p has multiple partitions.=A0

<partitionGroups>=

<partitionGroup id=3D=94group1=94 >=
<partitionGroup id=3D=94group2=94 >

<partitionGroups>
We define the partition algorithm for each partiti= on group which specifies the order of instance spawning. That is clear. My = concern is when there are multiple partition groups, how do we define the o= rder of the partition groups. Do we specify an algorithm for partition grou= p order or go one after the =A0other (the order partition groups are define= d in the policy) ?

Idea of the partition groups i= s to give the user(may be dev-op) the flexibility of changing algorithms am= ong partition sets.

So here we can simply have a f= ixed algorithm "One after Another" among partition groups. We can= get the order which defined in deployment policy itself as the order.

IMO this flexibility is enough and we do not need to co= mplicate this defining an algorithm for groups.

Th= anks

Appreciate your ideas.

[1]=A0<= a href=3D"https://docs.google.com/a/wso2.com/document/d/1tEexlFLalOATHxHvtn= RgUfosuQY_9UDiV4q--SQLfhU/edit" target=3D"_blank">https://docs.google.com/a= /wso2.com/document/d/1tEexlFLalOATHxHvtnRgUfosuQY_9UDiV4q--SQLfhU/edit<= span>

--
Udara Liyana= ge
Soft= ware Engineer
WSO2, In= c.:=A0http://wso2.com
le= an. enterprise. middleware

phone:=A0+94 71 443 6897



<= /div>--
--
La= hiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc= ., http://wso2.com
lean.enterprise.middleware

email: lahirus@wso2.com cell: (+94) 773 325 95= 4
blog: http:= //lahiruwrites.blogspot.com/
twitter: http://tw= itter.com/lahirus
linked-in: http://lk.linkedin.com/pub/l= ahiru-sandaruwan/16/153/146




--
--047d7b2ee2839c340904eb6e6dfc--