404

[ Avaa Bypassed ]




Upload:

Command:

elspacio@18.117.107.43: ~ $
3

\�me��@s�UddlZddlZddlZddlZddlZddlZddlZddlZddlZddl	Z	ddl
Z
ddlmZm
Z
mZmZmZddlmZmZeje�ZdOdPdQdRdSdTdUdVdWdXdYdZd[d�
Zdddd�ZdZdZdZdegZdd
ddddgZdZdZdZ ee eegd	d d!id"�Z!d d#d	d	d$�id d%d d&�gd'�Z"d(Z#d)Z$Gd*d+�d+ej%�Z&Gd,d-�d-e'�Z(Gd.d/�d/e(�Z)Gd0d1�d1�Z*Gd2d3�d3e*�Z+Gd4d5�d5e*�Z,Gd6d7�d7e,�Z-deee dfd8d9�Z.d:d;�Z/d\d=d>�Z0d]d?d@�Z1d^dAdB�Z2e&ej3ffgZ4dCdD�Z5edEk�r�ddl6Z6e.�Z7e7dk�r e8dF�e6j9dG�e:e6j;�dGk�rPe<ej=��e<ej=��dHgZ=ne6j;dGd�Z=dIdJ�Z>iZ?e@?xe=D]ZAe>e7eAe?dK��qtWe8ejBe?dGdd_dN��dS)`�N)�
atomic_helper�dmi�sources�subp�util)�
EventScope�	EventType�sdc:uuidT�hostname�root_authorized_keys�user-scriptF�	user-data�cloud-init:user-data�iptables_disable�
motd_sys_info�sdc:datacenter_name�sdc:vendor-data�sdc:operator-script�sdc:hostname�sdc:dns_domain)
zinstance-idzlocal-hostnamezpublic-keyszuser-scriptzlegacy-user-dataz	user-datarrZavailability_zonezvendor-datazoperator-scriptr
�
dns_domainzsdc:nicsz
sdc:resolversz
sdc:routes)znetwork-data�dns_servers�routeszlx-brandZkvmZSmartOSZ
datasourcezsdc:uuiduser-dataz"/native/.zonecontrol/metadata.sockz
/dev/ttyS1�<Z
ephemeral0z/dev/vdb)�
serial_device�serial_timeout�metadata_sockfileZno_base64_decode�base64_keys�
base64_all�disk_aliasesZmbr)Z
table_typeZlayoutZ	overwriteZext4)ZlabelZ
filesystem�device)Z
disk_setupZfs_setupaU#cloud-boothook
#!/bin/sh
fname="%(per_boot_d)s/01_smartos_vendor_data.sh"
mkdir -p "${fname%%/*}"
cat > "$fname" <<"END_SCRIPT"
#!/bin/sh
##
# This file is written as part of the default vendor data for SmartOS.
# The SmartOS datasource writes the listed file from the listed metadata key
#   sdc:operator-script -> %(operator_script)s
#   user-script -> %(user_script)s
#
# You can view content with 'mdata-get <key>'
#
for script in "%(operator_script)s" "%(user_script)s"; do
    [ -x "$script" ] || continue
    echo "executing '$script'" 1>&2
    "$script"
