Dougal Matthews 72ce841253 Only delete workflows with the tripleo-common-managed tag
The new workflow tag allows us to detect tripleo-common workflows. It is
safe to delete and reload these. Workflows that come from other places
shouldn't be removed.

There is some upgrade logic here that handles the O -> P upgrade, as on
the first run the workflows will not have the tripleo-common-managed
tag. If the tag isn't found, we revert to the current behaviour and then
on future undercloud installations this wont be a problem.

The new test is a duplication of a previous test but with multiple
workflows that have tripleo in the name. Only the one with the tag is
deleted.

Depends-On: Ieeb51f8e705b8988fb4d0f5d17d7fce6b5b04f36
Closes-Bug: #1715389
Change-Id: I84d441daedcafe686b9576d47b037977b493dbc7
(cherry picked from commit d6c0636421)
2017-09-07 21:12:26 +02:00
2017-01-24 10:01:45 -05:00
2015-11-30 22:56:47 +00:00
2017-01-24 10:01:45 -05:00
2017-08-24 21:04:45 +00:00
2015-05-28 11:27:15 -05:00
2014-02-18 09:48:12 -05:00
2017-06-06 18:11:28 +07:00
2017-03-28 22:03:54 +00:00

Team and repository tags

Team and repository tags

Undercloud Install via instack

instack-undercloud is tooling for installing a TripleO undercloud.

It is part of the TripleO project: https://docs.openstack.org/developer/tripleo-docs/index.html

Description
RETIRED, A utility to run diskimage-builder undercloud elements on a running host
Readme 20 MiB