BlockModelRMO::Move Allocation

Deletes allocations that exist between consumers in the consumerTargetSet and resources in the resourceSourceSet and creates corresponding allocations for resources in the resourceDestinationSet. Used by Microsoft. Provisioning Framework (MPF).

XML Input Schema

The following code fragment shows the format for sending data to this procedure. For more information on individual elements and attributes, see the Elements and Attributes table.

<executeData>1..1
  <allocation>1..1
	<resourceSourceSet>1..1</resourceSourceSet>
	<consumerTargetSet>1..1</consumerTargetSet>
	<resourceDestinationSet>1..1</resourceDestinationSet>
	<useFillRatio>0..1</useFillRatio>
  </allocation>
</executeData>

XML Output Schema

Move Allocation does not return data.

Elements and Attributes

The following table describes the XML schema elements and attributes. Unless otherwise indicated, the data type is string.

Element Description, relationships, and attributes
allocation Description:
 Encapsulates data required to describe an allocation.

Parent:
executeData

Children:
consumerTargetSet (minOccurs="1" maxOccurs="1")
resourceDestinationSet (minOccurs="1" maxOccurs="1")
resourceSourceSet (minOccurs="1" maxOccurs="1")
consumerTargetSet Description:
 Set of consumers with allocations to move.

Parent:
allocation

executeData Description:
 Encapsulates the procedure's input data.

Child:
allocation (minOccurs="1" maxOccurs="1")
resourceSourceSet Description:
 Set of resources for which consumers have allocations to move.

Parent:
allocation

resourceDestinationSet Description:
 Set of resources for which to create the new allocations.

Parent:
allocation

useFillRatio Description:
Indicates whether moved resources keep their existing values for virtual and actual allocations (false) or recalculate the actual allocation from the virtual allocation (true).

Parent:
allocation

Example

<request>
  <data/>
  <procedure>  
	<execute procedure="Add Resource to Candidates" namespace="CoreRMO"> 
	<executeData>
		<candidates>
		<targetSet>OldServerSet</targetSet>
		</candidates>
		<resourceInstance>
		<instanceName>iis-1</instanceName>
		<instanceLocation>Lab A, Building B</instanceLocation>
		<typeName>IISServer</typeName>
		</resourceInstance>
	</executeData>
	</execute>
	<execute procedure="Add Resource to Candidates" namespace="CoreRMO"> 
	<executeData>
		<candidates>
		<targetSet>NewServerSet</targetSet>
		<!-- Need to provide a rank before moving allocation to this resource. -->
		<rank>1</rank> 
		</candidates>
		<resourceInstance>
		<instanceName>iis-2</instanceName>
		<instanceLocation>Lab A, Building B</instanceLocation>
		<typeName>IISServer</typeName>
		</resourceInstance>
	</executeData>
	</execute>
	<execute procedure="Add Consumer to Candidates" namespace="CoreRMO"> 
	<executeData>
		<candidates>
		<targetSet>siteSet</targetSet>
		</candidates>
		<consumerInstance>
		<instanceName>tailspintoys.com</instanceName>
		<typeName>Website</typeName>
		</consumerInstance>
	</executeData>
	</execute>
	<execute procedure="Move Allocation" namespace="BlockModelRMO"> 
	<executeData>
		<allocation>
		<resourceSourceSet>OldServerSet</resourceSourceSet>
		<resourceDestinationSet>NewServerSet</resourceDestinationSet>
		<consumerTargetSet>siteSet</consumerTargetSet>
		</allocation>
	</executeData>
	</execute>
  </procedure>
</request>

Remarks

The process of recreating the allocations uses the same algorithm as Allocate except that it ignores the fill ratio on target resources.

This function will fail if there are insufficient ranked resources in the resource destination set to accommodate all the allocations being moved.

See Also

Allocate, BlockModelRMO Provider, Delete Allocation, Resource Manager, Update Allocation

Up Top of Page
) 1999-2002 Microsoft Corporation. All rights reserved.