done
END_SCRIPT
chmod +x "$fname"
z/var/dbc@s�eZdZdZejZejZej	e
je
je
j
hiZdd�Zdd�Zdd�Zdd	�Zd
d�Zdd
�Zdd�Zdd�Zdd�Zedd��ZdS)�DataSourceSmartOSZJoyentcCsdtjj||||�tj|jtj|ti�tg�|_i|_	d|_
d|_tj
j|jjd��|_|j�dS)N�scripts)r�
DataSource�__init__r�
mergemanydict�ds_cfgZget_cfg_by_path�DS_CFG_PATH�BUILTIN_DS_CONFIG�metadata�network_data�_network_config�os�path�join�paths�	get_cpathZ
script_base_d�_init)�selfZsys_cfgZdistror/�r3�'/usr/lib/python3.6/DataSourceSmartOS.pyr$�s
zDataSourceSmartOS.__init__cCstjj|�}d||jfS)Nz%s [client=%s])rr#�__str__�	md_client)r2�rootr3r3r4r5�szDataSourceSmartOS.__str__cCsZ|jtjkr$t�|_|jdkr$d|_|jtjkrVt|j|jd|jd|jdd�|_dS)Nrrr)�smartos_typerrr)r8r�UNSET�get_smartos_environr6�jmc_client_factoryr&)r2r3r3r4r1�s
zDataSourceSmartOS._initcCsHtjd�d}tjjdj|dg��rDtjdj|dg�dj|dg��dS)a�Mark the instance provisioning state as successful.

        When run in a zone, the host OS will look for /var/svc/provisioning
        to be renamed as /var/svc/provision_success.   This should be done
        after meta-data is successfully retrieved and from this point
        the host considers the provision of the zone to be a success and
        keeps the zone running.
        z-Instance provisioning state set as successfulz/var/svc�/ZprovisioningZprovision_successN)�LOG�debugr,r-�existsr.�rename)r2Zsvc_pathr3r3r4�_set_provisioned�s

z"DataSourceSmartOS._set_provisionedc
Cs�|j�i}d}|js$tjd�dS|jj�s@tjd|j�dS|jj�x0tj�D]$\}}|\}}|jj	||d�||<qTWx$t
j�D]\}}|jj|�||<q�W|jj�t
jj|jj�d|dd�}t
jj|d	�}d
t}	t|j	d	�||	ddd
�t
jj|d�}
t|j	d�|
ddd�|j	d�}dt}t||�|d�sd|d�rX|d|d<n|d|d<d}|d�rz|d}|d�s�t||
t
jj|jjd�d�d�|d<tj||jg�|_||_|d|_|d|_|d|_|j�dS)N�zNot running on smartosFz4No metadata device '%r' found for SmartOS datasource)�stripZ	instanceszinstance-id�datazuser-scriptz%s/user-scriptTi�)�	content_f�link�shebang�modezoperator-script)rErGrHzlegacy-user-dataz%s/mdata-user-datazlocal-hostnamer
z	user-datazvendor-datar"zper-boot)�user_script�operator_scriptZ
per_boot_dznetwork-datar)r1r8r=r>r6r?�open_transport�SMARTOS_ATTRIB_MAP�items�get�SMARTOS_ATTRIB_JSON�get_json�close_transportr,r-r.r/r0�
LEGACY_USER_D�write_boot_content�BUILTIN_VENDOR_DATArr%r)Zuserdata_rawZvendordata_rawr*�routes_datarA)
r2ZmdZudZci_nounZ	attributeZsmartos_nounrCZdata_drIZ
u_script_lrJZu_dataZu_data_fr3r3r4�	_get_data�sr













