post-upgrade

check-reboot

Verify if a reboot is necessary with yum-utils.

This validation checks if a reboot is necessary with yum-utils with the option: needs-restarting -r

• hosts: all

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

• parameters:

• roles: check_reboot

Role documentation

• check_reboot
  • Role Documentation

container-status

Ensure container status.

Detect failed containers and raise an error.

• hosts: undercloud, allovercloud

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

• parameters:

• roles: container_status

Role documentation

• container_status
  • Role Documentation
    • Molecule Scenarios

image-serve

Verify image-serve service is working and answering.

Ensures image-serve vhost is configured and httpd is running.

• hosts: undercloud

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

• parameters:

• roles: image_serve

Role documentation

• image_serve
  • Role Documentation
    • Role Variables: main.yml
    • Molecule Scenarios

nova-svirt

Check nova sVirt support.

Ensures all running VM are correctly protected with sVirt

• hosts: nova_libvirt

• groups: post-deployment, post-upgrade

• parameters:

• roles: nova_svirt

Role documentation

• nova_svirt
  • Role Documentation
    • Role Defaults
    • Molecule Scenarios

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

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: backup-and-restore, 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

overcloud-service-status

Verify overcloud services state after running a deployment or an update.

An Ansible role to verify the Overcloud services states after a deployment or an update. It checks the API /os-services and looks for deprecated services (nova-consoleauth) or any down services.

• hosts: Undercloud

• groups: post-deployment, post-upgrade, post-overcloud-upgrade, post-overcloud-converge

• parameters:

  • overcloud_service_status_debug: False

  • overcloud_service_api: [‘nova’, ‘cinderv3’]

  • overcloud_deprecated_services: {‘nova’: [‘nova-consoleauth’]}

• roles: overcloud_service_status

Role documentation

• overcloud_service_status
  • About The Role
    • Requirements
    • Dependencies
    • Example Playbook
    • License
    • Author Information
  • Full Description
    • Role Documentation
      • Role Defaults
      • Role Variables: main.yml
      • Molecule Scenarios

stack-health

Stack Health Check.

Check if all stack resources are in a ‘COMPLETE’ state before starting an upgrade.

• hosts: undercloud

• groups: pre-upgrade, post-upgrade

• parameters:

• roles: stack_health

Role documentation

• stack_health
  • Role Documentation
    • Role Variables: main.yml
    • Molecule Scenarios

undercloud-disabled-services

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_disabled_services

Role documentation

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

undercloud-proxy-validation

Verify proxy variables are properly set.

Check proxy configuration 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_proxy_validation

Role documentation

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

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
  • Requirements
  • Role Variables
  • Dependencies
  • Example Playbook
  • License
  • Author Information
    • Full Description
      • Role Documentation
        • Role Defaults
        • Role Variables: main.yaml