Release Notes #

SUSE CaaS Platform allows you to provision, manage, and scale container-based applications. SUSE offers an application development and hosting platform for containers that automates the tedious management tasks. This allows you to focus on development and writing apps that meet business goals.

The main benefits of SUSE CaaS Platform are:

SUSE CaaS Platform is backed by award-winning support from SUSE, an established technology leader with a proven history of delivering enterprise-quality support services.

The support for version SUSE CaaS Platform 2 ends with the release of version 3. We offer rolling updates allowing customers to upgrade the system via a maintenance update. When releasing version 3, SUSE will offer maintenance updates including packages enabling our customers to move to version 3 via a simple update.

For more information, check our Support Policy page https://www.suse.com/support/policy.html.

This section lists requirements that SUSE CaaS Platform has on its running environment and underlying hardware.

This SUSE product includes materials licensed to SUSE under the GNU General Public License (GPL). The GPL requires SUSE to provide the source code that corresponds to the GPL-licensed material. The source code is available for download at https://www.suse.com/download-linux/source-code.html.

Also, for up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code. Requests should be sent by e-mail to mailto:sle_source_request@suse.com or as otherwise instructed at https://www.suse.com/download-linux/source-code.html. SUSE may charge a reasonable fee to recover distribution costs.

To receive support, you need an appropriate subscription with SUSE. For more information, see https://www.suse.com/products/server/services-and-support/.

The following definitions apply:

For contracted customers and partners, SUSE CaaS Platform 2 is delivered with L3 support for all packages, except the following:

SUSE will only support the usage of original (that is, unchanged and un-recompiled) packages.

Over the life cycle of a SUSE Container as a Service Platform version, there may be updates to major Kubernetes upstream releases (and some minor releases also). However, the version provided in SUSE Container as a Service Platform will trail the upstream version by up to 6 months, to be able to provide additional QA.

Such version updates will be released as updates within the life of the product. This means there is no concept of overlap support between two versions. Only the latest maintenance update is supported.

The initial version of Kubernetes will be version 1.7.

This table summarizes the various limits which exist in our recent kernels and utilities (if related) for SUSE CaaS Platform 2.

SUSE CaaS Platform 2 exclusively supports the file system types Btrfs and OverlayFS. The root file system is a read-only Btrfs which enables transactional updates.

The following table lists supported and unsupported Btrfs features across multiple SUSE CaaS Platform versions.

* Btrfs is a copy-on-write file system. Instead of journaling changes before writing them in-place, it writes them to a new location and then links the new location in. Until the last write, the changes are not “committed”. Because of the nature of the file system, quotas are implemented based on subvolumes (qgroups).

The maximum file size above can be larger than the file system's actual size because of usage of sparse blocks. The numbers in the above table assume that the file systems are using 4 KiB block size. When using different block sizes, the results are different, but 4 KiB reflects the most common standard.

In this document: 1024 Bytes = 1 KiB; 1024 KiB = 1 MiB; 1024 MiB = 1 GiB; 1024 GiB = 1 TiB; 1024 TiB = 1 PiB; 1024 PiB = 1 EiB. See also http://physics.nist.gov/cuu/Units/binary.html.

For more information, also see: https://www.suse.com/products/caas-platform/technical-information/#FileSystem