Red Hat Bugzilla – Bug 1330217
[RFE] Enable configuring IPv6 in VM cloud-init
Last modified: 2018-03-29 06:46:36 EDT
Enable configuring IPv6 properties for VM cloud-init in the similar way that is done in host setup network flow. Here are the fields to be added: * IPv6 address * IPv6 prefix (0-128) * IPv6 gateway * IPv6 boot protocol (all IPv4 values + autoconf)
as discussed offline, moving to networking. Note: we don't want to reimplement a full cloud-init provisioning tool, rather we want to provide the most common things to configure. Your call which they are in context of network provisioning. Detailed/obscure/uncommon things are handled by a passthrough of custom configuration file
doc change for this featurelet: https://github.com/oVirt/ovirt-site/pull/820
Check with: oVirt Engine Version: 4.2.0-0.0.master.20170609091031.gitc86d08a.el7.centos cloud-init: cloud-init-0.7.2-3.el7.noarch found problem with Static IPv6 address with subnet prefix and gateway Fill BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1462654
Apparently, Fedora and CentOS's cloud-init does not handle our meta_data.json properly. We need to render it differently so it works well.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
the existing documentation for network interfaces is very limited. https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html-single/virtual_machine_management_guide/#sect-Using_Cloud-Init_to_Automate_the_Configuration_of_Virtual_Machines """ 11. Select the Network check box and use the + and - buttons to add or remove network interfaces to or from the virtual machine. """ is all we have. Before documenting IPv6 support, we need to document how in-guest networking is configured at all. Most important bit to add is that when selecting "+" the user must specify the in-guest name of the network interface card he or she would like to configure (e.g. eth0). Then, it may be worthwhile adding that IPv4 and IPv6 boot protocol and addresses for the guest may be specified.
moving this back to development as cloud-init team requests that we align with openstack protocol on the dhcp names in network_data.json (should be ipv4_dhcp and ipv6_dhcp). see notes in BZ1519271.
aligned with ipvX_dhcp notation of openstack. added blocker: 1519271
return to status 'modified' because there is not d/s for this for now.
Verified on RHEV 4.2.2.1-0.1.el7 using cloud-init 0.7.9-23 Run full test plan
Tested according to https://polarion.engineering.redhat.com/polarion/#/project/RHEVM3/wiki/Compute/Cloud_init_IPv6
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.