Brian E Carpenter <[email protected]> wrote: >> > this, the Anima solution will not be complete in itself. Especially >> > during the early formation of an AN after a cold start, this is a > >> problem. >> >> Please define "cold start", here.
> Power off on all racks; humans pressing factory reset buttons. Systems
> coming back in random order. All dependencies broken.
I think that we need to define "factory reset" in a document somewhere!
Thanks to ANIMA and LDevID certificates, I think that there are two kinds of
reset, but I'd like the WG to come to consensus.
There is "reset to factory defaults", which I would take to make to erase
all configuration files and all administrative credentials, and might even
mean to boot a specific OS image. But, it wouldn't mean to remove the LDevID.
An operator would do this when redeploying the equipment from one purpose to
another.
The second kind of "factor reset", would mean to delete the LDevID.
Still, I'm skeptical that we'd ever want to do that; it might mean to boot
using the IDevID. It might really mean, specifically, to run bootstrap again
without doing anything else. This is what a machine might do if it's LDevID
certificate is expired.
So, Max, Toerless, MichaelB, what are your thoughts here?
And I agree with Brian that we need a pure ANIMA solution when we cold start
a rack of equipment.
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
