maas-devel team mailing list archive
-
maas-devel team
-
Mailing list archive
-
Message #01973
Re: RFC: "Serialising" power actions
-
To:
Maas Devel <maas-devel@xxxxxxxxxxxxxxxxxxx>
-
From:
Mark Shuttleworth <mark@xxxxxxxxxx>
-
Date:
Tue, 23 Sep 2014 10:43:01 +0100
-
In-reply-to:
<20140915222619.GE31777@smitten>
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
In response to this thread:
* dropping and interpolating are both fraught with problems
Therefor:
* please implement a queue
* please ensure that there is an externally imposed timeout on every
action (so the queue never gets fully blocked even if one gets stuck)
* think carefully about how to handle a failure - does that invalidate
the node, or do we initiate an attempt to reset the BMC and re-establish
control
* provide feedback on the queue on commands, e.g.
$ maas power-off node1
Queue of power actions on node1:
* reboot (for admin) in progress
* reboot (for admin)
* pxe-boot (for fred)
then will power-off for you.
$ maas power-off node2
Powering off node2 for you now.
While that may seem pedantic, it's most understandable to the user
because they don't have to know what MAAS is doing or why; MAAS is just
doing what it has been told, and they can talk to the user in question
if it's been told something silly.
Mark
Attachment:
signature.asc
Description: OpenPGP digital signature
References