vsphere provider doesn't tag virtual machines
Bug #1677325 reported by
Nicholas Skaggs
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Andrew Wilkins | ||
Bug Description
The vsphere provider doesn't tag virtual machines that are spun up by juju. Since the names are randomized with a "juju-" prefix, there's no way to identify which machine belongs to what deployment inside of vsphere.
I would expect the model and controller names to be inserted as tags to make them identifiable.
| description: | updated |
| tags: | added: vsphere |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.2-beta3 |
| Changed in juju: | |
| assignee: | nobody → Andrew Wilkins (axwalk) |
| status: | Triaged → In Progress |
Revision history for this message
| Andrew Wilkins (axwalk) wrote | #1 |
Revision history for this message
| Nicholas Skaggs (nskaggs) wrote | #2 |
Revision history for this message
| Andrew Wilkins (axwalk) wrote | #3 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I don't think we'll be able to get tagging in for 2.2. To create tags, you need to use an entirely separate API/SDK: http://
What I will look at doing is putting VMs into folders, so they're organised by controller and model.