A number of actions still use ProcessTemplatesAction as a base class.
This doesn't make sense in most cases. This is an attempt to decouple
these classes.
Change-Id: I93106288c3f085034efb79a89e01b705f70db6ee
Co-Authored-By: Alex Schultz <aschultz@redhat.com>
Delete the old tarball from the config container when the
tripleo.config.get_overcloud_config action is run. This will prevent the
new tarball from also containing the old tarball, which causes the
tarball to grow in size.
Change-Id: I85c8659e16503c40e2f9ff915106040859cc03a5
Closes-Bug: #1801416
Pass the file object to swift client instead of reading it.
When the object passed have a 'read' method the client will
write data in chunks. Chunk size defaults to 65536.
Closes-Bug: #1796436
Change-Id: Ibdfa1019ebf291f30180fc2257d225e96c3306aa
Deleting swift containers (plans) with large numbers of files can
take longer than we'd like.
This patch uses the SwiftService API which contains an implementation
of bulk delete used by the swift CLI which speeds up delete operations.
Change-Id: I8362a7986e2e4ff0aecaf867faf47c24b658d15b
Closes-bug: #1615825
Add a new workflow, config_download_export, to export the
config_download files by providing a swift tempurl of the generated
tarball.
The CLI will be migrated to using this workflow.
Partial-Bug: #1783646
Change-Id: Ic3d3667a7e2d0b445a4ace4d9aa8643062eb9cf3
Override the default git commit message so that it's clear that the
config-download commit was run from the Mistral action.
Also, first download the existing config container if one exists. Since
the config-download dir is now managed as a git repo, we want to
preserve the git history, so we need to first reuse the existing
contents of the config container.
Change-Id: I0246918d89dfb564e3d472d4b2f517b5beaf4372
Each time the config-download workflow is run, create a symlink at
/var/lib/mistral/config-download-latest that will point to the latest
execution uuid under /var/lib/mistral. This will make it easier for
users to quickly find the latest config-download working directory.
Change-Id: I9375f343a70653203cb984065e14fe616a35c5cc
Makes config download write directly to the directory specified by
--config-dir, instead of a tmpdir underneath that location.
This change also breaks Config.download_config tasks into unique
funtions to support accessing directory creation functionality
independently from config retrieval and playbook creation.
Change-Id: Ie00f71b12f56262985c47810be0e80402e9e558e
Depends-On: Ibb59b044dc0c14bf48dc3d500536195230414c81
Depends-On: Icbd6dd65893f785b7ca8edf2eab46dbc7492e050
Closes-Bug: 1752118
The Ansible actions and DownloadConfig actions both relied on a tmp path
for the working files they saved. This is less than ideal as some of
this data could be sensitive so it should not be stored in /tmp.
Also, the path was unpredictable, making things more difficult from a
user perspective.
This patch adds a work_dir input to these actions and makes use of that
input from the config-download-deploy workflow. The default behavior
when this input is not supplied is the previous behavior to use a
generated path under /tmp.
Change-Id: I89b17d0c4f035705fd5230caad06d331fd5b5e76
implements: blueprint ansible-config-download
This review implement the minor update workflow
which does:
- a noop heat stack deployment to set and refresh
the heat config output.
- download the heat config and put them in a ansible
playbooks
- run the playbooks with the mistral action
It adds actions for the config download and update
deployment
Adds the config download as a library for being call
either, by the client or mistral
Closes-Bug: #1715557
Change-Id: I199b35f865c0e68d28c5ddd82e5b8fe61abb5f33
Emilien Macchi