[katello-devel] Modelling of environments, products, etc in Katello (related to renaming of environments)

Bryan Kearney bkearney at redhat.com
Fri Aug 10 00:05:58 UTC 2012


On 08/09/2012 12:37 PM, Cliff Perry wrote:
> On 08/09/2012 04:51 PM, Dmitri Dolguikh wrote:
>> Since uuids got no love, let's replace uuids with immutable
>> human-readable labels.
>> -d
>
> Hmm... random thoughts here.
>
> How often will rename of an environment actually happen?
>   - Continue to do not allow rename of an environment. If you really do
> not want to continue using an environment, I would think that:
>    - Would it be easier to allow customers to 'clone' an environment
> into a new Environment, then move systems from one environment to another.
>    - They would then retire (or delete) the old environment, when no
> longer used/needed.

The same issue is with products. As we put them into the url path, 
renames require regens of the certs.


>
> If you do wish to allow to rename an Environment.
>   - How will any proposed solution be impacted by upgrades? Can what you
> propose be implemented sanely to allow a current katello 1.0 user to
> consume/upgrade smoothly to this new model.
>   - I would vote for a unique immutable human-readable (assuming you
> have a latin based/derived alphabet) label. Or a numberic ID.
>    - I agree with Justin, that there was almost zero negative feedback
> in Satellite for customers wanting to change the label, as long as they
> could modify the description/name of the object.
>
> I know this could be its own thread... but IMHO using/feeding
> environment name/label into a yum URL is a bit limiting, if we have to
> restrict it and would propose that Environment name/label is not used
> but an arbitrary numeric ID, thus allowing Japanese, etc languages to be
> used in creation of an Environment name. (unless I am mistaken on how
> this works today).


The goal has been to make them somewhat readable since we are populating 
a repo file on disk.

-- bk







More information about the katello-devel mailing list