Ideas to provision dual-OS, with one OS not supported by ChemIT. |
Run Linux OS which John is familiar with. And do so directly on the hardware to optimize performance.
Unknown: Performance hit of running Debian as a guest of a Windows host machine.
Systems with OSes not supported by ChemIT run on Cornell's RedRover (wireless).
Only list likely candidates, not all possible options.
Recommendations/ |
|
Boot 1 |
Boot 2 |
Host |
Guest |
Network: |
Notes |
---|---|---|---|---|---|---|---|
|
Option 1 |
Windows |
Debian |
N/A |
N/A |
GreenNet |
Easiest to set up. |
|
Option 2 |
Windows |
Debian, but only run as a boot OS when h/w performance needed. |
Windows |
Debian, from Boot 2 partition. Run Debian this way, unless need h/w performance. |
ChemIT: FreedNet, if Windows is indeed usually running. |
Doable? Cost-effective, time-wise? |
|
Option 3 |
Windows |
Debian |
N/A |
N/A |
ChemIT: FreedNet |
Easiest to set up. |
|
Option |
Windows |
Debian |
N/A |
N/A |
ChemIT: Public IP |
Easiest to set up. |
John responsible for dual-boot capabilities. Can pull all networking info from Windows OS's configuration.
Windows cannot get patched unless it is running.
Mimics network as provisioned by a home-based ISP (non-static IP, very limited ACLs, etc.).
Instead of an ISP, the researcher's relationship is directly with CIT.
Requires a VPN (to re-log-in after 8 hours, if necessary) to access Eldor server.
No VPN required to print or access CIT SFS file shares.
In general, these networks are reserved for systems managed by ChemIT.
The Freed research network has strong protections, by both a router and ACLs.
Systems in the ChemIT network are more vulnerable to each other than from outside-the-network systems.