releases/deliverables/victoria/cyborg.yaml
Thierry Carrez acaf97ce91 Proposing victoria RC1 for cyborg
As a courtesy for project teams, on RC1 week the release management
team proposes a RC1 release for all cycle-with-rc deliverables,
based on HEAD. That RC1 will double as the branch point for the
stable/victoria branch for cyborg.

Release liaison or PTL should +1 this proposal if they are happy
with it, amend this proposal (for example with a more recent SHA)
to match their needs, or -1 to block it until release-critical
issues are all fixed.

Change-Id: I9cf067e9eb7cce4d1d94c43efe724d7b7e99b8b1
Signed-off-by: Thierry Carrez <thierry@openstack.org>
2020-09-21 16:57:25 +02:00

45 lines
2.0 KiB
YAML

---
team: cyborg
type: service
storyboard: 968
release-model: cycle-with-rc
repository-settings:
openstack/cyborg:
tarball-base: openstack-cyborg
cycle-highlights:
- |
Users can launch instances with accelerators managed by Cyborg since Ussuri
release, this release two more operations * Rebuild and * Evacuate are
supported. See `accelerator operation guide
<https://docs.openstack.org/api-guide/compute/accelerator-support.html>`_
to find all supported operations.
- |
Cyborg supported new accelerator drivers (Intel QAT and Inspur FPGA) and
reached an agreement that Vendors who want to implement a new driver should
at least provide a full driver report result. (Of course, providing
third-party CI is more welcome.) `Supported drivers
<https://docs.openstack.org/cyborg/latest/reference/support-matrix.html>_`
- |
Program API is supported, now users can program FPGA given the pre-uploaded
bitstream. `program API (PATCH deployable)
<https://specs.openstack.org/openstack/cyborg-specs/specs/train/approved/cyborg-api.html>_`
And API microversion for existed APIs is improved such as arq APIs.
- |
In this release, the policy refresh (RBAC with scoped) for cyborg is
partially implemented (Device Profile APIs), we've implemented new default
rules in base policy and device_profile policy, and added the basic
testing framework for all policies.
For the Backward Compatibility, old rules are maintained as deprecated
rules with same defaults as today so that existing deployment will keep
working as it is. After we implement all the features, we'll give two
cycles transition period for operators. See `policy default refresh
<https://specs.openstack.org/openstack/cyborg-specs/specs/ussuri/approved/policy-defaults-refresh.html>`_
releases:
- version: 5.0.0.0rc1
projects:
- repo: openstack/cyborg
hash: 9a16e9b678828f90dde810d37ebeb02f8581edf1
branches:
- name: stable/victoria
location: 5.0.0.0rc1