zDataSourceSmartOS._get_datacCsdtS)Nzserial (%s))�
SERIAL_DEVICE)r2r3r3r4�_get_subplatformMsz"DataSourceSmartOS._get_subplatformcCs|jdj|�S)Nr)r&rN)r2�namer3r3r4�device_name_to_devicePsz'DataSourceSmartOS.device_name_to_devicecCs|jtkrtSiS)N)r8�SMARTOS_ENV_KVM�BUILTIN_CLOUD_CONFIG)r2r3r3r4�get_config_objSs
z DataSourceSmartOS.get_config_objcCs
|jdS)Nzinstance-id)r))r2r3r3r4�get_instance_idXsz!DataSourceSmartOS.get_instance_idcCsN|jtjkrd|_|jdkrH|jdk	rHt|j|jd|jd|jd�|_|jS)Nrr)r*rrr)r+rr9r*�convert_smartos_network_datar)rU)r2r3r3r4�network_config[s

z DataSourceSmartOS.network_configN)�__name__�
__module__�__qualname__Zdsnamerr9r8r6rZNETWORKrZBOOT_NEW_INSTANCEZBOOTZBOOT_LEGACYZdefault_update_eventsr$r5r1rArVrXrZr]r^�propertyr`r3r3r3r4r!�s"
cr!c@seZdZdS)�JoyentMetadataFetchExceptionN)rarbrcr3r3r3r4relsrec@seZdZdS)�JoyentMetadataTimeoutExceptionN)rarbrcr3r3r3r4rfpsrfc@s�eZdZdZejd�Zd#dd�Zdd�Zdd	�Z	d
d�Z
dd
�Zdd�Zd$dd�Z
d%dd�Zd&dd�Zdd�Zdd�Zdd�Zdd�Zdd �Zd!d"�ZdS)'�JoyentMetadataClientz�
    A client implementing v2 of the Joyent Metadata Protocol Specification.

    The full specification can be found at
    http://eng.joyent.com/mdata/protocol.html
    z~V2 (?P<length>\d+) (?P<checksum>[0-9a-f]+) (?P<body>(?P<request_id>[0-9a-f]+) (?P<status>SUCCESS|NOTFOUND)( (?P<payload>.+))?)NcCs|dkrt�}||_||_dS)N)r:r8�fp)r2r8rhr3r3r4r$�szJoyentMetadataClient.__init__cCsdjtj|jd��d@�S)Nz{0:08x}zutf-8l��)�format�binasciiZcrc32�encode)r2�bodyr3r3r4�	_checksum�szJoyentMetadataClient._checksumcCs�|jj|�j�}t|d�t|d�krDtdj|dt|d����|j|d�}|d|krrtdj||d���|d|kr�tdj||d���|jdd�s�t	j
d	�dStj|d�}t	j
d
|�|S)NZlengthrlz*Incorrect frame length given ({0} != {1}).Zchecksumz*Invalid checksum (expected: {0}; got {1}).�
request_idz-Request ID mismatch (expected: {0}; got {1}).ZpayloadzNo value found.zValue "%s" found.)
�
line_regex�match�	groupdict�int�lenrerirmrNr=r>rZb64d)r2Zexpected_request_id�frameZ
frame_dataZexpected_checksum�valuer3r3r4�_get_value_from_frame�s(
z*JoyentMetadataClient._get_value_from_framecs�g��fdd�}d}x�yB|jjd�}t|�dkr>t||���|dkrL|�S�j|�Wqtk
r�}z$|jtjkr�t||��|��WYdd}~XqXqWdS)z�
        Reads a line a byte at a time until 
 is encountered.  Returns an
        ascii string with the trailing newline removed.

        If a timeout (per-byte) is set and it expires, a
        JoyentMetadataFetchException will be thrown.
        csdj��jd�S)N��ascii)r.�decoder3)�responser3r4�as_ascii�sz0JoyentMetadataClient._readline.<locals>.as_asciizPartial response: '%s'�r�
N)rh�readrsrf�append�OSError�errnoZEAGAIN)r2r{�msgZbyte�excr3)rzr4�	_readline�s"
zJoyentMetadataClient._readlinecCs |jj|jd��|jj�dS)Nrx)rh�writerk�flush)r2r�r3r3r4�_write�szJoyentMetadataClient._writecCsJtjd�|jd�|j�}tjd|�|dkr<td|��tjd�dS)NzNegotiating protocol V2z
NEGOTIATE V2
z	read "%s"ZV2_OKz'Invalid response "%s" to "NEGOTIATE V2"zNegotiation complete)r=r>r�r�re)r2rzr3r3r4�
_negotiate�s


zJoyentMetadataClient._negotiatec	Cs�djtjdd��}dj||f�}|r>|dtj|j��j�7}djt|�|j	|�|�}t
jd|�d}|jsx|j
�d}|j|�|j�}|r�|j�t
jd	|�d
|kr�dS|j||�}|S)Nz{0:08x}rl��� zV2 {0} {1} {2}
z#Writing "%s" to metadata transport.FTz"Read "%s" from metadata transport.�SUCCESS)ri�randomZrandintr.�base64�	b64encoderkryrsrmr=r>rhrKr�r�rQrv)	r2�rtype�paramrnZmessage_bodyr�Z
need_closerzrur3r3r4�request�s,
zJoyentMetadataClient.requestFcCs.|jd|d�}|dkr|S|r*|r*|j�}|S)NZGET)r�r�)r�rC)r2�key�defaultrC�resultr3r3r4rN�szJoyentMetadataClient.getcCs$|j||d�}|dkr|Stj|�S)N)r�)rN�json�loads)r2r�r�r�r3r3r4rP�szJoyentMetadataClient.get_jsoncCs|jdd�}|sgS|jd�S)NZKEYS)r��
)r��split)r2r�r3r3r4�listszJoyentMetadataClient.listcCs*djdd�||fD��j�}|jd|d�S)N� cSsg|]}tj|j���qSr3)r�r�rk)�.0�ir3r3r4�
<listcomp>sz,JoyentMetadataClient.put.<locals>.<listcomp>ZPUT)r�r�)r.ryr�)r2r��valr�r3r3r4�put
szJoyentMetadataClient.putcCs|jr|jj�d|_dS)N)rh�close)r2r3r3r4rQs
z$JoyentMetadataClient.close_transportcCs|jr
|S|j�|S)N)rhrK)r2r3r3r4�	__enter__szJoyentMetadataClient.__enter__cCs|j�dS)N)rQ)r2�exc_type�	exc_value�	tracebackr3r3r4�__exit__szJoyentMetadataClient.__exit__cCst�dS)N)�NotImplementedError)r2r3r3r4rKsz#JoyentMetadataClient.open_transport)NN)N)NF)N)rarbrc�__doc__�re�compileror$rmrvr�r�r�r�rNrPr�r�rQr�r�rKr3r3r3r4rgts$

!

rgcs8eZdZef�fdd�	Zdd�Zdd�Zdd�Z�ZS)	�JoyentMetadataSocketClientcstt|�j|�||_dS)N)�superr�r$�
socketpath)r2r�r8)�	__class__r3r4r$$sz#JoyentMetadataSocketClient.__init__cCs4tjtjtj�}|j|j�|jd�|_|j�dS)NZrwb)�socketZAF_UNIXZSOCK_STREAMZconnectr��makefilerhr�)r2Zsockr3r3r4rK(sz)JoyentMetadataSocketClient.open_transportcCstjj|j�S)N)r,r-r?r�)r2r3r3r4r?.sz!JoyentMetadataSocketClient.existscCsd|jj|jfS)Nz%s(socketpath=%s))r�rar�)r2r3r3r4�__repr__1sz#JoyentMetadataSocketClient.__repr__)	rarbrc�SMARTOS_ENV_LX_BRANDr$rKr?r��
__classcell__r3r3)r�r4r�#sr�csDeZdZdedf�fdd�	Zdd�Zdd�Zd	d
�Zdd�Z�Z	S)
�JoyentMetadataSerialClient�
Ncs"tt|�j||�||_||_dS)N)r�r�r$r �timeout)r2r r�r8rh)r�r3r4r$6sz#JoyentMetadataSerialClient.__init__cCstjj|j�S)N)r,r-r?r )r2r3r3r4r?=sz!JoyentMetadataSerialClient.existscCsZ|jdkrFtj|j|jd�}|j�s2td|j��||_tj|tj	�|j
�|j�dS)N)r�zUnable to open %s)rh�serialZSerialr r�ZisOpen�SystemError�fcntl�lockfZLOCK_EX�_flushr�)r2Zserr3r3r4rK@s
z)JoyentMetadataSerialClient.open_transportcCs�tjd�|jj}d|j_x(y|j�Wqtk
r>PYqXqWtjd�|dkr`d|j_n||j_xntjd�|jd�y6|j�}|dkr�P|dkr�tjd	�wjtjd
|�Wqjtk
r�tjd�YqjXqjWtjd�||j_dS)
NzFlushing inputg�������?zInput empty�z,Writing newline, expecting "invalid command"r�zinvalid command�FAILUREzGot "FAILURE".  Retrying.z%Unexpected response "%s" during flushzQTimeout while initializing metadata client. Is the host metadata service running?z'Got "invalid command".  Flush complete.)r=r>rhr�r�rfr��warning)r2r�rzr3r3r4r�Js8






