juju doesn't use vsphere terminology where applicable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Medium
|
Unassigned |
Bug Description
Vsphere and juju have very different terminologies. While they have been mapped in a reasonably coherent way, juju terminology is confusing for the vsphere user coming to juju.
add-cloud's interactive mode could use more vsphere terminology. Instead of "API endpoint", it could say "Vcenter host" (bug #1649647). Instead of "region", it could say "Datacenter name".
Also, juju has mapped the "zone" placement directive to vsphere clusters and hosts. AIUI, placement directives are per-provider, so supporting "cluster" and "host" as placement directives for vsphere would be clearer.
The rough mapping of vsphere to juju terminology is:
Cloud -> Vcenter
Region -> Datacenter name
Zone -> Host or cluster
Changed in juju: | |
assignee: | nobody → Richard Harding (rharding) |
tags: | added: oil |
Changed in juju: | |
assignee: | Richard Harding (rharding) → nobody |
tags: |
added: vsphere-provider removed: vsphere |
Just adding 2c here... this seems fatuous. Semantics in technology are difficult, sure, but to ask for a rename of "cloud" to "vcenter" is... I can think of worse words to use than "pointless".