Prepare for charmhub release
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charm-infra-node |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
As the charm's code has now been released publicly, the next step is to get this onto charmhub.
Based on team discussion:
* As "infra-node" is likely too generic a name, especially on charmhub which lacks user/group namespacing, we've decided to rename this charm to "maas-ops".
* So this charm may work nicely with future principal charms (e.g. maybe a future MAAS charm?), this charm should be reworked to be a subordinate charm. The current pattern would be for us to deploy an ubuntu principal onto the MAAS infra nodes and relate it with maas-ops as a subordinate.
Definition of done:
* Charm is renamed, reworked into a subordinate charm, tested successfully, and deployed to the charm store for public consumption.
* Ideally, this project should also be renamed to charm-maas-ops to match the new charm name. CI will likely also need to be updated if this is done.
| Eric Chen (eric-chen) wrote | #1 |
| Changed in charm-infra-node: | |
| status: | New → Won't Fix |
This charm is under maintenance mode. Only critical bug will be handled.