Red Hat Enterprise Linux OpenStack Platform 6 Release Notes

OpenStack Documentat ion Team

Red Hat Enterprise Linux OpenStackPlatform 6Release Notes

Release details for Red Hat Enterprise Linux OpenStack Plat form

Red Hat Enterprise Linux OpenStack Plat form 6 Release Notes

Release details for Red Hat Enterprise Linux OpenStack Plat form

OpenStack Documentation TeamRed Hat Customer Content [email protected]

Legal Notice

Copyright © 2015 Red Hat, Inc.

This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0Unported License. If you distribute this document, o r a modified version o f it, you must provideattribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all RedHat trademarks must be removed.

Red Hat, as the licensor o f this document, waives the right to enforce, and agrees not to assert,Section 4d o f CC-BY-SA to the fullest extent permitted by applicable law.

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the InfinityLogo, and RHCE are trademarks o f Red Hat, Inc., registered in the United States and o thercountries.

Linux ® is the registered trademark o f Linus Torvalds in the United States and o ther countries.

Java ® is a registered trademark o f Oracle and/or its affiliates.

XFS ® is a trademark o f Silicon Graphics International Corp. or its subsidiaries in the UnitedStates and/or o ther countries.

MySQL ® is a registered trademark o f MySQL AB in the United States, the European Union andother countries.

Node.js ® is an o fficial trademark o f Joyent. Red Hat Software Collections is not fo rmallyrelated to or endorsed by the o fficial Joyent Node.js open source or commercial pro ject.

The OpenStack ® Word Mark and OpenStack Logo are either registered trademarks/servicemarks or trademarks/service marks o f the OpenStack Foundation, in the United States and o thercountries and are used with the OpenStack Foundation's permission. We are not affiliated with,endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.

All o ther trademarks are the property o f their respective owners.

AbstractThe Release Notes document the major features, enhancements, and known issues o f the RedHat Enterprise Linux OpenStack Platform 6 release.

http://creativecommons.org/licenses/by-sa/3.0/

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

Chapt er 1 . Product Int roduct ion1.1. Ab o ut this Release1.2. Req uirements1.3. Hyp erviso r Sup p o rt1.4. Co ntent Delivery Netwo rk (CDN) Channels1.5. Pro d uct Sup p o rt

Chapt er 2 . Release Informat ion2.1. Enhancements2.2. Techno lo g y Preview2.3. Release No tes2.4. Kno wn Issues

Chapt er 3. Upgrading

Revision Hist ory

223334

66

181920

2 3

2 4

T able of Cont ent s

1

Chapter 1. Product Introduction

Red Hat Enterprise Linux OpenStack Platform provides the foundation to build a private or publicInfrastructure-as-a-Service (IaaS) cloud on top of Red Hat Enterprise Linux. It offers a massivelyscalable, fault-tolerant platform for the development of cloud-enabled workloads.

The current Red Hat system is based on OpenStack Juno, and packaged so that available physicalhardware can be turned into a private, public, or hybrid cloud platform including:

Fully distributed object storage

Persistent block-level storage

Virtual-machine provisioning engine and image storage

Authentication and authorization mechanism

Integrated networking

Web browser-based GUI for both users and administration.

The Red Hat Enterprise Linux OpenStack Platform IaaS cloud is implemented by a collection ofinteracting services that control its computing, storage, and networking resources. The cloud ismanaged using a web-based interface which allows administrators to control, provision, andautomate OpenStack resources. Additionally, the OpenStack infrastructure is facilitated through anextensive API, which is also available to end users of the cloud.

1.1. About this Release

This release of Red Hat Enterprise Linux OpenStack Platform is based on the OpenStack "Juno"release. It includes additional features, known issues, and resolved issues specific to Red HatEnterprise Linux OpenStack Platform.

Only changes specific to Red Hat Enterprise Linux OpenStack Platform are included in this releasenotes document. The release notes for the OpenStack "Juno" release itself are available at thefollowing location:

OpenStack "Juno" Release Notes

https://wiki.openstack.org/wiki/ReleaseNotes/Juno

Red Hat Enterprise Linux OpenStack Platform uses components from other Red Hat products.Specific information pertaining to the support of these components is available at:

https://access.redhat.com/site/support/policy/updates/openstack/platform/

To evaluate Red Hat Enterprise Linux OpenStack Platform, sign up at:

http://www.redhat.com/openstack/.

Red Hat Ent erprise Linux OpenSt ack Plat form 6 Release Not es

2

https://wiki.openstack.org/wiki/ReleaseNotes/Juno

https://access.redhat.com/site/support/policy/updates/openstack/platform/

http://www.redhat.com/openstack/

Note

The Red Hat Enterprise Linux High Availability Add-On is available for Red Hat EnterpriseLinux OpenStack Platform use cases. See the following URL for more details on the add-on:http://www.redhat.com/products/enterprise-linux-add-ons/high-availability/. See the followingURL for details on the package versions to use in combination with Red Hat Enterprise LinuxOpenStack Platform: https://access.redhat.com/site/solutions/509783

1.2. Requirements

This version of Red Hat Enterprise Linux OpenStack Platform is supported on Red Hat EnterpriseLinux 7.

The Red Hat Enterprise Linux OpenStack Platform dashboard is a web-based interface that allowsyou to manage OpenStack resources and services. The dashboard for this release supports thelatest stable versions of the following web browsers:

Chrome

Firefox

Firefox ESR

Internet Explorer 11 and later (with Compatibility Mode disabled)

To view the entire documentation suite for Red Hat Enterprise Linux OpenStack Platform, see:

https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform

1.3. Hypervisor Support

Red Hat Enterprise Linux OpenStack Platform is only supported for use with the libvirt driver(using KVM as the hypervisor on Compute nodes) or the VMware vCenter hypervisor driver. Refer tohttps://access.redhat.com/knowledge/articles/744153 for more information regarding theconfiguration of the VMware vCenter driver.

Red Hat does not provide support for other Compute virtualization drivers such as the deprecatedVMware "direct-to-ESX" hypervisor, and non-KVM libvirt hypervisors.

1.4 . Content Delivery Network (CDN) Channels

This section discusses channel and repository settings required for deploying Red Hat EnterpriseLinux OpenStack Platform 6.

