Ask Your Question
0

How do I create nova networks for Folsom on Ubuntu 12.04?

asked 2012-11-01 10:43:58 -0500

david-butler gravatar image

I have followed the instructions for the install and deploys of Openstack Folsom on Ubuntu 12.04 at: http://docs.openstack.org/trunk/openstack-compute/install/apt/content/ (http://docs.openstack.org/trunk/opens...)

All my services show as OK, but I cannot create a useable vm network.

I have tried the method in the main text with briding and the method in Appendix B (single node install, with vlan), but either get an error woth the create command or create a network that cannot be used when creating instances in the dashbaord, e.g.

For vlan network with briding, set in /etc/nova/nova.conf

Network settings

dhcpbridge_flagfile=/etc/nova/nova.conf dhcpbridge=/usr/bin/nova-dhcpbridge network_manager=nova.network.manager.VlanManager public_interface=eth0 vlan_interface=eth1 fixed_range=192.168.30.0/24 routing_source_ip=192.168.30.205 floating_range=192.168.40.224/27 network_size=32 force_dhcp_release=True iscsi_helper=ietadm iscsi_ip_address=192.168.40.205 rootwrap_config=/etc/nova/rootwrap.conf

The primary network interface

auto eth0 iface eth0 inet static address 192.168.40.205 netmask 255.255.255.0 network 192.168.40.0 broadcast 192.168.40.255 gateway 192.168.40.1 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 192.168.1.1 dns-search mnil.bc.co.uk

auto eth1 iface eth1 inet static address 192.168.30.205 netmask 255.255.255.0 network 192.168.30.0 broadcast 192.168.30.255 gateway 192.168.30.254 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 192.168.1.1 dns-search mnil.bc.co.uk

$ sudo nova-manage db sync

$ nova-manage network create private --fixed_range_v4=192.168.30.0/24 --num_networks=1 --bridge=br100 --bridge_interface=eth1 --network_size=256 Command failed, please check log for more info 2012-10-25 10:54:06 CRITICAL nova [req-d30f31cc-0c73-4ec5-85df-52963d4f6c5c None None] 'vlan_start'

$ nova-manage network create --fixed_range_v4=192.168.20.0/24 --num_networks=1 --network_size=256 --label=private1 --vlan=100 Command failed, please check log for more info 2012-10-26 11:53:11 CRITICAL nova [req-1c993005-6db7-471e-b957-2535acfb21ea None None] bridge_interface is required to create a network.

For a flat network with briding, set in /etc/nova/nova.conf

NETWORK

network_manager=nova.network.manager.FlatDHCPManager 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.40.205 public_interface=br100 vlan_interface=eth0 flat_network_bridge=br100 flat_interface=eth0 fixed_range=192.168.30.0/24 iscsi_helper=ietadm iscsi_ip_address=192.168.40.205 rootwrap_config=/etc/nova/rootwrap.conf

network interfaces in /etc/network/interfaces configured as

The primary network interface

auto eth0 iface eth0 inet static address 192.168.40.205 netmask 255.255.255.0 network 192.168.40.0 broadcast 192.168.40.255 gateway 192.168.40.1 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 192.168.1.1 dns-search mnil.bc.co.uk

Bridge network interface for VM networks

auto br100 iface br100 inet static address 192.168.30.1 netmask 255.255.255.0 bridge_stp off ... (more)

edit retag flag offensive close merge delete

11 answers

Sort by ยป oldest newest most voted
0

answered 2012-11-06 11:34:54 -0500

david-butler gravatar image

http://docs.openstack.org/trunk/openstack-compute/install/apt/content/ap_installingfolsomubuntuprecise.html (http://docs.openstack.org/trunk/opens...) is Appendix B from the instructions at http://docs.openstack.org/trunk/openstack-compute/install/apt/content/ (http://docs.openstack.org/trunk/opens...) .

These were the first set of instructions I followed.

When I try and create a network, I get the following error

$ nova-manage network create private --fixed_range_v4=192.168.30.0/24 --num_networks=1 --bridge=br100 --bridge_interface=eth0 --network_size=256 Command failed, please check log for more info 2012-11-06 11:06:18 CRITICAL nova [req-0b1d73c6-2a28-4c17-b159-cc311660cfcd None None] 'vlan_start'

Or

$ nova-manage network create private --fixed_range_v4=192.168.30.0/27 --num_networks=1 --bridge=br100 --bridge_interface=eth0 --network_size=32 Command failed, please check log for more info 2012-11-06 11:07:35 CRITICAL nova [req-f9248fd7-0932-4206-bd0a-e06f46f7fea9 None None] 'vlan_start'

I have working Diablo and Essex compute installs, which use nova.network.manager.FlatDHCPManager when using a bridge.

The nova.conf in these instructions uses network_manager=nova.network.manager.VlanManager

Also br100 was not setup in the install instructions and is not set in the nova.conf

