Re: [openstack-dev] [qa] [neutron] local.conf for devstack using neutron on home network

2014-11-11 Thread Chris Dent

On Sun, 9 Nov 2014, Kashyap Chamarthy wrote:


On Sun, Nov 09, 2014 at 02:48:49PM +, Chris Dent wrote:

On Sat, 8 Nov 2014, Kashyap Chamarthy wrote:


[I realize you intend to use physical machine for DevStack, still I
thought I'd post this here.]


Thanks for posting it. Each added datapoint will get us closer.


FWIW, this[1] is the minimal localrc contents (be sure to edit


That's minimal? :)


Hmm, apart from Cinder service in the said config, rest of them all
noted there are essential to get a minimal, functional DevStack --
at-least in my testing. Cinder isn't normally part of my test
environment (maybe I should add it), but I was investigating a bug in
that case, so if you don't prefer it, you can elide these:
c-api,c-bak,c-sch,c-vol.


I'm using minimal in the sense that the local.conf has few lines,
but results in a useful system for general dev exploration, or
provides a reasonable base to build from.

Thus the starting point ought to be:

* small statements about desired network topology
* list of enabled service (via enable_service, not ENABLED_SERVICES)
* service password settings


From just that reasonable defaults should be used.


With nova you can do that. Not so with neutron, yet.

I recognize that the above is not going to fit all use cases, but
the users I'm trying to satisfy here are early explorers who haven't
got far enough along where they need to tweak all the knobs, they
just want to get started.

I don't use a bare minimum install anyone either, but knowing what
one is provides a good foundation to build upon.

--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [qa] [neutron] local.conf for devstack using neutron on home network

2014-11-09 Thread Chris Dent

On Sat, 8 Nov 2014, Kashyap Chamarthy wrote:


[I realize you intend to use physical machine for DevStack, still I
thought I'd post this here.]


Thanks for posting it. Each added datapoint will get us closer.


FWIW, this[1] is the minimal localrc contents (be sure to edit


That's minimal? :)


Once the stack.sh is complete, I do some tasks Neutron expects:

 - Create a new private network
 - Create a new private subnet (on the above private network)
 - Create a router
 - Associate the router to an existing external network by setting it
   as its gateway
 - Associate the private network interface to the router
 - Add Neutron security group rules for ICMP and SSH


For devstack to live up to the dev in its name the above steps are
something I would expect devstack to do for me, assuming I set the
right varables and enabled the right services in local.conf.

--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [qa] [neutron] local.conf for devstack using neutron on home network

2014-11-09 Thread Kashyap Chamarthy
On Sun, Nov 09, 2014 at 02:48:49PM +, Chris Dent wrote:
 On Sat, 8 Nov 2014, Kashyap Chamarthy wrote:
 
 [I realize you intend to use physical machine for DevStack, still I
 thought I'd post this here.]
 
 Thanks for posting it. Each added datapoint will get us closer.
 
 FWIW, this[1] is the minimal localrc contents (be sure to edit
 
 That's minimal? :)

Hmm, apart from Cinder service in the said config, rest of them all
noted there are essential to get a minimal, functional DevStack --
at-least in my testing. Cinder isn't normally part of my test
environment (maybe I should add it), but I was investigating a bug in
that case, so if you don't prefer it, you can elide these:
c-api,c-bak,c-sch,c-vol.

That said, I should have defined what I consider minimal, broadly: Nova
(libvirt/KVM driver with nested virt), Neutron (OVS+GRE or VXLAN),
Keystone (with PKI), Glance.

 Once the stack.sh is complete, I do some tasks Neutron expects:
 
  - Create a new private network
  - Create a new private subnet (on the above private network)
  - Create a router
  - Associate the router to an existing external network by setting it
as its gateway
  - Associate the private network interface to the router
  - Add Neutron security group rules for ICMP and SSH
 
 For devstack to live up to the dev in its name the above steps are
 something I would expect devstack to do for me, assuming I set the
 right varables and enabled the right services in local.conf.
 

-- 
/kashyap

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [qa] [neutron] local.conf for devstack using neutron on home network

2014-11-08 Thread Kashyap Chamarthy
On Thu, Nov 06, 2014 at 07:24:02PM +, Chris Dent wrote:
 
 I seem to be struggling to cook a neutron configuration for my little
 home network that doesn't end in a variety of failures (devstack errors
 out, floating ips are on an unexpected (and unrouted) network, etc).
 I recognize that neutron is going to be complex out of necessity, so
 I'm not complaining, I just don't know what to do.
 
 I've fought with this in a variety of ways, getting the sense that I'm
 just doing it completely wrong, so I thought perhaps I should just ask
 if someone can produce a config for my network (described below).
 
 If you do help I'll be eternally grateful and owe you virtual beer and
 you'll get the satisfaction of knowing you've helped to educate someone
 out of the pit of ignorance.
 
 I have a wifi network 192.168.1.0/24
 
 I have a mac mini on that network.
 
 I use internet sharing to have an ethernet network (192.168.2.0/24)
 behind the mac. Out the etherport is a switch with two additional hosts
 (2.2 and 2.3), on each of which I'd like to run devstack on bare-metal
 with floating ips on the 192.168.2 network.
 
 Internet sharing is satisfactory for me. I don't need to reach the
 devstack hosts or their guests from beyond the mac, but I would like to
 reach them from the mac.
 
 Each devstack host has one physical interface, eth0, with a static
 IP. I'd like compute instances to get floating ips from a portion of
 that network.
 
 Using nova-networking I can make this work without issue:
 
 ```
 [[local|localrc]]
 HOST_IP=192.168.2.3
 FLOATING_RANGE=192.168.2.128/26
 ```
 
 What transformation is needed to get similar functionality with
 neutron?

[I realize you intend to use physical machine for DevStack, still I
thought I'd post this here.]

FWIW, this[1] is the minimal localrc contents (be sure to edit
ENABLED_SERVICES config directive to fit your needs) I use in my
DevStack Neutron setup in a virtual machine. This setup uses nested KVM
(LIBVIRT_TYPE=kvm in localrc does it) -- for it work, the host needs to
have nested KVM enabled:

$ modinfo kvm_intel | grep -i nested
parm:   nested:boolkvm   435079  1 kvm_intel

More details on that here[2], in case anyone else finds it useful.

Once the stack.sh is complete, I do some tasks Neutron expects:

  - Create a new private network
  - Create a new private subnet (on the above private network)
  - Create a router
  - Associate the router to an existing external network by setting it
as its gateway
  - Associate the private network interface to the router
  - Add Neutron security group rules for ICMP and SSH


[1] 
https://kashyapc.fedorapeople.org/virt/openstack/minimal_devstack_localrc.txt
[2] 
http://kashyapc.fedorapeople.org/virt/procedure-to-enable-nested-virt-on-intel-machines.txt

-- 
/kashyap

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [qa] [neutron] local.conf for devstack using neutron on home network

2014-11-07 Thread Chris Dent

On Thu, 6 Nov 2014, Kyle Mestery wrote:

On Thu, Nov 6, 2014 at 1:24 PM, Chris Dent chd...@redhat.com wrote:

Using nova-networking I can make this work without issue:

```
[[local|localrc]]
HOST_IP=192.168.2.3
FLOATING_RANGE=192.168.2.128/26
```

What transformation is needed to get similar functionality with
neutron?


Keep the above in your local.conf, and add the following:

Q_PLUGIN=ml2
Q_ML2_PLUGIN_MECHANISM_DRIVERS=openvswitch,logger
Q_AGENT=openvswitch
enable_service q-agt
ENABLE_TENANT_TUNNELS=True

That will enable GRE tunnels between your hosts using your HOST_IP as
the tunnel endpoint. And it should setup floating IPs per the range
you have specified as well.


Thanks but that doesn't quite get me all the way there. I probably
should have been more clear that I'm making a combined
controller/compute all-in-one. To that end I needed to add a few
more enabled services (q-svc, q-meta, q-dhcp).

That got me to a completed run but I had no public network and as
far as I could tell the private network was not associated with any
interface. I dug around doing a few net-, subnet- and router-
creates but seemed to be missing a piece.

I raise the pay to virtual scotch.

What I hope to have at the end of this process is a nicely commented
local.conf that I can post somewhere for people who want a similar
thing.

--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [qa] [neutron] local.conf for devstack using neutron on home network

2014-11-07 Thread Collins, Sean
On Fri, Nov 07, 2014 at 02:16:52PM CET, Chris Dent wrote:
 What I hope to have at the end of this process is a nicely commented
 local.conf that I can post somewhere for people who want a similar
 thing.

Yes, and I hope my patchset will accomplish this, I just need to make
changes to it based on both your feedback on the review, as well as
in-person discussions with Dean Troyer.

It is currently adapted from notes for my multi-node lab that contains
dual interfaces and provider networking. I am working to address your
comments about using a single interface, although some additions may
need to be done to DevStack to add the public interface to the bridge
and re-assign the IP address, similar to what Nova-Network does.

https://review.openstack.org/#/c/131201/

-- 
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [qa] [neutron] local.conf for devstack using neutron on home network

2014-11-07 Thread Chris Dent

On Fri, 7 Nov 2014, Collins, Sean wrote:


On Fri, Nov 07, 2014 at 02:16:52PM CET, Chris Dent wrote:

What I hope to have at the end of this process is a nicely commented
local.conf that I can post somewhere for people who want a similar
thing.


Yes, and I hope my patchset will accomplish this, I just need to make
changes to it based on both your feedback on the review, as well as
in-person discussions with Dean Troyer.


Awesome. Sorry about my tone in those comments. I was in the midst
of one the longer efforts to get things working (many edits to
lib/neutron, many dives in to `ip netns wtf`) and stumbled upon that
review and was initially \o/ and then :(.


It is currently adapted from notes for my multi-node lab that contains
dual interfaces and provider networking. I am working to address your
comments about using a single interface, although some additions may
need to be done to DevStack to add the public interface to the bridge
and re-assign the IP address, similar to what Nova-Network does.


I'll keep track of that review and if there are others that I can
test please give me a shout.

Thanks.

--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [qa] [neutron] local.conf for devstack using neutron on home network

2014-11-06 Thread Kyle Mestery
On Thu, Nov 6, 2014 at 1:24 PM, Chris Dent chd...@redhat.com wrote:

 I seem to be struggling to cook a neutron configuration for my little
 home network that doesn't end in a variety of failures (devstack errors
 out, floating ips are on an unexpected (and unrouted) network, etc).
 I recognize that neutron is going to be complex out of necessity, so
 I'm not complaining, I just don't know what to do.

 I've fought with this in a variety of ways, getting the sense that I'm
 just doing it completely wrong, so I thought perhaps I should just ask
 if someone can produce a config for my network (described below).

 If you do help I'll be eternally grateful and owe you virtual beer and
 you'll get the satisfaction of knowing you've helped to educate someone
 out of the pit of ignorance.

 I have a wifi network 192.168.1.0/24

 I have a mac mini on that network.

 I use internet sharing to have an ethernet network (192.168.2.0/24)
 behind the mac. Out the etherport is a switch with two additional hosts
 (2.2 and 2.3), on each of which I'd like to run devstack on bare-metal
 with floating ips on the 192.168.2 network.

 Internet sharing is satisfactory for me. I don't need to reach the
 devstack hosts or their guests from beyond the mac, but I would like to
 reach them from the mac.

 Each devstack host has one physical interface, eth0, with a static
 IP. I'd like compute instances to get floating ips from a portion of
 that network.

 Using nova-networking I can make this work without issue:

 ```
 [[local|localrc]]
 HOST_IP=192.168.2.3
 FLOATING_RANGE=192.168.2.128/26
 ```

 What transformation is needed to get similar functionality with
 neutron?

Keep the above in your local.conf, and add the following:

Q_PLUGIN=ml2
Q_ML2_PLUGIN_MECHANISM_DRIVERS=openvswitch,logger
Q_AGENT=openvswitch
enable_service q-agt
ENABLE_TENANT_TUNNELS=True

That will enable GRE tunnels between your hosts using your HOST_IP as
the tunnel endpoint. And it should setup floating IPs per the range
you have specified as well.

Thanks.
Kyle

 Thanks.

 --
 Chris Dent tw:@anticdent freenode:cdent
 https://tank.peermore.com/tanks/cdent

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev