Contents
Prerequisites
The Charon-SSP VE License Server has a number of prerequisites:
- The VE license server package
- A suitable Linux cloud instance in a supported cloud environment to be used as the VE license server
- Correct firewall settings
- The VE-capable Charon-SSP emulator software running on a Charon host with appropriate network access to the VE license server
These items are described below.
VE License Server Package
The Charon-SSP VE License Server package is delivered as an RPM package. Stromasys or your Stromasys VAR will provide you with the software or a download link.
Package name:
license-server-<version>.rpm
Where <version> indicates the version of the software, for example, 1.0.28.
Linux Cloud Instance for License Server
The license server package must be installed on a Linux cloud instance.
Currently supported cloud providers:
- Amazon AWS
- Oracle Cloud Infrastructure (OCI)
- Microsoft Azure
- Google Cloud Platform (GCP)
- IBM Cloud
Please refer to your cloud provider's documentation for configuring and launching an appropriate instance. A description of the basic steps of launching an instance can be found in Additional Information.
Software requirements for License Server:
Red Hat, CentOS, or Oracle Linux (64-bit) versions 7.x or 8.x
Basic hardware requirements (the shape or instance type capabilities) for running only the license server:
Must be sufficient for the selected Linux operating system.
Additional hardware requirements (the shape or instance type capabilities) for running the emulator software on the same system:
- If the license server is combined with the Charon-SSP emulator software on the same instance, the instance used must satisfy the requirements of the Charon-SSP host and all instances that will run on it. If this requirement exists, please refer to the Charon-SSP user's guide for details.
Additional general requirements:
- In the AWS cloud, an IAM role (IAMReadOnlyAccess is enough) must be attached to the instance. This can be done during the launch of the instance as indicated in the sample below.
Alternatively, the role can be set/changed by selecting the instance and then use the menu Actions > Instance Settings > Attach/Replace IAM Role.
Firewall Settings
Communication Between License Server and Client System
Any intermediate firewall as well as the cloud-specific subnet and instance security settings must permit the following ports to the appropriate source systems:
- TCP/8083: must be permitted from the client to license server to enable the use the the license by the client.
- TCP/8084: must be permitted by the the license server for any system that should access the web interface to display license information.
See Cloud-Specific Firewall Information for information about the mechanisms used in the different cloud environments.
Simplified sample commands if firewalld is used on the Linux system:
# firewall-cmd --permanent --zone=public --add-port=8084/tcp
# firewall-cmd --permanent --zone=public --add-port=8083/tcp
# firewall-cmd --reload
- The default zone name can be found with the command
firewall-cmd --get--default-zone
, a list of all zones can be displayed with the commandfirewall-cmd --get-zones
. - The parameter permanent writes the command to the respective firewalld configuration files. To add the command to the running firewall, re-run it without the parameter permanent.
- The above simplified sample does not limit the source IP address to the addresses of the license clients. This would require a more sophisticated configuration. Please refer to the documentation of your Linux system.
Communication Between License Server and Cloud Infrastructure
The license server must be able to access information provided by the cloud infrastructure. In particular, it must be able to communicate with the following addresses/systems:
- The metadata server of the cloud environment (169.254.169.254) on all cloud platforms.
- If running on AWS, the host iam.amazonaws.com
- If running on GCP, the host www.googleapis.com
Any intermediate firewall as well as the cloud-specific subnet and instance security settings must permit communication with these systems for the VE license server to function properly. See Cloud-Specific Firewall Information for information about the mechanisms used in the different cloud environments, and your Linux firewall documentation for any Linux specific questions.
Charon-SSP VE-Capable Emulator and Management Software
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-releases. Stromasys or your Stromasys VAR will provide you with the software or a download link.
Please note: The protocol versions used by the emulator software and the license server must be compatible. The software checks for compatible protocol versions and and reports an error should there be a mismatch.
The Charon-SSP packages to be installed are the following RPM packages:
- 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-x86_64.rpm, or
- charon-ssp-<architecture>-<version>.ve.el8-x86_64.rpm
In the above list, the parameters have the following meaning:
- <version> indicates the software version (e.g., 4.1.21).
- <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 el8 denotes packages intended for Red Hat/CentOS/Oracle Linux 8.x.
- Charon Agent, Manager, and Director are not license-model specific.
Please note:
- Unless there is GUI access to the Charon-SSP host system, Charon Manager and Charon Director must be installed on a remote management system that will be used to configure and manage the Charon-SSP software. The Charon-SSP emulator software can also be run from the command-line, in which case Charon Manager and Director are not required.
- The Charon Agent package contains the RPM and Debian packages for the Charon Manager on Linux and a ZIP file for the Charon Manager on Microsoft Windows (charon-manager-ssp-<version>.zip).
- The Charon-SSP VE emulator software can run on the same system as the license server or on a separate system with appropriate network access to the VE License Server.
VE License Server Software Installation
If you are not familiar with the installation of RPM packages, please refer to the regular user's guide or your Linux system documentation.
Please note:
- In versions before 1.0.17, the license server will not start automatically after the initial installation. It will be started once a valid license has been installed (see Installing a License on the VE License Server).
- When upgrading to version 1.0.24 from an older version of the license server, a license update is required due to a change in the license schema.
- If you plan to use a primary and a backup license server, the software must be installed on both systems.
VE License Server Installation Steps
Perform the following steps to install the VE License Server software:
- Copy the license server software package to the cloud instance:
- Use sftp to connect to the cloud instance.
# sftp -i ~/.ssh/<mykey>
<user>@<cloud-instance-ip>
where
<mykey> is the private key of the keypair you associated with your cloud instance
<user> is the privileged user associated with your cloud instance (e.g., "opc" on OCI, or "centos" for a CentOS instance on AWS)
<cloud-instance-ip> the ip address of your cloud instance - Copy the software package to the cloud instance using the following sftp command:
> put <local-path-to-license-server-package>
- Use sftp to connect to the cloud instance.
- Use ssh to log in on the cloud instance.
# ssh -i ~/.ssh/<mykey> <user>@<cloud-instance-ip>
- As a privileged user (root) go to the directory where you stored the installation package and install the package:
- Become the root user:
# sudo -i
- Go to the package location:
# cd <path-to-package-directory>
- Install the package:
- Linux 7.x:
# yum install license-server*.rpm
- Linux 8.x:
# dnf install license-server*.rpm
- Linux 7.x:
- Become the root user:
Below, you find the sample output of an installation:
# yum install license-server-1.0.16.rpm Loaded plugins: fastestmirror, langpacks Examining license-server-1.0.16.rpm: license-server-1.0.16-1.x86_64 Marking license-server-1.0.16.rpm to be installed Resolving Dependencies --> Running transaction check ---> Package license-server.x86_64 0:1.0.16-1 will be installed --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: license-server x86_64 1.0.16-1 /license-server-1.0.16 11 M Transaction Summary ================================================================================ Install 1 Package Total size: 11 M Installed size: 11 M Is this ok [y/d/N]: y Downloading packages: Running transaction check Running transaction test Transaction test succeeded Running transaction Installing : license-server-1.0.16-1.x86_64 1/1 Verifying : license-server-1.0.16-1.x86_64 1/1 Installed: license-server.x86_64 0:1.0.16-1 Complete!
Charon-SSP VE-Capable Emulator Software Installation
General Information
The Charon-SSP packages are RPM packages that are installed using the yum (Linux 7.x), dnf (Linux 8.x), or rpm command. They can be copied to the Charon host system using SFTP as shown in the example for copying the license server RPM.
At least the required emulator packages (charon-ssp-4*.rpm) and the agent (charon-agent*.rpm) must be installed for the system to run emulated SPARC systems and to allow remote management by the Charon Manager. If local management with graphical tools is required, then the Charon Manager and the Charon Director packages must also be installed.
Please note: To use the graphical user interface (Charon Manager for SSP) the Charon Manager package typically has to be installed on your local Linux or Windows PC that will be used for management purposes. Running the Charon Manager in a non-graphical cloud instance and export it via X11-Forwarding is possible, but will require additional configuration and installation steps (with access to a package repository) - this is outside the scope of this document. It is also possible to manage Charon-SSP via the command-line only. This is described in the general Charon-SSP user's guide.
Possible Additional Requirements
Many Linux cloud instance are missing packages that are typically available on workstation installations. Such packages may have to be installed, for example, if graphics device emulation or audio emulation are used. The same applies to the Charon-SSP Manager and the Server JIT feature.
The following table provides an overview of the Workstation-type packages that may be missing:
RPM Package | Graphics and audio emulation | Charon Manager* | Server JIT feature |
---|---|---|---|
libX11 | x | x | |
xorg-x11-server-utils | x | x | |
alsa-plugins-pulseaudio | x | ||
gtk2 | x | ||
xorg-x11-xauth (only required for X11-Forwarding) | x | ||
libicu (version 50 for Linux 7.x, version 60 for Linux 8.x) | x |
* If you install the Charon Manager with the yum command, these packages (except for xorg-x11-xauth) and any dependencies that these packages themselves may have, are resolved automatically if a package repository is available.
If you suspect problems caused by missing packages and the emulator was started via the Charon Manager, check the emulator crash-log file in addition to the emulator log file. If starting the emulator from the command-line, review the command-line output.
The packages above have their own dependencies. Install the above packages with the yum (or dnf) command in order to have their dependencies automatically installed. If your server does not have access to the standard operating system repositories, refer to this document for instructions on setting up a local repositories.
Sample Installation
Only the Charon-SSP emulator packages (4M, 4U(+), 4V(+)) are specific to the license model used. The packages required for managing Charon-SSP (Charon Agent, Manager, and Director) are the same as in the conventional product of the same version.
If you are not familiar with software installation on Linux, and for any additional information about the Charon-SSP software, please refer to the regular Charon-SSP user's guides on the Stromasys Product Documentation and Knowledge Base pages.
The log output below shows a sample Charon-SSP emulator and management package installation on a Linux 7 system:
# yum install charon*.rpm Loaded plugins: fastestmirror, langpacks (lines removed) Resolving Dependencies --> Running transaction check ---> Package charon-agent-ssp.x86_64 0:4.1.14-1 will be installed ---> Package charon-director-ssp.x86_64 0:4.1.14-1 will be installed ---> Package charon-manager-ssp.x86_64 0:4.1.14-1 will be installed ---> Package charon-ssp-4m.x86_64 0:4.1.14.cloud-1 will be installed ---> Package charon-ssp-4u+.x86_64 0:4.1.14.cloud-1 will be installed ---> Package charon-ssp-4v+.x86_64 0:4.1.14.cloud-1 will be installed --> Finished Dependency Resolution (lines removed) Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: charon-agent-ssp x86_64 4.1.14-1 /charon-agent-ssp-4.1.14-x86_64 28 M charon-director-ssp x86_64 4.1.14-1 /charon-director-ssp-4.1.14 287 k charon-manager-ssp x86_64 4.1.14-1 /charon-manager-ssp-4.1.14 4.2 M charon-ssp-4m x86_64 4.1.14.cloud-1 /charon-ssp-4m-4.1.14.cloud-x86_64 5.5 M charon-ssp-4u+ x86_64 4.1.14.cloud-1 /charon-ssp-4u+-4.1.14.cloud-x86_64 41 M charon-ssp-4v+ x86_64 4.1.14.cloud-1 /charon-ssp-4v+-4.1.14.cloud-x86_64 41 M Transaction Summary ================================================================================ Install 6 Packages Total size: 120 M Installed size: 120 M Is this ok [y/d/N]: y Downloading packages: Running transaction check Running transaction test Transaction test succeeded Running transaction Installing : charon-ssp-4u+-4.1.14.cloud-1.x86_64 1/6 Installing : charon-ssp-4v+-4.1.14.cloud-1.x86_64 2/6 Installing : charon-manager-ssp-4.1.14-1.x86_64 3/6 Installing : charon-director-ssp-4.1.14-1.x86_64 4/6 Installing : charon-agent-ssp-4.1.14-1.x86_64 5/6 Created symlink from /etc/systemd/system/multi-user.target.wants/ssp-agentd.service to /etc/systemd/system/ssp-agentd.service. Installing : charon-ssp-4m-4.1.14.cloud-1.x86_64 6/6 Verifying : charon-ssp-4m-4.1.14.cloud-1.x86_64 1/6 Verifying : charon-agent-ssp-4.1.14-1.x86_64 2/6 Verifying : charon-director-ssp-4.1.14-1.x86_64 3/6 Verifying : charon-manager-ssp-4.1.14-1.x86_64 4/6 Verifying : charon-ssp-4v+-4.1.14.cloud-1.x86_64 5/6 Verifying : charon-ssp-4u+-4.1.14.cloud-1.x86_64 6/6 Installed: charon-agent-ssp.x86_64 0:4.1.14-1 charon-director-ssp.x86_64 0:4.1.14-1 charon-manager-ssp.x86_64 0:4.1.14-1 charon-ssp-4m.x86_64 0:4.1.14.cloud-1 charon-ssp-4u+.x86_64 0:4.1.14.cloud-1 charon-ssp-4v+.x86_64 0:4.1.14.cloud-1 Complete!