Re: [Openstack] Quantum Integration Part 3
On Thu, Apr 26, 2012 at 3:32 AM, Emilien Macchi emilien.openst...@gmail.com wrote: ** Hi again, After inverstigation, it finally works. I have the network on my instances in using Quantum. The fact was I've follow official OVS documentation, and you should not follow this direction : ovs-vsctl add-port br-int eth1 Hi Emilien, 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. 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. Can you ping me with the error messages (can be offlist)? I still don't understand what you misconfigured, or how you fixed it. I've tried ovs-vsctl del-port br-int eth1, restart all the services and now, all is working. I have now a dual-node with : Nova-*, Glance, Quantum (without authentification), Keystone, and Horizon (without Quantum UI yet). 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. Dan Next steps : QoS, UI, Isolation testing, and documentation :-) I will continue to post about Quantum when I will advance in the project. Best regards Le mercredi 25 avril 2012 à 10:54 -0700, Dan Wendlandt a écrit : Hi Emilien, On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi emilien.openst...@gmail.com wrote: 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. 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. *- What is working at this time :* - Quantum-Server with MySQL - Quantum-Agent (with OVS) on each nova-compute node - OVS bridge with eth1 - nova-network seems working with Quantum *- What is not working (yet !) :* - 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 : http://paste.openstack.org/show/13821 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? I would look in the nova-network logs and see if you see an errors related to DHCP. - Horizon with Quantum : I can't integrate Quantum in the dashboard even with http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html 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. Dan -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ -- *Emilien Macchi* Phone : +33 685 117 748 Skype : memilien69 Twitter : EmilienMacchi https://twitter.com/ Website : http://my1.fr -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Quantum Integration Part 3
Hi Alan, That's a good question. I had assumed that my recent commits to https://www.github.com/openstack/openstack-manuals would automatically propagate to http://docs.openstack.org/incubation/openstack-network/admin/content/index.html, but that doesn't seem to have happened for the latest commits. Anne Gentle, can you help out here? Thanks! Dan On Thu, Apr 26, 2012 at 3:30 PM, Alan Kavanagh alan.kavan...@ericsson.comwrote: ** Hi Dan When will the revised Quantum Admin Guide be posted? Alan -- *From:* openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net[mailto: openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net] *On Behalf Of *Dan Wendlandt *Sent:* April-25-12 1:55 PM *To:* Emilien Macchi *Cc:* openstack@lists.launchpad.net *Subject:* Re: [Openstack] Quantum Integration Part 3 Hi Emilien, On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi emilien.openst...@gmail.com wrote: 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. 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. *- What is working at this time :* - Quantum-Server with MySQL - Quantum-Agent (with OVS) on each nova-compute node - OVS bridge with eth1 - nova-network seems working with Quantum *- What is not working (yet !) :* - 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 : http://paste.openstack.org/show/13821 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? I would look in the nova-network logs and see if you see an errors related to DHCP. - Horizon with Quantum : I can't integrate Quantum in the dashboard even with http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html 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. Dan -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Quantum Integration Part 3
Ah, the Jenkins job copies to incubated and it should be incubation - fixing now. Anne On Fri, Apr 27, 2012 at 10:30 AM, Dan Wendlandt d...@nicira.com wrote: Hi Alan, That's a good question. I had assumed that my recent commits to https://www.github.com/openstack/openstack-manuals would automatically propagate to http://docs.openstack.org/incubation/openstack-network/admin/content/index.html, but that doesn't seem to have happened for the latest commits. Anne Gentle, can you help out here? Thanks! Dan On Thu, Apr 26, 2012 at 3:30 PM, Alan Kavanagh alan.kavan...@ericsson.com wrote: ** Hi Dan When will the revised Quantum Admin Guide be posted? Alan -- *From:* openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net[mailto: openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net] *On Behalf Of *Dan Wendlandt *Sent:* April-25-12 1:55 PM *To:* Emilien Macchi *Cc:* openstack@lists.launchpad.net *Subject:* Re: [Openstack] Quantum Integration Part 3 Hi Emilien, On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi emilien.openst...@gmail.com wrote: 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. 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. *- What is working at this time :* - Quantum-Server with MySQL - Quantum-Agent (with OVS) on each nova-compute node - OVS bridge with eth1 - nova-network seems working with Quantum *- What is not working (yet !) :* - 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 : http://paste.openstack.org/show/13821 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? I would look in the nova-network logs and see if you see an errors related to DHCP. - Horizon with Quantum : I can't integrate Quantum in the dashboard even with http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html 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. Dan -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Quantum Integration Part 3
All fixed up, let me know if you have any other issues. Thanks Jim Blair for the help. Anne On Fri, Apr 27, 2012 at 10:57 AM, Anne Gentle a...@openstack.org wrote: Ah, the Jenkins job copies to incubated and it should be incubation - fixing now. Anne On Fri, Apr 27, 2012 at 10:30 AM, Dan Wendlandt d...@nicira.com wrote: Hi Alan, That's a good question. I had assumed that my recent commits to https://www.github.com/openstack/openstack-manuals would automatically propagate to http://docs.openstack.org/incubation/openstack-network/admin/content/index.html, but that doesn't seem to have happened for the latest commits. Anne Gentle, can you help out here? Thanks! Dan On Thu, Apr 26, 2012 at 3:30 PM, Alan Kavanagh alan.kavan...@ericsson.com wrote: ** Hi Dan When will the revised Quantum Admin Guide be posted? Alan -- *From:* openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net[mailto: openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net] *On Behalf Of *Dan Wendlandt *Sent:* April-25-12 1:55 PM *To:* Emilien Macchi *Cc:* openstack@lists.launchpad.net *Subject:* Re: [Openstack] Quantum Integration Part 3 Hi Emilien, On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi emilien.openst...@gmail.com wrote: 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. 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. *- What is working at this time :* - Quantum-Server with MySQL - Quantum-Agent (with OVS) on each nova-compute node - OVS bridge with eth1 - nova-network seems working with Quantum *- What is not working (yet !) :* - 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 : http://paste.openstack.org/show/13821 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? I would look in the nova-network logs and see if you see an errors related to DHCP. - Horizon with Quantum : I can't integrate Quantum in the dashboard even with http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html 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. Dan -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Quantum Integration Part 3
Hi Dan, Le vendredi 27 avril 2012 à 08:28 -0700, Dan Wendlandt a écrit : 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. I'm using default mode : VLAN. Can you ping me with the error messages (can be offlist)? I still don't understand what you misconfigured, or how you fixed it. I actually had an issue when I executed : ovs-vsctl add-port br-int eth1 I checked on the log and could see that Quantum-Agent didn't start. After inverstigation, it's seem that it was looking for a free physical interface to bridge. I released eth1 and all worked very good. 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. Of course I am ! I'm writing a documentation to install OpenStack Essex from scratch with Ubuntu 12.04 with Quantum OVS. I will to release it soon :-) Regards -- Emilien Macchi Phone : +33 685 117 748 Skype : memilien69 Twitter : EmilienMacchi Website : http://my1.fr ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Quantum Integration Part 3
Hi Dan, Le mercredi 25 avril 2012 à 10:54 -0700, Dan Wendlandt a écrit : 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? With a Debian image, I connect to the VM with VNC from dashboard, configure /etc/network/interfaces manually, ifup eth0, but I can't ping anything. Maybe the problem come from my OVS configuration ? I've created a bridge br-int, and attached eth1 on each server to this bridge (is it an error from me ?). Here you can find my nova-network.log : http://paste.openstack.org/show/13951/ My ovs-vswitchd.log of my nova-compute : http://paste.openstack.org/show/13952/ My nova-compute.log : http://paste.openstack.org/show/13954/ My Quantum-server.log : http://paste.openstack.org/show/13961/ And finally, the log file of the instance : http://paste.openstack.org/show/13960/ The errors you can read is in ovs-vwitchd.log with eth1, and on the quantum-server.log, it's talking about no route for the network. I continue to investigate today, and please contact me if anyone has an idea. Best regards I would look in the nova-network logs and see if you see an errors related to DHCP. - Horizon with Quantum : I can't integrate Quantum in the dashboard even with http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html 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. Dan -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Quantum Integration Part 3
Hi again, After inverstigation, it finally works. I have the network on my instances in using Quantum. The fact was I've follow official OVS documentation, and you should not follow this direction : ovs-vsctl add-port br-int eth1 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. I've tried ovs-vsctl del-port br-int eth1, restart all the services and now, all is working. I have now a dual-node with : Nova-*, Glance, Quantum (without authentification), Keystone, and Horizon (without Quantum UI yet). Next steps : QoS, UI, Isolation testing, and documentation :-) I will continue to post about Quantum when I will advance in the project. Best regards Le mercredi 25 avril 2012 à 10:54 -0700, Dan Wendlandt a écrit : Hi Emilien, On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi emilien.openst...@gmail.com wrote: 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. 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. - What is working at this time : - Quantum-Server with MySQL - Quantum-Agent (with OVS) on each nova-compute node - OVS bridge with eth1 - nova-network seems working with Quantum - What is not working (yet !) : - 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 : http://paste.openstack.org/show/13821 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? I would look in the nova-network logs and see if you see an errors related to DHCP. - Horizon with Quantum : I can't integrate Quantum in the dashboard even with http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html 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. Dan -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ -- Emilien Macchi Phone : +33 685 117 748 Skype : memilien69 Twitter : EmilienMacchi Website : http://my1.fr ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Quantum Integration Part 3
Salut Emilien, - Horizon with Quantum : I can't integrate Quantum in the dashboard even with http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html It's because this part of the doc is outdated, quantum in horizon has be disabled, new code is under review (https://review.openstack.org/#/c/6548/) - 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 : http://paste.openstack.org/show/13821 Got the same problem :( --- Nicolas PS : je parle français (je suis à Paris), on peut essayer de régler des problèmes en langue maternelle ;-) ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Quantum Integration Part 3
Hi Emilien, On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi emilien.openst...@gmail.com wrote: 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. 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. *- What is working at this time :* - Quantum-Server with MySQL - Quantum-Agent (with OVS) on each nova-compute node - OVS bridge with eth1 - nova-network seems working with Quantum *- What is not working (yet !) :* - 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 : http://paste.openstack.org/show/13821 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? I would look in the nova-network logs and see if you see an errors related to DHCP. - Horizon with Quantum : I can't integrate Quantum in the dashboard even with http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html 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. Dan -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Quantum Integration Part 3
Hi Dan, Thank you for your quick answer. I really was looking forward to hear you about my mail. I have VNC access from the dashboard, and tomorrow I will follow your tip about manual configuration. I will let you know about the result. For the dashboard, I want to try in order to have something graphical in my report, and I know people loves graphics stuff :-) But I totally understant that I need to use the Nova CLI, and that's I'm doing. Regards Le mercredi 25 avril 2012 à 10:54 -0700, Dan Wendlandt a écrit : Hi Emilien, On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi emilien.openst...@gmail.com wrote: 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. 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. - What is working at this time : - Quantum-Server with MySQL - Quantum-Agent (with OVS) on each nova-compute node - OVS bridge with eth1 - nova-network seems working with Quantum - What is not working (yet !) : - 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 : http://paste.openstack.org/show/13821 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? I would look in the nova-network logs and see if you see an errors related to DHCP. - Horizon with Quantum : I can't integrate Quantum in the dashboard even with http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html 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. Dan -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ -- Emilien Macchi Phone : +33 685 117 748 Skype : memilien69 Twitter : EmilienMacchi Website : http://my1.fr ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
