[openstack-dev] [Neutron][DevStack] How to increase developer usage of Neutron

Mike Spreitzer mspreitz at us.ibm.com
Thu Aug 14 19:53:10 UTC 2014


"CARVER, PAUL" <pc2929 at att.com> wrote on 08/14/2014 09:35:17 AM:

> Mike Spreitzer [mailto:mspreitz at us.ibm.com] wrote:
> 
> >I'll bet I am not the only developer who is not highly competent with
> >bridges and tunnels, Open VSwitch, Neutron configuration, and how 
DevStack
> >transmutes all those.  My bet is that you would have more developers 
using
> >Neutron if there were an easy-to-find and easy-to-follow recipe to use, 
to
> >create a developer install of OpenStack with Neutron.  One that's a 
pretty
> >basic and easy case.  Let's say a developer gets a recent image of 
Ubuntu
> >14.04 from Canonical, and creates an instance in some undercloud, and 
that
> >instance has just one NIC, at 10.9.8.7/16.  If there were a recipe for
> >such a developer to follow from that point on, it would be great.
> 
> https://wiki.openstack.org/wiki/NeutronDevstack worked for me.
> 
> However, I'm pretty sure it's only a single node all in one setup. At 
least,
> I created only one VM to run it on and I don't think DevStack has 
created
> multiple nested VMs inside of the one I create to run DevStack. I 
haven't
> gotten around to figuring out how to setup a full multi-node DevStack
> setup with separate compute nodes and network nodes and GRE/VXLAN 
tunnels.
> 
> There are multi-node instructions on that wiki page but I haven't tried
> following them. If someone has a Vagrant file that creates a full multi-
> node Neutron devstack complete with GRE/VXLAN tunnels it would be great
> if they could add it to that wiki page.

A working concrete recipe for a single-node install would be great.

https://wiki.openstack.org/wiki/NeutronDevstack is far from a concrete 
recipe, leaving many blanks to be filled in by the reader.
My problem is that as a non-expert in the relevant networking arcana, 
Neutron implementation,
and DevStack configuration options, it is not entirely obvious how to fill 
in the blanks.
For starters, 
http://docs.openstack.org/admin-guide-cloud/content/network-connectivity.html
speaks of four networks and, appropriately for a general page like that, 
does not relate them to NICs.
But at the start of the day, I need to know how many NICs to put on my 
host VM (the one in which I
will run DevStack to install OpenStack), how to configure them in the host 
VM's operating system,
and how to tell DevStack whatever details it needs and cannot figure out 
on its own
(I am not even clear on what that set is).
I need to know how to derive the fixed and floating IP address ranges from 
the networking context
of my host VM.
A recipe that requires more than one NIC on my host VM can be problematic 
in some situations,
which is why I suggested starting with a recipe for a host with a single 
NIC.

I am not using Xen in my undercloud.  I suspect many developers are not 
using Xen.
I did not even know it was possible to install OpenStack inside a Xen VM;
does that still work?

I was hoping for a working concrete recipe that does not depend on the 
undercloud,
rather something that works in a vanilla context that can easily be 
established with
whatever undercloud a given developer is using.

Thanks,
Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140814/480d2038/attachment.html>


More information about the OpenStack-dev mailing list