Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] How does input to ROOSTER_WAKEUP_CMD look like?
- Date: Mon, 17 Nov 2025 10:56:53 +0100
- From: Steffen Grunewald <steffen.grunewald@xxxxxxxxxx>
- Subject: Re: [HTCondor-users] How does input to ROOSTER_WAKEUP_CMD look like?
Hi Zach (and Todd - I heard you) -
On Fri, 2025-11-14 at 16:59:53 +0000, Zach McGrew wrote:
> Hey Steffen,
>
> The ClassAd is the same as what you would see from doing condor_status -long slotX@myhost > myclassad.txt
Thanks - I would have expected - since the ClassAd comes from a special place,
and described a machine in a special state - that to be different.
But it's too early to listen to the rooster crowing - I've got to put some
machines to sleep first.
> printf "MyAddress = \"<${the_ip}:9618>\"\nHardwareAddress = \"${hwaddr}\"\nSubnetMask = \"${subnet}\"\n" | condor_power -i
I couldn't get "wakeonlan" to power up a switched-off machine, thus I'd be
surprised if "condor_power" could do it (but I'm in for any susprise).
> You could probably use the htcondor2 Python bindings to parse the ClassAd, and one of the Python IPMI libraries to wrap this whole thing up into a nice replacement.
Probably I'll do - when I got the other things sorted. And maybe I'll come
up with an addition to the docs (although I'm missing other details, in
other places, more)
Thanks,
Steffen