<font size=2 face="sans-serif">Hi Ian and Vish,</font>
<br>
<br><font size=2 face="sans-serif">Thanks for your reply. From your response,
I still have some questions, hope you can help me to clear up them.</font>
<br>
<br><font size=2 face="sans-serif"><1> From Vish's response, may
I believe that static IPv6 injection using the interface.template will
be dropped in future because it is not a correct way to do net config as
you said?</font>
<br>
<br><font size=2 face="sans-serif"><2> If we still use the interface.template
to do net config, we'd better put it into metadata server, right?</font>
<br>
<br><font size=2 face="sans-serif"><3> If these two assumption above
are correct, my question is we still need to prepare some special ENV such
as images with cloud-init to run this tempest case </font><a href=https://review.openstack.org/#/c/58721/><font size=3 color=blue><u>https://review.openstack.org/#/c/58721/</u></font></a><font size=2 face="sans-serif">,
is it reasonable to be accepted by community? Is it the correct direction
to submit case for IPv6? How should I ask community to prepare the this
special ENV£¿</font>
<br>
<br><font size=2 face="sans-serif">Thanks & Best Regards,<br>
----------------------------------------------------<br>
Yang Yu(ÓÚÑî)<br>
----------------------------------------------------</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Vishvananda Ishaya <vishvananda@gmail.com></b>
</font>
<p><font size=1 face="sans-serif">2013-12-06 02:34</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
"OpenStack Development Mailing List \(not for usage questions\)"
<openstack-dev@lists.openstack.org></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">"OpenStack Development Mailing
List \(not for usage questions\)" <openstack-dev@lists.openstack.org></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [openstack-dev] [Neutron] Interfaces
file format, was [Tempest] Need to prepare
the IPv6 environment for static IPv6 injection
test case</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=3>Hi Ian,</font>
<br>
<br><font size=3>The rendered network template was a legacy item that got
stuck onto the config drive so we could remove file injection. It is not
intended that this is the correct way to do net config. We have intended
in the past to put a generic form of network info into the metadata service
and config drive. Cloud-init can parse this data and have code to set up
networking config on different operating systems.</font>
<br>
<br><font size=3>We actually discussed doing this during the Havana summit,
but no one ever made any progress. There was some debate about whether
there was an existing xml format and someone was going to investigate.
Since this has not happened, I propose we scrap that idea and just produce
the network info in json.</font>
<br>
<br><font size=3>Nova should be able to populate this data from its cached
network info. It might also be nice to stick it in a known location on
the metadata server so the neutron proxy could potentially overwrite it
with more current network data if it wanted to.</font>
<br>
<br><font size=3>Vish</font>
<br>
<br><font size=3>On Dec 4, 2013, at 8:26 AM, Ian Wells <</font><a href=mailto:ijw.ubuntu@cack.org.uk><font size=3 color=blue><u>ijw.ubuntu@cack.org.uk</u></font></a><font size=3>>
wrote:</font>
<br>
<br><font size=3>We seem to have bound our config drive file formats to
those used by the operating system we're running, which doesn't seem like
the right approach to take.<br>
</font>
<br><font size=3>Firstly, the above format doesn't actually work even for
Debian-based systems - if you have a network without ipv6, ipv6 ND will
be enabled on the ipv4-only interfaces, which strikes me as wrong. (This
is a feature of Linux - ipv4 is enabled on interfaces which are specifically
configured with ipv4, but ipv6 is enabled on all interfaces that are brought
up.)<br>
</font>
<br><font size=3>But more importantly, the above file template only works
for Debian-based machines - not Redhat, not Windows, not anything else
- and we seem to have made that a feature of Openstack from the relatively
early days of file injection. That's not an ipv6 only thing but a
general statement. It seems wrong to have to extend Openstack's config
drive injection for every OS that might come along, so is there a way we
can make this work without tying the two things together? Are we
expecting the cloud-init code in whatever OS to parse and understand this
file format, or are they supposed to use other information? In general,
what would the recommendation be for someone using a VM where this config
format is not native?<br>
<br>
-- </font>
<br><font size=3>Ian.</font>
<br><font size=3><br>
</font>
<br><font size=3>On 2 December 2013 03:01, Yang XY Yu <</font><a href=mailto:yuyangbj@cn.ibm.com target=_blank><font size=3 color=blue><u>yuyangbj@cn.ibm.com</u></font></a><font size=3>>
wrote:</font>
<br><font size=3 face="sans-serif">Hi all stackers,</font><font size=3>
<br>
</font><font size=3 face="sans-serif"><br>
Currently Neutron/Nova code has supported the static IPv6 injection, but
there is no tempest scenario coverage to support IPv6 injection test case.
So I finished the test case and run the it successfully in my local environment,
and already submitted the code-review in community: </font><a href=https://review.openstack.org/#/c/58721/ target=_blank><font size=3 color=blue><u>https://review.openstack.org/#/c/58721/</u></font></a><font size=3>,
</font><font size=3 face="sans-serif">but the community Jenkins env has
not supported IPv6 and there are still a few pre-requisites setup below
if running the test case correctly, </font><font size=3><br>
</font><font size=3 face="sans-serif"><br>
1. Special Image needed to support IPv6 by using cloud-init, currently
the cirros image used by tempest does not installed cloud-init.</font><font size=3>
<br>
</font><font size=3 face="sans-serif"><br>
2. Prepare interfaces.template file below on compute node.</font><font size=3>
</font><font size=1 color=#2f2f2f face="Arial"><br>
edit /usr/share/nova/interfaces.template</font><font size=3>
<br>
</font><font size=1 face="Arial"><br>
# Injected by Nova on instance boot</font><font size=3> </font><font size=1 face="Arial"><br>
#</font><font size=3> </font><font size=1 face="Arial"><br>
# This file describes the network interfaces available on your system</font><font size=3>
</font><font size=1 face="Arial"><br>
# and how to activate them. For more information, see interfaces(5).</font><font size=3>
<br>
</font><font size=1 face="Arial"><br>
# The loopback network interface</font><font size=3> </font><font size=1 face="Arial"><br>
auto lo</font><font size=3> </font><font size=1 face="Arial"><br>
iface lo inet loopback</font><font size=3> <br>
</font><font size=1 face="Arial"><br>
{% for ifc in interfaces -%}</font><font size=3> </font><font size=1 face="Arial"><br>
auto {{ </font><a href=http://ifc.name/ target=_blank><font size=1 color=blue face="Arial"><u>ifc.name</u></font></a><font size=1 face="Arial">
}}</font><font size=3> </font><font size=1 face="Arial"><br>
{% if use_ipv6 -%}</font><font size=3> </font><font size=1 face="Arial"><br>
iface {{ </font><a href=http://ifc.name/ target=_blank><font size=1 color=blue face="Arial"><u>ifc.name</u></font></a><font size=1 face="Arial">
}} inet6 static</font><font size=3> </font><font size=1 face="Arial"><br>
address {{ ifc.address_v6 }}</font><font size=3> </font><font size=1 face="Arial"><br>
netmask {{ ifc.netmask_v6 }}</font><font size=3> </font><font size=1 face="Arial"><br>
{%- if ifc.gateway_v6 %}</font><font size=3> </font><font size=1 face="Arial"><br>
gateway {{ ifc.gateway_v6 }}</font><font size=3> </font><font size=1 face="Arial"><br>
{%- endif %}</font><font size=3> </font><font size=1 face="Arial"><br>
{%- endif %}</font><font size=3> <br>
</font><font size=1 face="Arial"><br>
{%- endfor %}</font><font size=3> <br>
<br>
</font><font size=1 face="Arial"><br>
So considering these two pre-requisites, what should be done to enable
this patch for IPv6 injection? Should I open a bug for cirros to enable
cloud-init? Or skip the test case because of this bug ?</font><font size=3>
</font><font size=1 face="Arial"><br>
Any comments are appreciated!</font><font size=3> <br>
</font><font size=3 face="sans-serif"><br>
Thanks & Best Regards,<br>
----------------------------------------------------<br>
Yang Yu(ÓÚÑî)<br>
----------------------------------------------------</font><font size=3>
<br>
_______________________________________________<br>
OpenStack-dev mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:OpenStack-dev@lists.openstack.org"><font size=3 color=blue><u>OpenStack-dev@lists.openstack.org</u></font></a><font size=3 color=blue><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target=_blank><font size=3 color=blue><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><font size=3><br>
</font>
<br>
<br><font size=3>_______________________________________________<br>
OpenStack-dev mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:OpenStack-dev@lists.openstack.org"><font size=3 color=blue><u>OpenStack-dev@lists.openstack.org</u></font></a><font size=3><br>
</font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><font size=3>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></a>
<br><tt><font size=2>_______________________________________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.org<br>
</font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size=2><br>
</font></tt>
<br>