As of the oslo.context 4.0.0 release, RequestContext objects no
longer have a tenant attribute, instead expecting callers to use
project_id for that purpose. Update all context.tenant references to
context.project_id in order to facilitate this transition.
Change-Id: I2830ccf840bf4d1d8a516287adee51c46d2a5583
Now admin can see the list of user's environments,
but can't delete them. There will gives the 403 Forbidden.
This patch let admin can delete user's environment.
Change-Id: Ic208ae586427bb3eb9ce4749870158ccdfb09d76
Closes-Bug: #1654103
we don't have to def ensure_tree, because Oslo.utils 1.8
provides the function and just use it.I also deleted the
code in tests/unit/.
Change-Id: I61e9d87e6dde5b7a52e7b6399f4be6e8d5fca340
fcntl module is only needed on non-windows OS's and is not available on
windows. This commit restores ability to launch murano under windows.
Implements bp: murano-engine-package-cache
Change-Id: I70a17070b9c80d4f220f459a732ecf45f9d70e81
This commit modifies cleanup method of API package loader to include
cleaning up of stale downloaded packages. This is done with respect to
IPC and green-thread usage locks.
Implements blueprint: murano-engine-package-cache
Change-Id: I09a08c3646c32666893b5ed35463f8ec5e413284
401 Unauthorized is the HTTP status code used for authentication
errors for eg. Missing or Bad Authentication. 403 Forbidden
response is used for denying permission to access resources
for a correctly authenticated user.
This fix corrects the mistake in the api.
Change-Id: I0903b226cfe32a7aed69d265a27ca21d7cc9b98e
Closes-Bug:1477013
When session id or body were not provided - forbidden code was raised.
That may lead to confusion and make debuggind difficult.
This commit fixes error codes and provides explanation is responses.
API specification is updated.
Closes-Bug #1491785
Change-Id: I87d60a1a7d049ee7d482dd76ceeb9f446b452fca
Moves the session check to utils file, together with check_env and
applies the check during environment show API call, thus raising correct
errors in case supplied session id is invalid or belongs to a different
environment
Change-Id: Ic10956b604cfc7243f07774e9da11caaf18794cd
Closes-Bug: #1481099
Remove duplicated check environment code, use verify_env decorator or
check_env from utils. Note that tenant checks now return 403 instead
of 401.
Closes-Bug: #1479570
Change-Id: I1964a9933394df133ab0559542f0c5dafd56e9a6
To follow latest community practices we need to use oslo_log in
murano instead of handcrafted libs.
Unsupported log level 'audit' was changed to 'info'.
Change-Id: I40c0f3790e34bf80d0b63554e86b3cbc019eefca
It has the functional tests for the blueprint environment-template, including the management
of environment templates (creation, deletion, updating) and the creation of an environment
from the template.
Change-Id: I8fc5c7e1f6a4354b47f087fe141442ab604cfdd9
Remove gettextutils in favor of oslo.i18n suite for
internationalization purposes. Wrap murano.common.i18n around
oslo.i18n. Mark all logs messages of levels higher than
DEBUG for translation with _/_LI/_LW/_LE/_LC to conform with
oslo.i18n guidelines.
Change-Id: I09a2e2fc802e404f5c59fa4edd2a2124ad24101a
Implements: blueprint organize-translation
Removed #noqa from gettextutils and added them to import_exceptions.
I think it is better to specify option in one place (tox.ini) than
every time take care that you do not forget to specify this tag.
Also removed a few unused imports that were revealed in the process.
Change-Id: Ic4ca9cf374870075a36b88269ff8aea5a8e24a90
Deletion sessions were in 'deploying' state instead of 'deleting'.
Because of this such sessions could not be found by RPC result
processing code and remained in 'deploying' status causing UI
to display progress bar forever.
Also there were 2 duplicate SessionStates enums in the code with
and the second copy was outdated and didn't contained DELETING
status as well as other new session statuses. Because buggy code
was using that outdated enum it was necessary to merge both enums
into single declaration
Change-Id: I852f1f3dd1051c7b40afaa2575a4335b0f3c3104
Closes-Bug: #1386068
Now environment deletion is done as a regular deployment that can fail.
Environments that are deleted, but deletion process has failed remain in database
and shown in dashboard with status 'delete failure'. Environments that are being deleted
has status 'deleting' and do not disappear before they really got deleted on engine side
Also improved status reporting for environments. Now it also reports status of last deployment -
'deploy failure', 'delete failure'
P.S. Functional tests were slightly refactored and fixed to reflect changes
in deletion logic
Change-Id: I05625dd71f7ca9559bb88319b26b122214f15019
Closes-Bug: #1325101
Jeremy Stanley