<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi Ian,</div><div><br></div>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.<div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>Vish</div><div><br><div><div>On Dec 4, 2013, at 8:26 AM, Ian Wells <<a href="mailto:ijw.ubuntu@cack.org.uk">ijw.ubuntu@cack.org.uk</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div><div>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><br></div>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>
<br></div>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>-- <br></div>Ian.<br><div><div class="gmail_extra"><br><br><div class="gmail_quote">On 2 December 2013 03:01, Yang XY Yu <span dir="ltr"><<a href="mailto:yuyangbj@cn.ibm.com" target="_blank">yuyangbj@cn.ibm.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font face="sans-serif">Hi all stackers,</font>
<br>
<br><font face="sans-serif">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 color="blue" size="3"><u>https://review.openstack.org/#/c/58721/</u></font></a><font size="3">,
</font><font 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>
<br>
<br><font face="sans-serif">1. Special Image needed to support IPv6
by using cloud-init, currently the cirros image used by tempest does not
installed cloud-init.</font>
<br>
<br><font face="sans-serif">2. Prepare interfaces.template file
below on compute node.</font>
<br><font color="#2f2f2f" face="Arial" size="1"> edit /usr/share/nova/interfaces.template</font><font size="3">
</font>
<br>
<br><font face="Arial" size="1"># Injected by Nova on instance boot</font>
<br><font face="Arial" size="1">#</font>
<br><font face="Arial" size="1"># This file describes the network interfaces
available on your system</font>
<br><font face="Arial" size="1"># and how to activate them. For more information,
see interfaces(5).</font>
<br>
<br><font face="Arial" size="1"># The loopback network interface</font>
<br><font face="Arial" size="1">auto lo</font>
<br><font face="Arial" size="1">iface lo inet loopback</font>
<br>
<br><font face="Arial" size="1">{% for ifc in interfaces -%}</font>
<br><font face="Arial" size="1">auto {{ <a href="http://ifc.name/" target="_blank">ifc.name</a> }}</font>
<br><font face="Arial" size="1">{% if use_ipv6 -%}</font>
<br><font face="Arial" size="1">iface {{ <a href="http://ifc.name/" target="_blank">ifc.name</a> }} inet6 static</font>
<br><font face="Arial" size="1"> address {{ ifc.address_v6 }}</font>
<br><font face="Arial" size="1"> netmask {{ ifc.netmask_v6 }}</font>
<br><font face="Arial" size="1">{%- if ifc.gateway_v6 %}</font>
<br><font face="Arial" size="1"> gateway {{ ifc.gateway_v6 }}</font>
<br><font face="Arial" size="1">{%- endif %}</font>
<br><font face="Arial" size="1">{%- endif %}</font>
<br>
<br><font face="Arial" size="1">{%- endfor %}</font>
<br>
<br>
<br><font face="Arial" size="1">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>
<br><font face="Arial" size="1">Any comments are appreciated!</font>
<br>
<br><font face="sans-serif">Thanks & Best Regards,<br>
----------------------------------------------------<br>
Yang Yu(于杨)<br>
Cloud Solutions and OpenStack Development<br>
China Systems & Technology Laboratory Beijing<br>
E-mail: <a href="mailto:yuyangbj@cn.ibm.com" target="_blank">yuyangbj@cn.ibm.com</a> <br>
Tel: 86-10-82452757<br>
Address: Ring Bldg. No.28 Building, Zhong Guan Cun Software Park, <br>
No. 8 Dong Bei Wang West Road, ShangDi, Haidian District, Beijing 100193,
P.R.China <br>
----------------------------------------------------</font>
<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></div></div></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></div></body></html>