There are three different ways to setup a system: by RPM, by a Virtual Machine and from Source Code. The first two are recommended. Setting up from GIT is useful if you want to make changes in the code and contribute to github.
1. Installation with RPM
For CentOS 7 (RHEL 7)
Code Block | ||
---|---|---|
| ||
curl -vsL https://raw.githubusercontent.com/schmto/nmsprime/dev/INSTALL-REPO.sh | bash
yum install nmsprime-* |
Note: complete install runs in 13min on a blank CentOS 7 VM.
Widget Connector | ||
---|---|---|
|
2. Virtual Machine
We will provide a ready VM soon..
3. From Source Code
See: 3. From Source Code Link
Login
Username: root
...
1.1. Cloud | 1.2. On-Prem | |
---|---|---|
Remote Access | (1) | |
Full Functionality | ||
Automatically Backup (7) | (for SLA only) | |
Ready to start | <5min | <15min |
Required Tech-Knowledge (mostly Linux) | low | middle |
High Availability | >99,99% (2) | (3) |
Adaptive CPU Capacity | (4) | (4) |
Adaptive RAM Capacity | (4) | |
Adaptive Disk Capacity | (4) | |
Data Storage Region | EU (5) | your location |
Notes:
(1). See Cloud Guidance for getting your private credentials
(2). https://aws.amazon.com/de/ec2/
(3). Hosting your own infrastructure means: High Availability is your task. Depending on your infrastructure you could also reach >99,99%. How-To increase your availability by building your own Failover Architecture. We will consult Customers with a valid SLA regarding HA.
(4). Your Task / Job.
(5). Dynamically growing regarding the actual requirement
(6). default is Frankfurt. Can be changed regarding your needs. Contact: support@nmsprime.com
(7). Backup is hosted on a regional other IT infrastructure prevent that a regional lost affects your datas
(8). Mostly depening on your Linux knowledge