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.
...
For both MrProvisioner and Jenkins, 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.
Installing the Jenkins service
Add your jenkins-hpc IP to Update the Ansible host configuration:
Code Block | ||||
---|---|---|---|---|
| ||||
root@hpc-admin # vim /etc/ansible/hosts |
...
[jenkins |
...
]
10.50.0.4
[infra_servers]
10.50.0.3 |
Installing the Jenkins service
Clone the ansible repository to setup Jenkins:
Code Block | ||||
---|---|---|---|---|
| ||||
root@hpc-admin # git clone https://github.com/BaptisteGerondeau/ans_setup_jenkins.git && cd ans_setup_jenkins
|
Copy the secret files from our private repo there:
Code Block | ||||
---|---|---|---|---|
| ||||
root@hpc-admin # git clone ssh://git@dev-private-git.linaro.org/hpc/labconf.git && cd labconf && root@hpc-admin # cp -r labconf/roles/ ../ (overwriting roles in ans_set_jenkins) / |
Then run Ansible and wait until it exists with no errors:
Code Block | ||||
---|---|---|---|---|
| ||||
root@hpc-admin # cd ans_setup_jenkins && ansible-playbook configure-jenkins.yml -vvv -u root |
...
Ansible will start Jenkins automatically, so you should be able to just open the URL on your browser (assuming you have a route to the machine's IP):
If your Linaro login belongs to the hpc-sig-admin group, then you can directly login, as Jenkins is connected to LDAP, with your email and Linaro password.
BE CAREFUL: Jenkins is not yet using SSL, so your password will be passed plain text. Only use this if you are inside a VPN or on an isolated network.
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
...