z!JoyentMetadataSerialClient._flushcCsd|jj|j|jfS)Nz%s(device=%s, timeout=%s))r�rar r�)r2r3r3r4r�qsz#JoyentMetadataSerialClient.__repr__)
rarbrcr[r$r?rKr�r�r�r3r3)r�r4r�5s

'r�csNeZdZdZd�fdd�	Zddd�Zd�fd	d
�	Zddd�Zdd
d�Z�Z	S)� JoyentMetadataLegacySerialClienta�V1 of the protocol was not safe for all values.
    Thus, we allowed the user to pass values in as base64 encoded.
    Users may still reasonably expect to be able to send base64 data
    and have it transparently decoded.  So even though the V2 format is
    now used, and is safe (using base64 itself), we keep legacy support.

    The way for a user to do this was:
      a.) specify 'base64_keys' key whose value is a comma delimited
          list of keys that were base64 encoded.
      b.) base64_all: string interpreted as a boolean that indicates
          if all keys are base64 encoded.
      c.) set a key named b64-<keyname> with a boolean indicating that
          <keyname> is base64 encoded.r�Ncs(tt|�}|j|||�d|_d|_dS)N)r�r�r$rr)r2r r�r8�s)r�r3r4r$�s
z)JoyentMetadataLegacySerialClient.__init__FcCs�|rd|_d|_d}|jdkrH|j�}d|krBtj|jd��|_nd|_|jrRdS|jdkr�|dkrl|j�}t�}d|kr�t|jd�jd��}xDdd�|D�D]2}tj|j|��r�|j|�q�||kr�|j	|�q�W||_dS)NrFr�,cSs"g|]}|jd�r|dd��qS)zb64-�N)�
startswith)r��kr3r3r4r��szFJoyentMetadataLegacySerialClient._init_base64_keys.<locals>.<listcomp>)
rrr�rZis_true�_get�setr��add�remove)r2�reset�keysZb64_keysr�r3r3r4�_init_base64_keys�s.

