Fixed build warnings
This commit is contained in:
Ivan Kolodyazhny
Ivan Kolodyazhny
parent
4ec2c7e436
commit
3f631bd543
2
conf.py
2
conf.py
|
|
@ -75,7 +75,7 @@ release = '3.2'
|
|||
|
||||
# List of patterns, relative to source directory, that match files and
|
||||
# directories to ignore when looking for source files.
|
||||
exclude_patterns = ['_*', "pages", 'relnotes', 'contents',]
|
||||
exclude_patterns = ['_*', "pages", 'relnotes', 'contents', 'pdf_*']
|
||||
# exclude_patterns = ['_*', 'rn_index.rst']
|
||||
|
||||
# The reST default role (used for this markup: `text`) to use for all documents.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
.. index Documentation
|
||||
|
||||
|
||||
.. _Documentation:
|
||||
.. Documentation_:
|
||||
|
||||
=============================
|
||||
Documentation
|
||||
_Documentation
|
||||
=============================
|
||||
|
||||
.. toctree:: Documentation
|
||||
|
|
|
|||
|
|
@ -19,33 +19,34 @@ need to create it yourself, use this procedure:
|
|||
configure.
|
||||
|
||||
1. Create the partition itself
|
||||
::
|
||||
::
|
||||
|
||||
fdisk /dev/sdb
|
||||
n(for new)
|
||||
p(for partition)
|
||||
<enter> (to accept the defaults)
|
||||
<enter> (to accept the defaults)
|
||||
w(to save changes)
|
||||
|
||||
fdisk /dev/sdb
|
||||
n(for new)
|
||||
p(for partition)
|
||||
<enter> (to accept the defaults)
|
||||
<enter> (to accept the defaults)
|
||||
w(to save changes)
|
||||
|
||||
2. Initialize the XFS partition
|
||||
::
|
||||
::
|
||||
|
||||
mkfs.xfs -i size=1024 -f /dev/sdb1
|
||||
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
|
||||
::
|
||||
::
|
||||
|
||||
mkdir -p /srv/node/sdb1
|
||||
mkdir -p /srv/node/sdb1
|
||||
|
||||
4. Finally, add the new partition to fstab so it mounts automatically, then
|
||||
mount all current partitions
|
||||
::
|
||||
::
|
||||
|
||||
echo "/dev/sdb1 /srv/node/sdb1 xfs
|
||||
noatime,nodiratime,nobarrier,logbufs=8 0 0" >> /etc/fstab
|
||||
mount -a
|
||||
echo "/dev/sdb1 /srv/node/sdb1 xfs
|
||||
noatime,nodiratime,nobarrier,logbufs=8 0 0" >> /etc/fstab
|
||||
mount -a
|
||||
|
||||
|
||||
.. index:: HowTo: Redeploy a node from scratch
|
||||
|
|
|
|||
|
|
@ -11,9 +11,10 @@ through Corosync with MySQL issues.
|
|||
|
||||
1. Verify that corosync is really broken ``service corosync status``.
|
||||
|
||||
* You should see next error::
|
||||
* You should see next error
|
||||
::
|
||||
|
||||
corosync dead but pid file exists
|
||||
corosync dead but pid file exists
|
||||
|
||||
2. Start corosync manually ``service corosync start``.
|
||||
|
||||
|
|
|
|||
|
|
@ -32,13 +32,13 @@ This is a Puppet bug. See: http://projects.puppetlabs.com/issues/4680
|
|||
* On Puppet client
|
||||
::
|
||||
|
||||
rm -f /etc/puppet/ssl/certificate_requests/\*.pem
|
||||
rm -f /etc/puppet/ssl/certs/\*.pem
|
||||
rm -f /etc/puppet/ssl/certificate_requests/\*.pem
|
||||
rm -f /etc/puppet/ssl/certs/\*.pem
|
||||
|
||||
* On Puppet master
|
||||
::
|
||||
|
||||
rm -f /var/lib/puppet/ssl/ca/requests/\*.pem
|
||||
rm -f /var/lib/puppet/ssl/ca/requests/\*.pem
|
||||
|
||||
**Issue:**
|
||||
The manifests are up-to-date under ``/etc/puppet/manifests``, but Puppet
|
||||
|
|
|
|||
|
|
@ -6,6 +6,7 @@ Other Questions
|
|||
===============
|
||||
|
||||
.. TODO(mihgen): Provide more clear and reflecting reality answer
|
||||
|
||||
1. **[Q]** Why did you decide to provide OpenStack packages through your own
|
||||
repository?
|
||||
|
||||
|
|
|
|||
|
|
@ -49,8 +49,7 @@ a successful deployment.
|
|||
| the Fuel server from your PC). | |
|
||||
+--------------------------------------------------------+--------------+
|
||||
|
||||
.. note:: * You need tagged ports in order to use Nova-network VLAN Manager or
|
||||
Neutron with VLAN segmentation.
|
||||
.. note:: * You need tagged ports in order to use Nova-network VLAN Manager or Neutron with VLAN segmentation.
|
||||
|
||||
If you checked all the boxes in the above table, you are ready to deploy
|
||||
Mirantis OpenStack with Fuel.
|
||||
|
|
|
|||
|
|
@ -44,8 +44,8 @@ As a model example, the following configuration is used:
|
|||
From the server node side, ports with the following VLAN IDs for
|
||||
networks are used:
|
||||
|
||||
* eth0 - Management VLAN 101 (tagged), Storage VLAN 102(tagged) and
|
||||
Administrative VLAN 104 (untagged)
|
||||
* eth0 - Management VLAN 101 (tagged), Storage VLAN 102(tagged) and Administrative VLAN 104 (untagged)
|
||||
|
||||
* eth1 - Public/Floating VLAN 100 (tagged), Private VLAN 103 (tagged)
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ You must keep in mind, however, that the database uses Galera to
|
|||
achieve HA, and Galera is a quorum-based system. That means that you must provide
|
||||
at least 3 controller nodes.
|
||||
|
||||
.. image:: /_images/logical-diagram-controller_svg.jpg
|
||||
.. image:: /_images/logical-diagram-controller.svg
|
||||
:align: center
|
||||
|
||||
Every OpenStack controller runs HAProxy, which manages a single External
|
||||
|
|
|
|||
|
|
@ -58,6 +58,7 @@ structure:::
|
|||
packages/manifests/init.pp
|
||||
|
||||
**init.pp** should have this content:::
|
||||
|
||||
class profile {
|
||||
$tools = $::fuel_settings['tools']
|
||||
package { $tools :
|
||||
|
|
|
|||
|
|
@ -247,7 +247,7 @@ To prepare Murano for testing:
|
|||
|
||||
1. Configure key pair 'murano-lb-key' in the 'admin' tenant.
|
||||
2. Create a Windows image with Murano agent.
|
||||
See `Murano documentation <http://murano-docs.github.io/latest/administrators-guide/content/ch03.html>`_
|
||||
See `Murano documentation (Image Builder) <http://murano-docs.github.io/latest/administrators-guide/content/ch03.html>`_
|
||||
3. Upload the image to the OpenStack Image Service (Glance) into the 'admin' tenant.
|
||||
4. Rename the image name to 'ws-2012-std'.
|
||||
5. In the OpenStack Dashboard, click the 'Project' tab.
|
||||
|
|
|
|||
Loading…
Reference in New Issue