diff --git a/doc/install-guide/bk_openstackinstallguide.xml b/doc/install-guide/bk_openstackinstallguide.xml index c92341287b..6384c6f597 100644 --- a/doc/install-guide/bk_openstackinstallguide.xml +++ b/doc/install-guide/bk_openstackinstallguide.xml @@ -175,377 +175,6 @@ - - 2013-04-30 - - - - Grizzly release. - - - - - - 2013-04-18 - - - - Updates and clean up on the Object - Storage installation. - - - - - - 2013-04-08 - - - - Adds a note about availability of - Grizzly packages on Ubuntu and - Debian. - - - - - - 2013-04-03 - - - - Updates RHEL/CentOS/Fedora - information for Grizzly - release. - - - - - - 2013-03-26 - - - - Updates Dashboard (Horizon) - information for Grizzly - release. - - - - - - 2013-02-12 - - - - Adds chapter about Essex to Folsom - upgrade for Compute and related - services (excludes OpenStack Object - Storage (Swift) and OpenStack - Networking (Quantum)). - - - - - - 2013-01-16 - - - - Fix file copy issue for figures in - the /common/ directory. - - - - - - 2012-11-09 - - - - Folsom release of this - document. - - - - - - 2012-10-10 - - - - Doc bug fixes: 10544591064745 - - - - - - 2012-09-26 - - - - Adds an all-in-one install - section. - - - - - - 2012-07-23 - - - - Adds additional detail about - installing and configuring - nova-volumes. - - - Doc bug fixes: 978510 - 1027230 - - - - - - 2012-07-17 - - - - Update build process so two - uniquely-named PDF files are - output. - - - - - - 2012-07-13 - - - - Doc bug fixes: 1025840 - 1025847 - - - - - - 2012-06-19 - - - - Fix PDF links. - - - Doc bug fixes: 967778 - 984959, 1002294, 1010163. - - - - - - - 2012-05-31 - - - - Revise install guide to encompass - more Linux distros. - - - Doc bug fixes: 996988, 998116, 999005. - - - - - - 2012-05-03 - - - - Fixes problems with - glance-api-paste.ini - and - glance-registry-paste.ini - samples and instructions. - - - Removes "DRAFT" designation. - - - - - - 2012-05-02 - - - - Essex release. - - - - - - 2012-05-01 - - - - Updates the Object Storage and - Identity (Keystone) - configuration. - - - - - - 2012-04-25 - - - - Changes service_id copy/paste error - for the EC2 service-create - command. - Adds verification steps for Object - Storage installation. - Fixes - proxy-server.conf - file so it points to keystone not - tempauth. - - - - - - 2012-04-23 - - - - Adds installation and configuration - for multi-node Object Storage - service. - - - - - - 2012-04-17 - - - - Doc bug fixes: 983417, 984106, 984034 - - - - - - 2012-04-13 - - - - Doc bug fixes: 977905, 980882, 977823, adds additional - Glance database preparation - steps - - - - - - 2012-04-10 - - - - Doc bug fixes: 977831 - - - - - - 2012-03-23 - - - - Updates for Xen hypervisor. - - - - - - 2012-03-09 - - - - Updates for Essex release, includes - new Glance config files, new Keystone - configuration. - - - - - - 2012-01-24 - - - - Initial draft for Essex. - - - Assumes use of Ubuntu 12.04 - repository. - - - - - - - - 2011-01-24 - - - - Initial draft for Diablo. - - - - diff --git a/doc/install-guide/section_neutron-compute-node.xml b/doc/install-guide/section_neutron-compute-node.xml index 6cd9a9e2bc..6a4fa29173 100644 --- a/doc/install-guide/section_neutron-compute-node.xml +++ b/doc/install-guide/section_neutron-compute-node.xml @@ -5,26 +5,25 @@ xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:svg="http://www.w3.org/2000/svg" xmlns:html="http://www.w3.org/1999/xhtml" version="5.0"> - Configure compute node + Configure compute node with neutron services This section details set up for any node that runs the nova-compute component but does not run the full network stack. - By default, the system-config-firewall - automated firewall configuration tool is in place on RHEL. - This graphical interface (and a curses-style interface with - -tui on the end of the name) enables you - to configure IP tables as a basic firewall. You should disable - it when you work with Neutron unless you are familiar with the - underlying network technologies, as, by default, it blocks - various types of network traffic that are important to - Neutron. To disable it, simple launch the program and clear - the Enabled check box. - After you successfully set up OpenStack with Neutron, you - can re-enable and configure the tool. However, during Neutron - set up, disable the tool to make it easier to debug network + By default, the system-config-firewall automated + firewall configuration tool is in place on RHEL. This graphical interface + (and a curses-style interface with -tui on the end of + the name) enables you to configure IP tables as a basic firewall. You + should disable it when you work with OpenStack Networking unless you are + familiar with the underlying network technologies, as, by default, it + blocks various types of network traffic that are important to neutron + services. To disable it, launch the program and clear the + Enabled check box. + After you successfully set up OpenStack Networking with Neutron, you + can re-enable and configure the tool. However, during OpenStack + Networking setup, disable the tool to make it easier to debug network issues. @@ -246,7 +245,7 @@ firewall_driver=neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallD
- Install and configure Neutron plug-ins on a dedicated + <title>Install and configure OpenStack Networking plug-ins on a dedicated compute node
Install the Open vSwitch (OVS) plug-in on a dedicated diff --git a/doc/install-guide/section_neutron-initial-networks.xml b/doc/install-guide/section_neutron-initial-networks.xml index f34c009ebf..69bf9f0d9f 100644 --- a/doc/install-guide/section_neutron-initial-networks.xml +++ b/doc/install-guide/section_neutron-initial-networks.xml @@ -7,24 +7,20 @@ xmlns:html="http://www.w3.org/1999/xhtml" version="5.0"> <title>Create initial networks - In these sections, replace - SPECIAL_OPTIONS with any options - specific to your Networking plug-in choices. See here to check if your plug-in requires any special - options. + In these sections, replace SPECIAL_OPTIONS with any options specific to your OpenStack Networking plug-in choices. See here to check if your plug-in requires any special options. - Create the ext-net external network. - This network represents a slice of the outside world. VMs - are not directly linked to this network; instead, they - connect to internal networks. Outgoing traffic is routed by - Neutron to the external network. Additionally, floating IP - addresses from the subnet for ext-net - might be assigned to VMs so that the external network can - contact them. Neutron routes the traffic - appropriately. + Create the ext-net external network. This + network represents a slice of the outside world. VMs are not directly + linked to this network; instead, they connect to internal networks. + Outgoing traffic is routed by OpenStack Networking to the external + network. Additionally, floating IP addresses from the subnet for + ext-net might be assigned to VMs so that the + external network can contact them. Neutron-based services route the + traffic appropriately. # neutron net-create ext-net --router:external=True SPECIAL_OPTIONS @@ -116,16 +112,38 @@ router_id = EXT_TO_INT_ID for any other network. These options are not needed beyond the first - network, as Neutron automatically increments the - segmentation id and copy the network type option for any - additional networks. + network, as OpenStack Networking services automatically + increment the segmentation ID and copy the network type + option for any additional networks. - Now, return to the general OVS + Now, return to the general OVS instructions.
VLAN network options + + Some NICs have Linux drivers that do not handle + VLANs properly. See the + ovs-vlan-bug-workaround and + ovs-vlan-test man pages for more + information. Additionally, you might try turning off + rx-vlan-offload and + tx-vlan-offload by using + ethtool on the + DATA_INTERFACE. Another + potential caveat to VLAN functionality is that VLAN tags + add an additional 4 bytes to the packet size. If your + NICs cannot handle large packets, make sure to set the + MTU to a value that is 4 bytes less than the normal + value on the + DATA_INTERFACE. + If you run OpenStack inside a virtualized + environment (for testing purposes), switching to the + virtio NIC type (or a similar + technology if you are not using KVM/QEMU to run your + host VMs) might solve the issue. + When creating networks, use these options: --provider:network_type vlan --provider:physical_network physnet1 --provider:segmentation_id SEG_ID SEG_ID should be @@ -140,28 +158,6 @@ router_id = EXT_TO_INT_ID only needed if you wish to modify those values in any way. - - Some NICs have Linux drivers that do not handle - VLANs properly. See the - ovs-vlan-bug-workaround and - ovs-vlan-test man pages for more - information. Additionally, you might try turning off - rx-vlan-offload and - tx-vlan-offload by using - ethtool on the - DATA_INTERFACE. Another - potential caveat to VLAN functionality is that VLAN tags - add an additional 4 bytes to the packet size. If your - NICs cannot handle large packets, make sure to set the - MTU to a value that is 4 bytes less than the normal - value on the - DATA_INTERFACE. - If you run OpenStack inside a virtualized - environment (for testing purposes), switching to the - virtio NIC type (or a similar - technology if you are not using KVM/QEMU to run your - host VMs) might solve the issue. -