diff --git a/specs/kilo/agent-child-processes-status.rst b/specs/kilo/agent-child-processes-status.rst index 6630d25ed..51b28512e 100644 --- a/specs/kilo/agent-child-processes-status.rst +++ b/specs/kilo/agent-child-processes-status.rst @@ -159,6 +159,12 @@ Polling isn't ideal, but the alternatives aren't either, and we need a solution for this problem, specially for HA environments. +IPv6 Impact +----------- + +No effect on IPv6 expected here. + + Other Deployer Impact --------------------- diff --git a/specs/kilo/cisco-vpnaas-and-router-integration.rst b/specs/kilo/cisco-vpnaas-and-router-integration.rst index 16dc674d7..219495246 100644 --- a/specs/kilo/cisco-vpnaas-and-router-integration.rst +++ b/specs/kilo/cisco-vpnaas-and-router-integration.rst @@ -104,6 +104,12 @@ Wall clock time to create a VPN connection improves, as the Neutron commands will take all needed actions (no manual INI file changes needed). +IPv6 Impact +----------- + +This is expected to work in an IPv6 environment. + + Other Deployer Impact --------------------- diff --git a/specs/kilo/drop-rpc-compat.rst b/specs/kilo/drop-rpc-compat.rst index c2e9f4e4c..d6b50738b 100644 --- a/specs/kilo/drop-rpc-compat.rst +++ b/specs/kilo/drop-rpc-compat.rst @@ -148,6 +148,11 @@ Negligible. In theory, this is removing a compatibility layer so there should be less code, but the overall performance impact of removing the layer is negligible in the broader scope of things. +IPv6 Impact +----------- + +None + Other Deployer Impact --------------------- diff --git a/specs/kilo/dummy.rst b/specs/kilo/dummy.rst index 6cc37b617..11530074c 100644 --- a/specs/kilo/dummy.rst +++ b/specs/kilo/dummy.rst @@ -41,6 +41,10 @@ Performance Impact ------------------ +IPv6 Impact +----------- + + Other Deployer Impact --------------------- diff --git a/specs/kilo/guru-meditation-report.rst b/specs/kilo/guru-meditation-report.rst index 5f7cc2bba..3829f4a97 100644 --- a/specs/kilo/guru-meditation-report.rst +++ b/specs/kilo/guru-meditation-report.rst @@ -84,6 +84,11 @@ Performance Impact None. +IPv6 Impact +----------- + +None. + Other Deployer Impact --------------------- diff --git a/specs/kilo/ml2-cisco-nexus-md-prov-segment.rst b/specs/kilo/ml2-cisco-nexus-md-prov-segment.rst index f06722f31..9efa072ed 100644 --- a/specs/kilo/ml2-cisco-nexus-md-prov-segment.rst +++ b/specs/kilo/ml2-cisco-nexus-md-prov-segment.rst @@ -74,6 +74,11 @@ Performance Impact ------------------ None +IPv6 Impact +----------- + +None + Other Deployer Impact --------------------- In addition to the core cisco provider segment control plane code being ported diff --git a/specs/kilo/ml2-n1kv-mechanism-driver.rst b/specs/kilo/ml2-n1kv-mechanism-driver.rst index e98612f0f..2c488af1f 100644 --- a/specs/kilo/ml2-n1kv-mechanism-driver.rst +++ b/specs/kilo/ml2-n1kv-mechanism-driver.rst @@ -134,6 +134,11 @@ Performance Impact The performance of Cisco N1KV ML2 mechanism driver will depend on the responsiveness of the VSM. +IPv6 Impact +----------- + +None. + Other Deployer Impact --------------------- diff --git a/specs/kilo/ofagent-bridge-setup.rst b/specs/kilo/ofagent-bridge-setup.rst index c5ce22eef..412fb8526 100644 --- a/specs/kilo/ofagent-bridge-setup.rst +++ b/specs/kilo/ofagent-bridge-setup.rst @@ -73,6 +73,11 @@ Performance Impact none +IPv6 Impact +----------- + +none + Other Deployer Impact --------------------- diff --git a/specs/skeleton.rst b/specs/skeleton.rst index 6cc37b617..11530074c 100644 --- a/specs/skeleton.rst +++ b/specs/skeleton.rst @@ -41,6 +41,10 @@ Performance Impact ------------------ +IPv6 Impact +----------- + + Other Deployer Impact --------------------- diff --git a/specs/template.rst b/specs/template.rst index f03795b93..7e9c97fbd 100644 --- a/specs/template.rst +++ b/specs/template.rst @@ -210,6 +210,19 @@ Examples of things to consider here include: * Will the change include any locking, and if so what considerations are there on holding the lock? +IPv6 Impact +----------- + +Describe if this change will have an effect on IPv6 in Neutron. You should also +document here how your change will work with the existing IPv6 infrastructure +in Neutron. + +* Does this change work with IPv6? + +* Does this change require Neutron changes to facilitate working with IPv6? + +* Describe how this change will work when deployed with IPv6 tenant networks. + Other Deployer Impact --------------------- diff --git a/tests/test_titles.py b/tests/test_titles.py index 4cad32dae..f5d8a2dbd 100644 --- a/tests/test_titles.py +++ b/tests/test_titles.py @@ -64,6 +64,7 @@ class TestTitles(testtools.TestCase): self.assertIn('Notifications Impact', titles[proposed]) self.assertIn('Other End User Impact', titles[proposed]) self.assertIn('Performance Impact', titles[proposed]) + self.assertIn('IPv6 Impact', titles[proposed]) self.assertIn('Other Deployer Impact', titles[proposed]) self.assertIn('Developer Impact', titles[proposed]) self.assertIn('Community Impact', titles[proposed])