[Openstack] Crowbar problem (using Rob's ISO)
Hi All, I have tried installing OpenStack using the crowbar ISO provided by Rob (http://crowbar.zehicle.com/crowbar111219.iso) and successfully installed the admin node. But when it comes to PXE boot of the other crowbar nodes, the installation gets stuck showing: HOSTNAME=h00-0c-29-58-21-fe.crowbar.org NODE_STATE= /usr/lib/ruby/gems/1.8/gems/json-1.4.6/lib/json/common.rb:146 in ‘parse’: 705: unexpected token at ‘Host not found’ (JSON::ParserError) from /usr/lib/ruby/gems/1.8/gems/json1.4.6/lib/json/common.rb:146 in ‘parse’ from /updates/parse_node_data:57:in ‘main’ from /updates/parse_node_data:69 BMC_ROUTER= BMC_ADDRESS= BMC_NETMASK= /usr/lib/ruby/gems/1.8/gems/json-1.4.6/lib/json/common.rb:146 in ‘parse’: 705:unexpected token at ‘Host not found’ (JSON::ParserError) from /usr/lib/ruby/gems/1.8/gems/json1.4.6/lib/json/common.rb:146 in ‘parse’ from /updates/parse_node_data:57:in ‘main’ from /updates/parse_node_data:69 BMC_ROUTER= BMC_ADDRESS= BMC_NETMASK= HOSTNAME=h00-0c-29-58-21-fe.crowbar.org NODE_STATE= This problem has already been reported at Rob's blog but I am not sure if it is fixed. Any ideas? Thanks. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] nova-network service stuck
Hi All, I am having problem with getting nova-service to work. The last line that is shown on the screen is: 2012-04-14 19:42:39 DEBUG nova.utils [-] Attempting to grab file lock iptables for method apply... from (pid=3649) inner /opt/stack/nova/nova/utils.py:936 and the service is stuck at this point. So when I do a nova-manage service list, network service turns out to be unhappy. I haven't found much help on how to 'unlock' iptables file. Thoughts please ? Salman ___ 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] nova-network service stuck
Thanks Nate for the quick reply. There is no such directory on the system (I am using devstack if that helps...) Thanks, Salman Date: Sat, 14 Apr 2012 21:00:39 -0400 Subject: Re: [Openstack] nova-network service stuck From: nathanael.i.bur...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net Check in Nova's lock dir, on my system it's /var/lib/nova/tmp. Remove any files in there and restart the services. Nate On Apr 14, 2012 8:56 PM, Salman Malik salma...@live.com wrote: Hi All, I am having problem with getting nova-service to work. The last line that is shown on the screen is: 2012-04-14 19:42:39 DEBUG nova.utils [-] Attempting to grab file lock iptables for method apply... from (pid=3649) inner /opt/stack/nova/nova/utils.py:936 and the service is stuck at this point. So when I do a nova-manage service list, network service turns out to be unhappy. I haven't found much help on how to 'unlock' iptables file. Thoughts please ? Salman ___ Mailing list: https://launchpad.net/~openstack Post to : 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
Re: [Openstack] nova-network service stuck
Thanks Nat. The script didn't help but removing lock files from the directory that you mentioned definitely helped. Thanks, Salman Date: Sat, 14 Apr 2012 21:55:47 -0400 Subject: Re: [Openstack] nova-network service stuck From: nathanael.i.bur...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net Salman, The location for the locks is determined by the --lock_path setting in nova.conf. This is apparently set to the base path where the nova python code lives ($pybasedir) in devstack: 2012-04-14 21:35:42 DEBUG nova.service [-] lock_path : /opt/stack/nova from (pid=3700) wait /opt/stack/nova/nova/service.py:442 Since, that directory has a bunch of important files in it, certainly don't follow my previous advice and remove all the files in that directory. There is a bug (https://bugs.launchpad.net/nova/+bug/785955) about nova not cleaning up locks that should have been fixed in essex-4. As part of the fix to that Mike Pittaro wrote a cleanup locks script that should be in /opt/stack/nova/tools/clean_file_locks.py. Try running that and let us know if that fixed it. If not look for *.lock files in /opt/stack/nova Thanks, Nate On Sat, Apr 14, 2012 at 9:07 PM, Salman Malik salma...@live.com wrote: Thanks Nate for the quick reply. There is no such directory on the system (I am using devstack if that helps...) Thanks, Salman Date: Sat, 14 Apr 2012 21:00:39 -0400 Subject: Re: [Openstack] nova-network service stuck From: nathanael.i.bur...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net Check in Nova's lock dir, on my system it's /var/lib/nova/tmp. Remove any files in there and restart the services. Nate On Apr 14, 2012 8:56 PM, Salman Malik salma...@live.com wrote: Hi All, I am having problem with getting nova-service to work. The last line that is shown on the screen is: 2012-04-14 19:42:39 DEBUG nova.utils [-] Attempting to grab file lock iptables for method apply... from (pid=3649) inner /opt/stack/nova/nova/utils.py:936 and the service is stuck at this point. So when I do a nova-manage service list, network service turns out to be unhappy. I haven't found much help on how to 'unlock' iptables file. Thoughts please ? Salman ___ Mailing list: https://launchpad.net/~openstack Post to : 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
[Openstack] Unable to ping launched Instance
Hi Guys, I have launched an instance using dashboard. The 'intances and volume' tab shows that the instance is in active status and power state = running ( IP address = 10.0.0.3). But when I click on the instance name and go to see the logs, there are no logs (nothing in 'view full log' as well) and the Instance's VNC console shows: This kernel requires x86-64 CPU, but only detected an i686 CPU. Unable to boot - please use a kernel appropriate for your CPU I have had the same problem and the proposed solution that I found was to enable virtualization in BIOS. But I am running the devstack on a VirtualBox VM and thus can not enable that in BIOS. Since stack.sh is supposed to run on VMs, can someone propose a solution ? Thanks in advance, Salman ___ 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] Unable to ping launched Instance
Thanks Marton for the advice. I actually already had the libvirt_type=qemu, and since I did not have '--' before any of the lines in nova conf, I added that before the libvirt_type line. Then, I rebooted the VM and started rejoin-stack.sh to start the services again. But now when I launch an instance I get status: Error , Task: Spawning and Power State: no State. Any other thoughts as to what might be wrong ? (The log for the instance says : Unable to get log for instance 90bf00e8-6ece-4978-aa16-1b68f34bf44e. Possibly because machine never went up ?) Thanks, Salman Date: Sun, 15 Apr 2012 05:35:14 +0200 Subject: Re: [Openstack] Unable to ping launched Instance From: marton.k...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net Hi, Try qemu instead of kvm, and it'll work inside a virtualbox vm, Change the following nova config option: --libvirt_type=qemu Regards, Márton Kiss, CTO Xemeti 2012/4/15 Salman Malik salma...@live.com: Hi Guys, I have launched an instance using dashboard. The 'intances and volume' tab shows that the instance is in active status and power state = running ( IP address = 10.0.0.3). But when I click on the instance name and go to see the logs, there are no logs (nothing in 'view full log' as well) and the Instance's VNC console shows: This kernel requires x86-64 CPU, but only detected an i686 CPU. Unable to boot - please use a kernel appropriate for your CPU I have had the same problem and the proposed solution that I found was to enable virtualization in BIOS. But I am running the devstack on a VirtualBox VM and thus can not enable that in BIOS. Since stack.sh is supposed to run on VMs, can someone propose a solution ? Thanks in advance, Salman ___ Mailing list: https://launchpad.net/~openstack Post to : 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
Re: [Openstack] Unable to ping launched Instance
I haven't edited nova-compute.conf. Can you please tell me where to look for it ? Thanks, Salman Date: Sun, 15 Apr 2012 07:00:12 +0200 Subject: Re: [Openstack] Unable to ping launched Instance From: marton.k...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net Hi, It's a tricky issue. I bet you have a different libvirt_type setting in your nova.conf and separate nova-compute.conf. I experienced the same, and spent 2 days to tracking what could be wrong with libvirt that starting instances randomly going into no state. Regards, Márton Kiss, CTO Xemeti 2012/4/15 Salman Malik salma...@live.com: Thanks Marton for the advice. I actually already had the libvirt_type=qemu, and since I did not have '--' before any of the lines in nova conf, I added that before the libvirt_type line. Then, I rebooted the VM and started rejoin-stack.sh to start the services again. But now when I launch an instance I get status: Error , Task: Spawning and Power State: no State. Any other thoughts as to what might be wrong ? (The log for the instance says : Unable to get log for instance 90bf00e8-6ece-4978-aa16-1b68f34bf44e. Possibly because machine never went up ?) Thanks, Salman Date: Sun, 15 Apr 2012 05:35:14 +0200 Subject: Re: [Openstack] Unable to ping launched Instance From: marton.k...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net Hi, Try qemu instead of kvm, and it'll work inside a virtualbox vm, Change the following nova config option: --libvirt_type=qemu Regards, Márton Kiss, CTO Xemeti 2012/4/15 Salman Malik salma...@live.com: Hi Guys, I have launched an instance using dashboard. The 'intances and volume' tab shows that the instance is in active status and power state = running ( IP address = 10.0.0.3). But when I click on the instance name and go to see the logs, there are no logs (nothing in 'view full log' as well) and the Instance's VNC console shows: This kernel requires x86-64 CPU, but only detected an i686 CPU. Unable to boot - please use a kernel appropriate for your CPU I have had the same problem and the proposed solution that I found was to enable virtualization in BIOS. But I am running the devstack on a VirtualBox VM and thus can not enable that in BIOS. Since stack.sh is supposed to run on VMs, can someone propose a solution ? Thanks in advance, Salman ___ Mailing list: https://launchpad.net/~openstack Post to : 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
Re: [Openstack] Unable to ping launched Instance
I am using devstak's stack.sh script. Salman Date: Sun, 15 Apr 2012 07:12:42 +0200 Subject: Re: [Openstack] Unable to ping launched Instance From: marton.k...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net Are you using devstack or a package based deployment? M. 2012/4/15 Salman Malik salma...@live.com: I haven't edited nova-compute.conf. Can you please tell me where to look for it ? Thanks, Salman Date: Sun, 15 Apr 2012 07:00:12 +0200 Subject: Re: [Openstack] Unable to ping launched Instance From: marton.k...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net Hi, It's a tricky issue. I bet you have a different libvirt_type setting in your nova.conf and separate nova-compute.conf. I experienced the same, and spent 2 days to tracking what could be wrong with libvirt that starting instances randomly going into no state. Regards, Márton Kiss, CTO Xemeti 2012/4/15 Salman Malik salma...@live.com: Thanks Marton for the advice. I actually already had the libvirt_type=qemu, and since I did not have '--' before any of the lines in nova conf, I added that before the libvirt_type line. Then, I rebooted the VM and started rejoin-stack.sh to start the services again. But now when I launch an instance I get status: Error , Task: Spawning and Power State: no State. Any other thoughts as to what might be wrong ? (The log for the instance says : Unable to get log for instance 90bf00e8-6ece-4978-aa16-1b68f34bf44e. Possibly because machine never went up ?) Thanks, Salman Date: Sun, 15 Apr 2012 05:35:14 +0200 Subject: Re: [Openstack] Unable to ping launched Instance From: marton.k...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net Hi, Try qemu instead of kvm, and it'll work inside a virtualbox vm, Change the following nova config option: --libvirt_type=qemu Regards, Márton Kiss, CTO Xemeti 2012/4/15 Salman Malik salma...@live.com: Hi Guys, I have launched an instance using dashboard. The 'intances and volume' tab shows that the instance is in active status and power state = running ( IP address = 10.0.0.3). But when I click on the instance name and go to see the logs, there are no logs (nothing in 'view full log' as well) and the Instance's VNC console shows: This kernel requires x86-64 CPU, but only detected an i686 CPU. Unable to boot - please use a kernel appropriate for your CPU I have had the same problem and the proposed solution that I found was to enable virtualization in BIOS. But I am running the devstack on a VirtualBox VM and thus can not enable that in BIOS. Since stack.sh is supposed to run on VMs, can someone propose a solution ? Thanks in advance, Salman ___ Mailing list: https://launchpad.net/~openstack Post to : 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
Re: [Openstack] Unable to ping launched Instance
Thanks a lot Marton for your help. But there is no nova.conf file in the directory you mentioned. I have checked the log for nova-compute.log and I believe that the flag is set correctly because I read past the following line in the log : 2012-04-15 00:55:07 DEBUG nova.service [-] libvirt_type : qemu from (pid=2752) wait /opt/stack/nova/nova/service.py:442 Any other suggestions will be much appreciated. I need to get this thing up. Thanks, Salman Date: Sun, 15 Apr 2012 07:27:43 +0200 Subject: Re: [Openstack] Unable to ping launched Instance From: marton.k...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net In that case, check the libvirt type value /opt/stack/etc/nova/nova.conf, and check the value inside the log file of nova-compute after starting. M. 2012/4/15 Salman Malik salma...@live.com: I am using devstak's stack.sh script. Salman Date: Sun, 15 Apr 2012 07:12:42 +0200 Subject: Re: [Openstack] Unable to ping launched Instance From: marton.k...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net Are you using devstack or a package based deployment? M. 2012/4/15 Salman Malik salma...@live.com: I haven't edited nova-compute.conf. Can you please tell me where to look for it ? Thanks, Salman Date: Sun, 15 Apr 2012 07:00:12 +0200 Subject: Re: [Openstack] Unable to ping launched Instance From: marton.k...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net Hi, It's a tricky issue. I bet you have a different libvirt_type setting in your nova.conf and separate nova-compute.conf. I experienced the same, and spent 2 days to tracking what could be wrong with libvirt that starting instances randomly going into no state. Regards, Márton Kiss, CTO Xemeti 2012/4/15 Salman Malik salma...@live.com: Thanks Marton for the advice. I actually already had the libvirt_type=qemu, and since I did not have '--' before any of the lines in nova conf, I added that before the libvirt_type line. Then, I rebooted the VM and started rejoin-stack.sh to start the services again. But now when I launch an instance I get status: Error , Task: Spawning and Power State: no State. Any other thoughts as to what might be wrong ? (The log for the instance says : Unable to get log for instance 90bf00e8-6ece-4978-aa16-1b68f34bf44e. Possibly because machine never went up ?) Thanks, Salman Date: Sun, 15 Apr 2012 05:35:14 +0200 Subject: Re: [Openstack] Unable to ping launched Instance From: marton.k...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net Hi, Try qemu instead of kvm, and it'll work inside a virtualbox vm, Change the following nova config option: --libvirt_type=qemu Regards, Márton Kiss, CTO Xemeti 2012/4/15 Salman Malik salma...@live.com: Hi Guys, I have launched an instance using dashboard. The 'intances and volume' tab shows that the instance is in active status and power state = running ( IP address = 10.0.0.3). But when I click on the instance name and go to see the logs, there are no logs (nothing in 'view full log' as well) and the Instance's VNC console shows: This kernel requires x86-64 CPU, but only detected an i686 CPU. Unable to boot - please use a kernel appropriate for your CPU I have had the same problem and the proposed solution that I found was to enable virtualization in BIOS. But I am running the devstack on a VirtualBox VM and thus can not enable that in BIOS. Since stack.sh is supposed to run on VMs, can someone propose a solution ? Thanks in advance, Salman ___ Mailing list: https://launchpad.net/~openstack Post to : 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
Re: [Openstack] Unable to ping launched Instance
For some reason, all this time I had been thinking that I have been running 64 bit Ubuntu. But yes, you pointed out the exact problem. Thanks a lot ! Salman From: mih...@gmail.com Date: Sun, 15 Apr 2012 01:13:08 -0700 Subject: Re: [Openstack] Unable to ping launched Instance To: salma...@live.com CC: marton.k...@gmail.com; openstack@lists.launchpad.net Hi,you presumably running i686 VirtualBox VM for the OpenStack,but the cirros instance in devstack requires x86_64 machine.qemu emulates i686 if host is i686. Try to recreate base OS in VirtualBox in a 64bit mode. If you name your machine like 'Linux_11.10_64bit', VirtualBox will automaticallyconfigure x86_64 CPU emulation. Regards, On Sat, Apr 14, 2012 at 11:06 PM, Salman Malik salma...@live.com wrote: Thanks a lot Marton for your help. But there is no nova.conf file in the directory you mentioned. I have checked the log for nova-compute.log and I believe that the flag is set correctly because I read past the following line in the log : 2012-04-15 00:55:07 DEBUG nova.service [-] libvirt_type : qemu from (pid=2752) wait /opt/stack/nova/nova/service.py:442 Any other suggestions will be much appreciated. I need to get this thing up. Thanks, Salman Date: Sun, 15 Apr 2012 07:27:43 +0200 Subject: Re: [Openstack] Unable to ping launched Instance From: marton.k...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net In that case, check the libvirt type value /opt/stack/etc/nova/nova.conf, and check the value inside the log file of nova-compute after starting. M. 2012/4/15 Salman Malik salma...@live.com: I am using devstak's stack.sh script. Salman Date: Sun, 15 Apr 2012 07:12:42 +0200 Subject: Re: [Openstack] Unable to ping launched Instance From: marton.k...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net Are you using devstack or a package based deployment? M. 2012/4/15 Salman Malik salma...@live.com: I haven't edited nova-compute.conf. Can you please tell me where to look for it ? Thanks, Salman Date: Sun, 15 Apr 2012 07:00:12 +0200 Subject: Re: [Openstack] Unable to ping launched Instance From: marton.k...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net Hi, It's a tricky issue. I bet you have a different libvirt_type setting in your nova.conf and separate nova-compute.conf. I experienced the same, and spent 2 days to tracking what could be wrong with libvirt that starting instances randomly going into no state. Regards, Márton Kiss, CTO Xemeti 2012/4/15 Salman Malik salma...@live.com: Thanks Marton for the advice. I actually already had the libvirt_type=qemu, and since I did not have '--' before any of the lines in nova conf, I added that before the libvirt_type line. Then, I rebooted the VM and started rejoin-stack.sh to start the services again. But now when I launch an instance I get status: Error , Task: Spawning and Power State: no State. Any other thoughts as to what might be wrong ? (The log for the instance says : Unable to get log for instance 90bf00e8-6ece-4978-aa16-1b68f34bf44e. Possibly because machine never went up ?) Thanks, Salman Date: Sun, 15 Apr 2012 05:35:14 +0200 Subject: Re: [Openstack] Unable to ping launched Instance From: marton.k...@gmail.com To: salma...@live.com CC: openstack@lists.launchpad.net Hi, Try qemu instead of kvm, and it'll work inside a virtualbox vm, Change the following nova config option: --libvirt_type=qemu Regards, Márton Kiss, CTO Xemeti 2012/4/15 Salman Malik salma...@live.com: Hi Guys, I have launched an instance using dashboard. The 'intances and volume' tab shows that the instance is in active status and power state = running ( IP address = 10.0.0.3). But when I click on the instance name and go to see the logs, there are no logs (nothing in 'view full log' as well) and the Instance's VNC console shows: This kernel requires x86-64 CPU, but only detected an i686 CPU. Unable to boot - please use a kernel appropriate for your CPU I have had the same problem and the proposed solution that I found was to enable virtualization in BIOS. But I am running the devstack on a VirtualBox VM and thus can not enable that in BIOS. Since stack.sh is supposed to run on VMs, can someone propose a solution ? Thanks in advance, Salman ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net
[Openstack] Networking Issue (of newly launched instance)
Hi All, I have been able to launch an instance using devstack's dashboard. Now there seems to be networking problem. The log of the launched instance shows the following message repeatedly: cloud-setup: failed 1/30 : up 1.23. request failed wget: can't connect to remote host (169.254.169.254): No route to host and afterwards, the log shows: debug start ## ### /etc/rc.d/init.d/sshd start /etc/rc3.d/S45-cloud-setup: line 66: /etc/rc.d/init.d/sshd: not found ### ifconfig -a eth0 Link encap:Ethernet HWaddr FA:16:3E:28:AB:91 inet addr:10.0.3.19 Bcast:10.0.3.255 Mask:255.255.255.0 inet6 addr: fe80::f816:3eff:fe28:ab91/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX packets:96 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3054 (2.9 KiB) TX bytes:4780 (4.6 KiB) Interrupt:11 Base address:0xa000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:56 errors:0 dropped:0 overruns:0 frame:0 TX packets:56 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4928 (4.8 KiB) TX bytes:4928 (4.8 KiB) ### route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 10.0.3.20.0.0.0 UG0 00 eth0 10.0.3.00.0.0.0 255.255.255.0 U 0 00 eth0 ### cat /etc/resolv.conf search hsd1.il.comcast.net. nameserver 192.168.1.1 ### ping -c 5 10.0.3.2 PING 10.0.3.2 (10.0.3.2): 56 data bytes --- 10.0.3.2 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss ### pinging nameservers ping -c 5 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes --- 192.168.1.1 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss and after sometime: wget: can't connect to remote host (169.254.169.254): No route to host instance-id: public-ipv4: local-ipv4 : wget: can't connect to remote host (169.254.169.254): No route to host cloud-userdata: failed to read instance id WARN: /etc/rc3.d/S99-cloud-userdata failed Although the dashboard shows an IP of 10.0.0.3 for this instance, yet within the logs ifconfig -a is showing 10.0.3.19. I am not sure how this instance is connected to my host (or how it should be connected to my host). Someone help please, I can not even login to the instance using VNC. (Any insights to the networking part would be really helpful) This is my setup: My host VM (which is hosting devstack) has two VNICs: eth0 is NAT (IP:10.0.3.15) and eth1 is host only (IP:192.168.124.2). All devstack's configuration has been done with respect to 10.0.3.15 (i.e all services are bound to this address) ___ 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] Networking Issue (of newly launched instance)
Thanks Sheng. I think you are right. But how to resolve the issue ? Subject: Re: [Openstack] Networking Issue (of newly launched instance) From: gong...@cn.ibm.com To: salma...@live.com CC: openstack@lists.launchpad.net Date: Mon, 16 Apr 2012 07:47:17 +0800 I think the dhcp message is intercepted by your host's dhcp server. -openstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: - To: openstack@lists.launchpad.net From: Salman Malik salma...@live.com Sent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.net Date: 04/16/2012 12:30AM Subject: [Openstack] Networking Issue (of newly launched instance) Hi All, I have been able to launch an instance using devstack's dashboard. Now there seems to be networking problem. The log of the launched instance shows the following message repeatedly: cloud-setup: failed 1/30 : up 1.23. request failed wget: can't connect to remote host (169.254.169.254): No route to host and afterwards, the log shows: debug start ## ### /etc/rc.d/init.d/sshd start /etc/rc3.d/S45-cloud-setup: line 66: /etc/rc.d/init.d/sshd: not found ### ifconfig -a eth0 Link encap:Ethernet HWaddr FA:16:3E:28:AB:91 inet addr:10.0.3.19 Bcast:10.0.3.255 Mask:255.255.255.0 inet6 addr: fe80::f816:3eff:fe28:ab91/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX packets:96 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3054 (2.9 KiB) TX bytes:4780 (4.6 KiB) Interrupt:11 Base address:0xa000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:56 errors:0 dropped:0 overruns:0 frame:0 TX packets:56 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4928 (4.8 KiB) TX bytes:4928 (4.8 KiB) ### route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 10.0.3.20.0.0.0 UG0 00 eth0 10.0.3.00.0.0.0 255.255.255.0 U 0 00 eth0 ### cat /etc/resolv.conf search hsd1.il.comcast.net. nameserver 192.168.1.1 ### ping -c 5 10.0.3.2 PING 10.0.3.2 (10.0.3.2): 56 data bytes --- 10.0.3.2 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss ### pinging nameservers ping -c 5 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes --- 192.168.1.1 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss and after sometime: wget: can't connect to remote host (169.254.169.254): No route to host instance-id: public-ipv4: local-ipv4 : wget: can't connect to remote host (169.254.169.254): No route to host cloud-userdata: failed to read instance id WARN: /etc/rc3.d/S99-cloud-userdata failed Although the dashboard shows an IP of 10.0.0.3 for this instance, yet within the logs ifconfig -a is showing 10.0.3.19. I am not sure how this instance is connected to my host (or how it should be connected to my host). Someone help please, I can not even login to the instance using VNC. (Any insights to the networking part would be really helpful) This is my setup: My host VM (which is hosting devstack) has two VNICs: eth0 is NAT (IP:10.0.3.15) and eth1 is host only (IP:192.168.124.2). All devstack's configuration has been done with respect to 10.0.3.15 (i.e all services are bound to this address) ___ Mailing list: https://launchpad.net/~openstack Post to : 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
[Openstack] nova.conf query
Hi All, A quick question regarding nova.conf: How can I modify nova.conf and get it to work with devstack. The problem that I am facing is after modifying nova.conf, I have to reboot so as to restart services. But when I reboot, devstack needs to be reinstalled all over again using stack.sh and in the process it rewrites /etc/nova/nova.conf. Also according to documentation we can set flags in nova.conf using --flag_name=flag_value format. Is that an obsolete format ? (because the nova.conf that devstack creates don't have any -- in it). Please let me know how to effectively modify nova.conf so that the changes take effect (I am looking forward to change the network manager...) Thanks! Salman ___ 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] nova.conf query
Here is one example, that I actually intended to configure: http://docs.openstack.org/incubation/openstack-network/admin/content/EnablingQuantumManager-d1e453.html But there are plenty out there I guess... CC: openstack@lists.launchpad.net From: lo...@nimbisservices.com Subject: Re: [Openstack] nova.conf query Date: Mon, 16 Apr 2012 08:35:15 -0700 To: salma...@live.com Hi Salman: Can you send me a link to any docs that have the old --flag format? Lorin Sent from my iPad On Apr 16, 2012, at 6:17 AM, Salman Malik salma...@live.com wrote: Hi All, A quick question regarding nova.conf: How can I modify nova.conf and get it to work with devstack. The problem that I am facing is after modifying nova.conf, I have to reboot so as to restart services. But when I reboot, devstack needs to be reinstalled all over again using stack.sh and in the process it rewrites /etc/nova/nova.conf. Also according to documentation we can set flags in nova.conf using --flag_name=flag_value format. Is that an obsolete format ? (because the nova.conf that devstack creates don't have any -- in it). Please let me know how to effectively modify nova.conf so that the changes take effect (I am looking forward to change the network manager...) Thanks! Salman ___ Mailing list: https://launchpad.net/~openstack Post to : 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
Re: [Openstack] nova.conf query
Thank you both. I will give it a try and let you know. Date: Mon, 16 Apr 2012 07:23:29 -0700 Subject: Re: [Openstack] nova.conf query From: lzye...@gmail.com To: heut2...@gmail.com CC: salma...@live.com; openstack@lists.launchpad.net Yaguang, I think you shoud type screen -x stack If -S, I believe a new stack screen session would start. Also I remember that devstack runs its services on the account you ran stack.sh by default in the recent versions. LZY On Mon, Apr 16, 2012 at 6:40 AM, heut2008 heut2...@gmail.com wrote: devstack runs all nova services in a screen backgroud.you can sudo stack,then screen -S stack,you can see all services here.what you need do is change the nova.conf then stop the releative services,then start it again. 2012/4/16 Salman Malik salma...@live.com: Hi All, A quick question regarding nova.conf: How can I modify nova.conf and get it to work with devstack. The problem that I am facing is after modifying nova.conf, I have to reboot so as to restart services. But when I reboot, devstack needs to be reinstalled all over again using stack.sh and in the process it rewrites /etc/nova/nova.conf. Also according to documentation we can set flags in nova.conf using --flag_name=flag_value format. Is that an obsolete format ? (because the nova.conf that devstack creates don't have any -- in it). Please let me know how to effectively modify nova.conf so that the changes take effect (I am looking forward to change the network manager...) Thanks! Salman ___ Mailing list: https://launchpad.net/~openstack Post to : 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 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] OpenStack Quantum plugins
Hi All, I am trying to learn the functionality of Quantum plugins used in OpenStack. I have read through the Quantum Admin Guide and had few basic/quick question about quantum and OVS interaction with it: 1) OVS can have ports in which vNICS can be plugged, so why does it need to use an integration bridge for connecting all VMs on the same node to a network? 2) The OVS quantum plugin seems to implement the core API functions and (viewing the code) I concluded that it just makes maintains the logical mappings e.g. b/w net IDs and VLAN IDs in a database. So how is this mapping implemented on the actual ports of OVS? Is it the OVS quantum agent responsible for directing the packets to correct input/output ports based on the updates that it gets from the database? 3) The quantum admin guide says that the nova client will be the main user of quantum and will interact with it via REST API, so it would be nice if someone can point me to the code (file path name etc.) where this happens. Thanks, Salman PS: What is the purpose of Quantum Manager in this architecture and where should I look for its code? ___ 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] OpenStack Quantum plugins
Dan, Salavatore and others, your input is sought here. Can any one provide little explanation please? From: salma...@live.com To: openstack@lists.launchpad.net Subject: OpenStack Quantum plugins Date: Thu, 26 Apr 2012 19:55:20 + Hi All, I am trying to learn the functionality of Quantum plugins used in OpenStack. I have read through the Quantum Admin Guide and had few basic/quick question about quantum and OVS interaction with it: 1) OVS can have ports in which vNICS can be plugged, so why does it need to use an integration bridge for connecting all VMs on the same node to a network? 2) The OVS quantum plugin seems to implement the core API functions and (viewing the code) I concluded that it just makes maintains the logical mappings e.g. b/w net IDs and VLAN IDs in a database. So how is this mapping implemented on the actual ports of OVS? Is it the OVS quantum agent responsible for directing the packets to correct input/output ports based on the updates that it gets from the database? 3) The quantum admin guide says that the nova client will be the main user of quantum and will interact with it via REST API, so it would be nice if someone can point me to the code (file path name etc.) where this happens. Thanks, Salman PS: What is the purpose of Quantum Manager in this architecture and where should I look for its code? ___ 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] OpenStack Quantum plugins
Hi Dan, Thanks for replying. There are few more questions: I am trying to learn the functionality of Quantum plugins used in OpenStack. I have read through the Quantum Admin Guide and had few basic/quick question about quantum and OVS interaction with it: 1) OVS can have ports in which vNICS can be plugged, so why does it need to use an integration bridge for connecting all VMs on the same node to a network? I'm not sure I follow what question you're asking. When OVS is running on a host, it has one or more bridges, and bridges have ports. A linux device representing the vNIC must be added as a port of a bridge being managed by the Quantum plugin. We call this bridge the integration bridge. The Quantum plugin can then configure the ports and bridges appropriately to forward traffic based on the logical model created via the Quantum API. Can you be more precise about what you're asking here? In short it means that the OVS is managing the linux bridges and the linux devices representing vNICs must be added to these bridges (Does Quantum manager adds these devices to bridges?). And when you say that quantum plugin configures the ports and bridges appropriately to forward traffic, you mean that it updates the database and then quantum agent then assures the correct mapping of ports/network ids to logical networks at the switch level(by adding flow entries to vSwitch? or by adding the vNICs to right bridges, as there is one bridge per tenant's network on compute node). Right? 2) The OVS quantum plugin seems to implement the core API functions and (viewing the code) I concluded that it just makes maintains the logical mappings e.g. b/w net IDs and VLAN IDs in a database. So how is this mapping implemented on the actual ports of OVS? Is it the OVS quantum agent responsible for directing the packets to correct input/output ports based on the updates that it gets from the database? In VLAN-mode, its even simpler than that. The agent simply puts each port as a VLAN access port for the right VLAN, based on the database, and then has OVS perform standard L2 learning to forward packets. good to know. 3) The quantum admin guide says that the nova client will be the main user of quantum and will interact with it via REST API, so it would be nice if someone can point me to the code (file path name etc.) where this happens. This is the QuantumManager code in Nova: https://github.com/openstack/nova/tree/master/nova/network/quantum One word of warning: this code will be being simplified and largely removed in Folsom, so while its useful to look at it to learn about Quantum, I'd ask around before investing the time to make significant changes to the code. PS: What is the purpose of Quantum Manager in this architecture and where should I look for its code? Thanks for the reference. I have looked at the code and just to affirm my understanding please confirm/correct/answer the following: Quantum manager is responsible for configuring the network for new instances that spin up. When a tenant adds a port to his logical network the request will be forwarded to this manager by Nova and then Manager (using quantum client) would talk to quantum service/server (where can I see its code?) with the REST API. According to documentation, the quantum service is responsible for loading the plugin and passing the REST API calls to the plugin. The plugin then updates the database. Rest of the work is done by quantum agent. see above :) Thanks again for clarification. Since, I am still trying to understand the data flow, please pardon me for questions that are confusing. Salman ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ 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] OpenStack Quantum plugins
Hi Hitesh, Thanks for the considerate reply. Please see the inline comments. On Fri, Apr 27, 2012 at 1:25 AM, Salman Malik salma...@live.com wrote: Hi All, I am trying to learn the functionality of Quantum plugins used in OpenStack. I have read through the Quantum Admin Guide and had few basic/quick question about quantum and OVS interaction with it: 1) OVS can have ports in which vNICS can be plugged, so why does it need to use an integration bridge for connecting all VMs on the same node to a network? [Hitesh]: As far as I know that OVS have more features over the Linux bridge, for example, VM isolation, mobility and security. These can be configured by remote controller. To help and gian the control on all these activities the integration bridge is required. I am not sure about it but I Dan or Salvotore can explain this better way. You can find the more information here http://openvswitch.org/support/ Now, what I have understood from Dan's reply is that OVS itself consists of these bridges (each bridge on a node, being called as an integration bridge). Correct me if I am wrong. 2) The OVS quantum plugin seems to implement the core API functions and (viewing the code) I concluded that it just makes maintains the logical mappings e.g. b/w net IDs and VLAN IDs in a database. So how is this mapping implemented on the actual ports of OVS? Is it the OVS quantum agent responsible for directing the packets to correct input/output ports based on the updates that it gets from the database? [Hitesh]: OVS agent is responsible for to update the database(accoding to actions have been told) for the local server as well Quantum server. As far as I know OVS quantum is not responsible for directing the packets to correct in/op, This job is hadled by OVS core module on the server (datapath). OVS agent only updates the database and creation bridge etc.. Dan or Salvotore can be explained more... Are you sure that quantum agent updates the database? I used to think that it only grabs updates by looking into the database (which is actually modified by the plugin). I am not sure so just confirming. 3) The quantum admin guide says that the nova client will be the main user of quantum and will interact with it via REST API, so it would be nice if someone can point me to the code (file path name etc.) where this happens. [Hitesh]: You can see the devstack script where we are configuring nove-network to quantum. thats the enry point for the nova-network to communicate to quantum. I will share soon more on this. Thanks Hitesh for sharing you knowledge :) Can you comment on how nova-network interacts with Quantum-manager? However, I tried my best to give to these answers. Please feel free to correct me if anything needs to share more. Salman, Let me know if you want more info about this. I will be happy to share Thanks again Hitesh. I appreciate your help. Salman ___ Mailing list: https://launchpad.net/~openstack Post to : 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
Re: [Openstack] [Netstack] OpenStack Quantum plugins
Thank you both for furnishing the references and providing great explanations. Though I had looked at some of them earlier, but now looking at them again with your explanations in mind, makes a lot of sense. However, there is one last question: I understand that the API client calls are made to the REST API server running at port 9696 (by default), but what I haven't yet understood is how these API calls are passed to/fro the Quantum plugin. After some searching through the Quantum plugins' code directory, I found a rest.py file in Ryu plugin directory that (seems to ) register handler functions with API server that may get called when API server receives a call, but I am not sure. Is it how the OVS plugin works as well? I mean does all plugin register callback functions with API server (just asking because I couldn't find anything similar in rest of plugins' code). Thanks, Salman Date: Sun, 29 Apr 2012 15:01:03 +0530 Subject: Re: [Netstack] [Openstack] OpenStack Quantum plugins From: hitesh.wade...@gmail.com To: salma...@live.com; netst...@lists.launchpad.net; openstack@lists.launchpad.net CC: d...@nicira.com Hi Salman, I think Dan explained pretty well, which will be covered all the quantum thoughts that you have asked me. There might be some code changes are going to happen for Folsom design feature implementation. Also, please have a look at here, 1. http://wiki.openstack.org/QuantumAPIUseCases 2. http://qconlondon.com/dl/qcon-london-2012/slides/SalvatoreOrlando_QuantumVirtualNetworksForOpenStackClouds.pdf 3. http://www.slideshare.net/danwent/quantum-folsom-summit-developer-overview 4. http://www.slideshare.net/danwent/openstack-quantum-intro-os-meetup-32612 If you go to Salvatore's 'Inside_Quamtum' 'slide, It provides quite a good deal of details concerning about How the nova interacts with Quantum. On the VIF driver side, that is a piece which runs in the nova address space, and tells VM being spawned how their VIF should be plugged into networks. There are VIF drivers for Quantum as well as VIF drivers for the other network managers. VIF drivers can be both plugin and hypervisor specific. For instance, nova/virt/hypervisor_driver/vif (e.g.: nova/virt/xenapi/vif). For OVS and more on Network, please refer this link, http://openvswitch.org/support/, go for 1. J. Pettit, J. Gross “Open vSwitch Overview,” 2. S. Horman, “An Introduction to Open vSwitch,” If you want to see advance networking virtualization, refer these papers, 1. J. Pettit, J. Gross, B. Pfaff, M. Casado, S. Crosby, “Virtual Switching in an Era of Advanced Edges,” 2. B. Pfaff, J. Pettit, T. Koponen, K. Amidon, M. Casado, S. Shenker, “Extending Networking into the Virtualization Layer,” I hope these will help. I am also exploring the code :) (still learner) Thanks, Hitesh On Sun, Apr 29, 2012 at 2:41 AM, Dan Wendlandt d...@nicira.com wrote: On Fri, Apr 27, 2012 at 4:44 PM, Salman Malik salma...@live.com wrote: Hi Dan, Thanks for replying. There are few more questions: I am trying to learn the functionality of Quantum plugins used in OpenStack. I have read through the Quantum Admin Guide and had few basic/quick question about quantum and OVS interaction with it: 1) OVS can have ports in which vNICS can be plugged, so why does it need to use an integration bridge for connecting all VMs on the same node to a network? I'm not sure I follow what question you're asking. When OVS is running on a host, it has one or more bridges, and bridges have ports. A linux device representing the vNIC must be added as a port of a bridge being managed by the Quantum plugin. We call this bridge the integration bridge. The Quantum plugin can then configure the ports and bridges appropriately to forward traffic based on the logical model created via the Quantum API. Can you be more precise about what you're asking here? In short it means that the OVS is managing the linux bridges and the linux devices representing vNICs must be added to these bridges (Does Quantum manager adds these devices to bridges?). You have to be a bit careful here, because the linux bridge and open vswitch are two different things (you can think of open vswitch as an advanced version of the linux bridge). A driver in the Nova virt layer is actually the one who creates the linux devices that map to vNICs. For example, libvirt creates these devices as directed by the libvirt driver code: https://github.com/openstack/nova/blob/master/nova/virt/libvirt/vif.py . This code attaches the linux device to an OVS bridge as a port. The rest of the configuration of that port and the OVS bridge is up to the OVS plugin agent. And when you say that quantum plugin configures the ports and bridges appropriately to forward traffic, you mean that it updates the database and then quantum agent then assures the correct mapping of ports/network ids to logical networks
[Openstack] Instance IP assignment problem
Hi Guys, Can anyone provide any insight to the following question: https://answers.launchpad.net/nova/+question/195439 Thanks, Salman___ 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] Instance IP assignment problem
Hi Jorge, Thanks for looking into the post. I have made changes to the nova.conf file so that I only use 10.0.0.x network (but the problem is still the same). For this configuration, I assume that it will give out IPs to instances starting from 10.0.0.11. And just to inform you, my eth1 is configured to be 10.0.0.10 (which is a VM itself, and eth1 is configured as a host-only network with no DHCP) and this interface is plugged in the integration bridge used by quantum plugins. Thanks, Salman PS: Error log of a launched instance is also attached. Date: Tue, 1 May 2012 19:03:49 +0200 Subject: Re: [Openstack] Instance IP assignment problem From: jorge.delac...@stackops.com To: salma...@live.com CC: openstack@lists.launchpad.net Im not really sure but you are using range for your environment 10.0.3.x and 10.0.0.x for fixed. Can you attach a nova network conf? Regards El 01/05/2012 18:56, Salman Malik salma...@live.com escribió: Hi Guys, Can anyone provide any insight to the following question: https://answers.launchpad.net/nova/+question/195439 Thanks, Salman ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp Error_log Description: Binary data nova.conf Description: Binary data ___ 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] Instance IP assignment problem
Regarding L3 gateway, I believe its not necessary to have one (as the VM hasn't obtained an IP right now, so it can't talk to anything outside its net), but I am not sure. Regarding your problem, do you see any DHCP responses from the DHCP server ? I am asking this because I was having a similar problem earlier where I was getting assigned an IP address no in my desired fixed_network and I believe that was cause by another interfering DHCP server that was replying to discover messages before the nova-network could. Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: salma...@live.com CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:06:01 +0200 Hi Salman, I'm thinking about a networking issue. Where is your L3 gateway in this architecture ? Maybe do you need an ip helper tool to redirect DHCP broadcast ? What do you think about my problem (follow up to my last e-mail) ? Thanks Emilien Le mardi 01 mai 2012 à 14:00 -0500, Salman Malik a écrit : Hi, Here is the error log: http://pastebin.com/KrNZDrvD and nova.conf: http://pastebin.com/Fvd6dSZs Emilien, I am trying to get an understanding of how different Quantum plugins work with OpenStack. Ryu plugin is particularly interesting as it uses an OpenFlow controller to configure Vswitches. The problem I am faced with is (I think ) that I already have a private network and Quantum should assign IP addresses to instances using DHCP. But instances send out discover message on laucnh but never find a DHCP server (although there are 2 dnsmasqs running). Any ideas? Thanks, Salman Date: Tue, 1 May 2012 20:43:44 +0200 Subject: Re: [Openstack] Instance IP assignment problem From: jorge.delac...@stackops.com To: emilien.openst...@gmail.com CC: openstack@lists.launchpad.net; salma...@live.com Hi Emilien and Salman, Please, could you upload all the files, errors and conf in pastebin or something like that? I have troubles to open in phone :) Thank you El 01/05/2012 20:39, Emilien Macchi emilien.openst...@gmail.com escribió: Hi, I have a similar problem when I create a network per project_id with Quantum. My VMs don't get IP and I can't understand why today. But when I create a private network for all projects, VMs get an IP and all is working well. Do you have the same problem ? Salman, I'm interesting about your nova.conf. I can see you are using Ryu ? Can you tell me more about your use case or architecture ? Thanks Le mardi 01 mai 2012 à 12:28 -0500, Salman Malik a écrit : Hi Jorge, Thanks for looking into the post. I have made changes to the nova.conf file so that I only use 10.0.0.x network (but the problem is still the same). For this configuration, I assume that it will give out IPs to instances starting from 10.0.0.11. And just to inform you, my eth1 is configured to be 10.0.0.10 (which is a VM itself, and eth1 is configured as a host-only network with no DHCP) and this interface is plugged in the integration bridge used by quantum plugins. Thanks, Salman PS: Error log of a launched instance is also attached. Date: Tue, 1 May 2012 19:03:49 +0200 Subject: Re: [Openstack] Instance IP assignment problem From: jorge.delac...@stackops.com To: salma...@live.com CC: openstack@lists.launchpad.net Im not really sure but you are using range for your environment 10.0.3.x and 10.0.0.x for fixed. Can you attach a nova network conf? Regards El 01/05/2012 18:56, Salman Malik salma...@live.com escribió: Hi Guys, Can anyone provide any insight to the following question: https://answers.launchpad.net/nova/+question/195439 Thanks, Salman ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post
Re: [Openstack] Instance IP assignment problem
It may help if you can share the log of your launched instance as well. There is a possibility that we both are having the same issue. Netstack developers can give a definitive answer to this, but it would be interesting to learn what goes wrong with a launched instance. Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: salma...@live.com CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:26:26 +0200 Le mardi 01 mai 2012 à 14:22 -0500, Salman Malik a écrit : Regarding L3 gateway, I believe its not necessary to have one (as the VM hasn't obtained an IP right now, so it can't talk to anything outside its net), but I am not sure. Regarding your problem, do you see any DHCP responses from the DHCP server ? I am asking this because I was having a similar problem earlier where I was getting assigned an IP address no in my desired fixed_network and I believe that was cause by another interfering DHCP server that was replying to discover messages before the nova-network could. Here my nova.conf and I don't have any interfering DHCP server : https://github.com/EmilienM/doc-openstack/blob/master/Configuration%20Files/Essex-1/nova.conf Thanks Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: salma...@live.com CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:06:01 +0200 Hi Salman, I'm thinking about a networking issue. Where is your L3 gateway in this architecture ? Maybe do you need an ip helper tool to redirect DHCP broadcast ? What do you think about my problem (follow up to my last e-mail) ? Thanks Emilien Le mardi 01 mai 2012 à 14:00 -0500, Salman Malik a écrit : Hi, Here is the error log: http://pastebin.com/KrNZDrvD and nova.conf: http://pastebin.com/Fvd6dSZs Emilien, I am trying to get an understanding of how different Quantum plugins work with OpenStack. Ryu plugin is particularly interesting as it uses an OpenFlow controller to configure Vswitches. The problem I am faced with is (I think ) that I already have a private network and Quantum should assign IP addresses to instances using DHCP. But instances send out discover message on laucnh but never find a DHCP server (although there are 2 dnsmasqs running). Any ideas? Thanks, Salman Date: Tue, 1 May 2012 20:43:44 +0200 Subject: Re: [Openstack] Instance IP assignment problem From: jorge.delac...@stackops.com To: emilien.openst...@gmail.com CC: openstack@lists.launchpad.net; salma...@live.com Hi Emilien and Salman, Please, could you upload all the files, errors and conf in pastebin or something like that? I have troubles to open in phone :) Thank you El 01/05/2012 20:39, Emilien Macchi emilien.openst...@gmail.com escribió: Hi, I have a similar problem when I create a network per project_id with Quantum. My VMs don't get IP and I can't understand why today. But when I create a private network for all projects, VMs get an IP and all is working well. Do you have the same problem ? Salman, I'm interesting about your nova.conf. I can see you are using Ryu ? Can you tell me more about your use case or architecture ? Thanks Le mardi 01 mai 2012 à 12:28 -0500, Salman Malik a écrit : Hi Jorge, Thanks for looking into the post. I have made changes to the nova.conf file so that I only use 10.0.0.x network (but the problem is still the same). For this configuration, I assume that it will give out IPs to instances starting from 10.0.0.11. And just to inform you, my eth1 is configured to be 10.0.0.10 (which is a VM itself, and eth1 is configured as a host-only network with no DHCP) and this interface is plugged in the integration bridge used by quantum plugins. Thanks, Salman PS: Error log of a launched instance is also attached. Date: Tue, 1 May 2012 19:03:49 +0200 Subject: Re: [Openstack] Instance IP assignment problem
Re: [Openstack] Instance IP assignment problem
Hi Jorge, I tried the parameter but to no avail. Also this post (https://answers.launchpad.net/nova/+question/148445) says that it defaults to my_ip if not specified. Any other thoughts are much appreciated. Thanks, Salman Date: Tue, 1 May 2012 21:34:48 +0200 Subject: RE: [Openstack] Instance IP assignment problem From: jorge.delac...@stackops.com To: salma...@live.com CC: openstack@lists.launchpad.net; emilien.openst...@gmail.com Hi, In your conf Dalman I dont see a routing_sourceip and in Emilien's cong yes. Try with this parameter. El 01/05/2012 21:00, Salman Malik salma...@live.com escribió: Hi, Here is the error log: http://pastebin.com/KrNZDrvD and nova.conf: http://pastebin.com/Fvd6dSZs Emilien, I am trying to get an understanding of how different Quantum plugins work with OpenStack. Ryu plugin is particularly interesting as it uses an OpenFlow controller to configure Vswitches. The problem I am faced with is (I think ) that I already have a private network and Quantum should assign IP addresses to instances using DHCP. But instances send out discover message on laucnh but never find a DHCP server (although there are 2 dnsmasqs running). Any ideas? Thanks, Salman Date: Tue, 1 May 2012 20:43:44 +0200 Subject: Re: [Openstack] Instance IP assignment problem From: jorge.delac...@stackops.com To: emilien.openst...@gmail.com CC: openstack@lists.launchpad.net; salma...@live.com Hi Emilien and Salman, Please, could you upload all the files, errors and conf in pastebin or something like that? I have troubles to open in phone :) Thank you El 01/05/2012 20:39, Emilien Macchi emilien.openst...@gmail.com escribió: Hi, I have a similar problem when I create a network per project_id with Quantum. My VMs don't get IP and I can't understand why today. But when I create a private network for all projects, VMs get an IP and all is working well. Do you have the same problem ? Salman, I'm interesting about your nova.conf. I can see you are using Ryu ? Can you tell me more about your use case or architecture ? Thanks Le mardi 01 mai 2012 à 12:28 -0500, Salman Malik a écrit : Hi Jorge, Thanks for looking into the post. I have made changes to the nova.conf file so that I only use 10.0.0.x network (but the problem is still the same). For this configuration, I assume that it will give out IPs to instances starting from 10.0.0.11. And just to inform you, my eth1 is configured to be 10.0.0.10 (which is a VM itself, and eth1 is configured as a host-only network with no DHCP) and this interface is plugged in the integration bridge used by quantum plugins. Thanks, Salman PS: Error log of a launched instance is also attached. Date: Tue, 1 May 2012 19:03:49 +0200 Subject: Re: [Openstack] Instance IP assignment problem From: jorge.delac...@stackops.com To: salma...@live.com CC: openstack@lists.launchpad.net Im not really sure but you are using range for your environment 10.0.3.x and 10.0.0.x for fixed. Can you attach a nova network conf? Regards El 01/05/2012 18:56, Salman Malik salma...@live.com escribió: Hi Guys, Can anyone provide any insight to the following question: https://answers.launchpad.net/nova/+question/195439 Thanks, Salman ___ Mailing list: https://launchpad.net/~openstack Post to : 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 ___ 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] Instance IP assignment problem
? Thanks, Salman From: d...@nicira.com Date: Tue, 1 May 2012 14:40:58 -0700 Subject: Re: [Openstack] Instance IP assignment problem To: salma...@live.com CC: jorge.delac...@stackops.com; emilien.openst...@gmail.com; openstack@lists.launchpad.net On Tue, May 1, 2012 at 12:00 PM, Salman Malik salma...@live.com wrote: Hi, Here is the error log: http://pastebin.com/KrNZDrvD and nova.conf: http://pastebin.com/Fvd6dSZs Emilien, I am trying to get an understanding of how different Quantum plugins work with OpenStack. Ryu plugin is particularly interesting as it uses an OpenFlow controller to configure Vswitches. The problem I am faced with is (I think ) that I already have a private network and Quantum should assign IP addresses to instances using DHCP. But instances send out discover message on laucnh but never find a DHCP server (although there are 2 dnsmasqs running). I would first try this out with something like the OVS plugin (which incidentally uses OpenFlow as wel). This is a pretty commonly used configuration, and will help determine if the problem is in your configuration, or the Ryu plugin in particular. I would also try and see if dnsmasq is actually getting the request and sending a reply. You should be able to tcpdump on the linux device that dnsmasq is bound to (should start with gw-*). Alternately, you could look in /var/log/syslog (i think?) to see if dnsmasq if logging that is correctly receiving the DHCP requests. Dan Any ideas? Thanks, Salman Date: Tue, 1 May 2012 20:43:44 +0200 Subject: Re: [Openstack] Instance IP assignment problem From: jorge.delac...@stackops.com To: emilien.openst...@gmail.com CC: openstack@lists.launchpad.net; salma...@live.com Hi Emilien and Salman, Please, could you upload all the files, errors and conf in pastebin or something like that? I have troubles to open in phone :) Thank you El 01/05/2012 20:39, Emilien Macchi emilien.openst...@gmail.com escribió: Hi, I have a similar problem when I create a network per project_id with Quantum. My VMs don't get IP and I can't understand why today. But when I create a private network for all projects, VMs get an IP and all is working well. Do you have the same problem ? Salman, I'm interesting about your nova.conf. I can see you are using Ryu ? Can you tell me more about your use case or architecture ? Thanks Le mardi 01 mai 2012 à 12:28 -0500, Salman Malik a écrit : Hi Jorge, Thanks for looking into the post. I have made changes to the nova.conf file so that I only use 10.0.0.x network (but the problem is still the same). For this configuration, I assume that it will give out IPs to instances starting from 10.0.0.11. And just to inform you, my eth1 is configured to be 10.0.0.10 (which is a VM itself, and eth1 is configured as a host-only network with no DHCP) and this interface is plugged in the integration bridge used by quantum plugins. Thanks, Salman PS: Error log of a launched instance is also attached. Date: Tue, 1 May 2012 19:03:49 +0200 Subject: Re: [Openstack] Instance IP assignment problem From: jorge.delac...@stackops.com To: salma...@live.com CC: openstack@lists.launchpad.net Im not really sure but you are using range for your environment 10.0.3.x and 10.0.0.x for fixed. Can you attach a nova network conf? Regards El 01/05/2012 18:56, Salman Malik salma...@live.com escribió: Hi Guys, Can anyone provide any insight to the following question: https://answers.launchpad.net/nova/+question/195439 Thanks, Salman ___ Mailing list: https://launchpad.net/~openstack Post to : 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 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ 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
Re: [Openstack] Instance IP assignment problem
Hi Emilien, In your configuration you have the following flags: --flat_network_bridge=br100--floating_range=10.68.5.0/24Can you please tell me why you need br100 when you are using br-int with OVS ? Secondly, you seem to use floating_range flag as the second flag. I assume that it is the pool of addresses that your instances will get IP from, right? It may be worthwhile to modify it to fixed_range because Bilal suggested here that this config worked for him. Let us know. Thanks, Salman Date: Thu, 3 May 2012 08:29:42 -0400 Subject: Re: [Openstack] Instance IP assignment problem From: soh...@cs.toronto.edu To: emilien.openst...@gmail.com CC: ahal...@griddynamics.com; openstack@lists.launchpad.net; salma...@live.com Oops accidently hit send on my phone. I had a similar problem before. My problem was that the nic driver on the compute instance (your Essex 2) was dropping vlan tags, and then, openvswitch wasn't delivering packets. You can check it using tcpdump -e -vvv. BTW, if you are using virtualbox to run openstack, make sure you are not using vbox intel drivers. Use pcnet fast instead. OVS splinter may also be useful. Hope that helps. CheersSoheil On Thursday, May 3, 2012, Soheil Hassas Yeganeh wrote: I had a similar problem before. My problem was that the nic driver on the compute instance (your Essex 2) was dropping vlan tags, and then, openvswitch wasn can you find dhcp requests by using tcpdump for example ? sorry for off-topic but there may be many reasons of such issue with dhcp. last one for me was old dhcp client(Ubuntu) and udp checksum error. I have essex on centos and was trying ubuntu vm. On Thu, May 3, 2012 at 12:48 PM, Emilien Macchi emilien.openst...@gmail.com wrote: All seems alright but not working yet. http://paste.openstack.org/show/14791/ I have executed on both servers : ovs-vsctl add-port br-int eth1 Need I do something else ? How the DHCP is working in this case ? Le jeudi 03 mai 2012 à 09:29 +0100, Bilel Msekni a écrit : Then the problem isn't in the instance but in the nova-network service , please check if it is working well as well as give us the output log when you attempt to create a new instance. Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: ski...@hotmail.fr CC: salma...@live.com; openstack@lists.launchpad.net Date: Thu, 3 May 2012 10:21:37 +0200 Fixed IP Le jeudi 03 mai 2012 à 09:15 +0100, Bilel Msekni a écrit : Fixed IP or Floating IP ? From: emilien.openst...@gmail.com To: salma...@live.com Date: Thu, 3 May 2012 09:55:31 +0200 CC: openstack@lists.launchpad.net Subject: Re: [Openstack] Instance IP assignment problem Hi, As I told you, I have also a problem for instance IP assignement. My architecture : I use Quantum with OVS plugin on 2 servers Essex-1 Essex-2. Essex-1 runs all services and Essex-2 runs OVS, Quantum-agent nova-compute only. You can see more details here. My configurations files are here and in my documentation. Problem Description : When an instance is created in ESSEX-1, all is working (network). But when the VM is started on ESSEX-2, it does not get an IP address. (log file) I'm sure the problem comes from OVS connection with ESSEX-1. Do I need to configure something like a trunk or a tunnel between Essex-1 Essex-2 ? I miss something in my configuration, if you have any idea... Regards Emilien Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a écrit : It may help if you can share the log of your launched instance as well. There is a possibility that we both are having the same issue. Netstack developers can give a definitive answer to this, but it would be interesting to learn what goes wrong with a launched instance. ___ 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] Instance IP assignment problem
I see. So where do you use private IP's in your setup ? Thanks, Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: salma...@live.com CC: soh...@cs.toronto.edu; ahal...@griddynamics.com; openstack@lists.launchpad.net Date: Thu, 3 May 2012 17:02:23 +0200 Hi Salman, Le jeudi 03 mai 2012 à 09:47 -0500, Salman Malik a écrit : Hi Emilien, In your configuration you have the following flags: --flat_network_bridge=br100 I'm going to try to change it in both servers. --floating_range=10.68.5.0/24 That's actually my public pool, sot it's not my fixed pool (privates IPs). After my tests, I will let you know of course. Thanks, Regards Can you please tell me why you need br100 when you are using br-int with OVS ? Secondly, you seem to use floating_range flag as the second flag. I assume that it is the pool of addresses that your instances will get IP from, right? It may be worthwhile to modify it to fixed_range because Bilal suggested here that this config worked for him. Let us know. Thanks, Salman Date: Thu, 3 May 2012 08:29:42 -0400 Subject: Re: [Openstack] Instance IP assignment problem From: soh...@cs.toronto.edu To: emilien.openst...@gmail.com CC: ahal...@griddynamics.com; openstack@lists.launchpad.net; salma...@live.com Oops accidently hit send on my phone. I had a similar problem before. My problem was that the nic driver on the compute instance (your Essex 2) was dropping vlan tags, and then, openvswitch wasn't delivering packets. You can check it using tcpdump -e -vvv. BTW, if you are using virtualbox to run openstack, make sure you are not using vbox intel drivers. Use pcnet fast instead. OVS splinter may also be useful. Hope that helps. Cheers Soheil On Thursday, May 3, 2012, Soheil Hassas Yeganeh wrote: I had a similar problem before. My problem was that the nic driver on the compute instance (your Essex 2) was dropping vlan tags, and then, openvswitch wasn can you find dhcp requests by using tcpdump for example ? sorry for off-topic but there may be many reasons of such issue with dhcp. last one for me was old dhcp client(Ubuntu) and udp checksum error. I have essex on centos and was trying ubuntu vm. On Thu, May 3, 2012 at 12:48 PM, Emilien Macchi emilien.openst...@gmail.com wrote: All seems alright but not working yet. http://paste.openstack.org/show/14791/ I have executed on both servers : ovs-vsctl add-port br-int eth1 Need I do something else ? How the DHCP is working in this case ? Le jeudi 03 mai 2012 à 09:29 +0100, Bilel Msekni a écrit : Then the problem isn't in the instance but in the nova-network service , please check if it is working well as well as give us the output log when you attempt to create a new instance. Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: ski...@hotmail.fr CC: salma...@live.com; openstack@lists.launchpad.net Date: Thu, 3 May 2012 10:21:37 +0200 Fixed IP Le jeudi 03 mai 2012 à 09:15 +0100, Bilel Msekni a écrit : Fixed IP or Floating IP ? From: emilien.openst...@gmail.com To: salma...@live.com Date: Thu, 3 May 2012 09:55:31 +0200 CC: openstack@lists.launchpad.net Subject: Re: [Openstack] Instance IP assignment problem Hi
[Openstack] Unable to retrieve details for instance
Hi Guys, I am having problem with accessing details of the newly spun instances. I get this error at the dashboard: Unable to retrieve details for instance Instance-ID. There is also a stream of [error] in the horizon output (I don't know where its log go). Can someone point out any solutions? Thanks. ___ 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] Devstack installation script changed ?
Hi Dan, I am having internet connectivity issues on the node that I was installing the new devstack script. Hope it gets resolved today and then I would send 'git log' output to you. Also, although the line number that I reported is different from the one you sent, I think these lines are the same (may be some code has been added to the new devstack script). Vinay, I got around this problem by replacing $QUANTUM_OVS_CONF_FILE with $QUANTUM_PLUGIN_INI_FILE in line 1062 (assuming you are using the same stack.sh as I was) of the stack.sh file. But as Dan said may be we could remove this line altogether (I haven't tried doing that yet). Thanks, Salman From: d...@nicira.com Date: Sun, 13 May 2012 22:54:18 -0700 Subject: Re: [Openstack] Devstack installation script changed ? To: salma...@live.com; openstack@lists.launchpad.net On Sun, May 13, 2012 at 12:24 PM, Salman Malik salma...@live.com wrote: In the latest script that I downloaded, I had a problem in the following line: https://github.com/openstack-dev/devstack/blob/master/stack.sh#L1062 where instead of having $QUANTUM_PLUGIN_INI_FILE at the end of line, I had $QUANTUM_OVS_CONF_FILE. Changing it had fixed this issue but now I am seeing another problem related to ovsdb-server. The provider = line belongs in the QUANTUM_PLUGIN_INI_FILE , its impossible for things to have worked without that. Perhaps you tweaked the file? Either that or perhaps someone temporarily submitted a change to devstack that broke things. I think you have misunderstood me here. In the latest script I had $QUANTUM_OVS_CONF_FILE in the line mentioned above, rather than having $QUANTUM_PLUGIN_INI_FILE (which as you said contains the provider info). So I replaced $QUANTUM_OVS_CONF_FILE with $QUANTUM_PLUGIN_INI_FILE. I'm confused here, as the git history says that this line in the file hasn't changed since March, so it seems odd that it would have say $QUANTUM_OVS_CONF_FILE, rather than the correct $QUANTUM_PLUGIN_INI file. See: https://github.com/openstack-dev/devstack/blame/master/stack.sh Perhaps I'm still misunderstanding you. Can you reproduce this on a clean checkout of devstack? If so, can you send me the first couple lines from running git log in the devstack directory? Dan When doing sudo ovs-vsctl --no-wait -- --if -exists del-br br-int, script outputs show the following warning: May 13 11:55:46|2|stream_unix|ERR|/tmp/stream-unix.3587.o:connection to /use/local/var/run/openvswitch/db.sock failed: No such file or directory and then it keeps on attempting to reconnect. are you able to run ovs-vsctl commands outside of devstack? Yes, I am able to run ovs-vsctl outside of devstack. For example, sudo ovs-vsctl --version Did you install OVS by yourself, or just using the packages referenced by devstack? Anything interesting in /var/log/openvswitch ? I installed OVS by myself as well, because after enabling OVS plugin stack.sh was failing with missing ini file, so I installed OVS separately in hope that it would work correctly with devstack. Thanks, Salman I have checked that ovsdb-server is running. Any thoughts? Salman From: d...@nicira.com Date: Sat, 12 May 2012 19:25:30 -0700 Subject: Re: [Openstack] Devstack installation script changed ? To: salma...@live.com CC: openstack@lists.launchpad.net On Sat, May 12, 2012 at 7:07 PM, Salman Malik salma...@live.com wrote: Hi, The devstack script changes all the time actually, see: https://github.com/openstack-dev/devstack/commits/master I am asking this because last time when I tried devstack on virtualbox, I got OpenVswitch plugin installed with it (along with ovs_quantum_plugin.ini file) and could use it with quantum but now when I am trying to install devstack on a physical node, the script isn't installing open vswitch plugin because the directory structure of installed files seems to be different because when I run ./stack.sh after adding q-agt and q-svc to enabled services in localrc, the installation fails complaining that /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini is not found. But this path was present in my previous installation on virtualbox (I don't seem to remember if I had done anything special to get this plugin config in this path). Devstack with Quantum create /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini, using /opt/stack/quantum/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini as the initial version. See: https://github.com/openstack-dev/devstack/blob/master/stack.sh#L1103 Dan Comments please? Salman ___ 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] Understanding Integration Bridge and MACs
In addition to the mail that follows, I am having some problem with quantum networks as well. When I create a network using : sudo nova-manage network create --label=$tenant0 --fixed_range_v4=$iprange0 --project_id=$tenant0 I can see the network using both quantum list_nets $tenant0 and nova-manage network list, but when I delete the network using quantum delete_net $tenant0 $netID, the nova-manage network list still shows the network and when I try to use the same CIDR for another network,I get an error saying CIDR already in use. Shouldn't deleting quantum list_nets and nova-manage network list be consistent with each other ? From: salma...@live.com To: openstack@lists.launchpad.net Subject: Understanding Integration Bridge and MACs Date: Sun, 13 May 2012 19:42:14 -0500 Hi Dan and Others, I am trying to understand the actions taken by Ryu when the new instance sends DHCP discover message to dnsmasq. When I launch new instannce it keeps on sending discover messages and controller keeps on dropping these messages. But looking at the traffic I couldn't exactly map which MAC address belonged to which entity. Can someone help me with my understanding of the MAC addresses. Using ifconfig , ovs-ofctl show br-int and ovs-ofctl snoop br-int (output shown after MAC addresses), I know exactly about some MAC addresses and can't figure out some of them: Interfaces |HWAddress |IP-addr - eth0|08:00:27:7a:ff:65|10.0.3.15 eth1|08:00:27:16:d5:09 |10.0.0.10 plugged into br-int gw-82bd3a73-dc|fa:16:3e:49:57:1b |10.0.0.1 plugged into br-int (this is the --listen-address of my two dnsmasqs) br-int |08:00:27:16:d5:09 | why doesn't bridge have no IP ? new-instance |02:d8:47:48:35:26 == MAC address of newly launched instance? (see output below) Unkown |fa:16:3e:5e:02:17 ==Seemingly unknown MAC address(which is related to the new instance?) Unkown |33:33:00:00:00:16 == MAC address related to multicast ? Questions: 1. What is gw-82bd3a73-dc interface ? 2. I am kind of unsure why br-int is so useful? 3. Why doesn't br-int don't have any IP address? 4. Why do we need to plugin a compute node's interface to br-int? (so that guest instances on remote host can communicate with each other?) 5. What is the relationship b/w 02:d8:47:48:35:26 and fa:16:3e:5e:02:17 MAC addresses in the following output? = Output of : ovs-ofctl snoop br-int = OFPT_ECHO_REQUEST (xid=0x0): 0 bytes of payload OFPT_ECHO_REPLY (xid=0x0): 0 bytes of payload OFPT_PORT_STATUS (xid=0x0): ADD: 7(tap76127847-b1): addr:02:d8:47:48:35:26 config: 0 state: LINK_DOWN current:10MB-FD COPPER OFPT_FLOW_MOD (xid=0x491662da): DEL priority=0 buf:0x0 actions=drop OFPT_BARRIER_REQUEST (xid=0x491662db): OFPT_BARRIER_REPLY (xid=0x491662db): OFPT_PORT_STATUS (xid=0x0): MOD: 7(tap76127847-b1): addr:02:d8:47:48:35:26 config: 0 state: 0 current:10MB-FD COPPER OFPT_ECHO_REQUEST (xid=0x0): 0 bytes of payload OFPT_ECHO_REPLY (xid=0x0): 0 bytes of payload OFPT_PACKET_IN (xid=0x0): total_len=90 in_port=7 data_len=90 buffer=0x0167 tunnel0:in_port0007:tci(0) macfa:16:3e:5e:02:17-33:33:00:00:00:16 type86dd proto58 tos0 ipv6::-ff02::16 port143-0 fa:16:3e:5e:02:17 33:33:00:00:00:16, ethertype IPv6 (0x86dd), length 90: :: ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 OFPT_PACKET_OUT (xid=0x491662dc): in_port=7 actions_len=0 actions=drop buffer=0x0167 OFPT_PACKET_IN (xid=0x0): total_len=322 in_port=7 data_len=128 buffer=0x0168 tunnel0:in_port0007:tci(0) macfa:16:3e:5e:02:17-ff:ff:ff:ff:ff:ff type0800 proto17 tos0 ip0.0.0.0-255.255.255.255 port68-67 fa:16:3e:5e:02:17 ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 128: truncated-ip - 194 bytes missing! 0.0.0.0.68 255.255.255.255.67: BOOTP/DHCP, Request from fa:16:3e:5e:02:17, length 280 OFPT_PACKET_OUT (xid=0x491662dd): in_port=7 actions_len=0 actions=drop buffer=0x0168 OFPT_PACKET_IN (xid=0x0): total_len=78 in_port=7 data_len=78 buffer=0x0169 fa:16:3e:5e:02:17 ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 128: truncated-ip - 194 bytes missing! 0.0.0.0.68 255.255.255.255.67: BOOTP/DHCP, Request from fa:16:3e:5e:02:17, length 280 OFPT_PACKET_OUT (xid=0x491662e3): in_port=7 actions_len=0 actions=drop buffer=0x016e OFPT_PACKET_IN (xid=0x0): total_len=70 in_port=7 data_len=70 buffer=0x016f tunnel0:in_port0007:tci(0) macfa:16:3e:5e:02:17-33:33:00:00:00:02 type86dd proto58 tos0 ipv6fe80::f816:3eff:fe5e:217-ff02::2
Re: [Openstack] Understanding Integration Bridge and MACs
Thanks for quick reply Dan.
Here is another problem: there are some networks that show up in nova-manage
network list command but when I delete them using nova-manage network delete
--uuid uuid, I get get this error:
2012-05-02 02:43:57 TRACE nova File
/opt/stack/nova/nova/network/quantum/client.py, line 196, in do_request
2012-05-02 02:43:57 TRACE nova _(Quantum entity not found: %s), data)
2012-05-02 02:43:57 TRACE nova QuantumNotFoundException: (u'Quantum entity not
found: %s', '{QuantumError: {message: Unable to find a network with the
specified identifier., type: NetworkNotFound, detail: Network
8fdced2b-8235-4db8-b063-08e7cc9b78d8 could not be found}}')
Whereas other networks get deleted with great ease.
Seems to be a problem with database consistency? I have tried to restart the
stack as a whole, but get the same error...
From: d...@nicira.com
Date: Tue, 15 May 2012 09:29:02 -0700
Subject: Re: [Openstack] Understanding Integration Bridge and MACs
To: salma...@live.com
CC: openstack@lists.launchpad.net
Hi Salman,
You need to delete by UUID (since if quantum is used with melange, fixed_range
is not guaranteed to be unique).
just use:
nova network delete --uuid uuid
I just yesterday noticed that this was missing from the Quantum Admin Guide and
added it:
http://docs.openstack.org/trunk/openstack-network/admin/content/Net-Create-dle455.html
Dan
On Tue, May 15, 2012 at 9:22 AM, Salman Malik salma...@live.com wrote:
Thank you both but when I try to delete any such network using nova-manage
network delete tenant net_ID, I get the following error:
2012-05-02 01:47:59 TRACE nova File /opt/stack/nova/bin/nova-manage, line
867, in delete
2012-05-02 01:47:59 TRACE nova raise Exception(Deleting by fixed_range is
not supported \
2012-05-02 01:47:59 TRACE nova Exception: Deleting by fixed_range is not
supported with the QuantumManager
How can I delete nets defined using fixed_range parameter?
Thanks,
Salman
From: d...@nicira.com
Date: Mon, 14 May 2012 19:23:34 -0700
Subject: Re: [Openstack] Understanding Integration Bridge and MACs
To: salma...@live.com
CC: openstack@lists.launchpad.net
On Mon, May 14, 2012 at 3:19 PM, Salman Malik salma...@live.com wrote:
In addition to the mail that follows, I am having some problem with quantum
networks as well. When I create a network using :
sudo nova-manage network create --label=$tenant0 --fixed_range_v4=$iprange0
--project_id=$tenant0
I can see the network using both quantum list_nets $tenant0 and nova-manage
network list, but when I delete the network using quantum delete_net $tenant0
$netID, the nova-manage network list still shows the network and when I try to
use the same CIDR for another network,I get an error saying CIDR already in
use. Shouldn't deleting quantum list_nets and nova-manage network list be
consistent with each other ?
In Essex, when using Nova all Quantum network creation and deletion must occur
using nova-manage. This is because we store the IP address management data
associated with a network is stored in the Nova database. As Yong mentioned,
in Folsom we are storing IP address management data in Quantum itself, in which
case network creation can happen directly via the Quantum API and Nova VMs will
still be able to get IPs.
Dan
From: salma...@live.com
To: openstack@lists.launchpad.net
Subject: Understanding Integration Bridge and MACs
Date: Sun, 13 May 2012 19:42:14 -0500
Hi Dan and Others,
I am trying to understand the actions taken by Ryu when the new instance sends
DHCP discover message to dnsmasq. When I launch new instannce it keeps on
sending discover messages and controller keeps on dropping these messages. But
looking at the traffic I couldn't exactly map which MAC address belonged to
which entity. Can someone help me with my understanding of the MAC addresses.
Using ifconfig , ovs-ofctl show br-int and ovs-ofctl snoop br-int (output
shown after MAC addresses), I know exactly about some MAC addresses and can't
figure out some of them:
Interfaces |HWAddress |IP-addr
-
eth0|08:00:27:7a:ff:65|10.0.3.15
eth1|08:00:27:16:d5:09 |10.0.0.10
plugged into br-int
gw-82bd3a73-dc|fa:16:3e:49:57:1b |10.0.0.1
plugged into br-int (this is the --listen-address of my two dnsmasqs)
br-int |08:00:27:16:d5:09 |
why doesn't bridge have no IP ?
new-instance |02:d8:47:48:35:26 == MAC address of newly
launched instance? (see output below)
Unkown |fa:16:3e:5e:02:17 ==Seemingly unknown
MAC address(which is related to the new
Re: [Openstack] Understanding Integration Bridge and MACs
Thanks Yamahata. I have tried the all-in-one configuration and it worked without any problems. I will soon try the multi-node setup and will let you know of any problems/questions. I appreciate all the hard work that openstack community is putting in the project. Thanks, Salman Date: Thu, 17 May 2012 21:04:23 +0900 From: yamah...@valinux.co.jp To: salma...@live.com CC: openstack@lists.launchpad.net Subject: Re: [Openstack] Understanding Integration Bridge and MACs Hi. Sorry for delayed replay. Now precreated VM image is available for easy evaluation. It is announced on ryu-de...@lists.sourceforge.net, I site it for sure. I hope you can get successful result. From: FUJITA Tomonori fujita.tomonori@... Subject: pre-configured VM image file for OpenStack environment with Ryu Hi, We created a VM image file that enables you to easily set up multi-node Nova environment with Ryu in your desktop machine: https://github.com/osrg/ryu/wiki/RYU-OpenStack-environment-VM-image-file-HOWTO Enjoy! On Sun, May 13, 2012 at 07:42:14PM -0500, Salman Malik wrote: Hi Dan and Others, I am trying to understand the actions taken by Ryu when the new instance sends DHCP discover message to dnsmasq. When I launch new instannce it keeps on sending discover messages and controller keeps on dropping these messages. But looking at the traffic I couldn't exactly map which MAC address belonged to which entity. Can someone help me with my understanding of the MAC addresses. Using ifconfig , ovs-ofctl show br-int and ovs-ofctl snoop br-int (output shown after MAC addresses), I know exactly about some MAC addresses and can't figure out some of them: Interfaces |HWAddress |IP-addr - eth0|08:00:27:7a:ff:65|10.0.3.15 eth1|08:00:27:16:d5:09 | 10.0.0.10 plugged into br-int gw-82bd3a73-dc|fa:16:3e:49:57:1b |10.0.0.1 plugged into br-int (this is the --listen-address of my two dnsmasqs) br-int |08:00:27:16:d5:09 | why doesn't bridge have no IP ? new-instance |02:d8:47:48:35:26 == MAC address of newly launched instance? (see output below) Unkown |fa:16:3e:5e:02:17 ==Seemingly unknown MAC address(which is related to the new instance?) Unkown |33:33:00:00:00:16 == MAC address related to multicast ? Questions: 1. What is gw-82bd3a73-dc interface ? 2. I am kind of unsure why br-int is so useful? 3. Why doesn't br-int don't have any IP address? 4. Why do we need to plugin a compute node's interface to br-int? (so that guest instances on remote host can communicate with each other?) 5. What is the relationship b/w 02:d8:47:48:35:26 and fa:16:3e:5e:02:17 MAC addresses in the following output? = Output of : ovs-ofctl snoop br-int = OFPT_ECHO_REQUEST (xid=0x0): 0 bytes of payload OFPT_ECHO_REPLY (xid=0x0): 0 bytes of payload OFPT_PORT_STATUS (xid=0x0): ADD: 7(tap76127847-b1): addr:02:d8:47:48:35:26 config: 0 state: LINK_DOWN current:10MB-FD COPPER OFPT_FLOW_MOD (xid=0x491662da): DEL priority=0 buf:0x0 actions=drop OFPT_BARRIER_REQUEST (xid=0x491662db): OFPT_BARRIER_REPLY (xid=0x491662db): OFPT_PORT_STATUS (xid=0x0): MOD: 7(tap76127847-b1): addr:02:d8:47:48:35:26 config: 0 state: 0 current:10MB-FD COPPER OFPT_ECHO_REQUEST (xid=0x0): 0 bytes of payload OFPT_ECHO_REPLY (xid=0x0): 0 bytes of payload OFPT_PACKET_IN (xid=0x0): total_len=90 in_port=7 data_len=90 buffer=0x0167 tunnel0:in_port0007:tci(0) macfa:16:3e:5e:02:17-33:33:00:00:00:16 type86dd proto58 tos0 ipv6::-ff02::16 port143-0 fa:16:3e:5e:02:17 33:33:00:00:00:16, ethertype IPv6 (0x86dd), length 90: :: ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 OFPT_PACKET_OUT (xid=0x491662dc): in_port=7 actions_len=0 actions=drop buffer= 0x0167 OFPT_PACKET_IN (xid=0x0): total_len=322 in_port=7 data_len=128 buffer= 0x0168 tunnel0:in_port0007:tci(0) macfa:16:3e:5e:02:17-ff:ff:ff:ff:ff:ff type0800 proto17 tos0 ip0.0.0.0-255.255.255.255 port68-67 fa:16:3e:5e:02:17 ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 128: truncated-ip - 194 bytes missing! 0.0.0.0.68 255.255.255.255.67: BOOTP/DHCP, Request from fa:16:3e:5e:02:17, length 280 OFPT_PACKET_OUT (xid=0x491662dd): in_port=7 actions_len=0 actions=drop buffer= 0x0168 OFPT_PACKET_IN (xid=0x0): total_len=78 in_port=7 data_len=78 buffer=0x0169 fa:16:3e:5e:02:17
[Openstack] gw-* interface
Hi guys, I had posted a question regarding bridges on OpenFlow list and got a terrific explanation from Reid, as shown below: ___ 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] devstack installation failing
Thanks guys. Here is the output of the curl command:
{error: {message: Invalid tenant, code: 401, title: Not Authorized}}
Seems like there is no such tenant in keystone database. I tried doing keystone
tenant-list but it keeps on asking for one extra argument each time (i.e after
keystone tenant-list, I tried keystone --os_username admin tenant-list and
keystone --os_username --os_password tenant-list ). Anyway, what could be th
cause of keystone's database problems?
Date: Thu, 24 May 2012 00:40:19 -0500
Subject: Re: [Openstack] devstack installation failing
From: dolph.math...@gmail.com
To: mandar.v...@nttdata.com
CC: salma...@live.com; openstack@lists.launchpad.net
The output to the curl command below should definitely point you in the right
direction -- devstack is expecting keystone to return an authentication
response there, but it's getting something else instead. Feel free to paste the
results to the list.
-Dolph
On Wed, May 23, 2012 at 11:47 PM, Vaze, Mandar mandar.v...@nttdata.com wrote:
Last time when I ran into this error, I had updated (git pull) only nova, but
forgot to update keystone.
Once I updated (git pull) all the other projects, including keystone, the error
went away.
Few things you can use for troubleshooting :
1.
Run this command from terminal – See if the outpur gives any clue : “curl
-s -d '{auth:{passwordCredentials: {username: admin, password:
nova}, tenantName: admin}}' -H 'Content-type: application/json'
http://10.0.3.15:5000/v2.0/tokens”
2.
Check the keystone database, see if user admin and tenant admin are created OK
-Mandar
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net]
On Behalf Of Salman Malik
Sent: Thursday, May 24, 2012 9:48 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] devstack installation failing
Hi All,
While installing devstack, installation is failing with the error :
++ python -c 'import sys; import json; tok = json.loads(sys.stdin.read());
print tok['\''access'\'']['\''token'\'']['\''id'\''];'
++ curl -s -d '{auth:{passwordCredentials: {username: admin,
password: nova}, tenantName: admin}}' -H 'Content-type:
application/json'
http://10.0.3.15:5000/v2.0/tokens
Traceback (most recent call last):
File string, line 1, in module
KeyError: 'access'
With some searching I know this has something to do with the keystone but I
have no clue how to resolve this one.
Thanks for your help.
Salman
__
Disclaimer:This email and any attachments are sent in strictest confidence for
the sole use of the addressee and may contain legally privileged, confidential,
and proprietary data. If you are not the intended recipient, please advise the
sender by replying promptly to this email and then delete and destroy this
email and any attachments without any further use, copying or forwarding
___
Mailing list: https://launchpad.net/~openstack
Post to : 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
Re: [Openstack] devstack installation failing
Thanks Dolph for explaining the full command. Here is my output:
keystone --os_username=admin --os_password=nova --os_tenant_name=admin
--os_auth_url=http://10.0.3.15:5000/v2.0/ tenant-list
No handlers could be found for logger keystoneclient.client
Invalid tenant (HTTP 401)
where I used:
os_username=admin (default username that I previously used to access the
dashboard)
os_password=nova(password that I set during devstack installation and can be
seen in localrc, that I previously used to access dashboard)
os_tenant_name=admin(same as project name ? This is one of the two default
projects that I used to launch instances for)
I hope my credentials are correct (as explained above) but still I see Invalid
tenant as command's output. Any ideas?
Also, it would be great if you could correct my understanding of the following
terms: os_user=cloud user that provides IaaS to the tenants (and tenant is also
know as project in os jargon?)
Thanks,
Salman
Date: Thu, 24 May 2012 10:18:29 -0500
Subject: Re: [Openstack] devstack installation failing
From: dolph.math...@gmail.com
To: salma...@live.com
CC: mandar.v...@nttdata.com; openstack@lists.launchpad.net
keystoneclient is looking for enough arguments for it to either fully
authenticate or bypass authentication.
To fully authenticate:keystone --os_username=admin --os_password=secret
--os_tenant_name=project-x --os_auth_url=http://keystone:5000/v2.0/ tenant-list
To bypass authentication (i.e. you already have a token endpoint):keystone
--token=94eabe5d --endpoint=http://keystone:35357/v2.0/ tenant-list
As shown in the error messages you're seeing, you can also set all these
variables in your environment so you don't have to specify them for each
keystoneclient command.
-Dolph
On Thu, May 24, 2012 at 9:17 AM, Salman Malik salma...@live.com wrote:
Thanks guys. Here is the output of the curl command:
{error: {message: Invalid tenant, code: 401, title: Not Authorized}}
Seems like there is no such tenant in keystone database. I tried doing keystone
tenant-list but it keeps on asking for one extra argument each time (i.e after
keystone tenant-list, I tried keystone --os_username admin tenant-list and
keystone --os_username --os_password tenant-list ). Anyway, what could be th
cause of keystone's database problems?
Date: Thu, 24 May 2012 00:40:19 -0500
Subject: Re: [Openstack] devstack installation failing
From: dolph.math...@gmail.com
To: mandar.v...@nttdata.com
CC: salma...@live.com; openstack@lists.launchpad.net
The output to the curl command below should definitely point you in the right
direction -- devstack is expecting keystone to return an authentication
response there, but it's getting something else instead. Feel free to paste the
results to the list.
-Dolph
On Wed, May 23, 2012 at 11:47 PM, Vaze, Mandar mandar.v...@nttdata.com wrote:
Last time when I ran into this error, I had updated (git pull) only nova, but
forgot to update keystone.
Once I updated (git pull) all the other projects, including keystone, the error
went away.
Few things you can use for troubleshooting :
1.
Run this command from terminal – See if the outpur gives any clue : “curl
-s -d '{auth:{passwordCredentials: {username: admin, password:
nova}, tenantName: admin}}' -H 'Content-type: application/json'
http://10.0.3.15:5000/v2.0/tokens”
2.
Check the keystone database, see if user admin and tenant admin are created OK
-Mandar
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net]
On Behalf Of Salman Malik
Sent: Thursday, May 24, 2012 9:48 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] devstack installation failing
Hi All,
While installing devstack, installation is failing with the error :
++ python -c 'import sys; import json; tok = json.loads(sys.stdin.read());
print tok['\''access'\'']['\''token'\'']['\''id'\''];'
++ curl -s -d '{auth:{passwordCredentials: {username: admin,
password: nova}, tenantName: admin}}' -H 'Content-type:
application/json'
http://10.0.3.15:5000/v2.0/tokens
Traceback (most recent call last):
File string, line 1, in module
KeyError: 'access'
With some searching I know this has something to do with the keystone but I
have no clue how to resolve this one.
Thanks for your help.
Salman
__
Disclaimer:This email and any attachments are sent in strictest confidence for
the sole use of the addressee and may contain legally privileged, confidential,
and proprietary data. If you are not the intended recipient, please advise the
sender by replying promptly to this email and then delete and destroy this
email and any attachments without any further use, copying or forwarding
___
Mailing list: https://launchpad.net/~openstack
Post
Re: [Openstack] Development/Debugging
Thank you both. I have used pdb today with quantum service, just as you explained: by placing pdb.set_trace() function where I wanted to run the code myself. All worked well except when the a wait function from the eventlet library was called. After which program waits for an input and when an event happens it just doesn't return back to pdb (and continues normally). And yes, it seems that GUI tool might be hard to use, since there is no single main function but many daemons working together so it makes sense to go through each daemon at a time using pdb. But may be I am wrong... Hope other people also share their experience. Thanks again, Salman From: mandar.v...@nttdata.com To: salma...@live.com; openstack@lists.launchpad.net Subject: RE: [Openstack] Development/Debugging Date: Tue, 12 Jun 2012 03:58:39 + Salman, I haven’t used UI tools like Pydev and/or eclipse. I have a devstack installation running on linux box where I use ssh for all my development. TL;DR Version : I use pdb (aka Python Debugger) It is very easy to use if you have used gdb - (Refer to http://docs.python.org/library/pdb.html#debugger-commands if you are unfamiliar with pdb) Longer Version: · To trace how the “allocate_for_instance” works for Quantum – put “pdb.set_trace()” in method “def allocate_for_instance” in file nova/network/quantum/manager.py You also need “import pdb” somewhere at the top in the same file. · Stop and restart nova-network process from “screen” (So that modified nova/network/quantum/manager.py is used.) · Try to create an instance (which eventually needs to allocate fixed IP for the instance) Now go to “nova-network” console – as soon as RPC call is made to the method “allocate_for_instance” , execution will stop and you are presented with (pdb) interactive prompt – From here on you can debug using pdb commands -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Salman Malik Sent: Monday, June 11, 2012 10:49 PM To: openstack@lists.launchpad.net Subject: [Openstack] Development/Debugging Hi All, I have been trying to get my head around the OpenStack functionality for a while now but unfortunately haven't been able to grasp it. I am interested on working on Quantum (and may be creating new plugins) but I am still unable to debug my own problems. So I thought it would be best for me to learn from how code works. Although I have been looking at the code for quite some time but didn't get anywhere. Now I have installed Pydev on Eclipse and am wondering how to run the massive OpenStack code in debug mode (so as to learn the call/control flow) ? So I thought I could get some help from OpenStack gurus like how do you people develop/debug problems ? What environment are you using ? Any suggestions/tips are welcome. (Please note that I have read the nova and Quantum administration guides and also looked at the nova developer's guide) Any help would be much appreciated. Thanks, Salman __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ 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] Development/Debugging
Sorry for the confusion. I got your point. Inserting pdb.set_trace() in multiple daemons does work. Thanks for correcting me. Salman From: mandar.v...@nttdata.com To: salma...@live.com; openstack@lists.launchpad.net Subject: RE: [Openstack] Development/Debugging Date: Tue, 12 Jun 2012 04:42:39 + ... so it makes sense to go through each daemon at a time using pdb. Not sure what you mean, but you can easily put set_trace() in multiple daemons at the simultaneously, in fact it is useful to trace the flow across various openstack services. -Mandar __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
