Support for public baymodels
Operator's should be able to create and publish publicly available baymodels.
This allows new users to get started using magnum with minimum effort. Users would use the baymodel-list command to see the public models (created by the operator) and the models they have created themselves.
Blueprint information
- Status:
- Complete
- Approver:
- Adrian Otto
- Priority:
- Medium
- Drafter:
- Murali Allada
- Direction:
- Approved
- Assignee:
- Murali Allada
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Adrian Otto
- Completed by
- Adrian Otto
Related branches
Related bugs
Sprints
Whiteboard
This feature requires the following changes
1) Add a boolean type column called 'public' to the baymodel table; Default value will be False.
2) When a baymodel is created, we look at the role of the user creating it. If it is created by a service admin, we set the 'public' column to True.
Alternate approaches:
1) Add a --public flag to the bay-create command. If the user role is service admin and the --public flag is set to True, we make the baymodel public. This will also allow us to support public baymodels created by any user in the future.
2) Instead of using roles, we add a new operator_project_id to the magnum config file. Any user with that project id can create public baymodels. When a model is created, we just compare the project_id in the config file and the project_id in the users context, if they match, we set public = True. The Solum project used an approach like this to create public languagepacks created by the operator.
Gerrit topic: https:/
Addressed by: https:/
WIP: Adding support for public baymodels
Work Items
Dependency tree
* Blueprints in grey have been implemented.
