Merge "Adding backup-and-restore validation group"
This commit is contained in:
commit
8dd212ad1f
|
@ -47,6 +47,7 @@ Existing validations:
|
|||
validations-pre-update-run-details
|
||||
validations-pre-update-converge-details
|
||||
validations-post-update-details
|
||||
validations-backup-and-restore-details
|
||||
|
||||
|
||||
Indices and tables
|
||||
|
|
|
@ -8,6 +8,10 @@ prep:
|
|||
- description: >-
|
||||
Validations check the hardware configuration of the Undercloud node and
|
||||
should be run before **openstack undercloud install**.
|
||||
backup-and-restore:
|
||||
- description: >-
|
||||
Validations which should be run to validate your OpenStack
|
||||
deployment before you backup it and after restore it.
|
||||
openshift-on-openstack:
|
||||
- description: >-
|
||||
Validations which will check that the environment meets the requirements
|
||||
|
|
|
@ -7,6 +7,7 @@
|
|||
Uses `ceph health` to check if cluster is in HEALTH_WARN state
|
||||
and prints a debug message.
|
||||
groups:
|
||||
- backup-and-restore
|
||||
- post-deployment
|
||||
- post-ceph
|
||||
tripleo_delegate_to: "{{ groups['ceph_mon'] | default([]) }}"
|
||||
|
|
|
@ -6,6 +6,7 @@
|
|||
description: |
|
||||
Detect failed containers and raise an error.
|
||||
groups:
|
||||
- backup-and-restore
|
||||
- pre-upgrade
|
||||
- pre-update
|
||||
- post-deployment
|
||||
|
|
|
@ -6,6 +6,7 @@
|
|||
description: |
|
||||
Check for failed healthcheck systemd services.
|
||||
groups:
|
||||
- backup-and-restore
|
||||
- post-deployment
|
||||
retries_number: 1
|
||||
delay_number: 1
|
||||
|
|
|
@ -6,6 +6,7 @@
|
|||
description: |
|
||||
Ensures image-serve vhost is configured and httpd is running.
|
||||
groups:
|
||||
- backup-and-restore
|
||||
- pre-upgrade
|
||||
- post-deployment
|
||||
- post-upgrade
|
||||
|
|
|
@ -12,6 +12,7 @@
|
|||
to the Neutron services.
|
||||
|
||||
groups:
|
||||
- backup-and-restore
|
||||
- post-deployment
|
||||
|
||||
roles:
|
||||
|
|
|
@ -17,6 +17,7 @@
|
|||
1 -> At least one check encountered an issue and requires further investigation. This is considered a warning but the upgrade may be OK.
|
||||
2 -> There was an upgrade status check failure that needs to be investigated. This should be considered something that stops an upgrade.
|
||||
groups:
|
||||
- backup-and-restore
|
||||
- pre-upgrade
|
||||
roles:
|
||||
- nova_status
|
||||
|
|
|
@ -10,6 +10,7 @@
|
|||
correctly. This should also be run before upgrade as the process will
|
||||
likely fail with a cluster that's not completely healthy.
|
||||
groups:
|
||||
- backup-and-restore
|
||||
- post-deployment
|
||||
roles:
|
||||
- pacemaker_status
|
||||
|
|
|
@ -6,6 +6,7 @@
|
|||
description: |
|
||||
Check undercloud status before running a stack update - especially minor update and major upgrade.
|
||||
groups:
|
||||
- backup-and-restore
|
||||
- post-upgrade
|
||||
- pre-upgrade
|
||||
- post-update
|
||||
|
|
|
@ -113,6 +113,7 @@
|
|||
description: |
|
||||
Write a description of your validations
|
||||
groups:
|
||||
- backup-and-restore
|
||||
- no-op
|
||||
- prep
|
||||
- pre-introspection
|
||||
|
|
Loading…
Reference in New Issue