[katello-devel] Promotion topics for consideration
Tomas Strachota
tstrachota at redhat.com
Thu Aug 11 08:08:45 UTC 2011
Hi,
On 04/08/11 19:36, Bryan Kearney wrote:
> On 08/03/2011 10:03 AM, Todd Sanders wrote:
>> On 08/02/2011 02:17 PM, Justin Sherrill wrote:
>>> Hi,
>>>
>>> A few questions around promotions:
>>>
>>> 1. Currently if you have a new product, you can only promote the
>>> product and all its contents initially. Meaning that normally, I would
>>> sync a new product, and in order to get it to the next environment I
>>> would promote it across my entire path, promoting all of the content
>>> of the product initially. Is this correct?
>>
>> So I think this is the correct behavior; however we do need to ensure we
>> have a solution for customers that want to seed their environments with
>> a specific point release (i.e RHEL 6.1), and then manage only additional
>> RHSAs. I'll start looking into this scenario.
>>
>> I also think that filters (whitelist & blacklist) is key here. We need
>> to get this functionality in place as well.
>>
>>>
>>> 2. Currently in the UI we allow you to select content for promotion on
>>> products that have not been promoted. This was mainly due to to the
>>> lack of stability in that area.
>>
>> Yes, we should not allow you to select specific content for promotion
>> for a product that is not in the environment you are promoting to. Until
>> you have seeded the environment with the product, you are limited.
>>
>>> I believe this was interpreted differently because the current backend
>>> code will promote the full product X if you select to promote a
>>> package in X and it doesn't exist in the next environment.
>>
This is my fault. I did misunderstood the idea. I'm already working on
changes in validations that will fix it.
>> Yes. Sounds like this is just another area that needs refactoring to be
>> consistent across the board.
>>
>> BK - can you add backlog stories to correct this behavior?
>>
>>>
>>> You shouldn't be able to even select a package in product X if X is
>>> not in the next environment, correct?
>>
>> Absolutely correct.
>>
>> -Todd
>
> I will add this, but I am concerned with the apporach of "next env"
> logic. That means when we get to paths with more that one next, we will
> have to clone change sets instead of reusing them.
>
> -- bk
>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel
More information about the katello-devel
mailing list