A newer version of Mirantis OpenStack documentation is available!
  • Current Version
  • 9.0 Mirantis OpenStack

Release Notes

Release Notes for Mirantis OpenStack 9.0

Mirantis, Inc. is releasing Mirantis OpenStack version 9.0.

The following table lists the released revisions of this documentation:

Revision Date Description
9.0 G.A. July-08-2016 Initial G.A.

Mirantis OpenStack 9.0 is based on the OpenStack Mitaka release and includes enhancements, bug fixes, and known issues for the world's leading OpenStack infrastructure deployment and management technologies:

Major components versions

OpenStack core projects in the Mirantis OpenStack 9.0 hardened packages support the OpenStack Mitaka release.

OpenStack integrated projects
Operating systems
CentOS 7.2 (for the Fuel Master node only)
Ubuntu 14.04 (for the OpenStack nodes only)
Ubuntu: KVM, libvirt 1.2.9; QEMU 2.3
Networking backend Open vSwitch 2.4.0

What's new

Mirantis OpenStack 9.0 introduces a set of new features and enhancements. This section lists these improvements:

Network Functions Virtualization (NFV) features

  • CPU pinning - Fuel allows you to specify the amount of CPU cores on a compute node that will be dedicated for pinning.
  • NUMA - You can now enable and use Non-Uniform Memory Access (NUMA) on the OpenStack Mitaka environment.
  • Huge Pages - Fuel allows you to specify the amount of RAM on a compute node to be dedicated for Huge Pages.
  • SR-IOV:
    • Fuel detects NICs that support SR-IOV enablement and how many virtual functions (VFs) they can provide.
    • Fuel allows you to configure NIC as SR-IOV interface.
    • Fuel allows you to specify the amount of VFs that VMs can consume from this particular NIC.
    • Fuel allows you to assign NIC with SR-IOV enabled to a particular physical network. The tenant can then request a VM with a SR-IOV port attached to a specific physical network, for example, Public network.
  • DPDK:
    • Fuel detects NICs that support DPDK.
    • Fuel allows you to enable DPDK on specific NIC or bonded interfaces with this NIC.
    • Fuel allows you to adjust the amount of CPU cores and RAM provided to OVS-DPDK for performance tuning.
    • Fuel deploys DPDK-enabled OVS package and DPDK drivers when operators select DPDK features.

Lifecycle Management (LCM) features

  • As a user of Mirantis OpenStack you can now rely on Fuel to perform the following "Day 2" operations of OpenStack cloud lifecycle:
  • Fuel enables you to change the configuration of an OpenStack environment that is in the operational, error, stopped, or partially_deployed states for further redeployment of the OpenStack environment with new parameters. See Modify the OpenStack environment settings.
  • All deployment tasks that Fuel uses when configuring OpenStack are now idempotent. This enables the lifecycle management features that require re-running of deployment tasks with the updated input data in the post-deployment stage of cloud lifecycle.
  • You can stop and restart environment deployment without resetting the deployment process. This allows you to fix deployment errors and resume the deployment process without having to start it over completely. See Stop and resume the OpenStack environment deployment in the Fuel User Guide.
  • You can now perform configuration management for Mirantis OpenStack nodes using Puppet Master. See the knowledge base article.

Other features

  • Changed the iptables rules to allow SSH access to the Fuel Master node from the provided network only. By default, the provided network for SSH access is the Admin (PXE) network. You can change it during the Fuel Master node installation on the Security Setup tab of the Fuel setup menu. LP1557190
  • You can deploy your OpenStack environment on servers with disks provided by storage systems with multipath I/O. See Configure an OpenStack environment on nodes with multipath block devices in the Fuel User Guide.
  • Fuel now supports cgroups, which enable you to efficiently allocate a specific amount of system resources, including CPU and memory, to particular resource groups. See Manage control groups in the Fuel User Guide.
  • You can now install and configure etckeeper through Fuel plugin. See Fuel plugin etckeeper documentation.
  • Added detailed instructions on how to enable RHEL and Oracle Linux as compute nodes for Mirantis OpenStack 9.0. See the Integrate the RHEL compute nodes guide.
  • Enabled Glance Artifacts Repository (Glare) as a default storage for the Murano packages. Therefore, these packages are now located in your default OpenStack storage instead of the Murano database. See blueprint | spec.
  • The OpenStack Application catalog service is now also installable as a plugin for Fuel. This plugin is designed to enable upgrading of the stock Mirantis OpenStack Application Catalog together with plugin installation. This plugin update mechanism will be used to deliver future updates to the OpenStack Application catalog service.

Resolved issues