I cannot create a network using the Folsom Ubuntu install instructions, but I don know openstack engough to understand why.

The problem seems very simialr to the bugs I listed in my original question.

I have included my nova.conf and network config for reference:

$ more /etc/network/interfaces

This file describes the network interfaces available on your system

and how to activate them. For more information, see interfaces(5).

The loopback network interface

auto lo iface lo inet loopback

The primary network interface

auto eth0 iface eth0 inet static address 192.168.40.205 netmask 255.255.255.0 network 192.168.40.0 broadcast 192.168.40.255 gateway 192.168.40.1 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 192.168.1.1 dns-search mnil.bbc.co.uk

auto eth1 iface eth1 inet static address 192.168.30.205 netmask 255.255.255.0 network 192.168.30.0 broadcast 192.168.30.255 gateway 192.168.30.254 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 192.168.1.1 dns-search mnil.bbc.co.uk

$ sudo more /etc/nova/nova.conf [DEFAULT] logdir=/var/log/nova state_path=/var/lib/nova lock_path=/run/lock/nova verbose=True api_paste_config=/etc/nova/api-paste.ini scheduler_driver=nova.scheduler.simple.SimpleScheduler s3_host=192.168.40.205 ec2_host=192.168.40.205 ec2_dmz_host=192.168.40.205 rabbit_host=192.168.40.205 cc_host=192.168.40.205 nova_url=http://192.168.40.205:8774/v1.1/ sql_connection=mysql://nova:openstack@192.168.40.205/nova ec2_url=http://192.168.40.205:8773/services/Cloud

Auth

use_deprecated_auth=false auth_strategy=keystone keystone_ec2_url=http://192.168.40.205:5000/v2.0/ec2tokens

Imaging service

glance_api_servers=192.168.40.205:9292 image_service=nova.image.glance.GlanceImageService

Virt driver

connection_type=libvirt #libvirt_type=qemu libvirt_type=kvm libvirt_use_virtio_for_bridges=true start_guests_on_host_boot=false resume_guests_state_on_host_boot=false

Vnc configuration

novnc_enabled=true novncproxy_base_url=http://192.168.40 ... (more)

edit flag offensive delete link more
0

answered 2012-11-23 10:13:38 -0500

david-butler gravatar image

I still think there is a bug or a problem with the instructions.

I have not solved this problem.

edit flag offensive delete link more
0

answered 2012-11-23 10:21:41 -0500

koolhead17 gravatar image

http://docs.openstack.org/trunk/opens...

Does this not solve your issue David.

edit flag offensive delete link more
0

answered 2012-11-06 07:59:32 -0500

koolhead17 gravatar image

http://docs.openstack.org/trunk/opens...

The guide uses nova-network for folsom on 12.04.

edit flag offensive delete link more
0

answered 2012-11-07 09:31:59 -0500

hi, i do have a same problem pls inform me if u find the solution for this pls i need it..

edit flag offensive delete link more
0

answered 2012-11-22 19:09:58 -0500

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

edit flag offensive delete link more
0

answered 2012-11-23 16:08:04 -0500

david-butler gravatar image

Koolhead17,

I followed tha Appendix B, almost all of it worked without problems, except when I try and create a network using

$ nova-manage network create private --fixed_range_v4=192.168.30.0/24 --num_networks=1 --bridge=br100 --bridge_interface=eth1 --network_size=256 Command failed, please check log for more info 2012-10-25 10:54:06 CRITICAL nova [req-d30f31cc-0c73-4ec5-85df-52963d4f6c5c None None] 'vlan_start'

This means I cannot create a network and run a VM.

Dave.

edit flag offensive delete link more
0

answered 2012-11-29 06:42:56 -0500

Hi,

i'm also using the same manual but i user FlatDhcp Manager instaed of vlan manager it works for me may be u can try with that..

regards, Vignesh

edit flag offensive delete link more
0

answered 2012-11-30 09:53:30 -0500

david-butler gravatar image

Vignesh,

Thanks for the advice. Writing a paper at moment, but will try.

Did you need to manually configure a bridge interface (br100) in /etc/network/interfaces ?

Did you need to change any other nova.conf network settings from Appendix B beside the network_manage? e.g. public_interface, vlan_interface, flat_network_bridge, flat_interface

Which of the nova-manage network create private commands did you use?

Thanks in advance.

Dave.

edit flag offensive delete link more
0

answered 2012-11-30 11:06:40 -0500

Hi Dave,

http://www.hastexo.com/resources/docs/installing-openstack-essex-4-ubuntu-1204-precise-pangolin/step-5-install-and-configur (http://www.hastexo.com/resources/docs...)

This is the link which has configuaration regarding dhcpmanager. Try it if u have any problem please let me know....

regards, Vignesh

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2012-11-01 10:43:58 -0500

Seen: 257 times

Last updated: Dec 04 '12