summaryrefslogtreecommitdiffstats
path: root/docs/submodules/kvmfornfv
diff options
context:
space:
mode:
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>2018-09-18 18:19:47 +0200
committerGerrit Code Review <gerrit@opnfv.org>2018-09-21 14:07:23 +0000
commitf026fe07783489f1cb6818873b31bc802fe01c86 (patch)
treea1a5e8566449dec8924bd8a5d30a5bdd23185b91 /docs/submodules/kvmfornfv
parent5df2d9d6fc43c27d0ecc73f28f0808f4673af06e (diff)
Update git submodules
* Update docs/submodules/releng from branch 'master' - [fuel] verify: Add baremetal testing on request Duplicate fuel-verify jobs based on cluster type (virtual, baremetal) and allow (re)checking changes using a specific scenario: - ALL changes will trigger a virtual POD CI cycle (build, deploy, smoke) on submit, rebase etc., just like they used to; - change comments containing a substring formatted like: * `recheck: os-odl-nofeature-ha` * `reverify: os-odl-nofeature-noha` * `recheck` will trigger only virtual or baremetal deployments of the required scenario (default os-nosdn-nofeature-noha) on: * virtual PODs if scenario is NOHA; * baremetal PODs if scenario is HA; - limit arm64 verify job running on arm-virtual2 to the installation of infrastructure VMs and skip cluster setup to prevent POD time starvation; Limitations: - HA scenarios can only be verified on manual request via a change comment (e.g. 'recheck: os-odl-ovs-ha'); JIRA: FUEL-390 Change-Id: I6368cfd045180d6a7202b8d817b17a4b123ba2af Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Diffstat (limited to 'docs/submodules/kvmfornfv')
0 files changed, 0 insertions, 0 deletions