Hi Martin, On Fri, Aug 7, 2015 at 10:53 PM, Martin Eppel (meppel) <mep...@cisco.com> wrote:
> Hi, > > > > I have the following use case: > > > > I have a group with cartridges A,B and C and a group policy: min/max =1, 2 > (compute hosts - “partition1”, “partition2”), algorithm: round robin. > > > > My expectation would be as follows: > > > > When the group instance spins up, all cartridge instances are placed on > the same compute host (first partition - “partition1”). > > > > During runtime, I increase the groupMin/Max = 2 which will force stratos > to spin up a second group instance. > > > > My expectations would be that the all the cartridge instances of the 2nd > group instance will be placed on the 2nd partition (“partition2”). > > > > Is this correct ? > Yah..This is correct. According to the Round robin nature, autoscaler will choose partition2 for the 2nd group instance. > What will happen if one of the instances will go unhealthy and > auto-healed, where will it be placed ? > If the auto-healed happened, in order to select the partition for the replacement group instance, we scan through all the partitions again and find out the partition which has lowest instance count and we choose that partition for the replacement group instance. Our algorithm first normalize all the partitions to have equal number of instances, then choose the partition according to round robin manner. > > > If the expectations are not as described above, how can I configure > stratos to behave according the expectations ? > I believe you can achieve your requirement with the scenario that explained above. Please let us know, if you come across with any issues. Thanks, Reka > > > Thanks > > > > Martin > -- Reka Thirunavukkarasu Senior Software Engineer, WSO2, Inc.:http://wso2.com, Mobile: +94776442007
