Page History

...

Slaves hosted in LF handled by LF. All the requests and questions regarding these slaves should be submitted to Akraino HelpdeskJira Support Desk.

Connecting Slaves from Community Labs to Akraino Jenkins

...

1. Create a user named Jenkins on the machine you want to connect to Akraino Jenkins and give the user sudo rights.
2. Install needed software on the machine you want to connect to Akraino Jenkins as slave.
   1. openjdk 8
   2. monit
3. If the slave will be used for running virtual deployments, Functest, and Yardstick, install below software and make Jenkins user the member of the groups.
   1. docker
   2. libvirt

4. Create  Create slave root in Jenkins user home directory.

   Code Block
   language bash
   mkdir -p /home/jenkins/akraino/slave_root

   
   

5. Clone Akraino ci-management repository.

   Code Block
   language bash
   mkdir -p /home/jenkins/akraino/repos cd /home/jenkins/akraino/repos git clone https://gerrit.akraino.org/r/ci-management

   
   

6. Contact LF by sending mail to Akraino Helpdesk and request creation of a slave on Akraino Jenkins. Include below information in your mail.

   1. Slave root (/home/jenkins/akraino/slave_root)

   2. Number of executors (the number of concurrent jobs to allow on the slave).
   3. Label(s). The label(s) define what jobs can be run on a particular slave. Each job should have a slave-label defined in its JJB definition.
   4. A slave name. This has generally followed the convention of "<OS>-dev-<CPUs>c-<RAM>g", though this is not a strict rule. The important thing is that the name is a unique and useful identifier. Other elements, such as "prd" or "snd" to identify the environment or numbering at the end, will be added by LF.
7. You will receive a confirmation from LF containing the complete slave name and a secret token.

8. Run the following script in order to make sure there is no problem connecting. You should see INFO: Connected in the console log.
   

   Code Block
   language bash
   cp /home/jenkins/akraino/repos/ci-management/utils/jenkins-jnlp-connect.sh /home/jenkins/ cd /home/jenkins sudo ./jenkins-jnlp-connect.sh -j /home/jenkins -u jenkins -n <slave name on Akraino Jenkins> -s <the token you received from LF> -t

   
   

   1. If you receive a connectivity error, then you need to check your firewall and allow outgoing connections for the port.

9. Kill the Java slave.jar process.

10. Run the same script normally without test (-t) in order to get monit script created.

    Code Block
    language bash
    sudo ./jenkins-jnlp-connect.sh -j /home/jenkins -u jenkins -n <slave name on Akraino Jenkins> -s <the token you received from LF>

    
    

11. Edit monit configuration and enable http interface. The file to edit is /etc/monit/monitrc on Ubuntu systems. Uncomment below lines.
    

    Code Block
    # set httpd port 2812 and # use address localhost # only accept connection from localhost # allow localhost # allow localhost to connect to the server and

    
    

12. Restart monit service.

    1. Without systemd:
       sudo service monit restart

    2. With systemd: you have to enable monit service first and then restart it.
       sudo systemctl enable monit
sudo systemctl restart monit

13. Check to see if Jenkins comes up as managed service in monit.
    sudo monit status

14. Connect slave to Akraino Jenkins using monit.
    sudo monit start jenkins

15. Check slave on Akraino Jenkins to verify the slave is reported as connected. The slave on Akraino Jenkins should have some executors in “Idle” state if the connection is successful.