AutoManager → Manager: change a node’s tags. tags is merged onto the
node’s metadata — a key given here replaces its value, keys not given
are untouched — pushed to the provider (an EC2 node’s instance tags) and
announced as a node_tags_updated event. Persisted by the daemon, so a
Manager restart that rediscovers the node from the provider re-applies
the edit; this is what lets a runtime hot-spare spec edit (warmFor,
reservedFor, exclusive — task 90 fix-list 46) outlive a norsk-mgr
restart instead of reverting to the provision-time tags.
The spare tag is the daemon’s own (dropped when the node is given a
job). On an ELASTIC node it is refused (FAILED_PRECONDITION): those
spares are the AutoManager reconciler’s to provision and count. On a
LOCAL SERVER (cluster provider) spare: "true" marks the node as a hot
spare — refused (FAILED_PRECONDITION) while it holds a job — and any
other value clears it; warmFor / reservedFor / exclusive beside it
are the spare’s spec, as on an elastic one. Audited as
node-spare-set / node-spare-cleared. |