7=SrSSKJr SSKJr SSKJr SSKJr SSKJr SSKJ r SSKJ r SS K Jr SS KJr S rS rS rSSjrSrSrSrSrSrSSjrSrS SjrSrSrSrSr Sr!SSjr"g)!z1Flags for the compute resource-policies commands.)absolute_import)division)unicode_literals) arg_parsers)base) completers)flags) arg_utils) labels_utilcJ[R"SS[RS9$)Nzresource policyzcompute.resourcePolicies) resource_nameregional_collectionregion_explanation) compute_flagsResourceArgumentREGION_PROPERTY_EXPLANATIONAlib/googlecloudsdk/command_lib/compute/resource_policies/flags.pyMakeResourcePolicyArgrs&  ' '%4&BB DDrc$URSSSS9$)NzMaintenance configuration.Trequiredmutex)add_argument_groupparsers rAddMaintenanceParentGroupr%s#  " "#?,0)- # //rcPURS5nURS[SS9 g)Na  Concurrent Maintenance Controls Group. Defines a group config that, when attached to an instance, recognizes that instance as a part of a group of instances where only up the configured amount of instances in that group can undergo simultaneous maintenance. z--concurrency-limit-percenta  Defines the max percentage of instances in a concurrency group that go to maintenance simultaneously. Value must be greater or equal to 1 and less or equal to 100. Usage examples: `--concurrency-limit=1` sets to 1%. `--concurrency-limit=55` sets to 55%.typehelp)r add_argumentint) parent_groupconcurrent_groups rAddConcurrentControlGroupArgsr'+s7!446  =C&+ ,rc :URSUSS9nU(aUS- nURU(aSOS5n U RSS[RR US9 U RSSS 9n U RS R U5S S S R U5S9 U(aCU RSR U5SS[R"SS9SR U5S9 U(a[R"SR U5S/SQSR X1R55S9RU 5 URS5n U RSR U5S[R"5SR U5S9 g g )!z/Add Cycle Frequency args for Resource Policies.zCycle Frequency Group.Trzw Valid choices are 00:00, 04:00, 08:00, 12:00, 16:00 and 20:00 UTC. For example, `--start-time="08:00"`.zUsing command flags:z --start-timerr!r")rrz --daily-{} daily_cycle store_truez{} starts daily at START_TIME.)destactionr"z --hourly-{}HOURS hourly_cycle lower_boundz/{} occurs every n hours starting at START_TIME.)metavarr-r!r"z --weekly-{} weekly_cycle)mondaytuesday wednesdaythursdayfridaysaturdaysundayz,{} occurs weekly on WEEKLY_{} at START_TIME.)r-choiceshelp_strz Using a file:z--weekly-{}-from-fileweekly_cycle_from_filea A JSON/YAML file which specifies a weekly schedule. The file should contain the following fields: day: Day of the week with the same choices as `--weekly-{}`. startTime: Start time of the snapshot schedule with the same format as --start-time. For more information about using a file, see https://cloud.google.com/compute/docs/disks/scheduled-snapshots#create_snapshot_schedule )r-r!r"N) r add_groupr#rDatetime ParseUtcTimeformat BoundedIntrChoiceArgumentupper AddToParser FileContents) r flag_suffixstart_time_help cadence_helpsupports_hourlyhas_restricted_start_timessupports_weeklyr freq_groupfreq_flags_group cadence_groupfreq_file_groups rAddCycleFrequencyArgsrS<s(()?*EEO )) /R9t    , ,  #,,4$,G-+&   + 2 2< @ B [)   # # 2 > E E  [) '?FF ++-/ 0 1< M0J **?;O  &&{3 %  % % '   F; !!rc NURSS[R"SSS9SS9 g)Nz --max-percentzSets maximum percentage of instances in the group that can undergo simultaneous maintenance. If this flag is not specified default value of 1% will be set. Usage example: `--max-percent=10` sets to 10%.r1dr3 upper_bound)r"r!defaultr#rrDrs rAddMaxPercentArgrZ{s2   ! !aS Arc$URSSS9 g)Nz --descriptionz1An optional, textual description for the backend.r")r#rs r AddCommonArgsr]s >@rcPSSS.nURSSU[RSS9 g) z6Set arguments for workload-type for workload policies.zFor workloads that aim to be highly available. Common examples are web / ML serving, or distributed database clusters. Compute Engine spreads VMs at best-effort to improve reliability of the distributed infrastructure.zFor high throughput distributed workloads eg. HPC or ML training. Compute Engine collocates VMs at best-effort to reduce network latency between VMs.)HIGH_AVAILABILITYHIGH_THROUGHPUTz--typeTzJType of the workload policy defining the high-level intent of the cluster.)rr=r!r"N)r#r ChoiceToEnumName)rr=s rAddTypeArgsForWorkloadPolicyrbs? )  1 '   % %   rcUR5nURS[SS9 SSSS.nURSU[RS S 9 g ) zWSet arguments for max-topology-distance and accelerator-topology for workload policies.z--accelerator-topologyzSpecifies the topology of placement and interconnection performance required to create a slice of VMs with interconnected accelerators.r zVVMs are placed within the same cluster of capacity with improved latency between them.z[VMs are placed within the same block of capacity with improved latency compared to Cluster.zTightest collocation of VMs that provides minimized network latency. VMs are placed within the same rack of capacity with improved latency compared to Block.)CLUSTERBLOCKSUBBLOCKz--max-topology-distancezsSpecifies the topology of placement and interconnection network performance of the group of VMs (MIG / Multi-MIGs).)r=r!r"N)add_mutually_exclusive_groupr#strr ra)rgroupr=s rAAddMaxTopologyDistanceAndAcceleratorTopologyArgsForWorkloadPolicyrjso  - - /%  Q  # * 1 '  % % A rc`[R"SURRSSS.SSS9$)Nz--on-source-disk-delete)zkeep-auto-snapshotszcKeep automatically-created snapshots when the source disk is deleted. This is the default behavior.)zapply-retention-policyzjContinue to apply the retention window to automatically-created snapshots when the source disk is deleted.)KEEP_AUTO_SNAPSHOTSAPPLY_RETENTION_POLICYzORetention behavior of automatic snapshots in the event of source disk deletion.custom_mappingsrXr>)r ChoiceEnumMapper3ResourcePolicySnapshotSchedulePolicyRetentionPolicy!OnSourceDiskDeleteValueValuesEnum)messagess rGetOnSourceDiskDeleteFlagMapperrts@  # #BB(("8%<  rc$[U5 [X5 URS5n[U5 UR SSSS9 URSS9n[ R "US5 U(a UR S S [RS 9 g g ) z;Adds flags specific to snapshot schedule resource policies.zSnapshot propertiesz --guest-flushr,zbCreate an application consistent snapshot by informing the OS to prepare for the snapshot process.)r.r"T)rsnapshotz--snapshot-regionz'Region where the snapshot is scoped to.)r" completerN) AddSnapshotMaxRetentionDaysArgsAddOnSourceDiskDeleteArgsr@AddSnapshotLabelArgsr#rAddStorageLocationFlagcompute_completersRegionsCompleter)rrssupport_snapshot_regionsnapshot_properties_groupsnapshot_location_groups rAddSnapshotScheduleArgsrs!&)F-$../DE01((  /)0 6?? @&&'> K(( 6$55)rcURSSS9 URSSS9 URSSS9 URS[RRS S 9 URS [RRS S 9 g )z;Adds flags specific to instance schedule resource policies.z --timezonez Timezone used in interpreting schedule. The value of this field must be a time zone name from the tz database http://en.wikipedia.org/wiki/Tz_database r\z--vm-start-schedulezU Schedule for starting the instance, specified using standard CRON format. z--vm-stop-schedulezU Schedule for stopping the instance, specified using standard CRON format. z--initiation-datez` The start time of the schedule policy. The timestamp must be an RFC3339 valid string.r z --end-datezbThe expiration time of the schedule policy. The timestamp must be an RFC3339 valid string.N)r#rrAParsers rAddInstanceScheduleArgsrs            % % !     % % $rcLURSU[R"SS9SS9 g)zEAdds max retention days flag for snapshot schedule resource policies.z--max-retention-daysr1r2z0Maximum number of days snapshot can be retained.r*NrY)rrs rrxrxs,  ! !a 0 = ?rcL[U5RRU5 g)zEAdds onSourceDiskDelete flag for snapshot schedule resource policies.N)rt choice_argrG)rrss rryry's!(+66BB6JrcL[R"SSS9RU5 g)Nz(>??   # #q A H     rcSSS.nU[RR:XaURSS05 [R "SUR RUSSS 9$) z3Gets collocation flag mapper for resource policies.)zunspecified-collocationzmUnspecified network latency between VMs placed on the same availability domain. This is the default behavior.) collocatedzLLow network latency between more VMs placed on the same availability domain.)UNSPECIFIED_COLLOCATION COLLOCATED CLUSTERED) clusteredzJLowest network latency between VMs placed on the same availability domain.z --collocationNznCollocation specifies whether to place VMs inside the sameavailability domain on the same low-latency network.rn)rrrupdater rp"ResourcePolicyGroupPlacementPolicyCollocationValueValuesEnum)rsrros rrrZsw A ( / d%%% *  # #11LL%=  >>rcdSSS.n[R"SURRUSSS9$)zAGets availability domain scope flag mapper for resource policies.)zunspecified-scopezbInstances will be spread across different instrastructure to not share power, host and networking.)hostzbSpecifies availability domain scope across hosts. Instances will be spread across different hosts.)UNSPECIFIED_SCOPEHOSTz--scopeNzJScope specifies the availability domain to which the VMs should be spread.rn)r rprScopeValueValuesEnum)rsros rrrtsF 0C /  # #11FF%  rc US:XaSnOSnURSS[R"5UURXS9S9 g) z,Adds arguments related to resource policies.zinstance-templateaA list of resource policy names (not URLs) to be {action} each instance created using this instance template. If you attach any resource policies to an instance template, you can only use that instance template to create instances that are in the same region as the resource policies. Do not include resource policies that are located in different regions in the same instance template.z|A list of resource policy names to be {action} the {resource}. The policies must exist in the same region as the {resource}.z--resource-policiesRESOURCE_POLICY)r.resource)r4r!rr"N)r#rArgListrC)rr.rr help_texts rAddResourcePoliciesArgsrsY $$GI H        6  = ?rN)FFFT)F)T)#__doc__ __future__rrrgooglecloudsdk.callioperr"googlecloudsdk.command_lib.computerr|r r$googlecloudsdk.command_lib.util.apisr $googlecloudsdk.command_lib.util.argsr rrr'rSrZr]rbrjrtrrrxryrzrrrrrrrrs 8&'/(OE:<D/ ,*+05:*/#'<!~ @ 8"J(."J?K "J>4&?r