Versions Compared

Old Version 33

changes.mady.by.user W.Erber

Saved on

compared with

New Version 34

changes.mady.by.user W.Erber

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrections for current AWS image

...

Excerpt
nameCloudLicGeneralAWS

This chapter describes the basic licensing options available for Charon-SSP instances in cloud environments. Please note that even though other solutions may be possible the ones listed here represent the recommended solutions for Charon-SSP cloud-based solutions.

Charon-SSP requires a license to run emulated SPARC systems. For a typical cloud-based installation, there are different Charon-SSP product variants with different licensing models. As availability may differ depending on cloud environment, please contact your Stromasys representative for any questions about product availability and licensing options.

1. Old AWS marketplace image: the cloud-specific, prepackaged Charon-SSP AL (Automatic Licensing) marketplace image offers pay-as-you-go billing for Charon-SSP. Please contact Stromasys Sales should you be interested in this option. It utilizes either

  • a public, Stromasys-operated cloud-specific license server, or
  • a private customer-operated VE license server operating in AutoVE mode.

2. New AWS marketplace image: the cloud-specific, prepackaged Charon-SSP Amazon Linux marketplace image offers pay-as-you-go billing for Charon-SSP. It utilizes a public, Stromasys-operated cloud-specific AutoVE license server. Please contact your Stromasys representative should you require your own private AutoVE license server.

2. Charon-SSP VE (Virtual Environment) utilizing a customer-operated, private VE license server in a supported cloud environment. The license server, in this case, operates in general VE mode. Charon-SSP VE is available as a

  • prepackaged marketplace image on some cloud platforms, and
  • in RPM package format for a conventional installation.

These licensing options are briefly described below.

Please note: the user is responsible for any Solaris licensing obligations and has to provide the appropriate licenses.


Charon-SSP

...

Amazon Linux Licensing Overview


Excerpt
nameCloudLicAWSAutoVE

When a cloud instance is launched from an AWS Charon-SSP Automatic AutoVE Amazon Linux marketplace image, this instance requires a license to run emulated SPARC systems. This license is created automatically upon first launch of the Charon-SSP Automatic AutoVE instance.

Please note the following points:

  • You will be billed by AWS for your use of the Charon-SSP instance. Stromasys will not bill you directly. 
  • By default, this option requires that Charon instances have Internet access (via their own public IP address or NAT) for the license mechanism to work. If NAT is used, the gateway must be an instance in the same cloud (i.e., the source IP address must be from the address range of the same cloud provider in which the Charon host instance runs). The public, Stromasys-operated AutoVE license servers must be reachable on port 8083. Also, a DNS service must be reachable to resolve the host names of the license servers, or corresponding entries in /etc/hosts must exist. The license server details are provided below.
  • Alternatively, the customer can set up Should you require a private AutoVE server (making the need of access to the public Internet obsolete), please contact your Stromasys representative.
  • If you change the instance type after first launching the instance and thereby change the number of CPU cores (or if the number of CPU cores is changed by any other method), the license will be invalidated.
  • Some licensing problems or other requirements (e.g., additional CPU cores needed) may make it necessary to move the emulator to a new instance. Therefore, it is strongly recommended to store all relevant emulator data on a separate disk volume that can easily be detached from the old instance and attached to a new instance.
  • If you need to set up a new Charon host instance with automatic using the public AutoVE licensingservers, you must create it via launching a new instance from the appropriate marketplace image and (as necessary) copying/moving the emulator data and configuration to the new instance. Cloning the instance with will result in a system with an invalid 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).

...