This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for antelope. Also,
updating the template name to generic one.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: Icb4424810fc7e6ff4933bc93c6cd1b1315449328
In zed cycle, OpenStack projects and oslo lib
has dropped the py3.6 and py3.7 support
- https://governance.openstack.org/tc/reference/runtimes/zed.html
With oslo not supporting the py3.6 and py3.7, we disscussed in cyborg
team, and we will remove the py3.6 and py3.7 support too.
Closes-Bug: #1977636
Change-Id: Ib934e50ee6e89cb1e2b4cbf8390eee2baa30effd
Bandit check is a very important tool to check code security.
Before this patch, we put it as a non-voting job to temporarily ignore
existed bandit failures. After fixed all the existed bandit failures,
we should change this test job from non-voting to voting to make the
bandit job actually work, that is to let zuul do the bandit check for
all patches and give them zuul -1 once the new changes fail to pass
bandit the check.
Depends-On: https://review.opendev.org/#/c/720475
Depends-On: https://review.opendev.org/#/c/720456
Depends-On: https://review.opendev.org/#/c/720149
Depends-On: https://review.opendev.org/#/c/720143
Change-Id: I8480243382f66779a12b1e433b69d9be512e843e
Cyborg now does not have a code security check, which may connive at
possible security issues. For example, shell-related operations for drivers
may be insecure. Current "sudo lspci -nnn -D" in huawei ascend driver code[0]
is insecure, but there is no any job/test that can check the potential security
issues. So this patch introduces bandit as a code security check.
[0]:https://github.com/openstack/cyborg/blob/master/cyborg/accelerator/drivers/aichip/huawei/ascend.py#L69
Change-Id: Ia1f9acbbd176180cb5fe97b1a2eee5f98a95dea6
Python 2.7 support has been dropped. Last release of Cyborg to support
py2.7 is OpenStack Train. The minimum version of Python now
supported by Cyborg is Python 3.6.
Depends-On: https://review.opendev.org/#/c/691766/
Change-Id: Ie87ef7727b50d8d5ca43f0283c5688199c35412e
In this U version, Improve UT for important Cyborg module is
an important task.
It is necessary to add openstack-cover-jobs to zuul. This way
we can easily view the unit test coverage of each file.
such as nova:
https://github.com/openstack/nova/blob/master/.zuul.yaml#L374
Change-Id: I854a51a2105628c5e5e9c30282e0f4b259c33ed3
As part of Train community goal 'Support IPv6-Only Deployments and Testing'[1],
Tempest has defined the base job 'devstack-tempest-ipv6' which will
deploy services on IPv6.
This commit Run 'cyborg-tempest-ipv6-only' job in cyborg gate.
Because cyborg-tempest-ipv6-only is non-voting job it is added on check
pipeline only. This is non voting because cyborg-tempest job is not yet
voting.
Depends-On: https://review.opendev.org/#/c/682514/
Story: #2005477
Task: #35886
[1] https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
Change-Id: I24e6e1e407391932049a126502ba94e57cbc6124
Fix points are extracted in following methods.
1st: check with sixer:
change unicode function to use sixer lib.
2nd: check & fix manually.
2-1: as_dict() function
fix as_dict() to work in py3 env.
2-2: delete unnecessary as_dict() call in response to the change in as_dict()
2-3: fix all_pfs_have_vf() to be able to treat both list and iterator,
because filter() function returns list in py2, iterator in py3.
2-4: To treats map() in same way in py2/3 env , wrap map() with list() in P6,P7
2-5: add python3.7 to setup.cfg
2-6: add py3 tests, as voting
Change-Id: Ibfdec7258c731ee45ce1b9bdba4b2024cea78a12
Story: #2003219
Task: #23418
This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs as part of the
python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I0d5c754e54910f3bdca69470dd518411a0958d83
Story: #2002586
Task: #24291
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I9126f432d33b139f936cbf31f8f11bca3a92770f
Story: #2002586
Task: #24291
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I3066f4fdf016d26f43a34ecd60c64ec6423f31fd
This patch implements first step in zuulv3 migration guide [1]:
Move jobs to Cyborg repo
[1] https://docs.openstack.org/infra/manual/zuulv3.html#legacy-job-migration-details
Change-Id: I31d5d7aed511aca18c1096b9f5eb7572f683d613
Needed-By: If816cfec5ace8f9fd7293c0749948d2c0dcb817a
Needed-By: I40e9380d049f541bf34488a3010d95f4a6835179
OpenStack Release Bot
zhangbailin