On Tue, Mar 16, 2010 at 1:14 PM, David Schmitt wrote:
> On 3/16/2010 6:13 PM, Joe McDonagh wrote:
>>
>> David Schmitt wrote:
>>>
>>>
>>>
>>> Which leads me to another idea: inter-node dependencies:
>>>
>>> | node a { mysql_db { "foo": ... } }
>>> |
>>> | node b { app { "x": after => A>>Mysql_db["f
Hi all.
I am trying to use debian package preseeding within my modules.
Therefor I have created a preseed_package.pp like:
define authentication::preseed_package ( $ensure ) {
file { "/var/local/preseed/$name.preseed":
source => "$module_path/files/$name.preseed",
>
> Exactly, just add a "ttl-hint: 24" (hours) value to the JSON.
Hmm
I'd saw this as something that would be a property of the fact, rather
than the output of the fact.
That is, I didn't see a need for variable timeouts.
That being said, if we do the "fact.d" for plugins, those scripts wil
David Schmitt wrote:
[crossposting to puppet-dev, please trim follow-ups appropriately]
On 3/16/2010 11:52 AM, Jesús Couto wrote:
On Mon, Mar 15, 2010 at 3:18 PM, Michael DeHaan
mailto:mich...@reductivelabs.com>> wrote:
> that are very much procedural while Puppet manifest are more
On 3/16/10 2:42 PM, "Ben Lavender" wrote:
> I'm wondering if anyone else has run this sort of setup, and if so, if
> you preferred it or came to regret it?
We are doing something similar. We have a "wrapper" script that tries to
rsync down the latest version of /etc/puppet, then runs puppet in
Hi all,
I'm setting up a buzzword-compliant auto-scaling thing on EC2, and I
have something I'd like some more opinion on. Namely, I am going to
be making my own AMI (getting the app set up takes ~20 mins
otherwise), and it seems perfectly workable to store the entire config
in /etc/puppet and ju
On 3/16/2010 6:13 PM, Joe McDonagh wrote:
David Schmitt wrote:
Which leads me to another idea: inter-node dependencies:
| node a { mysql_db { "foo": ... } }
|
| node b { app { "x": after => A>>Mysql_db["foo"]; } }
David, are you suggesting this, or are you saying that this works?
I'm
David Schmitt wrote:
Which leads me to another idea: inter-node dependencies:
| node a { mysql_db { "foo": ... } }
|
| node b { app { "x": after => A>>Mysql_db["foo"]; } }
David, are you suggesting this, or are you saying that this works?
--
Joe McDonagh
AIM: YoosingYoonickz
IRC: joe-mac
Hi list,
is it possible to add a system variable like config_version to a template?
--
Cheers,
Daniel
--
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 th
On 3/16/2010 2:06 PM, Simon Mügge wrote:
Hi there!
Context: HowTo define a somewhat generic serviceinstance
Ive got:
#define.pp
define service::instance ( $instancename, $instanceip ) {
#do stuff
}
#class.pp
class serviceA {
service::instance{"funnyname":
instan
Hi there!
Context: HowTo define a somewhat generic serviceinstance
Ive got:
#define.pp
define service::instance ( $instancename, $instanceip ) {
#do stuff
}
#class.pp
class serviceA {
service::instance{"funnyname":
instancename => ["somenameA", "realnameA"],
See above, I upgraded Ruby to 1.8.5, but then ruby-shadow fails. The link
posted is what I used to get ruby-shadow working long ago under 24.8, but
it's not helping now.
On Mon, Mar 15, 2010 at 10:32 PM, Ohad Levy wrote:
> this breaks because puppet still uses YAML for the local catalog cache.
On Mon, 15 Mar 2010, Gary Larizza Jr. wrote:
> Visiting here -->
> http://docs.reductivelabs.com/references/stable/type.html#package
> It looks like appdmg, pkgdmg, and darwinport are the most viable
> providers for OS X.
I don't use OS X, but it is one of the platforms supported by pkgsrc
(see ht
On Mon, Mar 15, 2010 at 9:52 AM, Bruce Richardson wrote:
> On Mon, Mar 15, 2010 at 09:31:54AM +, Dick Davies wrote:
>> Offhand, does anyone know the difference between the 2
>> constructs below to manage secondary groups ?
>> This is the 'groupadd' provider I think (CentOS).
>> Think I'd prefe
[crossposting to puppet-dev, please trim follow-ups appropriately]
On 3/16/2010 11:52 AM, Jesús Couto wrote:
On Mon, Mar 15, 2010 at 3:18 PM, Michael DeHaan
mailto:mich...@reductivelabs.com>> wrote:
> that are very much procedural while Puppet manifest are more
> useful on a descrip
On Mon, Mar 15, 2010 at 3:18 PM, Michael DeHaan
wrote:
> > that are very much procedural while Puppet manifest are more
> > useful on a description of required software level.
>
> Sort of.
>
> The long story is that we don't have a really native feeling way to
> model multinode deployments and wor
On 3/15/2010 6:49 PM, Michael DeHaan wrote:
Yeah that's certainly one of the things I want to do, as is if we're
calling out to a command to parse it and can cache/process it in one
time as opposed to calling a billion ifconfig/dmidecodes that'd be
good too.
Yep, if you're shelling out or execu
17 matches
Mail list logo
