SUSE Cloud 4
Release Notes #
These release notes are generic for all SUSE Cloud 4 components. Some parts may not apply to a particular component.
Documentation can be found in the docu language directories on the
media. Documentation (if installed) is available below the /usr/share/doc/
directory of an installed system. The latest documentation can also be found online at http://www.suse.com/documentation/cloud/.
1 SUSE Cloud #
Powered by OpenStack™, SUSE Cloud is an open source enterprise cloud computing platform that enables easy deployment and seamless management of an Infrastructure-as-a-Service (IaaS) private cloud.
2 Support Statement for SUSE Cloud #
To receive support, customers need an appropriate subscription with SUSE; for more information, see http://www.suse.com/products/server/services-and-support/.
3 Major Changes in SUSE Cloud 4 #
SUSE Cloud 4 is a major update to SUSE Cloud and comes with many new features, improvements and bug fixes. The following list highlights a selection of the major changes:
OpenStack has been updated to the 2014.1 (Icehouse) release (https://wiki.openstack.org/wiki/ReleaseNotes/Icehouse), and the deployment framework has been updated accordingly to support new features. On top of the new features that come by default with this new version, here are some notable features that have been added:
Multiple block storage backends, with different drivers if needed, can now be defined and used at the same time in Block Storage (Cinder).
The driver for the FUJITSU Storage ETERNUS DX series and the VMware VMDK driver have been added for Block Storage (Cinder).
Load-Balancing-as-a-Service (LBaaS) and Firewall-as-a-Service (FWaaS) are enabled for OpenStack Networking (Neutron).
The
openstackcommand line interface is distributed and can be used by the cloud users in replacement of the command line interfaces specific to each OpenStack component (such asnova,keystone,glance,cinder,neutron, etc.). It provides a unified and more user-friendly interface to interact with OpenStack.Newer versions of the APIs can be enabled: Compute (Nova) API v3 and Volume (Cinder) API v2. Note that Identity (Keystone) API v3 and Image (Glance) API v2 are also available.
Database-as-a-Service for OpenStack (Trove) is included as technology preview.
The OpenStack Integration Test Suite (Tempest) can be deployed through a Crowbar barclamp to validate the OpenStack deployment. This is provided for convenience purposes only and is not supported.
The OpenStack infrastructure can be deployed in a highly available way, to provide a higher Service Level Agreement (SLA). This covers the controller side of OpenStack, but doesn't cover the hypervisor nodes. This feature was already provided through a maintenance update to SUSE Cloud 3 and is fully integrated in SUSE Cloud 4.
The distributed storage system Ceph has been updated to the 0.80 (Firefly) release. It is not a technology preview anymore, and is now supported. The Ceph Object Gateway can also be deployed.
4 Technology Previews #
Technology previews are packages, stacks, or features delivered by SUSE. These features are not supported. They may be functionally incomplete, unstable or in other ways not suitable for production use. They are mainly included for customer convenience and give customers a chance to test new technologies within an enterprise environment.
Whether a technology preview will be moved to a fully supported package later, depends on customer and market feedback. A technology preview does not automatically result in support at a later point in time. Technology previews could be dropped at any time and SUSE is not committed to provide a technology preview later in the product cycle.
Please, give your SUSE representative feedback, including your experience and use case.
SUSE Cloud 4 ships with the following technology previews:
Database-as-a-Service for OpenStack (Trove), and the respective Crowbar barclamp for deploying it.
EqualLogic driver for Cinder.
MongoDB, as database for Ceilometer.
5 Upgrading to SUSE Cloud 4 #
Upgrading to SUSE Cloud 4 is supported from SUSE Cloud 3, with the latest updates applied. If running a previous version, please first upgrade to SUSE Cloud 3. If running without the updates, please first apply them.
The upgrade process is a multi-step process that is semi-automated, thanks to the
suse-cloud-upgrade utility that will guide you through the various
steps. As the OpenStack infrastructure will be turned off for the upgrade, it is
important to suspend all running instances prior to the upgrade so they can be properly
restored after the upgrade. It is also highly recommended to perform a backup of both
the Administration Server and the OpenStack data.
The complete upgrade process is documented in the Deployment Guide, which can be found online at http://www.suse.com/documentation/cloud/.
6 Documentation and Other Information #
Read the READMEs on the CDs.
Get the detailed changelog information about a particular package from the RPM (with filename <FILENAME>):
rpm --changelog -qp <FILENAME>.rpmCheck the
ChangeLogfile in the top level of CD1 for a chronological log of all changes made to the updated packages.Find more information in the
docudirectory of CD1 of the SUSE Cloud 4 CDs. This directory includes PDF versions of the SUSE Cloud documentation.http://www.suse.com/documentation/cloud/ contains additional or updated documentation for SUSE Cloud.
Visit http://www.suse.com/products/ for the latest product news from SUSE and http://www.suse.com/download-linux/source-code.html for additional information on the source code of SUSE Linux Enterprise products.
7 Known Issues #
Upgrade from a SUSE Cloud 3 deployment with HA is not functional at release time. This will be addressed with an online update.
No pre-built image for Heat or Trove are shipped with SUSE Cloud; cloud administrators are responsible for creating such images.
The
trove updatecommand fails with aHTTP 404error. This will be addressed with an online update.No 32-bit support; currently x86_64 architecture is required for all components.
Live migration of instances only work between homogeneous compute nodes: the nodes need to have the same CPU features.
Removal of barclamps from a node do not necessarily shut down associated services or remove associated packages. This means that you may well run into problem if moving barclamp roles from one node to another. Manual remediation may be required in these cases.
8 How to Obtain Source Code #
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 http://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 http://www.suse.com/download-linux/source-code.html. SUSE may charge a reasonable fee to recover distribution costs.
9 Legal Notices #
SUSE makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses. Please refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software. SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2012, 2013, 2014 SUSE LLC. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
SUSE has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.suse.com/company/legal/ and one or more additional patents or pending patent applications in the U.S. and other countries.
For SUSE trademarks, see SUSE Trademark and Service Mark list (http://www.suse.com/company/legal/). All third-party trademarks are the property of their respective owners.