Update osprofiler rst

Add two missed period.
Change one sentence to help read.

Change-Id: I82f6b1d2175ff60633ac1b90fd84bb1c2803490e
This commit is contained in:
yufei 2018-01-17 16:33:54 +08:00
parent 8727c1a0b3
commit f527619ad5

View File

@ -30,7 +30,7 @@ option without using ceilometer. Here just use Redis as an example, user
can choose mongodb, elasticsearch, and `etc can choose mongodb, elasticsearch, and `etc
<https://git.openstack.org/cgit/openstack/osprofiler/tree/osprofiler/drivers>`_. <https://git.openstack.org/cgit/openstack/osprofiler/tree/osprofiler/drivers>`_.
Install Redis as the `centralized collector Install Redis as the `centralized collector
<https://docs.openstack.org/osprofiler/latest/user/collectors.html>`_ <https://docs.openstack.org/osprofiler/latest/user/collectors.html>`_.
Redis in container is easy to launch, `choose Redis Docker Redis in container is easy to launch, `choose Redis Docker
<https://hub.docker.com/_/redis/>`_ and run:: <https://hub.docker.com/_/redis/>`_ and run::
@ -53,7 +53,7 @@ to the real IP::
Then restart zun-api and zun-compute (Attention, the newest version of Then restart zun-api and zun-compute (Attention, the newest version of
Zun has move zun-api service to apache2 server. You can't restart the Zun has move zun-api service to apache2 server. You can't restart the
service just in screen. Use "systemctl restart apache2" will work) service just in screen. Use "systemctl restart apache2" will work).
Use below commands to get the trace information:: Use below commands to get the trace information::
@ -73,5 +73,5 @@ Stop the Redis container, then run the command::
In the zun-api log, will see "ConnectionError: Error 111 connecting to In the zun-api log, will see "ConnectionError: Error 111 connecting to
<ip-address>:6379. ECONNREFUSED." That means that osprofiler will write <ip-address>:6379. ECONNREFUSED." That means that osprofiler will write
the trace data to redis, but can't connect it. So the integration is fine. the trace data to redis, but can't connect it. So the integration is fine.
/etc/zun/api-paste.ini file changed (change the pipeline) need to re-deploy When /etc/zun/api-paste.ini file changed (change the pipeline), you need to
the devstack. re-deploy the zun service.