관리-도구
편집 파일: DataSourceAltCloud.cpython-39.opt-1.pyc
a '�Dg�! � @ s� d Z ddlZddlZddlZddlZddlmZmZmZm Z e� e �Z dZ ddgZi ddi d �Zd d � ZG d d � d ej�Zdd� ZeejejffgZdd� ZdS )zb This file contains code used to gather the user data passed to an instance on RHEVm and vSphere. � N)�dmi�sources�subp�utilz/etc/sysconfig/cloud-infoZmodprobeZfloppyi� Z localhost)zblock-device-mappingz instance-idzlocal-hostnameZ placementc C sp | d }| d }zt �|��� }W nH tyj zt �|��� }W n" tyd t �td� Y Y dS 0 Y n0 |S )an Description: This callback will be applied by util.mount_cb() on the mounted file. Deltacloud file name contains deltacloud. Those not using Deltacloud but instead instrumenting the injection, could drop deltacloud from the file name. Input: mount_dir - Mount directory Returns: User Data z/deltacloud-user-data.txtz/user-data.txtz Failed accessing user data file.N)r �load_text_file�strip�IOError�logexc�LOG)Z mount_dirZdeltacloud_user_data_fileZuser_data_fileZ user_data� r �H/usr/lib/python3.9/site-packages/cloudinit/sources/DataSourceAltCloud.py�read_user_data_callback& s r c s` e Zd ZdZdd� Zedd�� fdd� Zdd � Zd d � Zd d � Z dd� Z dd� Z dd� Z � Z S )�DataSourceAltCloudZAltCloudc C s* t j�| |||� d | _d| _t j| _d S )N)�/zfile://)r � DataSource�__init__�seedZsupported_seed_starts�METADATA_UNKNOWN�source)�selfZsys_cfgZdistro�pathsr r r r L s zDataSourceAltCloud.__init__N)�ci_pkl_version�returnc s" t � �|� t| d�s tj| _d S )Nr )�super� _unpickle�hasattrr r r )r r �� __class__r r r R s z DataSourceAltCloud._unpicklec C s t j�| �}d|| jf S )Nz %s [seed=%s])r r �__str__r )r �rootr r r r W s zDataSourceAltCloud.__str__c C s� t j�t�rJzt�t��� �� }W n" tyD t� t dt� Y dS 0 |S t � d�}|s\dS |�� }|� d�rrdS |� d�r�dS dS )at Description: Get the type for the cloud back end this instance is running on by examining the string returned by reading either: CLOUD_INFO_FILE or the dmi data. Input: None Returns: One of the following strings: 'RHEV', 'VSPHERE' or 'UNKNOWN' z'Unable to access cloud info file at %s.ZUNKNOWNzsystem-product-name�RHEVZVMWARE�VSPHERE)�os�path�exists�CLOUD_INFO_FILEr r r �upperr r r r Z read_dmi_data� startswith)r � cloud_typeZ system_nameZsys_namer r r �get_cloud_type[ s* � � z!DataSourceAltCloud.get_cloud_typec C sb t �d� | �� }t �dt|�� d|v r8| �� rRdS nd|v rN| �� rRdS ndS t�t d� dS )a� Description: User Data is passed to the launching instance which is used to perform instance configuration. Cloud providers expose the user data differently. It is necessary to determine which cloud provider the current instance is running on to determine how to access the user data. Images built with image factory will contain a CLOUD_INFO_FILE which contains a string identifying the cloud provider. Images not built with Imagefactory will try to determine what the cloud provider is based on system information. zInvoked get_data()zcloud_type: %sr Tr! FzFailed accessing user data.)r �debugr) �str�user_data_rhevm�user_data_vspherer r �r r( r r r � _get_data� s z DataSourceAltCloud._get_datac C s( | � � }|dkrd| _d|�� | jf S )z(Return the subplatform metadata details.r �/dev/fd0z%s (%s))r) r �lowerr. r r r �_get_subplatform� s z#DataSourceAltCloud._get_subplatformc C s d}z t � W n6 tjyD } z t�td|� W Y d}~dS d}~0 0 d}ztj|dd� W n: tjtfy� } z t�td|� W Y d}~dS d}~0 0 zt�|t �}W nT ty� } z|j t j krƂ W Y d}~n,d}~0 tj � y� t�td|� Y n0 || _ t| _|�rd S dS dS ) a� RHEVM specific userdata read If on RHEV-M the user data will be contained on the floppy device in file <user_data_file> To access it: modprobe floppy Leverage util.mount_cb to: mkdir <tmp mount dir> mount /dev/fd0 <tmp mount dir> The call back passed to util.mount_cb will do: read <tmp mount dir>/<user_data_file> NzFailed modprobe: %sFr0 � )r$ �timeoutzFailed udevadm_settle: %s �-Failed to mount %s when looking for user dataT)�modprobe_floppyr ZProcessExecutionErrorr r r Zudevadm_settle�OSError�mount_cbr �errno�ENOENT�MountFailedError� userdata_raw�META_DATA_NOT_SUPPORTED�metadata)r � return_str�eZ floppy_dev�errr r r r, � s8 � z"DataSourceAltCloud.user_data_rhevmc C s� d}t �d�}|D ]x}z t �|t�}|r4|| _W q�W q tyh } z|jtjkrT� W Y d}~qd}~0 t jy� t � t d|� Y q0 q|| _ t | _ |r�dS dS dS )a� vSphere specific userdata read If on vSphere the user data will be contained on the cdrom device in file <user_data_file> To access it: Leverage util.mount_cb to: mkdir <tmp mount dir> mount /dev/fd0 <tmp mount dir> The call back passed to util.mount_cb will do: read <tmp mount dir>/<user_data_file> Nz LABEL=CDROMr5 TF)r Zfind_devs_withr8 r r r7 r9 r: r; r r r< r= r> )r r? Z cdrom_listZ cdrom_devrA r r r r- � s, � z$DataSourceAltCloud.user_data_vsphere)�__name__� __module__� __qualname__Zdsnamer �intr r r) r/ r2 r, r- � __classcell__r r r r r H s +'6r c C s& t � t�\} }t�dd�t�| � d S )NzCommand: %s Output%s� )r �CMD_PROBE_FLOPPYr r* �join)�outZ_errr r r r6 s r6 c C s t �| t�S )N)r Zlist_from_depends� datasources)Zdependsr r r �get_datasource_list" s rL )�__doc__r9 Zloggingr" Zos.pathZ cloudinitr r r r Z getLoggerrB r r% rH r= r r r r6 ZDEP_FILESYSTEMZ DEP_NETWORKrK rL r r r r �<module> s( �" L �