Release magnum 9.2.0 for Train

Change-Id: I4c08f5795a0fc52cf4eb9ed1bf4fdfbbde1aa14a
This commit is contained in:
Bharat Kunwar 2019-12-24 14:59:22 +00:00
parent 53257288f9
commit ba138eb10b

View File

@ -6,24 +6,24 @@ type: service
repository-settings: repository-settings:
openstack/magnum: {} openstack/magnum: {}
cycle-highlights: cycle-highlights:
- Fedora CoreOS driver is now available which we are please to offer since - Fedora CoreOS driver is now available which we are please to offer
Fedora Atomic will be end of life at the end of this November. We welcome since Fedora Atomic will be end of life at the end of this November.
users to test and provide feedback for this driver. We welcome users to test and provide feedback for this driver.
- Node groups now allow users to create clusters with groups of nodes with - Node groups now allow users to create clusters with groups of nodes
different specs, e.g. GPU node groups and high memory node groups. Thanks with different specs, e.g. GPU node groups and high memory node
for the great work from CERN team and StackHPC. groups. Thanks for the great work from CERN team and StackHPC.
- Rolling upgrade is available for both Kubernetes version and the node - Rolling upgrade is available for both Kubernetes version and the
operating system with minimal downtime. node operating system with minimal downtime.
- Auto healing can be deployed on Kubernetes cluster to monitor the cluster - Auto healing can be deployed on Kubernetes cluster to monitor the
health and replace broken nodes when failure is detected. cluster health and replace broken nodes when failure is detected.
- Boot Kubernetes cluster from volumes and configurable volume types. - Boot Kubernetes cluster from volumes and configurable volume types.
They can even set the volume type etcd volumes. This may be useful for They can even set the volume type etcd volumes. This may be useful
cloud providers who want to use SSDs, NVMEs, etc. for cloud providers who want to use SSDs, NVMEs, etc.
- Private cluster can be created following best security practices, isolating - Private cluster can be created following best security practices,
Kubernetes clusters from Internet access. This may be a desirable feature isolating Kubernetes clusters from Internet access. This may be
for enterprise users. Now they have the flexibility to choose between a a desirable feature for enterprise users. Now they have the flexibility
private cluster by default and only allow access to the API exposed on to choose between a private cluster by default and only allow access
Internet or make it fully accessible. to the API exposed on Internet or make it fully accessible.
releases: releases:
- version: 9.0.0.0rc1 - version: 9.0.0.0rc1
projects: projects:
@ -42,6 +42,10 @@ releases:
projects: projects:
- repo: openstack/magnum - repo: openstack/magnum
hash: 347b7b74742306f8573d2a6cad8e966a8ccb58fb hash: 347b7b74742306f8573d2a6cad8e966a8ccb58fb
- version: 9.2.0
projects:
- repo: openstack/magnum
hash: 1115672e7284bdd77a5951e93d47b22495c33d91
branches: branches:
- name: stable/train - name: stable/train
location: 9.0.0.0rc1 location: 9.0.0.0rc1