You can install Red Hat Enterprise Linux OpenStack Platform 6 through the Content Delivery Network(CDN). To do so, configure subscript ion-manager to use the correct channels.

Run the following command to enable a CDN channel:

# subscription-manager repos --enable=[reponame]

Run the following command to disable a CDN channel:

Chapt er 1 . Product Int roduct ion

3

http://www.redhat.com/products/enterprise-linux-add-ons/high-availability/

https://access.redhat.com/site/solutions/509783


https://access.redhat.com/knowledge/articles/744153

# subscription-manager repos --disable=[reponame]

Table 1.1. Required Channels

Channel Repository NameRed Hat Enterprise Linux 7 Server (RPMS) rhel-7-server-rpms

Red Hat Enterprise Linux 7 Server - RH Common(RPMs)

rhel-7-server-rh-common-rpms

Red Hat Enterprise Linux OpenStack Platform6.0 (RPMS)

rhel-7-server-openstack-6.0-rpms

Red Hat Enterprise Linux OpenStack PlatformInstaller 6.0 (RPMS)

rhel-7-server-openstack-6.0-installer-rpms

Red Hat Enterprise Linux OpenStack PlatformImages

rhel-7-server-openstack-6.0-files

Table 1.2. Opt ional Channels

Channel Repository NameRed Hat Enterprise Linux 7 Server - Optional rhel-7-server-optional-rpms

Disable Channels

The following table outlines the channels you must disable to ensure Red Hat Enterprise LinuxOpenStack Platform 6 functions correctly.

Table 1.3. Disable Channels

Channel Repository NameRed Hat CloudForms Management Engine "cf-me-*"

Red Hat CloudForms Tools for RHEL 6 "rhel-6-server-cf-*"

Red Hat Enterprise Virtualization "rhel-6-server-rhev*"

Red Hat Enterprise Linux 6 Server - ExtendedUpdate Support

"*-eus-rpms"

Warning

Some packages in the OpenStack software repositories conflict with packages provided by theExtra Packages for Enterprise Linux (EPEL) software repositories.

The use of Red Hat Enterprise Linux OpenStack Platform on systems with the EPEL softwarerepositories enabled is unsupported.

1.5. Product Support

Available resources include:

Customer Portal

The Red Hat Customer Portal offers a wide range of resources to help guide you throughplanning, deploying, and maintaining your OpenStack deployment. Facilities available via


4

the Customer Portal include:

Knowledge base articles and solutions.

Reference architectures.

Technical briefs.

Product documentation.

Support case management.

Access the Customer Portal at https://access.redhat.com/.

Mailing Lists

Red Hat provides these public mailing lists that are relevant to OpenStack users:

The rhsa-announce mailing list provides notification of the release of security fixes forall Red Hat products, including Red Hat Enterprise Linux OpenStack Platform.

Subscribe at https://www.redhat.com/mailman/listinfo/rhsa-announce.

The rhos-list mailing list provides a forum for discussions about installing, running,and using OpenStack on Red Hat based distributions.

Subscribe at https://www.redhat.com/mailman/listinfo/rhos-list.

Chapt er 1 . Product Int roduct ion

5

https://access.redhat.com/

https://www.redhat.com/mailman/listinfo/rhsa-announce

https://www.redhat.com/mailman/listinfo/rhos-list

Chapter 2. Release Information

These release notes highlight technology preview items, recommended practices, known issues, anddeprecated functionality to be taken into consideration when deploying this release of Red HatOpenStack.

Notes for updates released during the support lifecycle of this Red Hat OpenStack release will appearin the advisory text associated with each update or the Red Hat Enterprise Linux OpenStack PlatformTechnical Notes. This document is available from the following page:


2.1. Enhancements

BZ#106 2022

Copy-on-Write cloning for RBD-backed disks is now supported. As such, the Computeservice no longer needs to download a glance image to local disk and then copy it again toRBD. Rather, disks can now be efficiently created directly in the Ceph system, therebyspeeding up the creation of instances and, in the process, saving bandwidth and diskspace.

BZ#89 106 2

An admin user can now specify the Provider network type (the physical mechanism bywhich the virtual network is implemented), when creating a new network. Previously, thedashboard (horizon) defaulted to the 'Local' provider network type, and it was not possibleto select another type. The types 'Flat' , 'VLAN', 'GRE', and 'VXLAN', and 'Local' can now beselected in the new 'Provider Network Type' drop-down field. Depending on the type, asegmentation ID, tunnel ID, or physical network name must be additionally specified.

BZ#9 74 19 9

This feature exposes interactive web-based serial consoles to openstack VMs through awebsocket proxy. Generally used as a debugging tool (for example, VMs can be accessedeven if network configuration fails). A new service (websocket proxy) is now available thathandles websocket connections to the serial consoles of the VMs. The websocket proxy canbe deployed on a machine other than from the hypervisor.

BZ#9 78500

The host argument for the 'nova evacuate' command has been made optional. This meansthat the user no longer has to know the host destination, simplifying evacuation in the caseof an unplanned failure.

BZ#1029 871

This enhancement enables changes to a subnet's IP address allocation pool using theupdate command. Previously, administrators were unable to change the allocation poolrange for a subnet. If shrinking the pool, consideration must be given to IP addresses thathave already been allocated.

BZ#104 1054

Compute now automatically attempts a controlled shutdown for stop, rescue, and deleteinstance actions. If the controlled shutdown fails, Compute falls back to a forced shutdown.


6


https://bugzilla.redhat.com/1062022






BZ#104 1119

Previously, when a rescue was done on an instance, the image_base_ref in theinstance_meta_data was used. If this attribute was not populated, the custom image_ref wasused instead. This posed a problem where the custom image used might be corrupt,leading to errors; or too large, leading to timeouts. Also, if the base image was deleted, theimage ref on the instance_system_metadata would be invalid, leading to the rescueoperation failing. With this release, the user can now specify which image is to be used forrescue (this could be a default base image, or a custom image).

BZ#104 1121

With this feature, there is now a standardized data reporting mechanism for VM diagnostics.The historic diagnostics API had no formal specification. As a result, different virtualizationdrivers in Nova reported a different data set and made it difficult for VM diagnostics toconsume the data in a predictable manner. With this update, a new version of thediagnostic API was implemented in the version 3 API, and it now defines a standardized setof data items that virtualization drivers must use for reporting.

