[katello-devel] Where should subscriptions be?

[Bryan Kearney]

On 07/16/2012 12:49 PM, Mike McCune wrote:
> On 07/12/2012 07:30 AM, Bryan Kearney wrote:
>> Questions from some design sessions on Foreman integration. Where should
>> we tie subscriptions to?
>>
>> We could put them onto the the component outline to say "Any system
>> provisioned from this outline should consume from this subscription".
>> This is better for the case where you create the system record first,
>> and then provision it.
>>
>> Or, we could put them on the activation key which would say "When you
>> register this machine with this key, you get this subscription". This is
>> better when you provision outside of katello and then register the
>> machine back.
>
> +1
>
> I know this is how it is done in Satellite and I don't want to blindly
> just do it like we did before but it worked well to have one central
> concept that tied a subscription to a registration point.
>
>
>>
>> Or, we could put them on both, and have some logic about how to handle
>> the case when it is on both. Or, perhaps, every component outline gets
>> an activation key?
>>
>
> just have every component outline have an activation key.  Let the akeys
> be the central location for quickly assigning a subscription to a
> system.  You can use them outside a system template or embed them.


I am fine with the model now being "Subscriptions are on keys, not on 
CO". when to auto-create keys can be a different story.. but I like that 
model.

-- bk