On 6/8/2010 1:42 PM, Leigh Stoller wrote:
As for "localizing" the admin mfs, I followed the instructions to generate a set of client ssh keys, installed them in /etc/ssh of the admin mfs image (ran prepare), and kept them around for use in other OS images later. Is that what you are referring to?Yes, but ...It occurs to me that the machine I rebooted from the command line had already booted the admin mfs, but the newly discovered/created node I'm operating on via the web is still running the freebsd.newnode mfs (until it reboots, of course). I don't think I put any keys into the freebsd.newnode image. Was I supposed to?No, the newnode MFS is special. When the node is in that, you cannot reboot from the web interface.
I'm confused. When, at the end of the node creation process the web interface says "rebooting node w.x.y.z" is it trying to run "wap newnode_reboot w.x.y.z"? Or is it just lying and, for this one special case, you've got to go physically reboot the machine to get it to boot the admin mfs for the first time?
There *is* a special command line utility: boss> wap newnode_reboot 111.222.333.444 Yes, it takes an IP address only.
For what it's worth I tried a "wap newnode_reboot w.x.y.z" for a node in freebsd.newnode whose address was w.x.y.z and it didn't reboot. Is that a problem and, if so, is it worth debugging?
Since "wap node_reboot pcX" appears to work once we've made it to the admin mfs I'm guessing that one manual reboot wouldn't be a big issue, but I want to make sure I don't have some latent config problem hiding in there.