I am using CentOS 6.6 x86_64
uname -a
Linux puppet.xor.in 2.6.32-504.1.3.el6.x86_64 #1 SMP Tue Nov 11 17:57:25
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
On Thursday, 18 December 2014 13:16:44 UTC+5:30, Varun Utagikar wrote:
>
> Hello All
>
> I could successfully declare and realize virtual users i
I solve this problem. Thank you.
By one pass the next task solved:
1) creating-change groups
2) creating-change users
3) remove users
4) remove groups
Groups and Users list are virtual in class.
The construction must be next:
if $fqdn =~ /ru-msk-tes-front.russia.test/ {
Group <| title == '
On Friday, February 15, 2013 12:35:59 AM UTC-6, Vlados Vlados wrote:
>
> Please help.
> I using virtual resource @user and @group.
>
> If i using next construction i get error with cycles
> class users {
> Group <| ENABLED_GROUPS |> ->User <| ENABLED_USERS' |> -> User
> <| DISABLED_USE
On Apr 18, 7:09 am, Robert Rothenberg wrote:
> I should add that I am using a masterless puppet environment, so a global
> list of all nodes is not available.
As far as I am aware, there is no solution available entirely Puppet
that would work in masterless mode.
> Some Googling suggested th
I should add that I am using a masterless puppet environment, so a global
list of all nodes is not available.
Some Googling suggested the use of multiple files that are concatenated,
but I think that's a messy kluge, and would like to avoid doing that.
On Wednesday, April 18, 2012 12:38:08 PM U
Hi,
[...]
> I have worked around this by passing in a $minute argument, but this
> seems a bit inelegant -- the slave certainly has no business
> determining the backup schedule. Other than a feature request for
> fqdn_rand to allow a value to be passed in, any ideas on a more
> elegant way to
(apologies for the derail)
On 09-Jun-11, at 7:51 PM, jcbollinger wrote:
[snip]
On Jun 9, 1:33 am, Sirtaj Singh Kang wrote:
On 08-Jun-11, at 9:31 PM, Brian Gallew wrote:
[snip]
See, there's the crux of the issue: arrays are *not* a method of
looping. Puppet's DSL is declarative, not procedur
Part of the challenge is that I haven't seen a generally accepted language
that succinctly describes what arrays do. If I had it to say again I would
have said arrays are Puppet's only available declarative multiplier.
On Thu, Jun 9, 2011 at 7:21 AM, jcbollinger wrote:
>
>
> On Jun 9, 1:33 am, S
On Jun 9, 1:33 am, Sirtaj Singh Kang wrote:
> On 08-Jun-11, at 9:31 PM, Brian Gallew wrote:
> [snip]
>
>
>
> > See, there's the crux of the issue: arrays are *not* a method of
> > looping. Puppet's DSL is declarative, not procedural (imperative).
>
> This isn't precisely true - every pure fun
On 08-Jun-11, at 9:31 PM, Brian Gallew wrote:
[snip]
See, there's the crux of the issue: arrays are *not* a method of
looping. Puppet's DSL is declarative, not procedural (imperative).
This isn't precisely true - every pure functional language I've seen
has some sort of list map and filt
Nice! More good things to look forward to. :)
On Wed, Jun 8, 2011 at 1:58 PM, Nigel Kersten wrote:
>
>
> On Wed, Jun 8, 2011 at 1:36 PM, Aaron Grewell wrote:
>
>> We've looked at two different possibilities thus far:
>>
>> 1) Make all resource types hash-aware. This is what I was originally
>
On Wed, Jun 8, 2011 at 1:36 PM, Aaron Grewell wrote:
> We've looked at two different possibilities thus far:
>
> 1) Make all resource types hash-aware. This is what I was originally
> asking for. It would mean changing the way resources are declared so that
> in the case of a hash their represen
We've looked at two different possibilities thus far:
1) Make all resource types hash-aware. This is what I was originally asking
for. It would mean changing the way resources are declared so that in the
case of a hash their representation of $name was appropriate for use with
defines and virtua
On Wed, Jun 8, 2011 at 12:07 PM, Aaron Grewell wrote:
> All I'm saying is that I think hashes should be first-class citizens in
> Puppet and right now they're not.
I agree with that as a high-level problem statement, but to make
progress we need to put legs on it. John's got one possibility: a
All I'm saying is that I think hashes should be first-class citizens in
Puppet and right now they're not. Every other object can be placed in an
array and easily and scalably declared. Hashes are "special" because you
can declare them like anything else, but you can't use them like anything
else.
On Jun 8, 12:17 pm, Randall Hansen wrote:
> On Tue, Jun 7, 2011 at 4:15 PM, Aaron Grewell wrote:
> > $users = [{ username => "bill", uid => "12345" },
> > { username => "ted", uid => "12346" }]
>
> Aaron, I think this is a completely sane request. We've talked about
> it before, but
On Jun 8, 11:33 am, Aaron Grewell wrote:
> If you look at what I tried to do you'll realize that's not the case. I
> understand what you're saying, but the issue is one of Puppet not supporting
> its own 'syntactic sugar' consistently. I created an array (this is not a
> convenience for a larg
I suspect the root of the problem I'm running into may be the simple nature
of $name. It's not capable of being an arbitrary object. I consider that
an architectural issue in a system that supports hashes which are structured
objects that can't really be reduced to a string. IMHO for a future ve
If you look at what I tried to do you'll realize that's not the case. I
understand what you're saying, but the issue is one of Puppet not supporting
its own 'syntactic sugar' consistently. I created an array (this is not a
convenience for a large number of machines, it's a requirement) but since
Here's the thing though: since arrays are the only native method of looping,
Puppet needs to handle arrays of all native types well. If it doesn't, from
an end-user perspective that's broken.
On Wed, Jun 8, 2011 at 8:36 AM, jcbollinger wrote:
>
>
> On Jun 7, 6:15 pm, Aaron Grewell wrote:
> > Hm
On Jun 8, 2011, at 8:45 AM, Aaron Grewell wrote:
> Here's the thing though: since arrays are the only native method of looping,
> Puppet needs to handle arrays of all native types well. If it doesn't, from
> an end-user perspective that's broken.
See, there's the crux of the issue: arrays are
On Jun 7, 6:15 pm, Aaron Grewell wrote:
> Hmmm, either I'm doing something wrong or virtual resources are incompatible
> with hashes.
I think it's a mix of about two parts "doing something wrong" to one
part "incompatible", coming out to more or less "Puppet doesn't do
what I wish it would."
On Feb 17, 2:25 pm, Forrie wrote:
> I have another related question. What happens when a virtual resource
> such as an NFS mount is not longer needed -- how do you prune that
> from the systems that had it "realized"? Can you "unrealize" them?
First, let's get the conceptual framework right.
Thank you! That worked. I was actually following an incorrect
example whereby the definition itself was capitalized.
What really irks me here is that the error message I was getting was
irrelevant -- at least, in my opinion it needed to be more specific
with syntactical errors. There must be s
Thank you! That worked. I was actually following an incorrect
example whereby the definition itself was capitalized.
What really irks me here is that the error message I was getting was
irrelevant -- at least, in my opinion it needed to be more specific
with syntactical errors. There must be s
Heed Felix's advice. In particular, do not captialize class,
definition, or resource type names when you *declare* a resource,
including a virtual one. Do capitalize where you *realize* a virtual
resource.
Also,
On Feb 16, 5:12 pm, Forrie wrote:
> class dce {
> define nfsmount(options} {
>
On Fri, Jan 14, 2011 at 2:23 AM, luke.bigum wrote:
> Hi Adam,
>
> Shame you can't use LDAP or NIS ;) But anyway...
>
Yes it makes me sad. I'd really, really, really like to use ldap but
my hands are tied.
--snip--
>
> Lastly, what you're trying to do is complex, especially with Puppet's
> "dec
Hi Adam,
Shame you can't use LDAP or NIS ;) But anyway...
Let me give you one of my working examples of virtual resources and
hopefully it'll give you an idea on how to solve your problem. I've
got Yum repos as virtual resources. Now I don't want every Yum repo on
every server, so I've got a 'yum
On 4/14/10 3:51 AM, Ken wrote:
@file { $myarray:
ensure => directory,
tag => "myfiles"
...
}
File<| tag == "myfiles" |>
Or I think this will work also, probably close to your first
requirement:
@file { $myarray:
ensure => directory,
}
realize(File[$myarray])
Hello
Thanks Ken,
I'll give it a shot.
Regards,
-Roy
On 4/14/10 3:51 AM, Ken wrote:
@file { $myarray:
ensure => directory,
tag => "myfiles"
...
}
File<| tag == "myfiles" |>
Or I think this will work also, probably close to your first
requirement:
@file { $myarray:
ensure =>
> @file { $myarray:
> ensure => directory,
> tag => "myfiles"
> ...
>
> }
>
> File <| tag == "myfiles" |>
Or I think this will work also, probably close to your first
requirement:
@file { $myarray:
ensure => directory,
}
realize(File[$myarray])
--
You received this message because you
Not sure if this works - using the expression: var == array doesn't
really make sense when you think about it as its trying to directly
compare a string with an array (which should fail). If there was an
'in' expression it would make more sense.
Of course this is academic. Because you could just t
I think I solved this. I had the nagios_host definition within a class and
the class only got compiled once.
Joel
On Thu, Oct 22, 2009 at 11:03 AM, Joel Heenan wrote:
> OK So I'm doing something silly here, but this is the behaviour I'm seeing.
> I am instatiating a large number of virtual @nag
On Jan 23, 2009, at 4:20 AM, Marce wrote:
>
> 2008/10/6 udo waechter :
>> Ah,
>> I see an error in my reasoning here:
>> On 06.10.2008, at 20:36, udo waechter wrote:
>>>
>>> What comes to my mind now, is that I can do a hack and replace:
>>>
>>> @@file{"queue-template-${name_real}":
2009/1/24 udo waechter :
>
> Hello Marce,
> nice to see that someone else is also configuring sge with puppet.
> I do want to release our module to the public soon. Currently i can
> configure nearly all aspects of the gridengin. Unfortunately I need to
> do some cleanups and documentation before
Hello Marce,
nice to see that someone else is also configuring sge with puppet.
I do want to release our module to the public soon. Currently i can
configure nearly all aspects of the gridengin. Unfortunately I need to
do some cleanups and documentation before releasing it.
On 23.01.2009, at
2008/10/6 udo waechter :
> Ah,
> I see an error in my reasoning here:
> On 06.10.2008, at 20:36, udo waechter wrote:
>>
>> What comes to my mind now, is that I can do a hack and replace:
>>
>>@@file{"queue-template-${name_real}":
>>path =>
>> "${sge_collects
Ah,
I see an error in my reasoning here:
On 06.10.2008, at 20:36, udo waechter wrote:
What comes to my mind now, is that I can do a hack and replace:
@@file{"queue-template-${name_real}":
path => "${sge_collects}/queue.template-${name_real}",
Hi,
On 06.10.2008, at 17:35, Teyo Tyree wrote:
udo waechter wrote:
Hi,
On 03.10.2008, at 19:15, Luke Kanies wrote:
On Oct 3, 2008, at 4:37 AM, udo waechter wrote:
I would like to know how I could have many hosts export the
"same" (as in identical) resource. Is this possible?
As with non
Hey Udo,
udo waechter wrote:
> Hi,
> On 03.10.2008, at 19:15, Luke Kanies wrote:
>
>>
>> On Oct 3, 2008, at 4:37 AM, udo waechter wrote:
>
> I would like to know how I could have many hosts export the
> "same" (as in identical) resource. Is this possible?
As with non-exported
Hi,
On 03.10.2008, at 19:15, Luke Kanies wrote:
On Oct 3, 2008, at 4:37 AM, udo waechter wrote:
I would like to know how I could have many hosts export the
"same" (as in identical) resource. Is this possible?
As with non-exported resources, you can't have multiple instances of
the same reso
On Oct 3, 2008, at 4:37 AM, udo waechter wrote:
>>>
>>> I would like to know how I could have many hosts export the
>>> "same" (as in identical) resource. Is this possible?
>>
>> As with non-exported resources, you can't have multiple instances of
>> the same resource. How would it even make sens
Hello,
On 02.10.2008, at 18:22, Luke Kanies wrote:
On Oct 1, 2008, at 8:02 AM, udo waechter wrote:
Hello everybody,
I have a question regarding virtual resources and the exporting/
collection thereof.
I have several hosts that should export one and the same file
resource. This should be colle
On Oct 1, 2008, at 8:02 AM, udo waechter wrote:
> Hello everybody,
> I have a question regarding virtual resources and the exporting/
> collection thereof.
>
> I have several hosts that should export one and the same file
> resource. This should be collected exactly once by one host.
> The res
44 matches
Mail list logo
