Permalink
Browse files

Removed starting nova-compute on the gateway (it is already started b…

…y 08-openstack-compute/05-nova-compute-start.sh)
  • Loading branch information...
1 parent af4e31d commit 3a1e43e0bb5217d6fa9fbca8671b2d826a6a6f6d @beloglazov committed Nov 14, 2012
@@ -18,15 +18,13 @@
# It is assumed that the gateway host is one of the compute hosts;
# therefore, the openstack-nova-* service are already installed.
-# Start the libvirt and Nova services (network, compute and VNC proxies)
+# Start the libvirt and Nova services (network, and VNC proxies)
service libvirtd restart
service openstack-nova-network restart
-service openstack-nova-compute restart
service openstack-nova-novncproxy restart
service openstack-nova-xvpvncproxy restart
# Make the service start on the system startup
chkconfig openstack-nova-network on
-chkconfig openstack-nova-compute on
chkconfig openstack-nova-novncproxy on
chkconfig openstack-nova-xvpvncproxy on
View
@@ -1923,16 +1923,14 @@ the gateway in our case.
::
# Start the Libvirt and Nova services
- # (network, compute and VNC proxies)
+ # (network, and VNC proxies)
service libvirtd restart
service openstack-nova-network restart
- service openstack-nova-compute restart
service openstack-nova-novncproxy restart
service openstack-nova-xvpvncproxy restart
# Make the service start on the system start up
chkconfig openstack-nova-network on
- chkconfig openstack-nova-compute on
chkconfig openstack-nova-novncproxy on
chkconfig openstack-nova-xvpvncproxy on
Binary file not shown.
@@ -1264,16 +1264,14 @@ <h4 id="openstack-gateway-network-gateway."><a href="#TOC"><span class="header-s
</ol>
<p>It is assumed that the gateway host is one of the compute hosts; therefore, the OpenStack compute service has already been configured and is running. This scripts starts 3 additional Nova services that are specific to the gateway host: <code>openstack-nova-network</code>, <code>openstack-nova-novncproxy</code>, and <code>openstack-nova-xvpvncproxy</code>. The <code>openstack-nova-network</code> service is responsible for bridging VM instances into the physical network, and configuring the Dnsmasq service for assigning IP addresses to the VMs. The VNC proxy services enable VNC connections to VM instances from the outside network; therefore, they must be run on a machine that has access to the public network, which is the gateway in our case.</p>
<pre class="sourceCode Bash"><code class="sourceCode bash"><span class="co"># Start the Libvirt and Nova services</span>
-<span class="co"># (network, compute and VNC proxies)</span>
+<span class="co"># (network, and VNC proxies)</span>
service libvirtd restart
service openstack-nova-network restart
-service openstack-nova-compute restart
service openstack-nova-novncproxy restart
service openstack-nova-xvpvncproxy restart
<span class="co"># Make the service start on the system start up</span>
chkconfig openstack-nova-network on
-chkconfig openstack-nova-compute on
chkconfig openstack-nova-novncproxy on
chkconfig openstack-nova-xvpvncproxy on</code></pre>
<ol start="52" style="list-style-type: example">
Binary file not shown.
@@ -1767,16 +1767,14 @@ in our case.
```Bash
# Start the Libvirt and Nova services
-# (network, compute and VNC proxies)
+# (network, and VNC proxies)
service libvirtd restart
service openstack-nova-network restart
-service openstack-nova-compute restart
service openstack-nova-novncproxy restart
service openstack-nova-xvpvncproxy restart
# Make the service start on the system start up
chkconfig openstack-nova-network on
-chkconfig openstack-nova-compute on
chkconfig openstack-nova-novncproxy on
chkconfig openstack-nova-xvpvncproxy on
```

0 comments on commit 3a1e43e

Please sign in to comment.