<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">On 14/08/12 02:07 PM, Bryan Kearney wrote: </div> <blockquote cite="mid:502A4D8E.8030602@redhat.com" type="cite">On 08/14/2012 09:04 AM, Dmitri Dolguikh wrote: <blockquote type="cite">On 14/08/12 02:01 PM, Bryan Kearney wrote: <blockquote type="cite">On 08/14/2012 07:17 AM, Dmitri Dolguikh wrote: <blockquote type="cite">On 13/08/12 11:13 PM, Mike McCune wrote: <blockquote type="cite">On 08/13/2012 08:00 AM, Dmitri Dolguikh wrote: <blockquote type="cite">On 13/08/12 03:57 PM, Justin Sherrill wrote: <blockquote type="cite">On 08/13/2012 10:55 AM, Dmitri Dolguikh wrote: <blockquote type="cite">On 13/08/12 03:52 PM, Justin Sherrill wrote: <blockquote type="cite">On 08/13/2012 10:45 AM, Dmitri Dolguikh wrote: <blockquote type="cite">This is a summary of the thread started at <a class="moz-txt-link-freetext" href="https://www.redhat.com/archives/katello-devel/2012-August/msg00102.html">https://www.redhat.com/archives/katello-devel/2012-August/msg00102.html</a>. Please see <a class="moz-txt-link-freetext" href="https://bugzilla.redhat.com/show_bug.cgi?id=795928">https://bugzilla.redhat.com/show_bug.cgi?id=795928</a> 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 <a class="moz-txt-link-abbreviated" href="mailto:katello-devel@redhat.com">katello-devel@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/katello-devel">https://www.redhat.com/mailman/listinfo/katello-devel</a> </blockquote> Any idea what the redhat.repo file will look like with numerical ids? Or yum repolist ? </blockquote> Same as now, but with environment uuids instead on environment names. -d </blockquote> </blockquote> Apologies, I didn't understand the question. The latter. -d <blockquote type="cite">So [123456] name=123456 baseurl=<a class="moz-txt-link-freetext" href="http://hostname/pulp/ACME_Corporation/123456/repo/">http://hostname/pulp/ACME_Corporation/123456/repo/</a> or [123456] name=Red Hat Enterprise Linux Server 6 RPMS baseurl=<a class="moz-txt-link-freetext" href="http://hostname/pulp/ACME_Corporation/123456/repo/">http://hostname/pulp/ACME_Corporation/123456/repo/</a> ? </blockquote> </blockquote> and this really blows for our users, IMHO. You go from a relatively readable and clear yum configuration file that a sysadmin can look at quickly and understand: [ACME_Corporation_zoo_zoorepo] name = zoorepo baseurl = <a class="moz-txt-link-freetext" href="https://katello.example.com/pulp/repos/ACME_Corporation/dev//custom/zoo/zoorepo">https://katello.example.com/pulp/repos/ACME_Corporation/dev//custom/zoo/zoorepo</a> enabled = 1 gpgcheck = 1 sslverify = 1 sslcacert = /etc/rhsm/ca/candlepin-local.pem sslclientkey = /etc/pki/entitlement/3783882558646362292-key.pem sslclientcert = /etc/pki/entitlement/3783882558646362292.pem to: [313024c0-c7bd-012f-d852-1803734d16c4] name = zoorepo baseurl = <a class="moz-txt-link-freetext" href="https://katello.example.com/pulp/repos/ACME_Corporation/83ef9ef0-c7bd-012f-d852-1803734d16c4//custom/zoo/313024c0-c7bd-012f-d852-1803734d16c4">https://katello.example.com/pulp/repos/ACME_Corporation/83ef9ef0-c7bd-012f-d852-1803734d16c4//custom/zoo/313024c0-c7bd-012f-d852-1803734d16c4</a> enabled = 1 gpgcheck = 1 sslverify = 1 sslcacert = /etc/rhsm/ca/candlepin-local.pem sslclientkey = /etc/pki/entitlement/3783882558646362292-key.pem sslclientcert = /etc/pki/entitlement/3783882558646362292.pem </blockquote> </blockquote> So, this pains me.. especially since tools like packagekit need to enable and disable repos. If there is a solution where the name and the id are Human Readable and "As close to locale as possible" then I am fine. Image how ugly this screen would look with UUIDS. </blockquote> My understanding is that the name does not have any constraints on what characters can be used. We could generate repository label (or w/e is used in the repo url using Product name, etc?) -d </blockquote> I would prefer the URl to be friendly, but I see how UUIDS will make it easier. So, give me a path where the IDs and names are as human readable as possible and I will be relent. </blockquote> Hmm. how about automatically generate labels in spirit of <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <a href="http://world.std.com/%7Ereinhold/diceware.html">http://world.std.com/~reinhold/diceware.html</a>? The trick would be guarantee uniqueness, I'll have to think about that... -d <blockquote cite="mid:502A4D8E.8030602@redhat.com" type="cite"> -- bk _______________________________________________ katello-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:katello-devel@redhat.com">katello-devel@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/katello-devel">https://www.redhat.com/mailman/listinfo/katello-devel</a> </blockquote> </body> </html>