<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:01 PM, Bryan Kearney
wrote:<br>
</div>
<blockquote cite="mid:502A4C0D.6060609@redhat.com" 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 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>
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
<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 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 uuids
<br>
- figure out/create migration from 1.0 to current
<br>
<br>
Bryan, everything minus the migration bit is
probably a couple 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 class="moz-txt-link-abbreviated" href="mailto:katello-devel@redhat.com">katello-devel@redhat.com</a>
<br>
<a 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 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 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 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 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>
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 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>
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
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.
<br>
</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?)<br>
<br>
-d<br>
<blockquote cite="mid:502A4C0D.6060609@redhat.com" type="cite">
<br>
-- bk
<br>
<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>