Stein Series Release Notes



Added new tool masakari-status upgrade check.

New Features

  • New framework for masakari-status upgrade check command is added. This framework allows adding various checks which can be run before a Masakari upgrade to ensure if the upgrade can be performed safely.

  • Added support to emit event notifications whenever user interacts with Masakari restFul APIs. The emitted notifications are documented at sample_payloads.

    To enable this feature one should set driver config option under the oslo_messaging_notifications section as shown below:

    driver = log

    Note: Possible values are messaging, messagingv2, routing, log, test, noop. Notifications can be completely disabled by setting driver value as noop

  • Added support to record the recovery workflow details of the notification which will be returned in a new microversion 1.1 in GET /notifications/{notification_id} API.

    For example, GET /notifications/<notification_uuid> response will contain recovery_workflow_details parameter as shown here notification_details

    Added a new config section in Masakari conf file for configuring the back end to be used by taskflow driver:

    # The back end for storing recovery_workflow details of the notification.
    # (string value)
    connection = mysql+pymysql://root:admin@<db name>?charset=utf8
    # Where db_name, can be a new database or you can also specify masakari
    # database.

    Operator should run masakari-manage db sync command to add new db tables required for storing recovery_workflow_details.

    Note: When you run masakari-manage db sync, make sure you have notification_driver=taskflow_driver set in masakari.conf.

Upgrade Notes

  • Operator can now use new CLI tool masakari-status upgrade check to check if Masakari deployment can be safely upgraded from N-1 to N release.