Nomad Configuration

Revision as of 16:42, 29 May 2020 by Dwallacelf (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Details of the different aspects of Nomad Configuration

Docker Hub Repositories

Jenkins Nomad Plugin Configuration

Proposed Jenkins Nomad Plugin Label to Docker Image Mapping

Jenkins Nomad Plugin Labels can only be created via LF Service Desk requests. In order to test CI jobs in the Jenkins Sandbox, a different label must exist which points to a sandbox Dockerhub repository to avoid disrupting operational jobs during docker image testing. This is the proposed nomenclature for the mapping of Jenkins Nomad Plugin labels and the corresponding dockerhub repositories (production and sandbox variants).

All new docker images will first be pushed to the Dockerhub associated 'sandbox repo' and all CI jobs utilizing the Jenkins Nomad Plugin Label will be verified in the Jenkins Sandbox, by modifying the appropriate JJB YAML files to point to the sandbox repo. Once all CI jobs have been verified, then the image will be pushed to the operational dockerhub repository associated with the label.

Label Nomenclature



  • {arch} = x86_64, arm64, ...
  • {os} = ubuntu1804, ubuntu2004, centos7, centos8, ...
  • {job} = project/job abbreviation (tbd)

NOTE: The 'sandbox' and 'verify' labels should NEVER be merged into the ci-management repository and will be added only to the Jenkins sandbox instance. The 'prod' labels will be added to both sandbox and production Jenkins instance.


Label Dockerhub Repo

Q & A

QUESTION 1: Is there a need for project specific images?

ANSWER 1: Current project jobs are generally tightly bound to VPP Infra dependencies with some additional requirements. For most executors it makes sense to combine dependencies into the VPP docker images rather than have per project images. Project jobs that are independent will have separate images (e.g. csit 'vpp-device' test).

QUESTION 2: Is there a need for different size labels (small, medium, large) with different resource allocations (eg. CPU, Memory, etc)?

ANSWER 2: Currently most of the 'size' flavors are unused. Initial plan is to not have size based labels. If specific jobs have different size requirements, then labels will be added with job specific postfix.

Legacy Jenkins Label to Docker Image Mapping

These labels are currently defined (circa VPP 20.05) and will be removed once there are no references to them in the ci-management repo. Some of them are not being used today.

Legacy Label(s) Dockerhub Repo
ubuntu1604-us, ubuntu1604-s, ubuntu1604-m, ubuntu1604-l, ubuntu1604-hub-us, ubuntu1604-nus,
ubuntu1804-us, ubuntu1804-s, ubuntu1804-m, ubuntu1804-l, ubuntu1804-hub-us, vpp-csit-device, vpp-csit-ubuntu18,
ubuntu1804arm-hub-us, ubuntu1804arm-s, ubuntu1804arm-m, vpp-csit-arm-ubuntu18
centos7-us, centos7-s, centos7-m, centos7-l, centos7-hub-us,