EC2 - Support Network Spaces
Bug #1644401 reported by
james beedy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
High
|
Unassigned |
Bug Description
Per discussion with @rickharding earlier this week, juju doesn't yet have full support for spaces in EC2. When deploying instances, it seems Juju will respect the spaces constraint until I need to add an additional unit, at this point Juju just places the unit in a random subnet (outside of my space), even if I have subnets in every AZ in the region. To my understanding, I have breached the point of networking support for EC2, and need to adjust my proposed means of network isolation in my provisioning. I'm strongly motioning for a legitimate push to bring the EC2's network spaces support up to speed. Just wanted to get this on the docket proper.
thx
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in juju: | |
importance: | Wishlist → High |
milestone: | none → 2.1.1 |
Changed in juju: | |
milestone: | 2.4-beta1 → none |
To post a comment you must log in.
This work will addressed at a later date than originally intended.
I am triaging this into 2.3 at this stage.