[katello-devel] Renaming of environments: summary

[Jason Rist]

On Mon 13 Aug 2012 08:45:46 AM MDT, Dmitri Dolguikh wrote:
> This is a summary of the thread started at
> https://www.redhat.com/archives/katello-devel/2012-August/msg00102.html.
> Please see https://bugzilla.redhat.com/show_bug.cgi?id=795928 for
> details of the issue with environment renaming.
>
> Quite a few folks suggested using of an immutable label instead of
> environment name, but at the end the idea was defeated by a comment
> from Cliff Perry about users from locales using non-ascii-based
> character sets.
> Another issue that was discovered was the migration of already
> established environments from current version of Katello to the
> version containing the fix. My current thinking is to use environment
> name value as uuid for "legacy" environments. This would significantly
> simply upgrade, as there will be no need to regenerate entitlement
> certificates, etc.
>
> Katello:
>  - introduce environment uuids (update db schema, model, etc)
>  - update candlepin (this will include updates to schema, and resource
> controller)
>  - update katello/katello cli to use uuids for environment identification
>  - update repository-related functionality to use environment uuids
>  - figure out/create migration from 1.0 to current
>
> Bryan, everything minus the migration bit is probably a couple days
> worth of work. Should I create a new story, or I can start on this
> right away?
>
> -d
>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel


Dmitri - I'd like to thank you for setting the precedent of summarizing 
the email chain that you started.  This is so helpful for those of us 
that a) have a hard time tracking such a long conversation and b) want 
to get an understanding of the expectations and scope of these types of 
changes.

That said,  I agree with the points you've laid out. This seems like a 
valid way forward.  Can we use the current naming if it already exists 
rather than reassigning or migrating to a UUID?

-J
--
Jason E. Rist
Senior Software Engineer
Systems Management and Cloud Enablement
Red Hat, Inc.
+1.919.754.4048
Freenode: jrist