On-premises
- Olivier Philippot
- Guillaume SUSSELIN
- Maxime (Deactivated)
UP TO DATE
Overview
The Core Server and the Power Test Bench Server are installed on your premises. The Core Server has to communicate to our central Monitoring and Update Center Server, for license security checking, health monitoring, and updates delivery. The Power Test Bench Server has to communicate with the Core Server.
On the diagram above, “Application Servers” are the usual backend servers of your applications, and “Application repository” is the repository where you put the built applications (Nexus for example…).
Power Test Bench Requirements
Explanations
The Power Test Bench Server is installed on your premises, delivered as applications to be installed on a Physical Server.
Below is the physical installation of the Power Test Bench with the smartphones power management through Plugwise Circles.
Hardware
Server
The minimum hardware configuration for the Power Test Bench Server is as follows:
- Physical Server (Not a virtual machine!)
- 4 Gb RAM
- CPU: 4 cores @ 2.8GHz
- 40 Gb Disk space
- 100 Mbps bandwidth
A physical server is required because a USB dongle, namely a Plugwise Stick, has to be connected to the server to control the power source of the smartphones.
Please note that these figures may vary depending on your number of agents. If needed, our technical team will assist you in a better sizing of the hardware.
Please note that if you install the VM Core Server on the Test Bench physical Server, you need to add the minimum hardware configuration of the VM so the minimum configuration of the physical server becomes :
- 12 Gb RAM
- 90 Gb Disk space
Test Bench devices
In addition to the server, you will need one or more test devices (smartphones, tablets). The device model should be chosen from compatibility list
Additionally, each smartphone has to be plugged to a power source through a Plugwise Circle (https://www.plugwise.com/circle), so that the power source can be toggled on and off. The Plugwise Circles communicate with the Power Test Bench Server using the ZigBee wireless protocol. They must be installed within 3 meters of the Power Test Bench Server.
WIFI hotspot
A good WIFI hotspot is required. You can install a Cisco Meraki MR33 (Optional). See Test Bench network requirements
Software
The following third-party software must be installed on the Power Test Bench Server:
- OS : Ubuntu 16.04+, Debian 8+
- Ansible >= 2.5.1 (for deployment)
- VirtualBox 6.0 (if the VM Core Server is installed on this server)
Prerequisites for the smartphones:
- OS : Android 5.0 minimum
- No software requirement
- Mentioned in the Compatibility List
GREENSPECTOR services are managed through supervisor and run with the user greenspector.
Core Server Requirements
Explanations
The Core Server is provided as a “closed box” VM, for safety reasons. You need to install this VM on your premises.
This VM includes a Debian OS, GREENSPECTOR Core Server software, our monitoring software, updates mechanism, and database.
Hardware
The minimum hardware allocation for the VM is as follows:
- 8 Gb RAM
- CPU: 4 cores @ 2.8GHz
- 50 Gb Disk space
- 100 Mbps bandwidth
Please note that these figures may vary depending on your number of users and usage. If needed, our technical team will assist you in a better sizing of the hardware.
This VM (OVA format) can either be run on a VM hypervisor or with VirtualBox if you have a physical server. Virtualbox supports many host OS. Please refer to https://virtualbox.org for more information.
In the case of an installation on a physical server, please allow for the extra resources needed by the underlying OS, VirtualBox, and any other software installed on it.
If using VirtualBox, you must switch on the virtualization capabilities (VT-d) in the BIOS of the server, and configure the network of the VM to use a bridge.
Please note that you can install this VM on the Test Bench physical Server.
Network Requirements
Power Test Bench Network Requirements
The Power Test Bench Server dialogues with the devices with WIFI. WIFI stability is very important. See the Test Bench Network Requirements
Internet access for the Core Server
The Core Server installed on your premises requires an internet connection.
It has to communicate to our central Monitoring and Update Center Server by HTTP(S), for license security checking, health monitoring, and updates delivery. The Core server has to communicate with the Power Test Bench.
Please make sure that your firewall will allow these connections. Also, if you use a proxy server, you may need to configure it. For the modules, the proxy configuration is ready.
Please note that in the event that the connection between the GREENSPECTOR Core Server and our Monitoring and Update Center Server is lost, then the GREENSPECTOR Core Server will try to re-establish the connection some time later. If the connection is unavailable for some longer time, GREENSPECTOR will cease functioning. In this case, only our Technical Support Team will be able to restart it.
SMTP Server
The Core Server needs to use a SMTP server in order to send some e-mails to the users (for password recovery, and so on). During the installation process, you will be able to enter a valid e-mail account to your SMTP server (either a dedicated account, or your admin’s so that the e-mails seem to be sent by him/her).
Network Flows
Below is the list of the network flows that must be authorized in your company firewalls.
| Flow ID | Port/Protocol | From | To | Description |
|---|---|---|---|---|
| TOOLS-1 | HTTP(S) 80/443 | Any computer or server which uses Tools (Browser, CLI, TestRunner...), Plugins (Jenkins plugin ...), or API | Power Test Bench Server | Usage of the GREENSPECTOR API and GREENSPECTOR Web Interface |
| JENKINS-1 | HTTP(S) 80/443 | Jenkins instances | Power Test Bench Server | Usage of the GREENSPECTOR API |
| SMTP-1 | SMTP | Core Server | SMTP Server | Send emails (user registration, password recovery) |
| GATEWAY-1 | HTTP(S) 80/443 | Power Test Bench Server | Core Server | Create benchmark or custom tests requests. Send tests status and results. |
| TESTBENCH-1 | ADB 5555 | Power Test Bench Server | Test Mobile Devices | Connect to run tests, measure, retrieve measures on Devices |
| TESTBENCH-2 | HTTP(S) 80/443 | Test Mobile Devices | Application servers | Access website, webapp and mobile app backend servers (Mobile devices need access to run test on your website, webapp, or mobile app). |
| TESTBENCH-3 | HTTP(S) 80/443 | Power Test Bench Server | Application servers | Access website or webapp backend servers (PC need access to website or webapp). Not usefull for testing APK. |
| TESTBENCH-4 | HTTP(S) 80/443 | Power Test Bench Server | Application repository | Get mobile apps to test (for example, APK) by downloading a link to an application repository. This is optional. |
| MERAKI-1 | HTTP(S) 80/443 | CISCO Management | Cisco Meraki | Management of Cisco Meraki via Web Interface or API in Cloud This is optional if you do not use a Cisco Meraki router. |
| MERAKI-2 | HTTP(S) 80/443 | Cisco Meraki | CISCO Management | Cisco Meraki sends data to Cisco Management This is optional if you do not use a Cisco Meraki router. |
| MUS-1 | HTTP(S) 80/443 | Core Server (Your premises) | Monitoring and Update Server (Greenspector Cloud) IP Greenspector (à fournir) | Send log reports for health monitoring and license check You may need to gather a proxy configuration for this flow. |
| MUS-2 | HTTP(S) 80/443 | Core Server (Your premises) | Monitoring and Update Server (Greenspector Cloud) IP Greenspector (à fournir) | Retrieve software updates You may need to gather a proxy configuration for this flow. |
| MONITORING-* | SSH 22 | GREENSPECTOR or Company Support Team | Core Server and Power Test Bench Server | Monitoring of the server |
| BACKUP-* | SSH 22 | GREENSPECTOR or Company Support Team | Core Server and Power Test Bench Server | Emergency server access by the GREENSPECTOR Support Team |
| DNS-* | DNS 53 | * | DNS Server | All modules must have access to a DNS |
| NTP-* | NTP 123 | * | NTP Server | All modules must have access to a NTP server for time synchronization |
Maintenance and updates
Monitoring
We take the monitoring of our servers very seriously, in order to provide you with the best level of service.
However on your premises, the underlying server (virtualization server or physical server) monitoring is yours to operate.
Core Server
The Core Server is provided as a “closed box” VM, for safety reasons. We assume that the hardware and software environment underlying the VM is operational, safe and secure.
We take charge of the VM monitoring. Our maintenance team will contact yours if any trouble shall arise. For monitoring purposes, the Core Server VM needs to communicate through HTTPS with GREENSPECTOR monitoring server.
Test Bench Server
You are responsible for monitoring the Power Test Bench Server (monitoring service status, checking log files for errors, etc.).
Database backup and restoration
Core Server
As of today, our Core Server VM does not include any database backup or restore mechanism. The backup and restore functions may be achieved by managing the full VM backup. This VM being installed on your premises, we consider that the VM backup is yours to operate. We recommend daily backups. In the event of a restoration is needed, our maintenance team will contact yours to ask for the restoration.
Test Bench Server
You are responsible of backing up the Power Test Bench Server.
Updates
When a software update is available, our maintenance team will inform your Admin team. They will decide if and when they want to download the updated components and to install them.
Related articles
In this section :