This section lists a number of Mirantis OpenStack resolved issues sorted by OpenStack components. For a complete list, refer to Mirantis OpenStack and Fuel for OpenStack Launchpad projects.


  • Fixed idempotency of compute tasks. The fix moved the Neutron integration bridge waiting procedure to the enable_nova_compute_service task where it belongs. LP1526895

  • Fixed deployment with enabled SR-IOV that failed on some hardware with the sriov_iommu_check entry in the log. This was a known issue with Linux kernel and some hardware platforms. LP1556854

  • Fixed cluster capacity calculation in the Fuel web UI:

    • Fuel calculates HDD capacity counting nodes with the storage role
    • Fuel calculates CPU and RAM counting nodes with the compute role


  • Removed support for the following resources from LCM since the old tasks' format for plugins is outdated:

    • r'/clusters/(?P<cluster_id>\d+)/orchestrator/plugins_pre_hooks/?$’
    • r'/clusters/(?P<cluster_id>\d+)/orchestrator/plugins_post_hooks/?$'

    Therefore, use the deployment graph API to get and analyze the plugins' tasks.

    Old granular tasks are now only supported in the backward compatibility mode. To run granular tasks in this mode:

    1. Log in to the Fuel Master node CLI.

    2. Download the environment settings file:

      $ fuel --env <environment_id> settings download
    3. Modify the settings file by adding the second value to the common section in YAML format:

      # common:
           propagate_task_deploy: value: true
    4. Upload the modified file to the environment:

      $ fuel --env <environment_id> settings upload


  • Fixed the issues with environment statuses. Now, the environment statuses are shown correctly. Depending on the nodes states, an environment may have one of the following statuses:

    • Operational - If all nodes in the environment are successfully deployed.
    • Partially deployed - If only some nodes are provisioned or deployed.
    • Error - If at least one node is in the error state.
    • Stopped - If you have stopped the deployment process.

    LP1422435 | LP1542201

  • Fixed the issue with the Fuel web UI displaying an incorrect status of nodes when post-deployment tasks are running. LP1439776

  • Fixed the issue with IP range intersection with default gateway values when the gateway and IP ranges are not explicitly set and multiple network groups are configured. LP1539503

  • Improved performance in large deployments by disabling high availability for remote protocol calls (RPC) queues which helped to significantly offload excessive RabbitMQ traffic. High availability is disabled by default for all types of RabbitMQ workloads except for the OpenStack Telemetry service. LP1550303


  • File injection is now disabled in the in Nova libvirt driver, which allows you to unify the settings for Ubuntu vs CentOS and file vs Ceph-based ephemerals. File injection can still be performed through configuration drive and cloud-init within images. LP1556819
  • Downed services of deleted hosts in Nova are now cleaned up on a new deploy cycle. LP1471172


  • Fixed the issue when deleting a DVR serviceable causing the removal of the network router from the L3 agent hosting SNAT. LP1524908


  • Fixed the issue with OSTF Murano tests failing if the Fuel Master node is not in the same network as the VMs. The fix implements a network check for the controller nodes. LP1495699


  • Added the capability for Ceilometer to gather main transformer-based metrics, such as cpu_util, disk.*.rate, and network.*.rate, by default. The Ceilometer compute agents create these metrics on the compute nodes without any changes in the pipeline.yaml file. LP1575251
  • Decreased support of custom metrics. Now, new metrics can be based only on the unit_conversion transformer and the arithmetic transformer (an expression with only one metric). LP1537708
  • Resolved the issue with the OSTF Ceilometer tests failing with the IndexError: list index out of range message. LP1543050


  • [CirrOS] Resolved the file injection issue for CirrOS images. LP1587960
  • [Horizon] Resolved the issue with the Horizon link being http://undefined/ after the OpenStack environment deployment. LP1544446
  • [Galera] Resolved the issue with Pacemaker killing the MySQL starting process before the full state transfer completes, when the transfer is required after a node fails in the MySQL Galera cluster. LP1478310

Known issues