z2JoyentMetadataLegacySerialClient._init_base64_keyscstt|�j|||d�S)N)r�rC)r�r�rN)r2r�r�rC)r�r3r4r��s
z%JoyentMetadataLegacySerialClient._getcCs,|tkrdS|j|d�|jr"dS||jkS)NF)r�T)�NO_BASE64_DECODEr�rr)r2r�r�r3r3r4�is_b64_encoded�sz/JoyentMetadataLegacySerialClient.is_b64_encodedcCsxt�}|j|d|d�}||kr"|S|j|�rhytj|j��j�}Wn$tjk
rft	j
d||�YnX|rt|j�}|S)NF)rCr�z#Failed base64 decoding key '%s': %s)�objectr�r�r�Z	b64decoderkryrj�Errorr=r�rC)r2r�r�rCZmdefaultr�r3r3r4rN�s
z$JoyentMetadataLegacySerialClient.get)r�N)F)NF)F)NF)
rarbrcr�r$r�r�r�rNr�r3r3)r�r4r�ys

"

r�cCsV|dkrt|�}|dkrdS|tkr2t|||d�S|tkrFt||d�Std|��dS)N)r r�r8)r�r8z"Unknown value for smartos_type: %s)r:r[r�r�r��
ValueError)r8rrr�
uname_versionr3r3r4r;�s
r;cCs~ddd|g}d}y tj|�\}}tjd||�Wn8tjk
rh}ztjtd||f�WYdd}~XnX|dkrvdS|j�S)N�filez--briefz--mime-typezscript %s mime type is %sz%Failed to identify script type for %s)rr=r>ZProcessExecutionErrorr�logexcrC)rE�cmd�f_typeZ_err�er3r3r4�
identify_file�s"r��cCs|rtjj|�rtj|�|r6tjj|�r6tj|�|s>dStj|||d�|r�|jd�r�t|�}|dkr�tj|dj	d|g�|d�t
jd|�|�ryHtjj|�r�tj|�|r�tjj|�r�tjtjj
|��tj||�Wn2tk
�r}ztjt
d|�WYdd}~XnXdS)	a
    Write the content to content_f. Under the following rules:
        1. If no content, remove the file
        2. Write the content
        3. If executable and no file magic, add it
        4. If there is a link, create it

    @param content: what to write
    @param content_f: the file name
    @param backup_d: the directory to save the backup at
    @param link: if defined, location to create a symlink to
    @param shebang: if no file magic, set shebang
    @param mode: file mode

    Becuase of the way that Cloud-init executes scripts (no shell),
    a script will fail to execute if does not have a magic bit (shebang) set
    for the file. If shebang=True, then the script will be checked for a magic
    bit and to the SmartOS default of assuming that bash.
    N)rHz#!z
