Batch v1 API - Class AllocationPolicy.Types.PlacementPolicy (2.11.0)

Version 2.11.0

• 2.12.0 (latest)
• 2.11.0
• 2.10.0
• 2.9.0
• 2.8.0
• 2.7.0
• 2.6.0
• 2.5.0
• 2.4.0
• 2.3.0
• 2.2.0
• 2.1.0
• 2.0.0
• 1.3.0
• 1.2.0
• 1.1.0
• 1.0.0

public sealed class AllocationPolicy.Types.PlacementPolicy : IMessage<AllocationPolicy.Types.PlacementPolicy>, IEquatable<AllocationPolicy.Types.PlacementPolicy>, IDeepCloneable<AllocationPolicy.Types.PlacementPolicy>, IBufferMessage, IMessage

Reference documentation and code samples for the Batch v1 API class AllocationPolicy.Types.PlacementPolicy.

PlacementPolicy describes a group placement policy for the VMs controlled by this AllocationPolicy.

Inheritance

object > AllocationPolicy.Types.PlacementPolicy

Implements

IMessageAllocationPolicyTypesPlacementPolicy, IEquatableAllocationPolicyTypesPlacementPolicy, IDeepCloneableAllocationPolicyTypesPlacementPolicy, IBufferMessage, IMessage

Inherited Members

object.GetHashCode()

object.GetType()

object.ToString()

Namespace

Google.Cloud.Batch.V1

Assembly

Google.Cloud.Batch.V1.dll

Constructors

PlacementPolicy()

public PlacementPolicy()

PlacementPolicy(PlacementPolicy)

public PlacementPolicy(AllocationPolicy.Types.PlacementPolicy other)

Parameter
Name	Description
other	AllocationPolicyTypesPlacementPolicy

Properties

Collocation

public string Collocation { get; set; }

UNSPECIFIED vs. COLLOCATED (default UNSPECIFIED). Use COLLOCATED when you want VMs to be located close to each other for low network latency between the VMs. No placement policy will be generated when collocation is UNSPECIFIED.

Property Value
Type	Description
string

MaxDistance

public long MaxDistance { get; set; }

When specified, causes the job to fail if more than max_distance logical switches are required between VMs. Batch uses the most compact possible placement of VMs even when max_distance is not specified. An explicit max_distance makes that level of compactness a strict requirement. Not yet implemented

Property Value
Type	Description
long