Allow specifying subnet/vnet CIDR when bootstrapping to Azure
Bug #1716887 reported by
Riordan Toms
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Ian Booth | ||
Bug Description
With no way to specify CIDR for subnets/vnets this creates a major hindrance when taking into consideration multiple networks and sites that already use the existing hardcoded values if ever cross network communication is required.
azure/networkin
azure/networkin
Is this already a road mapped feature? As I understand MAAS and AWS have this ability to specify subnet CIDR's and/or use existing VPC's when bootstrapping or creating/editing models.
What is the blocking issue for other clouds? Forgive my ignorance but what is so difficult about passing values from the CLI?
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in juju: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| milestone: | none → 2.3.0 |
Revision history for this message
| Tim Penhey (thumper) wrote | #2 |
| Changed in juju: | |
| milestone: | 2.3.0 → 2.4-beta1 |
| tags: | added: cpe-onsite |
| Changed in juju: | |
| milestone: | 2.4-beta1 → none |
Revision history for this message
| Ian Booth (wallyworld) wrote | #3 |
| Changed in juju: | |
| milestone: | none → 2.9-beta1 |
| assignee: | nobody → Ian Booth (wallyworld) |
| status: | Triaged → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I believe this stems from a time before Azure Resource Manager update which allowed more flexible setting of IP ranges. I don't think there is any specific reason why we couldn't allow users to specify an existing subnet range anymore, just historical baggage and not having the time to come back and clean this one up.
Thanks for the bug report, we'll try to get it into the queue for the next major release.