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.

...

You may get two warnings when you log in to Jenkins, which can be corrected on the Global Security screen:

• ERROR in config.xml: Jenkins may complain "version 1.1" is not supported, only 1.0. Editing /var/lib/jenkins/config.xml and changing that on the first line seems to work.
• Agent to master security subsystem is currently off: Go to Security Settings and check the box saying "Enable Agent → Master Access Control"
• Jenkins instance uses deprecated protocols: JNLP3-connect: Go to Security Settings > Agents and clear the box "Java Web Start Agent Protocol/3" in "Agent Protocols"
  

Themes: Install the Simple Theme Plugin and choose one from the list by updating the theme URL in the general settings.

Save the configuration and you should be all set.

Installing the Jenkins Jobs

...

Mr-Provisioner

You need to create their accounts the Jenkins account by hand in MrP, add their the ssh keys and generate their the MrP token. This requirement will be dropped when bug 102 is fixed.

Jenkins

Then add those tokens to the list in

For now, the process is the following:

• Log in as "admin"
• Create a user "jenkins", set its password to some random string (use 'pwgen')
• Logout as "admin" - Log in as "jenkins"
• Add the SSH keys of all slaves to it
• Generate a token, copy and paste somewhere
• Log out as "jenkins"

Jenkins

Having the APITOKEN generated by the step above, add it to hpc_lab_job_deploy/vars/jslave_tokens.yml.secret in the following format (same token for all users):

jslave_tokens:
  - jslave: d05ohpc
    token: APITOKEN
  - jslave-d03-benchmark: qdcohpc
    token: APITOKEN
  - jslave: d03bench
    token: APITOKEN
  - jslave: d05bench
    token: APITOKEN
  - jslave: qdcbench
    token: APITOKEN
jslave-d03-openhpc  - jslave: tx2bench
    token: APITOKEN
etc...

and then run the playbook:

...

The file server VM setup job handles the user creation + SSH keys copy, but this will move to the hpc_lab_jenkins repo.

Updating Jenkins Jobs

Once the jobs are installed and working, on every change pertaining the Jenkins configuration, you just need to update the repo and run the same playbook again:

root@hpc-admin # cd hpc_lab_jenkins
root@hpc-admin # git fetch -a & git pull
root@hpc-admin # ansible-playbook -vvv -u root hpc_jobs_deploy.yml

...