[openstack-dev] [TripleO] [Puppet] Package updates strategy

Jan Provaznik jprovazn at redhat.com
Thu May 28 08:47:24 UTC 2015


On 05/28/2015 10:25 AM, Martin Mágr wrote:
>
> On 05/28/2015 09:35 AM, Jan Provaznik wrote:
>> On 05/28/2015 01:10 AM, Steve Baker wrote:
>>> On 28/05/15 10:54, Richard Raseley wrote:
>>>> Zane Bitter wrote:
>>>>>
>>>>>
>>>>> One solution proposed was to do a yum update first but specifically
>>>>> exclude any packages that Puppet knows about (the --excludes flag
>>>>> appears sufficient for this); then follow that up with another Puppet
>>>>> run using ensure -> latest.
>>>>>
>>> My only concern with this approach is how do we collect and maintain the
>>> excludes list. Other than that it sounds reasonable.
>>
>> Why not swap the order? First run puppet using ensure=>latest which
>> updates/restarts everything Openstack depends on, then run yum/apt
>> update to update any remaining bits. You wouldn't need exclude list then.
>
> Isn't running Puppet with 'ensure => latest' enough? If packaging is
> correct all dependencies which will require update will be updated
> together with packages updated by Puppet. Am I missing something or the
> goal here is to update all packages?
>

Yes - the goal so to update all packages (so puppet only is not 
sufficient because it will not take care of packages which are not 
listed in puppet modules).




More information about the OpenStack-dev mailing list