summaryrefslogtreecommitdiff
path: root/tests/unittests/test_reporting_hyperv.py
diff options
context:
space:
mode:
authorDaniel Watkins <daniel@daniel-watkins.co.uk>2019-08-14 20:44:50 +0000
committerServer Team CI Bot <josh.powers+server-team-bot@canonical.com>2019-08-14 20:44:50 +0000
commit0e79a1b89287358a77fe31fb82c4bcd83ff48894 (patch)
tree56e23c8afea52a212e6e0eb5ce4d829119e6592a /tests/unittests/test_reporting_hyperv.py
parentb2d4dfe78e242d74471062e56a8b072d95f698bf (diff)
downloadvyos-cloud-init-0e79a1b89287358a77fe31fb82c4bcd83ff48894.tar.gz
vyos-cloud-init-0e79a1b89287358a77fe31fb82c4bcd83ff48894.zip
DataSourceOracle: configure secondary NICs on Virtual Machines
Oracle Cloud Infrastructure's Instance Metadata Service provides network configuration information for non-primary NICs. This commit introduces support, on Virtual Machines[0], for fetching that network metadata, converting it to v1 network-config[1] and combining it into the network configuration generated for the primary interface. By default, this behaviour is not enabled. Configuring the Oracle datasource to `configure_secondary_nics` enables it: datasource: Oracle: configure_secondary_nics: true Failures to fetch and generate secondary NIC configuration will log a warning, but otherwise will not affect boot. [0] The expected use of the IMDS-provided network configuration is substantially different on Bare Metal Machines, so support for that will be addressed separately. [1] This is v1 config, because cloudinit.net.cmdline generates v1 config and we need to integrate the secondary NICs into that configuration.
Diffstat (limited to 'tests/unittests/test_reporting_hyperv.py')
0 files changed, 0 insertions, 0 deletions