[katello-devel] registering to Library

Bryan Kearney bkearney at redhat.com
Wed May 15 13:26:13 UTC 2013


On 05/15/2013 09:00 AM, Tom McKay wrote:
>
>
> ----- Original Message -----
>> From: "Tom McKay" <thomasmckay at redhat.com>
>> To: "katello-devel" <katello-devel at redhat.com>
>> Sent: Tuesday, May 14, 2013 5:14:15 PM
>> Subject: Re: [katello-devel] registering to Library
>>
>>
>>
>> ----- Original Message -----
>>> From: "Tom McKay" <thomasmckay at redhat.com>
>>> To: "katello-devel" <katello-devel at redhat.com>
>>> Sent: Tuesday, May 14, 2013 1:58:40 PM
>>> Subject: [katello-devel] registering to Library
>>>
>>>
>>> I've just merged a pull-request [1] to allow registering systems to
>>> Library.
>>>
>>> For katello, registering to Library will mean that all content sync'ed down
>>> will be accessible to the system.
>>>
>>> For headpin, the implications are broader. Since headpin only proxies
>>> content
>>> directly from the CDN, environments had little value other than a way to
>>> organize them. With this change, there will only ever be the Library
>>> environment in headpin, but system groups are now available. This will
>>> hopefully keep the notion of both environments and groups consistent
>>> between
>>> katello and headpin.
>>>
>>> A migration script is in the works to update legacy headpin installs.
>>> 1) All systems moved to Library env
>>> 2) A system group will be made for each existing env
>>> 3) Systems will be added to appropriate system group
>>> 4) All users with a default system registration env will have that changed
>>> to
>>> Library
>>> 5) All activation keys will be switched to Library
>>> 6) RFE for the backlog: Allow system groups to be assigned to activation
>>> keys.
>
> It looks like setting a system group on an activation key is already there. Very nice.
>
> 6) Existing activation keys will point to appropriate system group


Good ideas on the migratoin script.
-- bk





More information about the katello-devel mailing list