[Openstack] Help with Nova Networking
Calvin Austin
caustin at bitglass.com
Thu Aug 1 01:29:29 UTC 2013
As you have 2 nics and you want to get this running I would try keeping the
bridge br100 for the em2 'private' network. Nova dhcp is already
configuring the .1 for you correctly so your /etc/network/interfaces should
simply have something this below for the bridge, currently your bridge is
also used for your nova address as well. bring your br100 down and up
against once you fix
Then use your em1 as your hosts 'known ip' that the services that want to
talk to it (your 130 address).
auto br100
iface br100 inet static
bridge_stp off
bridge_fd 0
bridge_ports em2
bridge_maxwait 0
iface em2 inet manual
up ifconfig $IFACE 0.0.0.0 up
up ifconfig $IFACE promisc
regards
calvin
On Tue, Jul 30, 2013 at 4:29 PM, Clint Dilks <clintd at waikato.ac.nz> wrote:
> Hi,
>
> I have got to the point where I am trying to launch a virtual machine as
> per
> http://docs.openstack.org/folsom/openstack-compute/install/yum/content/running-an-instance.html
>
> The boot command completes but it seems some key element of networking is
> failing.
> Does anyone have suggestions on how to trouble shoot this issue further?
>
> $ nova boot --flavor 2 --image 9ed7b2c4-f296-4fd0-9ffa-026231947a09
> --key_name mykey --security_group default cirros
>
> +-------------------------------------+--------------------------------------+
> | Property |
> Value |
>
> +-------------------------------------+--------------------------------------+
> | OS-DCF:diskConfig |
> MANUAL |
> | OS-EXT-SRV-ATTR:host |
> None |
> | OS-EXT-SRV-ATTR:hypervisor_hostname |
> None |
> | OS-EXT-SRV-ATTR:instance_name |
> instance-00000006 |
> | OS-EXT-STS:power_state |
> 0 |
> | OS-EXT-STS:task_state |
> scheduling |
> | OS-EXT-STS:vm_state |
> building |
> | accessIPv4
> | |
> | accessIPv6
> | |
> | adminPass |
> ASyz54u26TGK |
> | config_drive
> | |
> | created |
> 2013-07-30T22:14:32Z |
> | flavor |
> m1.small |
> | hostId
> | |
> | id |
> fc0c5515-9d30-4263-87ea-0f912c0fc7c7 |
> | image |
> cirros-0.3.0-x86_64 |
> | key_name |
> mykey |
> | metadata |
> {} |
> | name |
> cirros |
> | progress |
> 0 |
> | security_groups | [{u'name':
> u'default'}] |
> | status |
> BUILD |
> | tenant_id |
> f037ea1bab6d4dc08b880c5fdea29fb5 |
> | updated |
> 2013-07-30T22:14:32Z |
> | user_id |
> a66355f1760448989e63dc54e853674f |
>
> +-------------------------------------+--------------------------------------+
>
> But I notice that no IPV4 address has been assigned
>
> If do nova lists during the boot process I see the following
>
> $ nova list
> +--------------------------------------+--------+--------+----------+
> | ID | Name | Status | Networks |
> +--------------------------------------+--------+--------+----------+
> | fc0c5515-9d30-4263-87ea-0f912c0fc7c7 | cirros | BUILD | |
> +--------------------------------------+--------+--------+----------+
> $ nova list
>
> +--------------------------------------+--------+--------+-----------------------+
> | ID | Name | Status |
> Networks |
>
> +--------------------------------------+--------+--------+-----------------------+
> | fc0c5515-9d30-4263-87ea-0f912c0fc7c7 | cirros | BUILD |
> private=192.168.100.2 |
>
> +--------------------------------------+--------+--------+-----------------------+
> $ nova list
>
> +--------------------------------------+--------+--------+-----------------------+
> | ID | Name | Status |
> Networks |
>
> +--------------------------------------+--------+--------+-----------------------+
> | fc0c5515-9d30-4263-87ea-0f912c0fc7c7 | cirros | ERROR |
> private=192.168.100.2 |
>
> +--------------------------------------+--------+--------+-----------------------+
>
> And if I wait some time and then repeat the nova list it will change to
> $ nova list
> +--------------------------------------+--------+--------+----------+
> | ID | Name | Status | Networks |
> +--------------------------------------+--------+--------+----------+
> | fc0c5515-9d30-4263-87ea-0f912c0fc7c7 | cirros | ERROR | |
> +--------------------------------------+--------+--------+----------+
>
> The process does not seem to be getting as far as attempting to boot the
> image
>
> $ nova console-log fc0c5515-9d30-4263-87ea-0f912c0fc7c7
> ERROR: The resource could not be found. (HTTP 404) (Request-ID:
> req-b10876a4-9193-4158-829e-3454e80c706f)
>
> There doesn't seem to be any obvious errors in /var/log/nova/network.log.
> http://www.cms.waikato.ac.nz/~clintd/nova-network.log
>
> And all nova related services appear to be running
> ]# nova-manage service list
> Binary Host Zone
> Status State Updated_At
> nova-volume prancer nova
> enabled :-) 2013-07-30 23:14:22
> nova-scheduler prancer nova
> enabled :-) 2013-07-30 23:14:28
> nova-cert prancer nova
> enabled :-) 2013-07-30 23:14:25
> nova-compute prancer nova
> enabled :-) 2013-07-30 23:14:21
> nova-network prancer nova
> enabled :-) 2013-07-30 23:14:27
> nova-console prancer nova
> enabled :-) 2013-07-30 23:14:26
> nova-consoleauth prancer nova
> enabled :-) 2013-07-30 23:14:23
>
> # ip a
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> inet 169.254.169.254/32 scope link lo
> 2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen
> 1000
> link/ether 00:24:e8:fe:0e:8a brd ff:ff:ff:ff:ff:ff
> inet 130.217.218.18/16 brd 130.217.255.255 scope global em1
> 3: em2: <NO-CARRIER,BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc mq
> state DOWN qlen 1000
> link/ether 00:24:e8:fe:0e:8b brd ff:ff:ff:ff:ff:ff
> 5: br100: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
> UNKNOWN
> link/ether 00:24:e8:fe:0e:8b brd ff:ff:ff:ff:ff:ff
> inet 192.168.100.1/24 brd 192.168.100.255 scope global br100
> inet 192.168.206.130/24 brd 192.168.206.255 scope global br100
> 8: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
> UNKNOWN
> link/ether 52:54:00:83:81:d1 brd ff:ff:ff:ff:ff:ff
> inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
> 9: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen
> 500
> link/ether 52:54:00:83:81:d1 brd ff:ff:ff:ff:ff:ff
>
> I am also seeing the following in /var/log messages. Could it be related
> to the problem?
>
> Jul 31 10:46:55 prancer dnsmasq[17941]: read /etc/hosts - 2 addresses
> Jul 31 10:46:55 prancer dnsmasq[17941]: read
> /var/lib/nova/networks/nova-br100.conf
> Jul 31 10:48:22 prancer dnsmasq[17941]: read /etc/hosts - 2 addresses
> Jul 31 10:48:22 prancer dnsmasq[17941]: read
> /var/lib/nova/networks/nova-br100.conf
> Jul 31 10:50:29 prancer dnsmasq[17941]: read /etc/hosts - 2 addresses
> Jul 31 10:50:29 prancer dnsmasq[17941]: read
> /var/lib/nova/networks/nova-br100.conf
> Jul 31 10:50:31 prancer dnsmasq[17941]: read /etc/hosts - 2 addresses
> Jul 31 10:50:31 prancer dnsmasq[17941]: read
> /var/lib/nova/networks/nova-br100.conf
> Jul 31 10:50:32 prancer dnsmasq-dhcp[17941]: DHCPRELEASE(br100)
> 192.168.100.2 fa:16:3e:7f:0f:96 unknown lease
>
> # cat /etc/nova/nova.conf
> [DEFAULT]
>
> # LOGS/STATE
> verbose=True
> logdir=/var/log/nova
> state_path=/var/lib/nova
> lock_path=/var/lock/nova
> rootwrap_config=/etc/nova/
> rootwrap.conf
>
> # SCHEDULER
> compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler
>
> # VOLUMES
> volume_driver=nova.volume.driver.ISCSIDriver
> volume_group=nova-volumes
> volume_name_template=volume-%08x
> iscsi_helper=tgtadm
>
> # DATABASE
> sql_connection=mysql://nova:0pen5tack-nova@192.168.206.130/nova
>
> # COMPUTE
> libvirt_type=kvm
> compute_driver=libvirt.LibvirtDriver
> instance_name_template=instance-%08x
> api_paste_config=/etc/nova/api-paste.ini
>
> # COMPUTE/APIS: if you have separate configs for separate services
> # this flag is required for both nova-api and nova-compute
> allow_resize_to_same_host=True
>
> # APIS
>
> osapi_compute_extension=nova.api.openstack.compute.contrib.standard_extensions
> ec2_dmz_host=192.168.206.130
> s3_host=192.168.206.130
>
> # Qpid
> rpc_backend=nova.rpc.impl_qpid
> qpid_hostname=192.168.206.130
>
> # GLANCE
> image_service=nova.image.glance.GlanceImageService
> glance_api_servers=192.168.206.130:9292
>
> # NETWORK
> network_manager=nova.network.manager.FlatDHCPManager
> dhcpbridge=/usr/bin/nova-dhcpbridge
> force_dhcp_release=True
> dhcpbridge_flagfile=/etc/nova/nova.conf
> firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
> # Change my_ip to match each host
> my_ip=192.168.206.130
> public_interface=em2
> vlan_interface=em2
> flat_network_bridge=br100
> flat_interface=em2
> fixed_range=192.168.100.0/24
>
> # NOVNC CONSOLE
> novncproxy_base_url=http://192.168.206.130:6080/vnc_auto.html
> # Change vncserver_proxyclient_address and vncserver_listen to match each
> compute host
> vncserver_proxyclient_address=192.168.206.130
> vncserver_listen=192.168.206.130
>
> # AUTHENTICATION
> auth_strategy=keystone
> [keystone_authtoken]
> auth_host = 127.0.0.1
> auth_port = 35357
> auth_protocol = http
> admin_tenant_name = service
> admin_user = nova
> admin_password = nova
> signing_dirname = /tmp/keystone-signing-nova
>
>
> Thanks for any advice you are willing to share :)
>
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack at lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130731/852210fd/attachment.html>
More information about the Openstack
mailing list