post-update

openstack-endpoints

Check connectivity to various OpenStack services.

This validation gets the PublicVip address from the deployment and tries to access Horizon and get a Keystone token.

• hosts: undercloud

• groups: post-deployment, pre-upgrade, post-upgrade, pre-update, post-update

• parameters:

• roles: openstack_endpoints

Role documentation

• openstack_endpoints
  • Role Documentation
    • Role Variables: main.yml
    • Molecule Scenarios
      • Scenario: default
        • Example default configuration
        • Molecule Inventory
        • Example default playbook

oslo-config-validator

Openstack services configuration validation.

This role is intended to leverage the oslo-config-validator on each one of the configuration files found on a deployment. The goal is to quickly catch erroneous configurations.

When called manually, it will also be possible to generate a report returning all the differences between the current configuration and the default configuration

• hosts: all

• groups: post-deployment, post-system-upgrade, post-update, post-upgrade

• parameters:

  • oslo_config_validator_debug: False

  • oslo_config_validator_report: False

  • oslo_config_validator_validation: True

  • oslo_config_validator_invalid_settings: True

  • oslo_config_validator_report_path: /var/tmp/config_validator_report

  • oslo_config_validator_report_archive: True

  • oslo_config_validator_work_path: /var/lib/tripleo-config/oslo_config_validator

  • oslo_config_validator_checked_services: [‘nova’, ‘cinder’, ‘glance’, ‘heat’, ‘ironic’, ‘placement’, ‘neutron’, ‘keystone’]

• roles: oslo_config_validator

Role documentation

• oslo_config_validator
  • About the role
    • Exceptions
    • Requirements
    • Role Variables
    • Dependencies
    • Example Reporting Playbook
    • Example playbook to validate only one service
    • License
    • Author Information
  • Full Description
    • Role Documentation
      • Role Defaults
      • Role Variables: main.yml
      • Molecule Scenarios
        • Scenario: default
          • Example default configuration
          • Molecule Inventory
          • Example default playbook
        • Scenario: mocked_failure
          • Example mocked_failure configuration
          • Molecule Inventory
          • Example mocked_failure playbook

undercloud-service-status

Verify undercloud services state before running update or upgrade.

Check undercloud status before running a stack update - especially minor update and major upgrade.

• hosts: undercloud

• groups: backup-and-restore, post-upgrade, pre-upgrade, post-update, pre-update

• parameters:

• roles: undercloud_service_status

Role documentation

• undercloud_service_status
  • Role Documentation
    • Role Defaults
    • Role Variables: main.yaml