<div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 26, 2012 at 3:32 AM, Emilien Macchi <span dir="ltr"><<a href="mailto:emilien.openstack@gmail.com" target="_blank">emilien.openstack@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div>
Hi again,<br>
<br>
<br>
After inverstigation, it finally works.<br>
<br>
<br>
I have the network on my instances in using Quantum.<br>
<br>
<br>
The fact was I've follow official OVS documentation, and you should not follow this direction :<br>
<br>
ovs-vsctl add-port br-int eth1<br></div></blockquote><div><br></div><div>Hi Emilien,</div><div><br></div><div>Which mode are you running OVS in? VLAN or tunneled? If you are using VLAN-mode (default) you need to add some physical interface to br-int, so that VLANs are trunked to the physical network. Is it possible that eth1 was also the interface you were using for IP communication on the box? That definitely won't work with OVS or the linux bridge. I'll improve the docs around that to make this more clear. </div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<br>
<br>
If you see on the logs file of OVS, you can see that the bridge will not work properly... that's why my instances did not get the network.<br></div></blockquote><div><br></div><div>Can you ping me with the error messages (can be offlist)? I still don't understand what you misconfigured, or how you fixed it. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<br>
I've tried "ovs-vsctl del-port br-int eth1", restart all the services and now, all is working.<br>
<br>
<br>
I have now a dual-node with : Nova-*, Glance, Quantum (without authentification), Keystone, and Horizon (without Quantum UI yet).<br></div></blockquote><div><br></div><div>Great to hear. As I mentioned in a previous post, Horizon + Quantum isn't complete. You won't be able to create networks using Horizon, or boot VMs while specifying a particular set of vNICs. If you're interested in helping this work move forward more quickly, I'm happy to put you in touch with the right people. </div>
<div><br></div><div>Dan</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<br>
Next steps : QoS, UI, Isolation testing, and documentation :-)<br>
<br>
<br>
<br>
I will continue to post about Quantum when I will advance in the project.<br>
<br>
<br>
Best regards<div class="im"><br>
<br>
<br>
<br>
Le mercredi 25 avril 2012 à 10:54 -0700, Dan Wendlandt a écrit :
</div><blockquote type="CITE">
Hi Emilien,<br>
<br>
</blockquote><div><div class="h5">
<blockquote type="CITE">
On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi <<a href="mailto:emilien.openstack@gmail.com" target="_blank">emilien.openstack@gmail.com</a>> wrote:
</blockquote>
<blockquote type="CITE">
<blockquote>
<br>
For example, Quantum does not work with Keystone : When nova-network send an API call to Quantum-server, the token is missing in the HTTP HEADER. I've disabled Keystone at this time.<br>
<br>
</blockquote>
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<blockquote type="CITE">
That is correct. In the Quantum Admin Guide, it explains some work that was done to support Keystone Authn, but notes that this is all experimental, as the Quantum API does not support Authz. This is because the only person that calls Quantum in Essex is Nova itself. Troy Toman's team is working on Quantum Authz for Folsom, so the API can be exposed directly to tenants.
</blockquote>
<blockquote type="CITE">
</blockquote>
<blockquote type="CITE">
<blockquote>
<br>
<br>
<b>- What is working at this time :</b><br>
<br>
- Quantum-Server with MySQL<br>
- Quantum-Agent (with OVS) on each nova-compute node<br>
- OVS bridge with eth1<br>
- nova-network seems working with Quantum<br>
<br>
<b>- What is not working (yet !) :</b><br>
<br>
- When I create an instance (from dashboard or with Nova CLI), the network is created with Quantum, an private IP is attributed to the instance, but when I check the instance log file, the network interface doesn't get an IP adress. Here the log : <a href="http://paste.openstack.org/show/13821/" target="_blank">http://paste.openstack.org/show/13821</a>
</blockquote>
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<blockquote type="CITE">
Are you able to access the VM via VNC? If you statically configure the IP does it work? What happens if you run dhcpc manually?
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<blockquote type="CITE">
I would look in the nova-network logs and see if you see an errors related to DHCP.
</blockquote>
<blockquote type="CITE">
</blockquote>
<blockquote type="CITE">
<blockquote>
<br>
- Horizon with Quantum : I can't integrate Quantum in the dashboard even with <a href="http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html" target="_blank">http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html</a>
</blockquote>
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<blockquote type="CITE">
Essex Horizon does not support Quantum. Its actually not just a Horizon thing, it has to do with how the Nova + Quantum integration works. Each Quantum network has to be associated with appropriate IPAM subnet, meaning the existing . For now, you need to create networks using nova-manage. If you want VMs to get the default set of NICs, you can then boot them with Horizon. If you want to specify what networks vNICs are plugged into, this is only supported via the nova boot command with the --nic option. I'll flush this out in more detail in the Quantum Admin Guide.
</blockquote>
<blockquote type="CITE">
</blockquote>
<blockquote type="CITE">
Dan
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<blockquote type="CITE">
<blockquote>
<br>
<br>
<br>
<br>
</blockquote>
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<blockquote type="CITE">
-- <br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
Dan Wendlandt
</blockquote>
<blockquote type="CITE">
Nicira, Inc: <a href="http://www.nicira.com" target="_blank">www.nicira.com</a>
</blockquote>
<blockquote type="CITE">
twitter: danwendlandt<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
<br>
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<br>
</div></div><div class="im"><table cellspacing="0" cellpadding="0" width="100%">
<tbody><tr>
<td>
-- <br>
<b>Emilien Macchi</b><br>
Phone : <a href="tel:%2B33%20685%20117%20748" value="+33685117748" target="_blank">+33 685 117 748</a><br>
Skype : memilien69<br>
Twitter : <a href="https://twitter.com/" target="_blank">EmilienMacchi</a><br>
Website : <a href="http://my1.fr" target="_blank">http://my1.fr</a>
</td>
</tr>
</tbody></table>
</div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>Dan Wendlandt <div>Nicira, Inc: <a href="http://www.nicira.com" target="_blank">www.nicira.com</a><br><div>twitter: danwendlandt<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~<br></div></div><br>
</div>