Deploy translated template seamlessly after translation
Currently per the initial scope of the heat-translator project, it dumps a translated template as an output. We should provide a support for two things,
1. Support current behavior of dumping a translated file that can be used by end use in a way they want to. For example, solum user may want to use the translated file.
2. Allow user to seamlessly deploy the translated template i.e. run 'stack-create' command underneath and deploy the template with or without dumping a translated file per user choice.
This blueprint is to provide support for #2. The focus for this blueprint will be call python-heatclient or Heat REST API to invoke stack-create for now for TOSCA hello world template.
Blueprint information
- Status:
- Started
- Approver:
- Sahdev Zala
- Priority:
- Medium
- Drafter:
- Sahdev Zala
- Direction:
- Approved
- Assignee:
- bharaththiruveedula
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Good progress
- Milestone target:
- None
- Started by
- Sahdev Zala
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(Bharath)This BP will have a new flag for deployment to OpenStack Heat?
For example:
heat-translator --template-
If this is the case, we need all the parameters like username, password, auth_url, project_name as well to invoke heat client.
(spzala) Hi Bharath, I agree but for now my thinking is to take the same approach as we did to fetch Nova images i.e. if those needed parameters are set in the ENV then we continue to deployment otherwise we log warning with just translation. Thanks!
(Bharath) Sure, makes sense! I want to use same methods we used for creating nova flavors.
(spzala) Sure, thanks Bharath. Also, you may want to look at how Horizon is invoking Heat Client. And see if you rather prefer that way.
(spzala): Hi Bharath, I am working on this blueprint https:/
Gerrit topic: https:/
Addressed by: https:/
[WIP]Add support to create heat stack from TOSCA