Hi, +1 for not the defined order of the groups.
On Mon, Nov 18, 2013 at 2:23 AM, Udara Liyanage <[email protected]> wrote: > Hi All, > > The content of the above document is not shared. Sorry about the > inconvenience. I will paste a sample deployment policy inline. > > <deploymentPolicy id =”economyPolicy”> > > <partitionGroups> > > <partitionGroup id=”group1” > > > <partitionAlgo>OneAfterAnother</partitionAlgo> > > <partition id="partition1" > > > <max>3</max> > > <min>1</min> > > </partition> > > <partition id="partition2" > > > <max>5</max> > > <min>1</min> > > </partition> > > </partitionGroup> > > <partitionGroup id=”group2” > > > <partitionAlgo>RoundRobin</partitionAlgo> > > <partition id="partition4" > > > <max>3</max> > > <min>1</min> > > </partition> > > <partition id="partition5" > > > <max>5</max> > > <min>1</min> > > </partition> > > </partitionGroup> > > </partitionGroups> > </deploymentPolicy> > > > On Mon, Nov 18, 2013 at 2:14 AM, Lahiru Sandaruwan <[email protected]>wrote: > >> Hi Udara, >> >> Please find my comments inline. >> >> >> On Mon, Nov 18, 2013 at 12:28 PM, Udara Liyanage <[email protected]> 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. >>> >>> <partitionGroups> >>> <partitionGroup id=”group1” > >>> <partitionGroup id=”group2” > >>> >>> <partitionGroups> >>> >>> We define the partition algorithm for each partition 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 order of the >>> partition groups. Do we specify an algorithm for partition group order or >>> 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/1tEexlFLalOATHxHvtnRgUfosuQY_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: [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 >> >> > > > -- > Udara Liyanage > Software Engineer > WSO2, Inc.: http://wso2.com > lean. enterprise. middleware > > web: http://udaraliyanage.wordpress.com > phone: +94 71 443 6897 > -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897
