add-subnet help text incorrect
Bug #1636347 reported by
james beedy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Reed O'Brien |
Bug Description
`juju help add-subnet` gives some info pertaining to the `create-subnet` command which doesn't exist anymore.
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 2.1.0-beta1 |
Changed in juju: | |
milestone: | 2.1-beta1 → 2.1-beta2 |
Changed in juju: | |
milestone: | 2.1-beta2 → none |
Changed in juju: | |
milestone: | none → 2.1.1 |
milestone: | 2.1.1 → 2.1-rc1 |
Changed in juju: | |
milestone: | 2.1-beta4 → 2.1-rc1 |
Changed in juju: | |
assignee: | nobody → Reed O'Brien (reedobrien) |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
ubuntu@ ip-10-20- 100-90: ~$ juju help add-subnet <provider- id> <space> [<zone1> <zone2> ...]
Usage: juju add-subnet [options] <CIDR>|
Summary:
Add an existing subnet to Juju.
Options:
-B, --no-browser-login (= false)
Do not use web browser for authentication
-m, --model (= "")
Model to operate in. Accepts [<controller name>:]<model name>
Details:
Adds an existing subnet to Juju, making it available for use. Unlike
"juju create-subnet", this command does not create a new subnet, so it
is supported on a wider variety of clouds (where SDN features are not
available, e.g. MAAS). The subnet will be associated with the given
existing Juju network space.
Subnets can be referenced by either their CIDR or ProviderId (if the
provider supports it). If CIDR is used an multiple subnets have the
same CIDR, an error will be returned, including the list of possible
provider IDs uniquely identifying each subnet.
Any availablility zones associated with the added subnet are automatically
discovered using the cloud API (if supported). If this is not possible,
since any subnet needs to be part of at least one zone, specifying
zone(s) is required.