1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. SPDX-License-Identifier: CC-BY-4.0
3 .. (c) Open Platform for NFV Project, Inc. and its contributors
11 CI for OPNFV requires a range of resources in order to meet testing and
12 verification needs. Each resource must meet a set of criteria in order
13 to be part of CI for an OPNFV release. There are three types of
16 - Baremetal PODs (PODs)
17 - Virtual PODs (vPODs)
21 .. _ci-resources-baremetal-pods:
26 Baremetal PODs are used to deploy OPNFV on to baremetal hardware through
27 one of the installer projects. They enable the full range of scenarios
28 to be deployed and tested.
32 In order of a POD to be considered CI-Ready the following requirements
35 #. Pharos Compliant and has a PDF
36 #. Connected to Jenkins
39 #. No manual intervention
41 .. include:: tables/ci-baremetal-servers.rst
44 .. _ci-resources-virtual-pods:
49 Virtual PODs are used to deploy OPNFV in a virtualized environment
50 generally on top of KVM through libvirt.
54 #. Have required virtualization packages installed
55 #. Meet the Pharos resource specification for virtual PODs
56 #. Connected to Jenkins
59 .. include:: tables/ci-virtual-servers.rst
61 .. _ci-resources-build-servers:
66 Build servers are used to build project, run basic verifications (such
67 as unit tests and linting), and generate documentation.
71 #. Have required `packages_` installed
73 #. Connected to Jenkins
75 .. include:: tables/ci-build-servers.rst
83 .. include:: tables/none-ci-servers.rst
91 .. include:: tables/ci-labels.rst
93 .. _packages: https://wiki.opnfv.org/display/INF/Continuous+Integration#ContinuousIntegration-BuildServers