openstack team mailing list archive

[Anne Gentle <anne@xxxxxxxxxxxxx>]

On Mon, Jun 17, 2013 at 5:13 PM, Dmitry Makovey <dmitry@xxxxxxxxxxxxx>wrote:

>
> Hi,
>
> for a while now we've been trying to get a firm grip on networking
> options with as simple configuration as possible. We have ended
> selecting nova-network with FlatDHCP manager. It sounded simple on paper
> and conceptually it seemed to do what we need. But we can't bolt it
> together so far.
>
> In our case we have dual-nic machines pressed into service for OpenStack
> needs, and nic's assigned as such:
>
> * management network (a.k.a. private network), say 172.1.1.0/24
> * client network (a.k.a. public network) 192.168.1.0/24
>
> We also plan on running multiple nova-compute nodes, and have a back-end
> cinder and glance nodes.
>
> We do not intend exposing management network to our users so having it
> exposed to the VMs is not an option.
>
> we have added VM private netowrk via:
>
> # nova-manage network create privatenet 10.0.0.0/24 1 256 --bridge=privbr0
>
> that we hoped we can bridge into with the FlatDHCP setup. So far all of
> our attempts failed either due to misunderstanding of requirements for
> such implementation or due to misconfiguration. We can add a pool of
> "public IPs", we can assign it, but the traffic is not reaching VMs (or
> out of VMs):
>
> # nova-manage network create public --fixed_range_v4=192.168.1.0/24
> --dns1=192.168.2.1 --dns2=192.168.2.3 --bridge=br1
>
> # nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0
> # nova secgroup-add-rule default tcp 22 22 0.0.0.0/0
>
> # nova-manage floating create --ip_range=192.168.1.0/24
> # nova add-floating-ip 972b73d2-0e4b-4f61-907a-f0aeb5d5f974 192.168.1.3
> # nova list
>
> +--------------------------------------+------------+--------+------------------------------------+
> | ID                                   | Name       | Status | Networks
>                           |
>
> +--------------------------------------+------------+--------+------------------------------------+
> | 972b73d2-0e4b-4f61-907a-f0aeb5d5f974 | demorhel67 | ACTIVE |
> privatenet=10.0.0.4, 192.168.1.3    |
> ...
>
> Is there some reasonably thorough walk-through on FlatDHCP setup for a
> similar scenario?
>
>
This looks a lot like the example architecture in the Operations Guide at
http://docs.openstack.org/trunk/openstack-ops/content/example_architecture.html
.

I'd highly recommend
http://docs.openstack.org/trunk/openstack-ops/content/network_troubleshooting.html.
Let us know how it goes. A few Canadians wrote a bunch of that!

Anne



>  --
> Dmitry Makovey
> Web Systems Administrator
> Athabasca University
> (780) 675-6245
> ---
> Confidence is what you have before you understand the problem
>     Woody Allen
>
> When in trouble when in doubt run in circles scream and shout
>      http://www.wordwizard.com/phpbb3/viewtopic.php?f=16&t=19330
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>