I guess you'd need to look at the services individually, and determine what you had changed during the testing, and reverse it.
I suppose you could run the ansible playbook again. It might reinitialize some files for you. Using the "runansible" script should not destroy the function of the server. It should be able to run repeatedly. (though I saw a comment from Tim Moody yesterday that one of the services was erroring out if ansible was rerun). (I have not tested this) Of course you could reflash the XO, and start up the whole install process. But that would leave many things untested. You mention XO registration. You might try just running the server registration tag: (I have not tested this) ansible-playbook -i ansible_hosts xsce.yml --connection=local --tags="idmgr" On Sat, Feb 15, 2014 at 6:18 AM, <tkk...@nurturingasia.com> wrote: > Need to some advice in schoolserver installation, testing and actual > deployment. > > After XO registration on the school server.. and testing that all is well, > what is the best way to restore the schoolserver back to its virgin state > for the real deployment? > > Good weekend. > > --- > T.K. Kang > > > > _______________________________________________ > Server-devel mailing list > Server-devel@lists.laptop.org > http://lists.laptop.org/listinfo/server-devel >
_______________________________________________ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
