openstack team mailing list archive

[Vishvananda Ishaya <vishvananda@xxxxxxxxx>]

The vlans and bridges are not created until you run an instance in a project The network is only assigned to a project when it is first needed and the vlans and bridges are only created when an instance is launched on a host in that project.

Vish

On Nov 19, 2012, at 10:05 AM, Juris <juris@xxxxxx> wrote:

> Hi all,
> 
> I'm trying to configure Folsom to work with nova-networks and VlanManager and it doesn't work.
> 
> I can create networks with:
> nova-manage network create --label testnet --fixed_range_v4 10.0.2.0/24 --num_networks 1 --network_size 256 --vlan 200
> 
> list them later:
> nova-manage network list
> 1    	10.0.2.0/24       	None           	10.0.2.3       	None           	None           	200            	None           	32692942-8965-4174-a45a-18cda4c7d183
> 
> and there are no errors in /var/log/nova/*
> 
> However, I can't see any bridges and vlan interfaces if I run ip addr or brctl show.
> 
> networking section of nova.conf looks like this:
> network_manager=nova.network.manager.VlanManager
> force_dhcp_release=True
> dhcpbridge_flagfile=/etc/nova/nova.conf
> dhcpbridge=/usr/bin/nova-dhcpbridge
> firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
> public_interface=eth0
> vlan_interface=eth1
> fixed_range=10.0.0.0/24
> flat_network_dhcp_start=10.0.0.10
> network_size=256
> flat_injected=False
> multi_host=True
> send_arp_for_ha=True
> connection_type=libvirt
> 
> it's a pretty standard config and I can't see why it is not working.
> 
> Any help will be much appreciated.
> 
> Thank you in advance,
> Juris
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp