Adventures of a Small Time OpenStack Sysadmin relate the experience of converting a small VMware cluster into two small OpenStack clusters, and the adventures and friends I made along the way.
Adventures of a Small Time OpenStack Sysadmin Chapter 046 - Skydive
Around this time, during the Plan 2.0 era, I stopped doing OpenStack directly, and wandered off on a monitoring expedition, because I need a way to troubleshoot broken clusters and one of the primary troubleshooting tools is, well, troubleshooting tools, such as Skydive, Zabbix, Prometheus / Grafana, and later on in the Plan 3.0 era I provisioned an ELK stack (its a bit resource hungry, or can be anyway, so I waited until I had more resources in Plan 3.0).
There is not much to this "Skydive" post because its trivial to set up and easy to use.
First, links to some reference docs I used:
Kolla-Ansible Project Deployment Configuration Reference (PDCR) for Skydive
https://docs.openstack.org/kolla-ansible/yoga/reference/logging-and-monitoring/skydive-guide.html
Skydive Project repo
https://github.com/skydive-project/skydive/
Installation Notes:
Add one line, and deploy as usual:
enable_skydive: "yes"
As seen at this link:
The default login seems to be the Horizon Web UI password. I don't see an alternative password for Skydive in my /etc/kolla/passwords.yml file.
Skydive works immediately out of the box and is visually stunning.
Skydive integrates with Kolla-Ansible in the sense that it "just works" out of the box upon installation, but it does not "deep integrate" with OpenStack in the sense that instead of displaying OpenStack names for components, the names are all UUID-type internal designators. Very much like the experience of Zabbix monitoring.
Tomorrow, a MUCH longer post on Zabbix.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.