Red Hat OpenStack Platform component support levels and graduation requirements for RHOSP 15
Table of Contents
New features, services, and components. go through a number of support levels before inclusion in a Red Hat OpenStack Platform release 15 as fully supported for production use. This is to ensure the right balance between providing the enterprise stability expected of our offerings with the need to allow our valued customers and partners to experiment with new OpenStack-related technologies while providing feedback to help guide future development activities.
This article is intended to assist customers and partners with understanding these support levels and the current state of support in Red Hat OpenStack Platform for well various OpenStack 'big tent' projects.
Component Support Levels
| Type | Description | Knowledge Base Article |
|---|---|---|
| Community Support | As part of Red Hat's commitment to upstream first integration of new components into our OpenStack distributions begins in the RDO community where we work the open in collaboration with our customers and partners. While it may be possible to overlay components introduced in a given RDO release (e.g. RDO "Mitaka") on the equivalent Red Hat OpenStack Platform release (e.g. Red Hat OpenStack Platform 9) these packages will not be formally supported by Red Hat.
Customers and partners are welcome to provide feedback on components in the RDO distribution, and even to submit new components of their own, with a view to eventual inclusion in a Red Hat OpenStack Platform release. Production support will however only be provided for such components if or when all items in the supportability checklist (explained further in this article) are complete and the component is shipped in a formal Red Hat OpenStack Platform release. Community support in RDO can take two forms:
|
https://access.redhat.com/articles/1325163 |
| Technology Preview | Technology Preview components are shipped in a formal Red Hat OpenStack Platform release but are not fully supported, features in this state are listed as such in the release notes for each release where the technology preview designation applies. Technology Preview features provide early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process.
However, these features are not fully supported under Red Hat Subscription Level Agreements, may not be functionally complete, and are not intended for production use. As Red Hat considers making future iterations of Technology Preview features generally available with production support, we will attempt to resolve any issues that customers experience when using these features. |
https://access.redhat.com/support/offerings/techpreview |
| Production Support | Production Support components are shipped in a formal Red Hat OpenStack Platform release and are fully supported. Refer to the knowledge base for information on the scope of coverage, service level agreement, product life cycle, and more. | https://access.redhat.com/support/offerings/production |
Component Graduation
How does a feature/service/component graduate to Technology Preview?
To graduate from the community support levels to a technology preview in Red Hat OpenStack Platform there must be an identifiable use case that can not be, and is not, addressed by the existing supported offering and is only address via the introduction of the new feature/service/component. The feature/service/component must also have first reached the Community Support - Integrated support level in the RDO Community project.
Note that there is no mandatory deadline for a component to graduate from Community Support in RDO to a Technology Preview in Red Hat OpenStack Platform, graduation is criteria based. For a component to graduate from community support in RDO to a technology preview in Red Hat OpenStack Platform a number of items must be completed including but not limited to::
- A review of project stability, including API and interface stability, supportability of dependencies, and supportability of the associated back-ends where applicable.
- A check that automated tests exist, have been reviewed for coverage, and that the project is supported in the continuous integration harness.
- A new package security review.
- Creation of a documentation plan.
In addition all Community Support - Integrated criteria must have previously been met, and remain met.
How does a feature/service/component graduate to Production Support?
Note that there is no mandatory deadline for a component to graduate from a Technology Preview to Production Support in Red Hat OpenStack Platform, graduation is criteria based. For a component to graduate from a Technology Preview in Red Hat OpenStack Platform to production support in Red Hat OpenStack Platform a number of items must be completed including but not limited to::
- A review of the original driving use case(s) to ensure they remain valid and that the project still meets the requirements of the use case(s).
- A review of automated scenario testing coverage.
- A review of production level user documentation.
- A review of bugs filed during the Technology Previews to identify any outstanding critical or blocker bugs that must be addressed prior to graduation.
In addition all Technology Preview criteria must have previously been met, and remain met, and the component must have been in Technology Preview for at least one release cycle to gather customer and partner feedback.
Component Support Graduation
This dashboard reflects the current level of support that each OpenStack big tent component listed has graduated to. Note that this table is updated based on graduation status in the most recently available releases of the relevant software and the information contained does not apply retrospectively to previous releases. For information pertaining to which release a component first graduated to production support in Red Hat OpenStack Platform refer to Component, Plug-In, and Driver Support in RHEL OpenStack Platform.
A ✔ symbol indicates that the component has the support level of the column it appears in.
A ✘ symbol indicates that the component does not have the support level of the column it appears in.
| Component | Description | Big Tent- Community | Community Support - RDO (Packaged) | Community Support - RDO (Integrated) | Technology Preview - Red Hat OpenStack Platform | Production Support - Red Hat OpenStack Platform |
|---|---|---|---|---|---|---|
| Aodh | Telemetry Alarming service | ✔ | ✔ | ✔ | ✘ | ✔ |
| Barbican | Secrets management service | ✔ | ✔ | ✔ | ✘ | ✔ |
| BGP-VPN | BGP VPN Neutron networks | ✔ | ✔ | ✘ | ✘ | ✘ |
| Ceilometer | Telemetry service | ✔ | ✔ | ✔ | ✘ | ✔ |
| Cinder | Block storage service | ✔ | ✔ | ✔ | ✘ | ✔ |
| [Congress] | Governance service | ✔ | ✘ | ✘ | ✘ | ✘ |
| Designate | DNS service | ✔ | ✔ | ✘ | ✘ | ✘ |
| Dynamic Routing | L3 routing services to Neutron | ✔ | ✘ | ✘ | ✘ | ✘ |
| Freezer | Backup, Restore, and Disaster Recovery service | ✔ | ✘ | ✘ | ✘ | ✘ |
| Glance | Image service | ✔ | ✔ | ✔ | ✘ | ✔ |
| Gnocchi | Telemetry Time Series Database as a Service | ✔ | ✔ | ✔ | ✘ | ✔ |
| Heat | Orchestration service | ✔ | ✔ | ✔ | ✘ | ✔ |
| Horizon | Dashboard | ✔ | ✔ | ✔ | ✘ | ✔ |
| Ironic | Bare Metal service | ✔ | ✔ | ✔ | ✘ | ✔ |
| Keystone | Identity service | ✔ | ✔ | ✔ | ✘ | ✔ |
| Kolla | Containerized deployment | ✔ | ✘ | ✘ | ✘ | ✘ |
| Kuryr | Container networking | ✔ | ✔ | ✔ | ✘ | ✔ |
| L2GW | Layer 2 Gateways in Neutron | ✔ | ✔ | ✘ | ✘ | ✘ |
| Magnum | Containers service | ✔ | ✔ | ✘ | ✘ | ✘ |
| Manila | Shared File Systems service | ✔ | ✔ | ✔ | ✘ | ✔ |
| Mistral | Workflow service | ✔ | ✔ | ✘ | ✘ | ✘ |
| Murano | Application Catalog service | ✔ | ✔ | ✘ | ✘ | ✘ |
| Neutron | Network service | ✔ | ✔ | ✔ | ✘ | ✔ |
| Nova | Compute service | ✔ | ✔ | ✔ | ✘ | ✔ |
| Octavia | Load Balancer service | ✔ | ✔ | ✔ | ✘ | ✔ |
| Opstools | Tools for Availability Monitoring and Common Logging | ✘ | ✔ | ✔ | ✘ | ✔T |
| Panko | Telemetry event service | ✔ | ✔ | ✔ | ✘ | ✔ |
| Rally | Benchmark service | ✔ | ✔ | ✘ | ✔† | ✘ |
| Sahara | Data Processing service | ✔ | ✔ | ✘ | ✘† | ✔‡ |
| Skydive | Network Analysis service | ✘ | ✔ | ✘ | ✘ | ✘ |
| SFC | Service Function Chaining | ✔ | ✘ | ✘ | ✘ | ✘ |
| Swift | Object Storage service | ✔ | ✔ | ✔ | ✘ | ✔ |
| Tacker | NFV Orchestrator | ✘ | ✘ | ✘ | ✘ | ✘ |
| Tap as a Service | Port mirroring service | ✔ | ✘ | ✘ | ✘ | ✘ |
| Tempest | OpenStack Integration Test Suite | ✔ | ✔ | ✔ | ✘ | ✔ |
| TripleO | Deployment service | ✔ | ✔ | ✔ | ✘ | ✔ |
| Trove | Database service | ✔ | ✔ | ✘ | ✘ | ✘ |
| Zaqar | Message service | ✔ | ✔ | ✘ | ✘ | ✘ |
T Clients for Sensu and Fluentd are graduating to Full Support, Server-side components and Ansible playbooks for Server deployment remain Community Supported.
† Service, component, or feature graduated to technology preview under old graduation requirements and has been grandfathered into newer releases in this state. The updated criteria on this page will need to be met for graduation to production support.
‡ Service, component, or feature deprecated.
Component Deprecation Policy
From time to time features, projects, and components become obsolete either due to the introduction of a competing feature/project/component that better meets the defined use cases or as a result of the project being deprecated upstream. The deprecation process applies only to features/projects/components that have graduated to production support. The process is initiated and tracked via a deprecation bug in bugzilla.redhat.com. When deprecation occurs the feature/project/component an entry will appear in the release notes for the version of Red Hat OpenStack Platform the deprecation is occurring in highlighting both the deprecation and the intent to remove the feature/project/component in the future.
As part of the deprecation process Red Hat will endeavor to identify which customers and partners use the relevant feature/project/component, as well as any other items that have dependencies on the piece being deprecated, while working with the community and identified stakeholders to developer a migration plan. For relevant infrastructure level components this migration plan will include Red Hat OpenStack director (TripleO) support for automating the migration.
When the removal of the feature/project/component occurs the release notes for the Red Hat OpenStack Platform release in which the removal first occurs will include an entry highlighting the removal.
Comments