Update links to Murano Docs

Murano docs changed format and location.
Links in FUEL docs were outdated.

Change-Id: I0187fb82458c2a433b863b1fb1d9bc75274dc51b
Closes-bug: #1321700
Update control files to 5.0 and date to May 2014

List of major releases is removed from preface.rst: the intention of this table
is to track revisions of documentation for the current major release.

Change-Id: If0d87ccfdcb9b312174a6e1ddeefa03dd38f253f
Moved information from install to separate vbox doc

I did a wee bit of wordsmithing but the content is unchanged.

A section that used to be in the FAQ duplicated instructions to select
promiscuous mode, which is in the main instructions, so I deleted it.

Change-Id: I1d8e10f7c2ef37069d1c55c7b2b18368b39a8c31
Update PXE boot documentation

Change-Id: Icd7f2cea8dcee68151878bbb3ef5008520ec2a13
Closes-Bug: 1308279
Set up Planning Guide

I started with the "Preparing the MOS Deployment" table
The hardware setup steps have been moved to the Install Guide in another CM
Added a few issues that were not spelled out
Set up separate sections to hold the discussions for each issue.

"Network Topologies" cross-references architectural information in ref-arch
* Andrey Danin provided the "advice"
* Restructuring the network docs became necessary to make this work. To whit:

For Neutron, various structural modifications were required;
no substantive content modifications were made
* Added a couple headers and tags to ref-arch for Neutron topologies
* Deleted files from pre-install/0051-network-plan/topology:
  * 0710-neutron-topologies.rst -- header only, no longer required
  * 0720-neutron-vlan.rst -- duplicates info in ref-arch/neutron-intro/\
    0210-vlan.rst; this had a couple sentences at the end that weren't in
    ref-arch so I moved those over
  * 0730-neutron-gre.rst -- duplicates info in ref-arch/neutron-intro/\
    0220-gre.rst; this had a couple sentences at the end that weren't in
    ref-arch so I moved those over
  * 0760-neutron-vlan-plan.rst and 0780-neutron-gre-plan.rst were pulled
    into ref-arch/0260-neutron-config.rst.  Yes, this leaves one file with
    three headers in it but, when we deal with the content, these pieces
    need to be considered together
* pre-install/0051-network-plan/topology/0700-neutron.rst just sourced the
    above files so is deleted

For Nova, moved the nova-network topology info from pre-install to ref-arch
to parallel the Neutron section we set up there.
* The following files from pre-installation/0051-network-plan/topology/nova
  are now in reference-architecture/nova-intro and sourced from the
  6070-nova-topologies.rst file in reference-architecture.  Section titles
  are also modified to include "Nova-network" to improve readability:
  - 0620-nova-flat-dhcp.rst
  - 0630-nova-vlan.rst
  - 0659-nova-net-plan.rst
  - 0660-nova-plan-flatdhcp.rst
  - 0680-plan-vlan.rst
  - [ignore 0650-nova-assign-networks-to-nics.rst -- it is going to User Guide]
* Other files from this directory are disposed of as follows:
  - 0610-nova-topologies -- sourced ino ref-arch/6070-nova-topologies.rst
    (top file of nova section in ref-arch)
  - 0650-nova-assign-networks-to-nics.rst -- material is obsolete and done
    better in other files now included in user-guide.
