o w7exD @sbdZddlZddlZddlZddlZddlmZmZddlm Z ddl m Z m Z m Z mZmZmZmZddlZddlmZddlmZddlmZdd lmZdd lmZdd lmZmZmZm Z dd l!m"Z"e#e$Z%d Z&dZ'dZ(dddddddZ)de*fddZ+ d=dee e*de e*e ffddZ,GdddeZ-GdddeZ.GdddeZ/d e*de0fd!d"Z1Gd#d$d$ej2Z3de4fd%d&Z5 'd>d(ej6d)e*d*e4fd+d,Z7 'd>d(ej6d)e*d*e4dej8fd-d.Z9Gd/d0d0eZ:Gd1d2d2Z;e'e:jffgZ?d7d8Z@e$d9kr/ddlAZAd:ZBeAjCeBd;ZDeDEeFeGe=e:js  z0DataSourceLXD.network_config..z8LXD datasource generating network config using fallback.) rqrUNSETrrrrerfrr*r@itemsrBr )rKrr3r3r4network_configs(          zDataSourceLXD.network_config)rVrWrXdsnamerrrqr rstr__annotations__rr DataSourcertr rwintrv staticmethodboolryrrrpropertyrfrrYr3r3rLr4ros"   rocCs"tjtrtttjSdS)z=Return True when this platform appears to have an LXD socket.F)ospathexistsr^statS_ISSOCKlstatst_moder3r3r3r4rxs rxTsessionr_do_raisec Csft|||}|jstd||j|jiSz|WSty2}z t dj ||jd|d}~ww)NSkipping %s on [HTTP:%d]:%szFUnable to process LXD config at {url}. Expected JSON but found: {resp})r_resp) _do_requestokr*r@ status_codetextjsonrrrirj)rr_r url_responsermr3r3r4_get_json_responses,  rcCs|tdddD]}||}d|jkr!tdtd|j||qtd|j||r<|js      z_MetaDataReader._process_configrcCstQ}||jtd|ji}tj|vr&t |jd}t ||j |d<tj |vr3| ||tj|vrLt |jd}t||dd}|rL||d<|WdS1sXwYdS)N_metadata_api_versionr}rFr)requestsSessionmountrr]rrrrrrrrupdaterrr)rKrrrmd_router_rr3r3r4__call__s"     $z_MetaDataReader.__call__N) rVrWrXrrrHrrrfrrrr3r3r3r4rRs7rrrcCst|d|dS)a8Fetch metadata from the /dev/lxd/socket routes. Perform a number of HTTP GETs on known routes on the devlxd socket API. Minimally all containers must respond to /meta-data when the LXD configuration setting `security.devlxd` is true. When `security.devlxd` is false, no /dev/lxd/socket file exists. This datasource will return False from `is_platform_viable` in that case. Perform a GET of /config` and walk all `user.*` configuration keys, storing all keys and values under a dict key LXD_SOCKET_API_VERSION: config {...}. In the presence of the following optional user config keys, create top level aliases: - user.user-data -> user-data - user.vendor-data -> vendor-data - user.network-config -> network-config :param api_version: LXD API version to operated with. :param metadata_keys: Instance of `MetaDataKeys` indicating what keys to fetch. :return: A dict with the following optional keys: meta-data, user-data, vendor-data, network-config, network_mode, devices. Below is a dict representation of all raw configuration keys and values provided to the container surfaced by the socket under the /1.0/config/ route. )rr)r)rrr3r3r4rs#rcCs t|tSrO)rlist_from_depends datasources)dependsr3r3r4get_datasource_lists r__main__z*Query LXD metadata and emit a JSON object.) descriptionrrO)T)H__doc__rrPrrenumrr json.decoderrtypingrrrrr r r rrequests.adaptersr urllib3.connectionr urllib3.connectionpoolr cloudinitrrloggingrrrr cloudinit.netr getLoggerrVr*r^rrrrr5rBrDr[r]rfrnrrorrxrrResponserrrrrDEP_FILESYSTEMrrargparserArgumentParserparser parse_argsprint json_dumpsr3r3r3r4s  $           &  j  Q *