>gBdZddlZddlZddlZddlmZGddeZy)z Kubernetes No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator) # noqa: E501 The version of the OpenAPI document: release-1.32 Generated by: https://openapi-generator.tech N) ConfigurationceZdZdZ ddddZddddZdd Zed Zejd Zed Z e jdZ edZ e jdZ dZ dZ dZdZdZy )V1beta1ResourceClaimStatuszNOTE: This class is auto generated by OpenAPI Generator. Ref: https://openapi-generator.tech Do not edit the class manually. V1beta1AllocationResultz"list[V1beta1AllocatedDeviceStatus]z+list[V1beta1ResourceClaimConsumerReference]) allocationdevices reserved_forrr reservedForNc| t}||_d|_d|_d|_d|_|||_|||_|||_yy)z7V1beta1ResourceClaimStatus - a model defined in OpenAPIN) rlocal_vars_configuration _allocation_devices _reserved_for discriminatorrrr )selfrrr r s k/var/www/openai/venv/lib/python3.12/site-packages/kubernetes/client/models/v1beta1_resource_claim_status.py__init__z#V1beta1ResourceClaimStatus.__init__/sd # +'4 $(@% !!  !(DO  "DL  # ,D  $c|jS)zGets the allocation of this V1beta1ResourceClaimStatus. # noqa: E501 :return: The allocation of this V1beta1ResourceClaimStatus. # noqa: E501 :rtype: V1beta1AllocationResult r rs rrz%V1beta1ResourceClaimStatus.allocationAsrc||_y)zSets the allocation of this V1beta1ResourceClaimStatus. :param allocation: The allocation of this V1beta1ResourceClaimStatus. # noqa: E501 :type: V1beta1AllocationResult Nr)rrs rrz%V1beta1ResourceClaimStatus.allocationKs &rc|jS)aGets the devices of this V1beta1ResourceClaimStatus. # noqa: E501 Devices contains the status of each device allocated for this claim, as reported by the driver. This can include driver-specific information. Entries are owned by their respective drivers. # noqa: E501 :return: The devices of this V1beta1ResourceClaimStatus. # noqa: E501 :rtype: list[V1beta1AllocatedDeviceStatus] rrs rrz"V1beta1ResourceClaimStatus.devicesVs}}rc||_y)aSets the devices of this V1beta1ResourceClaimStatus. Devices contains the status of each device allocated for this claim, as reported by the driver. This can include driver-specific information. Entries are owned by their respective drivers. # noqa: E501 :param devices: The devices of this V1beta1ResourceClaimStatus. # noqa: E501 :type: list[V1beta1AllocatedDeviceStatus] Nr)rrs rrz"V1beta1ResourceClaimStatus.devicesas   rc|jS)aGets the reserved_for of this V1beta1ResourceClaimStatus. # noqa: E501 ReservedFor indicates which entities are currently allowed to use the claim. A Pod which references a ResourceClaim which is not reserved for that Pod will not be started. A claim that is in use or might be in use because it has been reserved must not get deallocated. In a cluster with multiple scheduler instances, two pods might get scheduled concurrently by different schedulers. When they reference the same ResourceClaim which already has reached its maximum number of consumers, only one pod can be scheduled. Both schedulers try to add their pod to the claim.status.reservedFor field, but only the update that reaches the API server first gets stored. The other one fails with an error and the scheduler which issued it knows that it must put the pod back into the queue, waiting for the ResourceClaim to become usable again. There can be at most 256 such reservations. This may get increased in the future, but not reduced. # noqa: E501 :return: The reserved_for of this V1beta1ResourceClaimStatus. # noqa: E501 :rtype: list[V1beta1ResourceClaimConsumerReference] rrs rr z'V1beta1ResourceClaimStatus.reserved_forms!!!rc||_y)aSets the reserved_for of this V1beta1ResourceClaimStatus. ReservedFor indicates which entities are currently allowed to use the claim. A Pod which references a ResourceClaim which is not reserved for that Pod will not be started. A claim that is in use or might be in use because it has been reserved must not get deallocated. In a cluster with multiple scheduler instances, two pods might get scheduled concurrently by different schedulers. When they reference the same ResourceClaim which already has reached its maximum number of consumers, only one pod can be scheduled. Both schedulers try to add their pod to the claim.status.reservedFor field, but only the update that reaches the API server first gets stored. The other one fails with an error and the scheduler which issued it knows that it must put the pod back into the queue, waiting for the ResourceClaim to become usable again. There can be at most 256 such reservations. This may get increased in the future, but not reduced. # noqa: E501 :param reserved_for: The reserved_for of this V1beta1ResourceClaimStatus. # noqa: E501 :type: list[V1beta1ResourceClaimConsumerReference] Nr)rr s rr z'V1beta1ResourceClaimStatus.reserved_forxs *rc~i}tj|jD]\}}t||}t |t rt t d|||<t|dr|jS|S)Nto_dicthasattrr!)xs rz4V1beta1ResourceClaimStatus.to_dict..sWQ -BaiikIIrr!cTt|ddr|d|djfS|S)Nr!rr")items rr%z4V1beta1ResourceClaimStatus.to_dict..s6tAw 2#'q'47??+s r__ne__z!V1beta1ResourceClaimStatus.__ne__s'%!;<||~00r)NNNN)__name__ __module__ __qualname____doc__r+ attribute_maprpropertyrsetterrr r!r9r;r@rBrrrrs 07EM#%M -$  && ^^    "" * *0.11rr)rFr7rer)kubernetes.client.configurationrobjectrrJrrrNs& 9[1[1r