pre-upgrade

pre-upgrade

check-ftype

XFS ftype check.

Check if there is at least 1 XFS volume with ftype=0 in any deployed node.

  • hosts: undercloud, overcloud
  • groups: pre-upgrade
  • metadata:
  • parameters:

View validation source code.

deployment-images

Verify existence of deployment images.

This validation checks that images bm-deploy-kernel and bm-deploy-ramdisk exist before deploying the overcloud, and that only one exists by that name.

  • hosts: undercloud
  • groups: pre-deployment, pre-upgrade
  • metadata:
  • parameters:
    • deploy_ramdisk_name: bm-deploy-ramdisk
    • deploy_kernel_name: bm-deploy-kernel

View validation source code.

node-health

Node health check.

Check if all overcloud nodes can be connected to before starting a scale-up or an upgrade.

  • hosts: undercloud
  • groups: pre-upgrade
  • metadata:
  • parameters:
    • hosts_are_ips: True

View validation source code.

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
  • metadata:
  • parameters:

View validation source code.

repos

Check correctness of current repositories.

Detect whether the repositories listed in yum repolist can be connected to and that there is at least one repo configured. Detect if there are any unwanted repositories (such as EPEL) enabled.

  • hosts: undercloud, overcloud
  • groups: pre-upgrade
  • metadata:
  • parameters:

View validation source code.

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
  • metadata:
  • parameters:

View validation source code.

undercloud-disk-space-pre-upgrade

Verify undercloud fits the disk space requirements to perform an upgrade.

Make sure that the root partition on the undercloud node is large enough before starting an upgrade We first check for an explicit /var mount point since that’s where we store logs and images and if it doesn’t exist, we fall back to /. http://tripleo.org/environments/environments.html#id5

  • hosts: undercloud
  • groups: pre-upgrade
  • metadata:
  • parameters:
    • min_undercloud_disk_gb: 10

View validation source code.

undercloud-heat-purge-deleted

Verify heat-manage purge_deleted is enabled in crontab.

Without a purge_deleted crontab enabled, the heat database can grow very large. This validation checks that the purge_deleted crontab has been set up.

  • hosts: undercloud
  • groups: pre-upgrade, pre-deployment
  • metadata:
  • parameters:
    • cron_check: heat-manage purge_deleted

View validation source code.

undercloud-ram

Verify the undercloud fits the RAM requirements.

Verify that the undercloud has enough RAM. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html/Director_Installation_and_Usage/sect-Undercloud_Requirements.html

  • hosts: undercloud
  • groups: prep, pre-introspection, pre-upgrade
  • metadata:
  • parameters:
    • min_undercloud_ram_gb: 16

View validation source code.

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: post-upgrade, pre-upgrade
  • metadata:
  • parameters:

View validation source code.

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.