Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Icb84e4860021f5aa24de0d68542863da7fee4aff
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Includes a minor fix to ipv6 rocky scenario.
Change-Id: I55440dff2fcf7674d4a9c86d9dcb131c226e68ea
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
With the move to upstream artifacts post-fraser the checks to use
upstream artifacts were relying on BRANCH == 'master'. This doesn't
scale as we preserve fraser functionality but add more branches like
gambia. Therefore inversing the logic to accomodate for new branches.
Change-Id: Ice17f6afd33744f44d253d320a194c3f6d02d8bf
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
|
|
Adds Gambia daily/verify jobs and prepares to migrate master queens
scenarios to rocky scenarios.
Change-Id: I7bfe6202e00fd62c1e668f3a6f9b481b9fbca99d
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
- keep fraser jobs for Dovetail, schedule 4 CI runs / week / arch;
- stop running Functest/Yardstick for fraser to cut down CI time;
- reschedule master/gambia triggers to ensure an uniform CI POD
allocation across the week;
- enable gambia triggers;
Change-Id: I2a66628ff3525cc9cbd4ffbb4b790633257b6cba
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I2120546e49bb0a12325d299c6a3b9b54004dc569
Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
Change-Id: I4280286aac855f3fcab5a72aa82e6f8087bbb63e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
|
|
|
|
Change-Id: I432061b472c22dfd65821f8aeaf9c0c5671f3759
Signed-off-by: Sofia Wallin <sofia.wallin@ericsson.com>
|
|
Change-Id: I70f8e7c9372e22e6f3e357b48a0a49f44a4d9078
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Ic1430742e98dd0e98ea3456c636a910c22a90e88
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Functest job timeout is not enough
Functest jobs are aborted after 480 min
Change-Id: I74dfe12b08e322aad53e10d5808b5b739b8d9ce2
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
Change-Id: I3bcc79438dcb552de3056dbd5e0cf263f327da28
Signed-off-by: Trinath Somanchi <trinath.somanchi@nxp.com>
|
|
The current codebase was intended for Fuel@OPNFV up to and including
the Danube release (based on Fuel@Openstack).
Starting with the Euphrates release, Fuel@OPNFV is based on Mirantis
Cloud Platform (MCP), so the Fuel adapter in modules.opnfv needs a
rework to accomodate the new platform:
- remove unused obsolete code in opnfv.utils;
- switch to key-based SSH auth instead of password-based;
- drop proxy-ing SSH to cluster nodes via installer node, instead
SSH directly via PXE/admin network;
Notes:
- MaaS node (when present) is marked with 'installer' role to prevent
ovs-vsctl queries on it;
- gtw01 node (when present) is not marked with any role yet;
JIRA: FUEL-394
Change-Id: If2b7744b950cd502df8eaca0137c9f845a9d077d
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
|
|
Change-Id: I58fc2c56d32c04f2c96136ed69335b5c64771e05
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
|
|
|
|
Adds jobs for building the following LaaS containers:
- opnfv/pharos-tools-laas-dashboard
- opnfv/pharos-tools-laas-celery
- opnfv/pharos-tools-laas-mq
Having these containers built seperately from docker-compose decouples
the build and deployment phases for the dashboard.
Change-Id: I919066f5defd02fe1bbf96cfdf8ec2a6b3d8757d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Some projects already moved away from OPNFV Docs git submodules.
The proposed hack has a couple of problems:
- it still downloads all of OPNFV docs + submodules (recursively!);
- it uses Jenkins to handle gerrit clone/fetch, just to nuke it and
clone the current project again;
But:
- it is a small change, to be replaced when global-jjb will support
gsutil upload for docs preview;
- it provides a locally built preview document instead of the old
(complete) doc preview;
Change-Id: I7426679187eb1cfabb181c59da61f3b794e50e5f
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Idea9af88bd02f647addec9142e0384dc6cf2029a
Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
|
|
|
|
|
|
|
|
|
|
|
|
Change-Id: Ic5e0a004422264fb91f27b1d1152518ef7b159b3
Signed-off-by: Martin Klozik <martin.klozik@tieto.com>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
This is still far from a clean and secure approach, as `pip install`
should not be ran with `sudo`.
However, `-H` limits the area we touch and also fixes some incompat
between disto-provided pip and pip-provided pip.
Change-Id: I0e19dfeaf66f6f453e3868c71016305ae050f0c8
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I450bbd4a3c0e386f949b3b06fe85e74661e2ef2b
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: I3f3b0b150defb12553740f0d4c3ec111fceb7a5b
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Change-Id: I135189c6fa8fbf01f67f37547ca120779c08fbc9
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
PDF/IDFs have been moved out of securedlab to the Pharos repo. Any
references to pulling the files from securedlab have been changed to
look in pharos.
Change-Id: I04608da51afdbe9ec55e3dd23c501c99946b58bb
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
The current impl doesn't exit as expected when running both tiers and
testcases [1][2].
[1] https://build.opnfv.org/ci/view/functest/job/functest-apex-baremetal-daily-master/324/console
[2] https://build.opnfv.org/ci/view/functest/job/functest-apex-baremetal-daily-fraser/284/console
Change-Id: I934c3f54313522011ed87ebebe77fbb285b8ab49
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
With the rework of Fuel & Armband repos, the condition for using sudo
got mixed up and alternated between on/off for armband's deploy/verify
jobs. Rewrite it based on lab allocation instead of project.
Change-Id: I428c585142017b170233858ec3160fdaf998db0c
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Ife7a1fe2feddc54b980e702733d829998f9e02e3
Signed-off-by: BIN HU <bh526r@att.com>
|
|
Change-Id: I2f3b0b150cefb12553740f0d4c3ec111fceb7a5b
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
==~ and its negative form previously used mean the pattern should
match the whole string, while =~ returns true for partial matches.
Change-Id: Ibdeacb4bc221820175b15a87db343fc950e0f9e8
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
While at it, tweak regex for verify job to match 'recheck' right
before EOF.
Change-Id: I3e8e1eeaf2ca947425fa2443b29e150c808eea07
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
- disable functest smoke on arm-virtual* PODs, since we don't perform
a full deployment on those PODs, only a basic integrity check;
Change-Id: I0bcd6da32118ea256652dc74977ef0ee7f2525ab
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
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>
|