text/plainr�z#!/bin/bashzadded shebang to file %sz$failed establishing content link: %s)r,r-r?�unlink�islinkrZ
write_filer�r�r.r=r>Z
ensure_dir�dirname�symlink�IOErrorr�)ZcontentrErFrGrHr�r�r3r3r4rS�s,


rScCsRtj�}|dkr|d}|dkr$tS|dkr8tjd�}n|}|rN|jd�rNtSdS)Nr�zBrandZ virtual linuxzsystem-product-nameZSmartDC)r,�unamer�rZ
read_dmi_datar�r[)r�Zproduct_namer�Zsystem_typer3r3r4r:,sr:c
svddddddgddd	d
ddd
ddg	ddgd��|rHt|ttf�sL|g}ng}|rft|ttf�sj|g}ng}|srg}dd�}dd�}|dd�|dd�d��g}�x�|D�]�}t�fdd�|j�D��}|jd|dd��d|kr�|jd|di�g}	�x>|jdg�D�],}
|
d k�r"dd!i}�ng}t�fd"d�|j�D��}|jd#|
d$��||
��r^d%nd&�d'|k�r�|jd'd(��rԈ�d)�sԇ�fd*d+�|jd,g�D�}
t|
��r�|
d-��d)<|jd��d)i�xR|D]J}t�fd.d�|j�D��}|jd|d/i�|j|�|jd
|i��q�W|	j|��qW|jd|	i�|j|�q�W|�rl|jd0||d1��d2|d3�S)4aReturn a dictionary of network_config by parsing provided
       SMARTOS sdc:nics configuration data

    sdc:nics data is a dictionary of properties of a nic and the ip
    configuration desired.  Additional nic dictionaries are appended
    to the list.

    Converting the format is straightforward though it does include
    duplicate information as well as data which appears to be relevant
    to the hostOS rather than the guest.

    For each entry in the nics list returned from query sdc:nics, we
    create a type: physical entry, and extract the interface properties:
    'mac' -> 'mac_address', 'mtu', 'interface' -> 'name'.  The remaining
    keys are related to ip configuration.  For each ip in the 'ips' list
    we create a subnet entry under 'subnets' pairing the ip to a one in
    the 'gateways' list.

    Each route in sdc:routes is mapped to a route on each interface.
    The sdc:routes properties 'dst' and 'gateway' map to 'network' and
    'gateway'.  The 'linklocal' sdc:routes property is ignored.
    Zmac_addressZmturYZparams�subnets�type�addressZ	broadcastZdns_nameserversZ
