...
Jenkins Build Minion Images
The OpenStack virtual machine Centos and Ubuntu images are created by a combination of ansible and packer jobs that are configured from the packer directory in the ci-management repository. Check the Jenkins build minions are OpenStack virtual machines. The software, the number of cores, amount of virtual memory and amount of disk memory are all configured in files managed in the directory `ci-management/jenkins-config/clouds/openstack/cattle` to see the full set. As of this writing these configuration files determine the images available to Jenkins jobsare the choices:
centos7-builder-1c-1g ubuntu1804-builder-2c-2g.cfg
centos7-docker-2c-8g-200g.cfg ubuntu1804-builder-4c-4g.cfg
centos7-docker-2c-8g.cfg ubuntu1804-docker-4c-4g.cfg |
Each config file contains an image name such as "ZZCI - CentOS 7 - builder - x86_64 - 20200317-165605.039". Each image can have a different set of software packages. It's fairly safe to assume that all have C compilers, Go compilers, Java virtual machines and Python interpreters. Discovering the exact software contents of a build node generally requires analyzing the Ansible roles and packer commands that are also maintained in the ci-management repository.
Image Templates
The images are created by a combination of ansible and packer jobs that are configured from the packer directory in the ci-management repository. The O-RAN-SC project has uses two classes of minion imagesprovision templates: "builder" and "docker". The latter mostly adds the Docker daemon and other software to the former. These two templates are combined with the two choices of Linux distro, currently Centos and Ubuntu base operating systems, for to yield a minimum of four image combinations. To add software, start with the file `packer/provision/local-docker.yaml`.
You can discover the available image names by checking the image builder job results in Jenkins - next section.
Image Builder Jobs
The images are built automatically on a monthly basis by these Jenkins jobs:
...
