Multitenancy support
We should be able to use the same Mistral installation for multiple tenants. Without it Mistral can't be actually considered an OpenStack project. This, first of all, requires to implement resource isolation between different tenants.
Blueprint information
- Status:
- Complete
- Approver:
- Renat Akhmerov
- Priority:
- Medium
- Drafter:
- Renat Akhmerov
- Direction:
- Needs approval
- Assignee:
- Nikolay Makhotkin
- Definition:
- New
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
2015.1
- Started by
- Nikolay Makhotkin
- Completed by
- Renat Akhmerov
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add project_id to the workbook and filter by it
Addressed by: https:/
Add OS_LOG_CAPTURE to testr.conf
Addressed by: https:/
Move all tests to use base.BaseTest
Addressed by: https:/
All tests should call the base class setUp()
Addressed by: https:/
Switch from unittest2 to testtools
Addressed by: https:/
make sure the api tests get a valid context
Addressed by: https:/
favor addCleanup() over tearDown()
Addressed by: https:/
Make sure the context is correctly passed through the rpc
Gerrit topic: https:/
Addressed by: https:/
Fix workbook and workflow models
Addressed by: https:/
Create standard workflows
Gerrit topic: https:/
Addressed by: https:/
Add 'project_id' to Execution and Task
Addressed by: https:/
Fix creating objects with the same names
Addressed by: https:/
Refactoring getting one object from DB
Work Items
Dependency tree
* Blueprints in grey have been implemented.
