You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

For Chemistry IT staff: Documentation references regarding the Stockroom (VM) servers and their environment. 

Full context

Documentation references collected by Oliver when he and Lulu refreshed the "dev" Stockroom server environment in Oct. 2016.

  • Consisted of both the Linux (WebApp) and Windows (QuickBooks) VMs, both hosted on AS-CHM-SERV-21 Hyper-V server (running on an old Dell desktop computer).
  • They were refreshed with VMs copied from "prod" (hosted on AS-CHM-SERV-05), "VSRV-10 QB Web Linux Prod2" and "VSRV-06 QB Win", respectively.
  • As of 11/1/2016, their current VM names are "VSRV-10 QB Web Linux dev 2015" and "VSRV-06 QB Win dev 2014", respectively.

THE MOST IMPORTANT THING TO REMEMBER

The most important thing to remember is that the "dev" Windows (QuickBooks) VM must NEVER see the "prod" WebApp Linux server.

  • Otherwise the "prod" WebApp will record transactions as successfully copied over and not subsequently get those transactions to the "prod" Windows (QuickBooks) system, for billing. And that would be very, very bad.
  • And if that were not enough motivation, if the "dev" Windows (QuickBooks) had a public IP, it may mess up our QuickBooks licensing count with Intuit, compromising our "prod" Windows (QuickBooks) function.

Documentation Oliver found related to the Stockroom servers

OneNote

  • P098 Singlebrook access
  • P098 Stockroom 2015 inventory system additions

Wiki

File share

  • R:\Chem IT\Infrastructure\ChemIT Servers\
    • Relevant files appear to be "Hyper-V Server planning 8-2013" and "Synology storage setup".

SharePoint

I didn't see anything substantial in SharePoint's "Stockroom Kiosk WebApp" folder, accessible by this URL:

Question Oliver has:

Is there any other documentation on how the VM's networks are configured and/ or "dev" OS's configured, especially non-defaults? Ideally, the directions to take copies of the 2 "prod" VMs and change their configs (at the VM and/ or OS levels) so they can then be started up in "dev". I understand the network must allow the two VM OSes on the same Host to see each other. And the Linux must see CU's KFS (account check) and CU's Kerberos (CUWebAuth), And the Linux must also enable direct access (public IP or VPN only?) by Singlebrook via ssh. Related, I understand that the "dev" Hyper-V host (Windows) is accessed by Brightworks, and that's how they access the Windows (QuickBooks) VM. So no changes are needed there, if that's correct.

  • No labels