Merge pull request #69 from e0ne/build-warnings

Fix build errors
This commit is contained in:
Mike Scherbakov 2013-11-20 01:25:56 -08:00
commit 4ec2c7e436
6 changed files with 41 additions and 41 deletions

View File

@ -18,7 +18,8 @@ need to create it yourself, use this procedure:
.. note:: Replace ``/dev/sdb`` with the appropriate block device you wish to
configure.
1. Create the partition itself::
1. Create the partition itself
::
fdisk /dev/sdb
n(for new)
@ -27,17 +28,20 @@ need to create it yourself, use this procedure:
<enter> (to accept the defaults)
w(to save changes)
2. Initialize the XFS partition::
2. Initialize the XFS partition
::
mkfs.xfs -i size=1024 -f /dev/sdb1
3. For a standard swift install, all data drives are mounted directly under
/srv/node, so first create the mount point::
/srv/node, so first create the mount point
::
mkdir -p /srv/node/sdb1
4. Finally, add the new partition to fstab so it mounts automatically, then
mount all current partitions::
mount all current partitions
::
echo "/dev/sdb1 /srv/node/sdb1 xfs
noatime,nodiratime,nobarrier,logbufs=8 0 0" >> /etc/fstab

View File

@ -29,12 +29,14 @@ This is a Puppet bug. See: http://projects.puppetlabs.com/issues/4680
**Workaround:**
* On Puppet client::
* On Puppet client
::
rm -f /etc/puppet/ssl/certificate_requests/\*.pem
rm -f /etc/puppet/ssl/certs/\*.pem
* On Puppet master::
* On Puppet master
::
rm -f /var/lib/puppet/ssl/ca/requests/\*.pem

View File

@ -60,8 +60,6 @@ installing OpenStack.
VirtualBox
----------
.. OpenStack-3.2-ReferenceArchitecture::
If you would like to evaluate Fuel on VirtualBox, you can take advantage of the
included set of scripts that create and configure all the required VMs for a
test environment, including the Master node and Slave nodes for OpenStack

View File

@ -326,23 +326,19 @@ network:
- The Storage and VM networks should be configured without access to
other networks (no L3 connectivity)
.. |image89| image:: /_images/image04.jpg
.. |image9| image:: /_images/image04.jpg
.. |image10| image:: /_images/image12.jpg
.. |image11| image:: /_images/image22.png
.. |image12| image:: /_images/image10.png
.. |image13| image:: /_images/image03.png
.. |image14| image:: /_images/image18.png
.. |image15| image:: /_images/image19.png
.. |image16| image:: /_images/image00.png
.. |image17| image:: /_images/image08.png
.. |image18| image:: /_images/image04.jpg
.. |image19| image:: /_images/image06.jpg
.. |image20| image:: /_images/image22.png
.. |image21| image:: /_images/image10.png
.. |image22| image:: /_images/image03.png
.. |image23| image:: /_images/image14.png
.. |image24| image:: /_images/image02.png
.. |image25| image:: /_images/image19.png
.. |image26| image:: /_images/image17.png
.. |image27| image:: /_images/image07.png
.. image:: /_images/image22.png
.. image:: /_images/image10.png
.. image:: /_images/image03.png
.. image:: /_images/image18.png
.. image:: /_images/image19.png
.. image:: /_images/image00.png
.. image:: /_images/image08.png
.. image:: /_images/image06.jpg
.. image:: /_images/image22.png
.. image:: /_images/image10.png
.. image:: /_images/image03.png
.. image:: /_images/image14.png
.. image:: /_images/image02.png
.. image:: /_images/image19.png
.. image:: /_images/image17.png
.. image:: /_images/image07.png

View File

@ -94,18 +94,18 @@ like this:
The most likely configuration for different number NICs on cluster nodes:
+------+----------------------------------------+----------------------------------------+
| NICs | VLAN | GRE |
+======+========================================+========================================+
| 2 | Not supported | .. image:: /_images/q32_gre_2nic.svg |
| | | :align: center |
+------+----------------------------------------+----------------------------------------+
| 3 | .. image:: /_images/q32_vlan_3nic.svg | .. image:: /_images/q32_gre_3nic.svg |
| | :align: center | :align: center |
+------+----------------------------------------+----------------------------------------+
| 4 | .. image:: /_images/q32_vlan_4nic.svg | .. image:: /_images/q32_gre_4nic.svg |
| | :align: center | :align: center |
+------+----------------------------------------+----------------------------------------+
+------+--------------------------------------------+--------------------------------------------+
| NICs | VLAN | GRE |
+======+============================================+============================================+
| 2 | Not supported | .. image:: /_images/q32_gre_2nic_svg.jpg |
| | | :align: center |
+------+--------------------------------------------+--------------------------------------------+
| 3 | .. image:: /_images/q32_vlan_3nic_svg.jpg | .. image:: /_images/q32_gre_3nic_svg.jpg |
| | :align: center | :align: center |
+------+--------------------------------------------+--------------------------------------------+
| 4 | .. image:: /_images/q32_vlan_4nic_svg.jpg | .. image:: /_images/q32_gre_4nic_svg.jpg |
| | :align: center | :align: center |
+------+--------------------------------------------+--------------------------------------------+
Known limitations

View File

@ -648,7 +648,7 @@ Known issues
volumes at the same time using some batch script.
*Redesign rc-scripts for quantum-<...>-agent*
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Neutron OVS agent drops all virtual networks and related settings on compute node after
manual restart. Normally it is managed by Controller and get all settings from it.