Return the instructions to using the "service" project as it was before
5ecee29572556140e57ed667ef275d8429c994b6, and as it is in other manual
installation instructions.
Add a note that describes the circumstances in which you need to use
"services" as the project name.
Change-Id: I76de8960ac640b9e8037879af85b84ce39b4cdcb
Co-Authored-By: Zane Bitter <zbitter@redhat.com>
Task: 28520
Story: 2003872
currently Heat fails to create a stack requiring deferred auth with
trusts when user happens to have a role assigned for which a different
but similar named role exist in another Keystone domain.
This patch makes Heat to attempt extract role IDs from the
auth_token_info first and pass those to Keystone trust if found.
Change-Id: Ic9207e3f027f9c56c14d548d404ecc0c2427f326
Story: 2002613
Task: 22237
The [keystone_authtoken]/auth_uri setting was deprecated in
favour of [keystone_authtoken]/www_authenticate_uri. This
commit uses the new setting as the fallback if
[clients_keystone]/auth_uri has not been set.
Change-Id: I4b6e254b1344865e3775948a8bbf1e9aac196e4f
Story: #2004434
Task: #28097
Non-containerized multinode scenario jobs are no longer supported
and should be removed from zuul config.
Change-Id: I0c98aecd82478fbf7e2b2a45d5b2664290155ed9
When a workflow execution fails, we don't return anything information to
the user. Let's propage what mistral sends us in the resource failure.
Change-Id: Ib412346f12450fa5e6a1291d635debe1a4add380
Story: #2004396
Task: #28025
Update the jobs that were explicitly using python 3.5 and have them
just use python 3 without specifying a minor version.
Change-Id: I38734f2956a30c01ff51e2d74a9c248e4304d08b
We are updating all Python projects to publish artifacts to PyPI. The
name "heat" is already taken there by another project, and they have
rejected our request to claim the name. We therefore need to change the
dist name used to package heat. We have some other projects publishing
using an "openstack-" prefix, so I propose using the name
"openstack-heat". This will not change the imports or anything else
about how the code works, just how it is packaged.
Add a grenade plugin for upgrading between the packages with different
names so that we can clean up the old version of the code and avoid
discovering the heat plugins multiple times in different locations.
Change-Id: I59b55cffd9e648f842eb286b936f09c5b55a76db
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This reverts commit 4e8a3ca6b2041c170f4073499ee0315616396af2.
This is handled generically with this change and its dependency:
https://review.openstack.org/#/c/606853/
Change-Id: Ic79cc07a2d11772c1892b2db8c4c02cc7be4081c
This adds basic framework for heat-status upgrade
check commands. For now it has only "check_placeholder"
check implemented.
Real checks can be added to this tool in the future.
Change-Id: I83629184b49a6cf91928df702db23156433d99f6
Story: 2003657
Task: 26131
We have the OutputDefinition API now, and no longer need to treat
templates like CFN JSON blobs to obtain information about outputs.
Change-Id: I8dfea1e9855a56fb85d2e3af40996d5f337d7859
In a number of places we parse templates passing None as the stack
definition, in order to be able to extract information from the template
in cases where we don't actually need to resolve functions.
However, the GetParam and GetFile HOT functions require an actual stack
definition to be passed in order to initialise them. So far we haven't
encountered any cases where those functions appear where we pass None
for the stack definition. Ensure that all Functions can always be
created even with no stack definition.
Note that the cfn ParamRef class is not affected, as the Ref function
always selects the GetResource implementation when the stack definition
is None.
Change-Id: Ic947dcdc17e9dbc58459a92ba970c292d70578cd
This was correct for the RDO installation guide.
This reverts commit b90278b503aff2ad8148af38525beb90ffb117d8.
Change-Id: I5107e712a903f334f1a3a996b9140e9e2fe0807a
When migrating stacks to convergence, if there are resources in
the database that are not in the current_template_id of the stack,
they are possibly of no isue, so it would better to delete those
resources from db to avoid any future update issues.
Change-Id: Ica99cec6765d22d7ee2262e2d402b2e98cb5bd5e
Story: #2004071
Task: 27092
Use '!=' instead of 'is not' to compare strings.
In practice, short strings that appear in the source code are interned
in CPython, but this is implementation-specific.
Change-Id: If3f305c2d647fcd7515cb0a326a30f4eda93acd3
With moving away from required milestone releases, the version numbers
calculated by PBR on the master branch will not work for those testing
upgrades from the last stable release. More details can be found in the
mailing list post here:
http://lists.openstack.org/pipermail/openstack-dev/2018-October/135706.html
This is an empty commit that will cause PBR to increment its calculated
version to get around this.
PBR will see the following which will cause it to increment the version:
Sem-Ver: feature
Please merge this patch as soon as possible to support those testing
upgrades.
Change-Id: Ifbba36f4974efcf891c7f5938acfeef75bb05dd2
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Quotes around {posargs} cause the entire string to be combined into one
arg that gets passed to stestr. This prevents passing multiple args
(e.g. '--concurrency=16 some-regex')
Change-Id: Iccbd680731592abab4980a51aa97c60d6ef95005
We use the notify.signal() call to notify the main thread that the stack
status has moved to IN_PROGRESS so that it can wait before returning
control to the user. Therefore it is expected that if an operation
eventually fails (or succeeds), signal() will have been called a long
time previously. The only reason it is there is to guard against
failures before the resource attains the IN_PROGRESS state, where the
persistence of the state has been deferred to coincide with the lock
release.
Story #2003988
Task: 26931
Change-Id: Ie0519ee78607f71855c2c0ace2cb4ff52c5809b6