openstack
/
searchlight-specs
Code Issues Proposed changes
searchlight-specs/specs/ocata/ironic-plugin.rst

2.3 KiB
Raw Blame History

Ironic plugin

https://blueprints.launchpad.net/searchlight/+spec/ironic-plugin

This spec is proposed to add ironic plugin for Searchlight. Ironic is OpenStack baremetal service. Plugin should support these baremetal resourses: nodes (OS::Ironic::Node), ports (OS::Ironic::Port) and chassis (OS::Ironic::Chassis).

Problem Description

Notifications about baremetal node state changes (power, provisioning) and create, update and delete of resources are proposed to ironic (1,2). Because information about node in the database can be changed quickly during deployment specification3 provides ways to limits flow of notifications. Using of Searchlight API with ironic plugin can reduce load on ironic API from periodical polling tasks.

Proposed Change

1. Searchlight listener should be changed because ironic can use any notifications message priority, not only INFO (4). For possibility of use this feature and backward compatibility new configuration option (list type) additional_priorities will be added to listener group. Allowed values are "audit", "debug", "warn", "error", "critical" and "sample". Default value is not set (no additional priorities).

2. Plugin with indexers and notification handlers for ironic nodes, ports and chassis shoud be implemented.

3. Custom Searchlight config should be used with ironic because ironic uses own hardcoded ironic_versioned_notifications topic (5).

Alternatives

None

References

  1. http://specs.openstack.org/openstack/ironic-specs/specs/approved/notifications.html↩︎

  2. https://review.openstack.org/#/c/347242↩︎

  3. https://review.openstack.org/#/c/347242↩︎

  4. http://specs.openstack.org/openstack/ironic-specs/specs/approved/notifications.html↩︎

  5. http://docs.openstack.org/developer/ironic/dev/notifications.html↩︎