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 install. A number of these also have RVM with
various Rubies i
;s annoying to commit, push, fetch and merge, just
> to get your changes from one environment to the next. I suppose it does
> help prevent mistakes though.
>
> I hope that story makes some sense. I'd be very interested to see how
> others set up their version control workfl
I finally got around to installing PuppetDB and connecting it to my Master.
I even set up Nginx to act as a reverse proxy, and I can make API calls
like a pro. The dashboard is nice, but I'm anxious to get at least the same
functionality that Puppet Dashboard gave me. Namely, a quick look at rec
This is an aside, but you should really be using gpgcheck. I define
repositories with yumrepo, but I also have a separate file resource to copy
the gpgkey to a local directory and set the appropriate yumrepo parameters.
On Tuesday, November 20, 2012 1:22:55 PM UTC-8, pmbuko wrote:
>
> On Nov 20,
Cool, cool. If I'm installing a repo for the first time, I usually install
the rpm manually on a test machine, then grab the .repo file from
/etc/yum.repos.d and the referenced gpgkey, and add everything in Puppet
with a custom define (which is really a wrapper around yumrepo with the
additiona
Good to hear! I'm looking forward to being able to replace Dashboard, and
PuppetDB has been working great for everything else so far.
On Tue, Nov 20, 2012 at 2:05 PM, Deepak Giridharagopal <
dee...@puppetlabs.com> wrote:
> On Tue, Nov 20, 2012 at 2:30 PM, Stephen Price wrote:
I believe Hiera (or puppet-hiera, not sure) has outstanding issues with
anything other than Ruby 1.8.7. Last time I tried using 1.9.3 with Puppet 3
I had to revert. Please correct me if I'm mistaken.
On Wednesday, December 12, 2012 4:31:51 AM UTC-8, vioilly wrote:
>
> I am going to revert to 1.8
I'm trying to update this from the PuppetLabs yum repo, but I'm getting
error reports about the rpm not being signed. Any insights?
On Thursday, December 27, 2012 11:00:43 AM UTC-8, Matthaus Litteken wrote:
>
> Facter 1.6.17 is a maintenance release in the 1.6.x series with bug fixes.
>
> Downlo
No, thank you!
On Thursday, December 27, 2012 11:41:38 AM UTC-8, Matthaus Litteken wrote:
>
> Stephen,
> Thanks for pointing that out. I'm re-signing the rpms right now and
> will have them shipped in a few minutes.
>
> On Thu, Dec 27, 2012 at 11:25 AM, Stephen Price
On Monday, January 14, 2013 7:49:33 AM UTC-8, R.I. Pienaar wrote:
>
> No I am not sure - I dont tend to use create_resources as I consider it
> about
> as bad as eval() :)
>
> I just know I recently went spelunking into that code while doing some
> prototype
> and noticed it worked
>
Sorry
I'm running PuppetDB installed from yum on CentOS 6, with a Postgres
backend. After upgrading from 1.0.5 to 1.1.1, my dashboard
(http://puppetdb/dashboard/index.html) is full of question marks with empty
graphs, and the top right displays "PuppetDB (unknown version)". Other than
that the upgrad
>
> What do you see in your puppetdb.log when you try to hit the dashboard?
>
> In your browser if you enable the javascript console - do you get any
> errors that might be helpful?
>
> ken.
>
> On Tue, Mar 5, 2013 at 8:31 AM, Stephen Price >
> wrote:
&
Guys, Can you expand the README to describe where this should be run from?
I've been trying to use it as a Puppet Face from different hosts, including
directly on the PuppetDB server, to no avail. I keep getting 'bad request'
or SSL cert errors. My PuppetDB is running on localhost:8080 with Ngin
-nodes binary,
> so you can try that instead of the puppet face if you are still getting SSL
> errors.
>
> --
> Erik Dalén
>
>
> On Thursday 28 March 2013 at 17:31, Stephen Price wrote:
>
> > Guys, Can you expand the README to describe where this should be
This is something you should be configuring on the Puppet master's local
MTA, be it Sendmail or Postfix or whatever. Then Puppet will just attempt
to send email through localhost, and the MTA can determine how to route it
and with what authentication methods.
On Thursday, August 22, 2013 8:21:2
t this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
Stephen Price
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe fro
I've been using PuppetDB as an ENC for a while, but I haven't really
utilized it for stored configs or anything. I was mostly interested in
replacing Dashboard's reporting capabilities, but PuppetDB doesn't yet do
anything (that I can see) with reports. So I'm currently looking into
setting up
query these facts?
On Tue, Aug 27, 2013 at 9:57 AM, Stephen Price wrote:
> I've been using PuppetDB as an ENC for a while, but I haven't really
> utilized it for stored configs or anything. I was mostly interested in
> replacing Dashboard's reporting capabilities
ts topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>
z8uFI/5yFZgVIG5wEJ
>
>
> On Tuesday, August 27, 2013 10:45:55 PM UTC-7, Stephen Price wrote:
>
>> Sorry, I meant I'm using Hiera as an ENC. I did see that PuppetDB has
>> report storage, but without an easy way to use that data (short of creating
>> my own interface
t;
>
>
> On Wed, Aug 28, 2013 at 9:13 PM, Stephen Price
> > wrote:
>
>> Thanks! I'll check it out. I think eventually I can see using Foreman
>> more for stuff like ENC and provisioning, but I wanted to proceed
>> cautiously by just starting with reporting an
21 matches
Mail list logo
