0

So far, based on my understanding of OpenStack Python SDK, I am able to read the Hypervisor, Servers instances, however, I do not see an API to receive and handle the change notification/events for the operations that happens on the cluster e.g. A new VM is added, an existing VM is deleted etc.

There is a similar old post (circa 2016) and I am curious if there have been any changes in Notification handling? Notifications to external systems from openstack

I see a documentation, which talks about emitting notifications over a message bus that indicate different events that occur within the service.

https://docs.openstack.org/ironic/latest/admin/notifications.html

I have the following questions:

Does Openstack Python SDK support notification APIs?
How do I receive/monitor notifications for VM related changes?
How do I receive/monitor notifications for compute/hypervisor related changes?
How do I receive/monitor notifications for Virtual Switch related changes?

I see other posts such as Notifications in openstack and they recommend to use Ceilometer project, which uses a Database. Is there more light-weight solution than using a completely different service like Ceilometer?

Thanks in advance for your help in this regard.

AnilJ
  • 1,951
  • 2
  • 33
  • 60

2 Answers2

1

As far as I see and I know, Openstack SDK doesn't provide such a function.

Ceilometer will also not help you. It only collects data by polling and by notifications over RPC. You would still have to poll the data from ceilometer by yourself. Beside this, ceilometer alone has the problem, that it only grow and will blow up your database, that's why you should also use gnocchi, when you use ceilometer.

At the moment I see only the 3 possible solutions for you:

  1. Write your own tool, which runs permanently in the background and collect the data in a regular interval over OpenstackSDK and REST-API requests.

  2. Write something, which does the same like ceilometer by reciving notifications over oslo-messaging (RPC). See the oslo_messaging_notifications-section in the configs: https://docs.openstack.org/ocata/config-reference/compute/config-options.html#id35 (neutron has also such an option) and use messagingv2 as driver like ceilometer does. But be aware here, that not every event creates a notification. The list of the ceilometer meter-data should give a good overview of which event are creating a notification and what can only be collected by polling: https://docs.openstack.org/ceilometer/pike/admin/telemetry-measurements.html. The number of notification-events is really low, so its possible, that it doesn't provides all events you want.

  3. Use in the oslo_messaging_notifications-section in the configs log as driver to write the notification in a log-file, and write a simple program to read the log-file and process or forward the read content. Here is the same problem like in number 2, that not every event creates a notification (log-entry in this case here). This has also the problem, that the notifications and so also the event-logs, are created on the compute-nodes (as far as I know) and so you would have to watch all compute-nodes by your tool.

Based on the fact, that I don't know, how much work it would be to write a tool to collect notifications over RPC and because I don't know, if all events you want to watch really creates a notification (base on the overview here: https://docs.openstack.org/ceilometer/pike/admin/telemetry-measurements.html), I would prefer number 1.

Its the easiest way to create a tool, which runs GET-Requests over REST-API in a regular interval and forward the results to the desired destination as your own custom notifications.

Tobias
  • 543
  • 1
  • 3
  • 15
  • Would you be able to provide an exact example of config file changes if I have to receive notifications from Nova service? I understand that in nova.conf, we need to change "username/pass in the transport_url" as well as in "rabbitmq cluster" config. – AnilJ Jul 10 '20 at 17:35
  • I'm very sorry, but I'm not able to provide you an exact example. :( But, as far as I unterstand it, you only have to set the `driver` the nova.conf. The `transport_url` only have to be used, when you want to use a different RabbitMQ-cluster for the notification. Normally it seems like you "only" have to connect to the rabbitmq-cluster to receive notifications and listen to the correct rabbitmq-queues. Here ceilometer register all its notifications in this loop here: https://github.com/openstack/ceilometer/blob/master/ceilometer/notification.py#L136 Maybe this help you. – Tobias Jul 11 '20 at 09:22
1

I followed the below references to get this working. Also, chatted with the author of this code and video.

https://github.com/gibizer/nova-notification-demo/blob/master/ws_forwarder.py
https://www.youtube.com/watch?v=WFq5JWXa9AM

In addition, I faced other issues:

  • By default, OpenStack server would not allow you to connect to RabbitMQ bus from remote host because of an IPTABLE rule. You will have to enable access to the RabbitMQ Port in the IP table.
AnilJ
  • 1,951
  • 2
  • 33
  • 60