* The following files from pre-install/0051-network-plan/0100-netconfig-options are deleted:
  - 0100-netconfig-options (header/intro info no longer needed)
  - 0110- (info pulled into
  - 0200 - sourced files below it that are moved and sourced elsewhere

The same sections that discussed the topologies had information about
routers and switches.  I'm not exactly sure where the best place is
for this but, for now, I'm putting it in ref-arch right after the write-up
about Public and Floating IPs.  Alas, that is in a different commit, and
that other commit creates a sub-directory where these files should go.
So, for now, I created two files in the main ref-arch directory; I will
move these into the proper place after everything is merged.
* 6030-router is based on install-guide/0070-networks/350-router.rst,
  with content also pulled in from pre-install/0051-network-plan/topology/\
  0900-routing-req.rst.  I did some rewriting but the content is unchanged.
  This includes a bunch of Fuel screen shots that I think are superfluous
  but I need to compare them to the rewritten User Guide; I may need to do
  some moving or xref'ing of information.
* 6034-switch.rst is renamed from install-guide/0070-networks/
  300-switch-config.rst.  I did a bit of editing but the content is
  unchanged.
* I had to tag the files with sample switch configurations so I could
  link to them.  I also prefaced each of those titles with either "Nova-network"
  or "Neutron".
* After the above, the following files are deleted:
  * pre-install/0051-network-plan/topology/0900-routing-req (included in
    new routing document)
  * pre-install/0051-network-plan/0200-topology-include.rst -- included files
    that are deleted or moved
  * pre-install/0051-network-plan.rst -- included files that are deleted
    or moved

ref-arch/0030-cluster-sizing.rst is deleted; its content was pulled into
pre-install/nodes-roles.rst.  I added a bit of intro material; the substantive
content is unchanged.

pages/pre-install-guide/4000-plan0summary.rst was a bogus file; is deleted

At Patch 6, I deleted the screen shots from 0060-quick-start-instart-fuel;
this info doesn't belong here anyhow.  I also right-aligned the diagrams in
the Examples and fixed the header levels for the examples at the end of the
document.

Change-Id: Ia4e68200bea2166d48d7691f80cc921459a337ff
Merge "Update PXE boot documentation"
Set up User Guide

This guide has been ordered to have sections that parallel
  what is in the introductory table, with screen shots, instructions,
  and appropriate xrefs in the same order as the table

Moved info about mapping logical-to-physical NICS from pre-install
Moved info about configuring the PXE network before deploying environment
  from install-guide
Added information about booting node servers before deploying environment
Deleted some superfluous and illegible screen shots that are now replaced
  by material in user-guide
Added "Configure Hardware" from information that was in the pre-install
  "Prerequisites" table.

TODO(Meg McRoberts):
  - Modularize the sections about each task/screen into separate
    files
  - Rewrite the intro (as well as the intros for Pre-Install and Install
  - A couple of screen shots are missing
  - Add xrefs to sections in other docs for supporting information.

Closes-Bug: 1289668
Closes-Bug: 1308279

Change-Id: Ie717a0fafbf40272f603bab361046fa36457501a
Clean up User Guide mistakes and define Glance

Change-Id: I56e39910e9976661336850cb6a36e8e2adc3ee5e
Explain requirements for Public and Floating IPs

This was originally written up as https://review.openstack.org/#/c/87739/,

To accomodate this material, I bumped the Logical Networks section
down a level into a separate file and put that plus this material
into the network-concepts subfile, both under the "Networking Concepts"
top-level header.

I incorporated the comments that were given to the initial CM.

Closes-Bug: 1308161

Change-Id: Iefc2deff829b9823703f535d26b7bdcd857a5fbc
Updated link to 5.0 video

Change-Id: If47b59bdafb15024683b36e4423ffde1f4bcbd37
updating issues for 5.0

Completed information about new features and other enhancements from google doc version
Added entries for most LPs on Mike's list; made note in each LP. A couple LPs need
  clarification for me to write them; that is noted in LP.
Updated the ceilometer info in ops guide about database access
Added the pdf/pdf_relnotes.rst file

Release date is now set for 27 May.

Change-Id: Icc36b57348750789632533b3b63087f316c831aa
Merge "Updated link to 5.0 video"
Merge "Explain requirements for Public and Floating IPs"
Merge "updating issues for 5.0"
Fixes to 5.0 release notes

* Savanna renamed to Sahara
* 'Highly Available architecture can run with one controller' section
  was removed, along with information about controller nodes scale up
  due to unresolved Related-Bug #1312627
* Network verification can be started after deployment of Neutron
  enabled environment.
* We have network verification and validation, verification is
  performed actively by issuing udp frames or listening for dhcp
  replies, while validation is static mechanism to ensure that there
  no collisions in networking configuration
* 'deployment' replaced to 'provisioning' when we talk about OS
  bootstrapping
* RabbitMQ was temporarily issue and release-notes tag was put there
  likely by mistake
* ... few more minor fixes

Change-Id: If9d32d04b85fd34716fee40f5eafb59bc1ee673e
Update ceilometer info for Fuel 5.0

Change-Id: I832ade2d238e0bf7a3f3b50a2ba024763fcc2681
Replace intro material for Planning and User Guides

This replaces 94510

Changes for new intro:
- pre-install -- 0010-intro text is replaced with new material
- user-guide -- 0000-intro text is replaced with new material

- install-guide -- deleted 0000-intro-header and the contents of
  the 0000-intro subdirectory (they were deleted in 94510 because
  they are no longer needed)

This also pulls install-guide out of the build.  This is necessary
to make the 5.0 release and is not a permanent change so unused
files such as those in the contents/ and pdf/ directories have
not been removed:
- contents.rst
- index.rst
- install-guide.rst
- pdf/conf.py -- had to delete the install-guide line

Modified some top-level *.rst files trying to resolve build and
xref issues -- some of these tags had _ rather than - which causes
problems.

Change-Id: I9ab382034caf2ecb7aaa9c552d10552e97be89cf
Workaround for 2.6 kernel on bootstrap nodes.

Meg edited and checked links.

Change-Id: I25fdca02e9b55c247640a1e607b895cca1651162
Closes-Bug: #1323355
First pass of vCenter information

This includes the following pieces:
- Section in pre-installation about prerequisites and planning considerations
- Section in ref-arch that explains the vCenter implementation
- Section in user-guide with specific instructions
  for deploying MOS with vCenter integration.
- Section in operations about using vCenter
- Entries in terminology for major components

The pre-install guide is being restructured in a different CM; the
location of the vCenter information needs to be established in that
context.

The current ref-arch guide does not have a well-written and complete
section about hypervisors and how they fit into the "big picture". I
put the vcenter section in the general vicinity of other existing
material that will be part of that discussion.

The user-guide is being restructured in a different CM; the location of
the vCenter information needs to be established in that context.

The ops-guide is currently a somewhat random assemblage of information;
it will be structured better in a later release.  The vCenter section
may become a subsection of another larger section but this piece does
not currently exist.  It seems best to put vCenter in as a separate
section for now.

Change-Id: I55bc68e7910c29f31fecf79fb18bcaae23a17068
Merge "Fixes to 5.0 release notes"