Promote volumes content from section to chapter.

This change takes the content about volumes out of the System Admin
chapter and puts it in a new chapter called volumes.

This is a pure refactoring, no content has been modified.

Change-Id: I7482925cd008009eb4f433c3c93ffda20cbbfc89
enable virtio NICs for windows image example

In the image management section, an example of how to boot a windows
image is given. Previously, virtio (a faster network card than
 default) was on the commandline, but not used in the VM

This change - taken from the bug report, and assumed to be OK rather
than tested - enables the nic.

fixes bug 1016663

Change-Id: I8b37f4eb268ca90a5b08238edec636a25973ec14
Update build process so two uniquely-named PDF files are output.

Change-Id: I5f3f098efadd80bb5cca1f420b0f862202b559e3
Merge "Promote volumes content from section to chapter."
Expand network troubleshooting section

Move troubleshooting from a subsubsection of Networking
(under floating IPs) to a subsection.

Add content about disabling reverse path filtering.

Add content about temporarily disabling firewall.

Patch set makes the xml:id="network-troubleshooting" and attempts to
address ambiguity pointed out in bug 1024321.

Change-Id: If3911b8920bddba16b72a75ba2d5a0c5b360d0ed
connection_type => compute_driver

Convert examples that use connection_type to compute_driver with
appropriate driver strings. There probably needs to be slightly more
explanation of the change. Also, there are additional tables that
are not modified by this patch, as I was unclear if they were
autogenerated or not.

Patchset does an include for updates
to the hypervisor config table and common config table
with the new compute_driver settings.

Change-Id: I5cdfb1a59c9029760de4796127bfbe16f4306d4c
Merge "Update build process so two uniquely-named PDF files are output."
Merge "enable virtio NICs for windows image example"
Add documentation for recently added os-used-limits extension.

The os-used-limits extension adds information for limits that have been used so
far to the /limits GET response.

The ext was added in this patch: https://review.openstack.org/#/c/9544/

Change-Id: I8bdb1b9ebdbc4b92a8e9a3143e8ed5d4724ac264
connection_type => compute_driver

Found one more instance where connection_type was used
in one of the diagrams. Updated it to compute_driver.

Change-Id: I82b6ccf99e3b9c65d6b8c6b0ab78366e147fd835
Adds text to explain intro arch diagram, updates dashboard install.

Fixes two doc bugs: bug 1025847, bug 1025840

Change-Id: I7bd348349ef49d581cbaf284497d13816535a11d
Merge "Expand network troubleshooting section"
Fix bug 1025910, bug 1026321

Brings a link to the RHEL Install and Deploy Guide and fixes
an incorrect reference to Image service (Keystone).

Change-Id: Ie53aa7a3f636965556b382fcf671d91294c52a8c
Adds new Disqus id openstack-ha-guide
for the High Availability Guide.

Change-Id: Ie30087d5f606a4231b8b3c7899d95630c1a85c48
Merge "Add documentation for recently added os-used-limits extension."
Fix CoreFilter setting to avoid overallocation

From Jon Proulx (jproulx), who is still awaiting approval:

"Only schedule instances on hosts if there are sufficient CPU
cores available. If this filter is not set, the scheduler may
overprovision a host based on cores"

but in reality cpu_allocation_ratio must also be set with this
 filter. According to http://docs.openstack.org/essex/openstack-
compute/admin/content/compute-options-reference.html
 cpu_allocation_ratio defaults to 16.0 meaning cpu will be
 overprovisioned by 16:1 to get the behaviour described
 cpu_allocation_ratio must be set to 1.0

fixes bug 1027309

Change-Id: Ieea6c5ab13ce3514e508e4ad3799253d348b64d4
Fixes the syntax of nova options table

This was causing the build to fail - the problem here is
 that some items in the table have 3 columns - but there is only
two columns setup in the top. Merging to have two columns
fixes the problem

fixes bug 1027396

Change-Id: Ia3463a89c3a577e8acc7d779cd8110b3c05c141d
metadata_host config option must be an IP address

Document more explicitly that the metadata_host configuration
option must be an IP address, not a hostname.

This issue came up on the OpenStack mailing list in the following
thread:

http://www.mail-archive.com/openstack@lists.launchpad.net/msg13269.html

Change-Id: I4a5e26900fe961dbf92a1a5c7a1b8db302845d94
Scheduler retry config option and filter.

New flag: scheduler_max_attempts

New scheduler filter: RetryFilter

Changes introduced by https://review.openstack.org/9540

Also removed some trailing whitespace on some lines.

Change-Id: I26eeb6964a55d4b9b1484e2504549344c32fe367
Troubleshooting packet drops across bridge with VLAN

Added a section in troubleshooting networking related to packets
being dropped in VLAN mode.

Docs are based on this blog post:
http://buriedlede.blogspot.com/2012/07/debugging-networking-problems-with.html

Change-Id: Iba56085703a98154b3035122f8ab3b36b5cbe41d