File manager - Edit - /opt/saltstack/salt/lib/python3.10/site-packages/salt/states/__pycache__/esxcluster.cpython-310.pyc
Back
o ;j�X � @ s d Z ddlZddlZddlmZ ddlZddlmZm Z ddl m Z ddl m Z ddlmZ zddlZdZW n eyA d ZY nw z dd lmZ dZW n eyW d ZY nw e�e�Zd d � Zd d� Zedd� �Zdd� Z edd� �Z edd� �Z eddd��Z dS )a� Manage VMware ESXi Clusters. .. Warning:: This module will be deprecated in a future release of Salt. VMware strongly recommends using the `VMware Salt extensions <https://docs.saltproject.io/salt/extensions/salt-ext-modules-vmware/en/latest/all.html>`_ instead of the ESX cluster module. Because the Salt extensions are newer and actively supported by VMware, they are more compatible with current versions of ESXi and they work well with the latest features in the VMware product line. Dependencies ============ - pyVmomi Python Module pyVmomi ------- PyVmomi can be installed via pip: .. code-block:: bash pip install pyVmomi .. note:: Version 6.0 of pyVmomi has some problems with SSL error handling on certain versions of Python. If using version 6.0 of pyVmomi, Python 2.7.9, or newer must be present. This is due to an upstream dependency in pyVmomi 6.0 that is not supported in Python versions 2.7 to 2.7.8. If the version of Python is not in the supported range, you will need to install an earlier version of pyVmomi. See `Issue #29537`_ for more information. .. _Issue #29537: https://github.com/saltstack/salt/issues/29537 Based on the note above, to install an earlier version of pyVmomi than the version currently listed in PyPi, run the following: .. code-block:: bash pip install pyVmomi==5.5.0.2014.1.1 The 5.5.0.2014.1.1 is a known stable version that this original ESXi State Module was developed against. � N��wraps)�ESXClusterConfigSchema� LicenseSchema)� dictupdate)�recursive_diff)� list_diffTF)� VmomiSupportc C s6 t sdS tsdS dtjv rtjdkrtjdk rdS dS )N)Fz/State module did not load: jsonschema not found)Fz,State module did not load: pyVmomi not foundz vim25/6.0)� � )r r � )FzaState module did not load: Incompatible versions of Python and pyVmomi present. See Issue #29537.T)�HAS_JSONSCHEMA� HAS_PYVMOMIr Z versionMap�sys� version_info� r r �J/opt/saltstack/salt/lib/python3.10/site-packages/salt/states/esxcluster.py� __virtual__P s r c s t � �� fdd��}|S )z> Decorator wrapper to warn about azurearm deprecation c s6 t jjjddtd� � | i t jjjdi |����}|S )NZArgonz�The 'esxcluster' functionality in Salt has been deprecated and its functionality will be removed in version 3008 in favor of the saltext.vmware Salt Extension. (https://github.com/saltstack/salt-ext-modules-vmware))�categoryr )�salt�utilsZversionsZ warn_until� FutureWarning�argsZ clean_kwargs)r �kwargs�ret��functionr r �wrappedj s � z%_deprecation_message.<locals>.wrappedr )r r r r r �_deprecation_messagee s r c C s dS )zT Retrieves and adapt the login credentials from the proxy connection module Tr )�lowr r r �mod_initz s r c C sB t �d� dd� td | d�D �}|s tj�d|� d���|d S ) z Retrieves the vsan_datastorezRetrieving vsan datastorec S s g | ] }|d dkr|�qS )�typeZvsanr )�.0Zdsr r r � <listcomp>� s �z'_get_vsan_datastore.<locals>.<listcomp>z!vsphere.list_datastores_via_proxy��service_instancez0No vSAN datastores where retrieved for cluster '�'r )�log�trace�__salt__r � exceptions�VMwareObjectRetrievalError)�si� cluster_nameZvsan_datastoresr r r �_get_vsan_datastore� s � �r. c C sv t d � }|dkr| t d � d }}n |dkr(t d � d t d � d }}n tj�d|� ���t�d | ||� |}t�d |� d }| i d d d�}g }i } d }�z�t�d� t�� } t�d| � zt � || � W n t jj y} } ztj� | ��d } ~ ww d } t d � } z t d ||| d�} W n` tjj y� d}td r�|�d�| ||�� t�|d � t d | � |�d d�|�d�� | Y W S t�d||� t d |||| d� |�d �||�� t�|d � | �d |i� Y nw | �r�d }d |v �r5d |d v �r5t| �d i ��d g �|�d i ��d g �d!�}t�d"|j� |d d = d | v �r5d | d v �r5| d d = t| |�}t�d#|j� |j�s]|�rL|j�s]|�d$�||�� t�|d � n�d}d%}|j�rl|� |j� �}|�r�|j�r�d&�|d�d'd(� |j�d�D ���}td �r�|�d)�| |||�� nR|j}|j}|�r�|j�r�t �|d d |jii� |�r�|j�r�t �|d d |jii� t�d*|� t d+ |||| d� |�d,�||�� t�|d � | �||d-�� t d | � d}td �r�|�r�d }|�|d�|�| d.�� |W S tjj�y: } z#tj d/| dd0� | �r$t d | � |�d t | �d�� |W Y d } ~ S d } ~ ww )1a� Configures a cluster. Creates a new cluster, if it doesn't exist on the vCenter or reconfigures it if configured differently Supported proxies: esxdatacenter, esxcluster name Name of the state. If the state is run in by an ``esxdatacenter`` proxy, it will be the name of the cluster. cluster_config Configuration applied to the cluster. Complex datastructure following the ESXClusterConfigSchema. Valid example is: .. code-block:: yaml drs: default_vm_behavior: fullyAutomated enabled: true vmotion_rate: 3 ha: admission_control _enabled: false default_vm_settings: isolation_response: powerOff restart_priority: medium enabled: true hb_ds_candidate_policy: userSelectedDs host_monitoring: enabled options: - key: das.ignoreinsufficienthbdatastore value: 'true' vm_monitoring: vmMonitoringDisabled vm_swap_placement: vmDirectory vsan: auto_claim_storage: false compression_enabled: true dedup_enabled: true enabled: true zvsphere.get_proxy_typeZ esxdatacenterzesxdatacenter.get_details� datacenterZ esxcluster�esxcluster.get_details�clusterzUnsupported proxy z.Running %s for cluster '%s' in datacenter '%s'zcluster_dict = %sFN�Default��name�changes�result�commentz)Validating cluster_configured state inputz schema = %s�&vsphere.get_service_instance_via_proxyzvsphere.list_clusterr$ T�testz5State {} will create cluster '{}' in datacenter '{}'.����vsphere.disconnect� �r6 r7 z)Creating cluster '%s' in datacenter '%s'.zvsphere.create_clusterz'Created cluster '{}' in datacenter '{}'�newZha�options�keyzoptions diffs = %sz diffs = %szBCluster '{}' in datacenter '{}' is up to date. Nothing to be done.� z{} ha: options: {}c S s g | ]}d |� ��qS )z r �r" �lr r r r# $ s z&cluster_configured.<locals>.<listcomp>z8State {} will update cluster '{}' in datacenter '{}': {}znew_values = %szvsphere.update_clusterz'Updated cluster '{}' in datacenter '{}'�r> �old�r6 r7 r5 � Error: %s��exc_info) r) r r* �CommandExecutionErrorr' �infor( r � serialize� jsonschema�validate�ValidationErrorZ InvalidESXClusterPayloadErrorr+ �__opts__�append�format�update�joinr �getZdiffsr � changes_strZ changes_str2�split� new_values� old_valuesr �error�str)r4 Zcluster_configZ proxy_typer- �datacenter_nameZ cluster_dict�changes_requiredr �commentsr5 �schema�exc�currentr, Zldiff�diffrV rX rY Z ret_statusr r r �cluster_configured� s , � �� �� ��� ������ ��� ���� ��� � ��rc c C s� t d � d t d � d }}|� d|� �}t�d|� | i ddd�}g }i }d }z�t d � } t| |�} | d |krL|�d �| d �� t�|d � nHd}td rc|�d�| |�� t�|d � n1t�d| d |� t d | d || d� |�d|� d�� dd |id | d id�i}t�|d � t d | � |�|s�dntd r�dndd� |�|d�� |W S t j j y� } z!tj d| dd � | r�t d | � |�d | jd �� |W Y d} ~ S d} ~ ww ) z� Configures the cluster's VSAN datastore WARNING: The VSAN datastore is created automatically after the first ESXi host is added to the cluster; the state assumes that the datastore exists and errors if it doesn't. r0 r1 r/ �/z*Running vsan_datastore_configured for '%s'Nr2 r3 Fr8 r4 z;vSAN datastore is correctly named '{}'. Nothing to be done.r: Tr9 z0State {} will rename the vSAN datastore to '{}'.z$Renaming vSAN datastore '%s' to '%s'zvsphere.rename_datastore)�datastore_nameZnew_datastore_namer% zRenamed vSAN datastore to '�'.Zvsan_datastorerD r; r< rF rG rH r= )r) r' rK r. rQ rR rP r( rS rT r r* rJ rZ �strerror) r4 re r- r\ � display_namer r^ r5 r] r, Zvsan_dsr` r r r �vsan_datastore_configuredS s| � ������ �� ��� ��ri c s\ | i ddd�}|st j�d��td � d td � d }}|� d|� �}t�d |� t�d |� d||d �}t�d |� g }i }d } d } �z�t�d� t�� } z t � d|i| � W n t jj yn } zt j� | ��d} ~ ww td � } td | d�}|� � D �]O\}� � fdd�|D �}|s�d} td r�|�d�| ||�� t�|d � qz td � || d�}W n# t jjy� } z|�|j� t�|d � d} W Y d}~qd}~ww |�d|� d �� t�|d � n|�d �|�� t�|d � |d }t�d � td ||| d!�}|�r|d nd}|�r,|d" � k�r,|�d#�||�� t�|d � qd} |d$ |d% k�rJ|�d&�||�� t�|d � d} qtd �ra|�d'�| ||�� t�|d � nnz td( � |||| d)� W n$ t jj�y� } z|�|j� t�|d � d} W Y d}~qd}~ww |�d*�||�� t�|d � td ||| d!�d }d+|d"< |�r�d+|d"< |�r�|d$ tjk�r�d,|d$< ||d-�||< qtd. | � |�| �s�dn td �r�dn| �r�d ndd/�|�td �s�|ni d0�� |W S t jj�y- } z"tjd1| dd2� | �rtd. | � |�d | jd3�� |W Y d} ~ S d} ~ ww )4a� Configures licenses on the cluster entity Checks if each license exists on the server: - if it doesn't, it creates it Check if license is assigned to the cluster: - if it's not assigned to the cluster: - assign it to the cluster if there is space - error if there's no space - if it's assigned to the cluster nothing needs to be done Nr2 r3 zNo licenses providedr0 r1 r/ rd z$Running licenses configured for '%s'z licenses = %s)r! r/ r1 z entity = %sFzValidating licenses�licensesr8 zvsphere.list_licensesr$ c s g | ] }|d � kr|�qS )r@ r rB ��licenser r r# � s z'licenses_configured.<locals>.<listcomp>Tr9 z>State {} will add license '{}', and assign it to cluster '{}'.r: zvsphere.add_license)r@ � descriptionr% zAdded license 'rf z0License '{}' already exists. Nothing to be done.r z Checking licensed entities...z vsphere.list_assigned_licenses)�entity�entity_display_namer% r@ zBLicense '{}' already assigned to cluster '{}'. Nothing to be done.Zcapacity�usedzGCannot assign license '{}' to cluster '{}'. No free capacity available.z2State {} will assign license '{}' to cluster '{}'.zvsphere.assign_license)Z license_key� license_namern ro r% z&Assigned license '{}' to cluster '{}'.z<hidden>Z UnlimitedrD r; r< rF rG rH r= )r r* ZArgumentValueErrorr) r' rK r( r rL rM rN rO ZInvalidLicenseError�itemsrP rQ rR ZVMwareApiError�err_msgrZ r �maxsizerS rT rJ rg )r4 rj r r- r\ rh rn r^ r5 Z has_errorsZ needs_changesr_ r` r, Zexisting_licensesrq Zfiltered_licensesZexisting_license�exZassigned_licensesZalready_assigned_licenseZassigned_licenser rk r �licenses_configured� s � �� �� � ���� � ���� �� � ������� � ��� ��rv )N) �__doc__�loggingr � functoolsr Zsalt.exceptionsr Z salt.config.schemas.esxclusterr r Z salt.utilsr Zsalt.utils.dictdifferr Zsalt.utils.listdifferr rM r � ImportErrorZpyVmomir r � getLogger�__name__r' r r r r. rc ri rv r r r r �<module> sD 2 � � @ R
| ver. 1.4 |
Github
|
.
| PHP 8.2.30 | Generation time: 0 |
proxy
|
phpinfo
|
Settings