Adjust documentation for PDF
This change wraps lines when needed and tunes the configuration for PDF
generation.
Change-Id: Ia483681e196aea4c6e291231131ab0447a586aef
(cherry picked from commit 45fcf4ff2a
)
This commit is contained in:
parent
3d3c6f9ccd
commit
afb2dfaa27
|
@ -261,3 +261,8 @@ texinfo_documents = [
|
||||||
|
|
||||||
# If true, do not generate a @detailmenu in the "Top" node's menu.
|
# If true, do not generate a @detailmenu in the "Top" node's menu.
|
||||||
#texinfo_no_detailmenu = False
|
#texinfo_no_detailmenu = False
|
||||||
|
|
||||||
|
# make latex stop printing blank pages between sections
|
||||||
|
# http://stackoverflow.com/questions/5422997/sphinx-docs-remove-blank-pages-from-generated-pdfs
|
||||||
|
latex_elements = {'classoptions': ',openany,oneside', 'babel':
|
||||||
|
'\\usepackage[english]{babel}'}
|
||||||
|
|
|
@ -55,7 +55,9 @@ For instance, lets take the following Heka message::
|
||||||
:Pid: 15595
|
:Pid: 15595
|
||||||
:Uuid: e67f91c5-259b-489f-adfa-8eea0b389eb2
|
:Uuid: e67f91c5-259b-489f-adfa-8eea0b389eb2
|
||||||
:Logger: collectd
|
:Logger: collectd
|
||||||
:Payload: {"type":"cpu","values":[0],"type_instance":"idle","dsnames":["value"],"plugin":"cpu","time":1442333737.646,"interval":10,"host":"node-1","dstypes":["derive"],"plugin_instance":"0"}
|
:Payload: {"type":"cpu","values":[0],"type_instance":"idle","dsnames":["value"],
|
||||||
|
"plugin":"cpu","time":1442333737.646,"interval":10,"host":"node-1",
|
||||||
|
"dstypes":["derive"],"plugin_instance":"0"}
|
||||||
:EnvVersion:
|
:EnvVersion:
|
||||||
:Severity: 6
|
:Severity: 6
|
||||||
:Fields:
|
:Fields:
|
||||||
|
|
|
@ -387,7 +387,8 @@ defines the default status in case none of the previous rules could be matched.
|
||||||
|
|
||||||
A policy rule is defined as shown in the example below::
|
A policy rule is defined as shown in the example below::
|
||||||
|
|
||||||
# The following rule definition reads as: "the cluster's status is critical if more than 50% of its members are either down or criticial"
|
# The following rule definition reads as: "the cluster's status is critical
|
||||||
|
# if more than 50% of its members are either down or criticial"
|
||||||
- status: critical
|
- status: critical
|
||||||
trigger:
|
trigger:
|
||||||
logical_operator: or
|
logical_operator: or
|
||||||
|
|
|
@ -30,7 +30,8 @@ Catalog, you need to follow these steps:
|
||||||
|
|
||||||
2. Copy the RPM file to the Fuel Master node::
|
2. Copy the RPM file to the Fuel Master node::
|
||||||
|
|
||||||
[root@home ~]# scp lma_collector-0.8-0.8.0-1.noarch.rpm root@<Fuel Master node IP address>:
|
[root@home ~]# scp lma_collector-0.8-0.8.0-1.noarch.rpm \
|
||||||
|
root@<Fuel Master node IP address>:
|
||||||
|
|
||||||
3. Install the plugin using the `Fuel CLI <http://docs.mirantis.com/openstack/fuel/fuel-7.0/user-guide.html#using-fuel-cli>`_::
|
3. Install the plugin using the `Fuel CLI <http://docs.mirantis.com/openstack/fuel/fuel-7.0/user-guide.html#using-fuel-cli>`_::
|
||||||
|
|
||||||
|
@ -91,4 +92,4 @@ if you need further instructions about how to build the Fuel Plugin Builder.
|
||||||
|
|
||||||
7. Now that you have created the RPM file, you can install the plugin using the `fuel plugins --install` command::
|
7. Now that you have created the RPM file, you can install the plugin using the `fuel plugins --install` command::
|
||||||
|
|
||||||
[root@fuel ~] fuel plugins --install ./fuel-plugin-lma_collector/lma_collector-0.8-0.8.0-1.noarch.rpm
|
[root@fuel ~] fuel plugins --install ./fuel-plugin-lma_collector/*.noarch.rpm
|
||||||
|
|
Loading…
Reference in New Issue