nova-status

this page last updated: 2019-07-23 10:14:29

nova-status¶

Role Documentation¶

Welcome to the “nova-status” role documentation.

Role Variables: main.yml¶

metadata:
  description: "Performs a release-specific readiness check before restarting services\
    \ with new code. This command expects to have complete configuration and access\
    \ to databases and services within a cell. For example, this check may query the\
    \ Nova API database and one or more cell databases. It may also make requests\
    \ to other services such as the Placement REST API via the Keystone service catalog\n\
    The nova-status upgrade check command has three standard return codes:\n0 -> All\
    \ upgrade readiness checks passed successfully and there is nothing to do. 1 ->\
    \ At least one check encountered an issue and requires further investigation.\n\
    \      This is considered a warning but the upgrade may be OK.\n2 -> There was\
    \ an upgrade status check failure that needs to be investigated.\n      This should\
    \ be considered something that stops an upgrade.\n"
  groups:
  - pre-upgrade
  name: Nova Status Upgrade Check

Molecule Scenarios¶

Molecule is being used to test the “nova-status” role. The following section highlights the drivers in service and provides an example playbook showing how the role is leveraged.

Scenario: default¶

Example default configuration¶

driver:
  name: docker
lint:
  enabled: false
log: true
platforms:
- easy_install:
  - pip
  environment:
    http_proxy: '{{ lookup(''env'', ''http_proxy'') }}'
    https_proxy: '{{ lookup(''env'', ''https_proxy'') }}'
  hostname: centos7
  image: centos:7
  name: centos7
  pkg_extras: python-setuptools python-enum34
- environment:
    http_proxy: '{{ lookup(''env'', ''http_proxy'') }}'
    https_proxy: '{{ lookup(''env'', ''https_proxy'') }}'
  hostname: fedora28
  image: fedora:28
  name: fedora28
  pkg_extras: python*-setuptools python*-enum
provisioner:
  env:
    ANSIBLE_LIBRARY: ../../../../library
    ANSIBLE_STDOUT_CALLBACK: yaml
  log: true
  name: ansible
scenario:
  test_sequence:
  - destroy
  - create
  - prepare
  - converge
  - verify
  - destroy
verifier:
  lint:
    name: flake8
  name: testinfra

Example default playbook¶

- gather_facts: false
  hosts: all
  name: Converge
  tasks:
  - include_role:
      name: nova-status
    name: working detection
  - block:
    - include_role:
        name: nova-status
      name: run validation
      vars:
        container_cli: docker
    name: make validation fail
    rescue:
    - meta: clear_host_errors
      name: Clear host errors
    - debug:
        msg: The validation works! End play
      name: Test output
    - meta: end_play
      name: End play
  - fail:
      msg: 'The nova-status validation didn''t properly detect bad upgrade

        status check!

        '
    name: Fail playbook if reached