openstack/openstack-manuals
Code Issues Proposed changes

Cleaning up some unused files and text

Browse Source 
These files were not included in the build and this text was
commented out - removing.

Change-Id: Icbbfd27de84047a11ebfd7eb9bd09ea47dfcdcde
This commit is contained in:
Tom Fifield
2012-09-11 21:53:31 +10:00
parent 62553b29d3
commit 8f83d60e32
5 changed files with 0 additions and 96 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
doc/src/docbkx/openstack-install/ch_installcomputeimage.xml
View File

@@ -15,7 +15,6 @@
<xi:include href="../common/introduction-to-xen.xml" />
<xi:include href="compute-config-guest-network.xml" />
<xi:include href="compute-database-mysql.xml"/>
<!-- <xi:include href="compute-database-postgresql.xml" /> -->
<xi:include href="compute-cloud-controller.xml" />
<xi:include href="compute-minimum-configuration.xml" />
<xi:include href="compute-db-sync.xml"/>
@@ -23,6 +22,4 @@
<xi:include href="compute-verifying-install.xml" />
<xi:include href="configure-creds.xml" />
<xi:include href="installing-additional-compute-nodes.xml" />
<!--<xi:include href="enable-access-security-group.xml" />-->
</chapter>

1
doc/src/docbkx/openstack-install/compute-create-network.xml
View File

@@ -4,7 +4,6 @@
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
<title>Creating the Network for Compute VMs</title>
<!--<para>To avoid confusion, you can also remove the unnecessary virtual network that libvirt creates. </para><literallayout class="monospaced">sudo virsh net-destroy default; rm /etc/libvirt/qemu/networks/autostart/default.xml</literallayout>-->
<para>You must run the command that creates the network and the bridge using the br100 specified in the nova.conf file to create the network that the virtual machines
use. This example shows the
network range using 192.168.100.0/24 as the fixed range for our guest VMs, but you can substitute the range for the network you have

54
doc/src/docbkx/openstack-install/compute-database-postgresql.xml
View File

@@ -1,54 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<section xml:id="setting-up-sql-database-postgresql"
xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
<title>Setting Up PostgreSQL as the Database on the Cloud Controller</title>
<para>OpenStack can use PostgreSQL as an alternative database. This is a matter of substituting the MySQL steps with PostgreSQL equivalents, as outlined here.</para>
<para>First, install PostgreSQL on the controller node.</para>
<literallayout class="monospaced">apt-fast install postgresql postgresql-server-dev-8.4 python-dev python-psycopg2</literallayout>
<para>Edit /etc/postgresql/8.4/main/postgresql.conf and change the listen_address to listen to all appropriate addresses, PostgreSQL listen only to localhost by default. For example:</para>
<para>To listen on a specific IP address:</para>
<literallayout class="monospaced"># - Connection Settings -
listen_address = '10.1.1.200,192.168.100.2'</literallayout>
<para>To listen on all addresses:</para>
<literallayout class="monospaced"># - Connection Settings -
listen_address = '*'</literallayout>
<para>Add appropriate addresses and networks to /etc/postgresql/8.4/main/pg_hba.conf to allow remote access to PostgreSQL, this should include all servers hosting OpenStack (but not neccessarily those hosted by Openstack). As an example, append the following lines:</para>
<literallayout class="monospaced">host all all 192.168.0.0/16
host all all 10.1.0.0/16
</literallayout>
<para>Change the default PostgreSQL user's password:</para>
<literallayout class="monospaced">
sudo -u postgres psql template1
template1=#\password
Enter Password:
Enter again:
template1=#\q</literallayout>
<para>Restart PostgreSQL:</para>
<literallayout class="monospaced">service postgresql restart</literallayout>
<para>Create nova databases:</para>
<literallayout class="monospaced">sudo -u postgres createdb nova
sudo -u postgres createdb glance</literallayout>
<para>Create nova database user which will be used for all OpenStack services, note the adduser and createuser steps will prompt for the user's password ($PG_PASS):</para>
<literallayout class="monospaced">
adduser nova
sudo -u postgres createuser -PSDR nova
sudo -u postgres psql template1
template1=#GRANT ALL PRIVILEGES ON DATABASE nova TO nova
template1=#GRANT ALL PRIVILEGES ON DATABASE glance TO nova
template1=#\q
</literallayout>
<para>For Nova components that require access to this database the required configuration in /etc/nova/nova.conf should be (replace $PG_PASS with password):</para>
<literallayout class="monospaced">sql_connection=postgresql://nova:$PG_PASS@control.example.com/nova</literallayout>
<para>At this stage the databases are empty and contain no content. These will be initialised when you do the nova-manage db sync command. </para>
</section>

37
doc/src/docbkx/openstack-install/enable-access-security-group.xml
View File

@@ -1,37 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<section xml:id="enabling-access-to-vms-on-the-compute-node"
xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
<title>Enabling Access to VMs on the Compute Node</title>
<para>One of the most commonly missed configuration areas is not
allowing the proper access to VMs. Use the nova client to
enable access. The commands below allow 'ping' and 'ssh' to
your VMs : </para>
<note>
<para> These commands need to be run as root only if the
credentials used to interact with nova-api have been put
under /root/.bashrc. If the EC2 credentials have been put
into another user's .bashrc file, then, it is necessary to
run these commands as the user. You can also add --os_username
as a parameter to the nova command when you want to run as a specific user. </para>
</note>
<literallayout class="monospaced">
nova  secgroup-add-rule default icmp - 1 -1 0.0.0.0/0
nova  secgroup-add-rule default tcp 22 22 0.0.0.0/0
</literallayout>
<para>Another common issue is you cannot ping or SSH your
instances after issuing these commands. Something to look at
is the amount of ‘dnsmasq’ processes that are running. If you
have a running instance, check to see that TWO "dnsmasq’"
processes are running. If not, perform the following: </para>
<literallayout class="monospaced">sudo killall dnsmasq
sudo service nova-network restart</literallayout>
<para>If you get the
<literallayout class="monospaced">instance not found</literallayout>
message while performing the restart, that means the service
was not previously running. You simply need to start it
instead of restarting it:
<literallayout class="monospaced">sudo service nova-network start</literallayout>
</para>
</section>

1
doc/src/docbkx/openstack-install/identity-install-keystone.xml
View File

@@ -103,7 +103,6 @@
get other services authenticating and authorizing with the
Identity service. </para>
<para>Scripted configuration:</para>
<!--<para>On Fedora, RHEL, and Centos, you can run this script to populate with sample data.</para><screen os="rhel;centos;fedora"><prompt>$</prompt> <userinput>sudo ADMIN_PASSWORD=$OS_PASSWORD SERVICE_PASSWORD=servicepass openstack-keystone-sample-data</userinput></screen>-->
<para>The Keystone project offers a bash script for populating
tenants, users, and roles at
<link xlink:href="https://github.com/openstack/keystone/blob/master/tools/sample_data.sh">https://github.com/openstack/keystone/blob/master/tools/sample_data.sh</link>