The 5.0.1 maintenance release for Mirantis OpenStack, which has now reached general availability, represents a big milestone for the product. For those who have already installed Mirantis OpenStack 5.0, this will be the first time that you can upgrade the Fuel Master Node in place and retain management of your existing 5.0 environments. No need to redeploy!
To upgrade the Fuel Master Node that manages an existing Mirantis OpenStack 5.0 cloud environment, just do the following:
Be sure that no installations are in progress on your Fuel Master Node!
Download the upgrade tarball from http://software.mirantis.com to a local system.
You’ll want to choose the “Upgrade Package” since you’re upgrading from 5.0 to 5.0.1. (If you’re a new customer, or on version 4.1.1 or earlier, can still download the ISO and IMG to install a new instance of the Fuel Master Node.)
Use scp or your SSH client to copy the tarball to a location on the Fuel Master Node disk that has adequate space, such as /var/tmp.
scp MirantisOpenStack-5.0.1-upgrade.tar firstname.lastname@example.org:/var/tmp
Log into the Fuel Master Node and extract the tarball contents:
cd /var/tmp # Use the directory where the tarball is located
tar -xf MirantisOpenStack-5.0.1-upgrade.tar
Once all the files are extracted, run the upgrade script from that same directory:
Do not interrupt the upgrade! The upgrade process can take 30-60 minutes. Some operations (such as uploading images) take some time; the listing of updated files may slow down, but this does not mean that the upgrade process has hung.
When the upgrade is complete, the following messages will appear on your screen
*** UPGRADE DONE SUCCESSFULLY
After the upgrade, you’ll notice in the Releases tab that you now have the ability to deploy and manage both the 2014.1 release (which came with Mirantis OpenStack 5.0) and the 2014.1.1-5.0.1 release (which was came with 5.0.1)
So, what else is in the 5.0.1 update?
We’ve further enhanced the High Availability of Mirantis OpenStack to address even more points of failure. For example, there’s further tolerance for the rare situation of multiple failures of the same controller or loss of the management interface on the primary controller.
When we released 5.0, there was a bootstrap kernel issue where the kernel was lacking the proper firmware files for some hardware types. While a patch has been available from Support for 5.0 customers on this issue, it’s now included by default when deploying a 5.0.1 environment.
As a maintenance release, we’ve address other important defect fixes. You can review the Release Notes for more information.
On the horizon
Mirantis 5.0.1 is a maintenance release to 5.0, but we’re hard at work on Mirantis OpenStack 5.1 which we hope to deliver with these new and exciting features:
Updating an existing OpenStack environment: With Mirantis OpenStack 5.1, you’ll be able to automatically update an existing environment to the latest offered version of OpenStack without redeployment. For example, if you’ve installed an environment using Mirantis OpenStack 5.0 (which is based on Icehouse 2014.1), there will be an option to update that environment to Icehouse 2014.1.1.
Deployment of ML2 OpenStack vSwitch by default: Starting with Havana, the legacy plugin structure for Neutron has been deprecated and replaced with a Modular Layer 2 (ML2) plugin structure. This change will enable Neutron to utilize a variety of Layer 2 network technologies rather than being locked in the monolithic structure found in previous releases of OpenStack.
Access Control to the Fuel UI and API: When using either the Fuel UI or Fuel APIs, users will be challenged to provide authentication credentials (e.g. username and password). These credentials and the authentication process will be handled by a local instance of Keystone present on the Fuel Master Node. Users will also be able to change their password within the Fuel UI.
VMWare NSX for KVM hypervisors: VMWare NSX is a is a software-defined network (SDN) that uses controllers and overlay networking. Mirantis OpenStack 5.1 will enable you to select VMWare NSX as an networking option for use with the KVM hypervisor.
Support Mellanox hardware: Mirantis OpenStack 5.1 will properly detect Mellanox hardware installed within discovered nodes. This enables an operator to
- Configure storage to work over ISER (High performance RDMA based ISCSI)
- Install OFED drivers, firmware and configure SR-IOV kernel parameters
- Install and configure the Mellanox SR-IOV plugin for OpenStack for high performance VM link
- Test the environment utilizing Mirantis OpenStack Health Checks