configure Nova network on a Xen server envrionment

asked 2015-07-20 14:26:27 -0600

BuildGuru gravatar image

updated 2015-07-22 10:36:33 -0600

I configured the network following :

http://docs.openstack.org/juno/install-guide/install/apt/content/nova-network-initial-network.html#treeDiv (http://docs.openstack.org/juno/instal...)

Nova-compute logs are showing that br100 is not found.

I created a bridge : sudo brctl addbr br100 eth2 xenbr2

my nova.conf has network_manager = nova.network.manager.FlatDHCPManager

flat_network_bridge = xenbr2

flat_interface = eth2

public_interface = eth2

the logs now show :

2015-07-20 15:10:21.572 1674 TRACE nova.utils [instance: 00129270-2c1a-447e-aa70-10722acaf444] Exception: Found no PIF for device br100

2015-07-20 15:10:15.899 1674 AUDIT nova.compute.claims [-] [instance: 00129270-2c1a-447e-aa70-10722acaf444] Claim successful

    2015-07-20 15:10:21.572 1674 TRACE nova.utils [instance: 00129270-2c1a-447e-aa70-10722acaf444] Exception:             Found no PIF for device br100
     2015-07-20 15:10:21.572 1674 TRACE nova.utils [instance: 00129270-2c1a-447e-aa70-10722acaf444]
        2015-07-20 15:10:21.590 1674 WARNING nova.virt.xenapi.vm_utils [-] [instance: 00129270-2c1a-447e-aa70-                10722acaf444] VM already halted, skipping shutdown...

2015-07-20 15:10:21.908 1674 INFO nova.virt.firewall [-] [instance: 00129270-2c1a-447e-aa70-10722acaf444] Attempted to unfilter instance which is not filtered 2015-07-20 15:10:21.915 1674 ERROR nova.virt.xenapi.vm_utils [-] Unable to destroy VDI OpaqueRef:4961d4a7-160d- 8517-cc5f-87c4ddae0063 2015-07-20 15:10:21.916 1674 ERROR nova.compute.manager [-] [instance: 00129270-2c1a-447e-aa70-10722acaf444] Instance failed to spawn 2015-07-20 15:10:21.916 1674 TRACE nova.compute.manager [instance: 00129270-2c1a-447e-aa70-10722acaf444] Traceback (most recent call last): 2

i tried using xenbr2 in my nova config file but with no luck

I tried using xenbr2 in the config file but it was not recognized by nova compute node,

     `                   015-07-22 11:22:03.139 21962 TRACE oslo.messaging.rpc.dispatcher ProcessExecutionError: Unexpected error while running command.
                                    2015-07-22 11:22:03.139 21962 TRACE oslo.messaging.rpc.dispatcher Command: sudo nova-rootwrap /etc/nova/rootwrap.conf                           ip link add link xenbr2 name vlan100 type vlan id 100
                               2015-07-22 11:22:03.139 21962 TRACE oslo.messaging.rpc.dispatcher Exit code: 1
                            2015-07-22 11:22:03.139 21962 TRACE oslo.messaging.rpc.dispatcher Stdout: u''
                            2015-07-22 11:22:03.139 21962 TRACE oslo.messaging.rpc.dispatcher Stderr: u'Cannot find device "xenbr2"\n'
                    2015-07-22 11:22:03.139 21962 TRACE oslo.messaging.rpc.dispatcher
                     2015-07-22 11:22:03.145 21962 ERROR oslo.messaging._drivers.common [req-11a33ea0-0046-4861-9f6c-               5681fbcb5d21 ] Returning exception Unexpected error while running command.
                     Command: sudo nova-rootwrap /etc/nova/rootwrap.conf ip link add link xenbr2 name vlan100 type vlan id 100
                     Exit code: 1
                        Stdout: u''

` 2

Here’s what my network and nova.conf look like :

@controller:~$ nova network-create OpenStack-net --bridge-interface xenbr2 --fixed-range-v4 MYNet --gateway MyNetwork --multi-host T --dns1 MyDNS --dns2 MyDNS --enable-dhcp T --dhcp-server MyDHCP

network_api_class = nova.network.api.API security_group_api = nova firewall_driver = nova.virt.firewall.NoopFirewallDriver network_manager = nova.network.manager.FlatDHCPManager network_size = 254 allow_same_net_traffic = False multi_host = True send_arp_for_ha = True share_dhcp_address = True force_dhcp_release = True flat_network_bridge = xenbr2 flat_interface = eth2 public_interface = eth2

I still see br100 in the networks table for this network (OpenStack-net) +---------------------+---------------------+------------+----+----------+-------------+---------------+--------+----------+------------+----------+------+--------------------+-----------------+---------------------+------------+----------------------------------+------+---------+------------+---------------+------------+------------------+------------+------------+--------------------------------------+----------+-----------+---------+------+-------------+-------------+---------------+ | created_at | updated_at | deleted_at | id | injected | cidr | netmask | bridge | gateway | broadcast | dns1 | vlan | vpn_public_address | vpn_public_port | vpn_private_address | dhcp_start | project_id | host | cidr_v6 | gateway_v6 | label | netmask_v6 | bridge_interface | multi_host | dns2 | uuid | priority | rxtx_base | deleted | mtu | dhcp_server | enable_dhcp | share_address | +---------------------+---------------------+------------+----+----------+-------------+---------------+--------+----------+------------+----------+------+--------------------+-----------------+---------------------+------------+----------------------------------+------+---------+------------+---------------+------------+------------------+------------+------------+--------------------------------------+----------+-----------+---------+------+-------------+-------------+---------------+ | 2015-07-22 ... (more)

edit retag flag offensive close merge delete

Comments

I was able to launch the instance by changing : flat_network_bridge = xenbr2 to flat_network_bridge = br100. Now the vm is instantiated, but gets br100 and a private IP address. I am not sure why it is not assigned an IP address

BuildGuru gravatar imageBuildGuru ( 2015-07-20 14:40:38 -0600 )edit