Ensure the documentation is kept up to date by automatically
generating it from the source when the docs are built.
Change-Id: I3f7e61de7534a44e5d0a4ce96aaed43f4e8951ff
According to Openstack summit session [1] stestr is maintained
project to which all Openstack projects should migrate.
Let's switch it then.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: Ib27496313447cac962e4849223ab9eb96a9d873f
This adds the entry point and config file necessary for using the
oslo.policy sample generation script. It also adds a tox target to
simplify the usage of it. Finally, this commit adds
murano.common.policies.base.list_rules to
murano.common.polices (__init__.py) so that the base rules are
also included in the generated policy file.
Note that the policy sample is generated as a YAML which is
the standard adopted by Nova [0] and Keystone [1] and is now
the standard across OpenStack since Ocata [2]:
While the old json format policy file is still supported,
we recommend using the newer YAML format file, more intuitive
syntax.
The output from tox -egenpolicy will be:
murano.policy.sample.yaml in murano/etc.
The policy documentation was already updated in
I1a8581a559e4333a74d56a5bdce7e6d1f117907d
[0] e845d66a1b/etc/nova/nova-policy-generator.conf
[1] https://github.com/openstack/keystone/blob/master/config-generator/keystone-policy-generator.conf
[2] https://docs.openstack.org/ocata/config-reference/policy-yaml-file.html#older-json-format-policy
Change-Id: I2356ac0b2033bd83caaf2672189670fc300e55fd
Partially-Implements: blueprint policy-in-code
1) Create separate config use the separate config.py
to use: tox -egencfconfig
2) Create separate db for murano service broker
to use: tox -e venv murano-cfapi-db-manage \
--config-file etc/murano/murano-cfapi.conf upgrade
Change-Id: Ifd3551ace000e496d99725f46dbead62f7ef64b0
partial-implement: bp separate-service-broker-from-murano
Sometimes user wants to specify it's own logging config.
But now it should be excluded from commit all the time.
Change-Id: I323375c7b8e49658fd96a001bd6b8a3dfd675031
* support scripts were copied from other projects like cinder, ...
* some modification were made to support some code checks
* at first we focus on code issues classified as 'refactor'
* job compare sets of code issues of current and previous commit
* if new issue emerged in current commit then -1
* use tox to launch locally 'tox -e pylint'
* next step is to create non-voting gate job
* job can be tested locally, example:
* 1) create method with more then 5 arguments
* 2) commit the change
* 3) run 'tox -e pylint'
* job should fail on 'Too many arguments'
Change-Id: Iccfb842de92e2284bedcfc7d9b1df5f456ba9d14
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
Additional changes:
* Removed testing framework for MuranoPL since it was based on Nose
* Made test_log run only on Linux hosts
* Every testcase is now required to have proper setUp method
Change-Id: I86ee5ec487019c2d1b77f0fd34f748cf9c6412a0
Implements: blueprint migrate-murano-ut-to-testtoools
zhurong