BZ#104 1376

OpenStack Compute now supports associating SR-IOV PCI devices with networks andbinding Neutron SR-IOV ports to them. PCI-Passthrough to SR-IOV virtual functionsprovide direct access to networking hardware specialized for virtualization with onephysical device supporting multiple virtual machines. By supporting SR-IOV devices,virtual machines can now employ SR-IOV hardware for networking.

BZ#104 19 6 6

Role-based access control (RBAC) checks are now supported for actions that interact withthe Compute service (nova); rules are defined in the /etc/openstack-dashboard/nova_policy.json configuration file. RBAC checks allow an administrator tofinely tune a user's access. For example, an administrator might allow end users to view thecomplete flavor listing.

BZ#104 19 6 7

Role-based access control (RBAC) checks are now supported for actions calling thenetwork service; rules are defined in the /etc/openstack-dashboard/neutron_policy.jsonconfiguration file. RBAC checks allow an administrator to finely tune a user's access. Forexample, an administrator might prevent end users from creating a subnet or changing afirewall policy.

BZ#104 19 71

An admin user can now evacuate a compute host using the dashboard. Two tabs nowprovide information for hypervisors: 'Hypervisor' and 'Compute Host' (Admin >Hypervisors). If a host is down, an 'Evacuate Host' action is now visible for it on theCompute Host tab (providing a modal window to perform the evacuation).

BZ#104 19 86

Support has been added for Block Storage volume backups in the dashboard. Users cannow create, view, delete, and restore volume backups. Note: This functionality is notdisplayed by default. To display volume-backup action items, update the /etc/openstack-dashboard/local_settings file with: OPENSTACK_CINDER_FEATURES = { 'enable_backup':True, } After updating the file, restart the httpd service with 'systemctl restart httpd'.

BZ#104 19 9 1

Chapt er 2 . Release Informat ion

7









There was a need to enable/disable Neutron related features based on the extension listfrom Neutron and remove Neutron related settings in local_settings.py. Neutron features likeLBaaS, FWaaS or VPNaaS are provided as extensions in Neutron. These features are nowenabled only when they are included in the extension list from Neutron. Also, changed thedefault settings of enable_lb/firewall/vpn to True. The default of these settings were set toFalse to avoid confusion to users because LB/FW/VPNaaS are optional features inNeutron. With this change, the corresponding features in Horizon are enabled dynamically,so it was reasonable to change the default to True. (FWaaS and VPNaaS are currently intechnical preview)

BZ#104 2023

An additional 'Action Log' tab is now available for specific instances (Project > Compute >Instances > [instance]). The tab lists all actions which have been carried out on thatspecific instance. For example, a tenant user can now use the 'Action Log' tab to see whocreated or shut down an instance.

BZ#104 2028

With this feature, there is now a widget for managing Glance metadata dictionary. Theadmin user is now able to edit properties of images directly under admin/images/edit.

BZ#104 2070

When using OpenStack Networking (neutron) with the dhcp_agent_scheduler extension, itis now possible to add and remove DHCP agents from networks using the dashboard. Thismakes it easier to manage the high availability of DHCP agents for OpenStack Networking.When logged in as admin and navigating to the Admin Networks panel, a new DHCPAgents column with the number of agents associated with each network is now visible.Clicking on a network name displays the network's details together with a new 'DHCPAgents' table where the admin can add and delete agents.

BZ#104 2113

Need for an interface to allow the user to assign domain role to users. The IdentityDashboard has been extended to support managing roles and users in different domains.

BZ#104 216 0

The Orchestration service now allows the user to update a stack in a FAILED state.Previously, failed stacks could only be deleted, not updated.

BZ#104 2271

The Telemetry service now uses the newer oslo.messaging library for RPC, therebyreplacing the deprecated openstack.common.rpc library.

BZ#104 239 6

This enhancement adds high availability for OpenStack Networking (neutron) virtualrouters. This was added due to the impact of virtual routers going down with a networknode; instances would lose external connectivity. Virtual routers can now be created withthe 'High availability' flag, if the administrator sets it as the default. As a result, routers willthen be created on multiple network nodes, with a designated single active instance node.The active node forwards traffic while the standbys monitor the master. In the event of failureimpacting the active node, one of the standby will take over as the new active node.

BZ#104 259 4


8









With this feature, you can now create and deploy Distributed Virtual Routers (DVR) usingthe Open vSwitch (OVS) infrastructure (DVR is currently in Technical Preview).

BZ#104 4 271

With this enhancement, Tenant networks can now be created that use the 'dnsmasq'process inside the DHCP agent to serve additional configuration to IPv6 DHCP clients,including addressing and support for IPv6 stateful subnets. Note that the default gateway isstill set by Router Advertisement messages sent by the L3 agent.

BZ#104 4 272

With this enhancement, Tenant networks can now be created that use the 'dnsmasq'process inside the DHCP agent to serve additional configuration to IPv6 DHCP clients,including support for IPv6 stateless subnets.

BZ#104 6 786

This enhancement allows the creation of Tenant networks that use the 'radvd' processwithin the L3 agent for Router Advertisement messages. As a result, instances are able touse Stateless Address Autoconfiguration (SLAAC) or DHCPv6 to configure their IPv6networking.

BZ#104 6 79 0

Extra Specs support for volume types has been added to the dashboard. An admin cannow add additional keys and values to volume types (GUI implementation of the 'cindertype-key' command). To view extra specs, select Admin> Volumes > Volume Types, andclick the type's 'View Extra Specs' action.

BZ#104 6 800

The code in the glance.store package used to store images into different store backendshas been pulled out into a self-standing library.

BZ#1053088

OpenStack Networking (neutron) has introduced new attributes for IPv6 networks: 'RouterAdvertisement' and 'Address Assignment', which enables IPv6 subnets to be configuredwith more granularity. If OpenStack Networking is in use and an IPv6 subnet is beingcreated, the dashboard now offers the following options in the 'IPv6 Address ConfigurationMode' drop-down field: --"SLAAC: Address discovered from Openstack Router" --"DHCPv6stateful: Address discovered from Openstack DHCP" --"DHCPv6 stateless: Addressdiscovered from Openstack Router and info from Openstack DHCP" Providing no optionmeans that addresses are configured manually or by a non-OpenStack system.

BZ#1056 389

