migrations should support renaming of models
Bug #1649738 reported by
Menno Finlay-Smits
This bug affects 7 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
It should be possible to rename a model during a model migration. This is necessary because the possibility of model name collisions is likely.
Before this can be done, we need to audit all providers to check where model names are being used to tag instances, storage, security groups etc. A model can not be renaming if the model name is used to tag cloud resources.
| tags: | added: model-migration |
| Changed in juju: | |
| status: | New → Triaged |
| Changed in juju: | |
| milestone: | 2.1.1 → 2.2.0 |
| Changed in juju: | |
| milestone: | 2.2-beta1 → 2.2-beta2 |
| Changed in juju: | |
| milestone: | 2.2-beta2 → 2.3-alpha1 |
| Changed in juju: | |
| importance: | High → Wishlist |
| milestone: | 2.3-beta1 → none |
Revision history for this message
| Graeme Moss (graememoss) wrote | #1 |
To post a comment you must log in.
What is the the plan on this it seems that it's a major problem as time passes models need to either have new names.
from the sounds of the problem models don't have uuid or an ID to make them unique and so everything works off the name and not a uuid surely this is not the case and should be a case of making sure that everything is using the uuid?
I'm interest if any investigation has been done or if this has just been left and forgotten?