Open Stack

On 05/28/2015 10:47 AM, Jan Provaznik wrote:
> 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).
>
>
> __________________________________________________________________________ 
>
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Then I'm +1 for running Puppet with 'ensure => latest' first and then 
'yum update -y'. Seems ideal solution from my point of view.