dns_searchZmetricZpointopointrZscopeZnetworkZgateway)�physical�subnet�routecSsd|kS)N�.r3)�addrr3r3r4�
is_valid_ipv4�sz3convert_smartos_network_data.<locals>.is_valid_ipv4cSsd|kS)N�:r3)r�r3r3r4�
is_valid_ipv6�sz3convert_smartos_network_data.<locals>.is_valid_ipv6N)rp�gw)�ipv4�ipv6c3s&|]\}}|�dkr||fVqdS)r�Nr3)r�r��v)�
valid_keysr3r4�	<genexpr>�sz/convert_smartos_network_data.<locals>.<genexpr>r�Z	interface)r�rYZmacZipsZdhcpZdhcp4c3s&|]\}}|�dkr||fVqdS)r�Nr3)r�r�r�)r�r3r4r��sZstatic)r�r�r�r�ZprimaryFr�cs g|]}��d|�r|�qS)rpr3)r�r�)�pgws�protor3r4r��sz0convert_smartos_network_data.<locals>.<listcomp>�gatewaysrc3s&|]\}}|�dkr||fVqdS)r�Nr3)r�r�r�)r�r3r4r��s�dstZ
nameserver)r�r��searchr|)�version�config)	�
isinstancer��tuple�dictrM�updaterNrsr)r*rrrr�r�r�ZnicZcfgr�Zipr�Z	routeentsr�r�Zrcfgr3)r�r�r�r4r_Bs�







r_cCstj|t�S)N)rZlist_from_depends�datasources)Zdependsr3r3r4�get_datasource_list�sr��__main__zDo not appear to be on smartos.r|r`cCs�||kr||S|tkr0t|}|j|�||<nz|dkrxxd	D]}t|||�q>Wt|d|d|d|dd�||<n2|tkr�t|\}}n
|d}}|j||d�||<||S)
Nr`�network-datarrr)r*rrrF)rC)r�rrr)rOrP�load_keyr_rLrN)�clientr�rDZkeynameZdepkeyrCr3r3r4r��s,
r�)r�r�rDr��: )�indentZ	sort_keysZ
separators)r	T)r
T)rT)rF)r
F)rF)rT)rT)rT)rF)rF)rT)rT)NFr�)NN)NNNN)r�r�)Cr�rjr�r�r�Zloggingr,r�r�r�r�Z	cloudinitrrrrrZcloudinit.eventrrZ	getLoggerrar=rLrOr�r[ZDS_NAMEr'r�ZMETADATA_SOCKFILErWZSERIAL_TIMEOUTr(r\rTrRr#r!�	Exceptionrerfrgr�r�r�r;r�rSr:r_ZDEP_FILESYSTEMr�r��sysZjmc�print�exitrs�argvr�r�r�rDr�r��dumpsr3r3r3r4�<module>s�
)G0DY
2

 


 


Filemanager

