Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: remove misleading mention of prerelease

...

Where <version> indicates the version of the software, for example, 1.01.354.

Div
classpagebreak


Linux Cloud Instance for License Server

...

The VE license server software requires matching Charon-SSP emulator software. The necessary features are available in Charon-SSP 4.2.x and its pre-releaseslater. Stromasys or your Stromasys VAR will provide you with the software or a download link. In certain cloud environments, Stromasys may offer a prepackaged Charon-SSP VE image on the cloud marketplace. This image includes the Charon-SSP emulator software (already installed) and the VE License Server RPM package (can be installed optionally). If you use a Charon host in the cloud and the instance was launched from such a prepackaged image, the required VE-capable emulator software is already installed (refer to the respective cloud-specific Getting Started Guide for more information).

...

  • Management components (not VE-specific):
    • charon-agent-ssp-<version>-x86_64.rpm
    • charon-director-ssp-<version>.rpm
    • charon-manager-ssp-<version>.rpm
  • VE-capable emulator software:
    • charon-ssp-<architecture>-<version>.ve.el7-x86_64.rpm
    • charon-ssp-<architecture>-<version>.ve.el8-x86_64.rpm

In the above list, the parameters placeholders have the following meaning:

  • <version> indicates the software version (e.g., 4.2.25).
  • <architecture> indicates the type of emulated SPARC covered by the software (currently it can have the values 4m, 4u, 4v, 4u+, or 4v+).
  • The string ve in the package containing the Charon emulator software indicates that this version of the emulator requires a VE license server.
  • The string el7 denotes packages intended for Red Hat/CentOS/Oracle Linux 7.x.
  • The string el8 denotes packages intended for Red Hat/CentOS/Oracle Linux 8.x.
  • Charon Agent, Manager, and Director are not license-model specific.

...

  1. Copy the license server software package to the cloud instance (if still required):
    1. Use sftp to connect to the cloud instance.
      # sftp -i ~/.ssh/<mykey>  <user>@<cloud-instance-ip>
      where
      1. <mykey> is the private key of the key-pair you associated with your cloud instance
      2. <user> is the user associated with your cloud instance (e.g., opc on OCI, or centos for a CentOS instance on AWS; for an instance installed from a prepackaged Charon-SSP VE image, use the SFTP user charon)
      3. <cloud-instance-ip> the ip address of your cloud instance
    2. Copy the software package to the cloud instance using the following sftp command:
      > put <local-path-to-license-server-package>
  2. Use ssh to log in on the cloud instance.
    # ssh-i ~/.ssh/<mykey> <user>@<cloud-instance-ip>
    where
    1. <mykey> is the private key of the key-pair you associated with your cloud instance
    2. <user> is the user for interactive login associated with your cloud instance (e.g., opc on OCI, or centos for a CentOS instance on AWS; for an instance installed from a prepackaged Charon-SSP VE image, use sshuser)
    3. <cloud-instance-ip> the ip address of your cloud instance
  3. As a privileged user (root) go to the directory where you stored the installation package and install the package:
    1. Become the root user:          # sudo -i
    2. Go to the package location:   # cd <path-to-package-directory>
      On an instance installed from a prepackaged Charon-SSP VE image, the installation package is stored under /charon/storage)
    3. Install the package:             
      1. Linux 7.x: # yum install license-server*.rpm
      2. Linux 8.x: # dnf install license-server*.rpm

...