...
The Charon-SSP VE License Server has a number of prerequisites:
- The VE license server package
- A suitable Linux instance to be used as the VE license server. This instance must run
- in a supported cloud environment, or
- in a supported VMware environment.
- 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 requirements are described in detail below.
VE License Server Package
...
Where <version> indicates the version of the software, for example, 1.1.45.
Div | ||
---|---|---|
| ||
Linux Instance for License Server
...
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 and in the cloud-specific Getting Started guides on the CHARON-SSP documenation page.
Depending on the cloud environment, 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). An instance launched from such a prepackaged image can also be used as a VE license server.
...
- Requirements for direct ESXi host binding:
- The VE license server must run in one of the VMs on the ESXi server.
- ESXi/vSphere version 6.5 and above.
- Valid license that supports the vSphere API feature.
- Ports 443 and 902 must be accessible to the VE license server host.
- 100 MB of free disk space on the ESXi server to be used by the VE license server host.
- Administrative user (and password) on the ESXi/vSphere host used for the binding between license server and ESXi/vSphere host.
- Requirements for vCenter Server binding:
- The VE license server must run in a VM on one of the ESXi systems managed by the vCenter server.
- Ports 443 and 902 must be accessible to the VE license server host.
- 100 MB of free disk space on the vCenter Server to be used by the VE license server host.
- Administrative user (and password) on the vCenter server used for the binding between license server and vCenter server.
...
The Linux system on which the VE license server runs must fulfill the following requirements:requirements described below.
Linux Hardware and Software requirements
Software requirements for the VE License Server itself:
Red Hat, CentOS, or Oracle Linux (64-bit) versions 7.x or 8.x
...
- 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 Charonthe Charon-SSP user's guide of your emulator version for details (see CHARON-SSP for Linux).
Div | ||
---|---|---|
| ||
Additional Linux Host Requirements for AWS cloud
...
See Cloud-Specific Firewall Information for information an overview about the traffic filtering mechanisms used in the different cloud environments.
...
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 an overview about the mechanisms used in the different cloud environments, and your Linux firewall documentation for any Linux specific questions.
...
- <version> indicates the software version (e.g., 4.23.5).
- <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.
...
If you are not familiar with the installation of RPM packages, please refer to the regular general Charon-SSP user's guide or your Linux system documentation.
...
- Copy the license server software package to the license server host (if still required):
- Use For example, use sftp to connect to the cloud instanceVE license server system.
# sftp -i ~/.ssh/<mykey>
<user>@<linux-ip>
where- <mykey> is the private key of the key-pair you associated with your cloud instance
(for an on-premises VMware installation where login with username/password is allowed, it is not needed) - <user> is the user associated with your license server instance (e.g., opc on OCI, centos for a CentOS instance on AWS, or the custom user on your VMware virtual machine;
for an instance installed from a prepackaged Charon-SSP VE image, use the SFTP user charon) - <linux-ip> is the ip address of your license server system
- <mykey> is the private key of the key-pair you associated with your cloud instance
- Copy the software package to the license server system using the following SFTP command:
> put <local-path-to-license-server-package>
- Use For example, use sftp to connect to the cloud instanceVE license server system.
- Use ssh to log in on the license server host.
where# ssh-i ~/.ssh/<mykey> <user>@<linux-ip>
- <mykey> is the private key of the key-pair you associated with your cloud instance
(for an on-premises VMware installation where login with username/password is allowed, it is not needed) - <user> is the user for interactive login associated with your license server instance (e.g., opc on OCI, centos for a CentOS instance on AWS, or the custom user on your VMware virtual machine;
for an instance installed from a prepackaged Charon-SSP VE image, use sshuser) - <linux-ip> is the ip address of your license server system
- <mykey> is the private key of the key-pair you associated with your cloud instance
- 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>
On an instance installed from a prepackaged Charon-SSP VE marketplace image, the installation package is stored
under /charon/storage) - 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:
...
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, or using other methods.
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 is installed on your local Linux or Windows PC that will be used for management purposes. Running the Charon Manager in a non-graphical cloud or VMware 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.
...
The following table provides an overview of the packages that may be missing:
RPM Package | Graphics and audio emulation | Charon Manager* | Server JIT feature | Charon Agent |
---|---|---|---|---|
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 | |||
pciutils | x |
* If you install the Charon Manager with the yum (or dnf) 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.
...