[Puppet Users] Re: Provider Augeas not functional on Sles10?
No, I have just installed the 4 packages. How do I compile these
bindings, I have not worked with ruby that much.
I have downloaded ruby-augeas-0.3.0.tgz from http://augeas.net/
download/ruby/ but do not know how to go further.
I need rake to compile this Rakefile?
On 14 Dez., 22:52, Dan Bode d...@reductivelabs.com wrote:
Did you compile the ruby augeas bindings?
On Mon, Dec 14, 2009 at 8:24 AM, Os ozzim...@googlemail.com wrote:
Hi,
I have a problem with augeas, puppet and Suse 10 SP2.
Augeas works when I use the augtool to edit files. But I would like to
use it in combination with puppet. My class looks something like this:
augeas {sysctl.conf:
provider = augeas,
context = /files/etc/sysctl.conf,
changes = [
set net.core.wmem_default 262144,
set net.core.wmem_max 262144,
set kernel.sem 250 32000 100 128,
],
}
When I do a 'puppetd -v -d --no-daemonize --onetime' on my node, I get
the following error:
err: //Node...Failed to retrieve current state of resource: Provider
augeas is not functional on this platform
I have installed the following packages:
# yum list | grep augeas
augeas.x86_64 0.5.0-3.1 installed
augeas-devel.x86_64 0.5.0-3.1 installed
augeas-lenses.x86_64 0.5.0-3.1 installed
libaugeas0.x86_64 0.5.0-3.1 installed
Is there something else I am missing or does augeas and puppet do not
work on Sles10 ?
Greetings,
Os
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Installing Specific RPM Version
Douglas Garstang wrote:
Silviu,
My system is aware of both the -1 and -2 releases in the repo.
This is before running puppet...
papp1 ~:# yum list tf-elements-core-tfel0-14.3-1.tf
[ stuff removed ]
Available Packages
tf-elements-core-tfel0.noarch
14.3-1.tf
papp1 ~:# yum list tf-elements-core-tfel0-14.3-2.tf
[ stuff removed ]
Available Packages
tf-elements-core-tfel0.noarch
14.3-2.tf
My manifest has:
package {
tf-elements-core-14.3-1.tf:
ensure = ${release};
}
and here's what puppet logs when it barfs:
debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -q
tf-elements-core-tfel0 --nosignature --nodigest --qf %{NAME}
%|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}
'
debug:
//Node[papp1.fr.twofish.com]/Elements::Setup[tfel0]/Package[tf-elements-core-tfel0]:
Changing ensure
debug:
//Node[papp1.fr.twofish.com]/Elements::Setup[tfel0]/Package[tf-elements-core-tfel0]:
1 change(s)
debug: Package[tf-elements-core-tfel0](provider=yum): Ensuring = 14.3-1.tf
debug: Puppet::Type::Package::ProviderYum: Executing '/usr/bin/yum -d
0 -e 0 -y install tf-elements-core-tfel0-14.3-1.tf'
debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -q
tf-elements-core-tfel0 --nosignature --nodigest --qf %{NAME}
%|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}
Here puppet tells you what it is doing. This output leads me to believe
that /usr/bin/yum -d 0 -e 0 -y install
tf-elements-core-tfel0-14.3-1.tf ends with an error, but I might be
wrong considering the fact that I haven't ever used yum, and I have
failed to use rpm (back when I was a newbie using redhat).
Try switching the versions again and run these two commands puppet used,
adding a echo Return code OK for each just to be sure that the
return value is ok and see what you get.
SIDENOTE: this is a way of debugging something that isn't working in
puppet :-) execs or anything else.
Silviu
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] no certificate found and waitforcert is disabled on all new puppet clients
This looks a lot like this problem: http://projects.reductivelabs.com/issues/2890 Have you tried rm -rf /etc/puppet/ssl on the client? Or you are avoiding exactly that? In 0.25.1 puppet seems to force the usage of the cached certificates despite the fact that some of the data may be wrong, so you should try to clean the ca certificate (in case the ca certificate changed), the certificate request and as a last resort the private key. All this is done by the above rm. (not sure if you knew all that so that's why I'm mentioning). Silviu paul matthews wrote: After further investigation it seems the problem exists with new 0.25.1 clients On the server I run:- puppetca --clean client.hostname On the client I run :- rm /etc/puppet/ssl/certs/client.hostname.pem Followed by the command that brings up the error # /opt/csw/bin/puppetd --trace --debug --test --factsync --server server.hostname.com http://server.hostname.com debug: Failed to load library 'shadow' for feature 'libshadow' debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Failed to load library 'ldap' for feature 'ldap' debug: Puppet::Type::User::ProviderLdap: feature ldap is missing debug: /File[/var/puppet/run/puppetd.pid]: Autorequiring File[/var/puppet/run] debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/puppet/lib]: Autorequiring File[/var/puppet] debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/puppet/clientbucket]: Autorequiring File[/var/puppet] debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet] debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/puppet/ssl/certs] debug: /File[/var/puppet/run]: Autorequiring File[/var/puppet] debug: /File[/var/puppet/log]: Autorequiring File[/var/puppet] debug: /File[/etc/puppet/ssl/private_keys/client.hostname.com.pem]: Autorequiring File[/etc/puppet/ssl/private_keys] debug: /File[/var/puppet/state/graphs]: Autorequiring File[/var/puppet/state] debug: /File[/var/puppet/state]: Autorequiring File[/var/puppet] debug: /File[/var/puppet/facts]: Autorequiring File[/var/puppet] debug: /File[/var/puppet/client_yaml]: Autorequiring File[/var/puppet] debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/public_keys/client.hostname.com.pem]: Autorequiring File[/etc/puppet/ssl/public_keys] debug: Finishing transaction 75308830 with 0 changes debug: Using cached certificate for ca warning: peer certificate won't be verified in this SSL session debug: Using cached certificate_request for client.hostname.com http://client.hostname.com debug: Using cached certificate for ca warning: peer certificate won't be verified in this SSL session debug: Using cached certificate for ca warning: peer certificate won't be verified in this SSL session Exiting; no certificate found and waitforcert is disabled I'm afraid it has me really stumped for ideas though Paul 2009/12/14 paul matthews paulsmatth...@googlemail.com mailto:paulsmatth...@googlemail.com Thanks Ohad for pointing this out - schoolboy error on my part. Unfortunately, this has not fixed things - both server and client are running 25.1. Do you know of anything else that may be causing this Thanks Paul 2009/12/14 Ohad Levy ohadl...@gmail.com mailto:ohadl...@gmail.com server must be newer or equal to the clients.. Ohad On Mon, Dec 14, 2009 at 7:36 PM, paul matthews paulsmatth...@googlemail.com mailto:paulsmatth...@googlemail.com wrote: Hi, I'm not too sure why this has cropped up after working fine for months but on new clients I get the following errors:- Thanks # puppetd --test warning: peer certificate won't be verified in this SSL session warning: peer certificate won't be verified in this SSL session warning: peer certificate won't be verified in this SSL session Exiting; no certificate found and waitforcert is disabled Most of the articles I've read suggest a much earlier bug. As it's a closed test environment I've set autosign = true in /etc/puppet.conf Does anyone know how I get round this. Clients are running 0.25.1, server = 0.24.8 Thanks Paul -- Paul Matthews -- --
Re: [Puppet Users] no certificate found and waitforcert is disabled on all new puppet clients
Silviu, That fixed it. I had assumed removing the .pem file ( /etc/puppet/ssl/certs/client.hostname.pem ) would be enough but removing the whole directory was the answer Thanks very much Paul 2009/12/15 Silviu Paragina sil...@paragina.ro This looks a lot like this problem: http://projects.reductivelabs.com/issues/2890 Have you tried rm -rf /etc/puppet/ssl on the client? Or you are avoiding exactly that? In 0.25.1 puppet seems to force the usage of the cached certificates despite the fact that some of the data may be wrong, so you should try to clean the ca certificate (in case the ca certificate changed), the certificate request and as a last resort the private key. All this is done by the above rm. (not sure if you knew all that so that's why I'm mentioning). Silviu paul matthews wrote: After further investigation it seems the problem exists with new 0.25.1 clients On the server I run:- puppetca --clean client.hostname On the client I run :- rm /etc/puppet/ssl/certs/client.hostname.pem Followed by the command that brings up the error # /opt/csw/bin/puppetd --trace --debug --test --factsync --server server.hostname.com http://server.hostname.com debug: Failed to load library 'shadow' for feature 'libshadow' debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Failed to load library 'ldap' for feature 'ldap' debug: Puppet::Type::User::ProviderLdap: feature ldap is missing debug: /File[/var/puppet/run/puppetd.pid]: Autorequiring File[/var/puppet/run] debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/puppet/lib]: Autorequiring File[/var/puppet] debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/puppet/clientbucket]: Autorequiring File[/var/puppet] debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet] debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/puppet/ssl/certs] debug: /File[/var/puppet/run]: Autorequiring File[/var/puppet] debug: /File[/var/puppet/log]: Autorequiring File[/var/puppet] debug: /File[/etc/puppet/ssl/private_keys/client.hostname.com.pem]: Autorequiring File[/etc/puppet/ssl/private_keys] debug: /File[/var/puppet/state/graphs]: Autorequiring File[/var/puppet/state] debug: /File[/var/puppet/state]: Autorequiring File[/var/puppet] debug: /File[/var/puppet/facts]: Autorequiring File[/var/puppet] debug: /File[/var/puppet/client_yaml]: Autorequiring File[/var/puppet] debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/public_keys/client.hostname.com.pem]: Autorequiring File[/etc/puppet/ssl/public_keys] debug: Finishing transaction 75308830 with 0 changes debug: Using cached certificate for ca warning: peer certificate won't be verified in this SSL session debug: Using cached certificate_request for client.hostname.com http://client.hostname.com debug: Using cached certificate for ca warning: peer certificate won't be verified in this SSL session debug: Using cached certificate for ca warning: peer certificate won't be verified in this SSL session Exiting; no certificate found and waitforcert is disabled I'm afraid it has me really stumped for ideas though Paul 2009/12/14 paul matthews paulsmatth...@googlemail.com mailto:paulsmatth...@googlemail.com Thanks Ohad for pointing this out - schoolboy error on my part. Unfortunately, this has not fixed things - both server and client are running 25.1. Do you know of anything else that may be causing this Thanks Paul 2009/12/14 Ohad Levy ohadl...@gmail.com mailto:ohadl...@gmail.com server must be newer or equal to the clients.. Ohad On Mon, Dec 14, 2009 at 7:36 PM, paul matthews paulsmatth...@googlemail.com mailto:paulsmatth...@googlemail.com wrote: Hi, I'm not too sure why this has cropped up after working fine for months but on new clients I get the following errors:- Thanks # puppetd --test warning: peer certificate won't be verified in this SSL session warning: peer certificate won't be verified in this SSL session warning: peer certificate won't be verified in this SSL session Exiting; no certificate found and waitforcert is disabled Most of the articles I've read suggest a much earlier bug. As it's a closed test environment I've set autosign =
Re: [Puppet Users] puppet-dashboard
Luke, Interesting. I think the issue here is with migration order. The Report#success? method depends on the existence of a `success` boolean field on the reports table, which may happen at a later migration than when the method is called. Flattening the migrations into a single file should alleviate this and is also a good idea in general. I'll fix this ASAP and release a new point version. Thanks for the heads up. -- Rein Henrichs http://reductivelabs.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Configuring Networking
On Tue, Dec 15, 2009 at 3:14 PM, Scott Smith sc...@ohlol.net wrote:
Douglas Garstang wrote:
I'll trying to work out the best way to configure networking in
puppet, being routes, dns and ip addresses.
http://github.com/ohlol/puppet-network
Doesn't handle route-#{iface} files, but would be trivial to add.
-scott
Thanks Scott, so you have some definitions to reconfigure networking,
but how do you ensure that they run BEFORE everything else?
Doug.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Configuring Networking
Scott Smith wrote:
http://github.com/ohlol/puppet-network
Doesn't handle route-#{iface} files, but would be trivial to add.
Scratch that -- it does! :) Been a long time since I wrote that.
-scott
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Configuring Networking
Douglas Garstang wrote:
On Tue, Dec 15, 2009 at 3:14 PM, Scott Smith sc...@ohlol.net wrote:
Douglas Garstang wrote:
I'll trying to work out the best way to configure networking in
puppet, being routes, dns and ip addresses.
http://github.com/ohlol/puppet-network
Doesn't handle route-#{iface} files, but would be trivial to add.
-scott
Thanks Scott, so you have some definitions to reconfigure networking,
but how do you ensure that they run BEFORE everything else?
You can use require =
-scott
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Announcing Puppet Dashboard 0.1.0 Release
I understand and sympathize with the political/legal reasons. We obviously want to do our best to support default RHEL4 configurations (since we have so many RHEL4 nodes running Puppet) and it is unfortunate that the available rake RPM lags JUST behind our requirements. Try running things with a rake = 0.8.3 dependency in config/environment.rb and see if things break. There may be a simple way to fix it (by monkey-patching rake inside our application, for instance) or it just might work, which would be fantastic. I'll do some digging myself as well. On Tue, Dec 15, 2009 at 3:00 PM, jw2dot...@gmail.com jw2dot...@gmail.comwrote: I'm sure this RubyGems topic probably deserves it's own thread... We go through a lot of political/legal paperwork at $WORK to deploy open-source software on our Red Hat systems. Throwing logic aside, we managed to get approval to use any RPM package from EPEL, but that's not the case for RubyGems out on rubyforge.org. RPM packages are simple to maintain and track for inventory purposes, but I agree with your comments on packaging systems falling behind.. (We still have lots of RHEL4 boxes, which can be very difficult with the ruby RPMs offered with that distro). Thanks for the gem docs. I'll pursue that route. On Dec 15, 4:43 pm, Rein Henrichs r...@reductivelabs.com wrote: At the risk of sparking another flame war, the best way to manage Ruby library dependencies is via Rubygems rather than your platform's packaging system -- which tends to have out of date Ruby packages and can conflict with installed gems[1]. Fortunately, it is entirely possible and in fact quite easy to install and use Rubygems as a local user (rather than root)[2]. We've done our best to remove external dependencies but this one unfortunately remains. The bottom line is that rake 0.8.4 is the first known-good version for the version of Rails that Dashboard uses and, as such, the first that we currently support. However, the rake install task (which is the only thing that requires rake aside from running the spec suite) may work or be made to work with older versions of rake. We would be happy to bump the dependency down to 0.8.3 to provide out-of-the-box support for RHEL5 and will gratefully accept patches that let us do that. [1] Seehttps://help.ubuntu.com/community/RubyOnRails [2]http://docs.rubygems.org/read/chapter/3 On Tue, Dec 15, 2009 at 1:09 PM, jw2dot...@gmail.com jw2dot...@gmail.comwrote: Bummer. Requires rake = 0.8.4, but RHEL5/EPEL is only 0.8.3. http://download.fedora.redhat.com/pub/epel/5/x86_64/repoview/rubygem-. .. On Dec 14, 3:29 pm, Rein Henrichs r...@reductivelabs.com wrote: Greetings Puppeteers, It's the holidays once again and, in the spirit of the season, I bring you the immediate release of Puppet Dashboard 0.1.0, codenamed Wira. Because the Wira is a car. From Malaysia. And cars have dashboards. Even cars from Malaysia. This release includes run success and total run time graphs and a global status drop-down tab that provides at-a-glance system status updates. We are still deciding on which information to present where and how best to present it, so expect these to change in upcoming releases as we converge on the most useful set of data to display. Coincidentally, this would be a great time to tell us which information is most important to you on which pages. You could even reply to this message on the list if you want (hint). Also, at the request of just about everyone, I've posted a tour of the latest Dashboard release on the Reductive Labs blog athttp:// reductivelabs.com/2009/12/14/a-tour-of-puppet-dashboard-0-1-0. Yes, it includes screenshots. Huzzah. Get the code athttp://github.com/reductivelabs/puppet-dashboard. Submit feature requests and bug reports athttp:// projects.reductivelabs.com/projects/dashboard. Have a great holiday season, folks. -- Rein Henrichshttp://reductivelabs.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com puppet-users%2bunsubscr...@googlegroups.compuppet-users%252bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Rein Henrichshttp://reductivelabs.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com . For more options, visit this group at
Re: [Puppet Users] Configuring Networking
On Tue, Dec 15, 2009 at 3:21 PM, Scott Smith sc...@ohlol.net wrote:
Douglas Garstang wrote:
On Tue, Dec 15, 2009 at 3:14 PM, Scott Smith sc...@ohlol.net wrote:
Douglas Garstang wrote:
I'll trying to work out the best way to configure networking in
puppet, being routes, dns and ip addresses.
http://github.com/ohlol/puppet-network
Doesn't handle route-#{iface} files, but would be trivial to add.
-scott
Thanks Scott, so you have some definitions to reconfigure networking,
but how do you ensure that they run BEFORE everything else?
You can use require =
Require in a definition, or in the classes? It doesn't seem feasible
to me to put a require on every single object in my puppet config
requiring networking!
Doug
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Configuring Networking
On Tue, Dec 15, 2009 at 3:22 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
On Tue, Dec 15, 2009 at 3:21 PM, Scott Smith sc...@ohlol.net wrote:
Douglas Garstang wrote:
On Tue, Dec 15, 2009 at 3:14 PM, Scott Smith sc...@ohlol.net wrote:
Douglas Garstang wrote:
I'll trying to work out the best way to configure networking in
puppet, being routes, dns and ip addresses.
http://github.com/ohlol/puppet-network
Doesn't handle route-#{iface} files, but would be trivial to add.
-scott
Thanks Scott, so you have some definitions to reconfigure networking,
but how do you ensure that they run BEFORE everything else?
You can use require =
Require in a definition, or in the classes? It doesn't seem feasible
to me to put a require on every single object in my puppet config
requiring networking!
Doug
And... even then I'd be requiring a definition, not a class. Is that
even valid? How would the syntax look?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Configuring Networking
Douglas Garstang wrote: On Tue, Dec 15, 2009 at 3:47 PM, Peter Meier peter.me...@immerda.ch wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 First question... are definitions executed in the order they appear? puppet doesn't execute anything. it manages resources and defines are resources as well. Fine. Does puppet manages resources and defines in the order they appear? No, it's declarative, not imperative. http://en.wikipedia.org/wiki/Declarative_programming http://en.wikipedia.org/wiki/Imperative_programming -scott -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Configuring Networking
Douglas Garstang writes: On Tue, Dec 15, 2009 at 3:47 PM, Peter Meier peter.me...@immerda.ch wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 First question... are definitions executed in the order they appear? puppet doesn't execute anything. it manages resources and defines are resources as well. Fine. Does puppet manages resources and defines in the order they appear? Ordering is indeterminate unless require or before are used in resource definitions, which then produce the declared ordering relationship. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Configuring Networking
On Tue, Dec 15, 2009 at 3:59 PM, Steven VanDevender ste...@uoregon.edu wrote: Douglas Garstang writes: On Tue, Dec 15, 2009 at 3:47 PM, Peter Meier peter.me...@immerda.ch wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 First question... are definitions executed in the order they appear? puppet doesn't execute anything. it manages resources and defines are resources as well. Fine. Does puppet manages resources and defines in the order they appear? Ordering is indeterminate unless require or before are used in resource definitions, which then produce the declared ordering relationship. I was hoping that was just classes. Watching the logs seemed to indicate that definitions were acted upon first. Oh well, back to my original question. How can I make sure that my network definitions are done FIRST? And before anyone says to use require, I can't a) put require on every single damn resource in my puppet config requiring the networking. That's asinine and b) How do you require a definition? That makes no sense. Doug. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Configuring Networking
On Dec 15, 5:01 pm, Douglas Garstang doug.garst...@gmail.com wrote: I'll trying to work out the best way to configure networking in puppet, being routes, dns and ip addresses. First question... are definitions executed in the order they appear? Do not attempt to rely on file order to control the sequence in which Puppet applies resources to the client system. Individual resources should instead use the require and / or before parameters to express dependencies on other resources or classes. I note also that you need to already have at least a partially- functional network configuration for Puppet to be able to retrieve its catalog from a remote puppetmaster. That makes for a bit of a chicken- and-egg problem with using Puppet to set up networking. It's not insurmountable, and no doubt you've already thought about that, but I just thought I'd mention it. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Configuring Networking
Douglas Garstang wrote: b) How do you require a definition? That makes no sense. A definition is essentially just a custom resource. -scott -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Purging unmanaged augeas entries?
Frank Sweetser f...@wpi.edu writes: I'm in the process of setting up sudoers entries to get managed by augeas. If you can insure a suitable recent sudo, you can use sudo's #includedir option and just manage a directory. seph -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
