...
A suite of 5 machines could perform the current OpSim functions - two existing machines (ops1 & ops2) one new machine to be acquired (ops3), and two virtual machines to be set up on existing machines.
- development for Simulations (TBD)
- production for Simulations (ops1 & ops2)
- would not need MAF installed or maintained as only Simulator codebase would be maintained
- this solves the problem of different python requirements for the Simulator and MAF
- only run simulations on these machine (as usual, run from /lsst/opsim with all output in this dir, not /home/*)
- development for MAF (VM my laptop or VM on ops3, a new machine)
- 8Gb VM on my laptop
- can use VPN to access ops1 & ops2
- can run MAF on ops1/ops2 DBs over VPN or local sqlite files to test code
- production for MAF (ops3, a new machine)
- run production MAF on ops3 -> update new code and run or rerun MAF on ops1 or ops2 to create output files
- move output files to ops4 (a VM)
- distribution (ops4 or opsdist - VM on DMZ machine)
- LSST/NOAO DMZ machine is to come on line imminently
- copy output files from within NOAO (MAF production machine ops3)
- run showMAF.py on an accessible port (8080?)
- specify runs for science community in one trackingDB
- specify runs for OpSim use (most of them) in another trackingDB
...