From 842dd948d71fe28cf3bd70168fbccac4f534b897 Mon Sep 17 00:00:00 2001 From: annegentle Date: Thu, 27 Sep 2012 09:48:51 -0500 Subject: [PATCH] Update install guide for folsom: - Point to cloud archive for ubuntu packages - Add Folsom to release table - Adds ch_installingfolsom.xml but doesn't xi:include it in book file yet. Patchset removes ch_installingfolsom.xml as I've patched the other patch to make it an appendix. Rebase against master. Change-Id: I0b1d8ffa8f62e6c5b38e6ee0df7ee2e2dd456ddb --- doc/src/docbkx/common/kvm.xml | 13 +++++---- doc/src/docbkx/common/qemu.xml | 25 +++++++++++------ .../bk_openstackinstallguide.xml | 12 ++++++++- .../openstack-install/ch_assumptions.xml | 10 +++++-- .../docbkx/openstack-install/ch_externals.xml | 8 +++--- .../openstack-install/ch_terminology.xml | 27 +++++++++++++++++-- .../compute-config-guest-network.xml | 6 ++--- .../install-config-proxy-node.xml | 11 ++++---- 8 files changed, 83 insertions(+), 29 deletions(-) diff --git a/doc/src/docbkx/common/kvm.xml b/doc/src/docbkx/common/kvm.xml index 593960483d..c2d936cb70 100644 --- a/doc/src/docbkx/common/kvm.xml +++ b/doc/src/docbkx/common/kvm.xml @@ -40,9 +40,11 @@ libvirt_type=kvm RHEL: Installing virtualization packages on an existing Red Hat Enterprise - Linux system from the Red Hat Enterprise Linux Virtualizaiton Host - Configuration and Guest Installation Guide. + >RHEL: Installing virtualization packages on + an existing Red Hat Enterprise Linux + system from the Red Hat Enterprise + Linux Virtualization Host Configuration and Guest + Installation Guide. SLES: Installing KVM from the SUSE Linux Enterprise - ServerVirtualization with KVM manual. + >SLES: Installing KVM from the SUSE + Linux Enterprise Server Virtualization with KVM + manual.
diff --git a/doc/src/docbkx/common/qemu.xml b/doc/src/docbkx/common/qemu.xml index 46ff282a14..b953818fa6 100644 --- a/doc/src/docbkx/common/qemu.xml +++ b/doc/src/docbkx/common/qemu.xml @@ -12,14 +12,16 @@ performance than KVM and is a poor choice for a production deployment. The typical uses cases for QEMU are - Running on older hardware that lacks virtualization support. + Running on older hardware that lacks + virtualization support. - Running the Compute service inside of a virtual machine for development or - testing purposes, where the hypervisor does not support native virtualization - for guests. + Running the Compute service inside of a virtual + machine for development or testing purposes, where + the hypervisor does not support native + virtualization for guests. - running on + KVM requires hardware support for acceleration. If hardware support is not available (e.g., if you are running Compute inside of a VM and the hypervisor does not expose the required hardware support), you can use QEMU instead. KVM and QEMU have the same level of @@ -47,9 +49,16 @@ libvirt_type=qemu
Tips and fixes for QEMU on RHEL - - If you are testing OpenStack in a virtual machine, you need to configure nova to use qemu without KVM and hardware virtualization. The second command relaxes SELinux rules to allow this mode of operation (https://bugzilla.redhat.com/show_bug.cgi?id=753589) The last 2 commands here work around a libvirt issue fixed in RHEL 6.4. Note nested virtualization will be the much slower TCG variety, and you should provide lots of memory to the top level guest, as the openstack created guests default to 2GM RAM with no overcommit. - + If you are testing OpenStack in a virtual machine, you need + to configure nova to use qemu without KVM and hardware + virtualization. The second command relaxes SELinux rules + to allow this mode of operation + (https://bugzilla.redhat.com/show_bug.cgi?id=753589) The + last 2 commands here work around a libvirt issue fixed in + RHEL 6.4. Note nested virtualization will be the much + slower TCG variety, and you should provide lots of memory + to the top level guest, as the OpenStack-created guests + default to 2GM RAM with no overcommit. The second command, setsebool, may take a while. $> sudo openstack-config --set /etc/nova/nova.conf DEFAULT libvirt_type qemu $> setsebool -P virt_use_execmem on diff --git a/doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml b/doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml index 6bad278cf8..e7960d139e 100644 --- a/doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml +++ b/doc/src/docbkx/openstack-install/bk_openstackinstallguide.xml @@ -26,7 +26,7 @@ trunk OpenStack - 2012-07-23 + 2012-09-26 Copyright details are filled in by the template. @@ -51,6 +51,16 @@ as well as sample configuration files. + + 2012-09-26 + + + + Adds an all-in-one install section. + + + + 2012-07-23 diff --git a/doc/src/docbkx/openstack-install/ch_assumptions.xml b/doc/src/docbkx/openstack-install/ch_assumptions.xml index 0b9cd1d206..6b01bb9b33 100644 --- a/doc/src/docbkx/openstack-install/ch_assumptions.xml +++ b/doc/src/docbkx/openstack-install/ch_assumptions.xml @@ -58,8 +58,14 @@ FlatDHCP with a single network interface. - KVM or Xen (XenServer or XCP) as the hypervisor. - + KVM or Xen (XenServer or XCP) as the + hypervisor. + + + On Ubuntu, enable the Cloud Archive repository by + adding the following to + /etc/apt/sources.list.d/folsom.list:deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/folsom main + Ensure the operating system is up-to-date by running yum update prior to diff --git a/doc/src/docbkx/openstack-install/ch_externals.xml b/doc/src/docbkx/openstack-install/ch_externals.xml index 98163907a9..c7fe8630b4 100644 --- a/doc/src/docbkx/openstack-install/ch_externals.xml +++ b/doc/src/docbkx/openstack-install/ch_externals.xml @@ -107,9 +107,11 @@ via iSCSI using IET or tgt. It can also be configured to use other iSCSI-based storage technologies. - In a future OpenStack release, functionality that is currently implemented by - nova-volume will be available through a - separate OpenStack project, codenamed Cinder. + In the Folsom OpenStack release, functionality available + through nova-volume is also available through a + separate OpenStack Volumes project, code-named + Cinder. openstack-dashboard The openstack-dashboard is a Django-based diff --git a/doc/src/docbkx/openstack-install/ch_terminology.xml b/doc/src/docbkx/openstack-install/ch_terminology.xml index 1aaebe7761..60e955ac97 100644 --- a/doc/src/docbkx/openstack-install/ch_terminology.xml +++ b/doc/src/docbkx/openstack-install/ch_terminology.xml @@ -28,6 +28,12 @@ + + Folsom + September 2012 + 2012.2 + 1.7.2 + Essex April 2012 @@ -123,6 +129,22 @@ Swift + + + Volumes + + + Cinder + + + + + Networking + + + Quantum + + @@ -190,8 +212,9 @@
Block storage (SAN) - In OpenStack: Volumes (nova-volume - service) in OpenStack Compute + In OpenStack: Volumes (nova-volume service) in OpenStack + Compute or cinder as a separate Volume service Related concepts: Amazon Elastic Block Store (EBS), Ceph RADOS Block Device (RBD), iSCSI With block storage, files are exposed through a diff --git a/doc/src/docbkx/openstack-install/compute-config-guest-network.xml b/doc/src/docbkx/openstack-install/compute-config-guest-network.xml index 0d2eed38d8..03ee4bf24b 100644 --- a/doc/src/docbkx/openstack-install/compute-config-guest-network.xml +++ b/doc/src/docbkx/openstack-install/compute-config-guest-network.xml @@ -11,8 +11,8 @@ Set your network interface in promiscuous mode so that it can receive packets that are intended for virtual machines. As root:# ip link set eth0 promisc on - Set up your /etc/network/interfaces file with these settings: - eth0: public IP, gateway + Set up your /etc/network/interfaces file with these settings: + eth0: public IP, gateway br100: no ports, stp off, fd 0, first address from fixed_range set in nova.conf files. Here's an Ubuntu/Debian example: # The loopback network interface @@ -30,7 +30,7 @@ address 192.168.100.1 netmask 255.255.255.0 bridge_stp off bridge_fd 0 - Here's an example for RHEL, Fedora, or CentOS. Create + Here's an example network setup for RHEL, Fedora, or CentOS. Create /etc/sysconfig/network-scripts/ifcfg-br100: diff --git a/doc/src/docbkx/openstack-install/install-config-proxy-node.xml b/doc/src/docbkx/openstack-install/install-config-proxy-node.xml index 7ff066b154..54424988e8 100644 --- a/doc/src/docbkx/openstack-install/install-config-proxy-node.xml +++ b/doc/src/docbkx/openstack-install/install-config-proxy-node.xml @@ -4,10 +4,11 @@ xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" > Installing and Configuring the Proxy Node - The proxy server takes each request and looks up locations for the - account, container, or object and routes the requests correctly. The - proxy server also handles API requests. You enable account - management by configuring it in the proxy-server.conf file. + The proxy server takes each request and looks up locations + for the account, container, or object and routes the requests + correctly. The proxy server also handles API requests. You + enable account management by configuring it in the + proxy-server.conf file. It is assumed that all commands are run as the root user. @@ -41,7 +42,7 @@ to #service memcached restart - To set up Object Storage to authenticate tokens we need to set the keystone Admin + RHEL/CentOS/Fedora Only: To set up Object Storage to authenticate tokens we need to set the keystone Admin token in the swift proxy file with the openstack-config command. # openstack-config --set /etc/swift/proxy-server.conf filter:authtoken admin_token $ADMIN_TOKEN # sudo openstack-config --set /etc/swift/proxy-server.conf filter:authtoken auth_token $ADMIN_TOKEN