At DNS record creation step Trove should not speak to Nova if Heat provisioning enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Triaged
|
Low
|
Unassigned |
Bug Description
When DNS record creation happens Trove-Taskmanager should not speak to Nova, it should speak to Heat for defining Compute Instance IP (PublicIP in terms Heat AWS::EC2::Instnace resource)
Prof. link: https:/
Instead of given mechanism Trove should able to read Stack outputs if Heat provisioning enabled.
Example(HOT): https:/
Example (AWS, JSON): https:/
Example (AWS, YAML): https:/
Changed in trove: | |
assignee: | nobody → Denis M. (dmakogon) |
description: | updated |
description: | updated |
Changed in trove: | |
importance: | Undecided → Medium |
Changed in trove: | |
status: | New → Triaged |
summary: |
- At DNS record creation step Trove should not speack to Nova if Heat + At DNS record creation step Trove should not speak to Nova if Heat provisioning enabled |
Changed in trove: | |
assignee: | Denis M. (dmakogon) → nobody |
Updating importance to "Low" (bugscrub, 2014-10-23)