diff options
| author | Chad Smith <chad.smith@canonical.com> | 2020-03-18 13:33:37 -0600 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-03-18 15:33:37 -0400 |
| commit | 6600c642af3817fe5e0170cb7b4eeac4be3c60eb (patch) | |
| tree | 9c33a76d7d9e758bdb47c5b856074dd86899dd74 /systemd/cloud-config.service.tmpl | |
| parent | 024bf27b5a3880dac916431296cb871707923562 (diff) | |
| download | vyos-cloud-init-6600c642af3817fe5e0170cb7b4eeac4be3c60eb.tar.gz vyos-cloud-init-6600c642af3817fe5e0170cb7b4eeac4be3c60eb.zip | |
ec2: render network on all NICs and add secondary IPs as static (#114)
Add support for rendering secondary static IPv4/IPv6 addresses on
any NIC attached to the machine. In order to see secondary IP
addresses in Ec2 IMDS network config, cloud-init now reads metadata
version 2018-09-24. Metadata services which do not support the Ec2
API version will not get secondary IP addresses configured.
In order to discover secondary IP address config, cloud-init now
relies on metadata API Parse local-ipv4s, ipv6s,
subnet-ipv4-cidr-block and subnet-ipv6-cidr-block metadata keys to
determine additional IPs and appropriate subnet prefix to set for a
nic.
Also add the datasource config option apply_full_imds_netork_config
which defaults to true to allow cloud-init to automatically configure
secondary IP addresses. Setting this option to false will tell
cloud-init to avoid setting up secondary IP addresses.
Also in this branch:
- Shift Ec2 datasource to emit network config v2 instead of v1.
LP: #1866930
Diffstat (limited to 'systemd/cloud-config.service.tmpl')
0 files changed, 0 insertions, 0 deletions