[WiP] Computer Virtualization - Use Cases - Architecturally Significant Requirements

This page aims to structure the most relevant use cases for computer virtualization, for supporting architectural assessment on a solution to make the user work more efficient, from the economic, scalability and secure perspectives.

Use cases

HPC, Mod&Sim

1. Users need to send data from their machines (GPU card accelerated, Windows OS) to remote HPC cluster storage to feed application for simulation
   1. Architectural concerns: 
      1. Where are these users located?
      2. What BU?
      3. What data volume?
      4. Mod&Sim Method/Application: Mechanical (Abacus)
      5. Is that export control data?
2. Users needs the client application (GPU card accelerated for visualization, Windows OS) connecting with its the server side in HPC to feed application for calculation/simulation
   1. Architectural concerns: 
      1. Where are these users located?
      2. What BU?
      3. What data volume?
      4. Mod&Sim Method/Application: Plastic Injection (Modflow)
      5. Is that export control data?
      6. Vendor solutions licensing match cloud constraints?
   2. PoC steps
      1. Setup a Windows 10 OS (Europe), Machine (see inventory GPU workstation, as baseline)
         1. GPU available/ready to use
         2. CPU/Memory capacity
         3. 30GB disk minimum
         4. Network inbound/outbound traffic 
      2. Install application (Which[Modflow]?): Speak with Pierre Gaige
         1. Data provided by Alban Nourry
         2. Application can be downloaded from vendor´s site 
      3. To make test only visualization, does not need to connect with HPC 
      4. Should be in Syensqo network (MegaPort?, ZScaler, ____): Speak with Scott O´Neil
      5. NDA with Microsoft for handling Syensqo resources: Speak with Scott O´Neil
      6. Account/Subscription to run the PoC: Speak with Scott O´Neil/Microsoft
      7. Connect with License Server (AWS); License File local workstation
      8. Have the final user available for the PoC
      9. Application/Infrastructure(Network) Diagram
         1. User (Syensqo Network, Europe) → Virtual PC (Azure, Europe)
         2. Virtual PC (Azure) → [Syensqo Network] → License Server (AWS)
            1. *Modflow (USA) → License Server (Public Internet)
            2. *Modflow (USA) → HPC (Azure: Pined node)
         3. Virtual PC (Azure) → HPC (Azure?, ___)

LabPC

1. Users in LabPC need to load in a vendor application a large file or large set of files leveraging only analytics capabilities, with no need to connect with instrument
   1. Architectural concerns:

Engineering

1. Users needs powerful computers to operate CAD applications, potentially accelerated with GPU cards
   1. Architectural concerns:

Architecturally Significant Requirements

[ WiP ]