관리-도구
편집 파일: DataSourceIBMCloud.cpython-39.pyc
a '�Dg�: � @ sl d Z ddlZddlZddlZddlZddlmZmZmZm Z m Z ddl m Z m Z mZmZ ddlmZ e�e�ZdZG dd� d�ZejejfZG d d � d e j�Ze e d �d d �Z dd� Z d!e d �dd�Z e e e e e f d �dd�Z!e ee ef d �dd�Z"e ee ef d�dd�Z#ee j$ffgZ%d d � Z&ed k�rhddl'Z'e'j(d d �Z)e)�*� Z+e"� Z,e-e �.e,�� dS )"a- Datasource for IBMCloud. IBMCloud is also know as SoftLayer or BlueMix. IBMCloud hypervisor is xen (2018-03-10). There are 2 different api exposed launch methods. * template: This is the legacy method of launching instances. When booting from an image template, the system boots first into a "provisioning" mode. There, host <-> guest mechanisms are utilized to execute code in the guest and configure it. The configuration includes configuring the system network and possibly installing packages and other software stack. After the provisioning is finished, the system reboots. * os_code: Essentially "launch by OS Code" (Operating System Code). This is a more modern approach. There is no specific "provisioning" boot. Instead, cloud-init does all the customization. With or without user-data provided, an OpenStack ConfigDrive like disk is attached. Only disks with label 'config-2' and UUID '9796-932E' are considered. This is to avoid this datasource claiming ConfigDrive. This does mean that 1 in 8^16 (~4 billion) Xen ConfigDrive systems will be incorrectly identified as IBMCloud. The combination of these 2 launch methods and with or without user-data creates 6 boot scenarios. A. os_code with user-data B. os_code without user-data Cloud-init is fully operational in this mode. There is a block device attached with label 'config-2'. As it differs from OpenStack's config-2, we have to differentiate. We do so by requiring the UUID on the filesystem to be "9796-932E". This disk will have the following files. Specifically note, there is no versioned path to the meta-data, only 'latest': openstack/latest/meta_data.json openstack/latest/network_data.json openstack/latest/user_data [optional] openstack/latest/vendor_data.json vendor_data.json as of 2018-04 looks like this: {"cloud-init":"#!/bin/bash\necho 'root:$6$<snip>' | chpasswd -e"} The only difference between A and B in this mode is the presence of user_data on the config disk. C. template, provisioning boot with user-data D. template, provisioning boot without user-data. With ds-identify cloud-init is fully disabled in this mode. Without ds-identify, cloud-init None datasource will be used. This is currently identified by the presence of /root/provisioningConfiguration.cfg . That file is placed into the system before it is booted. The difference between C and D is the presence of the METADATA disk as described in E below. There is no METADATA disk attached unless user-data is provided. E. template, post-provisioning boot with user-data. Cloud-init is fully operational in this mode. This is identified by a block device with filesystem label "METADATA". The looks similar to a version-1 OpenStack config drive. It will have the following files: openstack/latest/user_data openstack/latest/meta_data.json openstack/content/interfaces meta.js meta.js contains something similar to user_data. cloud-init ignores it. cloud-init ignores the 'interfaces' style file here. In this mode, cloud-init has networking code disabled. It relies on the provisioning boot to have configured networking. F. template, post-provisioning boot without user-data. With ds-identify, cloud-init will be fully disabled. Without ds-identify, cloud-init None datasource will be used. There is no information available to identify this scenario. The user will be able to SSH in as as root with their public keys that have been installed into /root/ssh/.authorized_keys during the provisioning stage. TODO: * is uuid (/sys/hypervisor/uuid) stable for life of an instance? it seems it is not the same as data's uuid in the os_code case but is in the template case. � N)�Any�Callable�Dict�Optional�Tuple)� atomic_helper�sources�subp�util)� openstackz 9796-932Ec @ s e Zd ZdZdZdZdZdS )� PlatformszTemplate/Live/Metadataz Template/Provisioning/Metadataz!Template/Provisioning/No-Metadataz OS-Code/LiveN)�__name__� __module__� __qualname__�TEMPLATE_LIVE_METADATA� TEMPLATE_PROVISIONING_METADATA� TEMPLATE_PROVISIONING_NODATA�OS_CODE� r r �H/usr/lib/python3.9/site-packages/cloudinit/sources/DataSourceIBMCloud.pyr m s r c sT e Zd ZdZdZ� fdd�Z� fdd�Zdd� Zd d � Zd d � Z e d d� �Z � Z S )�DataSourceIBMCloudZIBMCloudNc s0 t t| ��|||� d | _d | _d | _d | _d S �N)�superr �__init__�source�_network_config� network_json�platform)�self�sys_cfgZdistro�paths�� __class__r r r s zDataSourceIBMCloud.__init__c s$ t t| ��� }d|| j| jf }|S )Nz %s [%s %s])r r �__str__r r )r �rootZmstrr! r r r# � s zDataSourceIBMCloud.__str__c C s� t � }|d u rdS |d | _|d | _|d | _|�d�| _|�d�| _|�d�}|d | _zt� |�| _ W n6 t y� } z t � d |� d | _ W Y d }~n d }~0 0 d S ) NFr r �metadata�userdata� networkdata� vendordata� system-uuidz"Invalid content in vendor-data: %sT)�read_mdr r r% �getZ userdata_rawr � system_uuidr Zconvert_vendordataZvendordata_raw� ValueError�LOG�warning)r �resultsZvd�er r r � _get_data� s z DataSourceIBMCloud._get_datac C s d| j | jf S )z/Return the subplatform metadata source details.z%s (%s))r r �r r r r �_get_subplatform� s z#DataSourceIBMCloud._get_subplatformc C s | j du rdS | j t� kS )a quickly (local check only) if self.instance_id is still valid in Template mode, the system uuid (/sys/hypervisor/uuid) is the same as found in the METADATA disk. But that is not true in OS_CODE mode. So we read the system_uuid and keep that for later compare.NF)r, �_read_system_uuid)r r r r r �check_instance_id� s z$DataSourceIBMCloud.check_instance_idc C s^ | j tjkrddd�S | jd u rX| jtjd fvrNt�d� t j | jd d�| _n t�d� | jS )NZdisabled� )Zconfig�versionz(network config provided via network_json)Z known_macsz#no network configuration available.) r r r r r r ZUNSETr. �debugr Zconvert_net_jsonr3 r r r �network_config� s � z!DataSourceIBMCloud.network_config) r r r Zdsnamer, r r# r2 r4 r6 �propertyr: � __classcell__r r r! r r z s r )�returnc C s& d} t j�| �sdS t�| ��� �� S )zW Read the system uuid. :return: the system uuid or None if not available. z/sys/hypervisor/uuidN)�os�path�isfiler Zload_text_file�strip�lower)Z uuid_pathr r r r5 � s r5 c C s t j�d�S )z� Return boolean indicating if this is a xen hypervisor. :return: True if this is a xen hypervisor, False otherwise. z /proc/xen)r> r? �existsr r r r �_is_xen� s rD �#/root/provisioningConfiguration.cfg�/root/swinstall.log�/proc/1/environc C s� t j�| �r�d| }d}t j�|�rxt j�|�rbt �|�jt �|�jk}|d||rVdndf 7 }q�|d||f 7 }d}q�|d| 7 }ndd | }}t�d ||� |S ) z@Return boolean indicating if this boot is ibm provisioning boot.zconfig '%s' exists.Tz log '%s' from %s boot.�currentZpreviousz. log '%s' existed, but no reference file '%s'.Fz log '%s' did not exist.zconfig '%s' did not exist.zibm_provisioning=%s: %s)r> r? rC �stat�st_mtimer. r9 )Zprov_cfgZinst_logZboot_ref�msg�resultr r r �_is_ibm_provisioning� s( � � �rM c C s\ d} d}d}t � s|S i }z t�� }W n4 tjyZ } zt�d|� W Y d}~dS d}~0 0 t|�� �D ]�}|| }|� dd�� � }|� dd�� � } || |fvr�qh||v r�t�d ||| |� qh||kr�| t kr�t� d ||| |� qh|||< qh|� | i �� d �} |� |i �� d �} | �r"t j| fS | �rFt� �r:t j| fS t j| fS nt� �rXt jdfS |S ) z�Return a tuple (Platform, path) If this is Not IBM cloud, then the return value is (None, None). An instance in provisioning mode is considered running on IBM cloud.ZMETADATAzCONFIG-2)NNzFailed to run blkid: %sNZLABEL� ZUUIDz.Duplicate fslabel '%s'. existing=%s current=%sz/Skipping %s with LABEL=%s due to uuid != %s: %sZDEVNAME)rD r Zblkidr ZProcessExecutionErrorr. r/ �sorted�keysr+ �upper�IBM_CONFIG_UUIDr9 r r rM r r r ) Z label_mdataZ label_cfg2Z not_foundZfslabelsZdevsr1 �dev�dataZlabel�uuidZ metadata_pathZ cfg2_pathr r r �get_ibm_platform� s\ �� rV c C s� t � \} }| du r t�d� dS | tv s0|du r@t�d| � dS | |t� d�}z&tj�|�rft|�}n t � |t�}W n: t j y� } z t d| ||f �|�W Y d}~n d}~0 0 |�|� |S )a Read data from IBM Cloud. :return: None if not running on IBM Cloud. dictionary with guaranteed fields: metadata, version and optional fields: userdata, vendordata, networkdata. Also includes the system uuid from /sys/hypervisor/uuid.Nz!This is not an IBMCloud platform.z/Cloud-init is disabled during provisioning: %s.)r r r) z8Failed reading IBM config disk (platform=%s path=%s): %s)rV r. r9 � PROVISIONINGr5 r> r? �isdir�metadata_from_dirr Zmount_cbr �BrokenMetadata� RuntimeError�update)r r? �retr0 r1 r r r r* / s2 � ��� r* )� source_dirr= c C sj t t d�dd�}ttt tf d�dd�}t ttgtf td�dd �}d |d �|fd |d �dd� fd|d�|fd|d�|fg}i }|D ]&\}}}tj�| |�} || |�||< q�|d du r�t� | � d���i |d< |d } |d } d| v �r<zt � | d �| d< W n: t t f�y: } z t� d| � ���W Y d} ~ n d} ~ 0 0 d} | D ] \}}|| v �rD| | | |< �qD|S )a� Walk source_dir extracting standardized metadata. Certain metadata keys are renamed to present a standardized set of metadata keys. This function has a lot in common with ConfigDriveReader.read_v2 but there are a number of inconsistencies, such as key renames and only presenting a 'latest' version, which make it an unlikely candidate to share code. :return: Dict containing translated metadata, userdata, vendordata, networkdata as present. )�fnamer= c S s t j�dd| �S )Nr Zlatest)r> r? �join)r_ r r r �opathb s z metadata_from_dir.<locals>.opath)�blobr= c S s t �| �d��S )z� Load JSON from a byte string. This technically could return a list or a str, but we are only assuming a dict here. :param blob: The byte string to load JSON from. :return: The loaded JSON object. zutf-8)�json�loads�decode)rb r r r �load_json_bytese s z*metadata_from_dir.<locals>.load_json_bytes)r? � translatorr= c S s� zt �| �}||�W S tyH } z t�d| |� W Y d }~d S d }~0 ty� } z"t�d| � d|� ���W Y d }~n d }~0 0 d S )Nz Failed reading path '%s': %szFailed decoding z: )r Zload_binary_file�IOErrorr. r9 � Exceptionr rZ )r? rg �rawr1 r r r � load_fileq s z$metadata_from_dir.<locals>.load_fileZ metadata_rawzmeta_data.jsonr& Z user_datac S s | S r r )�xr r r �<lambda>~ � z#metadata_from_dir.<locals>.<lambda>r( zvendor_data.jsonr' znetwork_data.jsonNz' missing required file 'meta_data.json'r% Z random_seedz,Badly formatted metadata random_seed entry: ))Z public_keysz public-keys)�hostnamezlocal-hostname)rU z instance-id)�str�bytesr r r r> r? r` r rZ �base64Z b64decoder- � TypeError)r^ ra rf rk �filesr0 �namer? ZtranslZfpathZmd_rawZmdr1 �renamesZold_keyZnew_keyr r r rY S s> � � � rY c C s t �| t�S r )r Zlist_from_depends� datasources)Zdependsr r r �get_datasource_list� s rx �__main__zQuery IBM Cloud Metadata)� description)rE rF rG )/�__doc__rr rc Zloggingr> �typingr r r r r Z cloudinitr r r r Zcloudinit.sources.helpersr Z getLoggerr r. rR r r r rW Z DataSourcer rp r5 rD �boolrM rV r* rY ZDEP_FILESYSTEMrw rx �argparse�ArgumentParser�parser� parse_args�argsrT �printZ json_dumpsr r r r �<module> sD ] �D �� <$W �