to get your
submission in by 30 July because we won’t be extending the CFP deadline
this year.
We look forward to seeing your ideas for live stream (and in-person) talks,
and seeing more people and topics represented on the virtual stage at
Puppetize Live.
*Michael Stahnke*
*Director of Engineeri
anywhere we can get rid of it, I'm in favor.
>
> [1] https://github.com/stahnma/puppet-agent/commit/
> 02faa1ab51f74ddb827ca1c3f5da5c3ab9c17a20 (assuming, this is your repo?)
>
> Regards,
> Stefan
>
> - Original Message -
> > From: "Michael Stahnke&
In my spare time, I build out puppet-agents for Raspberry pis, because I
like pain and ARM boards.
I finally got Debian Stretch Working for armhf.
Debian 9
http://unsupported.s3.amazonaws.com/puppet-agent_5.
4.0.412.g8f7446e2-1stretch_armhf.deb
Debian 8
http://unsupported.s3.amazonaws.com/puppe
as well as the
sessions. Join us a day early for the contributor summit for open forums
if that works for you.
I want to invite you to come, but time is running out for the cheaper
tickets. Today is the last day for the 20% off price.
Michael Stahnke
Director of Engineering
--
You received th
A critical bug was reported (PUP-6608) that is affecting a significant
number of users in the Puppet 4.6.0 (puppet-agent 1.6.0) release, we are
pulling 4.6.0, and will be shipping 4.6.1 later this afternoon
Mike Stahnke
Release Engineering
--
You received this message because you are subscribe
It's up on nightlies, we've been building against the RCs.
http://nightlies.puppetlabs.com/puppet-agent-latest/repos/apt/xenial/pool/PC1/p/puppet-agent/
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop rec
Hey thanks for that feedback. If we could have that in a Jira ticket, it'd
be more likely to get attention, as we could get it to the right folk to
look at. I know I am always interested in feedback on our AIX work, because
all customers/users do not use it the same way.
File a ticket in the PUP p
tlabs.com/browse/PA/
[4] https://tickets.puppetlabs.com/browse/CPR/
Michael Stahnke
Release Engineering
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an ema
We also don't have wily packages up, so if the first bug was fixed, I don't
think it would work. It's a work in progress.
You can follow https://tickets.puppetlabs.com/browse/CPR-213 for more
information.
On Thu, Nov 5, 2015 at 7:05 AM, Markus Birth wrote:
> I can't install Puppet from the offi
On Tue, Nov 3, 2015 at 6:48 PM, Ryan Anderson
wrote:
> I've gotten puppet open source 3.7.x working on AIX, I haven't updated to
> 3.8, but I'm sure that would be trivial. The steps are basically:
> - Install the ruby 2.0.0 AIX rpm from perzl.org, plus its dependencies
> - Create directories: mkd
On Mon, Nov 2, 2015 at 11:46 AM, Jean-Francois Gratton
wrote:
> Hi,
>
> I've looked around to find an answer, all I could find seemed to be badly
> outdated.
>
> I'm looking to either sources or binaries to get a Puppet 3.8.x agent
> working on AIX 7.x .
>
Welcome to the fun :)
>
> I understand
On Mon, Oct 12, 2015 at 9:51 AM, Fabrice Bacchella <
fabrice.bacche...@orange.fr> wrote:
>
> > Le 12 oct. 2015 à 18:01, Michael Stahnke a
> écrit :
>
> > With transparency comes the ability to see things that are not perfect.
> We had a large conference last week
On Sat, Oct 10, 2015 at 2:54 AM, Fabrice Bacchella <
fabrice.bacche...@orange.fr> wrote:
> Same player shot again :
>
> https://tickets.puppetlabs.com/browse/PUP/fixforversion/14801/?selectedTab=com.atlassian.jira.plugins.jira-development-integration-plugin:release-report-tabpanel
>
> Version pupp
On Wed, Sep 30, 2015 at 6:34 AM, Trevor Vaughan
wrote:
> Hi Eric,
>
> Will a CVE be issued for this?
>
Yes
>
> Thanks,
>
> Trevor
>
> On Wed, Sep 30, 2015 at 12:47 AM, Eric Sorenson <
> eric.soren...@puppetlabs.com> wrote:
>
>> We've identified and are fixing a condition in puppet where the
>>
On Tue, Sep 22, 2015 at 12:40 PM, Kenton Brede wrote:
> I'm wondering the same thing here.
>
> Sorry, missed this thread the first time.
> Kent
>
> On Wed, Jul 22, 2015 at 6:28 PM, Ellison Marks wrote:
>
>> So, I'm going through the dance of upgrading to puppet 4.2 from 3.8 on
>> CentOS 6, and
Short answer, yes there are plans, but we haven't scheduled the work yet.
We know it's painful right now, and I'm sorry for that. I'll see we can get
that slotted in soon.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this
On Wed, Aug 26, 2015 at 9:54 PM, Michael Stahnke
wrote:
>
>
> On Wed, Aug 26, 2015 at 10:56 AM, Ellison Marks wrote:
>
>> We ran into a couple issues, all on centos6.
>>
>> Several package conflicts. Had to remove the puppetlabs-release package
>> to get t
On Wed, Aug 26, 2015 at 10:56 AM, Ellison Marks wrote:
> We ran into a couple issues, all on centos6.
>
> Several package conflicts. Had to remove the puppetlabs-release package to
> get the puppetlabs-release-pc1 package to install. New puppetserver package
> didn't obsolete the old puppet-serve
We had been talking about this internally for a bit as well.
Basically, we have a couple things we'd like to do.
1. In the Puppet Collections Paradigm, we are no longer removing items.
2. In the old production repos, we will still be removing items (to
eventually phase those repos out)
3. As far
ger 5.
> However, I can reproduce the problems with Passenger 4 on an older Debian 7
> installation. So I'm ruling out Passenger 5 as the immediate issue at this
> time.
>
I had it working with passenger-5.0.7 last time I tested, so I don't think
it's passenger.
>
>
For the AIO, you can certainly get passenger working. (Although we'd love
to hear why PuppetServer isn't working or what you want).
Config files on a gist:
https://gist.github.com/stahnma/cf89dfa79b053f138eb1
This should get you most of the way there. You might have to sub out
passenger versions
On Mon, Jun 29, 2015 at 10:33 AM, Daniel Urist wrote:
> Are there up-to-date instructions for how to install from the apt repos
> for jessie?
>
Install http://apt.puppetlabs.com/puppetlabs-release-pc1-jessie.deb and
then use apt-get to install puppet-agent. That should be about it.
>
> On Fri
>
>
>
> I also neglected to mention in the original announcement that we now have
> package repositories for Debian Jessie and Mac OS X Mavericks (10.9) and
> Yosemite (10.10) and these OSes will be part of the regular release
> pipelines
> going forward.
>
> For those looking for Mac packages, the
Can you file a ticket on that? I'd like to claim I'll remember to assign it
out from a mailing list post, but I probably won't.
If we have a ticket, I'll see if we can get somebody to look at it.
On Mon, May 4, 2015 at 7:54 AM, Victor Danilchenko
wrote:
> Hi guys,
>
> The Puppet that comes with
Rather than reply and quote lots of points, I'll just bring up a few things
which could help clarify our goals. I'm sure not everybody will agree or
love all of them, we know there are compromises here but attempted to make
choices with the user's benefit and ease of use in mind.
* The package is
On Wed, Apr 29, 2015 at 9:32 AM, Corey Osman wrote:
> I am glad I am not the only one who said WTF is Puppet Agent 1.0. If in
> fact this is referring to the collection repo around running puppet agent
> AIO than it should be called Puppet Agent Collection AIO 1.0 or something
> similar.
>
It's
Hey,
We're working on fixing this right now. I'll post more when we've resolved
the issue.
On Mon, Apr 27, 2015 at 8:31 AM, Charlie Sharpsteen
wrote:
> On Sunday, April 26, 2015 at 5:09:18 PM UTC-7, Pete Brown wrote:
>>
>> Hi gang,
>>
>> I was just looking to setup my vagrant environment with p
On Thu, Apr 16, 2015 at 12:28 AM, Jo Rhett wrote:
> I really thought you would upgrade Ruby to handle the exploits-in-the-wild
> security vulnerability in Ruby before release.
> https://www.ruby-lang.org/en/news/2015/04/13/ruby-2-1-6-released/
>
> In particular, isn’t Puppet vulnerable to this pr
On Wed, Apr 15, 2015 at 12:23 AM, Vishal Biyani wrote:
> I am trying to understand more about Puppet support on AIX. I have found
> bits and piece of information here and there but nothing which shows me
> complete picture. The best one I have found so far is :
> http://projects.puppetlabs.com/pr
What does your catalog look like? Could you try basically something empty
(no node classification, no custom facts/plugins) and see if it works? We
certainly have lots of people running Puppet on EL7.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" gro
And the Fedora 20 packages for Puppet and Facter at least, work just fine.
That's what I've been using at home.
On Fri, Jan 30, 2015 at 9:01 AM, Melissa Stone
wrote:
> Hi Dallas,
>
> We are getting everything prepared to start shipping Fedora 21 packages.
> You'll see that repo slowly being popu
On Wed, Oct 15, 2014 at 3:28 PM, Mike Seda wrote:
> Puppet Developers,
> Based on the SSL POODLE vulnerability (
> https://www.openssl.org/~bodo/ssl-poodle.pdf ), will you be patching
> WEBrick to deny SSLv3 like you did with SSLv2 (
> https://projects.puppetlabs.com/issues/19151 )?
>
Yes, the n
On Fri, Oct 3, 2014 at 7:53 AM, Tim Skirvin wrote:
> If using the Beaker framework is going to be a core part of
> determining that a puppet module has been "tested", I figure I'd better be
> able to use Beaker. And so far, this seems tricky, at least on my RHEL 6
> systems.
>
>
Sometimes yum (and things calling it) do better when using
package-name.arch like openldap-libs.i386 vs openldap-libs.x86_64 if
that makes sense. I think that's what's happening.
On Tue, Nov 19, 2013 at 5:43 AM, Dan White wrote:
> Did you try
>
> yum update --verbose
>
> as suggested ?
>
>
> “S
Our primary distribution server will be down for scheduled maintenance
at 03:00 UTC for approximately 1 hour. This system hosts
yum.puppetlabs.com, apt.puppetlabs.com, and downloads.puppetlabs.com.
Those services will be unavailable during this outage window.
If you have questions, please let me
On Wed, Jul 17, 2013 at 12:33 PM, Larry Sybrandt wrote:
> Hello All
>
> Just wondering where to manage an AIX server with multiple WPARS. At the
> host level or at each guest level?
>
> It seems like one way would be easier than another. I just can't figure out
> which one that is.
I played wit
Fedora 19 is now up on yum.puppetlabs.com.
As a word of caution, this is the first distro to adopt Ruby 2.0, so there
could be some bugs in a few spots. Please file if you run into them.
http://projects.puppetlabs.com/projects/puppet-community-pkg-repo/issues/new
stahnma
--
You received this
Fedora 19 is now up on yum.puppetlabs.com.
As a word of caution, this is the first distro to adopt Ruby 2.0, so there
could be some bugs in a few spots. Please file if you run into them.
http://projects.puppetlabs.com/projects/puppet-community-pkg-repo/issues/new
stahnma
--
You received this
://docs.puppetlabs.com/guides/upgrading.html
Web: http://ask.puppetlabs.com
IRC: #puppet
Mailing list: puppet-users@googlegroups.com
Thanks,
Michael Stahnke
Engineering
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this grou
On Wed, Jul 3, 2013 at 4:24 PM, Pete Brown wrote:
> I was just wondering the same thing.
> My dev environment runs in Fedora 18 and I almost upgraded yesterday
> but thought some testing was in order first.
>
> I am likely to do what I did last time and try installing the versions
> from the previ
On Wed, Jun 12, 2013 at 5:52 AM, Greg Chavez wrote:
> Which is just fine if your company has the Optional subscription.
> Mine doesn't. So I'm screwed unless I write a script to manually pull
> updates from Fedora or CentOS into a custom mrepo repository. Bit of a
> pain, that is.
The optional r
Fedora stock ships Puppet 2.7.18 and Ruby 1.9.3, which are not compatible.
I suggest adding yum.puppetlabs.com and upgrading to Puppet 3.
Either that or downgrade Ruby to 1.8.7.
This is a known issue with Puppet 2.7 and Ruby 1.9.3.
On Fri, Aug 17, 2012 at 6:51 AM, Peter Bukowinski wrote:
> Gr
The time has come for us to say good-bye to Puppet 2.6.x. Puppet 2.6.x is
now end of Life, as originally announced Jan 17, 2013.
Puppet 2.6.0 first launched July 20, 2010. Since that time, we've had two
major versions of Puppet, 2.7.x and the semantically versioned Puppet 3
series.
Puppet 2.7.x i
Unless you've elected to use legacy storeconfigs (with activerecord),
you are correct, your system should not be vulnerable.
stahnma
On Mon, Feb 4, 2013 at 6:15 AM, Kodiak Firesmith wrote:
> Hello fellow Puppet users!
>
> I'm trying to perform due diligence to make sure that our Puppet
> insta
The time has come for us to say good-bye to Puppet 2.6.x. Puppet
2.6.x will be end of life on April 30, 2013.
Puppet 2.6.0 first launched July 20, 2010. Since that time, we've had
two major version of Puppet, 2.7.x and the new semantically versioned
Puppet 3 series.
Puppet 2.7.x is largely on a
Thanks for the query. I don't know that we did make an official
announcement regarding Puppet 2.6.x. I will be doing that shortly (as in
today).
Mike
On Tue, Jan 15, 2013 at 8:53 AM, Michael Hrivnak wrote:
> I am trying to determine how much longer, if at all, version 2.6 of Puppet
> Open So
Puppet 3 has lots of performance improvements. In many cases it's
faster than 2.6.x was. Some of those fixes were back-ported to 2.7.20,
but not all of them could be.
For best performance, try out something in the Puppet 3 series.
On Wed, Dec 19, 2012 at 8:30 AM, shurik wrote:
> Hi
>
> We are
On Wed, Dec 12, 2012 at 12:54 PM, Alexander Philipp
wrote:
> Are there any good guides out there to using Puppet agents with a dedicated,
> separate ruby install? Our apps are all Ruby based and require different
> versions than Puppet. Installing the agent from a package will override our
> rub
On Wed, Nov 28, 2012 at 10:34 AM, asq wrote:
> i've made a migration on our puppetmasters yesterday, hoping it will run
> faster and/or make less load on machines with newer ruby. but actual result
> is just opposite, our compilation times went up a lot, ie:
>
> Nov 27 14:30:12 punch puppet-maste
Thanks Jeff for pointing out that the EPEL maintainer and the puppet labs
maintainer should have been coordinating on rubygem-json. (It's the same
guyme. I'm an idiot).
Mike
On Wed, Nov 28, 2012 at 11:37 AM, Brian Jolly wrote:
> That worked for me. Thanks!!!
>
>
> On Wed, Nov 28, 2012 a
On Mon, Nov 26, 2012 at 2:16 PM, Alaric wrote:
>
> On Nov 26, 2012, at 4:46 PM, Michael Stahnke wrote:
>
>>
>> I tried to reproduce this and just couldn't. Does this happen on
>> other systems?
>>
>> Is there any more information you could think
On Fri, Nov 23, 2012 at 2:46 PM, Alaric wrote:
> Hi,
>
> I'm having a weird issue and was wondering if anyone else had run into it. I
> recently upgraded from puppet 2.7 -> 3.0.1 After cleaning up some gems on my
> puppet master everything seemed to be working ok. I had originally used the
>
On Sun, Nov 25, 2012 at 11:00 PM, Walter Heck wrote:
> I think you might be using the wrong tool for the job, but we need a
> little bit more information to determine that: What do you want to do
> with these facts once you have them in puppet?
>
> If you are managing websites with puppet, you sho
On Tue, Nov 13, 2012 at 8:31 AM, Bret Wortman wrote:
> It is kind of funny that we're talking about using puppet's tricks for
> working around bad start scripts for puppet's own software
>
>
> On Tuesday, November 13, 2012 9:58:57 AM UTC-5, jcbollinger wrote:
>>
>>
>>
>> On Tuesday, November 1
On Tue, Nov 6, 2012 at 6:37 AM, jcbollinger wrote:
>
>
> On Monday, November 5, 2012 2:10:58 PM UTC-6, msuho wrote:
>>
>> Hi-
>>
>> I am running RedHat Enterprise version 6.
>>
>> Linux luke 2.6.32-131.17.1.el6.x86_64 #1 SMP Thu Sep 29 10:24:25 EDT 2011
>> x86_64 x86_64 x86_64 GNU/Linux
>>
>> I'm
On Sun, Nov 4, 2012 at 8:50 PM, Alex Harvey wrote:
> Hi all,
>
> Not sure if anyone out there would be using HP-UX on PA-RISC but just in
> case we've run into a real brick wall on this one.
>
> We are apparently encountering exactly the same issue as this person did -
> http://www.ruby-forum.com/
I'm trying to close the loop on this thread.
We recognize that some users were negatively impacted by having Puppet
3.0.0 in the same repositories as the previously released versions.
While we attempted to communicate our intentions to release that way
by design, not everybody saw those communicat
On Fri, Oct 26, 2012 at 10:36 AM, Ramin K wrote:
> On 10/26/2012 2:19 AM, Gavin Williams wrote:
>>
>> Morning all
>>
>> Not sure on the best place to raise this, so thought I'd start here...
>>
>> I'm starting to work with Puppet and Oracle Linux 6.1.
>> Unfortunately I'm finding a lot of existing
On Tue, Oct 23, 2012 at 11:14 AM, Worker Bee wrote:
> Hi Everyone;
>
> So, the FreeBSD Port is now available. However, I am a bit confused about
> hiera. The Makefile does not list rubygem-puppet-hiera as a requirement for
> the agent. This IS required in the redhat spec files for the agent. S
On Tue, Oct 16, 2012 at 4:37 PM, Jakov Sosic wrote:
> On 10/17/2012 01:02 AM, Craig White wrote:
>>
>> The puppet server should probably be running on something newer than
>> CentOS 5.x (a vm perhaps?)
>
>
> Can you run 3.0 server with 2.7 clients?
Yes.
>
>
>
> --
> Jakov Sosic
> www.srce.unizg.h
On Tue, Oct 9, 2012 at 9:46 AM, Klaus Ethgen wrote:
> Michael Stahnke schrieb:
> [Bug in domain.rb]
>>> I think that is a bug in facter but I do not know how to open a bug
>>> report on the website, there is only a way to display open issues.
>>
On Tue, Oct 9, 2012 at 5:05 AM, Klaus Ethgen wrote:
> Hello,
>
> The domain.rb tries to get the domain by calling hostname without any
> option. This will mostly leed in only the name without any domain part.
> The hostname tool only give the fqdn if called with -f (or --fqdn or
> --long).
>
> Add
On Tue, Oct 9, 2012 at 8:22 AM, Peter Berghold wrote:
> Got the following:
>
> err: Could not retrieve catalog from remote server: Error 400 on SERVER:
> Could not autoload package: Could not autoload
> /usr/local/lib/site_ruby/1.8/puppet/provider/package/windows.rb: no such
> file to load -- wind
On Tue, Oct 2, 2012 at 1:30 PM, Jeff McCune wrote:
> On Tue, Oct 2, 2012 at 1:17 PM, Robert Rothenberg wrote:
>> I am using CentOS 6 with the PuppetLabs yum repo from
>> http://yum.puppetlabs.com
>>
>> I noticed that today version 3 is available on the repo, so of course, an
>> upgrade to Puppet
On Fri, Sep 21, 2012 at 6:48 PM, Jakov Sosic wrote:
> On 09/19/2012 11:55 PM, Hai Tao wrote:
>>
>> There seems to be a few vmware tools installation modules. Has someone
>> used these modules to install VMware tools?
>>
>> Searching http://forge.puppetlabs.com ...
>> NAMEDESCRI
On Fri, Sep 21, 2012 at 8:45 AM, Stephen Price wrote:
> John's right. Yum and RVM will manage Rubies separately.
>
> Is there a specific reason you want Puppet to use 1.9.2 instead of CentOS
> 6's version from yum repos (1.8.7)? I run CentOS on close to 100 hosts, all
> with 1.8.7 as the default i
There's also http://rubygems.org/gems/web-facter. not sure if that
would help. I haven't played with web-facter, but thought it looked
somewhat interesting.
Mike
On Fri, Sep 21, 2012 at 5:07 AM, Bill Fraser wrote:
> On 12-09-20 10:36 PM, Hiu wrote:
>> hi all,
>>
>> I would like to gather for t
I used to just institute policy that hostnames could not be re-used.
It had a few benefits beyond puppet, like application people not
hard-coding hostnames and using cnames as the maker intended.
Mike
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" gr
It's the time of year again where we gather the Puppet faithful from
around the world and hold PuppetConf. What started last year in
Portland is moving to San Francisco this year, with a bigger venue,
more tracks and amazing speakers. PuppetConf 2012 takes place in San
Francisco, from September 27
On Mon, Aug 6, 2012 at 5:21 PM, alike wrote:
> This is my first time to install puppet and it's quite frustrating to me.
> If anyone can help me out that would be great.
>
> My current installation failed with the below error:
>
> ** /opt/puppet/bin/erb -T - './erb/send_cert_request.rb.erb' >
> '/
Ruby is in the base repos (or optional channel in RHEL 6), so there
isn't a need for us to provide it. It is provided by the distro
vendor.
On Mon, Aug 6, 2012 at 11:26 AM, unixman wrote:
>
>> I mean yum install puppet of course
>> Chris
>
> --
> You received this message because you are subscri
You only need activeMQ in one spot to do mcollective stuff. So, the
Puppet Server is an acceptable place to do that. If you're not yet
using mcollective, then you don't need ActiveMQ at all.
Mike
On Thu, Jul 26, 2012 at 11:41 AM, Hai Tao wrote:
> on the puppet server ( i have only one), shou
I can't reproduce this. I used sudo because it was out-of-date on my system.
[0] root@centos6-64 /tmp> rpm -q sudo
sudo-1.7.4p5-9.el6_2.x86_64
[0] root@centos6-64 /tmp> yum list available | grep sudo
sudo.x86_641.7.4p5-12.el6_3 updates
[0] root@cento
This has to do with Ruby 1.9.3 being the default (and only) ruby in
Fedora 17. Puppe 2.7 in Fedora 17 has a couple of outstanding bugs in
the 2.7.x series with Ruby 1.9.3. Reporting is one of them. It can't
easily be fixed without modifying behavior. When Puppet 3.0 arrives,
this is fixed with
Did something else pull that package in as a dependency?
On Thu, Jul 26, 2012 at 7:37 AM, Matthew Barr
wrote:
> We just saw an interesting scenario:
> Puppet 2.7.18 updated packages on a RHEL 6.2 box to a newer version without
> logging that fact.
>
> We've already fixed our code so it doesn't
On Tue, Jul 17, 2012 at 8:41 AM, Mateusz Lenik wrote:
> Hello,
>
> My name is Mateusz and I'm one of the GSoC 2012 students.
> My proposal was to expand features of Ruby DSL for Puppet.
> The idea is to make Ruby DSL as similar as possible to Puppet language, so
> it
> can be learned easily and st
As many of you have doubtless noticed, Puppet 3 and Facter 2 have been sitting
in RC (Release Candidate process) for a long time. That's about to change, but
they won't be getting released as they currently stand. Puppet 3 and Facter 2
have been pulled out of the RC process after we recognized that
We've had a few cancellations for our Puppet Camp Chicago (July 23, 2
weeks from today). If you'd like to speak about Puppet,what you're
doing with it, DevOps, etc we may have a spot for you.
You can game fame, fortune or at least a little notoriety.
If you'd like to speak, just reply to me with
Puppet Dashboard *can* be installed on EL 5 based systems if you've
updated Ruby to a 1.8.7 version. By default, EL5 comes with 1.8.5
versions of ruby which have known issues with Dashboard. If you
search the archives of this list, there are a few posts about getting
1.8.7 onto EL5 specifically f
On Mon, Jun 25, 2012 at 6:19 AM, jcbollinger wrote:
>
>
> On Saturday, June 23, 2012 7:38:20 PM UTC-5, Kelsey Hightower wrote:
>>
>> There is a pending pull request that adds the ability for Puppet to load
>> Faces, parser functions, and report processors installed via Rubygems.
>>
>> https://gith
I've used 2.7.13 and higher with Ruby 1.9.3. The only real problem I
remember having was around reports. I wasn't doing anything super
complicated though.
Mike
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email
If you really want to use Oracle java, see this:
http://docs.puppetlabs.com/pe/2.5/install_basic.html#vendor-packages
On Fri, Jun 8, 2012 at 8:16 AM, Scott wrote:
>
> Jeeva gmail.com> writes:
>
>>
>> Hi,
>>
>> I was trying to instal puppet-enterprise-2.5.1-el-5-x86_64 in centos6
>> machine
I let this sit for a week or so to see what response would be.
In general:
If you are a puppet user/community member and want to post a job at
your company, that is ok. Please add JOB to the subject line.
If you are a recruiter or hiring for a 3rd party, it is not ok. You
can use traditional re
How do folks feel about getting Puppet job listings on this list?
I've rejected a few that we quite spammy, but when the subject matter
really is a system admin with puppet experience, the decision becomes
a bit different.
I'm looking for general feelings. A simple +1 or -1 would be great.
Mike
evor
>
> On Fri, May 25, 2012 at 10:49 AM, Michael Stahnke
> wrote:
>> I have Ruby 1.9 (the build from Fedora 17) available for EL6 variants.
>> It's not super-tested, but I've used it for some tests/experiments.
>>
>> http://stahnma.fedorapeople.org/ruby/
I have Ruby 1.9 (the build from Fedora 17) available for EL6 variants.
It's not super-tested, but I've used it for some tests/experiments.
http://stahnma.fedorapeople.org/ruby/
Mike
On Thu, May 24, 2012 at 8:13 PM, Trevor Vaughan wrote:
> Nan,
>
> Using the 'alternatives' system is probab
On Tue, May 22, 2012 at 5:07 AM, felix wrote:
>
> ah ! thanks
>
> before:
>
> puppet:
> Installed: (none)
> Candidate: 0.25.4-2ubuntu6.7
> Version table:
> 0.25.4-2ubuntu6.7 0
> 500 http://archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
> 500 http://security.ubunt
://projects.puppetlabs.com/projects/puppetdb/issues
Michael Stahnke
Community Manager
Puppet Labs
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group,
On Wed, May 16, 2012 at 8:34 AM, jcbollinger wrote:
>
>
> On May 16, 5:23 am, Jeeva wrote:
>> Hi,
>>
>> I was trying to instal puppet-enterprise-2.5.1-el-5-x86_64 in centos6
>> machine. But got below error.
>>
>> ## Installing packages from files...
>> error: Failed dependencies:
>> java
t;> * Don't insult others
>> * Attempt to limit cross-posting with other lists
>>
>>
>> We don't have clear community guidelines or formal policy around this.
>> I'd like to keep this as simple as possible.
>>
>> Thanks for understanding
post. This was just a chore
that needed to go out. Our list has grown quite a bit, so a gentle
reminder is a good thing.
>
> On Tue, May 15, 2012 at 10:44:59AM -0700, Michael Stahnke wrote:
>> I wanted to quickly make a reminder on mailing list etiquette:
>>
>> * Don
sting with other lists
We don't have clear community guidelines or formal policy around this.
I'd like to keep this as simple as possible.
Thanks for understanding,
Michael Stahnke
Community Manager
--
You received this message because you are subscribed to the Google Groups
&quo
On Tue, Apr 24, 2012 at 1:53 AM, Bill Proud wrote:
> Sounds good.
>
> One problem that I have with the forge is that the extent to which the
> modules have been tested is not clear to me. Can I take it that the core
> modules that ship with puppet will have been through a similar testing cycle
>
n those two pages, and I think it would be nice to have
> this information on at least one of them.
>
> Thanks in advance.
>
> Best regards,
> Christophe
>
>
> On 8 avr, 00:42, Michael Stahnke wrote:
>> On Thu, Apr 5, 2012 at 10:34 PM, Christophe L
>> wrote:
&
There was some discussion and concern about moving the Nagios
types/providers out of the core area of Puppet for Telly. We made a
mistake of talking about a point solution to a problem rather than the
vision on where we’d like it to go, and why. We’ve attempted to
outline this a bit more so you c
There also could be mcollective logs on the end-points that would tell
you what command were run etc.
On Wed, Apr 18, 2012 at 6:10 AM, jcbollinger wrote:
>
>
> On Apr 18, 3:17 am, Luke Bigum wrote:
>> If you're really really lucky you can look in ${vardir}/clientbucket on
>> an Agent (usually
On Mon, Apr 16, 2012 at 9:52 PM, Paul Hinze wrote:
> On Mon, Apr 16, 2012 at 4:55 PM, Steve Roberts wrote:
>> But since the provider has already clipped the attributes they don't
>> get set in the first run.
>>
>> when run a second time the attributes do get set correctly, but that
>> seems a bit
On Mon, Apr 16, 2012 at 11:36 AM, Todd Zullinger wrote:
> Michael Stahnke wrote:
>>
>> For the next major Puppet version, code-named Telly, we have some changes
>> coming. This is the first in a series of emails around these changes and
>> may require some input fr
lly. Obviously you're running things that
MUCH older than what telly is setup to do.
Another option would be to run Puppet Enterprise (which includes Ruby
1.8.7), but doesn't support RHEL 3 or 4. I'd probably talk to my boss
about what end-of-life really means ;)
>
> On Ap
Puppet Labs is happy to announce full support for Ruby 1.9.3 will be part of
the next major release of Puppet, codenamed Telly. Ruby 1.8.7 and 1.9.3 are
considered the primary supported Ruby versions, on all platforms including
Unix, Linux, Windows, and MacOS-X. Ruby 1.8.5 is also supported, on t
1 - 100 of 271 matches
Mail list logo
