oarnodesetting(1)

💅 oarnodesetting — the OAR commands glow-up ✨

okay bestie, welcome to oarnodesetting(1), straight out of the OAR commands collection. this is the tool that lets you ✨change stuff✨ about the resources in your OAR cluster — their state, their properties, all of it. no cap, it's giving main character energy for cluster admin. 🎀

---

🌸 NAME 🌸

oarnodesetting — change the state and properties of resources in OAR. periodt.

---

✨ SYNOPSIS ✨

oarnodesetting -a -h hostname [-p "property=value" [-p ...]]

oarnodesetting -h hostname [-s state] [-p "property=value" [-p ...]] [-m
on | off]] [-d on | off]

oarnodesetting -r resource_id [-s state] [-p "property=value" [-p ...]]
[-m on | off]] [-d on | off]

oarnodesetting --sql "SQL where clause"  [-s state] [-p "property=value"
[-p ...] [-m on | off]] [-d on | off]

like, you pick how you wanna target your resources (by hostname, by resource id, or by a whole SQL where clause), and then you tell it what to change. iconic behaviour honestly. 🦋

---

💖 DESCRIPTION 💖

so basically, this command is used to change the state and properties of resources in OAR. that's the whole vibe. you point it at some resources, you tell it what you want them to be, and it makes it happen. chef's kiss. 👑

---

🎀 OPTIONS 🎀

• -r, --resource [resource id] — the resource id of the resource you wanna modify. that's the one, bestie. 🎯
• -h, --hostname [hostname] — the hostname for the resources you wanna modify. name the node, change the node. simple as. 🖥️
• --sql [SQL] — pick which resources to modify straight from the database using a SQL where clause on the resource table. example they give: "type = 'default'". very demure, very database. 🗄️
• -f, --file [file] — grab a hostname list out of a file (one hostname per line) for the resources you wanna modify. bulk mode unlocked. 📄
• -a, --add — add a new resource. new resource just dropped. ✨
• -s, --state STATE — set the new state of the resource. the possible states are: Alive, Absent, Dead and Suspected. choose wisely bestie, these are literally the four states. 🚦
• -m, --maintenance [on|off] — set or unset maintenance mode for resources. heads up: this is equivalent to setting its state to Absent and its available_upto to 0. so it's a two-for-one situation, iykyk. 🔧
• -d, --drain [on|off] — prevent new jobs from being scheduled on the resources. this is equivalent to setting the drain property to YES. no new jobs allowed, we're booked. 🚫
• -p, --property ["property=value"] — set the property of resources to the given value. give it a value, it holds the value. 💾
• -p, --property [property!] — unset the property of resources. yes it's the same flag, no that's not a typo, the exclamation mark is doing the work here. bye property! 👋
• -n, --nowait — do not wait for job ends when resources switch to Absent or Dead. impatient? valid. no waiting around here. ⏩
• --last-property-value [property] — get the last value used for a property, as sorted by SQL's ORDER BY DESC. for when you forgot what you set it to last time. we've all been there. 🙈

---

🌈 EXAMPLES 🌈

here's the little showcase, all exact, all cute:

oarnodesetting -s Alive -h node012
oarnodesetting -s Absent -r 21
oarnodesetting -p mem=512 -h node012
oarnodesetting -p "cpu_model=Xeon Gold 5120" -h node012
oarnodesetting -p gpu! --sql "gpucount = 0"

look at that range. bringing a node back to Alive, making one Absent by id, setting mem to 512, setting a whole cpu_model to Xeon Gold 5120 (fancy 💅), and unsetting gpu on everything where gpucount = 0. versatility? ate. 🔥

---

👑 COPYRIGHTS 👑

Copyright 2003-2021 Laboratoire d'Informatique de Grenoble (<http://www.liglab.fr>). This software is licensed under the GNU General Public License Version 2 or above.

there is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. fr fr, no warranty bestie, we said what we said. 😭

---

and that's the whole page! this was oarnodesetting from the oarnodesetting manual, dated 2023-07-10. go forth and set some nodes, you've got this. 🫶💜