Add an "IPv6 Impact" section to the template

This change adds a requirement for an "IPv6 Impact" section. In the review for
Kilo priorities [1], the issue was raised around IPv6 being a priority. One
outcome was the thought to ensure new features are IPv6 ready from the start.
This change ensures specs have a section detailing how they affect IPv6.

I've also updated approved specs with what I perceive to be their IPv6
readiness. I hope the original authors can view these to confirm what I've
put in there.

[1] https://review.openstack.org/#/c/136514/

Change-Id: I6b12615d5d650ea55b8e78fd43c702af8f87b3f7

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
 ---------------------
 

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
 ---------------------
 

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
 ---------------------
 

specs/kilo/dummy.rst

@@ -41,6 +41,10 @@ Performance Impact
 ------------------
 
 
+IPv6 Impact
+-----------
+
+
 Other Deployer Impact
 ---------------------
 

specs/kilo/guru-meditation-report.rst

@@ -84,6 +84,11 @@ Performance Impact
 
 None.
 
+IPv6 Impact
+-----------
+
+None.
+
 Other Deployer Impact
 ---------------------
 

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

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
 ---------------------
 

specs/kilo/ofagent-bridge-setup.rst

@@ -73,6 +73,11 @@ Performance Impact
 
 none
 
+IPv6 Impact
+-----------
+
+none
+
 Other Deployer Impact
 ---------------------
 

specs/skeleton.rst

@@ -41,6 +41,10 @@ Performance Impact
 ------------------
 
 
+IPv6 Impact
+-----------
+
+
 Other Deployer Impact
 ---------------------
 

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
 ---------------------
 

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])