File manager - Edit - /opt/saltstack/salt/lib/python3.10/site-packages/salt/states/__pycache__/net_napalm_yang.cpython-310.pyc
Back
o ;j�$ � @ s� d Z ddlZddlZddlZddlZddlZddlZe�e �Z zddl Z dZ W n e y2 dZ Y nw dZdd� Zdd � Zd d � ZdS ) a NAPALM YANG state ================= Manage the configuration of network devices according to the YANG models (OpenConfig/IETF). .. versionadded:: 2017.7.0 Dependencies ------------ - napalm-yang - pyangbing > 0.5.11 To be able to load configuration on network devices, it requires NAPALM_ library to be installed: ``pip install napalm``. Please check Installation_ for complete details. .. _NAPALM: https://napalm.readthedocs.io .. _Installation: https://napalm.readthedocs.io/en/latest/installation/index.html � NTF� napalm_yangc C s t sdS tjj�ttt�S )z� NAPALM library must be installed for this module to work and run in a (proxy) minion. This module in particular requires also napalm-yang. )FzHUnable to load napalm_yang execution module: please install napalm-yang!)�HAS_NAPALM_YANG�salt�utils�napalmZvirtual�__opts__�__virtualname__�__file__� r r �O/opt/saltstack/salt/lib/python3.10/site-packages/salt/states/net_napalm_yang.py� __virtual__< s r c K sR |� dd�}t|t�rt|d t�r|d }tjj�| �}|� dd�p(t� dd�}|� dd�p4t� dd�}|� dd�p@t� dd�}|� d d�pLt� d d�}|� d d�pXt� d d�} |� d g �} t d � } t � d | � d|vrrd|i}|g}tjj � | d�� } tjjjtjj�tjj�|��| dd� W d � n1 s�w Y t d |d| d��} t � d� t � | � t d | g|�R d| i�}t � d� t � |� |� dd�}|r�|�ddd�� t � d� |S t � d � |d d }d |v r�|�d � t d |g|�R | ||||d ��}t � d � t � |� t d! | � ||d < tjjj||||t| d"�S )#a� Manage the device configuration given the input data structured according to the YANG models. data YANG structured data. models A list of models to be used when generating the config. profiles: ``None`` Use certain profiles to generate the config. If not specified, will use the platform default profile(s). compliance_report: ``False`` Return the compliance report in the comment. .. versionadded:: 2017.7.3 test: ``False`` Dry run? If set as ``True``, will apply the config, discard and return the changes. Default: ``False`` and will commit the changes on the device. commit: ``True`` Commit? Default: ``True``. debug: ``False`` Debug mode. Will insert a new key under the output dictionary, as ``loaded_config`` containing the raw configuration loaded on the device. replace: ``False`` Should replace the config with the new generate one? State SLS example: .. code-block:: jinja {%- set expected_config = pillar.get('openconfig_interfaces_cfg') -%} interfaces_config: napalm_yang.managed: - data: {{ expected_config | json }} - models: - models.openconfig_interfaces - debug: true Pillar example: .. code-block:: yaml openconfig_interfaces_cfg: _kwargs: filter: true interfaces: interface: Et1: config: mtu: 9000 Et2: config: description: "description example" �modelsNr �testF�debug�commitT�replace�compliance_report�profilesz temp.filezCreating temp file: %sZto_dict�wzutf-8)�encodingznapalm_yang.parse)Zconfigr z"Parsed the config from the device:z napalm_yang.compliance_report�filepathzCompliance report:�compliesz Already configured as required.)�resultZcommentzAll good here.z3Does not comply, trying to generate and load config�_kwargs�napalm_yang.load_config�r r r r r zLoaded config result:z file.remove)�optsr )�get� isinstance�tuple�listr r r � default_retr �__salt__�logr �filesZfopenZyamlZ safe_dump�json�loads�dumps�update�pop� loaded_ret)�name�data�kwargsr �retr r r r Zreturn_compliance_reportr Z temp_fileZ file_handleZ device_configr r �loaded_changesr r r �managedR s� ?� � �� ��� ��� �r0 c K s� |� dd�}t|t�rt|d t�r|d }tjj�| �}|� dd�p(t� dd�}|� dd�p4t� dd�}|� dd�p@t� dd�}|� d d�pLt� d d�}|� d g �} d |v r\|� d � t d |g|�R | ||||d ��} tjj� || ||�S )aC Configure the network device, given the input data strucuted according to the YANG models. .. note:: The main difference between this function and ``managed`` is that the later generates and loads the configuration only when there are differences between the existing configuration on the device and the expected configuration. Depending on the platform and hardware capabilities, one could be more optimal than the other. Additionally, the output of the ``managed`` is different, in such a way that the ``pchange`` field in the output contains structured data, rather than text. data YANG structured data. models A list of models to be used when generating the config. profiles: ``None`` Use certain profiles to generate the config. If not specified, will use the platform default profile(s). test: ``False`` Dry run? If set as ``True``, will apply the config, discard and return the changes. Default: ``False`` and will commit the changes on the device. commit: ``True`` Commit? Default: ``True``. debug: ``False`` Debug mode. Will insert a new key under the output dictionary, as ``loaded_config`` containing the raw configuration loaded on the device. replace: ``False`` Should replace the config with the new generate one? State SLS example: .. code-block:: jinja {%- set expected_config = pillar.get('openconfig_interfaces_cfg') -%} interfaces_config: napalm_yang.configured: - data: {{ expected_config | json }} - models: - models.openconfig_interfaces - debug: true Pillar example: .. code-block:: yaml openconfig_interfaces_cfg: _kwargs: filter: true interfaces: interface: Et1: config: mtu: 9000 Et2: config: description: "description example" r Nr r Fr r Tr r r r r ) r r r r r r r r! r r) r" r* ) r+ r, r- r r. r r r r r r/ r r r � configured� s. E ��� r1 )�__doc__�loggingZsalt.utils.filesr Zsalt.utils.jsonZsalt.utils.napalmZsalt.utils.stringutilsZsalt.utils.yaml� getLoggerr r# r r � ImportErrorr r r0 r1 r r r r �<module> s& �
| ver. 1.4 |
Github
|
.
| PHP 8.2.30 | Generation time: 0 |
proxy
|
phpinfo
|
Settings