-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 02 April 2008, Paul Lathrop wrote:
Hi Luke,
Comments inline:
On Mon, Mar 31, 2008 at 1:46 PM, Luke Kanies [EMAIL PROTECTED] wrote:
* Should it be part of Puppet (vs. a separate tool)?
I think it should be a separate tool, to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 09 May 2008, Luke Kanies wrote:
On May 9, 2008, at 3:20 PM, Marcin Owsiany wrote:
I'm not sure about the exact syntax, but I do think that there
should be
a sticky relation feature (possibly with another feature to
unstick
that).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 30 May 2008, James Turnbull wrote:
Signed-off-by: James Turnbull [EMAIL PROTECTED]
---
lib/puppet/sslcertificates/ca.rb | 11 ---
1 files changed, 8 insertions(+), 3 deletions(-)
diff --git
Luke Kanies wrote:
On Jun 13, 2008, at 9:55 PM, aj wrote:
Aye, #1365..
Basically you can call ipaddress_eth0 (and ipaddress_eth0_0 et al)
from
inside a Puppet manifest, and you can see the output when you call
`facter`, but when you try to call `facter ipaddress_eth0` it'll
return
Luke Kanies schrieb:
On Oct 14, 2008, at 9:26 AM, Sean E. Millichamp wrote:
-Puppet.debug Running chcon #{flag} #{value} #{file}
-retval = system(chcon #{flag} #{value} #{file})
+Puppet.debug Running chcon -h #{flag} #{value} #{file}
+retval = system(chcon
Brice Figureau schrieb:
On Tue, 2008-11-04 at 10:04 -0600, Luke Kanies wrote:
On Nov 4, 2008, at 9:28 AM, Brice Figureau wrote:
On Tue, 2008-11-04 at 09:05 -0600, Luke Kanies wrote:
I'd do that. Just generate docs for what people specify.
I'd also probably have puppetdoc accept standard
Luke Kanies schrieb:
Hi all,
These problems keep cropping up, and it seems like we need a more
comprehensive solution.
The current 'master' branch has permission problems in puppetmasterd
(as implied), and it's basically a race condition that shows up again
and again.
[...]
Luke Kanies schrieb:
On Oct 31, 2008, at 10:33 AM, jerico wrote:
I don't agree on that. It might be a specially declarative and less
procedural/imperative language and is probably not turing complete (no
idea about that, I didn't try the proof!) But maybe this is just an
argument about
Luke Kanies schrieb:
On Nov 5, 2008, at 1:14 AM, David Schmitt wrote:
Luke Kanies schrieb:
On Oct 31, 2008, at 10:33 AM, jerico wrote:
I don't agree on that. It might be a specially declarative and less
procedural/imperative language and is probably not turing complete
(no
idea about
Luke Kanies schrieb:
Note: the user tags are not stored in the rails database except
under
the special resource parameter tag. This also doesn't seem right.
Really? So if someone sets 'tags' parameters on a resource, they're
not stored in the db as parameters?
No they're stored as a
Nigel Kersten schrieb:
On Tue, Jun 2, 2009 at 2:48 PM, Luke Kanies l...@madstop.com wrote:
* Do we still want an environment specified on the command line to be
overridden by an environment fact ?
(I'm unsure about which should take precedence myself)
Erm, no idea? You tell me.
I
Luke Kanies schrieb:
On Jun 5, 2009, at 7:53 AM, Stephan Gorget wrote:
Luke Kanies a écrit :
On May 29, 2009, at 8:06 AM, Stephan Gorget wrote:
I rewrote the patch to match what you said, but package installation
doesn't respect ordering now because I no longer use
resource.evaluate(), I
Luke Kanies schrieb:
On Jun 12, 2009, at 8:51 AM, James Turnbull wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
There are quite a lot of tickets that aren't assigned to a target
release or assigned to Unplanned.
The unassigned tickets are:
Peter Meier wrote:
Hi
Since we're all having this conversation I guess some logical
questions are what other language features? Loops? A lot of people
want a loop syntax?
Hashes before loops, and really, 99% of people who want loops do so
because they don't want to manage resources.
Brice Figureau wrote:
On Wed, June 17, 2009 11:53, Thomas Bellman wrote:
Brice Figureau wrote:
I've almost finished node matching, even though I'm not really satisfied
of how it works. Node matching is O(1) for the moment, but as soon as
you
add regexp in the mix, it becomes essentially
Luke Kanies wrote:
I like the idea, but I'm not too stoked with the implementation.
Having a separate attribute that's only sometimes used seems clumsy.
That being said, I don't have a better idea, either.
Anyone have any other ideas on how to specify this?
Why not extending the
Luke Kanies wrote:
I can actually think of *two* new states that one might want: add to
fstab
and remount an existing mount with new flags, and add to fstab but
don't
touch an existing mount at all. One might for example want to have
a line
in fstab for a USB stick, which defaults
Peter Meier wrote:
Hi
I'd like to suggest extending this feature so you can choose to only
store facts as well, and given that, it probably makes sense to allow
you to choose whether or not nodes are stored.
So maybe a multi-valued setting that allows you to choose what subset
of facts,
Luke Kanies wrote:
On Jul 1, 2009, at 11:06 AM, Christian Hofstaedtler wrote:
* Luke Kanies l...@madstop.com [090701 18:01]:
On Jul 1, 2009, at 3:19 AM, David Schmitt wrote:
Luke Kanies wrote:
I can actually think of *two* new states that one might want:
add to
fstab
and remount
Avi Miller wrote:
3. There is a 4000 character limit (in Oracle, possibly different in
MySQL/PostgreSQL) for a VARCHAR2 column. The following columns are
created as text by default: resource.title, fact_values.value,
param_values.value; what is the likelihood of any of these being larger
aurelien.degrem...@cea.fr wrote:
Presently, puppetd can output 2 kinds of informations:
- first, a trace-like output with all the 'notice:', info and warning/err
messages.
This is much more like a trace, usefull for understanding unexpected
behaviour, but not really usefull for admins
Luke Kanies wrote:
On Jul 16, 2009, at 8:14 AM, aurelien.degrem...@cea.fr wrote:
Hello
I'm interest by helping fixing this but I'm not sure I will have
time to dig into Puppet code.
Moreover, it seems puppet arguments are a bit tricky because lot of
arguments are not handled in the
Luke Kanies wrote:
The other cases that come to my mind are restarting puppetd from
within
a transaction and aborting a --test run from the commandline with ^C.
The former probably should wait until the end of the (presumably
bootstrap) transaction, while the latter should abort
Brice Figureau wrote:
Maybe what worries me in fact, is that most people think that using
--debug --trace on the client is enough. But all what they'll get is the
client side trace which ends up as not being useful at all.
The perfect fix for my issue, would be when --debug or --trace are
Thomas Bellman wrote:
Luke Kanies wrote:
On Jul 31, 2009, at 9:13 AM, Thomas Bellman wrote:
[...]
@@ -61,10 +61,14 @@ Put angle brackets around each octet in the
node's IP address::
end
end
re = Regexp.compile(regexp, reflags, lang)
-if global
-
Thomas Bellman wrote:
David Schmitt wrote:
Thomas Bellman wrote:
I could do it something like this:
strings = [args[0]].flatten
if global
result = strings.collect { |s| s.gsub(re, replacement) }
else
result = strings.collect { |s| s.sub(re, replacement
Luke Kanies wrote:
I've also got a 'git-cleanup-branch' script that cleans up things
like this by looking through the git history to see if a given commit
(as determined by its summary, rather than its commit, since that
will change on a rebase) is merged, and if so removes the local and
+1.
Luke Kanies wrote:
Given that it's my goal to make the next major release 1.0, there's
one big compatibility change we should probably make as part of that
release: Switching away from dynamic scoping.
This is obviously pretty bad, but I've not gotten around to fixing it,
mostly
Luke Kanies wrote:
On Sep 11, 2009, at 4:51 PM, Markus wrote:
Something I got to wondering about after our chat; would this require
the attribute names to be unique up to potentially co-included classes
(e.g. effectively global)? In other words, if I wrote something like
this:
class
Bostjan Skufca wrote:
Something like combined primary key in relational database.
For example, if I want to write a type for managing mysql users, I
would like to specify the namevar as a combination of:
- username and
- hostname
Ofcourse you can do it like:
mysql_user {u...@host:
but
R.I.Pienaar wrote:
hello,
- David Schmitt da...@dasz.at wrote:
Having node{} statements as definitive source for variables supports
the split between configuration (variables, class lists) and the
actual implementation within classes and modules. This also ties very
cleanly
Luke Kanies wrote:
Regarding the naming collisions, It might be nice to have namespaces
available for that:
class jokeofthedayserver($port) {...}
class cokemachinestatusserver($port) {...}
$jokeofthedayserver::port = 4000
$cokemachinestatusserver::port = 4001
Steven Jenkins wrote:
Markus Roberts wrote:
Mark Drayton made a good point
(http://projects.reductivelabs.com/issues/2601#note-3); are we making
the code more complicated than it needs to be to get less functionality
than we might otherwise have? Rather than saying that it takes one
Brice Figureau wrote:
On Tue, 2009-09-22 at 08:38 +0200, David Schmitt wrote:
mar...@reality.com wrote:
The idea is that x/y/z (chained division) is rarer than regexp--in part
because nobody trusts My Dear Aunt Sally that far.
So it gets rid of the problem that was originally discovered
Brice Figureau wrote:
On Fri, 2009-10-23 at 10:24 +0200, David Schmitt wrote:
Brice Figureau wrote:
This is not the right fix, but more a hackish workaround.
text = facts.render(format)
-return {:facts_format = format, :facts = CGI.escape(text)}
+return
Markus Roberts wrote:
This is an extension of the prior patch to cover additional cases
found by automated testing (repeated catalog runs with a 1% chance
of timeout forced on all timeout-bound operations, ~5000 runs).
The new cases recurred multiple times (100 each) and in a final pass
Markus Roberts wrote:
I ran it, and found nothing new, but it occurs to me that, while a
valuable additional test the enumerated forced-timeout method
actually covers fewer cases than the random method. To see this,
consider a hypothetical bug that caused the client to exit
Markus Roberts wrote:
It'd be great if you could abolish the parse-order dependency
altogether. As long as all variable/value reference chains form a
directed acylcic graph, they could be evaluated after finishing the
parse, regardless of order.
Could you
Peter Meier wrote:
Are we not using the rails validation methods on purpose ?
e.g.
validate_uniqueness_of :name
will ensure that no two (hosts, parameters etc) will be created.
This ofcourse generates another select statement each time (to verify if
it already exists)...
That sounds like
Markus Roberts wrote:
BTW, I'm wondering how puppetdoc will deal with future
interpretation :-(
A simple way would be to just ignore that in puppetdoc. Then strings
only show the variable name and that's it.
For a more intimate support, you can evaluate the future down to either
the value,
On 15.12.2009 01:53, Jesse Wolfe wrote:
Make sure that we don't try to do anything to webrick until it has
really started.
Signed-off-by: Jesse Wolfejes5...@gmail.com
---
lib/puppet/network/http/webrick.rb |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git
[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
mich...@reductivelabs.com mailto:mich...@reductivelabs.com wrote:
that are very much procedural while Puppet manifest are more
On 3/17/2010 5:25 AM, Dan Bode wrote:
Hi All,
I have been working on a type/provider for sudoers and would appreciate
any feedback.
It can be found at:
http://github.com/bodepd/puppet-sudo
There are some slight limitations documented in the README.
Plenty of examples in the tests directory
On 3/17/2010 8:42 PM, Luke Kanies wrote:
On Mar 16, 2010, at 4:07 AM, 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
mich...@reductivelabs.com mailto:mich
On 23.03.2010 00:07, James Turnbull wrote:
Bug #2247 - enablerepo and disablerepo for yum type (which has got 7
votes and we've bumped from three releases now)
Bug #3113 - When importing a manifest puppet needs to chill Bug
(Martin's patch is tested)
Bug #3387 - backslashes aren't correctly
On 3/22/2010 9:04 PM, Dan Bode wrote:
* Overloading the type with the three different types of records
confuses me. Perhaps defines for each of the three types could
improve the situation?
This is not possible with parsedfile. Parsedfile is not able to
synchronize reading/writing
Hi Dan, Trevor, *
On 3/25/2010 11:16 AM, Trevor Vaughan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Inline...
On 03/25/2010 04:09 AM, Dan Bode wrote:
snip/
I can also imagine use cases where this would be too limiting. If two
classes wanted to specify the same Cmnd_Alias for two
Am 26.03.2010 23:10, schrieb Nigel Kersten:
@@ -47,9 +49,12 @@ Puppet::Type.type(:package).provide :dpkg, :parent =
Puppet::Provider::Package
if hash[:status] == 'not-installed'
hash[:ensure] = :purged
-elsif hash[:status] != installed
+
Hi Eric,
I've created http://projects.reductivelabs.com/issues/3444 for you. You
can subscribe there and add any useful info you might have, like log
output from your Puppet master and client. You can generate these logs
by running the Puppet master and client with the --trace --verbose
On 4/11/2010 4:53 AM, Daniel Pittman wrote:
amrsetamr...@gmail.com writes:
Daniel Pittman wrote:
amrsetamr...@gmail.com writes:
Would it be possible to do something like:
file { /foo/voo/bar/baz :
[...]
}
Isn't that just:
file { /foo: owner = foo, recurse = true }
file {
On 4/20/2010 11:53 AM, Thomas Bellman wrote:
Luke Kanies wrote:
Because imports are parse-time, not compile-time. That is, they're
evaluated as the file is read, rather than when a given host's
configuration is compiled.
Related: I do find it a bit confusing that you can write imports
On 4/30/2010 10:45 AM, James Turnbull wrote:
Signed-off-by: James Turnbullja...@lovedthanlost.net
---
lib/facter/ipaddress.rb | 32 ++---
lib/facter/kernel.rb |6 ++-
lib/facter/macaddress.rb | 29 +---
lib/facter/util/resolution.rb | 100
Do you think this plus the relationship syntax (including the
many to many resulting from relationships between collections)
essentially cover the concerns, or are there more steps we should
be planning on taking?
its going to suck explaining to newbies but I think it does all it
needs.
What
On 5/17/2010 8:34 AM, Luke Kanies wrote:
On May 16, 2010, at 5:14 PM, Matthew Delves wrote:
Hey All,
I'm wondering what the status of Puppet under Windows is. Is there a
howto out there for testing this?
David Schmitt is working on the Windows support right now, but we don't
yet have
On 5/17/2010 1:27 PM, James Turnbull wrote:
I'll push my version to github when I've got something approaching testable.
David
I've had quite a lot of feedback from people who have indicated that
a thin layered tool that integrates with WMI/PowerShell would suit
equally well as a fat client
On 5/21/2010 5:56 PM, Annie Rana wrote:
Thanks much all for your inputs, suggestions and ideas. I am a
researcher and I am planning to use Puppet as policy-based management
system. As we all know that puppet provides a low-level declarative
language to define policies so I was interested to know
On 6/4/2010 3:45 AM, Daniel Pittman wrote:
Well, my use case pretty much always comes down to do something for this data
about this host, and hasn't ever gotten more than two levels deep:
backuppc::server needs a per-client configuration
per-client configuration needs this clients
On 6/3/2010 3:54 AM, Trevor Vaughan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been following this thread with interest and I think that Donavan
is hitting upon something that I've also been wanting.
However, the way I was looking at it was as a set of atomic, optionally
Hi all,
a recurring problem with the namevars are resources that do not have a
natural unique single-property key. For example, mysql users are defined
by their username and the host(-pattern) they are connection from.
Traditionally, this was solved by ugly hackery in the type. In the
this as a core feature, that also can be used
by current types.
Best Regards, DavidS
Trevor
On 06/04/2010 06:45 AM, David Schmitt wrote:
Hi all,
a recurring problem with the namevars are resources that do not have a
natural unique single-property key. For example, mysql users are defined
pretty sure you'd want to use the existing require/before syntax to
specify the dependencies on locks.
Best Regards, David
Trevor
On 06/04/2010 04:33 AM, David Schmitt wrote:
On 6/3/2010 3:54 AM, Trevor Vaughan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been following
On 6/4/2010 4:27 PM, Markus Roberts wrote:
# redefine resources
mysql_user {
frob: ;
f...@%: ;
foo: host = localhost;
f...@localhost: ;
}
The last pair isn't really a duplicate though, unless you change foo to
frob or frob to foo.
Exactly. I'm glad if that's the only
Am 05.06.2010 05:33, schrieb Daniel Pittman:
David Schmittda...@dasz.at writes:
On 6/4/2010 3:45 AM, Daniel Pittman wrote:
Well, my use case pretty much always comes down to do something for this data
about this host, and hasn't ever gotten more than two levels deep:
backuppc::server
Am 06.06.2010 01:30, schrieb Markus Roberts:
It seems to me we kind of have two problems: How to uniquely
specify the resource with parameters, and how to specify it with a
resource reference. Your solution (the title becomes a template
filled in by the different parameters)
On 6/7/2010 3:08 AM, Daniel Pittman wrote:
Luke Kaniesl...@puppetlabs.com writes:
To me, we need to be focusing on fixing Collection so it actually works well
for this purpose. It sounds like most of Daniel Pittman's needs would be
solved by better resource collection.
Well, maybe. One use
On 6/7/2010 12:19 AM, Markus Roberts wrote:
David --
If I'm understanding you correctly, this is completely opposite of what
was discussed at puppet camp (which leads me to suspect that I'm not
understanding you correctly).
My understanding is that the situation can be broken down into
On 6/7/2010 3:16 PM, Daniel Pittman wrote:
concat works reasonably well, but depends no multiple fragments scattered over
multiple systems, and storeconfigs, which makes for two problems:
One, we now have anything up to two hours for an update to propagate, as
puppet needs to run on the source
On 6/7/2010 4:43 PM, Markus Roberts wrote:
David --
That's the internal/implementation side of it. Please see below for
explainations about the frills
I added for the more user/developer oriented spec in my mail.
I saw it, I'm just not sold on it (yet). The internal side, as you call
it,
On 6/8/2010 7:18 PM, Markus Roberts wrote:
David --
I'll leave the final decision to you. Just let me restate that I
believe that having the additional
render or to_s block (what I called canonical_form in
4c0c0e2a.6090...@dasz.at mailto:4c0c0e2a.6090...@dasz.at)
for display purposes[1]
On 6/9/2010 6:19 PM, Markus Roberts wrote:
I'd advocate a mkdir -p style solution, unless anyone can see problems
with that.
Well, I would say that we should either be localizing or not. We're now
defaulting to a value that works great for the linux world but doesn't even
work in the
On 6/9/2010 3:08 PM, Luke Kanies wrote:
On Jun 9, 2010, at 3:27 AM, David Schmitt wrote:
On 6/8/2010 7:18 PM, Markus Roberts wrote:
David --
I'll leave the final decision to you. Just let me restate that I
believe that having the additional
render or to_s block (what I called
On 6/10/2010 3:36 AM, Daniel Pittman wrote:
Luke Kaniesl...@puppetlabs.com writes:
1) Easy way to force updates when a required catalog has been changed.
(This doesn't automatically fix the problem of new data showing up, only
changed data.)
2) With good graph viewing, a
On 10.06.2010 18:55, Luke Kanies wrote:
Signed-off-by: Luke Kaniesl...@puppetlabs.com
---
autotest/images/fail.png| Bin 0 - 19978 bytes
autotest/images/pass.png| Bin 0 - 21763 bytes
autotest/images/pending.png | Bin 0 - 19745 bytes
autotest/watcher.rb | 124
On 6/21/2010 11:16 PM, Thomas S Hatch wrote:
I have written puppet types for cobbler, they seem to work very well,
but I have a question. Because of the very nature of cobbler there are
a lot of interconnected requirements, and all of these requirements are
directly inferred by the puppet
On 9/16/2010 1:26 AM, Luke Kanies wrote:
Hi all,
I've just stuck my proposal for a Catalog Service (which we've been
bandying about internally for a while, and which I've been thinking
about even longer) on the wiki:
On 9/17/2010 11:03 PM, Luke Kanies wrote:
On Sep 17, 2010, at 4:41 AM, David Schmitt wrote:
On 9/16/2010 1:26 AM, Luke Kanies wrote:
Hi all,
I've just stuck my proposal for a Catalog Service (which we've
been bandying about internally for a while, and which I've been
thinking about even
+1, no comments.
;-) D.
On 9/24/2010 12:04 PM, Brice Figureau wrote:
On Thu, 2010-09-23 at 18:27 -0700, Jacob Helwig wrote:
Actually, for me, it's harder to top-post, since my mail client is setup
to automatically put me just above my signature (below the quoted email)
when composing. ;-)
On Tue, 28 Sep 2010 12:15:47 -0700, Nigel Kersten nig...@google.com
wrote:
Have we been able to come up with any use cases other than packages
where combining offers a benefit?
The nagios types seem to be reparsing/rewriting the target on every
resource. Having them grouped and written out at
On Tue, 28 Sep 2010 17:23:18 -0700, Luke Kanies l...@puppetlabs.com
wrote:
* I want to create a Response object that gets queued, rather than the
actual object created, because it will make error propagation and other
stuff a lot easier. I plan to duplicate the http model (e.g., response
On 9/29/2010 4:34 AM, Lindsay Holmwood wrote:
On 29 September 2010 07:27, Luke Kaniesl...@puppetlabs.com wrote:
On Sep 28, 2010, at 8:41, James Turnbullja...@puppetlabs.com wrote:
1. Scrap webrick as base server and replace with -
mongrel/passenger/other?
Webrick sucks but it's the
On 10/4/2010 11:20 AM, Trevor Vaughan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Could you make this behavior a configurable option?
Safe by default and unsafe when explicitly told to be.
IIUIC the code does only replicate the default settings in auth. Thus
removing the extra
On 10/2/2010 1:06 AM, Luke Kanies wrote:
On Sep 17, 2010, at 1:41 AM, David Schmitt wrote:
On 9/16/2010 1:26 AM, Luke Kanies wrote:
I've updated the document with these notes and Brice's.Would you
prefer I post the whole doc here, or just rely on people checking the
original out?
http
On 10/4/2010 11:24 AM, Aurelien Degremont wrote:
Luke Kanies a écrit :
I completely agree that there should continue to be REST support. My
question is whether there's significant value to keeping REST as the
primary communication mechanism, and if so, what is it?
I totally agree with Jeff
Hi Igal,
I've tried to apply this patch on 1.0.3 and replaced the else with
simply returning -1. and it didn't do too much good.
I've also attached the mysql profiling for Nan, but it seems to be
partially a problem of our quite heavily loaded server as the query times
are 2s and 0.8s.
Thanks
On 03.10.2010 05:09, Spenser wrote:
I have been working on getting the puppet-virt module located at
http://github.com/carlasouza/puppet-virt to work. I debugged two
small issues but have been stumped by this larger one. My code with
the small changes are at
On 10/6/2010 6:54 PM, Nan Liu wrote:
On Wed, Oct 6, 2010 at 8:43 AM, David Schmittda...@dasz.at wrote:
On 03.10.2010 05:09, Spenser wrote:
I have been working on getting the puppet-virt module located at
http://github.com/carlasouza/puppet-virt to work. I debugged two
small issues but have
On Tue, 12 Oct 2010 15:51:29 -0700, Paul Berry p...@puppetlabs.com
wrote:
On Tue, Oct 12, 2010 at 3:41 PM, Luke Kanies l...@puppetlabs.com
wrote:
On Oct 12, 2010, at 2:22 PM, Nigel Kersten wrote:
On Tue, Oct 12, 2010 at 2:17 PM, Markus Roberts
mar...@puppetlabs.com
wrote:
Hmm, the
Hi Nan, people!
On Tue, 12 Oct 2010 11:31:07 -0700, Nan Liu n...@puppetlabs.com wrote:
On Fri, Oct 8, 2010 at 12:27 AM, David Schmitt da...@dasz.at wrote:
Yes, it's the http://github.com/DavidS/puppet-mysql/ module. I
overlooked
that Spenser wrote about ralsh. I'm seeing that message also
On 10/15/2010 12:17 AM, Luke Kanies wrote:
On Oct 14, 2010, at 2:08 PM, Markus Roberts wrote:
I went back and re-read the thread about autoloading
(http://groups.google.com/group/puppet-dev/browse_thread/thread/2228455628cf083c/7aa89c325721fe08),
and my understanding of the
On 10/25/2010 2:28 AM, Nigel Kersten wrote:
I concur. I made the mistake of using booleans early on, and it would
have been useful to have this made obvious before I dug a larger hole
for myself.
+1.
Best Regards, David
--
dasz.at OG Tel: +43 (0)664 2602670 Web:
On Fri, 29 Oct 2010 14:01:24 -0700, Jacob Helwig ja...@puppetlabs.com
wrote:
On Fri, 29 Oct 2010 20:40:48 +0200, Brice Figureau wrote:
I suppose once the iteration is done and patches merged in next,
raising
a red flag on some changes will be too late, is that right (at least
for
this
On 11/2/2010 3:54 PM, Markus Roberts wrote:
I suppose once the iteration is done and patches merged
in next, raising a red flag on some changes will be too
late, is that right (at least for this iteration)?
The patches are being merged into next before the end of
On 11/18/2010 11:13 AM, donavanm wrote:
@@ -80,11 +103,11 @@ Facter.add(virtual) do
end
Facter.add(is_virtual) do
-confine :kernel = %w{Linux FreeBSD OpenBSD SunOS HP-UX}
+confine :kernel = %w{Linux FreeBSD OpenBSD SunOS HP-UX Darwin}
setcode do
case
On 1/3/2011 10:32 PM, Brice Figureau wrote:
Hi,
This is my Christmas Gift for the community :)
That's something that was haunting me for a long time: a way to manage
switch/routers directly from puppet.
Unfortunately most of the switches/routers don't run ruby natively and
as such can't run
On 26.01.2011 03:17, Nick Fagerlund wrote:
Yeah, so that's a thing where the HTML is low-level enough to be
annoying. Markdown (and whatever parser we're using) is smart enough
to handle it, though, so if you use a native Markdown code block
(indent all continuous lines four spaces or a hardtab,
Hi Trevor,
Debian uses the tilde (~) for this:
1.2~alpha 1.2~beta 1.2~rc 1.2
See the Debian Policy[1] for all gory details, specifically Footnote#34
Best Regards, David
[1]http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version
On 28.01.2011 13:29, Trevor Vaughan
On Mon, 31 Jan 2011 00:19:11 -0800, Luke Kanies l...@puppetlabs.com
wrote:
Hi all,
I think there are a few classes or subsystems in Puppet that could, and
maybe should, be extracted into separate projects so they can be more
widely used; at worst, they could at least be shared by our other
On 31.01.2011 20:11, Daniel Pittman wrote:
On Mon, Jan 31, 2011 at 10:50, Thomas Bellmanbell...@nsc.liu.se wrote:
James Turnbull wrote:
According to
http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap03.html#tag_03_266:
Multiple successive slashes are considered to be the same
On 02.02.2011 09:37, donavan wrote:
On a related note is there a similar discussion about 'vendor'ing
puppet modules? I see sites needing to extend/override classes for
local requirements, like $operatingsystem support.
rantThat's because people are still entrenched in the bunker mind set
On 04.02.2011 06:59, Nick Lewis wrote:
$name can now be used to set default values in defined resource types
Feature #5061: should be able to access ($name, $module_name, $title)
from within defined resources type parameter list
The $name variable is now resolved within the scope of the
1 - 100 of 247 matches
Mail list logo
