diff --git a/conf.py b/conf.py index ad680d21b..1256e4c01 100644 --- a/conf.py +++ b/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. diff --git a/contents.rst b/contents.rst index 344cb3789..ef3c7f20a 100644 --- a/contents.rst +++ b/contents.rst @@ -1,10 +1,10 @@ .. index Documentation -.. _Documentation: +.. Documentation_: ============================= -Documentation +_Documentation ============================= .. toctree:: Documentation diff --git a/pages/frequently-asked-questions/0030-howtos.rst b/pages/frequently-asked-questions/0030-howtos.rst index b763bf457..b5d67af14 100644 --- a/pages/frequently-asked-questions/0030-howtos.rst +++ b/pages/frequently-asked-questions/0030-howtos.rst @@ -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) + (to accept the defaults) + (to accept the defaults) + w(to save changes) - fdisk /dev/sdb - n(for new) - p(for partition) - (to accept the defaults) - (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 diff --git a/pages/frequently-asked-questions/0040-corosync-crashes.rst b/pages/frequently-asked-questions/0040-corosync-crashes.rst index 1ad84ae5e..4b6cdc70c 100644 --- a/pages/frequently-asked-questions/0040-corosync-crashes.rst +++ b/pages/frequently-asked-questions/0040-corosync-crashes.rst @@ -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``. diff --git a/pages/frequently-asked-questions/0070-common-technical-issues.rst b/pages/frequently-asked-questions/0070-common-technical-issues.rst index 0951a6ce6..563a2aaf5 100644 --- a/pages/frequently-asked-questions/0070-common-technical-issues.rst +++ b/pages/frequently-asked-questions/0070-common-technical-issues.rst @@ -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 diff --git a/pages/frequently-asked-questions/0080-other-questions.rst b/pages/frequently-asked-questions/0080-other-questions.rst index 4954e0dec..4670b883d 100644 --- a/pages/frequently-asked-questions/0080-other-questions.rst +++ b/pages/frequently-asked-questions/0080-other-questions.rst @@ -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? diff --git a/pages/pre-install-guide/0030-pre-installation-checklist.rst b/pages/pre-install-guide/0030-pre-installation-checklist.rst index ab40f8181..af07024bf 100644 --- a/pages/pre-install-guide/0030-pre-installation-checklist.rst +++ b/pages/pre-install-guide/0030-pre-installation-checklist.rst @@ -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. diff --git a/pages/pre-install-guide/0090-appendix.rst b/pages/pre-install-guide/0090-appendix.rst index 1c2fc03c8..e853fce35 100644 --- a/pages/pre-install-guide/0090-appendix.rst +++ b/pages/pre-install-guide/0090-appendix.rst @@ -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) diff --git a/pages/reference-architecture/0020-logical-setup.rst b/pages/reference-architecture/0020-logical-setup.rst index 53826c867..b72ef0ce4 100644 --- a/pages/reference-architecture/0020-logical-setup.rst +++ b/pages/reference-architecture/0020-logical-setup.rst @@ -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 diff --git a/pages/user-guide/custom-attributes.rst b/pages/user-guide/custom-attributes.rst index 676be7f72..e3bb7363a 100644 --- a/pages/user-guide/custom-attributes.rst +++ b/pages/user-guide/custom-attributes.rst @@ -58,6 +58,7 @@ structure::: packages/manifests/init.pp **init.pp** should have this content::: + class profile { $tools = $::fuel_settings['tools'] package { $tools : diff --git a/pages/user-guide/post-install-healthchecks.rst b/pages/user-guide/post-install-healthchecks.rst index 2c287d3af..3e96515c9 100644 --- a/pages/user-guide/post-install-healthchecks.rst +++ b/pages/user-guide/post-install-healthchecks.rst @@ -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 `_ + See `Murano documentation (Image Builder) `_ 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.