Foreman doesn't support puppet 4.x yet. Lots of open tickets :)
On Friday, July 24, 2015 at 7:11:08 AM UTC-5, Dirk Heinrichs wrote:
>
> Am 24.07.2015 um 12:59 schrieb Felix Frank:
>
> If you need a good ENC, look at Foreman. If you need reporting, look at
> puppetboard or Puppet Explorer.
>
>
Am 24.07.2015 um 12:59 schrieb Felix Frank:
> If you need a good ENC, look at Foreman. If you need reporting, look at
> puppetboard or Puppet Explorer.
Is any of those ready for Puppet 4? At least Foreman 1.9 (current
development version) doesn't seem to be. There is an open ticket, though...
By
On 07/23/2015 12:45 AM, Stack Kororā wrote:
>
> It also appears to me that puppet dashboard is not yet ready for 4.
> Anyone have any thoughts on that?
Hi,
the dashboard was discontinued, afaik, so it may never be "ready" to
work with Puppet 4+.
If you need a good ENC, look at Foreman. If you n
On Wednesday, July 22, 2015 at 4:06:51 PM UTC-5, Kevin Corcoran wrote:
>
>
> We added a new feature in Puppet Server 2.1.0 which allows it to be used
> with Puppet 3 agents (as well as Puppet 4 agents, of course).
>
>
> https://docs.puppetlabs.com/puppetserver/latest/release_notes.html#whats-new
On 07/22/2015 11:06 PM, Kevin Corcoran wrote:
> Hi,
>
> We added a new feature in Puppet Server 2.1.0 which allows it to be
> used with Puppet 3 agents (as well as Puppet 4 agents, of course).
>
> https://docs.puppetlabs.com/puppetserver/latest/release_notes.html#whats-new-in-puppet-server-21
>
> -
On Tue, Jul 21, 2015 at 9:33 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> On 07/21/2015 04:14 PM, jcbollinger wrote:
>
>
>> 2)
>> I read in the changelog that the older clients should work with the
>> backward compatibility, but is it worth even trying? Or should I just push
>> out
One last update on my progress.
I have 4 installed on Scientific Linux with the only client being itself at
the moment. The current plan is to either find replacement modules or move
over as many modules as I can. If I can get the bulk of the modules and a
few important ones, then I will be ver
On Tuesday, July 21, 2015 at 11:33:29 AM UTC-5, Felix.Frank wrote:
>
> On 07/21/2015 04:14 PM, jcbollinger wrote:
>
>
>> 2)
>> I read in the changelog that the older clients should work with the
>> backward compatibility, but is it worth even trying? Or should I just push
>> out the update
On Tuesday, July 21, 2015 at 9:44:45 AM UTC-5, Martijn wrote:
>
> Op dinsdag 21 juli 2015 01:28:09 UTC+2 schreef Stack Kororā:
>>
>> If I am willing to take the time to migrate to puppet-forge modules
>> anyway (plus hopefully fix any bad code I can't replace), wouldn't this be
>> a good time t
On Tuesday, July 21, 2015 at 9:14:04 AM UTC-5, jcbollinger wrote:
>
>
>
>> Questions!
>>
>> 1a)
>> I am debating as to whether I need to build multiple puppet masters or
>> not. Is the following documentation still valid for the 4.x series of
>> puppet?
>> https://docs.puppetlabs.com/guides/
On 07/21/2015 04:14 PM, jcbollinger wrote:
>
>
> 2)
> I read in the changelog that the older clients should work with
> the backward compatibility, but is it worth even trying? Or should
> I just push out the updated puppet client wherever I can before
> adding the server into m
Op dinsdag 21 juli 2015 01:28:09 UTC+2 schreef Stack Kororā:
>
> If I am willing to take the time to migrate to puppet-forge modules anyway
> (plus hopefully fix any bad code I can't replace), wouldn't this be a good
> time to switch puppet versions too?
>
I would definitely think so, but one th
On Monday, July 20, 2015 at 6:28:09 PM UTC-5, Stack Kororā wrote:
>
> Greetings,
>
> First, a short intro. :-)
>
> Last year I invested quite a bit of time building out a puppet
> infrastructure. I have +150 Scientific Linux 6 and RHEL 6 servers running
> puppet 3.7.1. It has been working real
13 matches
Mail list logo