- Original Message -
> From: "Corey Osman"
> To: "puppet-dev"
> Sent: Saturday, January 30, 2016 5:45:05 AM
> Subject: [Puppet-dev] RFC - A specification for module schemas
> Hi,
>
> I wanted to bring up a conversation in hopes that we as a community can
> create a
> specification fo
Hi,
I wanted to bring up a conversation in hopes that we as a community can create
a specification for something I am calling module schemas. Before I get into
that I want to provide a little background info.
This all started a few years ago when hiera first came out. Data seperation in
the f
On Fri, Jan 29, 2016 at 12:08 PM, Alex Harvey wrote:
> The main issue I still have, and I just checked again, is that too many
> Forge modules say in their documentation that they're only supporting
> Puppet 3. E.g. Logstash, Nginx. Now, maybe in actual fact they work fine
> in Puppet 4; and th
On Saturday, January 30, 2016 at 3:44:05 AM UTC+11, Chris Price wrote:
>
>
>
> On Fri, Jan 29, 2016 at 8:16 AM, Alex Harvey > wrote:
>
>> Yep, it's solved in Puppet 4 - the all-in-one package is fantastic, as is
>> so much in Puppet 4. However PE hasn't release Puppet 4 yet;
>>
>
> OSS Puppet
On Fri, Jan 29, 2016 at 8:16 AM, Alex Harvey wrote:
> Yep, it's solved in Puppet 4 - the all-in-one package is fantastic, as is
> so much in Puppet 4. However PE hasn't release Puppet 4 yet;
>
OSS Puppet 4 was released almost a year ago. Puppet 4 shipped in PE
2015.2.0 in July of last year. T
On Fri, 29 Jan 2016 at 17:16 Alex Harvey wrote:
> Yep, it's solved in Puppet 4 - the all-in-one package is fantastic, as is
> so much in Puppet 4. However PE hasn't release Puppet 4 yet; my assessment
> of the Puppet Forge is that not many modules out there are ready; and I am
> not super confid
On Saturday, January 30, 2016 at 3:26:23 AM UTC+11, Rob Nelson wrote:
>
> The ruby 1.8.7 that comes with EL6 and 2.0.0 with EL7 work fine. The
> vendor offers 1.9.3 and 2.2.0 in their SCL repos, respectively. What
> specifically is the problem that the "too many yaks to shave" complaints
> are
The ruby 1.8.7 that comes with EL6 and 2.0.0 with EL7 work fine. The vendor
offers 1.9.3 and 2.2.0 in their SCL repos, respectively. What specifically
is the problem that the "too many yaks to shave" complaints are referencing
that the vendor's base and SCL repos do not address?
This is a sincere
Yep, it's solved in Puppet 4 - the all-in-one package is fantastic, as is
so much in Puppet 4. However PE hasn't release Puppet 4 yet; my assessment
of the Puppet Forge is that not many modules out there are ready; and I am
not super confident that other tools in the ecosystem like Beaker,
Lib
SCL upstream comes from the vendor (
https://access.redhat.com/documentation/en-US/Red_Hat_Software_Collections/1/html-single/1.0_Release_Notes/index.html#appe-Documentation-1.0_Release_Notes-Revision_History)
so that sounds like the best solution in this case. Even if you move to
EL7, it provides
On Fri, Jan 29, 2016 at 2:04 AM, Erik Dalén
wrote:
> Well, there was an old thread here about this. The conclusions were
> summarized here: http://projects.puppetlabs.com/issues/2198#note-41
>
Yes, and that thinking was somewhat captured in this epic in Jira:
https://tickets.puppetlabs.com/brows
Isn't this already solved with the Puppet 4.x packaging (puppet-agent)? So
why insist on installing an old Puppet version instead of a modern one?
Personally I prefer that PuppetLabs is developing new features in Puppet
4.x instead of spending time improving packaging and stuff for Puppet 3.x.
On
Thanks for the heads up. Anything less than Puppet Labs providing a
working Ruby at yum.puppetlabs.com, or CentOS providing one, feels to me
like a bit of a hack. I've seriously got a customer wanting to ditch
Puppet and go to Ansible because because they just want it to be easy to
install op
Ruby 1.9.3 is available in the Software Collections (SCL) repository.
Instructions at
https://digitalchild.info/centos-6-5-and-ruby1-9-3-via-software-collections/
.
There may be some side effects for any system utilities that expect 1.8.7
but that's a risk you'll have to accept if you're still on
Well, there was an old thread here about this. The conclusions were
summarized here: http://projects.puppetlabs.com/issues/2198#note-41
AFAIK none of that has been implemented though. And perhaps bigger
refactorings of the RAL would be better to allow concurrent processing as
well as batching.
On
15 matches
Mail list logo
