On Tue, Apr 07, 2015 at 07:12:42PM -0400, Zane Bitter wrote:
On 07/04/15 05:13, Steven Hardy wrote:
On Thu, Apr 02, 2015 at 06:31:39PM -0400, Zane Bitter wrote:
A few of us have been looking for a way to perform software updates to
servers in a TripleO Heat/Puppet-based overcloud that avoids
On Thu, Apr 02, 2015 at 06:31:39PM -0400, Zane Bitter wrote:
A few of us have been looking for a way to perform software updates to
servers in a TripleO Heat/Puppet-based overcloud that avoids an impedance
mismatch with Heat concepts and how Heat runs its workflow. As many talented
TripleO-ers
On 07/04/15 05:13, Steven Hardy wrote:
On Thu, Apr 02, 2015 at 06:31:39PM -0400, Zane Bitter wrote:
A few of us have been looking for a way to perform software updates to
servers in a TripleO Heat/Puppet-based overcloud that avoids an impedance
mismatch with Heat concepts and how Heat runs its
On 03/04/15 01:29, Giulio Fidente wrote:
hi there,
thanks for sharing this, I have a
On 04/03/2015 12:31 AM, Zane Bitter wrote:
A few of us have been looking for a way to perform software updates to
servers in a TripleO Heat/Puppet-based overcloud
[...]
Here's a trivial example of what
On 02/04/15 20:31, Fox, Kevin M wrote:
I'm not sure how to feel about this... Its clever...
That's... unfortunate ;)
Ideally this would sound like something that is a natural fit for Heat's
data model. The reason it's not is that config management tools like
Puppet are less sophisticated
Hi,
On Fri, Apr 3, 2015 at 1:31 AM, Zane Bitter zbit...@redhat.com wrote:
A few of us have been looking for a way to perform software updates to
servers in a TripleO Heat/Puppet-based overcloud that avoids an impedance
mismatch with Heat concepts and how Heat runs its workflow. As many
...@redhat.com]
Sent: Thursday, April 02, 2015 3:31 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [TripleO][Heat] Overcloud software updates and
ResourceGroups
A few of us have been looking for a way to perform software updates to
servers in a TripleO Heat/Puppet-based overcloud
A few of us have been looking for a way to perform software updates to
servers in a TripleO Heat/Puppet-based overcloud that avoids an
impedance mismatch with Heat concepts and how Heat runs its workflow. As
many talented TripleO-ers who have gone before can probably testify,
that's
hi there,
thanks for sharing this, I have a
On 04/03/2015 12:31 AM, Zane Bitter wrote:
A few of us have been looking for a way to perform software updates to
servers in a TripleO Heat/Puppet-based overcloud
[...]
Here's a trivial example of what this deployment might look like:
