if called by mistral-db-manage it will log info level
to /var/log/mistral/mistral-db-manage
Included some debug level logging also for main actions.
Change-Id: I0574b38efcc0dd7485953bf3089ff0a5a3ef6394
Closes-Bug: #1689821
Release note and command line parameter added.
From now it is optional to list openstack modules in mapping file which
you would not include into supported action set.
Change-Id: I5ab01395c507fc857dca7cf08ab344a07def0dcf
TrivialFix: Similar [1] in Kolla project
As we known, Exceptions are raised by the sys.exit() function. When they
are not handled, no stack traceback is printed in the Python interpreter.
Therefore, when using sys.exit(main()) instead of main()
may be more readable and reasonable.
[1] https://review.openstack.org/#/c/349353/
Change-Id: Ic71d4bfb1085c68ea9eb7e1382e7263a81634ad1
python-ironic-inspector needs an actual session when creating the
client, since it will try to fetch and furtherly validate the given
version regardless if a version is explicitly given. This fetching
and validation do calls to keystone which require credentials. Thus,
I'm using mistral's service credentials to fetch the required info.
Change-Id: I908552d2fb8ab4a5a3593f03f92ee6a31b672034
* use oslo.log for logging functionality
* get rid of the file /mistral/openstack/common/log.py
Implements: blueprint mistral-log-enhancement
Partial-Bug: #1459188
Change-Id: I6b62cffda0a20b6caf59cc30bcc33c21ae1e5898
* Standard workflows are creating during sync_db.sh
* Standard workflows include:
- std.create_instance
- std.delete_instance
(list will be extended in future)
* Standard actions:
- std.wait_ssh (needed for std.create_instance)
* Make it possible to see these workflows from any project (global scope)
* Small changes in sqlalchemy api and workflows_service
Partially implements blueprint mistral-multitenancy
Change-Id: I8a8ace40949b2b711a292aac94d7e6354d1dff9c
* Action factory register actions in DB at starting
* Added script tools/sync_db.sh for sync with db
(Updates system actions, it is required before
first Mistral launch)
* Changed init Mistral in devstack: we must do
sync_db before the launching.
* Since we have to write all actions in DB, unit
test are also modified:
* Now in tearDown() we don't drop db at all,
but just delete all things except Actions.
* Created heavy_init() method as a replacement
setUpClass(), see comments in tests/base.py
* Register actions operation is too much expensive
operation so we create db and init actions in
heavy_init() method.
TODO:
* Provide executor info to construct action class in
runtime using action_factory
* Modify/write an instruction 'How to start Mistral'
Change-Id: If4416c4da5c05189126c109aa613a0303c1b7ef0
Eyal