create history of the overcloud deploy command

Bug #1673700 reported by mathieu bultel on 2017-03-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mathieu bultel

Bug Description

Generate an history (a log file into a directory like ~/.tripleo/history ) for tracking all the overcloud deploy command launch by the user, with a timestamp.
The history file for the deploy command would be useful to track what previous command has been run, which environment files has been passed and which templates has been used.
In some context, like update or upgrade, where sometimes customers upgrade their cloud from several major releases, will allow us to debug more easily and understand more quickly what kind of argument has been used by the users.
Another context would be for the automation and CI purpose, where with a such log file, we would be able to discover automatically the updta/upgrade/scale overcloud command.

The review attached only track the templates and the environment files, but we think of adding more information there..

The log file should looks like:
2017-03-16 16:23:58.645824 templates: /usr/share/openstack-tripleo-heat-templates
2017-03-16 16:23:58.645843 environment_files: /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.yaml, /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml, /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml, /home/stack/network-environment.yaml, /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml, /usr/share/openstack-tripleo-heat-templates/environments/major-upgrade-composable-steps.yaml, overcloud-repo.yaml, /home/stack/tripleo-heat-templates/ci/environments/multinode_major_upgrade.yaml

Tags: ux Edit Tag help
Changed in tripleo:
assignee: nobody → mathieu bultel (mat-bultel)
milestone: none → pike-1
Changed in tripleo:
status: New → In Progress
description: updated
Changed in tripleo:
importance: Undecided → Low
Changed in tripleo:
milestone: pike-1 → pike-2
Changed in tripleo:
milestone: pike-2 → pike-3

Submitter: Jenkins
Branch: master

commit fa1683ca9d4d69fafb36d8ca8acfa7c23ec6b4eb
Author: Mathieu Bultel <email address hidden>
Date: Thu Mar 16 16:29:51 2017 +0100

    create history for the overcloud deploy command

    Add a history directory in user $HOME for tracking
    all the calls of the openstack overcloud deploy command
    passed by the users.
    Each deploy command run by a user is now track in an history file under
    $HOME/.tripleo directory.
    It allow to retrieve all the previous calls from
    the openstack overcloud deploy command, the environment files used and the
    templates directories used, for analysis, debugging or tracking. See

    It will be very usefull for post deployment user experience and
    for customer debuging.

    This review aim to be backport for old releases support.
    I will implement a mistral workflow in a follow up review for
    Pike, as suggested by D0ugal (D Matthews)

    Change-Id: Ibf7dd4a7b0036b6f2a0809d0448a05665c809167
    Closes-Bug: #1673700

Changed in tripleo:
status: In Progress → Fix Released

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

tags: added: ux
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers