Charm name is confusing
Bug #1999290 reported by
Vern Hart
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Loadbalancer Charm |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
Why is this charm have "openstack" in its name? There doesn't appear to be anything openstack-specific about this charm.
It seems to be especially confusing when used in a deployment that is NOT openstack.
Why not just call it loadbalancer?
Revision history for this message
| Alex Kavanagh (ajkavanagh) wrote | #1 |
| Changed in charm-openstack-loadbalancer: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
To post a comment you must log in.
> Why is this charm have "openstack" in its name? There doesn't appear to be anything openstack-specific about this charm.
It's intended usage was originally for OpenStack systems. It's great that it is being used elsewhere! At the time, it probably just seemed like a good idea to associate it with OpenStack.
> Why not just call it loadbalancer?
There's quite a lot of work in renaming *all* of the artefacts associated with renaming a charm, so there'd need to be a really compelling reason to do so - and not saying that "it's confusing when not used in an OpenStack system", isn't a good reason.
Even if we went with just renaming the charm (i.e. not the repositories, etc), this will cause work for people currently using the openstack-