Interface AllocationPolicy.PlacementPolicyOrBuilder

All Superinterfaces:
com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder
All Known Implementing Classes:
AllocationPolicy.PlacementPolicy, AllocationPolicy.PlacementPolicy.Builder
Enclosing class:
AllocationPolicy

public static interface AllocationPolicy.PlacementPolicyOrBuilder extends com.google.protobuf.MessageOrBuilder
  • Method Summary

    Modifier and Type
    Method
    Description
    UNSPECIFIED vs.
    com.google.protobuf.ByteString
    UNSPECIFIED vs.
    long
    When specified, causes the job to fail if more than max_distance logical switches are required between VMs.

    Methods inherited from interface com.google.protobuf.MessageLiteOrBuilder

    isInitialized

    Methods inherited from interface com.google.protobuf.MessageOrBuilder

    findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
  • Method Details

    • getCollocation

      String getCollocation()
       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.
       
      string collocation = 1;
      Returns:
      The collocation.
    • getCollocationBytes

      com.google.protobuf.ByteString getCollocationBytes()
       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.
       
      string collocation = 1;
      Returns:
      The bytes for collocation.
    • getMaxDistance

      long getMaxDistance()
       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
       
      int64 max_distance = 2;
      Returns:
      The maxDistance.