Page History

...

-          New String Parameter added:  deploymentPlanner

Wiki Markup                       Possible list of values: {FirstFitPlanner (default), UserDispersingPlanner}

-          ServiceOfferingResponse:  deploymentPlanner

...

-          Create ServiceOffering should include a field with tag ‘Deployment Planner to use’unmigrated-wiki-markup

\-          Value should be a drop down list that currently has {FirstFitPlanner (default), UserDispersingPlanner}

-          By default, value should be ‘FirstFitPlanner‘

...

Then this is how we choose the resources:

...

• List Pods in order of available aggregate capacity. Say list is: {P2, P1}unmigrated-wiki-markup
• Get number of VMs of this account for each pod and list in ascending order. Say it is: {P1 (1 Vms), P2 (2 Vms)}
• Choose the pods in this order. So P1 first and then P2.unmigrated-wiki-markup
• Within each pod list clusters based on aggregate capacity. Say for P1: {C2}unmigrated-wiki-markup
• List by number of VMs for this account per cluster in ascending order. Say: {C1(0 Vms), C2(1 Vms)}
• We cannot choose cluster C1 now, since it has no capacity. So choose clusters in this order but having capacity.
• Finally from C2, choose a host with less number of VMs for this account and a pool with less number of volumes for this account.

...

Wiki Markup                Then reorder the list by total weight. The final ordered list will be: {C2, C3, C1}