Is there no other source (eg puppetlabs)? the Optional Channel seems
to be a bit of an administrative barrier.
On May 16, 5:20 pm, Nathan Powell wrote:
> augeas comes from the rhel optional channel. You'll have to enable that.
>
>
>
>
>
>
>
>
>
> On Wed, May 16, 2012 at 12:13 PM, Tim Coote wrot
On 17/05/12 09:18, Tim Coote wrote:
> Is there no other source (eg puppetlabs)? the Optional Channel seems
> to be a bit of an administrative barrier.
>
> On May 16, 5:20 pm, Nathan Powell wrote:
>> augeas comes from the rhel optional channel. You'll have to enable that.
Puppet Labs don't ship
Many thanks for your reply, unfortunately I'm quickly getting into a
mess:
On Wed, May 16, 2012, at 07:58 AM, jcbollinger wrote:
>
>
> On May 15, 9:32 am, Biltong wrote:
> > I have a class that pulls in some yum repositories. One of the yum
> > repositories is disabled, but on one host I'd lik
Currently and going forward people will be running multiple versions
of puppet. What are the plans for puppet compatibility with Modules?
Thinking we may want to be able to specify what version of Puppet is
running and ask for the compatible module. (Which may be the same).
Thanks,
Brian
--
You
On May 16, 2012, at 7:18 PM, Steve Traylen wrote:
>
> not a puppet problem, a vanilla yum or rpm also fails with this.
> Steve.
>
That's what I figured. Found this problem only on freshly kickstarted systems.
So, during the kickstart, the package was being installed from the 'base' repo,
and
Hello,
when running the command "ip a" on a debian VM, I get this
1: lo: mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: mtu 15
- Original Message -
> From: "Christophe L"
> To: puppet-users@googlegroups.com
> Sent: Thursday, May 17, 2012 2:36:49 PM
> Subject: [Puppet Users] Puppet facter 1.6.8 and inet6 addresses
>
> Hello,
>
> when running the command "ip a" on a debian VM, I get this
>
> 1: lo: mtu 16436 q
Thanks, Dominic. I get your point about augeas-libs not being
published from puppetlabs' repo. I don't think that I've got the whole
picture, however. I've got "rhel-x86_64-server-optional-6.1.z"
enabled, but it doesn't inlcude the necessary augeas-libs update to
support the puppet releases. Is it
On May 17, 4:19 am, Biltong wrote:
> Many thanks for your reply, unfortunately I'm quickly getting into a
> mess:
>[...]
> On Wed, May 16, 2012, at 07:58 AM, jcbollinger wrote:
>
> > On May 15, 9:32 am, Biltong wrote:
> > > I have a class that pulls in some yum repositories. One of the yum
> >
On 17/05/12 14:40, Tim Coote wrote:
> Thanks, Dominic. I get your point about augeas-libs not being
> published from puppetlabs' repo. I don't think that I've got the whole
> picture, however. I've got "rhel-x86_64-server-optional-6.1.z"
> enabled, but it doesn't inlcude the necessary augeas-libs u
On May 16, 8:51 pm, Joshua Hoblitt wrote:
> The class structure I have is something like the following.
>
> users::common
> users::dev
> users::prod
> etc...
>
> users::{dev, prod} do not use inheritance. Almost all node include
> users::common. Some include users::common and user::dev, while
Hello,
I'm having some trouble with subclasses accessing other subclasses within
the same main class.
I have boiled it down a general case. I have the following files:
## /etc/puppet/modules/test1
class test1 {
class {'test2::bar':}
}
## /etc/puppet/modules/test2/init.pp
class test2 {
You can't require Class['test2::foo'] unless it's already available where
you're requiring it. You need to include test2::foo in test2::bar.
On Thu, May 17, 2012 at 10:53 AM, LTH wrote:
> Hello,
>
> I'm having some trouble with subclasses accessing other subclasses within
> the same main class.
On Thu, May 17, 2012 at 4:43 AM, Brian Gupta wrote:
> Currently and going forward people will be running multiple versions
> of puppet. What are the plans for puppet compatibility with Modules?
>
> Thinking we may want to be able to specify what version of Puppet is
> running and ask for the compa
Hi all,
In addition to the repository moves that Ken announced[1], we will
soon be removing puppet-tftp. Anyone using this repository should
switch to the puppetlabs-tftp module. The inetd functionality from
puppet-tftp has been ported to puppetlabs-tftp.
Let me know if you have any questions or
On Thu, May 17, 2012 at 12:05 PM, Ryan Coleman wrote:
> On Thu, May 17, 2012 at 4:43 AM, Brian Gupta wrote:
>> Currently and going forward people will be running multiple versions
>> of puppet. What are the plans for puppet compatibility with Modules?
>>
>> Thinking we may want to be able to spec
On Thu, May 17, 2012 at 9:23 AM, Brian Gupta wrote:
> Will general best practice for forge modules to be developed against
> current latest puppet version, or maintain backward compatibility
> going forward? e.g. - let's say there is a version of a module that
> works with 2.7, when Telly ships wi
On Thu, May 17, 2012 at 12:38 PM, Ryan Coleman wrote:
> On Thu, May 17, 2012 at 9:23 AM, Brian Gupta wrote:
>> Will general best practice for forge modules to be developed against
>> current latest puppet version, or maintain backward compatibility
>> going forward? e.g. - let's say there is a ve
On Thu, May 17, 2012 at 9:55 AM, Brian Gupta wrote:
> On Thu, May 17, 2012 at 12:38 PM, Ryan Coleman wrote:
>> On Thu, May 17, 2012 at 9:23 AM, Brian Gupta
>> wrote:
>>> Will general best practice for forge modules to be developed against
>>> current latest puppet version, or maintain backward
On Thursday, May 17, 2012 11:23:40 AM UTC-4, James Sweeny wrote:
>
> You can't require Class['test2::foo'] unless it's already available where
> you're requiring it. You need to include test2::foo in test2::bar.
>
>
Thanks.
If I include test2:foo in test2::bar, do I still need require =>
[Class
The point of the "require" parameter is to define a dependency
relationship. In the example you gave, it doesn't really make sense to have
the exec require a class that does nothing (test2::foo), so you can drop
the require.
On the other hand, if the exec actually needed test2::foo to work correct
On Thursday, May 17, 2012 7:11:18 AM UTC-7, jcbollinger wrote:
>
>
>
> On May 16, 8:51 pm, Joshua Hoblitt wrote:
>
> > as that would
> > preclude ::dev and ::prod being included on the same node.
>
>
> why do you say that? That might become the case if you discovered
> other, similar requir
On Thu, May 17, 2012 at 8:44 PM, Joshua Hoblitt wrote:
>
>
> On Thursday, May 17, 2012 7:11:18 AM UTC-7, jcbollinger wrote:
>
>>
>>
>> On May 16, 8:51 pm, Joshua Hoblitt wrote:
>>
>> > as that would
>> > preclude ::dev and ::prod being included on the same node.
>>
>>
>> why do you say that? Th
I had a bit of a play with this today and couldn't get anything working...
(I am something of as puppet newbie as you can tell so go easy on me!).
In Jeff's example above:
---
# motd module:
class motd($motd_content='UNSET') {
$motd_content_real = $motd_content ? {
UNSET => template("mo
On Thu, May 17, 2012 at 10:03 AM, Nan Liu wrote:
> On Thu, May 17, 2012 at 9:55 AM, Brian Gupta
> wrote:
> > On Thu, May 17, 2012 at 12:38 PM, Ryan Coleman
> wrote:
> >> On Thu, May 17, 2012 at 9:23 AM, Brian Gupta
> wrote:
> >>> Will general best practice for forge modules to be developed aga
I wrote a custom fact called "xen_total_memory" that pulls the xen memory from
xm info:
require 'facter/util/memory'
begin
xen_total_memory = `xm
info`.grep(/total_memory/).to_s.split(/:/)[1].lstrip.chomp
rescue
xen_total_memory = ""
end
Facter.add('xen_total_memory') do
confine :kernel
Facter 2.0.0rc2 is a maintenance release candidate with bug fixes.
It includes contributions from Hailee Kenney.
This release is available for download at:
https://downloads.puppetlabs.com/facter/facter-2.0.0rc2.tar.gz
https://apt.puppetlabs.com
https://yum.puppetlabs.com
See the Verifying Pu
On Thu, May 17, 2012 at 11:30 AM, Rufus McDufus wrote:
> I had a bit of a play with this today and couldn't get anything working...
Hrm, I'm sure we'll be able to sort it out.
> Are you actually trying to overload the real motd module?
No, the module named site and the module named motd can exi
Hello fellow community members!
I just joined you in order to find an information about how to start
using Puppet...
Currently we use cfengine for our legacy system containing several OS
platforms, including physical and virtual servers. For fresh new
hardware and OS versions we decided to go wit
Facter 1.6.9 is a release in the 1.6.x branch with bug fixes and
improvements.
It includes contributions from the following people: Jeff Weiss,
Joachim de Groot, Ken Barber, Matthaus Litteken, Moses Mendoza, and
Stefan Schulte.
This release is available for download at:
https://downloads.puppetl
Welcome :)
I started here:
http://docs.puppetlabs.com/learning/
Lots of good material.
On May 17, 10:24 pm, "Anatoliy Lisovskiy (Wavebourn)"
wrote:
> Hello fellow community members!
>
> I just joined you in order to find an information about how to start
> using Puppet...
>
> Currently we use
Can anyone validate this? I am attempting to run the puppet cert/ca
standlone commands.
I am running form an unchanged master branch and if I run (simplified
for the example):
puppet cert generate host
the resulting ca_key.pem is not encrypted.
If I run :
puppet ca generate host
the resulting ca_
Hi folks,
idont see a separate group for puppet dashboard ,so i guess I'll ask here?
http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html
mentions that we need to have scripts/delayed_jobs running in the
background. and we seem to have that.
But we still somehow have 30,000 pending
In a posting a few days ago was this hiera.yaml source listing:
-
:backends: - json
:hierarchy: - %{fqdn}
- %{lmax_role}_role
- %{lmax_env}_server
- %{pop}.tradefair
- common
:json:
:datadir: - /etc/puppet/priva
One way I have seen for setting up system users is to create them virtually and
then realize them with the spaceship operator, say by ggroup -- like this:
User <| groups == 'wheel' |>
Reference:
http://www.mail-archive.com/puppet-users@googlegroups.com/msg29719.html
In the referenced posting,
On Thu, May 17, 2012 at 9:12 PM, Dan White wrote:
> One way I have seen for setting up system users is to create them
> virtually and then realize them with the spaceship operator, say by ggroup
> -- like this:
>
> User <| groups == 'wheel' |>
>
> Reference:
> http://www.mail-archive.com/puppet-u
Hello,
I tried to setup the following facter module provided by the community:
aedwards-iproute2facts
https://github.com/AbbyEdwards/puppet-iproute2facts
but the facts doesn't appear on the client node when running facter.
Could you tell me what I did wrong please ?
Below, all the steps I did.
Ah, thanks Jeff! I think my problem is that I'm assuming the target module
won't necessarily allow you to pass an alternate source content path, so
I'm basically trying to write a wrapper module which provides an extra
parameter of that content source.
--
You received this message because you
Puppet 3.0.0rc1 is a feature release candidate for the 3.0 series of Puppet.
Puppet 3.0 has breaking changes from the Puppet 2.7 series and has new
dependencies of Facter version 2.0.0 or greater, and Hiera (and the
hiera puppet functions) version 1.0.0 or greater. There are a lot of
new features,
Hi All,
I'm trying use use puppet in masterless mode to automate the setup of an
RT4 server.
I've used the example preseed define from
http://projects.puppetlabs.com/projects/1/wiki/Debian_Preseed_Patterns.
I set up RT4 manually, dumped the debconf keys into a preseed file, rolled
back the VM
40 matches
Mail list logo
