<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:26 PM, Dmitri Dolguikh
wrote:<br>
</div>
<blockquote cite="mid:502A51FE.7010008@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 14/08/12 02:07 PM, Bryan Kearney
wrote:<br>
</div>
<blockquote cite="mid:502A4D8E.8030602@redhat.com" type="cite">On
08/14/2012 09:04 AM, Dmitri Dolguikh wrote: <br>
<blockquote type="cite">On 14/08/12 02:01 PM, Bryan Kearney
wrote: <br>
<blockquote type="cite">On 08/14/2012 07:17 AM, Dmitri
Dolguikh wrote: <br>
<blockquote type="cite">On 13/08/12 11:13 PM, Mike McCune
wrote: <br>
<blockquote type="cite">On 08/13/2012 08:00 AM, Dmitri
Dolguikh wrote: <br>
<blockquote type="cite">On 13/08/12 03:57 PM, Justin
Sherrill wrote: <br>
<blockquote type="cite">On 08/13/2012 10:55 AM, Dmitri
Dolguikh wrote: <br>
<blockquote type="cite">On 13/08/12 03:52 PM, Justin
Sherrill wrote: <br>
<blockquote type="cite">On 08/13/2012 10:45 AM,
Dmitri Dolguikh wrote: <br>
<blockquote type="cite">This is a summary of the
thread started at <br>
<a moz-do-not-send="true"
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>.
<br>
<br>
<br>
<br>
Please see <a moz-do-not-send="true"
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 <br>
details of the issue with environment
renaming. <br>
<br>
Quite a few folks suggested using of an
immutable label instead of <br>
environment name, but at the end the idea was
defeated by a <br>
comment <br>
from Cliff Perry about users from locales
using non-ascii-based <br>
character sets. <br>
Another issue that was discovered was the
migration of already <br>
established environments from current version
of Katello to the <br>
version containing the fix. My current
thinking is to use <br>
environment name value as uuid for "legacy"
environments. This <br>
would significantly simply upgrade, as there
will be no need to <br>
regenerate entitlement certificates, etc. <br>
<br>
Katello: <br>
- introduce environment uuids (update db
schema, model, etc) <br>
- update candlepin (this will include
updates to schema, and <br>
resource controller) <br>
- update katello/katello cli to use uuids
for environment <br>
identification <br>
- update repository-related functionality to
use environment <br>
uuids <br>
- figure out/create migration from 1.0 to
current <br>
<br>
Bryan, everything minus the migration bit is
probably a couple <br>
days <br>
worth of work. Should I create a new story, or
I can start on this <br>
right away? <br>
<br>
-d <br>
<br>
_______________________________________________
<br>
katello-devel mailing list <br>
<a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:katello-devel@redhat.com">katello-devel@redhat.com</a>
<br>
<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://www.redhat.com/mailman/listinfo/katello-devel">https://www.redhat.com/mailman/listinfo/katello-devel</a>
<br>
</blockquote>
Any idea what the redhat.repo file will look
like with numerical <br>
ids? Or yum repolist ? <br>
</blockquote>
Same as now, but with environment uuids instead on
environment <br>
names. <br>
-d <br>
</blockquote>
<br>
</blockquote>
Apologies, I didn't understand the question. The
latter. <br>
-d <br>
<blockquote type="cite">So <br>
<br>
[123456] <br>
name=123456 <br>
baseurl=<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://hostname/pulp/ACME_Corporation/123456/repo/">http://hostname/pulp/ACME_Corporation/123456/repo/</a>
<br>
<br>
or <br>
<br>
[123456] <br>
name=Red Hat Enterprise Linux Server 6 RPMS <br>
baseurl=<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://hostname/pulp/ACME_Corporation/123456/repo/">http://hostname/pulp/ACME_Corporation/123456/repo/</a>
<br>
<br>
<br>
? <br>
<br>
</blockquote>
</blockquote>
<br>
<br>
and this really blows for our users, IMHO. You go from
a relatively <br>
readable and clear yum configuration file that a
sysadmin can look at <br>
quickly and understand: <br>
<br>
[ACME_Corporation_zoo_zoorepo] <br>
name = zoorepo <br>
baseurl = <br>
<a moz-do-not-send="true" 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>
<br>
<br>
<br>
enabled = 1 <br>
gpgcheck = 1 <br>
sslverify = 1 <br>
sslcacert = /etc/rhsm/ca/candlepin-local.pem <br>
sslclientkey =
/etc/pki/entitlement/3783882558646362292-key.pem <br>
sslclientcert =
/etc/pki/entitlement/3783882558646362292.pem <br>
<br>
to: <br>
<br>
[313024c0-c7bd-012f-d852-1803734d16c4] <br>
name = zoorepo <br>
baseurl = <br>
<a moz-do-not-send="true" 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>
<br>
<br>
<br>
enabled = 1 <br>
gpgcheck = 1 <br>
sslverify = 1 <br>
sslcacert = /etc/rhsm/ca/candlepin-local.pem <br>
sslclientkey =
/etc/pki/entitlement/3783882558646362292-key.pem <br>
sslclientcert =
/etc/pki/entitlement/3783882558646362292.pem <br>
</blockquote>
</blockquote>
<br>
So, this pains me.. especially since tools like packagekit
need to <br>
enable and disable repos. If there is a solution where the
name and <br>
the id are Human Readable and "As close to locale as
possible" then I <br>
am fine. Image how ugly this screen would look with UUIDS. <br>
</blockquote>
My understanding is that the name does not have any
constraints on what <br>
characters can be used. We could generate repository label (or
w/e is <br>
used in the repo url using Product name, etc?) <br>
<br>
-d <br>
</blockquote>
<br>
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. <br>
</blockquote>
<br>
Hmm. how about automatically generate labels in spirit of
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true"
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...<br>
</blockquote>
<br>
Looking at pulp docs, I see that the base url in yum repository
configuration file, and the url used to access repositories via pulp
API are completely different. As long the urls used in yum
configuration file are not being used to access resources managed
directly by Katello, and as long as Pulp doesn't enforce uniqueness
of those urls, I think we can make them as human readable as we'd
like.<br>
<br>
Alternatively, we could use a couple approaches to make uuids more
human readable, but at the expense of length. One approach would be
to break up uuid into eight 16-bit groups, and then use each group
as an index in the common dictionary. <br>
<br>
Yet another approach would be to use Bubble Babble encoding (
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="http://wiki.yak.net/589/Bubble_Babble_Encoding.txt">http://wiki.yak.net/589/Bubble_Babble_Encoding.txt)</a>
on uuid. In that case, <a moz-do-not-send="true"
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">83ef9ef0-c7bd-012f-d852-1803734d16c4</a>
will be converted to
xobov-zyloz-byxox-xucor-toxax-xebed-zyxox-xukah-doxix-xekab-fosig-tuhes-guxix.<br>
<br>
I don't think either of those are worth the effort, however.<br>
-d<br>
<br>
<blockquote cite="mid:502A51FE.7010008@redhat.com" type="cite"> <br>
-d<br>
<blockquote cite="mid:502A4D8E.8030602@redhat.com" type="cite"> <br>
-- bk <br>
<br>
<br>
<br>
_______________________________________________ <br>
katello-devel mailing list <br>
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:katello-devel@redhat.com">katello-devel@redhat.com</a>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://www.redhat.com/mailman/listinfo/katello-devel">https://www.redhat.com/mailman/listinfo/katello-devel</a>
<br>
</blockquote>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
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></pre>
</blockquote>
<br>
<br>
</body>
</html>