, one for each HA service, and then
take it from there. I've found it pretty straightforward to write
custom facts, not hugely more complicated than whatever the underlying
process is to get the data.
--
* Matt McLeod | People can do the work,
* m...@boggle.org | so machines
e the class in the same file in the manifest, but
now that the schedule is defined *in* the class the ordering is working
out OK.
But I'll need to let it run for longer before I'm prepared to say
it's definitely OK.
Matt
Matt McLeod wrote:
>
> Luke Kanies wrote:
> >
o you the define the schedule inside a class or a node definition?
>
> cheers,
> Ohad
>
> On Tue, Feb 17, 2009 at 12:51 PM, Matt McLeod wrote:
>
> >
> > Luke Kanies wrote:
> > > I've not seen this before, and I just verified that finding a schedule
> &
ack with more info tomorrow once it's been running for
24 hours with the simplified test case.
Matt
--
* Matt McLeod | mail: m...@boggle.org | blog: http://abortrephrase.com/ *
--- People can do the work, so machines have time to think ---
--~--~-~--~~~---~--~~
Yo
this point,
is anyone other than me even reading this?
Matt
Matt McLeod wrote:
>
> This one was my own fault for not noticing the patched source
> tarballs. Switched to Ruby 1.8.7-p72 and this goes away.
>
> Now to see if it helps with the schedule problem.
>
> Matt McLeod wr
This one was my own fault for not noticing the patched source
tarballs. Switched to Ruby 1.8.7-p72 and this goes away.
Now to see if it helps with the schedule problem.
Matt McLeod wrote:
>
> In an effort to figure out what might be causing the scheduling
> problem I tried doin
ginally did the Puppet
installs. I used that because the stable release broke Puppet in
some other exciting way I can no longer recall...
Matt
--
* Matt McLeod | mail: m...@boggle.org | blog: http://abortrephrase.com/ *
--- People can do the work, so machines have time to think ---
--~--~--
though it was also
happening with the node at 0.24.6 (I just upgraded that to see if it
was a version mismatch problem). Both ends are running Solaris 10 U6,
master is SPARC, node is Opteron.
Any ideas?
Matt
--
* Matt McLeod | mail: m...
; stuff
and then realised when testing for multiple-zone support (prompted
by your email) that it couldn't go in there, it has to be in my
base code for Solaris 10.
This produces "full" zones, if you want sparse ones then just
add the necessary bits. The results are LiveUpgrade-safe on
u
James Turnbull wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Matt McLeod wrote:
> > OK. So the docco is completely wrong: everything referenced in the
> > template needs to be set as a variable prior to defining the zone.
> > I'd assu
oes that make sense?
>
> Andrew
>
>
> On Tue, Jan 27, 2009 at 5:22 PM, Matt McLeod wrote:
>
> >
> > I'm following the example provided in the type reference
> > under 'zone', i.e.:
> >
> >zone{myzone:
> >
ts/nodes.pp:90 on node elided.example.com
This is with Puppet 0.24.7 on both client and server.
I've not really needed the templating before so it's possible that
there's a really obvious error in the template provided in the
type reference and I'm just not seeing it.
Mat
s an idle time followed by a rush of puppet clients
> > > hitting the puppetmaster followed by another idle time.
> > >
> > > This is probably worse when clients run a logrotate script with a client
> > > restart from a cronjob.
> > >
> > > I wou
their related entities,
> > including Investment Technology Group, Inc., (collectively referred to as
> > "ITG") and may contain information that is private, confidential or subject
> > to legal professional or other privilege. No confidentiality or privilege
> > is waived or lost by any mis-transmission of thi
14 matches
Mail list logo
