Page Comparison

...

• The Charon-SSP instance requires Internet access (via public IP address or NAT) for the license mechanism to work. If NAT is used, the gateway must be an OCI instance. At the time of writing, the license servers that must be reachable are cloud-oci1.stromasys.com and cloud-oci2.stromasys.com on port 8080. Also a DNS service must be reachable to resolve the host names of the license servers, or corresponding entries in /etc/hosts must exist.
• If you need to change the hardware characteristics of your instance, you need to create the number of host CPU cores is changed in any way, it will invalidate the license. 
• Some license problems (e.g., additional CPU cores needed) may require moving the emulator to a new instance. Therefore, it is strongly recommended to store all relevant emulator data on a separate storage block volume that can easily be detached from the old instance and attached to a new instance.
• If the number of host CPU cores is changed in any way, it will invalidate the license. 
• Should access to the license be lost, there is a grace period of 24 hours. If license access is not restored within this period, the emulator will stop (if a guest system is running at the time, this is the equivalent of disconnecting the power without clean shutdown, i.e., it may lead to loss of data).

...

By selecting a shape in OCI, you select the virtual hardware that will be used for Charon-SSP. Therefore, the selection of an instance type determines the hardware characteristics of the Charon-SSP virtual host hardware (e.g., how many CPU cores and how much memory your virtual Charon host system will have).

To facilitate a fast transfer of emulator data from one OCI instance to another, it is strongly recommended to store all relevant emulator data on a separate block volume that can easily be detached from the old instance and attached to a new instance.

General CPU requirement: Charon-SSP requires modern x86-64 architecture processors with a recommended CPU frequency of at least 3.0GHz.

The OCI non-baremetal shapes available at the time of writing offer CPU frequencies up to 2.2GHz. This limits the ability of the emulator to deliver the highest performance. Please contact Stromasys to discuss your requirements if you have any concerns.

Minimum requirements for Charon-SSP:

• Minimum number of host system CPU cores:
  • At least one CPU core for the host operating system.
  • For each emulated SPARC system:
    • One CPU core for each emulated CPU of the instance.
    • At least one additional CPU core for I/O. If server JIT optimization is used, add an additional I/O CPU for improved translation speed.
• Minimum memory requirements:
  • At least 2GB of RAM for the host operating system.
  • For each emulated SPARC system:
    • The configured memory of the emulated instance.
    • 2GB of RAM (6GB of RAM if server JIT is used) to allow for DIT optimization, emulator requirements, run-time buffers, SMP and graphics emulation.
• One or more network interfaces, depending on customer requirements.
• Charon-SSP/4U+ and Charon-SSP/4V+ must run on hardware supporting VT-x (baremetal shape). These product variants are not supported on AMD processors. Please contact Stromasys or your Stromasys VAR if you need this type of emulated SPARC hardware to discuss your requirements in detail.

 Please note that the sizing guidelines above—in particular regarding number of host CPU cores and host memory—show the minimum requirements. Every use case has to be reviewed and the actual host sizing has to be adapted as necessary. For example, the number of I/O CPUs may have to be increased if the guest applications produce a high I/O load. Also take into consideration that a system with many emulated CPUs in general is also able to create a higher I/O load and thus the number of I/O CPUs may have to be raised. 

...

Your instance should now be visible in the list of compute instances.

It is recommended to create separate storage space (disk volumes) for Charon application data (e.g., disk images). If required, such volumes can later easily be migrated to another instance (see Storage Management).