On Tuesday, November 18, 2014 3:35:25 AM UTC-6, Mike Hendon wrote:
>
>* Please note that some changes in puppet 4 mean that puppet 3 agents
> won’t be able to talk to puppet 4 masters (or vice-versa).
>
> This might cause an issue.
> I would suggest that the puppet RPMs are renamed to someth
* Please note that some changes in puppet 4 mean that puppet 3 agents
won’t be able to talk to puppet 4 masters (or vice-versa).
This might cause an issue.
I would suggest that the puppet RPMs are renamed to something like puppet4
so that unexpected breakages don't occur.
--
You received th
On Nov 17, 2014, at 2:19 PM, Peter Meier wrote:
> And how will the release plan of PL looks like regarding 4.0? Will we
> end up with having 4.0 in the repositories one day and all the people
> that sync the repo (or directly update from it) will just update?
>
> Or will someone take over the d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> Please note that some changes in puppet 4 mean that puppet 3
>> agents won’t be able to talk to puppet 4 masters (or vice-versa).
>> This probably means you don’t want to be updating puppet itself
>> with “ensure => latest” :)
>>
> point taken, but
On Mon, Nov 17, 2014 at 6:22 AM, Byron Miller wrote:
> I for one would love to feel more safe when tempting fate upgrading my
> puppet infrastructure. I like the idea of rolling upgrades (if upgraded,
> point here), but i would love to have some sort of process in puppet to
> handle this. A confi
I for one would love to feel more safe when tempting fate upgrading my
puppet infrastructure. I like the idea of rolling upgrades (if upgraded,
point here), but i would love to have some sort of process in puppet to
handle this. A configuration/feature flag that says "hey puppet, we're
upgradin
On Fri, Nov 14, 2014 at 4:02 PM, Erik Dalén
wrote:
>
>
> On Fri Nov 14 2014 at 7:16:07 PM Felix Frank <
> felix.fr...@alumni.tu-berlin.de> wrote:
>
>> On 11/14/2014 07:09 PM, Henrik Lindberg wrote:
>> >
>> > Please note that some changes in puppet 4 mean that puppet 3 agents
>> > won’t be able to
On Fri Nov 14 2014 at 7:16:07 PM Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> On 11/14/2014 07:09 PM, Henrik Lindberg wrote:
> >
> > Please note that some changes in puppet 4 mean that puppet 3 agents
> > won’t be able to talk to puppet 4 masters (or vice-versa). This probably
> > means
On 11/14/2014 07:09 PM, Henrik Lindberg wrote:
>
> Please note that some changes in puppet 4 mean that puppet 3 agents
> won’t be able to talk to puppet 4 masters (or vice-versa). This probably
> means you don’t want to be updating puppet itself with “ensure => latest” :)
>
Hi,
point taken, but
** Next PR Triage Wednesday, November 19th @ 10:00 am Pacific. **
Priorities
1.
Puppet 3.7.4
2.
Native Facter 0.3.0
3.
Puppet Server 1.0.0
4.
Code removal for puppet 4
5.
New puppet doc implementation
Commentary
Puppet:
We are going
Sorry a bout the botched format... investigating
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To view this discu
11 matches
Mail list logo
