----- Original Message -----
From: "Michael Stahnke" <stahnma(a)puppetlabs.com>
To: "EPEL Development List" <epel-devel(a)lists.fedoraproject.org>
Sent: Tuesday, October 1, 2013 11:25:06 PM
Subject: Re: EPEL Updating Puppet to 2.7.x
On Wed, Aug 7, 2013 at 4:22 PM, Jeff Sheltren <jeff(a)tag1consulting.com>
> On Wed, Aug 7, 2013 at 9:43 AM, Kevin Fenzi <kevin(a)scrye.com> wrote:
>> So, could you remind us again of the various interactions of the
>> versions? (or is there a doc on it?)
>> Ie, of 2.6, 2.7, 3.0, which versions clients can talk to which versions
So 2.6 clients should be able to talk with 2.7.x masters. The later
2.7.x stuff is even better with more helpful warnings and deprecation
> I'm not sure about 2.7 -> 3.0, but for the sake of this discussion perhaps
> what's important is that 2.6 clients and/or servers don't get along with
> clients and/or servers. So any existing client or server using EPEL puppet
> will need to be updated at the same time.
>> Also, is there any changes people would need to make to their puppet
>> manifests between 2.6 and 2.7?
The main things are:
Service resource types by default have has_status => true in 2.7.x
(which was mostly of the time manually set in 2.6.x by people
authoring code anyway).
Yeah, this shouldn't really cause issues. Most people already used it to get status
I think there was one other item, but I can't for the life of me
remember it right now. There also is some ill-defined behavior in
2.7.x on using Class/Variable names with a hyphen in them. I'd advice
This was in a lead-up to 3.x where you can't use hyphens in class names. I believe
it's just a deprecation warning, though, so that shouldn't directly affect
> I think there are some small things here, but should mostly just work --
> able to share some (relatively simple) configs between 2.6 and 2.7
> servers/clients with no issues. If someone could provide more detail than
> that, I'd appreciate it :)
Sam, any idea where this is at?
I'm ready to flip the switch. I haven't heard any strong opposition so I'll
start the update process.
Yell if you're in opposition or forever hold your peace.
>> In general I'm in favor of getting it updated...
> +1, just hate the surprise breakage for those that don't see this coming...
> epel-devel mailing list
epel-devel mailing list