flat networking on testing installation

Asked by ms on 2011-08-18

Hi,

I'm new to nova and I'm trying to install it on two nodes. One serves as a compute node, only nova-compute is installed there. And the other serves as a controller like in this guide: http://cssoss.wordpress.com/2011/04/27/openstack-beginners-guide-for-ubuntu-11-04-installation-and-configuration/ . The main difference and my problem is the networking. For my testing purposes I only have one static IP available for vm and I can't figure it out how to set the nova.conf files on both machines. Can anyone please somehow guide me through these settings?

Thanks in advance.
ms

Question information

Language:
English Edit question
Status:
Answered
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Last query:
2011-08-19
Last reply:
2011-08-19
Brian Lamar (blamar) said : #1

Can you provide your current nova.conf configurations? IP addresses assigned to VMs don't typically come from the configuration file, rather they come from networks/fixed_ips set up in the database using the "nova-manage network create" command. What does running "nova-manage network list" and "nova-manage fixed list" show you? Can you give more detailed information on any errors that you're encountering?

ms (micromanc3r) said : #2

controller:

--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--verbose

--network_manager = nova.network.manager.FlatManager
--num_networks=1

--s3_host=136.242.19.184
--rabbit_host=136.242.19.184
--cc_host=136.242.19.184
--ec2_url=http://136.242.19.184:8773/services/Cloud
--fixed_range=136.242.19.186/32
--network_size=1
--FAKE_subdomain=ec2
--routing_source_ip=136.242.19.184
--sql_connection=mysql://root:secret@136.242.19.184/nova
--glance_host=136.242.19.184
--image_service=nova.image.glance.GlanceImageService
--iscsi_ip_prefix=136.242.
--------------------------------------------------------------------------------
compute node:

--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--verbose
--libvirt_type=xen

--network_manager = nova.network.manager.FlatManager
--num_networks=1

--s3_host=136.242.19.184
--rabbit_host=136.242.19.184
--cc_host=136.242.19.184
--ec2_url=http://136.242.19.184:8773/services/Cloud
--fixed_range=136.242.19.186/32
--network_size=1
--FAKE_subdomain=ec2
--routing_source_ip=136.242.19.180
--sql_connection=mysql://root:secret@136.242.19.184/nova
--glance_host=136.242.19.184
--image_service=nova.image.glance.GlanceImageService
--------------------------------------------------------------------------------------
network list and fixed list show nothing because they are not set yet... I'm not sure how to set "network create" when I only want to add one IP to the database...is that even possible?

Brian Lamar (blamar) said : #3

If you're using close to the latest source code then "nova-manage network create --help" will show you the options for creating a network.

You should be able to add a single IP via something like this:

$ nova-manage network create --label=my_network --num_networks=1 --network_size=1 --fixed_range_v4=XXX.XXX.XXX.XXX/32

Brian Lamar (blamar) said : #4

Hmm, this actually doesn't seem to be working for me because the nova-manage network code is expecting more than one IP in the network. If you're seeing what I'm seeing and this use case is important to you, I'd file a bug @ bugs.launchpad.net/nova and we can get this fixed in the future.

Vish Ishaya (vishvananda) said : #5

Yes it reserves the broadcast ip and the gateway ip, so it will be very confused if you give it a /32

Can you help with this problem?

Provide an answer of your own, or ask ms for more information if necessary.

To post a message you must log in.