Hi Aaron, Thanks as usual for the reply.
I mostly root caused the horizon error last night and filed a bug that ultimately was resolved as duplicate to the following: https://bugs.launchpad.net/horizon/+bug/1040956, which I am sure the horizon people are all over now. Until that bug is fix, horizon is pretty much useless with Quantum since you can't spin up instances. Suspect the fix is easy enough - detect that user is dealing with a quantum based deployment somehow and don't try querying nova about floating ips when computing quotas. I think while I wait for the fix to come in, I'm going to learn more about command line. Horizon has been a huge help (as has been devstack) to get me playing with, and learning about, quantum and OVS (it's quantum and OVS I am particularly interested in, not installing openstack or spinning up VMs), so eager to see the bug get fixed asap. I'm definitely using the latest code, and was aware v1 was yanked from the codebase (I figured my setting v2 in localrc was a no-op). Didn't know the quantum/keystone stuff got worked out. Two questions for you: Is the gw- interface missing on the controller node a symptom of a problem? Or is it not yet supported with F3 Quantum/OVS plugin? I see tap interfaces being built, just not seeing the gw- interface. Is it correct that I don't need q-dhcp and n-net any longer? Thanks! syd From: Aaron Rosen [mailto:aro...@nicira.com] Sent: Tuesday, August 28, 2012 10:17 PM To: Syd (Sydney) Logan Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Upgrading from devstack pre-F3/quantum v1/OVS to latest not going well :-( Hi Syd, Unfortunately, I don't believe there are any tools to upgrade the ovs_quantum db to it's current format. That said, I don't believe it would be that hard to write one to migrate your setup. If you read though this page http://wiki.openstack.org/RunningQuantumV2Api it gives an example of creating a network and boot vms on it. I'm not familiar with horizon (maybe someone else who is can help you out). One last thing. Are you running the latest devstack code? The v1 api code has been removed from quantum so you can remove the following line from rclocal NOVA_USE_QUANTUM_API=v2 I'd also suggest also removing this line since devstack can now configure quantum to use keystone by default. Q_AUTH_STRATEGY=noauth Best, Aaron On Wed, Aug 29, 2012 at 12:53 AM, Syd (Sydney) Logan <slo...@broadcom.com<mailto:slo...@broadcom.com>> wrote: I played around with horizon a bit more and discovered that the "demo" project page does have a Create Instance button, but when I try and do so I get an error message saying that horizon is unable to get quota information. I tracked down a bug that was filed 5 days ago on someone seeing the same message, and it was punted over to nova after the horizon guys concluded that it was a nova bug. I'm going to see if I can work around this problem in horizon (or rootcause it) tomorrow only because I have no other obvious course of action at the moment. Here is my localrc, the same as what was working well before I grabbed latest devstack (and it grabbed the latest git versions of the openstack apps): HOST_IP=192.168.4.1 FLAT_INTERFACE=eth1 FIXED_RANGE=10.4.128.0/20<http://10.4.128.0/20> FIXED_NETWORK_SIZE=4096 FLOATING_RANGE=192.168.4.128/25<http://192.168.4.128/25> MULTI_HOST=True Q_INTERFACE=eth1 LOGFILE=/opt/stack/logs/stack.sh.log ADMIN_PASSWORD=password MYSQL_PASSWORD=password RABBIT_PASSWORD=password SERVICE_PASSWORD=password SERVICE_TOKEN=xyzpdqlazydog LIBVIRT_FIREWALL_DRIVER=nova.virt.firewall.NoopFirewallDriver ENABLED_SERVICES=g-api,g-reg,key,n-api,n-crt,n-obj,n-cpu,cinder,c-sch,c-api,c-vol,n-sch,n-novnc,n-xvnc,n-cauth,horizon,mysql,rabbit,openstackx,q-svc,quantum,q-agt Q_PLUGIN=openvswitch Q_AUTH_STRATEGY=noauth NOVA_USE_QUANTUM_API=v2 syd From: Syd (Sydney) Logan Sent: Tuesday, August 28, 2012 2:19 PM To: 'openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>' Subject: Upgrading from devstack pre-F3/quantum v1/OVS to latest not going well :-( Hi, Is there a recommended procedure for upgrading nodes that were configured pre-Folsom 3 to use quantum V1/OVS that were deployed with devstack? I probably should have asked this question before trying, but I went ahead and tried. I had a multi-node setup that I was driving with Horizon that was working very well. Now I'm just trying to get a single node setup working, and not getting far. To get sync'd up with the latest, I did the following: $ rm -rf /opt/stack (this is where devstack pulled things to) $ rm -rf /etc/quantum; rm -rf /etc/nova In the devstack localrc: Removed n-net from ENABLED_SERVICES Added q-dhcp to ENABLED_SERVICES (I had this disabled in pre-F3 after e-mails with Aaron Rosen when he helped me get going earlier, I've tried both ways and seems not to make a difference) Added NOVA_USE_QUANTUM=v2 (but this doesn't seem to make a difference either) And I ran devstack. I got no errors when I ran devstack. When I launched Horizon, some problems are evident. There is no launch instance button on the Instances page. Because I don't yet know the command UI enough to spin up and configure VMs, I figured I'd try running the devstack exercise.sh script to see what happens. It creates a few VMs, but none get an IP address (before I used to get IPs in 10.4.128.0). It reports all tests passed, as well. If I click through in the UI on the VM, I see that for networking address it assigns all VMs is the value "Net1". I've looked at console logs for the VMs created and see failures trying to dhcp (that's why I naively added q-dhcp back to ENABLED_SERVICES), but as I mentioned above, adding q-dhcp didn't help, and I'm wondering if it was a good idea anyway since Aaron steered me away from it before. Output of ps shows expected services running (e.g., OVS daemon, plugins, agents) and services lists displayed by Horizon (e.g., nova, quantum, etc.) all seem normal to me. Notably missing is the OVS gw- interface that was present before I upgraded (at http://wiki.openstack.org/RunningWQuantumV2Api there is this: "Note: with v2, Quantum no longer uses the L3 + NAT logic from nova-network. Quantum will not have the equivalent functionality until F-3, so you won't be able to ping the VMs from the nova controller host." Is that the reason?) The gw interface is the way I could ping VMs from the host. The missing gateway, horizon UI missing the create instance button, and not getting networks for VMs spun up by devstack's exercise script are the major symptoms. I trust that devstack is up to sync with what is happening in Folsom, and that I am actually pulling down F3 code at this point (I've not tried to verify this). I'm not aware of any need to tweek the devstack exercise script, I am assuming it is designed to work as is. I'm thinking of wiping my entire disk and starting from scratch in case blowing away /etc/nova etc. and /opt/stack were not enough to reset state, but before I do this, any pointers to links or mail messages (I've scanned for relevant posts but missed finding any) that would be helpful before I do this? Thanks, syd _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net> Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