The ability for an administrator to manage image metadata (custom properties) has beenadded to the dashboard. The admin user can now add, update, or delete image metadata(implements the 'glance image-update <imageID> --property <key>=<value>' command).To view or update an image's metadata, select Admin > System > Images, and click theimage's 'Update Metadata' action.

BZ#1057828

Role-based access control (RBAC) checks are now supported for actions that interact withthe Orchestration service (heat); rules are defined in the /etc/openstack-dashboard/heat_policy.json configuration file. RBAC checks allow an administrator tofinely tune a user's access. For example, an administrator might prevent end users from


9









changing a stack template.

BZ#1058578

Add support for Datastores to Horizon (Trove dashboard). Basic support for Trove hasbeen added to Horizon (Trove dashboard): Added Datastore type/version drop down inLaunch Instance Added Datastore type/version in Instance Details

BZ#106 2037

With this feature, there is now a separate Identity dashboard.

BZ#106 4 129

The Telemetry service now supports CSV download of daily usage data. In the dashboard,this feature is available through the 'Download CSV summary' button of the Admin >Overview panel. This button also becomes available after querying usage data.

BZ#107374 0

Keystone now supports domain specific identity backends. This allows for a singleKeystone instance to use multiple identity backends, such as centralized LDAP for normalusers and a Keystone specific SQL database for service users.

BZ#1076 305

MongoDB is still the preferred Telemetry back end for large installations; however, with thisrelease SQL now features improved read/write processing, which may be suitable for smallinstallations. This was accomplished through extensive refactoring of the database tables,query structuring, and optional parallelization of the ceilometer-collector service.

BZ#1076 307

The user can now sort tables by timestamp in the dashboard (a timestamp parser has beenadded). For example, in the Project > Compute > Overview window, the user can now sortinstances by 'Time since created'.

BZ#1076 309

Table filtering has been updated in the dashboard to use API query attributes. A drop-downbox and an input field for filtering have been added to tables for admin instances, adminimages, and project instances. For example, the admin instances table might be filtered for'Status=Active'.

BZ#10786 28

With this release, parameters in HOT templates can now be defined with the type "boolean".

BZ#108074 3

Code for the Sahara dashboard has been merged into the dashboard (horizon) code. IfSahara is correctly installed (openstack-sahara) and configured, no further dashboardconfiguration is necessary to display the 'Data Processing' tab for each region (Project >Data Processing).

BZ#1081828

This feature improves the workflow of creating a load balancer. You can now create a loadbalancer by specifying the IP address and port number.

BZ#1081834


10












You can now configure the openstack-cinder-volume service to limit I/O bandwidth whencopying data between volumes. This allows you to throttle the load placed on theopenstack-cinder-volume node for long-running I/O copy operations. To use this feature,configure the 'volume_copy_blkio_cgroup_name' and 'volume_copy_bps_limit' settings in/etc/cinder/cinder.conf of the openstack-cinder-volume node accordingly.

BZ#108289 5

The state of an instance provided potentially interesting metrics, particularly to consumersof polled instance-related metrics. These metrics were already available to pollsters, butwas not included in the resource metadata recorded for the instance in previous releases.With this release, the current instance state is now included in resource metadata reportedfor polled instance-related meters.

BZ#1083057

The systemd script no longer explicitly sets a log file. This ensures that syslog settings takeprecedence during logging.

BZ#1084 072

A new feature allows users to download an image's data partially and restart the downloadat any time, as long as the image data is available in the server. This has been implementedusing the 'Content-Range' header, which follows the form "Content-Range: bytesFIRST_BYTE-LAST_BYTE/INSTANCE_BYTES". This header will be parsed only ondownload requests and there is no support on the client library yet. Refer to the HTTP'sspecification for more information about the specific forms of this header.

BZ#1084 26 6

The Orchestration service now supports an OS::Nova::ServerGroup resource, which allowsyou to apply scheduling constraints (like affinity or anti-affinity) to a group of servers.

BZ#10856 4 5

This enhancement enables ipset kernel groups to be used for matching IP addresses iniptables security groups. The previous implementation of security groups, which madeintensive use of iptables rules, resulted in an exponential growth of iptables rules in somecases. Specifically, multiple IP addresses previously needed to be added to the securitygroups of each Compute node's network port. As a result of this enhancement, the size ofiptables rules on Compute nodes are significantly reduced, resulting in a performanceincrease in accepting new connections.

BZ#1086 06 8

Previously, the Telemetry service always aggregated across all disks associated with anindividual instance, making it impossible to bill for individual volume. This release nowfeatures the ability to gather disk metrics for individual devices. Specifically, the Telemetryservice now supports new per-device disk.device.{read|write}.{requests|bytes} meters, inaddition to the original aggregated disk.{read|write}.{requests|bytes} meters.

BZ#1086 522

Orchestration now supports OS::Sahara::Cluster, OS::Sahara::NodeGroupTemplate, andOS::Sahara:ClusterTemplate resource types, so that users can manage OpenStack DataProcessing resources through Orchestration templates.

BZ#1089 125


11









The Telemetry service can now poll for SNMP metrics in a generic way. This allows theTelemetry service to gather additional SNMP metricts without writing a new pollster for eachnew metric.

BZ#109 026 9

OpenStack Compute can now optionally provide a config drive to instances based on aproperty on the image in the OpenStack Image service. Previously, Compute configurationdetermined whether a config drive was used and what format to use for it. With this update,users can now indicate config drive requirements using image properties.

BZ#109 074 1

A new rule now makes it possible to restrict an image's downloads by using the built-inpolicy engine. This rule ("download_image": " role:admin or rule:restricted") must be addedto the policy.json file to ensure it is effective.

BZ#109 1579

The Orchestration service now features an OS::Glance::Image resource type, which allowsimages to be created in the Image service as part of a Heat template.

BZ#109 39 76

A new OS-ENDPOINT-POLICY extension was added to Keystone. This extension allows forassigning separate policies to specific services or even individual endpoints. Policyassignment is now more flexible.

BZ#109 5055

A 'Metadata' column has been added to the Flavors table (Admin > System > Flavors) thatdisplays whether extra specs have been specified for a flavor ('Yes' or 'No'). The user cannow click on either the column value or the 'Update Metadata' action to view or updatedefined metadata.

