Installation
Installation Overview
The N-Squared Voucher Server software is released in multiple packages to provide the various logical components for a complete platform.
Instructions for installing these packages are given below.
Once installed, the appropriate configuration must be applied in order to bring the platform into service.
OS Support
All N2VS packages are designed to be installed on Linux-based systems such as Red Hat Linux and Debian. Installation is performed using standard package management tools:
yum
/dnf
andrpm
on Red Hat systems.apt
,apt-get
anddpkg
on Debian systems.
N2VS is officially supported on the following systems:
- Red Hat systems:
- Red Hat Enterprise Linux 8
- Red Hat Enterprise Linux 9
- Debian systems:
- Ubuntu 22.04 LTS
- Ubuntu 24.04 LTS
In practice, N2VS will run on any relatively modern Debian-based or Red Hat-based distribution with appropriate adjustments to these installation instructions.
Minimum Server Requirements
Each logical component has slightly different recommended minimum requirements:
Type | Free Disk | RAM | CPU GHz | Notes |
---|---|---|---|---|
GUI | 1Gb | 1Gb | 2GHz | Lightweight web application with static file content. |
API | 1Gb | 1GB | 2GHz | Lightweight API application only. |
SVC | 5GB | 8GB | 2x 2GHz | Resource-intensive under load; scale according to expected voucher services traffic. |
DB | 50GB | 8GB | 2GHz | Moderately intensive under load. |
In cases where components are co-installed, resources must be increased to accommodate.
Installation Planning
At minimum, an N2VS platform must be able to perform the functions of the GUI, API, SVC, and DB logical components. These may be on separate physical or virtual servers, or co-hosted as required. There may also be multiple instances of any component type, as required for business continuity or expected traffic load.
When planning the footprint of an N2VS platform, the following recommendations apply for production environments:
- At least two SVC nodes should be present, with each able to take the projected full voucher redemption traffic. This allows maintenance of one node at a time while still providing service.
- Similarly, if BSS/OSS continuity is required, multiple API nodes can be used in an active/active setup. These can be loadshared to as required by your IP infrastructure.
- Consider also having multiple DB instances to prevent a single point of failure. There must always be a single active primary SMF database, however at least one secondary SMF node is suggested. The MongoDB Voucher Database must have at least two data nodes as well as one arbiter node.
Installation Disclaimer
No installation guide can cover every pre-requisite or potential eventuality of package installation. While N-Squared has documented the expected N2VS installation steps, sometimes a target environment may differ in an unexpected manner and require additional or alternative steps actions to achieve an operational N2VS environment. Please contact N-Squared to discuss such situations.
Package Availability
Individual packages for manual installation are available on request from N-Squared as part of a licensed software or services agreement.
N-Squared may alternately furnish access details for a software repository that can be integrated with your OS package management tools or satellite repository server directly for ease of installation and maintenance.
Package Versions
All packages distributed by N-Squared will include the following parts to identify them uniquely:
<NAME>
- the name of the package, as referred to in these instructions.<M>
- the major revision number of the package.<m>
- the minor revision number of the package.<p>
- the point release number of the package.<b>
- the build number of the package release.
Package names take a slightly different format, depending on the OS type.
RPM-based Systems | DEB-based Systems |
---|---|
<NAME>-<M>.<m>.<p>-b.noarch.rpm |
<NAME>_<M>.<m>.<p>-<b>_all.deb |
Installation Instructions
Instructions for the installation of each logical component are given in the following sub-sections:
For service nodes:
Additional instructions are available for:
Generally there is no required order of installation for N2VS components. However, in order to complete the appropriate configuration of the platform, all planned components should be fully installed before such configuration is started.
Note that specific steps may have to be performed prior to component installation on Red Hat or Debian systems.