Name Type Size Permission Actions
DataSourceAkamai.cpython-36.opt-1.pyc File 8.18 KB 0644
DataSourceAkamai.cpython-36.pyc File 8.18 KB 0644
DataSourceAliYun.cpython-36.opt-1.pyc File 3.22 KB 0644
DataSourceAliYun.cpython-36.pyc File 3.22 KB 0644
DataSourceAltCloud.cpython-36.opt-1.pyc File 6.74 KB 0644
DataSourceAltCloud.cpython-36.pyc File 6.74 KB 0644
DataSourceAzure.cpython-36.opt-1.pyc File 47.95 KB 0644
DataSourceAzure.cpython-36.pyc File 47.95 KB 0644
DataSourceBigstep.cpython-36.opt-1.pyc File 1.84 KB 0644
DataSourceBigstep.cpython-36.pyc File 1.84 KB 0644
DataSourceCloudSigma.cpython-36.opt-1.pyc File 3.62 KB 0644
DataSourceCloudSigma.cpython-36.pyc File 3.62 KB 0644
DataSourceCloudStack.cpython-36.opt-1.pyc File 5.97 KB 0644
DataSourceCloudStack.cpython-36.pyc File 5.97 KB 0644
DataSourceConfigDrive.cpython-36.opt-1.pyc File 8.18 KB 0644
DataSourceConfigDrive.cpython-36.pyc File 8.18 KB 0644
DataSourceDigitalOcean.cpython-36.opt-1.pyc File 3.65 KB 0644
DataSourceDigitalOcean.cpython-36.pyc File 3.65 KB 0644
DataSourceEc2.cpython-36.opt-1.pyc File 23.49 KB 0644
DataSourceEc2.cpython-36.pyc File 23.49 KB 0644
DataSourceExoscale.cpython-36.opt-1.pyc File 5.92 KB 0644
DataSourceExoscale.cpython-36.pyc File 5.92 KB 0644
DataSourceGCE.cpython-36.opt-1.pyc File 9.83 KB 0644
DataSourceGCE.cpython-36.pyc File 9.93 KB 0644
DataSourceHetzner.cpython-36.opt-1.pyc File 3.78 KB 0644
DataSourceHetzner.cpython-36.pyc File 3.78 KB 0644
DataSourceIBMCloud.cpython-36.opt-1.pyc File 12.44 KB 0644
DataSourceIBMCloud.cpython-36.pyc File 12.44 KB 0644
DataSourceLXD.cpython-36.opt-1.pyc File 13.31 KB 0644
DataSourceLXD.cpython-36.pyc File 13.31 KB 0644
DataSourceMAAS.cpython-36.opt-1.pyc File 11.86 KB 0644
DataSourceMAAS.cpython-36.pyc File 11.86 KB 0644
DataSourceNWCS.cpython-36.opt-1.pyc File 3.77 KB 0644
DataSourceNWCS.cpython-36.pyc File 3.77 KB 0644
DataSourceNoCloud.cpython-36.opt-1.pyc File 7.97 KB 0644
DataSourceNoCloud.cpython-36.pyc File 7.97 KB 0644
DataSourceNone.cpython-36.opt-1.pyc File 1.47 KB 0644
DataSourceNone.cpython-36.pyc File 1.47 KB 0644
DataSourceOVF.cpython-36.opt-1.pyc File 9.15 KB 0644
DataSourceOVF.cpython-36.pyc File 9.15 KB 0644
DataSourceOpenNebula.cpython-36.opt-1.pyc File 11.75 KB 0644
DataSourceOpenNebula.cpython-36.pyc File 11.75 KB 0644
DataSourceOpenStack.cpython-36.opt-1.pyc File 7.91 KB 0644
DataSourceOpenStack.cpython-36.pyc File 7.91 KB 0644
DataSourceOracle.cpython-36.opt-1.pyc File 10.99 KB 0644
DataSourceOracle.cpython-36.pyc File 10.99 KB 0644
DataSourceRbxCloud.cpython-36.opt-1.pyc File 7.19 KB 0644
DataSourceRbxCloud.cpython-36.pyc File 7.19 KB 0644
DataSourceScaleway.cpython-36.opt-1.pyc File 10.84 KB 0644
DataSourceScaleway.cpython-36.pyc File 10.84 KB 0644
DataSourceSmartOS.cpython-36.opt-1.pyc File 24.51 KB 0644
DataSourceSmartOS.cpython-36.pyc File 24.51 KB 0644
DataSourceUpCloud.cpython-36.opt-1.pyc File 4.36 KB 0644
DataSourceUpCloud.cpython-36.pyc File 4.36 KB 0644
DataSourceVMware.cpython-36.opt-1.pyc File 23.66 KB 0644
DataSourceVMware.cpython-36.pyc File 23.66 KB 0644
DataSourceVultr.cpython-36.opt-1.pyc File 3.44 KB 0644
DataSourceVultr.cpython-36.pyc File 3.44 KB 0644
__init__.cpython-36.opt-1.pyc File 30.52 KB 0644
__init__.cpython-36.pyc File 30.52 KB 0644