This document is specific to the London RedCentric lab, but should evolve to a more generic setup once we have more labs. For now, there are some hard-coded logic in the wiki as well as the scripts, to make sure we can reproduce at least the one lab we have. Once we have more labs, we'll work to automate that using configuration files, command line options, etc.
...
With the network in place, you can clone the HPC Lab Conf repository (you must be allowed and have your key in the private repo)create both VMs.
First Jenkins:
| Code Block |
|---|
root@hpc-admin # cd ~/labconf/kvm root@hpc-admin # ./jenkins_virt_install.sh |
And the same for Then MrProvisioner:
| Code Block | ||||
|---|---|---|---|---|
| ||||
root@hpc-admin # cd ~/labconf/kvm root@hpc-admin # ./mrp_virt_install.sh |
For both MrProvisioner and Jenkinsboth, the preseed will setup statis IPs (10.50.0.3 and 10.50.0.4 respectively), and they should be visible from the wider network, including the host.
This is done to simplify VM migration and a potential new installation on a different server.
The network setup step above assumes the same IPs, so everything is fixed. In time we'll use configuration files so you don't have to change too many scripts.
Installing the Jenkins service
...
You may get two warnings when you log in to Jenkins, which can be corrected on the Global Security screen:
- Agent to master security subsystem is currently off: Check the box saying "Enable Agent → Master Access Control"
- Jenkins instance uses deprecated protocols: JNLP3-connect: Uncheck the box "Java Web Start Agent Protocol/3" in "Agent Protocols"
Save the configuration and you should be all set.
Installing the MrP service
...