You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,25 +104,25 @@ If you are enabling `swift3` in `ENABLED_SERVICES` devstack will install the swi
104
104
105
105
Only Swift proxy server is launched in the screen session all other services are started in background and managed by `swift-init` tool.
106
106
107
-
# Quantum
107
+
# Neutron
108
108
109
109
Basic Setup
110
110
111
-
In order to enable Quantum a single node setup, you'll need the following settings in your `localrc` :
111
+
In order to enable Neutron a single node setup, you'll need the following settings in your `localrc` :
112
112
113
113
disable_service n-net
114
114
enable_service q-svc
115
115
enable_service q-agt
116
116
enable_service q-dhcp
117
117
enable_service q-l3
118
118
enable_service q-meta
119
-
enable_service quantum
119
+
enable_service neutron
120
120
# Optional, to enable tempest configuration as part of devstack
121
121
enable_service tempest
122
122
123
123
Then run `stack.sh` as normal.
124
124
125
-
devstack supports adding specific Quantum configuration flags to both the Open vSwitch and LinuxBridge plugin configuration files. To make use of this feature, the following variables are defined and can be configured in your `localrc` file:
125
+
devstack supports adding specific Neutron configuration flags to both the Open vSwitch and LinuxBridge plugin configuration files. To make use of this feature, the following variables are defined and can be configured in your `localrc` file:
@@ -144,7 +144,7 @@ If tempest has been successfully configured, a basic set of smoke tests can be r
144
144
145
145
# Multi-Node Setup
146
146
147
-
A more interesting setup involves running multiple compute nodes, with Quantum networks connecting VMs on different compute nodes.
147
+
A more interesting setup involves running multiple compute nodes, with Neutron networks connecting VMs on different compute nodes.
148
148
You should run at least one "controller node", which should have a `stackrc` that includes at least:
149
149
150
150
disable_service n-net
@@ -153,15 +153,15 @@ You should run at least one "controller node", which should have a `stackrc` tha
153
153
enable_service q-dhcp
154
154
enable_service q-l3
155
155
enable_service q-meta
156
-
enable_service quantum
156
+
enable_service neutron
157
157
158
158
You likely want to change your `localrc` to run a scheduler that will balance VMs across hosts:
159
159
160
160
SCHEDULER=nova.scheduler.simple.SimpleScheduler
161
161
162
162
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:
0 commit comments