Ocata to Pike operator driven ansible upgrade

[Marios Andreou]

For Newton to Ocata ansible upgrades tasks drive the major upgrade for all roles that do not explicitly disable them (e.g. the default "Controller" role is upgraded with ansible).

For some nodes such as those running openstack-nova-compute, the operator may prefer to drive the upgrade 'manually'. For Newton to Ocata the operator drives upgrade of these nodes with the 'upgrade-non-controller.sh' [1] to run the 'tripleo_upgrade_node.sh' [2] script.

For Ocata to Pike we should instead drive the 'manual upgrade' of these roles with ansible tasks. The tasks are already defined in the tripleo-heat-templates, for example nova-compute @ [3] so it is a matter of collecting the ansible tasks for these roles into a playbook that the operator can drive the execution of (though we will still have to orchestrate execution of the puppet-apply after the successful run of the ansible playbook, as we are currently doing at the end of [2])

[1] https://github.com/openstack/tripleo-common/blob/stable/ocata/scripts/upgrade-non-controller.sh
[2] https://github.com/openstack/tripleo-heat-templates/blob/stable/ocata/extraconfig/tasks/tripleo_upgrade_node.sh
[3] https://github.com/openstack/tripleo-heat-templates/blob/stable/ocata/puppet/services/nova-compute.yaml#L153

[mathieu bultel (mat-bultel)]

I have openned a BP for this:
https://blueprints.launchpad.net/tripleo/+spec/ansible-upgrade-playbook-from-undercloud

A POC is in progress:
https://review.openstack.org/444224

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/444224
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=d26d5c680d92cdd47a1ea9a649ffaeef05c4e663
Submitter: Jenkins
Branch: master

commit d26d5c680d92cdd47a1ea9a649ffaeef05c4e663
Author: Mathieu Bultel <email address hidden>
Date: Fri Mar 10 12:12:13 2017 +0100

    Dump all deployment role_data files to a config dir

    Add new overcloud cli command in order to dump
    all the configs from the overcloud contains in role_data.
    All different type of configs are dump in a separate file
    per role ex:
    ls config/tmpD2nDOd-config/
    config_settings-Compute.yaml
    global_config_settings-Compute.yaml
    logging_sources-Compute.yaml
    monitoring_subscriptions-Compute.yaml
    service_config_settings-Compute.yaml
    service_metadata_settings-Compute.yaml
    service_names-Compute.yaml
    step_config-Compute.yaml
    upgrade_batch_tasks-Compute.yaml
    upgrade_tasks-Compute.yaml

    The upgrade_tasks is in yaml format and can be directly
    call with ansible-playbook command, example:

    $ cat config/tmpD2nDOd-config/upgrade_tasks-Compute.yaml
    - hosts: Compute
      name: Compute playbook
      tasks:
      - name: Stop snmp service
        service: name=snmpd state=stopped
        tags: step1
      - name: Stop nova-compute service
        service: name=openstack-nova-compute state=stopped
        tags: step1

    This patch to allow operators to run manually
    the upgrade tasks via ansible on the Undercloud.

    Change-Id: I7d89ffde8a19b30aaf59efb11e41d32cfa644b83
    Closes-bug: #1665585

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-tripleoclient 7.2.0 release.