... | ... | @@ -33,6 +33,8 @@ The following picture is an overview of the currently chosen architecture. |
|
|
|
|
|
**Note that in the previous picture, the term `node` is used in the Jenkins terminology as a remote server where the processing is "farmed out". It is not related to the 4G eNB / 5G gNB terminology.**
|
|
|
|
|
|
The name of the server are generic to describe their function. Typing `ssh nodea.eurecom.fr` will result in an error.
|
|
|
|
|
|
# 2. Server Details #
|
|
|
|
|
|
## 2.1. Jenkins server ##
|
... | ... | @@ -78,6 +80,8 @@ The first method is fundamental for the master CI job since it requires a remote |
|
|
* A lot of processing power
|
|
|
* Pre-installed uvt-kvm tool with pre-downloaded VM images
|
|
|
* See [this page](http://manpages.ubuntu.com/manpages/trusty/man1/uvt-kvm.1.html) for details
|
|
|
* At time of writing, we are using **Ubuntu Server 16.04 LTS**.
|
|
|
* `uvt-simplestreams-libvirt sync arch=amd64 release=xenial`
|
|
|
* For optimization of the network Internet usage, we have installed the `apt-cacher` package.
|
|
|
* It sets up a repository cache on this remote node so that once a package is downloaded from an official repository, all created Virtual Machines will download it from the remote node.
|
|
|
* See more details on [this help page](https://help.ubuntu.com/community/Apt-Cacher-Server)
|
... | ... | |