Hello,
> My question is this. Are the modules intended to be used with the
> author-modulename naming convention? If so, did I do something wrong
> or is there something wrong with the camptocamp-apt module that is not
> allowing this?
This module was indeed made to be used as "apt" not "camptoca
Le lundi 07 juin 2010 à 09:18 +0200, Marc Fournier a écrit :
> Hello,
>
> > My question is this. Are the modules intended to be used with the
> > author-modulename naming convention? If so, did I do something wrong
> > or is there something wrong with the camptocamp-apt module that is not
> > allo
a lame solution, but usable -
have a link from /etc/puppet//modelname to the forge dl location?
(excluding the unwanted name of course)
On Mon, Jun 7, 2010 at 3:18 PM, Marc Fournier
wrote:
> Hello,
>
> > My question is this. Are the modules intended to be used with the
> > author-modulename namin
Hi all,
I've released a small tool that displays when puppet last ran
successfully on your nodes. Here's a bit more about that:
http://blog.absurd.li/2010/06/07/a_small_tool_for_puppet.html
You can get it here:
http://github.com/kschiess/last_puppetrun
Note that you probably have to ins
I’m happy to announce a new version of Foreman - 0.1-5
Highlights are:
*Web interface*
Most of the pages have been rewritten, there are many changes:
Search options
- Hosts (filter based on facts, based on host groups etc
- Facts (all hosts with fact x or with value y etc)
- Reports (
Just following up:
Ubuntu package (tested on Ubuntu 10.04) can be found here:
http://theforeman.org/attachments/download/109/foreman_0.1.5-1_all.deb
RHEL5 packages can be found here:
http://theforeman.org/repo/el5/noarch/rubygem-rack-1.0.1-1.noarch.rpm
http://theforeman.org/repo/el5/noarch/forema
On Mon, Jun 7, 2010 at 3:18 AM, Marc Fournier
wrote:
> Hello,
>
>> My question is this. Are the modules intended to be used with the
>> author-modulename naming convention? If so, did I do something wrong
>> or is there something wrong with the camptocamp-apt module that is not
>> allowing this?
>
On Sun, Jun 6, 2010 at 5:13 PM, David Schmitt wrote:
> Am 04.06.2010 18:34, schrieb Dan:
>>
>> Most of my machines are pretty cookie-cutter, so I have one class and
>> config file setup for different services. For example, pretty much
>> have one hosts.allow that goes out everywhere. However, th
On Fri, Jun 4, 2010 at 5:25 PM, Todd Zullinger wrote:
> Oded wrote:
>> Never tried it myself but I think you can create the certificate as
>> a part of the provisioning process, and then somehow place it in the
>> new server.
>> http://serverfault.com/questions/19462/how-can-i-pre-sign-puppet-cert
just for completion, autosign is enabled only once a kickstart/preseed etc
file has been requested by the predefined ip address (or mac) in foreman.
I agree that signing the clients without autosign is a good alternative, but
i'm not sure if trusting your fqdn is any different to trusting your ip
On 6/7/2010 2:51 PM, Michael DeHaan wrote:
On Mon, Jun 7, 2010 at 3:18 AM, Marc Fournier
wrote:
Hello,
My question is this. Are the modules intended to be used with the
author-modulename naming convention? If so, did I do something wrong
or is there something wrong with the camptocamp-apt mo
- "Michael DeHaan" wrote:
> Nice ideaI like that.
>
> I had toyed with adding such an autosign-simulating feature to
> Cobbler that ohad mentioned (but different*), but I don't see how that
> provides any greater security, as once you have
> automated provisioning via TFTP (it's an open
On Jun 6, 2010, at 2:53 AM, Douglas Garstang wrote:
> We used to pass a bunch of settings back to our modules from
> definitions on the node manifests. Since external nodes don't support
> definitions, I presume these definitions have go get pushed back into
> a module and a class somewhere, and t
On Fri, Jun 4, 2010 at 11:34 AM, Dan wrote:
> Most of my machines are pretty cookie-cutter, so I have one class and
> config file setup for different services. For example, pretty much
> have one hosts.allow that goes out everywhere. However, there are
> always exceptions. So I have 3 hosts tha
On Mon, Jun 7, 2010 at 6:09 AM, David Schmitt wrote:
> On 6/7/2010 2:51 PM, Michael DeHaan wrote:
>
>> On Mon, Jun 7, 2010 at 3:18 AM, Marc Fournier
>> wrote:
>>
>>> Hello,
>>>
>>> My question is this. Are the modules intended to be used with the
author-modulename naming convention? If so
> I think the modules should be written so that they assume they are
> named after what they are in forge.
I don't think this is a good idea, if I've understood it fully.
IHMO, modules in the forge should be, in the long term, interoperable
and possible interchangeable.
I should "include apache
I am running into a problem with my LDAP puppet setup with this error
message:
PuppetClient:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not parse for environment DR: undefined method `to_sym' for ["ENV1",
"ENV2"]:Array
PuppetMaster:
err: Could not parse for env
Early Bird rate ends tomorrow, so sign up soon if you're interested:
http://www.puppetlabs.com/events/bay-area-training/
Contact Amy Hoang: a...@puppetlabs.com (503) 575-9784 if you have
any questions, etc.
Best,
Scott C.
--
You received this message because you are subscribed to the Google
Hi,
I am just getting started with puppet. Our stack runs on 1.9 and it
seems puppet is not quiet there yet.
I figure I could run puppetmaster on 1.8 but the clients will need
to install and run 1.9.
Any advise there? or are we doomed for the time being?
Thanks!
--
You received this m
I was working on updating some of our RHEL-3 systems, and looks like putting
puppet on there is a little harder due to older libraries, so before I went and
tried retro-fitting these guys I thought I'd see if anyone was using it with
luck there and any tips/tricks I might watch out for?
Thanks!
On Sun, 06 Jun 2010, Douglas Garstang wrote:
> I was just doing a little research on the best way to switch over to
> external nodes. It seems like you can't use a combination of the two
> systems.
I assume that "the two systems" means (1) an external node classifier,
and (2) node {...} definition
On Sun, 06 Jun 2010, Ashley Penney wrote:
> This is currently killing me too. I also heavily used definitions in
> nodes for things that didn't really seem to belong in modules (one
> offs, mount points for admins to rummage around on the command line,
> the odd tweak here and there) and the inabi
On Sun, 06 Jun 2010, Nicolas Szalay wrote:
> - "Douglas Garstang" a =??crit :
> | I was just doing a little research on the best way to switch over to
> | external nodes. It seems like you can't use a combination of the two
> | systems. Apparently if the external node tool can't find an extern
On Mon, Jun 7, 2010 at 3:02 PM, Alan Barrett wrote:
> On Sun, 06 Jun 2010, Nicolas Szalay wrote:
>> - "Douglas Garstang" a =??crit :
>> | I was just doing a little research on the best way to switch over to
>> | external nodes. It seems like you can't use a combination of the two
>> | systems
Has anyone been using this in production to store facts remotely in a
distributed environment? I have been testing it in my lab where latency and
bandwith to a remote mysql server is very good so it works well. But if I
attempt to use it across a wan with ~150ms puppetqd seems to die. If I
don't
On Mon, Jun 7, 2010 at 1:46 PM, Daniel Wittenberg
wrote:
> I was working on updating some of our RHEL-3 systems, and looks like putting
> puppet on there is a little harder due to older libraries, so before I went
> and tried retro-fitting these guys I thought I'd see if anyone was using it
> w
- "Al @ Lab42" a écrit :
| > I think the modules should be written so that they assume they are
| > named after what they are in forge.
|
| I don't think this is a good idea, if I've understood it fully.
|
| IHMO, modules in the forge should be, in the long term, interoperable
| and possibl
On Jun 7, 2010, at 10:40 AM, DeRailed wrote:
> Hi,
>
> I am just getting started with puppet. Our stack runs on 1.9 and it
> seems puppet is not quiet there yet.
> I figure I could run puppetmaster on 1.8 but the clients will need
> to install and run 1.9.
>
> Any advise there? or are we
Oh yeah, I want to move off it, and even have the new RHEL-5 boxes built, but
the legacy app isn't moving too quickly and the resources I need to make it go
faster are allocated elsewhere so for the time being I've decided that I'd like
to get them under controla little anyway :)
Dan
On J
Think I found the issue from an strace, the rubygems-sqlit3 rpm was
missing.. still curious on where the logs end up for it though. The fact
that its using sqllite also doesn't help as I think I am running into
locking issues if I try to run a cross environment update.
How to deal with sqllite lo
We use it on our RHEL3 boxes and the other poster is correct. You must
build all the dependencies yourself. Fortunately for use we have a build
environment for it still and it hasn't been an issue.Once you get through
that though, it works remarkably well.
Drew
On Mon, Jun 7, 2010 at 1:56 PM, D
Was the build process pretty straight-forward? If not, mind sharing your
changes/spec files/rpm's?
Thanks,
Dan
On Jun 7, 2010, at 3:03 PM, Andrew Hamilton wrote:
> We use it on our RHEL3 boxes and the other poster is correct. You must build
> all the dependencies yourself. Fortunately for
I'm not the one that builds them, but I don't believe there was anything out
of the ordinary that was done for it. I'm the only one in the organization
that has RHEL3 boxes and they usually consult me if something strange has to
be done. We have a fairly static RHEL3 build environment that uses a
When I installed Puppet on RHEL3 servers I had to first rebuild ruby-1.8.6:
http://ppadron.blog.br/2009/10/28/how-to-install-ruby-1-8-6-rpm-package-on-rhel3/
Take a look at Todd Zullinger's comment on this and rebuild puppet RPM
package. In my case, I did it with 0.24.8.
You can get puppet specfile
>
> I would prefer shortname, let puppet fail when there are collisions. Or
> maybe initials could be used for namespacing. ds_apache (tough luck Danielle
> Steel)
>
>>
Let's think about how the package manager's do it as this is
essentially a (really really primitive) package manager.
Hmm, they
On 06/06/2010 12:47 PM, Klaus Ethgen wrote:
Sure. And they get collected by facter without problems. But I am only
able to disperse one of them to all hosts.
regardless, you can collect like this
Ssh_authorized_key<<| type => "rsa" ||>
Ssh_authorized_key<<| type => "dsa" ||>
Oh, s
Nicolas Szalay wrote:
> - "Al @ Lab42" a écrit :
>
> | > I think the modules should be written so that they assume they are
> | > named after what they are in forge.
> |
> | I don't think this is a good idea, if I've understood it fully.
> |
> | IHMO, modules in the forge should be, in the
You might want to see my post on installing puppet on ESX 3.5 which is RHEL
3 based
http://groups.google.com/group/puppet-users/browse_thread/thread/3de6777df0a75ba2/fdfef3e8d8ff0ccd
Regards
John
On 8 June 2010 03:46, Daniel Wittenberg wrote:
> I was working on updating some of our RHEL-3 sys
I've created rpm's for ruby to co exists with the ruby that is part of RHEL3
(e.g. it gets installed in /usr/local).
if you don't care about that, just grab the srpm from any newer RHEL and
rebuild the packages. afterwards I think you could simply install the puppet
packages for RHEL4.
Ohad
On Tu
On Mon, 07 Jun 2010, Jay Christopherson wrote:
> err: Could not parse for environment DR: undefined method `to_sym' for
> ["ENV1", "ENV2"]:Array
>
> The "environment" variable is part of the LDAP node definition and in this
> case, the node in question belongs to two different environments and so
40 matches
Mail list logo
