Install seems automatable, but the files in setup/automation are missing MAINIP

[deargle]

I was tinkering with trying to automate my net install by providing a config file as was possible with SO 16. I found the answer files in setup/automation -- TESTING=true at the top seems to suggest that they are for automation, but regardless, they seemed to maybe be exhaustive for automating a build. I was copying the one I wanted (import-net-centos) into /root/install_opt, after I saw that so-setup looked in there for a file to load options for. Got stuck for a good while until just now I think I've narrowed it down to MAINIP never gets set if /root/install_opt exists, so things start to timeout on connectivity attempts when salt is trying to assert that the minion can reach the master (it can't, because it doesn't have a MAINIP, I think). And probably pillar will break too and lots of other things.

Sorry for the rambling, it's late at night so my thoughts are clouded, but idk, and I haven't tested that MAINIP is the only thing missing because in premature resignation I nuked my gcp nested virt testing instance for the night and I don't want to launch it again, but maybe a page on the docs saying "advanced: you can automate a build by starting from the setup/automation scripts, and also adding a MAINIP in there".

Oh and the docs page for the analyst vm script doesn't mention that it only works on centos -- not ubuntu! No biggie in vagrant world though, but that was a surprise.

Securityonion 2 looks slick btw, high five