BZ#109 6 56 7

With this release, floating IP addresses created in Orchestration templates can now beupdated in-place to connect to a different server. Previously a change to a template to movethe attached port would result in a new Floating IP being created and the existing oneremoved.

BZ#109 7514

In previous releases, every virtual CPU was configured as a socket. Some guest operatingsystems have arbitrary limits on the number of sockets they support, but are not limited inthe number of cores or threads. This prevented an instance's OS from taking full advantageof the virtual CPUs configured. With this release, the Compute service can now control aninstance's virtual CPU topology. This allows an administrator and/or tenant users tospecify constraints for the number of threads, cores and sockets to use for a guest instance.The Compute service will use the constraint information to configure a suitable guest CPUtopology. With this, a guest OS such as Windows can take full advantage of all virtualCPUs without encountering support limits.

BZ#109 7517

Need for a feature to enable resetting the state of a volume exposed in the administratordashboard. This functionality was available only through the CLI command: # cinder reset-state --state available <volume-id> Exposed the functionality of the 'cinder reset-state'command in the UI. As is the case with the 'cinder reset-state' command, this change


12









permits an operator to select any valid status, regardless of the current status of the volume.

BZ#109 79 89

Previous Compute versions delegated all CPU placement to the operating system kernel.Although the kernel attempted to keep guest processes running on a single NUMA node,this was not enforced. This meant that guests could drift across NUMA nodes, resulting inan inefficient usage of host resources and limiting guest performance. With this update,Compute can now place guest instances on specific host NUMA nodes. The cloudadministrator or tenant user can set preferences for the guest NUMA topology layout byenabling a scheduler filter that performs intelligent NUMA placement (affinity server groupusing hw:numa_policy=strict metadata). Compute takes into account the guest topologyand then pins the guest instance to one or more host NUMA nodes, resulting in a moreconsistent guest performance and efficient use of host resources.

BZ#109 79 9 7

With this feature, administrators can now reset the state of a snapshot.

BZ#1100538

With this release, the Orchestration service now features OS::Heat::SwiftSignal andOS::Heat::SwiftSignalHandle resource types, which provide an alternate implementation ofWaitConditions that use OpenStack Object Storage to store data.

BZ#1100539

You can now configure a separate storage back end for Telemetry alarms. In previousreleases, alarm-related data could only be stored in the same storage back-end as sampledata. This was inconvenient, as neither the volume nor the nature of these data are similar.On a different back end, however, different criteria can now be usefully applied whenselecting the appropriate database.

BZ#1101371

With this feature, basic support for Trove was added to Horizon. Management ofincremental backups is now supported.

BZ#1101378

The Block Storage service now allows you to set Consistency Groups. With this, you cangroup multiple volumes together as a single entity; this, in turn, allows you to performoperations on multiple volumes (for example, create snapshots) at once, rather thanindividually.

BZ#11034 04

With this enhancement, all tables are now included during the creation of the databaseschema. This behavior allows for easier plugin management. Consequently, all OpenStackNetworking (neutron) tables are present in the database after upgrading to Red HatEnterprise Linux OpenStack Platform 6.

BZ#110356 0

