Jump to: navigation, search

Difference between revisions of "NeutronDevstack"

(Basic Setup)
 
(17 intermediate revisions by 12 users not shown)
Line 1: Line 1:
__NOTOC__
+
 
 
== Basic Setup ==
 
== Basic Setup ==
  
In order to use Quantum with devstack (http://devstack.org) a single node setup, you'll need the following settings in your localrc (see [http://devstack.org/stack.sh.html  this page ] for more details on localrc).
+
In order to use Neutron with devstack (http://devstack.org) a single node setup, you'll need the following settings in your local.conf (see [http://devstack.org/stack.sh.html  this page ] for more details on local.conf).
 
 
  
 
<pre><nowiki>
 
<pre><nowiki>
 +
[[local|localrc]]
 
disable_service n-net
 
disable_service n-net
 
enable_service q-svc
 
enable_service q-svc
Line 11: Line 11:
 
enable_service q-dhcp
 
enable_service q-dhcp
 
enable_service q-l3
 
enable_service q-l3
enable_service quantum
+
enable_service q-meta
 
# Optional, to enable tempest configuration as part of devstack
 
# Optional, to enable tempest configuration as part of devstack
 
enable_service tempest
 
enable_service tempest
Line 20: Line 20:
  
 
If tempest has been successfully configured, a basic set of smoke tests can be run as follows:
 
If tempest has been successfully configured, a basic set of smoke tests can be run as follows:
 
  
 
<pre><nowiki>
 
<pre><nowiki>
 
$ cd /opt/stack/tempest
 
$ cd /opt/stack/tempest
$ nosetests tempest/tests/network/test_network_basic_ops.py
+
$ nosetests tempest/scenario/test_network_basic_ops.py
 
</nowiki></pre>
 
</nowiki></pre>
  
  
See the Quantum Admin Guide for details on interacting with Quantum: [[ http://docs.openstack.org/trunk/openstack-network/admin/content/index.html ]]
+
See the Neutron Admin Guide for details on interacting with Neutron: http://docs.openstack.org/trunk/openstack-network/admin/content/index.html
 +
 
 +
== XS/XCP Setup ==
 +
 
 +
See the following page for instructions on configuring Neutron (then called Quantum, which tells you how old the linked doc is) with OVS on XS/XCP: [[QuantumDevstackOvsXcp]]
  
 
== Multi-Node Setup ==
 
== Multi-Node Setup ==
  
A more interesting setup involves running multiple compute nodes, with Quantum networks connecting VMs on different compute nodes.   
+
A more interesting setup involves running multiple compute nodes, with Neutron networks connecting VMs on different compute nodes.   
  
You should run at least one "controller node", which should have a stackrc that includes at least:  
+
You should run at least one "controller node", which should have a localrc that includes at least:  
  
  
Line 43: Line 46:
 
enable_service q-dhcp
 
enable_service q-dhcp
 
enable_service q-l3
 
enable_service q-l3
enable_service quantum
+
enable_service q-meta
</nowiki></pre>
+
enable_service neutron
 
 
 
 
You likely want to change your localrc to run a scheduler that will balance VMs across hosts:
 
 
 
 
 
<pre><nowiki>
 
SCHEDULER=nova.scheduler.simple.SimpleScheduler
 
 
</nowiki></pre>
 
</nowiki></pre>
  
  
You can then run many compute nodes, each of which should have a stackrc which includes the following, with the IP address of the above controller node:  
+
You can then run many compute nodes, each of which should have a localrc which includes the following, with the IP address of the above controller node:  
  
  
 
<pre><nowiki>
 
<pre><nowiki>
ENABLED_SERVICES=n-cpu,rabbit,g-api,quantum,q-agt
+
ENABLED_SERVICES=n-cpu,rabbit,neutron,q-agt
 
SERVICE_HOST=[IP of controller node]
 
SERVICE_HOST=[IP of controller node]
 
MYSQL_HOST=$SERVICE_HOST
 
MYSQL_HOST=$SERVICE_HOST
Line 67: Line 63:
  
  
'''Note:''' the need to include 'g-api' and 'rabbit' here seems to be a bug, which may have been fixed by the time you're reading this. Without it, nova-compute dies because it can't import the glance.common library.  This process does not actually need to be running on this host, we just need a way to make sure the glance.common library is installed.  If 'rabbit' is not specified, nova-compute also will try to connect to rabbit on localhost, not the "controller host".  See the following link for info on both issues: https://answers.launchpad.net/devstack/+question/197749
+
'''Note:''' the need to include 'rabbit' here seems to be a bug, which may have been fixed by the time you're reading this.If 'rabbit' is not specified, nova-compute also will try to connect to rabbit on localhost, not the "controller host".  See the following link for info on both issues: https://answers.launchpad.net/devstack/+question/197749

Latest revision as of 19:23, 21 August 2014

Basic Setup

In order to use Neutron with devstack (http://devstack.org) a single node setup, you'll need the following settings in your local.conf (see this page for more details on local.conf).

[[local|localrc]]
disable_service n-net
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
enable_service q-meta
# Optional, to enable tempest configuration as part of devstack
enable_service tempest


Then run stack.sh as normal.

If tempest has been successfully configured, a basic set of smoke tests can be run as follows:

$ cd /opt/stack/tempest
$ nosetests tempest/scenario/test_network_basic_ops.py


See the Neutron Admin Guide for details on interacting with Neutron: http://docs.openstack.org/trunk/openstack-network/admin/content/index.html

XS/XCP Setup

See the following page for instructions on configuring Neutron (then called Quantum, which tells you how old the linked doc is) with OVS on XS/XCP: QuantumDevstackOvsXcp

Multi-Node Setup

A more interesting setup involves running multiple compute nodes, with Neutron networks connecting VMs on different compute nodes.

You should run at least one "controller node", which should have a localrc that includes at least:


disable_service n-net
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
enable_service q-meta
enable_service neutron


You can then run many compute nodes, each of which should have a localrc which includes the following, with the IP address of the above controller node:


ENABLED_SERVICES=n-cpu,rabbit,neutron,q-agt
SERVICE_HOST=[IP of controller node]
MYSQL_HOST=$SERVICE_HOST
RABBIT_HOST=$SERVICE_HOST
Q_HOST=$SERVICE_HOST


Note: the need to include 'rabbit' here seems to be a bug, which may have been fixed by the time you're reading this.If 'rabbit' is not specified, nova-compute also will try to connect to rabbit on localhost, not the "controller host". See the following link for info on both issues: https://answers.launchpad.net/devstack/+question/197749