Templates directory should be renamed for better visibility

[Emilien Macchi]

When deploying a containerized undercloud, tripleoclient creates 2 directories in $HOME:

- tripleo-A_4mgH-config (A_4mgH is generated), which is the config-download.
- tripleoclient-Wvg4w0 (Wvg4w0 is generated), which contains the templates used to deploy.

Having both directories in $HOME is really good for our operators, so they can easily make some change and redeploy, also they have easy access to the data.

However, the generated string put in the directory name isn't very helpful. Instead we should use timestamp.

Like: tripleo-config-download-2018-04-06 (instead of tripleo-*-config) and templates-2018-04-06 (instead of tripleoclient-*).

Note: on a related topic, the directories permissions are too strong, see https://bugs.launchpad.net/tripleo/+bug/1761595 but this topic is out of context in this bug.

[Emilien Macchi (emilienm)]

Part of the bug is resolved by Jill: https://bugs.launchpad.net/tripleo/+bug/1752118

So we need to solve the tripleoclient dir.

[Alex Schultz (alex-schultz)]

The tripleoclient- folder is an actual temporary folder and should be removed once the installation is complete. I'm updating this to happen by default.

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/560578

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/562032

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/560578
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=f6a9761985889ecc6111817384b0c42b7ef71e76
Submitter: Zuul
Branch: master

commit f6a9761985889ecc6111817384b0c42b7ef71e76
Author: Alex Schultz <email address hidden>
Date: Wed Apr 11 12:55:40 2018 -0600

    Save temporary working data

    This change adds a new install artifact that contains the heat temporary
    directory, hieradata override file, and the ansible scripts used during
    the undercloud install.

    This includes a new lower limit of tripleo-common 9.0.1

    Depends-On: Ie00f71b12f56262985c47810be0e80402e9e558e
    Depends-On: I16f19a121212d989e1184103054eb890ec4b9297
    Change-Id: I62d34ea7817d5e62613ddcdbb69f2a7463273ccf
    Related-Bug: #1761810

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/566326

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/566326
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=732df8509ec95b4d2aed4d035a0f07dd7f0b027c
Submitter: Zuul
Branch: master

commit 732df8509ec95b4d2aed4d035a0f07dd7f0b027c
Author: Alex Schultz <email address hidden>
Date: Fri May 4 08:22:15 2018 -0600

    Set cleanup in undercloud.conf

    If it's defined, we should set the value. Otherwise we can't flip the
    value from True (The new default) to False.

    Change-Id: I13561c3c2f190d9ae62a8ace88e0ddedf414519c
    Needed-By: I027a76d2f37a5af5bd0a599783287632298acf3f
    Related-Bug: #1761810

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/562032
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=cb7a79bfb6d1e3c7f742996f1ba9109e4ceee3a0
Submitter: Zuul
Branch: master

commit cb7a79bfb6d1e3c7f742996f1ba9109e4ceee3a0
Author: Alex Schultz <email address hidden>
Date: Tue Apr 17 13:24:18 2018 -0600

    Enable cleanup by default for undercloud install

    The goal of this change is to remove the randomly generated data that we
    we use during the installation of the undercloud by default. This
    change switches the cleanup configuration in the undercloud.conf to
    be true by default so we cleanup the generated heat temporary files by
    default. The undercloud deploy flag still remains the same where it is
    not currently enabled by default if you leverage the 'openstack
    undercloud deploy' command.

    Change-Id: I027a76d2f37a5af5bd0a599783287632298acf3f
    Related-Bug: #1761810