On 05/28/2015 08:24 PM, Zane Bitter wrote:
On 28/05/15 03:35, 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:
Steve is working on a patch to allow package-based updates of
overcloud
nodes[1] using the distro's
On 05/28/2015 05:32 PM, James Slagle wrote:
Then I'm +1 for running Puppet with 'ensure = latest' first and then 'yum
update -y'. Seems ideal solution from my point of view.
How would this solve the library update problem though?. If a new
version of a library is released to address a security
On 28/05/15 03:35, 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:
Steve is working on a patch to allow package-based updates of overcloud
nodes[1] using the distro's package manager (yum in the case of RDO,
but
From: Zane Bitter [zbit...@redhat.com]
Sent: Thursday, May 28, 2015 11:24 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [TripleO] [Puppet] Package updates strategy
On 28/05/15 03:35, Jan Provaznik wrote:
On 05/28/2015 01:10 AM, Steve Baker wrote:
On 28/05
Excerpts from Zane Bitter's message of 2015-05-28 11:24:33 -0700:
On 28/05/15 03:35, 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:
Steve is working on a patch to allow package-based updates of overcloud
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
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
On 05/28/2015 01:10 AM, Steve Baker wrote:
On 28/05/15 10:54, Richard Raseley wrote:
Zane Bitter wrote:
Steve is working on a patch to allow package-based updates of overcloud
nodes[1] using the distro's package manager (yum in the case of RDO, but
conceivable apt in others). Note we're
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
On Thu, May 28, 2015 at 5:02 AM, Martin Mágr mm...@redhat.com wrote:
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:
Steve is working on a patch to allow package-based updates of overcloud
nodes[1] using the distro's package manager (yum in the case of RDO, but
conceivable apt in others). Note we're talking exclusively about minor
updates, not version-to-version upgrades here.
Dan mentioned
On 28/05/15 10:54, Richard Raseley wrote:
Zane Bitter wrote:
Steve is working on a patch to allow package-based updates of overcloud
nodes[1] using the distro's package manager (yum in the case of RDO, but
conceivable apt in others). Note we're talking exclusively about minor
updates, not
12 matches
Mail list logo
