Fix release notes linking
The StX release notes contains a table with links to older versions of the notes, however, they point to local copies on the same branch, not the original copies on respective branches. These copies need to be deleted and the links corrected to point to the respective branches. Partial-Bug: 2056459 Change-Id: I95c82127b49043b3bda3c095dc60e7198c18c804 Signed-off-by: Ron Stone <ronald.stone@windriver.com>
This commit is contained in:
Ron Stone
parent
cf23a7855a
commit
40c867139d
|
|
@ -72,6 +72,6 @@ For additional information about project teams, refer to the
|
|||
New features in this version
|
||||
----------------------------
|
||||
|
||||
.. include:: /releasenotes/r7-0-release-notes-85446867da2a.rst
|
||||
.. include:: /releasenotes/index.rst
|
||||
:start-after: start-new-features-r7
|
||||
:end-before: end-new-features-r7
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
|
|
@ -1,108 +0,0 @@
|
|||
==================
|
||||
R1.0 Release Notes
|
||||
==================
|
||||
|
||||
These are the release notes for StarlingX R1.0.
|
||||
|
||||
.. contents::
|
||||
:local:
|
||||
:depth: 1
|
||||
|
||||
---------
|
||||
ISO Image
|
||||
---------
|
||||
|
||||
You can find a pre-built image for R1.0 at the
|
||||
`StarlingX mirror
|
||||
<https://mirror.starlingx.windriver.com/mirror/starlingx/centos/2018.10/20181110/outputs/iso/>`__.
|
||||
|
||||
------------
|
||||
New Features
|
||||
------------
|
||||
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| StoryBoard ID | Feature |
|
||||
+===================================+===================================+
|
||||
| N/A | ovs-dpdk integration |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 2002820 | Support for external Ceph backend |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 2202821 | Support for adding compute nodes |
|
||||
| | to all-in-one duplex deployments |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 2002822 | Support remote client for Windows |
|
||||
| | and Mac OS |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 2003115 | Deprecate proprietary Cinder |
|
||||
| | volume backup and restore |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 2002825 | Support Gnocchi storage backend |
|
||||
| | for OpenStack telemetry |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 2002847 | Add ntfs-3g packages |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 2002826 | Memcached integration |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 2002935 | Support for Precision Time |
|
||||
| | Protocol (PTP) |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 2003087 | Generalized interface and network |
|
||||
| | configuration |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 2003518 | Enable Swift on controllers |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 2002712 | StarlingX API documentation |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
|
||||
-------------
|
||||
Other changes
|
||||
-------------
|
||||
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| StoryBoard ID | Change |
|
||||
+===================================+===================================+
|
||||
| 2002827 | Decouple Service Management REST |
|
||||
| | API from sysinv |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 2002828 | Decouple Fault Management from |
|
||||
| | stx-config |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 2002829 | Decouple Guest-server/agent from |
|
||||
| | stx-metal |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 2002832 | Replace compute-huge init script |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 2002834 | Add distributed cloud repos to |
|
||||
| | StarlingX |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 2002846 | Python Optimization |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 2003389, 2003596 | Upgrade kernel and srpm/rpms to |
|
||||
| | CentOS 7.5 |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 3003396, 2003339 | Upgrade libvirt to 4.7.0 |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| 3002891 | Stx-gui plug-in for Horizon |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| Many | Build enhancements, cleanups and |
|
||||
| | optimizations |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| Many | Enable basic zuul checks and |
|
||||
| | linters |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| Many | Python 2 to 3 upgrade for |
|
||||
| | stx-update, stx-metal, stx-fault, |
|
||||
| | stx-integ |
|
||||
+-----------------------------------+-----------------------------------+
|
||||
|
||||
-------
|
||||
Testing
|
||||
-------
|
||||
|
||||
Review the R1.0
|
||||
`test plan <https://wiki.openstack.org/wiki/StarlingX/stx.2018.10_Testplan>`__
|
||||
for a list of tests executed on the R1.0 release.
|
||||
|
||||
View the
|
||||
`testing summary <https://wiki.openstack.org/wiki/StarlingX/stx.2018.10_TestingSummary>`__
|
||||
to see the status of testing for the R1.0 release.
|
||||
|
|
@ -1,64 +0,0 @@
|
|||
====================
|
||||
R2.0.1 Release Notes
|
||||
====================
|
||||
|
||||
.. contents::
|
||||
:local:
|
||||
:depth: 1
|
||||
|
||||
---------
|
||||
ISO image
|
||||
---------
|
||||
|
||||
You can find pre-built ISO and Docker images for stx.2.0.1 at the
|
||||
`StarlingX mirror,
|
||||
<https://mirror.starlingx.windriver.com/mirror/starlingx/release/2.0.1/centos/>`_
|
||||
|
||||
------
|
||||
Branch
|
||||
------
|
||||
|
||||
The source code for stx.2.0.1 is available in the r/stx.2.0 branch
|
||||
in the StarlingX git repositories. The exact source code can be cloned by:
|
||||
|
||||
::
|
||||
|
||||
repo init -u https://opendev.org/starlingx/manifest -b refs/tags/2.0.1b
|
||||
repo sync --force-sync
|
||||
|
||||
----------
|
||||
Deployment
|
||||
----------
|
||||
|
||||
A full system install is required to deploy stx.2.0.1. There is no upgrade
|
||||
patch from StarlingX release 2.0.
|
||||
|
||||
-------
|
||||
Changes
|
||||
-------
|
||||
|
||||
The StarlingX 2.0.1 release provides fixes for the following bugs:
|
||||
|
||||
* `1817936 <https://bugs.launchpad.net/starlingx/+bug//1817936/>`_
|
||||
Periodic message loss seen between VIM and OpenStac REST APIs
|
||||
* `1827246 <https://bugs.launchpad.net/starlingx/+bug//1827246/>`_
|
||||
Access to VM console not working as Horizon redirects to
|
||||
novncproxy.openstack.svc.cluster.local
|
||||
* `1830736 <https://bugs.launchpad.net/starlingx/+bug//1830736/>`_
|
||||
Ceph osd process was not recovered after lock and unlock on storage
|
||||
node with journal disk
|
||||
* `1843915 <https://bugs.launchpad.net/starlingx/+bug//1843915/>`_
|
||||
Cannot apply a chart with a local registry
|
||||
* `1843453 <https://bugs.launchpad.net/starlingx/+bug//1843453/>`_
|
||||
Calico configuration file has yaml format error
|
||||
* `1836638 <https://bugs.launchpad.net/starlingx/+bug//1836638/>`_
|
||||
RT kernel memory leak when creating/deleting pods
|
||||
* `1840771 <https://bugs.launchpad.net/starlingx/+bug//1840771/>`_
|
||||
CVE-2018-14618:NTLM buffer overflow via integer overflow
|
||||
* `1836685 <https://bugs.launchpad.net/starlingx/+bug//1836685/>`_
|
||||
CVE: integer overflow in the Linux kernel when handling TCP
|
||||
Selective Acknowledgments (SACKs)
|
||||
* `1837919 <https://bugs.launchpad.net/starlingx/+bug//1837919/>`_
|
||||
dbmon timeouts are too low
|
||||
* `1838692 <https://bugs.launchpad.net/starlingx/+bug//1838692/>`_
|
||||
ansible replay fails if kubeadm init was not successful
|
||||
|
|
@ -1,203 +0,0 @@
|
|||
==================
|
||||
R2.0 Release Notes
|
||||
==================
|
||||
|
||||
.. contents::
|
||||
:local:
|
||||
:depth: 1
|
||||
|
||||
---------
|
||||
ISO image
|
||||
---------
|
||||
|
||||
You can find a pre-built ISO and Docker images for StarlingX release 2.0 at the
|
||||
`StarlingX mirror
|
||||
<https://mirror.starlingx.windriver.com/mirror/starlingx/release/2.0.0/centos/>`_.
|
||||
|
||||
------
|
||||
Branch
|
||||
------
|
||||
|
||||
The source code for StarlingX release 2.0 is available in the r/stx.2.0 branch
|
||||
in the StarlingX git repositories.
|
||||
|
||||
----------
|
||||
Deployment
|
||||
----------
|
||||
|
||||
A full system install is required to deploy the StarlingX release 2.0.
|
||||
There is no upgrade path from StarlingX release 1.0 (stx.2018.10)
|
||||
|
||||
-----------------------------
|
||||
New features and enhancements
|
||||
-----------------------------
|
||||
|
||||
The main feature in the StarlingX R2.0 release is the re-structuring of the
|
||||
software to provide a containerized OpenStack cloud on top of a bare metal
|
||||
Kubernetes cluster. In R2.0 StarlingX manages the
|
||||
|
||||
* Dedicated physical servers
|
||||
* Kubernetes services
|
||||
* Containerized OpenStack services
|
||||
|
||||
This allows StarlingX to support the hosting of applications in multiple
|
||||
scenarios. For example:
|
||||
|
||||
* On bare metal servers using OpenStack Ironic
|
||||
* On virtual machines using OpenStack Nova
|
||||
* In containers using Kubernetes
|
||||
|
||||
StarlingX 2.0 eliminates patches against upstream OpenStack. The 1.0 release of StarlingX included many patches against OpenStack Pike. The 2.0 release contains
|
||||
about 5 patches against Nova and is otherwise running completely unmodified Stein.
|
||||
|
||||
The 5 patches are back ports of the NUMA live migration fixes that were recently
|
||||
accepted into upstream for OpenStack Train. This means that the next release of StarlingX will run completely unmodified OpenStack.
|
||||
|
||||
*****************************
|
||||
R2.0 feature list and stories
|
||||
*****************************
|
||||
|
||||
The list below provides a detailed list of features with the associated
|
||||
StoryBoard entries for the features.
|
||||
|
||||
* Kubernetes container platform:
|
||||
|
||||
`2002843, <https://storyboard.openstack.org/#!/story/2002843>`_
|
||||
`2004273, <https://storyboard.openstack.org/#!/story/2004273>`_
|
||||
`2004712, <https://storyboard.openstack.org/#!/story/2004712>`_
|
||||
`2004642, <https://storyboard.openstack.org/#!/story/2004642>`_
|
||||
`2004022, <https://storyboard.openstack.org/#!/story/2004022>`_
|
||||
`2003907, <https://storyboard.openstack.org/#!/story/2003907>`_
|
||||
`2003909, <https://storyboard.openstack.org/#!/story/2003909>`_
|
||||
`2004760, <https://storyboard.openstack.org/#!/story/2004760>`_
|
||||
`2005350, <https://storyboard.openstack.org/#!/story/2005350>`_
|
||||
`2003908, <https://storyboard.openstack.org/#!/story/2003908>`_
|
||||
`2004520, <https://storyboard.openstack.org/#!/story/2004520>`_
|
||||
`2005249, <https://storyboard.openstack.org/#!/story/2005249>`_
|
||||
`2004763, <https://storyboard.openstack.org/#!/story/2004763>`_
|
||||
`2002844, <https://storyboard.openstack.org/#!/story/2002844>`_
|
||||
`2005193, <https://storyboard.openstack.org/#!/story/2005193>`_
|
||||
`2002840, <https://storyboard.openstack.org/#!/story/2002840>`_
|
||||
`2005066, <https://storyboard.openstack.org/#!/story/2005066>`_
|
||||
`2004711, <https://storyboard.openstack.org/#!/story/2004711>`_
|
||||
`2004762, <https://storyboard.openstack.org/#!/story/2004762>`_
|
||||
`2005198, <https://storyboard.openstack.org/#!/story/2005198>`_
|
||||
`2004470, <https://storyboard.openstack.org/#!/story/2004470>`_
|
||||
`2003087, <https://storyboard.openstack.org/#!/story/2003087>`_
|
||||
`2004710, <https://storyboard.openstack.org/#!/story/2004710>`_
|
||||
`2004447, <https://storyboard.openstack.org/#!/story/2004447>`_
|
||||
`2004007, <https://storyboard.openstack.org/#!/story/2004007>`_
|
||||
`2003491, <https://storyboard.openstack.org/#!/story/2003491>`_
|
||||
`2002845, <https://storyboard.openstack.org/#!/story/2002845>`_
|
||||
`2002841, <https://storyboard.openstack.org/#!/story/2002841>`_
|
||||
`2002839 <https://storyboard.openstack.org/#!/story/2002839>`_
|
||||
|
||||
* Containerized Openstack services:
|
||||
|
||||
`2002876, <https://storyboard.openstack.org/#!/story/2002876>`_
|
||||
`2003910, <https://storyboard.openstack.org/#!/story/2003910>`_
|
||||
`2004751, <https://storyboard.openstack.org/#!/story/2004751>`_
|
||||
`2005424, <https://storyboard.openstack.org/#!/story/2005424>`_
|
||||
`2004764, <https://storyboard.openstack.org/#!/story/2004764>`_
|
||||
`2004433, <https://storyboard.openstack.org/#!/story/2004433>`_
|
||||
`2005074 <https://storyboard.openstack.org/#!/story/2005074>`_
|
||||
|
||||
* Containerized OVS support as the default virtual switch:
|
||||
|
||||
`2004649 <https://storyboard.openstack.org/#!/story/2004649>`_
|
||||
|
||||
* SR-IOV network device plug-in support:
|
||||
|
||||
`2005208 <https://storyboard.openstack.org/#!/story/2005208>`_
|
||||
|
||||
* Ansible bootstrap deployment:
|
||||
|
||||
`2004695 <https://storyboard.openstack.org/#!/story/2004695>`_
|
||||
|
||||
* Collected integration for platform resource monitoring:
|
||||
|
||||
`2002823 <https://storyboard.openstack.org/#!/story/2002823>`_
|
||||
|
||||
* OVS-DPDK integration enhancements:
|
||||
|
||||
`2004472, <https://storyboard.openstack.org/#!/story/2004472>`_
|
||||
`2002944, <https://storyboard.openstack.org/#!/story/2002944>`_
|
||||
`2002947 <https://storyboard.openstack.org/#!/story/2002947>`_
|
||||
|
||||
* CentOS upgrade to 7.6:
|
||||
|
||||
`2004521, <https://storyboard.openstack.org/#!/story/2004521>`_
|
||||
`2004522, <https://storyboard.openstack.org/#!/story/2004522>`_
|
||||
`2004516, <https://storyboard.openstack.org/#!/story/2004516>`_
|
||||
`2004901, <https://storyboard.openstack.org/#!/story/2004901>`_
|
||||
`2004743, <https://storyboard.openstack.org/#!/story/2004743>`_
|
||||
`2003597 <https://storyboard.openstack.org/#!/story/2003597>`_
|
||||
|
||||
* qemu/libvirt updates:
|
||||
|
||||
`2003395, <https://storyboard.openstack.org/#!/story/2003395>`_
|
||||
`2005212 <https://storyboard.openstack.org/#!/story/2005212>`_
|
||||
|
||||
* Ceph upgrade to mimic:
|
||||
|
||||
`2004540, <https://storyboard.openstack.org/#!/story/2004540>`_
|
||||
`2003605 <https://storyboard.openstack.org/#!/story/2003605>`_
|
||||
|
||||
* Openstack rebase to Stein:
|
||||
|
||||
`2004765, <https://storyboard.openstack.org/#!/story/2004765>`_
|
||||
`2004583, <https://storyboard.openstack.org/#!/story/2004583>`_
|
||||
`2004455, <https://storyboard.openstack.org/#!/story/2004455>`_
|
||||
`2004751, <https://storyboard.openstack.org/#!/story/2004751>`_
|
||||
`2004765, <https://storyboard.openstack.org/#!/story/2004765>`_
|
||||
`2006167, <https://storyboard.openstack.org/#!/story/2006167>`_
|
||||
`2005750 <https://storyboard.openstack.org/#!/story/2005750>`_
|
||||
|
||||
* StarlingX-specific source patch removal:
|
||||
|
||||
`2003857, <https://storyboard.openstack.org/#!/story/2003857>`_
|
||||
`2004583, <https://storyboard.openstack.org/#!/story/2004583>`_
|
||||
`2004600, <https://storyboard.openstack.org/#!/story/2004600>`_
|
||||
`2004869, <https://storyboard.openstack.org/#!/story/2004869>`_
|
||||
`2004610, <https://storyboard.openstack.org/#!/story/2004610>`_
|
||||
`2004607, <https://storyboard.openstack.org/#!/story/2004607>`_
|
||||
`2004427, <https://storyboard.openstack.org/#!/story/2004427>`_
|
||||
`2004386, <https://storyboard.openstack.org/#!/story/2004386>`_
|
||||
`2004312, <https://storyboard.openstack.org/#!/story/2004312>`_
|
||||
`2003394, <https://storyboard.openstack.org/#!/story/2003394>`_
|
||||
`2003112, <https://storyboard.openstack.org/#!/story/2003112>`_
|
||||
`2004455, <https://storyboard.openstack.org/#!/story/2004455>`_
|
||||
`2005212, <https://storyboard.openstack.org/#!/story/2005212>`_
|
||||
`2004557, <https://storyboard.openstack.org/#!/story/2004557>`_
|
||||
`2004477, <https://storyboard.openstack.org/#!/story/2004477>`_
|
||||
`2004406, <https://storyboard.openstack.org/#!/story/2004406>`_
|
||||
`2004404, <https://storyboard.openstack.org/#!/story/2004404>`_
|
||||
`2004216, <https://storyboard.openstack.org/#!/story/2004216>`_
|
||||
`2004203, <https://storyboard.openstack.org/#!/story/2004203>`_
|
||||
`2004135, <https://storyboard.openstack.org/#!/story/2004135>`_
|
||||
`2004133, <https://storyboard.openstack.org/#!/story/2004133>`_
|
||||
`2004109, <https://storyboard.openstack.org/#!/story/2004109>`_
|
||||
`2004108, <https://storyboard.openstack.org/#!/story/2004108>`_
|
||||
`2004020, <https://storyboard.openstack.org/#!/story/2004020>`_
|
||||
`2004019, <https://storyboard.openstack.org/#!/story/2004019>`_
|
||||
`2003803, <https://storyboard.openstack.org/#!/story/2003803>`_
|
||||
`2003767, <https://storyboard.openstack.org/#!/story/2003767>`_
|
||||
`2003765, <https://storyboard.openstack.org/#!/story/2003765>`_
|
||||
`2003759, <https://storyboard.openstack.org/#!/story/2003759>`_
|
||||
`2003758, <https://storyboard.openstack.org/#!/story/2003758>`_
|
||||
`2003757 <https://storyboard.openstack.org/#!/story/2003757>`_
|
||||
|
||||
* DevStack enablement:
|
||||
|
||||
`2005285, <https://storyboard.openstack.org/#!/story/2005285>`_
|
||||
`2003160, <https://storyboard.openstack.org/#!/story/2003160>`_
|
||||
`2003163, <https://storyboard.openstack.org/#!/story/2003163>`_
|
||||
`2004370, <https://storyboard.openstack.org/#!/story/2004370>`_
|
||||
`2003161, <https://storyboard.openstack.org/#!/story/2003161>`_
|
||||
`2003159, <https://storyboard.openstack.org/#!/story/2003159>`_
|
||||
`2003126 <https://storyboard.openstack.org/#!/story/2003126>`_
|
||||
|
||||
* Miscellaneous build enhancements:
|
||||
|
||||
`2004013, <https://storyboard.openstack.org/#!/story/2004013>`_
|
||||
`2004043 <https://storyboard.openstack.org/#!/story/2004043>`_
|
||||
|
|
@ -1,145 +0,0 @@
|
|||
==================
|
||||
R3.0 Release Notes
|
||||
==================
|
||||
|
||||
.. contents::
|
||||
:local:
|
||||
:depth: 1
|
||||
|
||||
---------
|
||||
ISO image
|
||||
---------
|
||||
|
||||
You can find a pre-built ISO and Docker images for StarlingX release 3.0 at the
|
||||
`StarlingX mirror
|
||||
<https://mirror.starlingx.windriver.com/mirror/starlingx/release/3.0.0/centos/>`_.
|
||||
|
||||
------
|
||||
Branch
|
||||
------
|
||||
|
||||
The source code for StarlingX release 3.0 is available in the r/stx.3.0 branch
|
||||
in the StarlingX Git repositories.
|
||||
|
||||
----------
|
||||
Deployment
|
||||
----------
|
||||
|
||||
A system install is required to deploy the StarlingX release 3.0. There is no
|
||||
upgrade path from previous StarlingX releases.
|
||||
|
||||
-----------------------------
|
||||
New features and enhancements
|
||||
-----------------------------
|
||||
|
||||
The list below provides a detailed list of features with the associated
|
||||
StoryBoard entries for the features.
|
||||
|
||||
* Infrastructure and Cluster Monitoring
|
||||
|
||||
`2005733 <https://storyboard.openstack.org/#!/story/2005733>`_
|
||||
|
||||
* Integrate with Openstack Train
|
||||
|
||||
`2006544 <https://storyboard.openstack.org/#!/story/2006544>`_
|
||||
|
||||
* Integrate Distributed Cloud with containers
|
||||
|
||||
`2004766 <https://storyboard.openstack.org/#!/story/2004766>`_
|
||||
|
||||
* Integrate Backup & Restore with containers
|
||||
|
||||
`2004761 <https://storyboard.openstack.org/#!/story/2004761>`_
|
||||
|
||||
* Intel FPGA K8s Device Plugin Initial Integration
|
||||
|
||||
`2006495 <https://storyboard.openstack.org/#!/story/2006495>`_
|
||||
|
||||
* Intel GPU K8s Device Plugin Integration
|
||||
|
||||
`2005937 <https://storyboard.openstack.org/#!/story/2005937>`_
|
||||
|
||||
* Intel QAT K8s Device Plugin Integration
|
||||
|
||||
`2005514 <https://storyboard.openstack.org/#!/story/2005514>`_
|
||||
|
||||
* Layered Build Prep
|
||||
|
||||
`2006166 <https://storyboard.openstack.org/#!/story/2006166>`_
|
||||
|
||||
* Redfish Integration
|
||||
|
||||
`2005861 <https://storyboard.openstack.org/#!/story/2005861>`_
|
||||
|
||||
* Support for authenticated registry for bootstrap and application apply
|
||||
|
||||
`2006274 <https://storyboard.openstack.org/#!/story/2006274>`_
|
||||
|
||||
* Support for OpenID connect authentication parameters for bootstrap
|
||||
|
||||
`2006235 <https://storyboard.openstack.org/#!/story/2006235>`_
|
||||
|
||||
* Support for floating and pinned workloads on worker nodes
|
||||
|
||||
`2006565 <https://storyboard.openstack.org/#!/story/2006565>`_
|
||||
|
||||
* Support for NTP and PTP co-existence
|
||||
|
||||
`2006499 <https://storyboard.openstack.org/#!/story/2006499>`_
|
||||
|
||||
* Time Sensitive Networking for VMs
|
||||
|
||||
`2005516 <https://storyboard.openstack.org/#!/story/2005516>`_
|
||||
|
||||
* Upversion container components
|
||||
|
||||
`2005860, <https://storyboard.openstack.org/#!/story/2005860>`_
|
||||
|
||||
`2006347 <https://storyboard.openstack.org/#!/story/2006347>`_
|
||||
|
||||
-------------------------
|
||||
Known limitations in R3.0
|
||||
-------------------------
|
||||
|
||||
The following are known limitations in the StarlingX R3.0 release. Workarounds
|
||||
are suggested where applicable. Note that these limitations are considered
|
||||
temporary and will likely be resolved in a future release.
|
||||
|
||||
********************************
|
||||
Changing Keystone admin password
|
||||
********************************
|
||||
|
||||
After the Keystone admin password is changed, kube-system namespace registry
|
||||
secrets must be manually updated.
|
||||
Tracking Launchpad: https://bugs.launchpad.net/starlingx/+bug/1853017
|
||||
|
||||
It is recommended that the Keystone admin password not be changed unless necessary.
|
||||
|
||||
**Workaround:** If you must update the WRCP's Keystone admin user password in R3.0,
|
||||
you must also manually update the kube-system namespace's registry secrets that
|
||||
hold the admin password for image pulls:
|
||||
|
||||
#. Update the WRCP Keystone admin user password:
|
||||
|
||||
::
|
||||
|
||||
openstack user set --password newP@ssw0rd admin
|
||||
|
||||
#. Update the kube-system namespace's `registry-local-secret` secret:
|
||||
|
||||
::
|
||||
|
||||
kubectl -n kube-system create secret docker-registry registry-local-secret --docker-server=registry.local:9001 --docker-username=admin --docker-password=newP@ssw0rd -o yaml --dry-run=true > registry-local-secret-update.yaml
|
||||
kubectl -n kube-system replace secret registry-local-secret -f registry-local-secret-update.yaml
|
||||
|
||||
#. Update the kube-system namespace's `default-registry-key` secret:
|
||||
|
||||
::
|
||||
|
||||
kubectl -n kube-system create secret docker-registry default-registry-key --docker-server=registry.local:9001 --docker-username=admin --docker-password=newP@ssw0rd -o yaml --dry-run=true > default-registry-key-update.yaml
|
||||
kubectl -n kube-system replace secret default-registry-key -f default-registry-key-update.yaml
|
||||
|
||||
In a distributed cloud deployment, the registry secrets must also be updated on
|
||||
all subclouds in the system.
|
||||
|
||||
|
||||
|
|
@ -1,181 +0,0 @@
|
|||
==================
|
||||
R4.0 Release Notes
|
||||
==================
|
||||
|
||||
.. contents::
|
||||
:local:
|
||||
:depth: 1
|
||||
|
||||
---------
|
||||
ISO image
|
||||
---------
|
||||
|
||||
The pre-built ISO and Docker images for StarlingX release 4.0 are located at the
|
||||
`StarlingX mirror
|
||||
<https://mirror.starlingx.windriver.com/mirror/starlingx/release/4.0.1/centos/flock/outputs/>`_.
|
||||
|
||||
------
|
||||
Branch
|
||||
------
|
||||
|
||||
The source code for StarlingX release 4.0 is available in the r/stx.4.0
|
||||
branch in the `StarlingX repositories <https://opendev.org/starlingx>`_.
|
||||
|
||||
----------
|
||||
Deployment
|
||||
----------
|
||||
|
||||
A system install is required to deploy StarlingX release 4.0. There is no
|
||||
upgrade path from previous StarlingX releases. For detailed instructions, see
|
||||
the `Installation guides for R5.0 and older releases
|
||||
<https://docs.starlingx.io/r/stx.5.0/deploy_install_guides/index.html>`_.
|
||||
|
||||
-----------------------------
|
||||
New features and enhancements
|
||||
-----------------------------
|
||||
|
||||
The list below provides a detailed list of new features and links to the
|
||||
associated user guides (if applicable).
|
||||
|
||||
* Intel FPGA support for Kubernetes
|
||||
|
||||
The Intel N3000 FPGA Programmable Acceleration Card is now supported
|
||||
in StarlingX, including support for orchestrating updates to the
|
||||
card's firmware.
|
||||
|
||||
Guide: :doc:`Host FPGA Configuration for the Intel N3000 FPGA Programmable
|
||||
Acceleration Card </archive/configuration/intel_n3000_fpga>`
|
||||
|
||||
* Kata Containers
|
||||
|
||||
Workloads can now be deployed in Kata Containers by StarlingX, which
|
||||
provides a higher degree of isolation than workloads in generic containers.
|
||||
|
||||
Guide: :doc:`How to run Kata Containers with Kubernetes on StarlingX
|
||||
</operations/kata_container>`
|
||||
|
||||
* Active Directory Integration for Kubernetes APIs
|
||||
|
||||
StarlingX administrators can now deploy an optional system application
|
||||
to support using Windows Active Directory for authentication of the
|
||||
Kubernetes API.
|
||||
|
||||
Guide: :doc:`Authenticate Kubernetes Users with Windows Active Directory
|
||||
Server </archive/configuration/k8s_auth_winactivedir>`
|
||||
|
||||
* Certificate Manager Integration
|
||||
|
||||
StarlingX now provides a Certification Manager to enable automated
|
||||
certificate issuance, monitor certificate expiration dates, and configure
|
||||
an auto-renew process.
|
||||
|
||||
Guide: :doc:`Enable secure HTTPS access and manage certificates </archive/configuration/cert_config>`
|
||||
|
||||
* Time-Sensitive Networking (TSN) in Kata Containers
|
||||
|
||||
Time-Sensitive Networking has been enabled for workloads running in Kata
|
||||
Containers.
|
||||
|
||||
Guide: :doc:`Enable TSN in Kata Containers
|
||||
</developer_resources/stx_tsn_in_kata>`
|
||||
|
||||
* Upversion OpenStack services
|
||||
|
||||
The built-in OpenStack services, including Keystone, Horizon, Barbican, and
|
||||
others, have been updated to Train. For more details, consult the
|
||||
`OpenStack documentation for Train <https://docs.openstack.org/train/>`_.
|
||||
|
||||
* Upversion OpenStack application
|
||||
|
||||
The built-in OpenStack application has been updated to Ussuri. For
|
||||
more details, consult the `OpenStack documentation for Ussuri
|
||||
<https://docs.openstack.org/ussuri/>`_.
|
||||
|
||||
* Kubernetes support in backup and restore functionality
|
||||
|
||||
Back up and restore is now available for workloads running in
|
||||
Kubernetes pods.
|
||||
|
||||
Guide: :doc:`Backup and restore your deployment </developer_resources/backup_restore>`
|
||||
|
||||
* Kubernetes manual upgrade capability
|
||||
|
||||
StarlingX now has the capability of updating the Kubernetes images
|
||||
installed on the platform.
|
||||
|
||||
Guide: :doc:`Upgrade your Kubernetes version </archive/configuration/k8s_upgrade>`
|
||||
|
||||
* Redfish virtual media support
|
||||
|
||||
StarlingX now supports the Redfish Virtual Media Controller to
|
||||
support a secure BMC based ISO image boot.
|
||||
|
||||
* Kernel rebase to 4.18
|
||||
|
||||
The Linux kernel used by StarlingX has been upgraded to version 4.18 as
|
||||
provided in CentOS 8.
|
||||
|
||||
* Upversion Kubernetes components
|
||||
|
||||
Kubernetes was upversioned to v1.18.1, Calico was upversioned to v3.12, and
|
||||
Helm was upversioned to v3.
|
||||
|
||||
* Layered build
|
||||
|
||||
StarlingX builds have been monolithic and time consuming. The new Layered
|
||||
build system decomposes the system into separate layers that can be built
|
||||
independently. Both Layered and Monolithic builds are supported in this
|
||||
release.
|
||||
|
||||
Guides: :doc:`Layered build reference (overview) </developer_resources/Layered_Build>`
|
||||
and :doc:`Layered build guide (step by step instructions) </developer_resources/layered_build_guide>`
|
||||
|
||||
* Open Platform Communications Unified Architecture (OPC UA) support
|
||||
|
||||
OPC UA is a data exchange standard for industrial communication in the
|
||||
Industrial IoT (IIoT) category. StarlingX now supports OPC UA.
|
||||
|
||||
Guide: :doc:`How to enable OPC UA on StarlingX </developer_resources/stx_opcua>`
|
||||
|
||||
----------
|
||||
Bug status
|
||||
----------
|
||||
|
||||
**********
|
||||
Fixed bugs
|
||||
**********
|
||||
|
||||
This release provides fixes for a number of defects. Refer to the StarlingX bug
|
||||
database to review the `R4.0 fixed defects
|
||||
<https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=FIXRELEASED&field.tag=stx.4.0>`_.
|
||||
|
||||
*********
|
||||
Open bugs
|
||||
*********
|
||||
|
||||
Use the StarlingX bug database to review `R4.0 open bugs
|
||||
<https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=stx.4.0+not-yet-in-r-stx40&field.tags_combinator=ALL&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search>`_.
|
||||
|
||||
At the time of release, the following R4.0 bugs were open:
|
||||
|
||||
* `1890350 <https://bugs.launchpad.net/starlingx/+bug/1890350>`_
|
||||
* `1887589 <https://bugs.launchpad.net/starlingx/+bug/1887589>`_
|
||||
* `1870999 <https://bugs.launchpad.net/starlingx/+bug/1870999>`_
|
||||
* `1879018 <https://bugs.launchpad.net/starlingx/+bug/1879018>`_
|
||||
* `1881915 <https://bugs.launchpad.net/starlingx/+bug/1881915>`_
|
||||
* `1886429 <https://bugs.launchpad.net/starlingx/+bug/1886429>`_
|
||||
* `1888546 <https://bugs.launchpad.net/starlingx/+bug/1888546>`_
|
||||
|
||||
-----------------
|
||||
Known limitations
|
||||
-----------------
|
||||
|
||||
The following are known limitations in this release. Workarounds
|
||||
are suggested where applicable. Note that these limitations are considered
|
||||
temporary and will likely be resolved in a future release.
|
||||
|
||||
* `1887589 <https://bugs.launchpad.net/starlingx/+bug/1887589>`_ Creating a
|
||||
new instance with Horizon fails.
|
||||
|
||||
|
||||
|
||||
|
|
@ -1,70 +0,0 @@
|
|||
====================
|
||||
R5.0.1 Release Notes
|
||||
====================
|
||||
|
||||
.. contents::
|
||||
:local:
|
||||
:depth: 1
|
||||
|
||||
---------
|
||||
ISO image
|
||||
---------
|
||||
|
||||
The pre-built ISO and Docker images for StarlingX release 5.0.1 are located at
|
||||
the `StarlingX mirror
|
||||
<https://mirror.starlingx.windriver.com/mirror/starlingx/release/5.0.1/centos/flock/outputs/>`_.
|
||||
|
||||
------
|
||||
Branch
|
||||
------
|
||||
|
||||
The source code for StarlingX release 5.0.1 is available in the r/stx.5.0.1
|
||||
branch in the `StarlingX repositories <https://opendev.org/starlingx>`_.
|
||||
|
||||
----------
|
||||
Deployment
|
||||
----------
|
||||
|
||||
A system install is required to deploy StarlingX release 5.0.1. There is no
|
||||
upgrade path from previous StarlingX releases.
|
||||
|
||||
Use the `R5.0 Installation Guides <https://docs.starlingx.io/r/stx.5.0/deploy_install_guides/r5_release/index-install-r5-ca4053cb3ab9.html>`
|
||||
to install R5.0.1.
|
||||
|
||||
-----------------------------
|
||||
New features and enhancements
|
||||
-----------------------------
|
||||
|
||||
None.
|
||||
|
||||
|
||||
----------
|
||||
Bug status
|
||||
----------
|
||||
|
||||
**********
|
||||
Fixed bugs
|
||||
**********
|
||||
|
||||
This release provides fixes for the following bug.
|
||||
|
||||
* `1940696 <https://bugs.launchpad.net/starlingx/+bug/1940696>`_ Bootstrap of
|
||||
controller-0 failing due to missing tag in gcr.io registry
|
||||
|
||||
|
||||
-----------------
|
||||
Known limitations
|
||||
-----------------
|
||||
|
||||
The following are known limitations in this release. Workarounds
|
||||
are suggested where applicable. Note that these limitations are considered
|
||||
temporary and will likely be resolved in a future release.
|
||||
|
||||
* `1925668 <https://bugs.launchpad.net/starlingx/+bug/1925668>`_ Bootstrap
|
||||
replay fails when changing mgmt subnet
|
||||
|
||||
This item is fixed in the master branch.
|
||||
|
||||
Running the bootstrap playbook will fail if it is re-run after first running
|
||||
it with one management subnet (default or specified) and then specifying a new
|
||||
management subnet.
|
||||
|
|
@ -1,165 +0,0 @@
|
|||
==================
|
||||
R5.0 Release Notes
|
||||
==================
|
||||
|
||||
.. contents::
|
||||
:local:
|
||||
:depth: 1
|
||||
|
||||
---------
|
||||
ISO image
|
||||
---------
|
||||
|
||||
The pre-built ISO and Docker images for StarlingX release 5.0 are located at
|
||||
the `StarlingX mirror
|
||||
<https://mirror.starlingx.windriver.com/mirror/starlingx/release/5.0.0/centos/flock/outputs/>`_.
|
||||
|
||||
------
|
||||
Branch
|
||||
------
|
||||
|
||||
The source code for StarlingX release 5.0 is available in the r/stx.5.0
|
||||
branch in the `StarlingX repositories <https://opendev.org/starlingx>`_.
|
||||
|
||||
----------
|
||||
Deployment
|
||||
----------
|
||||
|
||||
A system install is required to deploy StarlingX release 5.0. There is no
|
||||
upgrade path from previous StarlingX releases. For detailed instructions, see
|
||||
the `R5.0 Installation Guides <https://docs.starlingx.io/r/stx.5.0/deploy_install_guides/r5_release/index-install-r5-ca4053cb3ab9.html>`.
|
||||
|
||||
-----------------------------
|
||||
New features and enhancements
|
||||
-----------------------------
|
||||
|
||||
The list below provides a detailed list of new features and links to the
|
||||
associated user guides (if applicable).
|
||||
|
||||
* Rook / Ceph
|
||||
|
||||
A new storage backend rook-ceph to provide storage service to StarlingX.
|
||||
|
||||
Guide: `Install StarlingX Kubernetes on Bare Metal Standard with Rook
|
||||
Storage <https://docs.starlingx.io/r/stx.5.0/deploy_install_guides/r5_release/bare_metal/rook_storage.html>`
|
||||
|
||||
* FPGA image update orchestration for distributed cloud
|
||||
|
||||
Added support for orchestrating updates to the Intel N3000 FPGA Programmable
|
||||
Acceleration Card across the subclouds in a distributed cloud configuration.
|
||||
|
||||
Guide: :ref:`Device Image Update
|
||||
Orchestration <device-image-update-orchestration>`
|
||||
|
||||
* Automatic certificate renewal for DC admin endpoints
|
||||
|
||||
In Distributed Cloud configurations, ``admin`` endpoints for the platform
|
||||
keystone services (e.g. Configuration API, DC Manager API, etc.) on
|
||||
systemController and subclouds are HTTPS with internally generated
|
||||
certificates. This feature adds support for automatically renewing the
|
||||
certificates associated with these ``admin`` endpoints.
|
||||
|
||||
Guide: :ref:`Certificate Management for Admin REST API Endpoints
|
||||
<certificate-management-for-admin-rest-api-endpoints>`
|
||||
|
||||
* Vault integration for secret management support
|
||||
|
||||
StarlingX now integrates the open source Vault secret management into the
|
||||
StarlingX solution. The StarlingX integration of Vault uses open source Raft
|
||||
(PVC-based) as its storage backend. For more information, refer to:
|
||||
https://www.vaultproject.io/
|
||||
|
||||
The following services are supported:
|
||||
|
||||
* Encryption-as-a-service / Secret Management: Vault provides data encryption
|
||||
for applications and is used to store and access secrets.
|
||||
* Vault-manager: The Vault-manager pod handles the initialization of Vault,
|
||||
configuring Transport Layer Security (TLS) for all Vault communication that
|
||||
provides the ability to automatically unseal Vault pods in deployments
|
||||
where an external autounseal provider is not available.
|
||||
|
||||
Guide: :ref:`Vault Overview <security-vault-overview>`
|
||||
|
||||
* Support for container image signature validation
|
||||
|
||||
StarlingX supports image security policies using the Portieris admission
|
||||
controller. Portieris uses a Kubernetes Mutating Admission Webhook to modify
|
||||
Kubernetes resources such as pods, deployments, and others, at the point of
|
||||
creation, to ensure that Kubernetes runs only policy compliant images; for
|
||||
example, only signed images. The StarlingX integration of Portieris is
|
||||
integrated with cert-manager and works with external registries, with an
|
||||
associated Notary server for holding images’ trust data.
|
||||
|
||||
Guide: :ref:`Portieris Overview <portieris-overview>`
|
||||
|
||||
* Edgeworker for industrial deployments
|
||||
|
||||
``EdgeWorker`` is a new personality of nodes. Edgeworker nodes are typically
|
||||
small systems running dedicated workloads with Ubuntu as its operating system.
|
||||
They usually do not meet worker nodes' minimum requirements but now they can
|
||||
be managed by StarlingX.
|
||||
|
||||
Guide: :ref:`Deploy Edgeworker Nodes <deploy-edgeworker-nodes>`
|
||||
|
||||
* SNMP v3 support
|
||||
|
||||
StarlingX has updated its SNMP solution to be a containerized SNMP solution,
|
||||
delivered as an optional system application. Net-SNMP is still used as the
|
||||
underlying SNMP Agent. SNMP is configured through helm-overrides of the SNMP
|
||||
system application. The SNMP system application now supports both SNMPv2c
|
||||
and SNMPv3.
|
||||
|
||||
Guide: :ref:`SNMP Overview <snmp-overview>`
|
||||
|
||||
* Distributed cloud scaling
|
||||
|
||||
The distributed cloud deployment now supports up to 200 |AIO-SX| subclouds.
|
||||
|
||||
Guide: :ref:`Distributed Cloud Architecture <distributed-cloud-architecture>`
|
||||
|
||||
* Secure Device Onboard (SDO)
|
||||
|
||||
|SDO| is open source software that automates the “onboard” process, which
|
||||
occurs when an SDO device establishes the first trusted connection with a
|
||||
device management service. This release adds support for the SDO Rendezvous
|
||||
(RV) service.
|
||||
|
||||
Guide: :doc:`Enable SDO Rendezvous Service </developer_resources/stx_sdo_rv>`
|
||||
|
||||
* Hardware enablement
|
||||
|
||||
Added support for Intel Ice Lake CPU, Intel Mt. Bryce eASIC (Pomona Lake),
|
||||
and Intel Columbiaville NIC.
|
||||
|
||||
Guides: :ref:`Configuring VF Interfaces Rate Limiting Using the CLI
|
||||
<configuring-vf-interfaces-rate-limiting-using-cli>` and :ref:`Verified
|
||||
Commercial Hardware <verified-commercial-hardware>`
|
||||
|
||||
|
||||
----------
|
||||
Bug status
|
||||
----------
|
||||
|
||||
**********
|
||||
Fixed bugs
|
||||
**********
|
||||
|
||||
This release provides fixes for a number of defects. Refer to the StarlingX bug
|
||||
database to review the `R5.0 fixed defects
|
||||
<https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=FIXRELEASED&field.tag=stx.5.0>`_.
|
||||
|
||||
|
||||
-----------------
|
||||
Known limitations
|
||||
-----------------
|
||||
|
||||
The following are known limitations in this release. Workarounds
|
||||
are suggested where applicable. Note that these limitations are considered
|
||||
temporary and will likely be resolved in a future release.
|
||||
|
||||
* `1925668 <https://bugs.launchpad.net/starlingx/+bug/1925668>`_ This item is
|
||||
fixed in the master branch.
|
||||
|
||||
Running the bootstrap playbook will fail if it is re-run after first running
|
||||
it with one management subnet (default or specified) and then specifying a new
|
||||
management subnet.
|
||||
|
|
@ -1,235 +0,0 @@
|
|||
.. _r6-0-release-notes-bc72d0b961e7:
|
||||
|
||||
==================
|
||||
R6.0 Release Notes
|
||||
==================
|
||||
|
||||
.. contents::
|
||||
:local:
|
||||
:depth: 1
|
||||
|
||||
---------
|
||||
ISO image
|
||||
---------
|
||||
|
||||
The pre-built ISO and Docker images for StarlingX release 6.0 are located at
|
||||
the `StarlingX mirror
|
||||
<https://mirror.starlingx.windriver.com/mirror/starlingx/release/6.0.0/centos/flock/outputs/>`_.
|
||||
|
||||
------
|
||||
Branch
|
||||
------
|
||||
|
||||
The source code for StarlingX release 6.0 is available in the r/stx.6.0
|
||||
branch in the `StarlingX repositories <https://opendev.org/starlingx>`_.
|
||||
|
||||
----------
|
||||
Deployment
|
||||
----------
|
||||
|
||||
A system install is required to deploy StarlingX release 6.0. There is no
|
||||
upgrade path from previous StarlingX releases. For detailed instructions, see
|
||||
the `Installation Guide <https://docs.starlingx.io/r/stx.6.0/deploy_install_guides/index-install-e083ca818006.html>`_.
|
||||
|
||||
-----------------------------
|
||||
New features and enhancements
|
||||
-----------------------------
|
||||
|
||||
The list below provides a detailed list of new features and links to the
|
||||
associated user guides (if applicable).
|
||||
|
||||
|
||||
* Kernel Upversion to 5.10
|
||||
|
||||
|prod-long| now supports kernel version 5.10 to include |VRF| and the user
|
||||
space tooling to configure the routing and forwarding interfaces.
|
||||
|
||||
Guide: https://www.kernel.org/doc/Documentation/networking/vrf.txt
|
||||
|
||||
* Platform Certificates Managed by Cert-Manager
|
||||
|
||||
Platform services can now use cert-manager to simplify the management
|
||||
(e.g. auto-renewals) of the following Platform certificates:
|
||||
|
||||
* RESTAPI /GUI certificate
|
||||
* registry.local certificate
|
||||
* OIDC/DEX certificate
|
||||
|
||||
Guides:
|
||||
|
||||
* :ref:`Create a local CA Issuer <starlingx-rest-api-applications-and-the-web-admin-server-cert-9196c5794834>`
|
||||
|
||||
* :ref:`Configure REST API Applications and Web Administration Server Certificate <configure-rest-api-applications-and-web-administration-server-certificates-after-installation-6816457ab95f>`
|
||||
|
||||
* :ref:`Configure Docker Registry Certificate <configure-docker-registry-certificate-after-installation-c519edbfe90a>`
|
||||
|
||||
* :ref:`Set up OIDC Auth Applications <configure-oidc-auth-applications>`
|
||||
|
||||
* :ref:`OIDC Client Dex Server Certificates <oidc-client-dex-server-certificates-dc174462d51a>`
|
||||
|
||||
* Management of Kubernetes Root CA Certificate
|
||||
|
||||
You can update Kubernetes Root |CA| certificate on a running system, with
|
||||
either an uploaded certificate or an auto-generated certificate.
|
||||
Orchestration is also provided for both Cloud and Distributed Cloud.
|
||||
|
||||
Guides:
|
||||
|
||||
* :ref:`Manual Kubernetes Root CA Certificate Update <manual-kubernetes-root-ca-certificate-update-8e9df2cd7fb9>`
|
||||
|
||||
* :ref:`Kubernetes Root CA Certificate Update Cloud Orchestration <kubernetes-root-ca-certificate-update-cloud-orchestration-a627f9d02d6d>`
|
||||
|
||||
• Auditd support
|
||||
|
||||
The Linux Auditing System helps system administrators track security
|
||||
violation events based on preconfigured audit rules. The events are
|
||||
recorded in a log file and the information in the log entries helps to
|
||||
detect misuse or unauthorized activities.
|
||||
|
||||
The Linux Audit daemon, **auditd**, is the main component of the Linux
|
||||
Auditing System, and is responsible for writing the audit logs.
|
||||
|
||||
Guide: :ref:`Linux Auditing System <auditd-support-339a51d8ce16>`
|
||||
|
||||
* Alarm Support for Expiring and Expired Certificates
|
||||
|
||||
Expired certificates may prevent the proper operation of platform and
|
||||
applications running on the platform. In order to avoid expired
|
||||
certificates, |prod-long| generates alarms for certificates that are within
|
||||
30 days (default) of expiry or have already expired.
|
||||
|
||||
Guide: :ref:`Expiring-Soon and Expired Certificate Alarms <alarm-expiring-soon-and-expired-certificates-baf5b8f73009>`
|
||||
|
||||
* Make a separate CA for Kubernetes and etcd
|
||||
|
||||
This is the etcd Root |CA| certificate. It signs etcd server and client
|
||||
certificates, and ``kube-apiserver`` etcd client certificate. This is also
|
||||
the |CA| certificate used to verify various server and client certificates
|
||||
signed by etcd Root |CA| certificate. You can now provide a separate Root
|
||||
|CA| for Kubernetes and etcd.
|
||||
|
||||
Guide: :ref:`Etcd Certificates <etcd-certificates-c1fc943e4a9c>`
|
||||
|
||||
* Support for stx-ceph-manager
|
||||
|
||||
* Ceph upversion from Mimic to Nautilus
|
||||
|
||||
Upgraded the supported Ceph version to Nautilus (14.2.22).
|
||||
|
||||
Guide: N/A
|
||||
|
||||
* Firmware Update for BMC and Retimer
|
||||
|
||||
The firmware for Intel MAX 10 |BMC| and C827 retimer can now be updated
|
||||
using the :command:`device-image-upload` command. A new option
|
||||
``--retimer-included <true/false>`` has been added where a boolean
|
||||
indicates whether the |BMC| firmware includes a retimer firmware. A new
|
||||
parameter ``--bmc <true/false>`` is added to specify the functional |BMC|
|
||||
image (optional).
|
||||
|
||||
Guide: :ref:`Update an N3000 FPGA Image <updating-an-intel-n3000-fpga-image>`
|
||||
|
||||
* AIO-SX to AIO-DX Migration
|
||||
|
||||
You can migrate an |AIO-SX| subcloud to an |AIO-DX| subcloud without
|
||||
reinstallation. This operation involves updating the system mode, adding
|
||||
the OAM unit IP addresses of each controller, and installing the second
|
||||
controller.
|
||||
|
||||
Guide: :ref:`Migrate an AIO-SX to an AIO-DX Subcloud <migrate-an-aiosx-subcloud-to-an-aiodx-subcloud>`
|
||||
|
||||
* Distributed Cloud Subcloud Rehoming
|
||||
|
||||
You can move subclouds from one Distributed Cloud system to another while
|
||||
the current System Controller is reinstalled in a disaster recovery
|
||||
scenario. Another use case for the subcloud rehoming process is to add
|
||||
already deployed subclouds when the subclouds from multiple System
|
||||
Controllers are being consolidated into a single System Controller, because
|
||||
the rehoming playbook does not work with freshly installed/bootstrapped
|
||||
subclouds.
|
||||
|
||||
Guide: :ref:`Rehome a Subcloud <rehoming-a-subcloud>`
|
||||
|
||||
* Container Component Upversion
|
||||
|
||||
The default version of a fresh install for Kubernetes is 1.21.8, while for
|
||||
an upgrade from 5.0, it will be 1.18.1. You will need to upgrade
|
||||
Kubernetes to each version up to 1.21.8 in order to be ready to upgrade to
|
||||
the next version of |prod|.
|
||||
|
||||
Guide: :ref:`Manual Kubernetes Version Upgrade <manual-kubernetes-components-upgrade>`
|
||||
|
||||
* Use pf-bb-config to configure Intel FPGA N3000
|
||||
|
||||
The **pf-bb-config** package is used to statically configure the baseband
|
||||
device within N3000 devices.
|
||||
|
||||
Guide: :ref:`N3000 FPGA Overview <n3000-overview>`
|
||||
|
||||
* AIO-SX: Support for pci device/NIC replacement without host reinstall
|
||||
|
||||
For replacement of N3000 or ACC100 device on a host, without requiring a
|
||||
host or system (in case of |AIO-SX|) re-install and re-configuration, in
|
||||
the case of the replaced device having **different vendor** or **device
|
||||
ID** information, see :ref:`N3000 and ACC100 replacement with different vendor or device-id <fec-replacement-with-different-vendor-or-device-id-b1ab1440e15f>`.
|
||||
|
||||
For the replacement of a N3000 or ACC100 device on a host, without requiring
|
||||
a host or system (in case of |AIO-SX|) re-install and re-configuration, in
|
||||
the case of the replaced device having the **same vendor** and **device
|
||||
ID** information, see :ref:`N3000 and ACC100 replacement with the same vendor and device-id <n3000-and-acc100-replacement-with-the-same-vendor-and-device-id-cccabcdc5d43>`.
|
||||
|
||||
For the replacement of a NIC on a host, without requiring a host or system
|
||||
(in case of |AIO-SX|) re-install and re-configuration, in the case of the
|
||||
replaced NIC having the same vendor or device ID information, see
|
||||
:ref:`NIC replacement with the same vendor and device-id <nic-replacement-with-the-same-vendor-and-device-id-32942b7b05e5>`.
|
||||
|
||||
For the replacement of a NIC on a host, without requiring a host or system
|
||||
(in case of |AIO-SX|) re-install and re-configuration, in the case of the
|
||||
replaced NIC having different vendor or device ID information, see
|
||||
:ref:`NIC replacement with a different vendor or device-id <replace-a-nic-with-a-different-vendor-or-device-id-b406c1c190a9>`.
|
||||
|
||||
• Allow admin password change without controller host lock
|
||||
|
||||
In a subcloud, if the |CLI| command returns an authentication after you
|
||||
source the script ``/etc/platform/openrc``, you can verify the password on
|
||||
the subcloud by using the :command:`env \| grep OS\_PASSWORD` command. If it
|
||||
returns the old password, you will need to run the :command:`keyring set CGCS admin`
|
||||
command and provide the new admin password.
|
||||
|
||||
* Subcloud Deployment with Local Installation
|
||||
|
||||
Subcloud Install is enhanced to support a local install option for Redfish
|
||||
supported servers that are “Prestaged” with a valid install bundle.
|
||||
|
||||
Prestaging can be done manually or automated by building a
|
||||
self-installing “Prestaging ISO” image using the ``gen-prestaged-is.sh`` tool.
|
||||
This tool accepts parameters that include install bundle components and
|
||||
produces a “Prestaging ISO”.
|
||||
|
||||
Guide: :ref:`Subcloud Deployment with Local Installation <subcloud-deployment-with-local-installation-4982449058d5>`
|
||||
|
||||
|
||||
----------
|
||||
Bug status
|
||||
----------
|
||||
|
||||
**********
|
||||
Fixed bugs
|
||||
**********
|
||||
|
||||
This release provides fixes for a number of defects. Refer to the StarlingX bug
|
||||
database to review the `R6.0 fixed defects
|
||||
<https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=FIXRELEASED&field.tag=stx.6.0>`_.
|
||||
|
||||
|
||||
-----------------
|
||||
Known limitations
|
||||
-----------------
|
||||
|
||||
The following are known limitations in this release. Workarounds
|
||||
are suggested where applicable. Note that these limitations are considered
|
||||
temporary and will likely be resolved in a future release.
|
||||
|
||||
* N/A
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
Loading…
Reference in New Issue