OVS: Add support for IPv6 addresses as tunnel endpoints
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Invalid
|
Low
|
Unassigned | ||
openstack-manuals |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
https:/
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.
commit 773394a1887bec6
Author: Frode Nordahl <email address hidden>
Date: Mon Dec 14 13:51:48 2015 +0100
OVS: Add support for IPv6 addresses as tunnel endpoints
Remove IPv4 restriction for local_ip configuration statement.
Check for IP version mismatch of local_ip and remote_ip before creating
tunnel.
Create hash of remote IPv6 address for OVS interface/port name with least
posibility for collissions.
Fix existing tests that fail because of the added check for IP version
and subsequently valid IP addresses in _setup_tunnel_port.
DocImpact
Change-Id: I9ec137ef8c688b
Closes-Bug: #1525895
Changed in neutron: | |
status: | New → Confirmed |
Changed in openstack-manuals: | |
status: | New → Confirmed |
Changed in openstack-manuals: | |
assignee: | Rohit Agarwalla (rohitagarwalla) → nobody |
status: | In Progress → Confirmed |
Not sure if I should be the owner since I did most of the later work on this change.
The change on docs.openstack.org really just need to mention either address family is possible, I didn't actually find any place where it said "IPv4 only". So matching the config.py change I made the setting could be described like this:
local_ip - Local IP address of tunnel endpoint. Can be either an IPv4 or IPv6 address.