Thanks.
To: arin...@live.com CC: openstack@lists.launchpad.net Subject: RE: [Openstack] nova-network no ip for vm From: jsbry...@us.ibm.com Date: Thu, 25 Apr 2013 11:59:10 -0500 Arindam, You need to make sure that nova-network is not started and that quantum is started on your control node. Also ensure that your /etc/nova/nova.conf is configured to use quantum and a plugin. For my setup I have: network_api_class = nova.network.quantumv2.api.API quantum_admin_username = <username> quantum_admin_password = <password> quantum_admin_auth_url = http://localhost:5000/v2.0/ quantum_auth_strategy = keystone quantum_admin_tenant_name = service quantum_url = http://localhost:9696/ libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtOpenVswitchVirtualPortDriver linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver linuxnet_ovs_integration_bridge = br-int quantum_ovs_bridge = br-int In the default section of my nova.conf. Obviously those will vary depending on your hypervisor and which plugin you are using. Jay S. Bryant Linux Developer - OpenStack Enterprise Edition Department 7YLA, Building 015-2, Office E125, Rochester, MN Telephone: (507) 253-4270, FAX (507) 253-6410 TIE Line: 553-4270 E-Mail: jsbry...@us.ibm.com -------------------------------------------------------------------- All the world's a stage and most of us are desperately unrehearsed. -- Sean O'Casey -------------------------------------------------------------------- From: Arindam Choudhury <arin...@live.com> To: Jay S Bryant/Rochester/IBM@IBMUS, openstack <openstack@lists.launchpad.net>, Date: 04/25/2013 11:42 AM Subject: RE: [Openstack] nova-network no ip for vm Hi, Actually the problem was solved by installing nbd module. Now I have one weird problem. I have mistakenly installed nova-network in compute node and it had became the default one. Can you tell be how to fix it? To: arin...@live.com Subject: Re: [Openstack] nova-network no ip for vm From: jsbry...@us.ibm.com Date: Thu, 25 Apr 2013 11:32:18 -0500 Arindam, I realized last night that the iptables command I sent didn't have the right network interface specification for your environment. It should have been: iptables -I INPUT -i <interface on control node to the compute nodes> -p udp --dport 67:68 --sport 67:68 -j ACCEPT . It looks like that might be vnet0? Sorry, I don't use iptables much and just stumbled upon the fix for our environment out of luck. :-) Jay S. Bryant Linux Developer - OpenStack Enterprise Edition Department 7YLA, Building 015-2, Office E125, Rochester, MN Telephone: (507) 253-4270, FAX (507) 253-6410 TIE Line: 553-4270 E-Mail: jsbry...@us.ibm.com -------------------------------------------------------------------- All the world's a stage and most of us are desperately unrehearsed. -- Sean O'Casey -------------------------------------------------------------------- From: Arindam Choudhury <arin...@live.com> To: Staicu Gabriel <gabriel_sta...@yahoo.com>, openstack <openstack@lists.launchpad.net>, Date: 04/25/2013 04:19 AM Subject: Re: [Openstack] nova-network no ip for vm Sent by: "Openstack" <openstack-bounces+jsbryant=us.ibm....@lists.launchpad.net> Hi, Thanks for your reply. Here is the logs from /var/log/messages: Apr 25 11:14:40 aopcso1 kernel: [589256.953753] device vnet0 entered promiscuous mode Apr 25 11:14:40 aopcso1 kernel: [589257.014414] br100: port 2(vnet0) entering forwarding state Apr 25 11:14:40 aopcso1 kernel: [589257.014430] br100: port 2(vnet0) entering forwarding state Apr 25 11:14:55 aopcso1 kernel: [589272.014705] br100: port 2(vnet0) entering forwarding state and the logs from /var/log/syslog: Apr 25 11:14:07 aopcso1 dnsmasq[12485]: direcciónes /etc/hosts - 23 leídas Apr 25 11:14:07 aopcso1 dnsmasq-dhcp[12485]: read /var/lib/nova/networks/nova-br100.conf Apr 25 11:14:39 aopcso1 NetworkManager[3980]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/vnet0, iface: vnet0) Apr 25 11:14:39 aopcso1 NetworkManager[3980]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/vnet0, iface: vnet0): no ifupdown configuration found. Apr 25 11:14:39 aopcso1 NetworkManager[3980]: <warn> /sys/devices/virtual/net/vnet0: couldn't determine device driver; ignoring... Apr 25 11:14:40 aopcso1 kernel: [589256.953753] device vnet0 entered promiscuous mode Apr 25 11:14:40 aopcso1 kernel: [589257.014414] br100: port 2(vnet0) entering forwarding state Apr 25 11:14:40 aopcso1 kernel: [589257.014430] br100: port 2(vnet0) entering forwarding state Apr 25 11:14:44 aopcso1 ntpd[4796]: Listen normally on 67 vnet0 fe80::fc16:3eff:fe8a:f597 UDP 123 Apr 25 11:14:44 aopcso1 ntpd[4796]: peers refreshed Apr 25 11:14:50 aopcso1 kernel: [589267.164541] vnet0: no IPv6 routers present Apr 25 11:14:55 aopcso1 kernel: [589272.014705] br100: port 2(vnet0) entering forwarding state Date: Thu, 25 Apr 2013 01:53:02 -0700 From: gabriel_sta...@yahoo.com Subject: Re: [Openstack] nova-network no ip for vm To: arin...@live.com; openstack@lists.launchpad.net Hi, A place to look for eventually error messages is also /var/log/messages. Look for dnsmasq related message and post them here. Regards, Gabriel From: Arindam Choudhury <arin...@live.com> To: openstack <openstack@lists.launchpad.net> Sent: Thursday, April 25, 2013 11:10 AM Subject: [Openstack] nova-network no ip for vm Hi, I am really stuck, any help will be highly appreciated. I installed a two node openstack deployment on debian wheezy: # nova-manage service list Binary Host Zone Status State Updated_At nova-network aopcach internal enabled :-) 2013-04-25 08:05:18 nova-cert aopcach internal enabled :-) 2013-04-25 08:05:18 nova-conductor aopcach internal enabled :-) 2013-04-25 08:05:18 nova-consoleauth aopcach internal enabled :-) 2013-04-25 08:05:18 nova-scheduler aopcach internal enabled :-) 2013-04-25 08:05:18 nova-network aopcso1 internal enabled :-) 2013-04-25 08:05:15 nova-compute aopcso1 nova enabled :-) 2013-04-25 08:05:15 # nova-manage network list id IPv4 IPv6 start address DNS1 DNS2 VlanID project uuid 1 192.168.100.0/24 None 192.168.100.2 8.8.4.4 None None None 5f6a8ef4-7003-48f8-8922-5303f37d0ce8 But when boot up a vm(the cirros from the tutorial), it dont get any ip. Starting network... udhcpc (v1.18.5) started Sending discover... Sending discover... Sending discover... No lease, failing WARN: /etc/rc3.d/S40network failed ### ifconfig a eth0 Link encap:Ethernet HWaddr FA:16:3E:CD:3B:97 inet6 addr: fe80::f816:3eff:fecd:3b97/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1361 errors:0 dropped:6 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:159974 (156.2 KiB) TX bytes:902 (902.0 B) lo Link 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:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) In controller or compute node the nova-network.log does not generate any logging of events. on the horizon I dont have any network listing. _______________________________________________ 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
<<inline: ATT00001>>
<<inline: ATT00002>>
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
