Re: [Openstack] Cannot reboot instance: Unable to add bridge
Try using quantum cleanup utilities. Stop quantum services and run quantum-ovs-cleanup and quantum-netns-cleanup. Then restart the services and everything should be fine. Filipe Manco http://about.me/fmanco 2013/7/29 Mahardhika mahardika.gil...@andalabs.com Hi, i've got strange situation, in my case here, 3 nodes are get power cut from source when i turn it on, instance can't boot, and have this as the nova-compute.log * Cannot reboot instance: Unable to add bridge qbrbe24b178-79 port tapbe24b178-79: Invalid argument* i have restart quantum-server and it's component, also with openvswith . hoping some clue 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 ___ 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] Grizzly keystone files user and tenant issues
Are you sure you're using the right Keystone version? Have you properly installed Ubuntu Cloud Archive? Otherwise you need to provide more information. Filipe Manco http://about.me/fmanco 2013/7/5 raghavendra@accenture.com Hi, I have tried to install Grizzly using the below link: ** ** https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst ** ** However when I try to run the files ** ** *keystone_basic.sh * ** ** and ** ** *keystone_endpoints_basic.sh * ** ** ** ** It says tenant and user needs to be declared properly. Has anyone tried to install Grizzly? Please guide /assist. ** ** Regards, Raghavendra Lad. -- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. __ www.accenture.com ___ 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] Grizzy,Quantum public network ports DOWN
From what I can see in the logs you must create the file /etc/sudoers.d/quantum_sudoers with the following contents: Defaults:quantum !requiretty quantum ALL = (root) NOPASSWD: /usr/bin/quantum-rootwrap About the libvirt error edit the file /etc/libvirt/qemu.conf and add the following: cgroup_device_acl = [ /dev/null, /dev/full, /dev/zero, /dev/random, /dev/urandom, /dev/ptmx, /dev/kvm, /dev/kqemu, /dev/rtc,/dev/hpet , /dev/net/tun ] Probably this won't fix all of your issues. The logs ofI don't the l3 agent will be helpful. Filipe Manco http://about.me/fmanco 2013/6/18 Samuel Winchenbach swinc...@gmail.com I may have found the cause of my problem, but I am unsure of the solution. In my libvirt log file I found many error messages similar to this: 2013-06-18 13:12:19.812+: 8353: warning : virAuditSend:135 : Failed to send audit message virt=kvm resrc=net reason=open vm=instance-0033 uuid=bca8a09e-46aa-408b-81cd-2432068361c1 net=FA:16:3E:71:7F:68 path=/dev/net/tun rdev=0A:C8: Operation not permitted Sam On Mon, Jun 17, 2013 at 8:52 PM, Samuel Winchenbach swinc...@gmail.comwrote: Here is a bunch more information from quantum: http://pastie.org/pastes/8053820/text If anyone has any ideas I would really appreciate it. Thanks! On Mon, Jun 17, 2013 at 5:07 PM, Samuel Winchenbach swinc...@gmail.comwrote: Hi All, I have been stuck on a problem for a couple of days now. I am using Grizzly on Ubuntu 12.04 LTS. I can launch vms, create networks, subnets, routers, etc. The problem is quantum reports that all fors on the public network are DOWN for example: http://pastie.org/pastes/8053283/text Does anyone have any hints or tips on what might be causing this, or the errors listed below in the quantum logs? Thanks! quantum configuration: http://pastie.org/pastes/8053100/text nova configuration: http://pastie.org/pastes/8043800/text quantum logs: http://pastie.org/pastes/8053269/text (this is everything logged during the creation the networks, launching of vm instances, allocating the floating ip and assigning it to a VM) ___ 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] Grizzy,Quantum public network ports DOWN
What is the status of quantum agent-list? I see on your node test3 the agents are down and you don't have openvswitch agent. I would check for the logs of the l3 agent? Have you configured the external network id on the l3 agent config file? Filipe Manco http://about.me/fmanco 2013/6/18 Samuel Winchenbach swinc...@gmail.com Hi Filipe, Thanks for the response. I already had the /etc/sudoers.d/quantum_sudoers file. On a whim I added root_helper = sudo quantum-rootwrap /etc/quantum/rootwrap.conf to /etc/quantum/dhcp_agent.ini and that took care of that problem. I managed to remove the libvirt errors by disabling apparmor. All the ports on my public network are still listed as DOWN I have managed to remove all of the errors and warnings from quantum but those ports will still not come up. I really am lost. Thanks again for the post, I am not sure what to try next :/ Sam On Tue, Jun 18, 2013 at 10:13 AM, Filipe Manco filipe.ma...@gmail.comwrote: From what I can see in the logs you must create the file /etc/sudoers.d/quantum_sudoers with the following contents: Defaults:quantum !requiretty quantum ALL = (root) NOPASSWD: /usr/bin/quantum-rootwrap About the libvirt error edit the file /etc/libvirt/qemu.conf and add the following: cgroup_device_acl = [ /dev/null, /dev/full, /dev/zero, /dev/random, /dev/urandom, /dev/ptmx, /dev/kvm, /dev/kqemu, /dev/rtc,/dev/hpet , /dev/net/tun ] Probably this won't fix all of your issues. The logs ofI don't the l3 agent will be helpful. Filipe Manco http://about.me/fmanco 2013/6/18 Samuel Winchenbach swinc...@gmail.com I may have found the cause of my problem, but I am unsure of the solution. In my libvirt log file I found many error messages similar to this: 2013-06-18 13:12:19.812+: 8353: warning : virAuditSend:135 : Failed to send audit message virt=kvm resrc=net reason=open vm=instance-0033 uuid=bca8a09e-46aa-408b-81cd-2432068361c1 net=FA:16:3E:71:7F:68 path=/dev/net/tun rdev=0A:C8: Operation not permitted Sam On Mon, Jun 17, 2013 at 8:52 PM, Samuel Winchenbach swinc...@gmail.comwrote: Here is a bunch more information from quantum: http://pastie.org/pastes/8053820/text If anyone has any ideas I would really appreciate it. Thanks! On Mon, Jun 17, 2013 at 5:07 PM, Samuel Winchenbach swinc...@gmail.com wrote: Hi All, I have been stuck on a problem for a couple of days now. I am using Grizzly on Ubuntu 12.04 LTS. I can launch vms, create networks, subnets, routers, etc. The problem is quantum reports that all fors on the public network are DOWN for example: http://pastie.org/pastes/8053283/text Does anyone have any hints or tips on what might be causing this, or the errors listed below in the quantum logs? Thanks! quantum configuration: http://pastie.org/pastes/8053100/text nova configuration: http://pastie.org/pastes/8043800/text quantum logs: http://pastie.org/pastes/8053269/text (this is everything logged during the creation the networks, launching of vm instances, allocating the floating ip and assigning it to a VM) ___ 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] Problem running devstack / stack.sh
I think the problem is with mysql. Try to cleanup mysql DB (maybe reinstall mysql-server). Check the stack.sh log for mysql related errors previous to the ones you present. Filipe Manco http://about.me/fmanco 2013/6/18 zan tosh ztos...@gmail.com I am getting stuck with the following errors while installing using devstack (stable/grizzly). 2013-06-18 09:43:01 + export OS_SERVICE_TOKEN=password 2013-06-18 09:43:01 + OS_SERVICE_TOKEN=password 2013-06-18 09:43:01 + export OS_SERVICE_ENDPOINT= http://localhost:35357/v2.0 2013-06-18 09:43:01 + OS_SERVICE_ENDPOINT=http://localhost:35357/v2.0 2013-06-18 09:43:01 + create_keystone_accounts 2013-06-18 09:43:01 ++ keystone tenant-create --name admin 2013-06-18 09:43:01 ++ grep ' id ' 2013-06-18 09:43:01 ++ get_field 2 2013-06-18 09:43:01 ++ read data 2013-06-18 09:43:01 An unexpected error prevented the server from fulfilling your request. (OperationalError) (1045, Access denied for user 'root'@'localhost' (using password: YES)) None None (HTTP 500) 2013-06-18 09:43:01 + ADMIN_TENANT= 2013-06-18 09:43:01 ++ keystone user-create --name admin --pass password --email ad...@example.com 2013-06-18 09:43:01 ++ grep ' id ' 2013-06-18 09:43:01 ++ get_field 2 2013-06-18 09:43:01 ++ read data 2013-06-18 09:43:02 An unexpected error prevented the server from fulfilling your request. (OperationalError) (1045, Access denied for user 'root'@'localhost' (using password: YES)) None None (HTTP 500) 2013-06-18 09:43:02 + ADMIN_USER= 2013-06-18 09:43:02 ++ keystone role-create --name admin 2013-06-18 09:43:02 ++ grep ' id ' 2013-06-18 09:43:02 ++ get_field 2 2013-06-18 09:43:02 ++ read data 2013-06-18 09:43:02 An unexpected error prevented the server from fulfilling your request. (OperationalError) (1045, Access denied for user 'root'@'localhost' (using password: YES)) None None (HTTP 500) 2013-06-18 09:43:02 + ADMIN_ROLE= 2013-06-18 09:43:02 + keystone user-role-add --user_id --role_id --tenant_id 2013-06-18 09:43:03 usage: keystone user-role-add --user user --role role [--tenant tenant] 2013-06-18 09:43:03 keystone user-role-add: error: argument --user/--user-id/--user_id: expected one argument 2013-06-18 09:43:03 ++ keystone tenant-create --name service 2013-06-18 09:43:03 ++ grep ' id ' 2013-06-18 09:43:03 ++ get_field 2 2013-06-18 09:43:03 ++ read data 2013-06-18 09:43:03 An unexpected error prevented the server from fulfilling your request. (OperationalError) (1045, Access denied for user 'root'@'localhost' (using password: YES)) None None (HTTP 500) 2013-06-18 09:43:03 + SERVICE_TENANT= 2013-06-18 09:43:03 ++ keystone role-create --name=Member 2013-06-18 09:43:03 ++ grep ' id ' 2013-06-18 09:43:03 ++ get_field 2 2013-06-18 09:43:03 ++ read data 2013-06-18 09:43:04 An unexpected error prevented the server from fulfilling your request. (OperationalError) (1045, Access denied for user 'root'@'localhost' (using password: YES)) None None (HTTP 500) 2013-06-18 09:43:04 + MEMBER_ROLE= 2013-06-18 09:43:04 ++ keystone role-create --name=anotherrole 2013-06-18 09:43:04 ++ grep ' id ' 2013-06-18 09:43:04 ++ get_field 2 2013-06-18 09:43:04 ++ read data 2013-06-18 09:43:04 An unexpected error prevented the server from fulfilling your request. (OperationalError) (1045, Access denied for user 'root'@'localhost' (using password: YES)) None None (HTTP 500) 2013-06-18 09:43:04 + ANOTHER_ROLE= 2013-06-18 09:43:04 ++ keystone tenant-create --name=invisible_to_admin 2013-06-18 09:43:04 ++ grep ' id ' 2013-06-18 09:43:04 ++ get_field 2 2013-06-18 09:43:04 ++ read data 2013-06-18 09:43:05 An unexpected error prevented the server from fulfilling your request. (OperationalError) (1045, Access denied for user 'root'@'localhost' (using password: YES)) None None (HTTP 500) 2013-06-18 09:43:05 + INVIS_TENANT= 2013-06-18 09:43:05 ++ keystone tenant-create --name=demo 2013-06-18 09:43:05 ++ grep ' id ' 2013-06-18 09:43:05 ++ get_field 2 2013-06-18 09:43:05 ++ read data 2013-06-18 09:43:05 An unexpected error prevented the server from fulfilling your request. (OperationalError) (1045, Access denied for user 'root'@'localhost' (using password: YES)) None None (HTTP 500) 2013-06-18 09:43:05 + DEMO_TENANT= 2013-06-18 09:43:05 ++ keystone user-create --name demo --pass password --email d...@example.com 2013-06-18 09:43:05 ++ grep ' id ' 2013-06-18 09:43:05 ++ get_field 2 2013-06-18 09:43:05 ++ read data 2013-06-18 09:43:05 An unexpected error prevented the server from fulfilling your request. (OperationalError) (1045, Access denied for user 'root'@'localhost' (using password: YES)) None None (HTTP 500) 2013-06-18 09:43:06 + DEMO_USER= 2013-06-18 09:43:06 + keystone user-role-add --user_id --role_id --tenant_id 2013-06-18 09:43:06 usage: keystone user-role-add --user user --role role [--tenant tenant] 2013-06-18 09:43:06 keystone user-role-add: error: argument --user/--user-id/--user_id: expected one argument 2013-06
Re: [Openstack] Grizzy,Quantum public network ports DOWN
Honestly I'm not sure because I've always used IPs. But according to the logs it looks so. After changing configurations you should probably run quantum-netns-cleanup and quantum-ovs-cleanup before starting the services. Filipe Manco http://about.me/fmanco 2013/6/18 Samuel Winchenbach swinc...@gmail.com I think I may be onto something: http://pastie.org/pastes/8056137/text from syslog Jun 18 12:57:26 test1 ovs-vsctl: 1|vsctl|INFO|Called as /usr/bin/ovs-vsctl -- --may-exist add-port br-int qvo3eb6d144-07 -- set Interface qvo3eb6d144-07 external-ids:iface-id=3eb6d144-077e-42cf-ad2e-57c50aa00399 external-ids:iface-status=active external-ids:attached-mac=fa:16:3e:92:31:1e external-ids:vm-uuid=add44e48-6f42-4ede-a646-f29e74ccc02d Jun 18 12:57:26 test1 ovs-vswitchd: 03753|socket_util|ERR|test1-int is not a valid IP address Jun 18 12:57:26 test1 ovs-vswitchd: 03755|netdev_vport|ERR|gre-1: gre type requires valid 'remote_ip' argument Jun 18 12:57:30 test1 ovs-vsctl: 1|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=2 set Port qvo3eb6d144-07 tag=1 Jun 18 12:57:30 test1 ovs-vswitchd: 03768|netdev_vport|ERR|gre-1: gre type requires valid 'remote_ip' argument Looks like you might not be able to use entries from /etc/hosts in the config files? On Tue, Jun 18, 2013 at 10:42 AM, Samuel Winchenbach swinc...@gmail.comwrote: I have three agents running (Open vSwitch agent, DHCP agent, and L3 agent): http://pastie.org/pastes/8055658/text The agents listed on test3 are there because ubuntu starts them automatically. L3 agent will never run on test3 because it doesn't even have an external interface. Right now I am just trying to limit it to one node. Here is my l3_agent.ini: http://pastie.org/pastes/8055674/text Here are a list of bridges (eth1 is my external interface) http://pastie.org/pastes/8055678/text Thanks again for all your help! On Tue, Jun 18, 2013 at 10:32 AM, Filipe Manco filipe.ma...@gmail.comwrote: What is the status of quantum agent-list? I see on your node test3 the agents are down and you don't have openvswitch agent. I would check for the logs of the l3 agent? Have you configured the external network id on the l3 agent config file? Filipe Manco http://about.me/fmanco 2013/6/18 Samuel Winchenbach swinc...@gmail.com Hi Filipe, Thanks for the response. I already had the /etc/sudoers.d/quantum_sudoers file. On a whim I added root_helper = sudo quantum-rootwrap /etc/quantum/rootwrap.conf to /etc/quantum/dhcp_agent.ini and that took care of that problem. I managed to remove the libvirt errors by disabling apparmor. All the ports on my public network are still listed as DOWN I have managed to remove all of the errors and warnings from quantum but those ports will still not come up. I really am lost. Thanks again for the post, I am not sure what to try next :/ Sam On Tue, Jun 18, 2013 at 10:13 AM, Filipe Manco filipe.ma...@gmail.comwrote: From what I can see in the logs you must create the file /etc/sudoers.d/quantum_sudoers with the following contents: Defaults:quantum !requiretty quantum ALL = (root) NOPASSWD: /usr/bin/quantum-rootwrap About the libvirt error edit the file /etc/libvirt/qemu.conf and add the following: cgroup_device_acl = [ /dev/null, /dev/full, /dev/zero, /dev/random, /dev/urandom, /dev/ptmx, /dev/kvm, /dev/kqemu, /dev/rtc,/dev/hpet , /dev/net/tun ] Probably this won't fix all of your issues. The logs ofI don't the l3 agent will be helpful. Filipe Manco http://about.me/fmanco 2013/6/18 Samuel Winchenbach swinc...@gmail.com I may have found the cause of my problem, but I am unsure of the solution. In my libvirt log file I found many error messages similar to this: 2013-06-18 13:12:19.812+: 8353: warning : virAuditSend:135 : Failed to send audit message virt=kvm resrc=net reason=open vm=instance-0033 uuid=bca8a09e-46aa-408b-81cd-2432068361c1 net=FA:16:3E:71:7F:68 path=/dev/net/tun rdev=0A:C8: Operation not permitted Sam On Mon, Jun 17, 2013 at 8:52 PM, Samuel Winchenbach swinc...@gmail.com wrote: Here is a bunch more information from quantum: http://pastie.org/pastes/8053820/text If anyone has any ideas I would really appreciate it. Thanks! On Mon, Jun 17, 2013 at 5:07 PM, Samuel Winchenbach swinc...@gmail.com wrote: Hi All, I have been stuck on a problem for a couple of days now. I am using Grizzly on Ubuntu 12.04 LTS. I can launch vms, create networks, subnets, routers, etc. The problem is quantum reports that all fors on the public network are DOWN for example: http://pastie.org/pastes/8053283/text Does anyone have any hints or tips on what might be causing this, or the errors listed below in the quantum logs? Thanks! quantum configuration: http://pastie.org/pastes/8053100/text nova configuration: http://pastie.org/pastes/8043800/text quantum logs: http://pastie.org/pastes/8053269/text
Re: [Openstack] Grizzy,Quantum public network ports DOWN
Stop quantum agents (not quantum-api) and openvswitch service. Delete /etc/openvswitch/conf.db and delte all agents using quantum agent-delete id. Start openvswitch service and then quantum agents. If ports still down check quantum logs mainly quantum l3-agent. If you don't find anything interesting delete the networks and recreate them. If you still have references to test1-int check the quantum database ovs_tunnel_endpoints table and manually remove any reference. Filipe Manco http://about.me/fmanco 2013/6/18 Samuel Winchenbach swinc...@gmail.com Hmmm I used both of those commands, but no matter what I do I can not remove references to test1-int in /etc/openvswitch/conf.db Should I just manually replace those with the IP? Delete the file? On Tue, Jun 18, 2013 at 1:14 PM, Filipe Manco filipe.ma...@gmail.comwrote: Honestly I'm not sure because I've always used IPs. But according to the logs it looks so. After changing configurations you should probably run quantum-netns-cleanup and quantum-ovs-cleanup before starting the services. Filipe Manco http://about.me/fmanco 2013/6/18 Samuel Winchenbach swinc...@gmail.com I think I may be onto something: http://pastie.org/pastes/8056137/text from syslog Jun 18 12:57:26 test1 ovs-vsctl: 1|vsctl|INFO|Called as /usr/bin/ovs-vsctl -- --may-exist add-port br-int qvo3eb6d144-07 -- set Interface qvo3eb6d144-07 external-ids:iface-id=3eb6d144-077e-42cf-ad2e-57c50aa00399 external-ids:iface-status=active external-ids:attached-mac=fa:16:3e:92:31:1e external-ids:vm-uuid=add44e48-6f42-4ede-a646-f29e74ccc02d Jun 18 12:57:26 test1 ovs-vswitchd: 03753|socket_util|ERR|test1-int is not a valid IP address Jun 18 12:57:26 test1 ovs-vswitchd: 03755|netdev_vport|ERR|gre-1: gre type requires valid 'remote_ip' argument Jun 18 12:57:30 test1 ovs-vsctl: 1|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=2 set Port qvo3eb6d144-07 tag=1 Jun 18 12:57:30 test1 ovs-vswitchd: 03768|netdev_vport|ERR|gre-1: gre type requires valid 'remote_ip' argument Looks like you might not be able to use entries from /etc/hosts in the config files? On Tue, Jun 18, 2013 at 10:42 AM, Samuel Winchenbach swinc...@gmail.com wrote: I have three agents running (Open vSwitch agent, DHCP agent, and L3 agent): http://pastie.org/pastes/8055658/text The agents listed on test3 are there because ubuntu starts them automatically. L3 agent will never run on test3 because it doesn't even have an external interface. Right now I am just trying to limit it to one node. Here is my l3_agent.ini: http://pastie.org/pastes/8055674/text Here are a list of bridges (eth1 is my external interface) http://pastie.org/pastes/8055678/text Thanks again for all your help! On Tue, Jun 18, 2013 at 10:32 AM, Filipe Manco filipe.ma...@gmail.comwrote: What is the status of quantum agent-list? I see on your node test3 the agents are down and you don't have openvswitch agent. I would check for the logs of the l3 agent? Have you configured the external network id on the l3 agent config file? Filipe Manco http://about.me/fmanco 2013/6/18 Samuel Winchenbach swinc...@gmail.com Hi Filipe, Thanks for the response. I already had the /etc/sudoers.d/quantum_sudoers file. On a whim I added root_helper = sudo quantum-rootwrap /etc/quantum/rootwrap.conf to /etc/quantum/dhcp_agent.ini and that took care of that problem. I managed to remove the libvirt errors by disabling apparmor. All the ports on my public network are still listed as DOWN I have managed to remove all of the errors and warnings from quantum but those ports will still not come up. I really am lost. Thanks again for the post, I am not sure what to try next :/ Sam On Tue, Jun 18, 2013 at 10:13 AM, Filipe Manco filipe.ma...@gmail.com wrote: From what I can see in the logs you must create the file /etc/sudoers.d/quantum_sudoers with the following contents: Defaults:quantum !requiretty quantum ALL = (root) NOPASSWD: /usr/bin/quantum-rootwrap About the libvirt error edit the file /etc/libvirt/qemu.conf and add the following: cgroup_device_acl = [ /dev/null, /dev/full, /dev/zero, /dev/random, /dev/urandom, /dev/ptmx, /dev/kvm, /dev/kqemu, /dev/rtc,/dev/hpet , /dev/net/tun ] Probably this won't fix all of your issues. The logs ofI don't the l3 agent will be helpful. Filipe Manco http://about.me/fmanco 2013/6/18 Samuel Winchenbach swinc...@gmail.com I may have found the cause of my problem, but I am unsure of the solution. In my libvirt log file I found many error messages similar to this: 2013-06-18 13:12:19.812+: 8353: warning : virAuditSend:135 : Failed to send audit message virt=kvm resrc=net reason=open vm=instance-0033 uuid=bca8a09e-46aa-408b-81cd-2432068361c1 net=FA:16:3E:71:7F:68 path=/dev/net/tun rdev=0A:C8: Operation not permitted Sam On Mon, Jun 17, 2013 at 8:52 PM, Samuel Winchenbach swinc
Re: [Openstack] (Quantum) - how use a router physic and not virtual ?
Hello Can you give more details about your use case? I'm currently developing an extension that will provide a way to use physical routers the same way you would use the virtual ones. You can read the blueprint herehttps://blueprints.launchpad.net/quantum/+spec/provider-router. I would appreciate any comments. Regards Filipe Manco http://about.me/fmanco 2013/5/27 Alexandre De Carvalho alexandre7.decarva...@gmail.com Hi ! I would like to have the same network topology that you can see in the picture. But i want use a router physic and not virtual. And i don't know how to do it. What is the configuration for quantum ? Thanks for your help ! [image: Images intégrées 1] -- regards, Alexandre ___ 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] [Quantum] Error while creating integration bridge
Probably the openvswitch service isn't running. Run service openvswitch status to check it. If it is already running try to restart it. Filipe Manco http://about.me/fmanco 2013/5/8 Ashutosh Narayan aashutoshnara...@gmail.com Hi Folks, I was following the below link to install Quantum on Grizzly - https://fedoraproject.org/wiki/Packstack_to_Quantum While running the step to create integration bridge I get the following error : [root@ ~(keystone_admin)]# ovs-vsctl add-br br-int 2013-05-08T10:50:37Z|2|reconnect|WARN|unix:/usr/local/var/run/openvswitch/db.sock: connection attempt failed (Connection refused) ovs-vsctl: unix:/usr/local/var/run/openvswitch/db.sock: database connection failed (Connection refused) What could be the possible reason behind this ? Thank you, -- Ashutosh Narayan http://ashutoshn.wordpress.com/ ___ 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] [Quantum][Grizzly] Second NIC is not getting IP address from the network
Just to make it clear, do you see both NICs on the VM? Filipe Manco http://about.me/fmanco 2013/4/17 Anil Vishnoi vishnoia...@gmail.com Hi All, I created two network, one private network for project (say 'TestProject'), and second network at admin level, but its shared network. I spawned one VM and connected it to private network. VM successfully boots up and get the IP address from its respective private network DHCP. I spawned second VM and connected it to the shared network, and it boots up successfully and gets IP address from the shared network DHCP. I spawned third VM and connected it to both the network, and the order was 1.Private Network 2. Shared Network. VM boots up successfully but only gets the IP address from the private network DHCP and second NIC didn't receive any ip from shared network DHCP. Next i spawned fourth VM and this time i changed the ordering of NIC, 1. Shared Network 2.Private Network. VM gets the IP address from shared network DHCP but not from private network DHCP. Looks like whatever first network you add while creating VM, it will just make DHCP request for the first network only. Is this expected behavior ? My understanding is both the NIC should get IP address if DHCP is enabled for the connected networks. Few point i want to mention * I am using cirros VM image * Meta data service is running on my network node, but i am still not able to reach the mata data service. Please let me know if further details are needed for debugging this issue. Thanks in advance!!! -- Thanks Anil ___ 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] How to delete or update subnet in quantum
About the port update, according to the Quantum
APIhttp://docs.openstack.org/api/openstack-network/2.0/content/Concepts-d1e369.html#d6e256
you
cannot update the tenant-id.
I guess the problem is that no error is returned. I just tested with
Grizzly and the problem is fixed: it gives Cannot update read-only
attribute tenant_id.
Filipe Manco
http://about.me/fmanco
2013/4/17 Paul Michali p...@cisco.com
Can you do a port list to see if port in use?
PCM (Paul Michali)
Contact info for Cisco users http://twiki.cisco.com/Main/pcm
On Apr 16, 2013, at 3:49 PM, Atif Wasi wrote:
Hi Folks,
Have a relatively easy question. I assigned a subnet with a wrong IP and
an incorrect tenant-id. Now when I try to update the subnet with the
correct tenant-id, it is not taking the new value (see below).
Also how do I delete a subnet ? When I try to delete it, I am getting the
following error message. I made sure that there are no floatingip assigned
to this subnet.
Any help will be appreciated. I am running OpenStack Folsom
Thanks
Atif...
(quantum) subnet-list
+--+--+--+--+
| id | name | cidr |
allocation_pools |
+--+--+--+--+
| 47e9644b-c536-4662-8771-2f296d47ad4d | | 192.168.100.0/24 |
{start: 192.168.100.2, end: 192.168.100.254} |
| 48a105de-8bb4-4303-9958-717d110a9456 | | 192.168.1.9/24 |
{start: 192.168.1.10, end: 192.168.1.20} |
| 95cb5b22-a4f0-48eb-bc7a-8870797cb51a | | 192.168.10.0/24 |
{start: 192.168.10.2, end: 192.168.10.254} |
+--+--+--+--+
(quantum) subnet-delete 48a105de-8bb4-4303-9958-717d110a9456
Unable to complete operation on network %(net_id)s. There is one or more
ports still in use on the network.
(quantum) subnet-update 48a105de-8bb4-4303-9958-717d110a9456 --tenant-id
b443045cd0d54377b637cc0ba998bf89
Updated subnet: 48a105de-8bb4-4303-9958-717d110a9456
(quantum) subnet-show 48a105de-8bb4-4303-9958-717d110a9456
+--+--+
| Field| Value|
+--+--+
| allocation_pools | {start: 192.168.1.10, end: 192.168.1.20} |
| cidr | 192.168.1.9/24 |
| dns_nameservers | |
| enable_dhcp | False|
| gateway_ip | 192.168.1.1 |
| host_routes | |
| id | 48a105de-8bb4-4303-9958-717d110a9456 |
| ip_version | 4|
| name | |
| network_id | 036e83fc-c322-4dfc-89d2-10d867752055 |
| tenant_id| 6bd416e48a394f06bfbf4d0856740262 |
+--+--+
___
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] [DevStack] Does Devstack support grizilly already?
I've been testing grizzly with devstack and it works just fine. Filipe Manco http://about.me/fmanco 2013/4/15 HuYanrui h...@arraynetworks.com.cn ** the default clone version is trunk? trunk already have grizilly 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 ___ 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] Grizzly official packages
Is it safe to downgrade to a previous Ubuntu version? Can someone point a good tutorial on how to do it properly? Thanks Filipe Manco http://about.me/fmanco 2013/4/9 Brad Knowles bknow...@momentumsi.com On Apr 9, 2013, at 1:43 AM, skible.openst...@gmail.coma skible.openst...@gmail.com wrote: Thanks for your reply. In that case, i will upgrade my ubuntu server to 13.04 and download the grizzly packages from there. Is this the best you to get grizzly ? Quoting Mac Innes, Kiall ki...@hp.com: 12.04 will get packages for OpenStack Grizzly, Havana and I, 13.04 on the other hand will get Grizzly and that's it. If you want Havana, you'll need to upgrade to 13.10, or downgrade to 12.04 when the time comes. So, it all depends on what you want to do with those systems. Do you want to keep upgrading the OS on them to each new release, maybe because there are other things being released that you want to play with which won't be made available for 12.04? In that case, going with 13.04 should be fine. -- Brad Knowles bknow...@momentumsi.com Senior Consultant ___ 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] Grizzly official packages
Ok. Thank you. Best regards Filipe Manco http://about.me/fmanco 2013/4/9 Mark Lehrer m...@tpsit.com Is it safe to downgrade to a previous Ubuntu version? Can someone point a good tutorial on how to do it properly? Theoretically possible, but probably not worth the effort. I would suggest reinstalling with 12.04 and then move over the configs and data. Mark ___ 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] Grizzly official packages
No big deal. Asked only because some of my test/development machines are running Ubuntu 12.10. Should have installed Ubuntu LTS. The way to go is upgrade to Ubuntu 13.04, right? Regards Filipe Manco http://about.me/fmanco 2013/4/6 Daviey Walker dave.wal...@canonical.com On 6 April 2013 19:56, Filipe Manco filipe.ma...@gmail.com wrote: Is there any way to use OpenStack Grizzly in Ubuntu 12.10? Can we use the cloud archive repos? Filipe Manco http://about.me/fmanco Hi Filipe, We have made Grizzly available in both the current Ubuntu development series, which is 13.04 (Raring Ringtail), and also made it available to the most recent LTS (Long Term Support) version which is 12.04 (Precise Pangolin), via the Ubuntu Cloud Archive. At this current time, there are not packages available for 12.10. Our focus is currently on the current development version, and the most recent LTS. May I ask what makes 12.10 interesting to you, for Grizzly? Thanks. -- Kind Regards, Dave Walker dave.wal...@canonical.com Engineering Manager, Ubuntu Server ___ 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] Grizzly official packages
Is there any way to use OpenStack Grizzly in Ubuntu 12.10? Can we use the cloud archive repos? Filipe Manco http://about.me/fmanco 2013/4/5 Chuck Short chuck.sh...@canonical.com Hi They will not be backported to 12.10 only for 12.04. chuck On 13-04-05 03:32 AM, skible.openst...@gmail.coma wrote: Hi there, How can i add the official grizzly packages to ubuntu 12.10 ? This seems to work fine on ubuntu 12.04 but not sure it does on 12.10 ! deb http://ubuntu-cloud.archive.**canonical.com/ubuntuhttp://ubuntu-cloud.archive.canonical.com/ubuntuprecise-updates/grizzly main regards, Stacker __**_ Mailing list: https://launchpad.net/~**openstackhttps://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~**openstackhttps://launchpad.net/~openstack More help : https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp __**_ Mailing list: https://launchpad.net/~**openstackhttps://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~**openstackhttps://launchpad.net/~openstack More help : https://help.launchpad.net/**ListHelphttps://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] Rebooted, now can't ping my guest
I read the bug description
(https://bugs.launchpad.net/quantum/+bug/1091605) and
the fix (https://review.openstack.org/#/c/18302/). But I don't understand
who is the responsible to call the script on the startup.
Should I put it on something like rc.local? Or is quantum plugins'
responsibility to run the utility?
2013/3/1 Sylvain Bauza sylvain.ba...@digimind.com
There is a known bug for the network bridges, when rebooting :
https://bugs.launchpad.net/quantum/+bug/1091605
Try to delete/recreate your br-int/br-ex and then restart
openvswitch_plugin/l3/dhcp agents, it should fix the issue.
-Sylvain
Le 01/03/2013 15:04, The King in Yellow a écrit :
In my case, it actually appears that my vms aren't up-- the instances
panel says they are up, but looking at the console, it appears they aren't
getting an IP address. This is a new instance:
Begin: Running /scripts/init-bottom ... done.
[2.849416] EXT4-fs (vda1): re-mounted. Opts: (null)
cloud-init start-local running: Thu, 28 Feb 2013 13:29:09 +. up 10.41
seconds
no instance data found in start-local
cloud-init-nonet waiting 120 seconds for a network device.
cloud-init-nonet gave up waiting for a network device.
ci-info: lo: 1 127.0.0.1 255.0.0.0 .
ci-info: eth0 : 1 . . fa:16:3e:e0:17:f0
route_info failed
Waiting for network configuration...
It looks like it made an OVS port, though. This is on the compute node,
openvswitch-agent.log:
2013-02-28 08:34:19DEBUG [quantum.agent.linux.utils]
Command: ['sudo', '/usr/bin/quantum-rootwrap',
'/etc/quantum/rootwrap.conf', 'ovs-vsctl', '--timeout=2', 'get',
'Interface', 'qvo4f36c3ea-5c', 'external_ids']
Exit code: 0
Stdout: '{attached-mac=fa:16:3e:e0:17:f0,
iface-id=4f36c3ea-5c49-4625-a830-0c81f27ba139, iface-status=active,
vm-uuid=239d3051-255e-4213-9511-af0a82fcc744}\n'
Stderr: ''
2013-02-28 08:34:19DEBUG [quantum.agent.linux.utils] Running command:
sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf ovs-vsctl
--timeout=2 get Interface qvo62721ee8-08 external_ids
2013-02-28 08:34:19DEBUG [quantum.agent.linux.utils]
:
root@os-compute-01:/var/log/quantum# ovs-vsctl show
3a52a17f-9846-4b32-b309-b49faf91bfc4
Bridge br-int
Port qvo62721ee8-08
tag: 1
Interface qvo62721ee8-08
Port qvo1ed73bcc-9d
tag: 1
Interface qvo1ed73bcc-9d
Port qvoce0c94a9-ef
tag: 1
Interface qvoce0c94a9-ef
Port qvo135e78dd-8e
tag: 4095
Interface qvo135e78dd-8e
Port qvof37b7a55-a3
tag: 1
Interface qvof37b7a55-a3
Port br-int
Interface br-int
type: internal
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port qvoaed25b41-9c
tag: 1
Interface qvoaed25b41-9c
Port qvo4f36c3ea-5c
tag: 1
Interface qvo4f36c3ea-5c
Bridge br-tun
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port gre-1
Interface gre-1
type: gre
options: {in_key=flow, out_key=flow,
remote_ip=10.10.10.1}
Port br-tun
Interface br-tun
type: internal
ovs_version: 1.4.0+build0
root@os-compute-01:/var/log/quantum#
I supposed it should be getting address via DHCP from quantum-dhcp-agent
on the network node? It was running, nothing regarding this MAC in the
logs. I restarted quantum-dhcp-agent and rebooted, no change.
In fact, I got two CirrOS vms up, logged on the console and manually IPed
them (10.5.5.10/24 and 10.5.5.11/24), and they can't ping each other. I
would expect them to, right? They should both be connected to OVS switch
br-int, right?
Any pointers?
___
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
--
Filipe Manco
about.me/fmanco
___
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] Rebooted, now can't ping my guest
Ok
I'm using the script (I'm calling it from rc.local) and everything works
fine, even for instances that already exist.
Thanks
2013/3/5 Sylvain Bauza sylvain.ba...@digimind.com
This is up to your responsability to hit the script, afaik.
I haven't deployed the bugfix, I preferred creating my own script called
by rc.local by convenience (and also because I found the issue and
mitigated it before talking to the forum)
Once I'll migrate to 2012.2.3, I'll use this .py instead.
-Sylvain
Le 05/03/2013 13:23, Filipe Manco a écrit :
I read the bug description (
https://bugs.launchpad.net/quantum/+bug/1091605) and the fix (
https://review.openstack.org/#/c/18302/). But I don't understand who is
the responsible to call the script on the startup.
Should I put it on something like rc.local? Or is quantum plugins'
responsibility to run the utility?
2013/3/1 Sylvain Bauza sylvain.ba...@digimind.com
There is a known bug for the network bridges, when rebooting :
https://bugs.launchpad.net/quantum/+bug/1091605
Try to delete/recreate your br-int/br-ex and then restart
openvswitch_plugin/l3/dhcp agents, it should fix the issue.
-Sylvain
Le 01/03/2013 15:04, The King in Yellow a écrit :
In my case, it actually appears that my vms aren't up-- the instances
panel says they are up, but looking at the console, it appears they aren't
getting an IP address. This is a new instance:
Begin: Running /scripts/init-bottom ... done.
[2.849416] EXT4-fs (vda1): re-mounted. Opts: (null)
cloud-init start-local running: Thu, 28 Feb 2013 13:29:09 +. up 10.41
seconds
no instance data found in start-local
cloud-init-nonet waiting 120 seconds for a network device.
cloud-init-nonet gave up waiting for a network device.
ci-info: lo: 1 127.0.0.1 255.0.0.0 .
ci-info: eth0 : 1 . . fa:16:3e:e0:17:f0
route_info failed
Waiting for network configuration...
It looks like it made an OVS port, though. This is on the compute node,
openvswitch-agent.log:
2013-02-28 08:34:19DEBUG [quantum.agent.linux.utils]
Command: ['sudo', '/usr/bin/quantum-rootwrap',
'/etc/quantum/rootwrap.conf', 'ovs-vsctl', '--timeout=2', 'get',
'Interface', 'qvo4f36c3ea-5c', 'external_ids']
Exit code: 0
Stdout: '{attached-mac=fa:16:3e:e0:17:f0,
iface-id=4f36c3ea-5c49-4625-a830-0c81f27ba139, iface-status=active,
vm-uuid=239d3051-255e-4213-9511-af0a82fcc744}\n'
Stderr: ''
2013-02-28 08:34:19DEBUG [quantum.agent.linux.utils] Running command:
sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf ovs-vsctl
--timeout=2 get Interface qvo62721ee8-08 external_ids
2013-02-28 08:34:19DEBUG [quantum.agent.linux.utils]
:
root@os-compute-01:/var/log/quantum# ovs-vsctl show
3a52a17f-9846-4b32-b309-b49faf91bfc4
Bridge br-int
Port qvo62721ee8-08
tag: 1
Interface qvo62721ee8-08
Port qvo1ed73bcc-9d
tag: 1
Interface qvo1ed73bcc-9d
Port qvoce0c94a9-ef
tag: 1
Interface qvoce0c94a9-ef
Port qvo135e78dd-8e
tag: 4095
Interface qvo135e78dd-8e
Port qvof37b7a55-a3
tag: 1
Interface qvof37b7a55-a3
Port br-int
Interface br-int
type: internal
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port qvoaed25b41-9c
tag: 1
Interface qvoaed25b41-9c
Port qvo4f36c3ea-5c
tag: 1
Interface qvo4f36c3ea-5c
Bridge br-tun
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port gre-1
Interface gre-1
type: gre
options: {in_key=flow, out_key=flow,
remote_ip=10.10.10.1}
Port br-tun
Interface br-tun
type: internal
ovs_version: 1.4.0+build0
root@os-compute-01:/var/log/quantum#
I supposed it should be getting address via DHCP from quantum-dhcp-agent
on the network node? It was running, nothing regarding this MAC in the
logs. I restarted quantum-dhcp-agent and rebooted, no change.
In fact, I got two CirrOS vms up, logged on the console and manually
IPed them (10.5.5.10/24 and 10.5.5.11/24), and they can't ping each
other. I would expect them to, right? They should both be connected to
OVS switch br-int, right?
Any pointers?
___
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