You can now perform a 'cinder retype' through the dashboard. This allows you to migratevolumes or to change any volumes setting (that are set from the volume's type) through theweb interface.

BZ#1104 9 24


13










A single guest can now have multiple network interfaces attached to the same logical hostnetwork. Previous versions of OpenStack Compute had an artificial restriction that a singleguest cannot have multiple network interfaces connected to the same host network. Thereare, however, some valid use cases where this is required and thus Compute could notsatisfy those use cases. With this update, the tenant user can now set up guest networkinterfaces without any restrictions imposed by Compute.

BZ#11054 06

The MongoDB back end can now persist notification payloads, which in turn allows eventprocessing for Telemetry services configured to use a MongoDB back end. In previousreleases, this functionality was only available through the SQLAlchemy back end, whichwas not fully supported in Red Hat Enterprise Linux OpenStack Platform.

BZ#11074 9 1

Functionality for Cinder Quality of Service (QoS) extra specs management such asmaximum IO/seconds (maxIOPS) is now available in the administrator dashboard.Currently qos specs must be managed via the cinder CLI commands: - cinder-qos-create -cinder-qos-delete - cinder-qos-key - cinder-qos-list - cinder-qos-show And theirassociations to volume types are handled with the cinder CLI commands: - cinder-qos-associate - cinder-qos-get-association - cinder-qos-disassociate - cinder-qos-disassociate-all

BZ#11079 25

Cinder CLI has a upload-to-image function that supports uploading a volume into glanceas an image - this functionality needs to be made available in Horizon. -It is now possibleto use a glance image as source to create a cinder volume in Horizon.

BZ#11084 36

This enhancement adds MAC address learning management to the Dashboard (horizon).Users are able to view and toggle the MAC address learning state of a port, in environmentswhere this feature is supported.

BZ#11089 9 2

The Block Storage scheduler now features a new volume number (count) weigher. Thisadds more flexibility in volume scheduling policy, as it allows you to configure volumedistribution based on the number of volumes per back-end (rather than available back-endspace).

BZ#1109 4 09

The description for the 'Create Volume Type' dialogue has been enhanced to make it clearthat creating a type is equivalent to the 'cinder type-create' command. After the volume typeis created, the user can then further define the type by adding extra specs.

BZ#1109 4 20

In Horizon, there's a feature need to automatically populate the "Format" field in the CreateImage modal after the user has filled out the Image Source/Image File fields. Auto populatethe image format field based on the file extension.

BZ#111059 2


14









This feature adds a configurable policy for managing SSH host keys, allowing systemadministrators to choose how secure they wish their SSH connections to be. As a result,Cinder can store and verify SSH host keys, increasing security for drivers using SSHconnections.

BZ#11109 88

With this feature, Nova can now take snapshots of network based Cinder volumes.

BZ#11109 9 4

With this release, when retrieving a list of events from the Orchestration API, clients can nowrequest a paginated list and avoid having to retrieve what may be a very large amount ofdata in a single request.

BZ#111256 0

This feature improves the page loading performance when displaying the Project Volumespage.

BZ#1114 171

This enhancement adds a SMBFS driver to Block Storage (cinder). As a result, Samba andWindows shares are now able to serve as volume backends.

BZ#11176 08

With this release, the Orchestration API output when showing a stack now includes theusername of the owner of a stack (i.e. the user who created it).

BZ#11176 09

A transformer has been added that allows samples to be derived from primarymeasurements associated with different meters. Previously, derived samples could only becomputed within a transformer based on the successive value of primary samplesassociated with the same meters. With this update, derived meters can now be constructedbased on arithmetic rules involving multiple primary meters.

BZ#11176 13

Support for Neutron DVR (Distributed Virtual Router) has been implemented in Horizon.(DVR is currently in Technical Preview) Neutron DVR includes new changes to neutron CLIspecifically in areas of router-creation, router-scheduling, show commands etc., whileadding in admin functionality for distributed virtual router (DVR) functionality to Horizon.

BZ#11189 4 3

Need to be able to disable console access when not accessible from outside a cloud-provider's infrastructure. -A config option added to/etc/openstack_dashboard/local_settings: CONSOLE_TYPE. Valid options are "AUTO","VNC", "SPICE", "RDP" or None. When it's set to None, console access is disabled.

BZ#11204 85

A new volume driver has been added that supports SMB shares from Windows. The driversupports Windows Server 2012 (R2 included). Volumes are exported through SMB sharesas disk images (similar flow to the NFS driver).

BZ#112184 3

With this release, Keystone now supports the standard JSON Home document format for API


15











With this release, Keystone now supports the standard JSON Home document format for APIdiscovery. Keystone's previously supported API discovery response format was a non-standard JSON document. This format required a client to have Keystone specificknowledge to understand how to use the response. The JSON Home document formatallows API discovery to use a standardized format, allowing client applications to performAPI discovery across multiple services in a standard way.

BZ#112276 7

The puppet-keystone puppet module now supports deploying Keystone in Apache HTTPD.

BZ#1124 133

Add support for Spark jobs in Sahara data processing UI. Support for Spark EDP jobs inthe data processing dashboard has been added. The changes are: -Added Spark as a jobtype when creating jobs -Added some help text for Spark job creation -Hide appropriateconfiguration fields when launching a Spark job -Made job type drop down translatable

BZ#112509 3

There was a need to add the ability for admins to create/update/delete custom propertiesand metadata for Images. This is useful for admins and users to meaningfully describeimages by sharing key-value pairs and tag metadata. A new "Update metadata" option isnow visible in the Admin Images panel that enables you to custom properties andmetadada for Images.

BZ#11274 05

When using nova-network with multiple networks, it is now possible to set the MTU, enableor disable DHCP, set the DHCP server, and indicate whether the network shares addresseswith other networks. Previously, it was not possible to set these parameters on a per-network basis, making it more difficult to use nova-network with multiple networks. With thisupdate, administrators now have more flexibility with settings when using multiple networkswith nova-network.

BZ#1127526

In previous releases, the accuracy and timeliness of Telemetry samples could be negativelyimpacted if the central agent became overloaded by a large number of resources. Tomitigate this, the Telemetry service now features workload partitioning; this features allowsthe central agent to scale horizontally with each instance polling a disjointed set ofresources. To do this, the 'tooz' utility coordinates group membership accross multiplecentral agents that share polling of resources.

BZ#112839 8

Need for a feature wherein operators can disable L3 Router features by configurationoptions. -New config option 'enable_router' to OPENSTACK_NEUTRON_NETWORK. Thedefault is True as router feature is enabled in most deployments and it is the current defaultbehavior of Horizon. If this option is False, Router panel disappears. -Network Topologypanel shows routers in the topology map and also has "Create Router" button. If"enable_router" is set to False, routers in the topology map are not displayed, and "CreateRouter" button is not shown. -'enable_floatingip' option toOPENSTACK_NEUTRON_NETWORK. Similar to the floating IP feature in Neutron providedby L3 router extension, if this option is set to False, "Floating IP" tab and"Associate/Disassociate Floating IP" menu in the instance table are not shown.

BZ#1129 518

This release adds Cinder Consistency Group support for the EMC VNX Direct Driver.


16








BZ#1130371

With this release, the "heat stack list" command now provides a "--show-nested" option thatincludes any nested stacks in the output. Normally, only stacks created directly by the userappear in the list and nested stacks are omitted.

BZ#1130372

Tooz-driven group membership coordination is now used, which allows multiple ceilometer-alarm-evaluator services to share the workload. The group membership-based solutionprovides a simple but robust technique for managing workload sharing that is lessproblematic than the previous RPC-fanout-based solution. Alarm evaluators can now beset up on multiple nodes using configuration for individual instances; if an evaluator fails,its workload is transferred to the other evaluators.

BZ#1130726

With this release, keystone now emits CADF notifications for role assignment events,providing a more complete audit trail. Role assignment operations affect a user's access tocloud resources; keeping an audit trail of these actions can be important to detectmalicious actions.

BZ#113176 8

The Orchestration service now features an OS::Heat::SoftwareDeployments resource, whichcan deploy a single SoftwareConfiguration to a group of servers. This is helpful fordeploying a cluster where each server has to be configured with the IP addresses of everyserver in the cluster.

BZ#1132103

This feature updates cinderclient so that users are now prompted for a password via thecommand line if no password is specified via an environment variable or the --os-passwordoption.

BZ#1132104

If no password is provided using either --os-password or env[OS_PASSWORD], python-glanceclient now falls back to password entry using tty.

BZ#114 9 59 9

With this feature, you can now use Cinder to create a volume by specifying either the imageID or image name.

BZ#1158170

To allow individual operations such as POST samples API to be selectively configured asadmin-only, this update includes configurable Role-Based Access Control for theceilometer API. As a result, individual API operations can now be restricted to admin (or anyother individual role) by adding a rule to the '/etc/ceilometer/policy.json' file of the form:" telemetry:create_samples": " rule:context_is_admin"

BZ#116 04 05

RBD snapshots and cloning are now used for Ceph-based ephemeral disk snapshots. Withthis update, data is manipulated within the Ceph server, rather than transferred acrossnodes, resulting in better snapshotting performance for Ceph.


17










BZ#11779 9 5

This enhancement allows SR-IOV virtual functions (VF) to passthrough to ' flat' projectnetwork types. This is due to PCI passthrough with SR-IOV not being VLAN-specific. As aresult, OpenStack Networking project networks with the " flat" network type can now takeadvantage of SR-IOV networking support.

BZ#1180216

Previously, the OS::Heat::ResourceGroup resource in a template failed validation ifconfigured with size "0" . Since some template authors use this mechanism to createoptional parts of a template, a size of zero no longer causes a validation failure.

BZ#1180335

With this release, support for specifying a redis-sentinel in the backend URL had beenadded. This allows ceilometer fail over between a cluster of redis services, as to avoid theredis service being a single point of failure. As a result, the tooz client can use a cluster ofredis services as the backend with the sentinel failing over mastership of the cluster asnecessary.

BZ#11806 07

RBD snapshots and cloning are now used for Ceph-based ephemeral disk snapshots. Withthis update, data is manipulated within the Ceph server, rather than transferred acrossnodes, resulting in better snapshotting performance for Ceph.

BZ#11834 21

OpenStack Sahara enables the fast provisioning and easy management of Hadoopclusters on OpenStack. Hadoop is used to store and analyze large amounts of data, whichis usually unstructured but can be a combination of both complex and structured data.OpenStack Sahara is fully supported in this release. For information on how to installOpenStack Sahara, refer to: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/6/html/Installation_and_Configuration_Guide/chap-OpenStack_Sahara_Installation.html

BZ#11854 4 4

This update introduces the rabbitmq-cluster resource agent for managing clusteredRabbitMQ instances with the Pacemaker cluster manager.

BZ#1186 070

This enhancement includes a feature, virt-v2v, which allows users the ability to convertimages from a variety of hypervisors to run on OpenStack cloud.

2.2. Technology Preview

BZ#1100535

Ironic, an OpenStack bare-metal provisioning service, is now included in this release as atechnology preview. This project provisions bare metal machines using commontechnologies (such as PXE boot and IPMI) to cover a wide range of hardware, whilesupporting pluggable drivers to allow the addition of vendor-specific functionality.

BZ#11834 14

Trove (Database-as-a-Service) is included in this release as a Technology Preview. This


18










service allows users to quickly and easily utilize the features of a relational or non-relational database without the burden of administrative overhead. With Trove, users anddatabase administrators can provision and manage multiple database instances asneeded. For more information about Trove, refer to https://wiki.openstack.org/wiki/Trove.

BZ#119 0788

This release includes a v2 and a v3 version of the OpenStack Compute API. While v2 of theAPI is fully supported, v3 is experimental and remains a technology preview.

BZ#119 8508

This release includes Distributed Virtual Routing (DVR) as a technical preview. DVRenables the placement of L3 Routers across Compute nodes, allowing network traffic to bedirected between them (East-West) without first requiring routing through a Network node.

BZ#119 8855

VPN-as-a-Service (VPNaaS) is included in this release as a Technology Preview. VPNaaSallows tenants to use VPN features for network connectivity.

BZ#119 8856

The Firewall-as-a-Service (FWaaS) plug-in adds perimeter firewall management toNetworking. FWaaS uses iptables to apply firewall policy to all Networking routers within aproject. FWaaS is currently in technical preview; untested operation is not recommended.

BZ#119 889 7

The OpenDaylight driver for OpenStack Networking is included in this release as aTechnology Preview.

2.3. Release Notes

BZ#1158213

In High Availability environments deployed through the Red Hat Enterprise LinuxOpenStack Platform Installer, SELinux no longer needs to be Permissive on the HAcontroller to allow VNC access. A bug that required this in previous releases has since beenfixed.

BZ#89 4 4 4 0

Red Hat OpenStack does not yet fully support being used with ipv6 networkingtechnologies. Only ipv4 is supported at this time.

BZ#9 75014

In order for Nova's resize command to work when using the libvirt driver and attempting toresize between nodes (the default resize method), the Nova users on the compute nodesmust have permission to perform passwordless SSH to the other compute nodes. To set thisup, generate SSH keys for the Nova user on each compute node, and then add thegenerated keys from the other compute nodes to the ~/authorized_keys file for the Nova useron each compute node.

BZ#104 2550

This update enables OpenStack Networking (neutron) to create a Provider Network thatuses an upstream device with Router Advertisement multicasts. As a result, instances areable to use Stateless Address Autoconfiguration (SLAAC) to configure their IPv6


19










able to use Stateless Address Autoconfiguration (SLAAC) to configure their IPv6networking.

BZ#116 9 4 70

Support for the XML format in the Nova v2 API was deprecated in Red Hat Enterprise LinuxOpenStack Platform 5 and has been removed in Red Hat Enterprise Linux OpenStackPlatform 6. Customers wishing to interact with the Nova v2 API need to use the JSONformat, which has wide OpenStack SDK support.

BZ#1184 6 6 3

The sysfsutils package is now a dependency of the Compute service. This packageprovides the Compute service with the ability to attach Block Storage volumes. In previousreleases, sysfsutils was not a hard dependency of the Compute service; this required usersto manually install sysfsutils as well during manual Compute installations. With thisrelease, installing Compute packages will automatically install sysfsutils as well.

2.4 . Known Issues

BZ#114 19 23

The Red Hat Enterprise Linux OpenStack Platform Installer does not support UEFI booting.As a result, when attempting to perform a PXE-boot on a UEFI host, the installer will fail todownload the required PXE images. To work around this, switch the host to ' legacy' modefor PXE booting.

BZ#114 4 034

During subnet creation of the Public API, Admin API, and Management networks, the RedHat Enterprise Linux OpenStack Platform installer does not validate whether: 1) IPAM is setto 'DHCP' and boot mode 'dhcp' (provisioning network), or 2) IPAM is set to ' internal db'and boot mode set to 'static' If IPAM is set to ' internal db', then the range of IP addressesmust be greater than or equal to the number of controllers (3) plus the number of VIPs (10-12 depending on which network). Because these settings are not validated, it is possible forsubnets to be created without enough IPs to allocate enough VIPs. In such cases,generating VIPs could result in puppet errors. To prevent this, you need to manually ensurethat your API subnets (Admin, Public, Management) have enough available IP addresses toallocate enough VIPs.

