Knowledge Base Administration Guide

Simscope Quickstart Guide

Contact & Help


If you would like a walkthrough, screen share, or any help installing Simscope and the Tunnel, please contact Payton via email or phone:

Payton Quackenbush
payton@verops.com
1-512-573-1905


Quickstart Intro

This guide (sections 1.1 through 1.5) walks through setup of:

This process can take anywhere from 1 hour to an afternoon, so please make sure you have a few hours to walk through this guide.


Database Storage Requirements

Simscope manages its own database (DB) to store and query all data.

An approximation of how much size you need for Simscope is:

→ 1 kB per simulation

# For example, with 150k simulations per day, this would store approximately
> 150*1000 * 1kB → 150MB / day

Volume

The DB volume choice affects database performance:

VolumePerformance
Local diskHigh
VM Local StorageHigh/Medium
NFS (Netapp)Medium/Low

Note: if you have large volume activity (simulations), or if you have saturated network or NFS volume, Simscope is recommended to run on either Local Disk or VM Local Storage, instead of NFS.

One nice benefit of VM Local Storage is usually they can be set up to run VM snapshots, for easy backup/recovery.


Machine/OS Requirements

Simscope Server (daemon) and Tunnel server run on Linux x86-64 platforms:

MinimumRecommendedPerformance
Platformx86-64, 2-core4-core4+ cores
Physical Memory2 GB8+ GB32+ GB
Disk Space5 GB100 GB1 TB
Simulations/Day25k500k+
  • Note: the Simscope Performance profile is targeted at large workloads of 500k+ simulations per day.

Linux distributions supported:

  • CentOS 6 or higher (x86-64)
  • RHEL 6 or higher (x86-64)
  • Ubuntu (x86-64)
  • SuSE (x86-64)
  • Docker (containers)
  • Please contact VerOps if you have a different Linux x64 OS, so that it can be supported.

Diagram of Simscope, RabbitMQ, and the Tunnel

Here's a basic diagram of the workflow for Simscope. The blue boxes are related to Simscope.

Simscope