<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;color:#3d85c6">Hi Sean</div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;color:#3d85c6"><br>
</div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;color:#3d85c6">I will join the Neutron IRC, get the inputs and address them at the earliest. </div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;color:#3d85c6">
<br></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;color:#3d85c6">I like to know the requirements for J & K release cycles and what other open source reference plugins have done towards this. We need to ramp up our resources on ipv6 support.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Aug 24, 2014 at 12:18 PM, Collins, Sean <span dir="ltr"><<a href="mailto:Sean_Collins2@cable.comcast.com" target="_blank">Sean_Collins2@cable.comcast.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">




<div>
<div style="direction:ltr;font-family:Tahoma;color:#000000;font-size:10pt">Hi,<br>
<br>
The amount of tests that we are having to add skips to for the One Convergence plugin has grown quite a bit lately.
<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/unit/oneconvergence/test_nvsd_plugin.py#n58" target="_blank">http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/unit/oneconvergence/test_nvsd_plugin.py#n58</a><br>

<br>
This is the only plugin that inherits from the NeutronDbPluginV2 class and has completely disabled creating Subnets that have an ip_version of 6.<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/oneconvergence/plugin.py#n228" target="_blank">http://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/oneconvergence/plugin.py#n228</a><br>

<br>
I hate to single out this plugin. Before this development cycle, open source plugins would allow the creation of Subnets with ip_version set to 6, and then have lots of bugs which would prevent any instances from actually obtaining IPv6 addresses and routing.
 But we didn't have to explicitly skip tests every time someone wanted to fix bugs - like the following patch.<br>
<br>
<a href="https://review.openstack.org/#/c/116317/" target="_blank">https://review.openstack.org/#/c/116317/</a><br>
<br>
Also, I want to highlight some meeting minutes, where it was discussed that in the K release, all plugins will be required to support IPv6. I hope we can discuss this, build consensus, and ensure that the K release requirement is reasonable.<br>

<br>
<a href="http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-07-14-21.02.html" target="_blank">http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-07-14-21.02.html</a><br>
<br>
<div>
<div style="font-family:Tahoma;font-size:13px">Sean M. Collins<br>
</div>
</div>
</div>
</div>

<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><br>Thanks<br>OSM<br>(Subrahmanyam Ongole)<br>
</div>