Rocky Series Release Notes

6.0.0

New Features

  • Masakari has been enabled for mutable config. Below option may be reloaded by sending SIGHUP to the correct process.

    ‘retry_notification_new_status_interval’ option will apply to process unfinished notifications.

  • Operators can now purge the soft-deleted records from the database tables. Added below command to purge the records:

    masakari-manage db purge --age_in_days <days> --max_rows <rows>

    NOTE: notifications db records will be purged on the basis of update_at and status fields (finished, ignored, failed) as these records will not be automatically soft-deleted by the system.

  • Masakari now support policy in code, which means if operators doesn’t need to modify any of the default policy rules, they do not need a policy file. Operators can modify/generate a policy.yaml.sample file which will override specific policy rules from their defaults.

    Masakari is now configured to work with two oslo.policy CLI scripts that have been added:

    • The first of these can be called like oslopolicy-list-redundant --namespace masakari and will output a list of policy rules in policy.[json|yaml] that match the project defaults. These rules can be removed from the policy file as they have no effect there.
    • The second script can be called like oslopolicy-policy-generator --namespace masakari --output-file policy-merged.yaml and will populate the policy-merged.yaml file with the effective policy. This is the merged results of project defaults and config file overrides.

    NOTE: Default policy.json file is now removed as Masakari now uses default policies. A policy file is only needed if overriding one of the defaults.

  • Operator can now customize workflows to process each type of failure notifications (hosts, instance and process) as per their requirements. Added below new config section for customized recovery flow in a new conf file masakari-custom-recovery-methods.conf

    • [taskflow_driver_recovery_flows]

    Under [taskflow_driver_recovery_flows] is added below five new config options

    • ‘instance_failure_recovery_tasks’ is a dict of tasks which will recover instance failure.
    • ‘process_failure_recovery_tasks’ is a dict of tasks which will recover process failure.
    • ‘host_auto_failure_recovery_tasks’ is a dict of tasks which will recover host failure for auto recovery.
    • ‘host_rh_failure_recovery_tasks’ is a dict of tasks which will recover host failure for rh recovery on failure host.

Upgrade Notes

  • WSGI application script masakari-wsgi is now available. It allows running the masakari APIs using a WSGI server of choice (for example nginx and uwsgi, apache2 with mod_proxy_uwsgi or gunicorn). The eventlet-based servers are still available, but the WSGI options will allow greater deployment flexibility.