[Openstack-operators] Network Configuration - Centos 6.2

Ronald J. Yacketta yacketrj at potsdam.edu
Fri Jun 1 18:28:33 UTC 2012


On 6/1/2012 2:16 PM, Lorin Hochstein wrote:
> On Jun 1, 2012, at 2:07 PM, Ronald J. Yacketta wrote:
>
>> Hello all!
>>
>> Trying to setup a simple (lol simple..) openstack single node 
>> configuration for testing. Been up and down and all around networking 
>> and noting seems to make sense or works.
>>
>> rpm -qa | grep openstack
>> openstack-swift-object-1.4.8-2.el6.noarch
>> openstack-swift-doc-1.4.8-2.el6.noarch
>> openstack-glance-2012.1-5.el6.noarch
>> openstack-dashboard-2012.1-4.el6.noarch
>> openstack-swift-container-1.4.8-2.el6.noarch
>> openstack-swift-proxy-1.4.8-2.el6.noarch
>> openstack-keystone-2012.1-3.el6.noarch
>> openstack-nova-2012.1-4.el6.noarch
>> openstack-swift-1.4.8-2.el6.noarch
>> openstack-swift-account-1.4.8-2.el6.noarch
>> openstack-quantum-2012.1-4.el6.noarch
>> openstack-utils-2012.1-1.el6.noarch
>>
>> Current attempt is to mirror the configuration shown here 
>> http://unchainyourbrain.com/openstack/13-networking-in-nova.
>>
>> network configuration
>>
>> eth0 [public]:
>> DEVICE="eth0"
>> BOOTPROTO="static"
>> NM_CONTROLLED="no"
>> ONBOOT="yes"
>> IPADDR=137.143.102.116
>> GATEWAY=137.143.110.254
>> NETMASK=255.255.240.0
>>
>> eth1 [private]: (tried with and without assigning an IP)
>> DEVICE="eth1"
>> MTU="1500"
>> ONBOOT=yes
>> NM_CONTROLLED="no"
>> IPADDR=192.168.0.1
>> NETMASK=255.255.255.0
>>
>> nova.conf
>> network_manager = nova.network.manager.FlatDHCPManager
>> fixed_range=10.200.0.0/24
>> flat_network_dhcp_start=10.200.0.2
>> flat_network_bridge=br100
>> flat_interface=eth1
>> flat_injected=False
>> public_interface=eth0
>>
>> brctl:
>> bridge name     bridge id               STP enabled     interfaces
>> br100           8000.000000000000       no
>> virbr0          8000.525400e396a2       yes             virbr0-nic
>>
>> created nova network via:
>> nova-manage network create demonet 10.200.0.0/24 1 256 --bridge=br100
>>
>> It is my understanding that nova-network _should_ configure br100 and 
>> all the other network bits, correct? if so, then something is just 
>> not right in my config seeing that nova-network does not configure 
>> anything with br100 or eth1.
>>
>> Anyone see where I went wrong?
>>
>
> Ron:
>
> A lot of the Linux networking stuff done by nova-network doesn't 
> happen until you launch your first instance. (I'm surprised you 
> already have a br100 bridge already, did you create that manually?). 
> Have you tried to launch one yet?
>
> Take care,
>
> Lorin
> --
> Lorin Hochstein
> Lead Architect - Cloud Services
> Nimbis Services, Inc.
> www.nimbisservices.com <https://www.nimbisservices.com/>
>
>
>
>
Have tried several times over to launch an instance, in each and every 
case it is left in an ERROR state. Feel a lot of my issue is lack of 
concise documentation as well as being very very green with openstack.

looking through the nova/network.log I see the following error for an 
instance I just tried to launch

failed to bind listening socket for 10.0.0.1: Address already in use

10.0.0.1 was assigned to br100 by nova, even more confused now ;)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20120601/62c5af77/attachment-0002.html>


More information about the Openstack-operators mailing list