Instance resource doesn't allow IP assignment to VPC/quantum network
Bug #1096013 reported by
Steven Hardy
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Steve Baker | ||
Grizzly |
Fix Released
|
High
|
Steve Baker |
Bug Description
Now we have initial support for quantum-based VPC resources, we need a way to assign an instance to a specific virtual private subnet.
This probably means we need to implement PrivateIpAddres
Changed in heat: | |
milestone: | none → grizzly-3 |
Changed in heat: | |
assignee: | nobody → Steve Baker (steve-stevebaker) |
no longer affects: | heat |
Changed in heat: | |
milestone: | none → grizzly-rc1 |
status: | Fix Committed → Fix Released |
Changed in heat: | |
importance: | Undecided → High |
Changed in heat: | |
milestone: | grizzly-rc1 → 2013.1 |
To post a comment you must log in.
Setting this to High importance - this has been a FAQ from users on IRC recently so there seems to be a need to add this functionality.