BZ#9 9 0073

The Block Storage GlusterFS volume driver configuration does not provide a way to movea GlusterFS server from one address to another. As a result, attempting to do so will resultin Block Storage using the new address as a new GlusterFS server, while still trying toaccess volume data at the old location. Workaround: Update the SQL DB's cinder.volumetable provider_location field to point to the desired location for volumes you are moving.

BZ#116 7073

The SELinux policies for Keystone are missing some enforcement rules for certainoperations. As a result, SELinux will cause keystone to malfunction if SELinux is set toenforcing mode. Since this is an early release of Red Hat Enterprise Linux OpenStackPlatform 6.0, not all SELinux issues have been found. Red Hat recommends to set SELinuxto permissive mode. For more information on how to enable and disable SELinux, see:https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/SELinux_Users_and_Administrators_Guide/sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html


20







BZ#116 8277

The Red Hat Access plug-in for Red Hat Enterprise Linux OpenStack Platform does notsupport Internet Explorer 9. Internet Explorer 9 users attempting to leverage the Red HatAccess plug-in in Red Hat Enterprise Linux OpenStack Platform will be unsuccessful.

BZ#116 9 135

The Red Hat Access plug-in for Red Hat Enterprise Linux OpenStack Platform does notsupport Internet Explorer 9. Internet Explorer 9 users attempting to leverage the Red HatAccess plug-in in Red Hat Enterprise Linux OpenStack Platform will be unsuccessful.

