In Pike OpenStack documentation is changed in a way that the project repos contain most of the documentation material [1]. This affcects how the doc folder shall be strucutred inside the project repo. With this change I align the install guide to the new structure and correct the warnings during the document generation. The overall work is tracked in [2]. [1]: http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html [2]: https://etherpad.openstack.org/p/doc-migration-tracking Change-Id: Ib5400247d2ba5f8dac80ef68a43d06868bd42f1c Depends-On: Ia750cb049c0f53a234ea70ce1f2bbbb7a2aa9454 Signed-off-by: csatari <gergely.csatari@nokia.com>
5.2 KiB
Install and configure for Red Hat Enterprise Linux and CentOS
This section describes how to install and configure the Root Cause Analysis service for Red Hat Enterprise Linux 7 and CentOS 7.
Manual
Install Vitrage
Install Vitrage and python-vitrageclient
- Install Vitrage:
$ sudo pip install vitrage
$ sudo pip install python-vitrageclient
To install a specific version, add the version number:
$ sudo pip install vitrage==VITRAGE_VERSION
$ sudo pip install python-vitrageclient==VITRAGE_CLIENT_VERSION
Release version | Vitrage version | Client version |
---|---|---|
Ocata | 1.5.1 | 1.1.1 |
Pike | ... | ... |
Configure Vitrage
Create the Vitrage folders
- Create /etc/vitrage folder and sub folders, with permission 755:
$ mkdir /etc/vitrage
$ chmod 755 /etc/vitrage
$ mkdir /etc/vitrage/static_datasources
$ chmod 755 /etc/vitrage/static_datasources
$ mkdir /etc/vitrage/templates
$ chmod 755 /etc/vitrage/templates
$ sudo mkdir /var/log/vitrage
$ sudo chmod 755 /var/log/vitrage
Copy policy.json to /etc/vitrage/
Copy api-paste.ini to /etc/vitrage/
Copy the datasources_values folder with its content
Note: You don't need to copy all files in this folder, only the ones that belong to datasources you plan to use. The only file that must be copied is vitrage.yaml
Create the vitrage.conf file
Create /etc/vitrage/vitrage.conf file with the following information:
[DEFAULT]
# debug = False
transport_url = <transport-url>
# notifiers = nova
[service_credentials]
auth_url = http://<ip>:5000
region_name = RegionOne
project_name = admin
password = <password>
project_domain_id = default
user_domain_id = default
username = admin
auth_type = password
[keystone_authtoken]
auth_uri = http://<ip>:5000
project_domain_name = Default
project_name = service
user_domain_name = Default
password = <password>
username = vitrage
auth_url = http://<ip>:35357
auth_type = password
Set the list of datasource you would like to use for Vitrage.
Note: In order for a datasource to be supported, the underlying component (like Neutron, Heat, Zabbix, etc.) should be installed separately.
[datasources]
types = nova.host,nova.instance,nova.zone,static,aodh,cinder.volume,neutron.network,neutron.port,heat.stack,doctor
Configure notifications from other datasources
Notifications from Aodh
In order to configure notifications from Aodh to Vitrage, set the following in `/etc/aodh/aodh.conf`:
[oslo_messaging_notifications]
driver = messagingv2
topics = notifications,vitrage_notifications
Notifications from other OpenStack components
In order to configure notifications from OpenStack components (Nova, Cinder, Neutron, Heat and Aodh) to Vitrage, set the following in their conf files:
[DEFAULT]
notification_topics = notifications,vitrage_notifications
notification_driver=messagingv2
Initialize Vitrage
Create the Vitrage account
openstack user create vitrage --password password --domain=Default
openstack role add admin --user vitrage --project service
openstack role add admin --user vitrage --project admin
Create the Vitrage endpoint
openstack service create rca --name vitrage --description="Root Cause Analysis Service"
openstack endpoint create --region <region> --publicurl http://<ip>:8999 --internalurl http://<ip>:8999 --adminurl http://<ip>:8999 vitrage
Start the Vitrage Services
Run the following commands:
vitrage-graph
vitrage-api
vitrage-notifier
Install the Vitrage Dashboard
Follow the vitrage-dashboard installation procedure.
Automatic
Automatic installation for RDO is in progress; the patch can be found on the RDO Gerrit