OpenStack and AWS - Bindings do not affect machine placement
Bug #1878202 reported by
Joseph Phillips
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Simon Richardson | ||
Bug Description
At present, only the MAAS provider accommodates bindings returned with provisioning info.
We need to ensure:
1. The OpenStack provider provisions NICs on the host that reflect application bindings.
2. The EC2 provider provisions a machine connected to one of the bindings. We do not currently support multi-NIC on AWS, but landing the target machine in *one* of the appropriate subnets will reflect the current behaviour with regard to space constraints.
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Joseph Phillips (manadart) |
| milestone: | none → 2.8.1 |
| tags: | added: network |
Revision history for this message
| Simon Richardson (simonrichardson) wrote | #1 |
| Changed in juju: | |
| assignee: | Joseph Phillips (manadart) → Simon Richardson (simonrichardson) |
| status: | Triaged → In Progress |
Revision history for this message
| Simon Richardson (simonrichardson) wrote | #2 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Submitted PR https:/