This section lists the Mirantis OpenStack known issues sorted by OpenStack components:


  • The EC2 API support was removed from Fuel. Therefore, the EC2 service nova_ec2 does not exist in the catalog list. To make S3 work if EC2 is missing, you can generate or download credentials using openstackclient:

    openstack ec2 credentials create


  • On a redeployment attempt, changing a public network CIDR on the unlocked Settings tab results in deployment failure. Public network shares CIDR with Neutron Floating network which does not support CIDR changes. LP1587897

  • Disk partitioning on controllers does not automatically reset back to the default state if you change the Glance back end. LP1450100

  • Default disk allocation may not use entire disk space. To prevent this, before deploying, check that you do not have unallocated disk space:

    1. Open the Nodes tab.
    2. Select a node.
    3. Click Configure Disks.


  • In the Fuel web UI, clicking Stop deployment when a node is in the Ready status disables the Deploy changes button if the post-deployment tasks are in progress. As a workaround, reset the environment. LP1466431

  • When deploying an environment with a single controller, compute roles fail while attempting to resolve primary-controller. LP1419201

  • Fuel CLI fails to execute fuel --fuel-version if the Keystone password is not the default one. LP1399608

  • In environments that are not updated to 9.0, the common tasks will run multiple times if a node has multiple roles assigned. LP1424295

  • If a 9.0 environment was deployed after the release of Mirantis OpenStack 9.1, the redeployment fails with the following error: AssertionError: Task 'deploy' has incorrect status. error != ready, 'u'dpdk'. LP1641931


    • Update Mirantis OpenStack from 9.0 to 9.1 using the Update to the minor version instruction.

    • For new Mirantis OpenStack 9.0 deployments, reinstall the Fuel Master node 9.0. During reinstallation, when Fuel prompts you to access the Fuel setup screen, complete the following steps:

      1. Open the Fuel setup menu.

      2. In the Shell Login section, select Shell Login.

      3. In the Shell Login window, enter the following:

        yum-config-manager --disable mos9.0-updates --save
      4. Proceed with the Fuel Master node reinstallation.


  • Live migration of the volume-backed instances with config_drive_format=vfat is not supported by libvirt prior to version 1.2.17. LP1589460


    • Set force_config_drive to False in nova.conf and restart the OpenStack services before booting the instance.
    • Use Ceph for ephemerals.
    • Set up a file-based local storage, for example, NFS.
    • Upgrade libvirt to v1.2.17.
  • In rare cases, the SR-IOV migration may cause an ERROR status of the instance. LP1592409


  • If Glare is enabled, the package_size_limit parameter in murano.conf is ignored. LP1590474


  • When you delete a large number of volumes at once, some of them may remain with the Deleting status. LP1550192

    To resolve the issue, change the DB driver for Cinder to PyMySQL in the Cinder configuration file:

    1. Open the etc/cinder.conf file for editing.

    2. Change the value of the connection parameter to the following:

      connection = mysql+pymysql://user:passwod@db_host/cinder?charset=utf8
    3. Restart the cinder-volume service:

      service cinder-volume restart


  • [Docker] Since the DockerInc::Docker::Container resource is not supported by Heat in community and is not used by Murano anymore, it is deprecated in Mirantis OpenStack 9.0 and will not be provided in the default Mirantis OpenStack installation in 10.0.


  • The Sahara engine may cause memory leaks and, as a result, may malfunction. LP1536259
  • An SSH connection to a large OpenStack environment, such as the one that includes 500 compute nodes and a Hadoop cluster, may time out during provisioning. LP1545049


  • [Corosync/Pacemaker] All Corosync-managed services (RabbitMQ, Neutron agents, MySQL, and others) are installed with an override file in /etc/init/SERVICENAME.override. This blocks upstart from starting a particular service automatically, but it does not prohibit a user from manually running /etc/init.d/SERVICENAME start. Changing this behavior may lead to a duplicate copy of the service that an administrator can launch simultaneously. There should be no scenario where services run duplicate instances. Therefore, this solution in place is appropriate. LP1495133

  • [NFV] Spawning a VM across several NUMA nodes with DPDK deployment causes a loss of network connectivity to the VM. LP1591087

  • [NFV] [Intel XL710 40 Gbit] DPDK driver for the Intel XL710 NIC incorrectly handles incoming VLAN tags. It leads to packets losses for the packets longer than the MTU value configured on DPDK port minus 4 bytes. For example, if the configured value is 1500 bytes (default), then the packets with size between 1497 and 1500 bytes inclusive will be lost. LP1587310

    The workaround is to decrease MTU by 4 bytes on all the interfaces that send traffic to VMs with DPDK private network.

  • [NFV] [Intel XL710 40 Gbit] If both DPDK and SR-IOV are configured on ports of the same Intel XL710 NIC, DPDK fails to initialize port and ovs-vswitchd stops that leads to the environment deployment failure. LP1583077


    1. Install Linux kernel version > 3.17, for example, the linux-image-generic-lts-vivid packet.
    2. Change the DPDK driver from igb_uio to vfio-pci.
  • [DPDK] A DPDK-enabled application running inside an instance can cause segmentation fault in host Open vSwitch. LP1597004

    As a workaround, use DPDK version 16.04 or later.

Fuel Master node upgrade from 8.0 to 9.0

You can upgrade the Fuel Master node 8.0 (Liberty) to the latest version using the backup-restore procedure that involves the reinstallation of the Fuel Master node.


Currently, a Mirantis OpenStack environment upgrade from 8.0 to 9.0 is not supported. But you can use the upgraded Fuel Master node to maintain your old environments as well as create new Mirantis OpenStack environments.

Always consult Mirantis Support if you plan to upgrade your Mirantis OpenStack environment or the Fuel Master node.

See documentation.

How to obtain the product

Mirantis OpenStack is distributed as a self-contained ISO.

You can download the ISO as well as the Mirantis VirtualBox scripts from Download Mirantis OpenStack.

For evaluation purposes, install Mirantis OpenStack using the Mirantis VirtualBox scripts. See QuickStart Guide for details.