On Fri, May 20, 2011 at 08:23, Nigel Kersten wrote:
> On Fri, May 20, 2011 at 5:39 AM, Mark Stanislav
> wrote:
>>
>> In short, I'm in agreement with you. With the CA which is defaulted to 5
>> years (not at all surprising) there's no doubt that soon (maybe 2.7 is a
>> good time?) that 2048 key si
That works.
Thanks a lot@
-yushu
+-+
| Yushu Yao
| Ph:1-510-486-4690
|
| Lawrence Berkeley National Lab
| 1 Cyclotron Road
| Berkeley CA 94720 - USA
+-+
On Mon, May 23, 2011 at 4:41 PM, Nan Liu wr
What is the current issue number? The only one I could find that
mentions the same problem is this , http://projects.puppetlabs.com/issues/7203.
Would any changes to my current puppet.conf (see below) make this
problem no longer an issue? I'm not suing storeconfig, and not really
sure if I need
On Mon, May 23, 2011 at 4:01 PM, MolMorroco wrote:
> # 1. able to see confirm pluginsync = true works
> $ find /var/lib/puppet/lib/puppet/ -type f
> /var/lib/puppet/lib/puppet/type/custominstall.rb
> /var/lib/puppet/lib/puppet/provider/custominstall/custominstall.rb
>
> # 2. but I still get the fo
On Mon, May 23, 2011 at 9:30 AM, Kevin Beckford wrote:
> I shall try this inquiry again:
>
> I installed the puppet module tool version 0.3.3 locally to my laptop.
>
> I have installed ruby 1.9.2 on the laptop. Surely by now, puppet and
> facter work with ruby 1.9.2? They certainly seem to work
# 1. able to see confirm pluginsync = true works
$ find /var/lib/puppet/lib/puppet/ -type f
/var/lib/puppet/lib/puppet/type/custominstall.rb
/var/lib/puppet/lib/puppet/provider/custominstall/custominstall.rb
# 2. but I still get the following messages
$ sudo less /var/log/messags
May 23 17:45:20 d
On Mon, May 23, 2011 at 4:09 PM, Aaron Grewell wrote:
> I've got a conditional statement that isn't working the way I expect. I've
> created a define() for building network interfaces, but two of the entries
> (master & slave) are only appropriate for bonded interfaces. I would like
> them to be
On Mon, May 23, 2011 at 3:51 PM, Aaron Grewell wrote:
> I'm having a problem with variable interpolation that I haven't found a good
> solution to. I want to use a variable as part of the name of a fact, but
> the interpolation doesn't work as expected. I've allowed for passing the
> mac address
On Mon, May 23, 2011 at 4:21 PM, Yushu Yao wrote:
> One Follow up question:
>
> how do I apply the compiled catalog on the client?
>
> The yaml I get from puppet master --compile is like:
> cat mytest.yaml
> {
> "data": {
> "edges": [
> {
> "target": "Class[main]",
> "s
One Follow up question:
how do I apply the compiled catalog on the client?
The yaml I get from puppet master --compile is like:
cat mytest.yaml
{
"data": {
"edges": [
{
"target": "Class[main]",
"source": "Stage[main]"
...
}
If I do on the client: puppet apply --t
I've got a conditional statement that isn't working the way I expect. I've
created a define() for building network interfaces, but two of the entries
(master & slave) are only appropriate for bonded interfaces. I would like
them to be completely excluded from regular interfaces. This seems easy
On Mon, Apr 4, 2011 at 12:13 PM, Marcus Downing
wrote:
> As I said, the "sourceselect => all" parameter is necessary to make puppet
> merge the listed sources rather than selecting one of them.
> I take your point that variables are a fragile way of specifying. I'll try
> refactoring it based on c
I'm having a problem with variable interpolation that I haven't found a good
solution to. I want to use a variable as part of the name of a fact, but
the interpolation doesn't work as expected. I've allowed for passing the
mac address into my define() but if it's not provided I want to look it up
On Mon, May 23, 2011 at 9:34 AM, Chip wrote:
> I have pre, main, and post stages configured in my manifests.
>
> When I assign variables in the node declaration they are present in
> the main stage, but not my pre-stage.
>
> How do I assign variables at the node level that can be referenced in
> m
On Mon, May 23, 2011 at 2:06 PM, hyzhang wrote:
> Hi,
>
> I wrote a custom facter called active_interface and put in /etc/puppet/
> modules/networking/lib/facter directory.
> Then I did "export RUBYLIB=/etc/puppet/modules/networking/lib" on
> puppet master.
>
> On puppet master, it works.
> facter
Hi,
I wrote a custom facter called active_interface and put in /etc/puppet/
modules/networking/lib/facter directory.
Then I did "export RUBYLIB=/etc/puppet/modules/networking/lib" on
puppet master.
On puppet master, it works.
facter active_interface
eth0
But on client, it did not even seem to tr
On 07/28/2010 02:58 AM, David Schmitt wrote:
On 7/28/2010 12:41 AM, Christopher Johnston wrote:
David,
Curious on how you handle doing a grant of *.* (all attributes) I looked
through your puppet type and I see you are individually listing every
type out but you are missing event_priv and trigg
On 05/23/2011 12:34 PM, Chip wrote:
I have pre, main, and post stages configured in my manifests.
When I assign variables in the node declaration they are present in
the main stage, but not my pre-stage.
How do I assign variables at the node level that can be referenced in
my pre stage?
-Chip
On 05/20/2011 11:31 AM, Mark wrote:
We are looking to hire a full time (or possibly a consultant) in
Boston with experience in AWS and Puppet (or Chef :)
http://www.fiksu.com/company/careers/cloud-operations-manager
Any good leads on other places to look for someone like that?
Thanks!
Altho
On Mon, May 23, 2011 at 9:30 AM, Kevin Beckford wrote:
> I shall try this inquiry again:
> I installed the puppet module tool version 0.3.3 locally to my laptop.
> I have installed ruby 1.9.2 on the laptop. Surely by now, puppet and facter
> work with ruby 1.9.2? They certainly seem to work well
I shall try this inquiry again:
I installed the puppet module tool version 0.3.3 locally to my laptop.
I have installed ruby 1.9.2 on the laptop. Surely by now, puppet and facter
work with ruby 1.9.2? They certainly seem to work well.
I have installed ruby using macports, and am using the +no
I have pre, main, and post stages configured in my manifests.
When I assign variables in the node declaration they are present in
the main stage, but not my pre-stage.
How do I assign variables at the node level that can be referenced in
my pre stage?
-Chip Schweiss
--
You received this messag
On Mon, May 23, 2011 at 10:08 AM, Aaron Grewell wrote:
> You'll have to copy the entire contents of /usr into the Puppet tree to do
> this, you can't serve it in place. I wouldn't do what you're doing anyway.
> Puppet is great for serving config files but for serving all of /usr I'd
> choose eith
On Sun, May 22, 2011 at 7:48 AM, Mark wrote:
> Great, thanks for the pointer. I saw the consulting page and we will
> give you a call about that. We definitely would prefer a full-time
> person, but we are looking at all of the options..
>
You might have more luck asking on Twitter using the #
On Sun, May 22, 2011 at 11:06 PM, Matthew Macdonald-Wallace <
li...@truthisfreedom.org.uk> wrote:
> Hi all,
>
> I've got modules for NGINX and PHP-FPM which are working fine, the issue
> I'm running into is that quite often NGinx will start before php-fpm is
> even installed.
>
> I'm wondering if
On 04/21/2011 03:21 PM, Glenn Buckholz wrote:
I was wondering if anyone has, or is aware of puppet dashboard
integration with secstate (https://fedorahosted.org/secstate/) .
A use case would be, I run a compliance report in secstate, it shows
up on the puppet dashboard and allows me to see where
You'll have to copy the entire contents of /usr into the Puppet tree to do
this, you can't serve it in place. I wouldn't do what you're doing anyway.
Puppet is great for serving config files but for serving all of /usr I'd
choose either NFS or rsync and call your sync script from Puppet.
On May 23
On May 20, 10:20 am, Carles Amigó wrote:
> Hi,
>
> I'm trying to pass a parameter different from the default to the child
> of a parametrized class with inheritance,
I would not recommend mixing class inheritance with parameterized
classes.
As a separate matter, I would recommend to most peop
On May 21, 2:11 am, Patrick Mohr wrote:
> On Fri, May 20, 2011 at 3:15 PM, jcbollinger wrote:
>
> > On May 20, 3:17 pm, Randall Hansen wrote:
> > >http://projects.puppetlabs.com/issues/7600
>
> > > I call this the "agent orange" option :)
>
> > > This works, purging all unmanaged hosts entries:
Hi,
Now i am getting error like:
err: /Stage[main]//File[/usr/local/sbin]: Failed to generate additional
resources using 'eval_generate': Error 400 on SERVER: Not authorized to call
search on /file_metadata/usr/local/sbin with {:recurse=>true,
:links=>"manage", :checksum_type=>"md5"}
On Mon, Ma
Hi,
You've got it a bit wrong.
Here is what I think you're trying to do:
http://docs.puppetlabs.com/guides/techniques.html#how-can-i-manage-whole-directories-of-files-without-explicitly-listing-the-files
I think if you're starting out, you should try something simpler and less
likely to destroy
I too am in the Metro Detroit area and would be interested.
- Brad
>
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose it
Try looking into the recurse => true parameter.
--
Nathan Clemons
http://www.livemocha.com
The worlds largest online language learning community
On Mon, May 23, 2011 at 3:05 AM, Sumith Sudhakaran wrote:
> HI
>
> How can i copy a directory from puppet master to client
>
> I have tried this, but
HI
How can i copy a directory from puppet master to client
I have tried this, but its giving error. I am using redhat 5.6 and puppet
2.6.8
file { "/usr":
ensure => "directory",
owner => "root",
group => "root",
mode => 777,
content => template("/usr/local/sbin/),
Please help me..
--
* Regards
Hi,
Bit hard to make any real comment on the blog because we don't have a copy of
the manifest (or test case), the version that exhibits the behavior or a log to
show what is occurring. Nor has he(or she) filed a bug report to my knowledge.
If I experienced that sort of behaviour that's what I
Nigel Kersten:
> On Sat, May 21, 2011 at 1:42 AM, Brice Figureau <
> brice-pup...@daysofwonder.com> wrote:
> > If you really want to simplify people's life, make those extra
> > attributes become metaparameters (but please keep the old syntax):
> >
> > user { luke: ensure => present, virtual => [bo
Nan Liu:
> On this subject, should we support regular expression?
> User <| title =~ /*adm/ |>
If you're going down this road, it's probably worthwhile to add the full
set of comparison operators such as <= and so forth.
--
"There should be a homonym exam before people are
issued keyboards."
Jordan Sissel:
> +1 to this. Any change here should also updae the export syntax as well.
>
> replace @@user { foo: ; }
> with export user { foo: ; }
Agreed!
> Any plans on making the realizing/importing queries changed as well?
>
> realize/query: User <| title == "foo" |>
> export query: User
38 matches
Mail list logo
