Stephen Finucane
c0aef97c49
Nova supports file injection of network templates. Putting these in a config drive is the only way to configure networking without DHCP. At present, setting the 'use_ipv6' config option to False prevents the generation of IPv6 network info, even if there are IPv6 networks available. This was fine when using nova-network, where the same config option is used to control generation of these subnets. However, a mismatch between this nova option and equivalent IPv6 options in neutron would result in IPv6 packets being dropped. Seeing as there is apparent reason for not including IPv6 network info when IPv6 capable networks are present, we can ignore this option. Instead, we include info for all available networks in the template, be they IPv4 or IPv6. Change-Id: I188fc2cd1b26fe7a71804f7e7d66b111d6f15e30 Implements: blueprint centralize-config-options-pike
20 lines
925 B
YAML
20 lines
925 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
Injected network templates will now ignore the ``use_ipv6`` config option.
|
|
|
|
Nova supports file injection of network templates. Putting these in a
|
|
config drive is the only way to configure networking without DHCP.
|
|
|
|
Previously, setting the ``use_ipv6`` config option to ``False`` prevented
|
|
the generation of IPv6 network info, even if there were IPv6 networks
|
|
available. This was fine when using nova-network, where the same config
|
|
option is used to control generation of these subnets. However, a mismatch
|
|
between this nova option and equivalent IPv6 options in neutron would
|
|
have resulted in IPv6 packets being dropped.
|
|
|
|
Seeing as there was no apparent reason for not including IPv6 network info
|
|
when IPv6 capable networks are present, we now ignore this option.
|
|
Instead, we include info for all available networks in the template, be
|
|
they IPv4 or IPv6.
|