Releases
Release Name | Status | Most Recent Maintenance Release Date | Initial Release Date | Next Phase | EOL Date |
---|---|---|---|---|---|
Rabat | Pre-Planning | TBD | 1H26 | Planning | TBD |
Quebec | Pre-Planning | TBD | 2H25 | Planning | TBD |
Paris | Pre-Planning | TBD | 1H25 | Planning | TBD |
Oslo | Pre-Planning | TBD | 2H24 | Planning | TBD |
New Delhi | Pre-Planning | TBD | 1H24 | Planning | TBD |
Montreal | Development | TBD | 2H23 | Current Release | TBD |
London | Current Release |
| Supported Release | 1H24 | |
Kohn | Supported Release |
| EOL | 2H23 | |
Jakarta | EOL |
|
| ||
Istanbul | EOL |
|
|
| |
Honolulu | EOL |
|
|
| |
Guilin | EOL |
|
|
| |
Frankfurt | EOL |
|
|
| |
El Alto | EOL |
|
|
| |
Dublin (doc) | EOL |
|
| ||
Casablanca (doc) | EOL |
|
|
| |
Beijing (doc) | EOL |
|
| ||
Amsterdam (doc) | EOL |
|
|
Status Definitions
Status | Meaning |
---|---|
Pre-Planning | Only the release name and an approximate time frame have been determined. |
Planning | Pre-M0. The release name has been chosen and tentative milestone dates have been determined. |
Requirements Definition | Between M0 and M2. The schedule has been approved and requirements are being documented and prioritized. |
Development | After M2 but before release. Requirements are being implemented and tested. |
Current Release | The approved output of the release process which interested end users should be deploying. |
Maintenance Release | The approved output of bug fixes and other changes made to the initial release, or a prior maintenance release. |
Supported Release | Previously a Current Release. Still supported, but only receiving critical updates. ONAP supports the current release and the current release - 1. |
End of Life (EOL) | This release is no longer supported. |
5 Comments
Steven Wright
This seems to be in need of updating given the TSC presentation here. The E,F,G release cadence is changed and, the view needs to look forward several years beyond 2020.
Herbert Eiselt
Seems to need update. Actual Development Version is Kohn.
David McBride
Fixed
Md Habibur Rahman
Hi there,
I am trying to deploy full ONAP-KOHN version in HA Kubernetes cluster on Openstack. I am using the following document: https://docs.onap.org/en/kohn/guides/onap-operator/settingup/index.html. I prepared the base environment following the docs and the specs of my nodes are:
NAME STATUS ROLES AGE VERSION
onap-m1 Ready control-plane 8d v1.26.3
onap-m2 Ready control-plane 7d1h v1.26.3
onap-w1 Ready <none> 7d1h v1.26.3
onap-w2 Ready <none> 7d1h v1.26.3
onap-w3 Ready <none> 7d1h v1.26.3
onap-w4 Ready <none> 7d1h v1.26.3
onap-w5 Ready <none> 7d1h v1.26.3
onap-w6 Ready <none> 7d1h v1.26.3
**Though it recommends to use Kubernetes components of 1.23.8 in the docs, but I use 1.26.3 (latest version) to make stable HA cluster according to illustration attached in https://kubernetes.io/releases/version-skew-policy/. Is it mandatory to use 1.23.8 version ???
However, when I was trying to deploy OOM Helm release, I am getting following error:
I will appreciate any kind of help or suggestion to resolve this issue. Thanks in advance,
Habib
Michael Dürre
This is not a good place to get help for issues. Please use the email discussion groups from here or our Slack