Visible to Intel only — GUID: hkl1522372958199
Ixiasoft
Visible to Intel only — GUID: hkl1522372958199
Ixiasoft
A.1.1.1. Specifying DSE II Computing Resources
If you have a laptop or standard computer, you can use the single compilation feature to compile your design on a workstation with higher computing performance and memory capacity.
Alternatively, you can distribute the DSE II iterative compilation workload across different computing resources via one of the following supported remote hosts methods:
- Kubernetes (Beta)—run DSE II in a managed Kubernetes cluster running outside of your network such as on Microsoft Azure* or in a cluster on premise.
- LSF—run DSE II in a Load Sharing Facility (LSF) remote farm. The LSF manages, monitors, and analyzes workloads and networks different computers into a single system.
- PBSPro—run DSE II in the Altair PBS Professional* (PBSPro) workload manager and scheduler.
- Slurm—run DSE II in the free and open-source Slurm job scheduler for Linux and Unix-like kernels.
- SSH—run DSE II in Secure Shell (SSH) that allows secure communication between multiple computers and allows access and management of networked systems.
- SunGrid (Beta)—run DSE II in Sun Grid Engine (SGE) job scheduling system that manages and distributes computational workloads across a cluster of computers.
- Torque—run DSE II in the Adaptive Computing TORQUE job scheduling system that manages and distributes computational workloads across a cluster of computers.
When running on a compute farm, you can direct DSE II to safely exit after submitting all the jobs while the compilations continue to run until completion. Optionally, you can receive an e-mail when the compilations are complete.
If you launch jobs using SSH, the remote host must enable public and private key authentication. For private keys encrypted with a pass phrase, the remote host must run the ssh key agent to decrypt the private key, so the quartus_dse executable can access the key.