BZ#116 9 138

Known bugs with Microsoft Internet Explorer 9 Cross Origin Resource Sharing (CORS) willprevent Internet Explorer 9 users from leveraging the Red Hat Access plug-in for Red HatEnterprise Linux OpenStack Platform. There is no workaround other than using a differentbrowser. The inability to use the Red Hat Access plug-in on Internet Explorer 9 will not affectthe overall functionality of the Horizon dashboard. Only Red Hat Access plug-in featureswill be disabled.

BZ#11739 87

In deployments using IPv6 networks with OpenStack Networking, IPv6 subnets do not havea gateway set. As a result, IPv6 networks do not work as expected.

BZ#1174 215

Stateful DHCPv6 is currently nonfunctional in the Red Hat Enterprise Linux OpenStackPlatform 6 (Juno) GA as a result of upstream bug 1377843. Further details are available athttps://bugs.launchpad.net/neutron/+bug/1377843.

BZ#117536 7

Due to a missing dependency to python-oslo-utils, python-glanceclient fails to work. As acurrent workaround, install both the python-oslo-utils and the python-glanceclient packageat the same time using the following command: yum install -y python-oslo-utils python-glanceclient

BZ#11776 11

A known issue has been identified for interactions between High Availability (VRRP) routersand L2 Population. Currently, when connecting a HA router to a subnet, HA routers use adistributed port by design. Each router has the same port details on each node that it'sscheduled on, and only the master router has IPs configured on that port; all the slaveshave the port without any IPs configured. Consequently, L2Population uses the staleinformation to advise that the router is present on the node (which it states in the portbinding information for that port). As a result, each node that has a port on that logicalnetwork has a tunnel created only to the node where the port is presumably bound. Inaddition, a forwarding entry is set so that any traffic to that port is sent through the createdtunnel. However, this action may not succeed as there is not guarantee that the masterrouter is on the node specified in the port binding. Furthermore, in the event that the masterrouter is in fact on the node, a failover event would cause it to migrate to another node andresult in a loss of connectivity with the router.

BZ#1181307

The python-pbr package required by Red Hat Enterprise Linux OpenStack Platform puppetmodules is not present in Red Hat Enterprise Linux OpenStack Platform 6. Installationusing Packstack will fail if Ironic (a Technology Preview package) is enabled. Manual


21









installation is required for Ironic at the moment.

BZ#11826 4 2

When an overcloud node boots up, it runs os-collect-config as a part of registration. Theos-collect-config script saves data from the Orchestration (heat) metadata API locally andthen calls os-refresh-config any time that metadata has changed. Subsequent calls to theregistration script call subscription-manager again and it returns a non-zero exit code. Withthe return of a non-zero exit code, the script fails, the stack results in a timeout, and multipleregistrations can occur. There is no current workaround.

BZ#118309 9

An iptables setting in the undercloud causes overcloud nodes to fail to register since thenodes have no external access. As a workaround, run the following command on theundercloud image: iptables -D FORWARD -j REJECT --reject-with icmp-host-prohibited

BZ#1183104

Previous to the Satellite 6 release, the katello-agent and its dependencies needed the rhel-7-server-rh-common-beta-rpms repository to be enabled. Since the Satellite 6 release,necessary packages have been moved to the rhel-7-server-rh-common-rpms repository.However, upstream code still references the rhel-7-server-rh-common-beta-rpms repositorywhich no longer have the latest packages, causing Satellite instances to fail.

BZ#119 5252

A quiet dependency on a newer version of selinux-policy causes openstack-selinux 0.6.23to fail to install modules when paired with selinux-policy packages from Red Hat EnterpriseLinux 7.0 or 7.0.z. This causes Keystone and other OpenStack services to receive 'AVC'denials under some circumstances, causing them to malfunction. Two workarounds allowservices to function correctly: 1) Leave openstack-selinux at 0.6.18-2.el7ost until you areready to update to Red Hat Enterprise Linux 7.1. At that time, a 'yum update' will resolve theissue. 2) Install the updated selinux-policy and selinux-policy-targeted packages from RedHat Enterprise Linux 7.1 (version selinux-policy-3.13.1-23.el7 or later), then updateopenstack-selinux to version 0.6.23-1.el7ost.


22





Chapter 3. Upgrading

For details on upgrading from a previous version of Red Hat Enterprise Linux OpenStack Platform,refer to https://access.redhat.com/articles/1317223/. This article also contains links to instructions foreach recommended upgrade method.

Chapt er 3. Upgrading

23

https://access.redhat.com/articles/1317223/

Revision History

Revision 6 .0.1-1 Thu Mar 05 2015 Don DomingoUpdated for first maintenance release of Red Hat Enterprise Linux OpenStack Platform 6.0.

Revision 6 .0.0-5 Tue Mar 03 2015 Don DomingoAdded some items relevant to GA release and edited some notes for clarity.

Revision 6 .0.0-4 Wed Feb 11 2015 Don DomingoRelease for Red Hat Enterprise Linux OpenStack Platform 6.0.


24

Documents

Red Hat Enterprise Linux OpenStack Platform 6 Release Notes