[katello-devel] Renaming of environments: summary, take II

[Dmitri Dolguikh]

Please see original conversation thread [1], first attempt at summary 
[2], and BZ [3] for details.

The majority of the conversation revolved around use of human-readable 
ids to preserve user-friendiness of urls vs. using uuids to preserve 
data consistency of client applications that use Katello API. Another 
concern expressed was readability of repository urls genereated by 
Katello in yum configuration files. It was suggested to use Punycode for 
encoding of non-ascii-based labels.

Proposed changes:
  - introduce immutable labels
  - replace use of environment name with environment label in urls not 
impacting data integrity, such as repository urls. This would eliminate 
the need for entitlement certificate regeneration after environment name 
changes
  - introduce uuids, and replace current use of primary db keys in 
resource urls with uuids

Tasks on Katello side:
  - take a look at and implement Punycode
  - introduce environment labels: db changes, model changes, controller 
changes
  - introduce uuids: db changes, model changes, controller changes
  - figure out migration for existing Katello installations

Tasks on Candlepin side:
  - add label and uuid fields to model. Replace use of environment names 
with environment labels



[1] https://www.redhat.com/archives/katello-devel/2012-August/msg00102.html
[2] https://www.redhat.com/archives/katello-devel/2012-August/msg00144.html
[3] https://bugzilla.redhat.com/show_bug.cgi?id=795928
[4] http://en.wikipedia.org/wiki/Punycode

-d
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/katello-devel/attachments/20120815/b8cea258/attachment.htm>