diff options
author | Chad Smith <chad.smith@canonical.com> | 2018-08-17 20:24:58 +0000 |
---|---|---|
committer | Server Team CI Bot <josh.powers+server-team-bot@canonical.com> | 2018-08-17 20:24:58 +0000 |
commit | 47548df9ded4ad4088d3d846f1876b29b16aa7d1 (patch) | |
tree | 2518ce7708e80f1df883fc525047e14e42ee7de1 /tools/ds-identify | |
parent | 51f49dc1da0c045d01ddc977874c9bed70cb510f (diff) | |
download | vyos-cloud-init-47548df9ded4ad4088d3d846f1876b29b16aa7d1.tar.gz vyos-cloud-init-47548df9ded4ad4088d3d846f1876b29b16aa7d1.zip |
azure: allow azure to generate network configuration from IMDS per boot.
Azure datasource now queries IMDS metadata service for network
configuration at link local address
http://169.254.169.254/metadata/instance?api-version=2017-12-01. The
azure metadata service presents a list of macs and allocated ip addresses
associated with this instance. Azure will now also regenerate network
configuration on every boot because it subscribes to EventType.BOOT
maintenance events as well as the 'first boot'
EventType.BOOT_NEW_INSTANCE.
For testing add azure-imds --kind to cloud-init devel net_convert tool
for debugging IMDS metadata.
Also refactor _get_data into 3 discrete methods:
- is_platform_viable: check quickly whether the datasource is
potentially compatible with the platform on which is is running
- crawl_metadata: walk all potential metadata candidates, returning a
structured dict of all metadata and userdata. Raise InvalidMetaData on
error.
- _get_data: call crawl_metadata and process results or error. Cache
instance data on class attributes: metadata, userdata_raw etc.
Diffstat (limited to 'tools/ds-identify')
0 files changed, 0 insertions, 0 deletions