Home > Blogs > OpenStack Blog for VMware > Tag Archives: Upgrade

Tag Archives: Upgrade

VMware Integrated OpenStack 3.1 GA. What’s New!

VMware announced general availability (GA) of VMware Integrated OpenStack 3.1 on Feb 21 2017. We are truly excited about our latest OpenStack distribution that gives our customers enhanced stability on top of the Mitaka release and streamlined user experience with Single Sign-On support with VMware Identity Manager.   For OpenStack Cloud Admins, the 3.1 release is also about enhanced integrations that allows Cloud Admins to further take advantage of the battle tested vSphere Infrastructure & Operations tooling providing enhanced security, OpenStack API performance monitoring,  brownfield workload migration, and seamless upgrade between central and distributed OpenStack management control planes.






VIO 3.1 is available for download here.  New features include:

  • Support for the latest versions of VMware products. VMware Integrated OpenStack 3.1 supports and is fully compatible with VMware vSphere 6.5, VMware NSX for vSphere 6.3, and VMware NSX-T 1.1.   To learn more about vSphere 6.5, visit here, vSphere 6.3 and NSXT, visit here.
  • NSX Policy Support in Neutron. NSX administrators can define security policies, shared by the OpenStack Cloud Admin with cloud users. Users can either create their own rules, bounded with the predefined ones that can’t be overridden, or only use the predefined, depending on the policy set by the OpenStack Cloud Admin.  NSX Provider policy feature allows Infrastructure Admins to enable enhanced security insertion and assurance all workloads are developed and deployed based on standard IT security policies.
  • New NFV Features. Further expanding on top of VIO 3.0 capability to leverage existing workloads in your OpenStack cloud, you can now import vSphere VMs with NSX network backing into VMware Integrated OpenStack.  The ability to import vSphere VM workloads into OpenStack and run critical Day 2 operations against them via OpenStack APIs enables you to quickly move existing development projects or production workloads to the OpenStack Framework.  VM Import steps can be found here.  In addition full passthrough support by using VMware DirectPath I/O is supported.
  • Seamless update from compact mode to HA mode. If you are updating from VMware Integrated OpenStack 3.0 that is deployed in compact mode to 3.1, you can seamlessly transition to an HA deployment during the update. Upgrade docs can be found here.
  • Single Sign-On integration with VMware Identity Manager. You can now streamline authentication for your OpenStack deployment by integrating it with VMware Identity Manager.  SSO integration steps can be found here.
  • Profiling enhancements.  Instead of writing data into Ceilometer, OpenStack OSprofiler can now leverage vRealize Log Insight to store profile data. This approach provides enhanced scalability for OpenStack API performance monitoring. Detailed steps on enabling OpenStack Profiling can be found here.

Try VMware Integrated OpenStack Today



Apples To Oranges: Why vSphere & VIO are Best Bests for OpenStack Adoption

OpenStack doesn’t mandate defaults for compute, network and storage, which frees you to select the best technology. For many VMware customers, the best choice will be vSphere to provide OpenStack Nova compute capabilities.


It is commonly asserted that KVM is the only hypervisor to use in an OpenStack deployment. Yet every significant commercial OpenStack distro supports vSphere. The reasons for this broad support are clear.

Costs for commercial KVM are comparable to vSphere. In addition, vSphere has tremendous added benefits: widely available and knowledgeable staff, vastly simplified operations, and proven lifecycle management that can keep up with OpenStack’s rapid release cadence.


Let’s talk first about cost. Traditional, commercial KVM has a yearly recurring support subscription price. Red Hat OpenStack Platform-Standard 2 sockets can be found online at $11,611/year making the 3 year cost around $34,833[i]. VMware vSphere with Operations Management Enterprise Plus (multiplied by 2 to match Red Hat’s socket pair pricing) for 3 years, plus the $200/CPU/year VMware Integrated OpenStack SnS is $14,863[ii]. Even when a customer uses vCloud Suite Advanced, costs are on par with Red Hat. (Red Hat has often compared prices using VMware’s vCloud Suite Enterprise license to exaggerate cost differences.)



When 451 Research[iii] compared distro costs based on a “basket” of total costs in 2015 they found that commercial distros had a cost that was close to regular virtualization. And if VMware Integrated OpenStack (VIO) is the point of comparison, the costs would likely be even closer. The net-net is that cost turns out not to be a significant differentiator when it comes to commercial KVM compared with vSphere. This brings us to the significant technical and operational benefits vSphere brings to an OpenStack deployment.


In the beginning, it was assumed that OpenStack apps would build in the resiliency that used to be assumed from a vSphere environment, thus allowing vSphere to be removed. As the OpenStack project has matured, capabilities such as VMware vMotion and DRS (Distributed Resource Scheduler) have risen in importance to end users. Regardless of the application the stability and reliability of the underlying infrastructure matters.


There are two sets of reasons to adopt OpenStack on vSphere.


First, you can use VIO to quickly (minutes or hours instead of days or weeks) build a production-grade, operational OpenStack environment with the IT staff you already have, leveraging the battle-tested infrastructure your staff already knows and relies on. No other distro uses a rigorously tested combination of best-in-class compute (vSphere Ent+ for Nova), network (NSX for Neutron), and storage (VSAN for Cinder).


Second, only VMware, a long-time (since 2012), active (consistently a top 10 code contributor) OpenStack community member provides BOTH the best underlying infrastructure components AND the ongoing automation and operational tools needed to successfully manage OpenStack in production.


In many cases, it all adds up to vSphere being the best choice for production OpenStack.


[i] http://www.kernelsoftware.com/products/catalog/red_hat.html
[ii] http://store.vmware.com/store/vmware/en_US/cat/ThemeID.2485600/categoryID.66071400
[iii] https://451research.com/images/Marketing/press_releases/CPI_PR_05.01.15_FINAL.pdf

This Article was written by Cameron Sturdevant,  Product Line Manager at VMware

Upgrade Issues? Not with VIO!

An OpenStack cloud upgrade can be a challenging task for administrators as they manage numerous considerations:

  • How do I upgrade each service’s components while mitigating user impact?
  • Can I skip one or more OpenStack releases during my upgrade, or must I upgrade to every single release between my current implementation and the latest community release?
  • Which control plane services are implemented in the OpenStack deployment and need to be upgraded?
  • How does each OpenStack service’s high availability configuration alter my upgrade process?
  • What is my change control window and will any required service outages remain within required service level agreements (SLA)?

At each OpenStack Summit, there are multiple sessions that discuss these topics, and the Austin Summit was no exception with VMware participating in an upgrade experts’ panel. Continue reading

Upgrade OpenStack with VMware

The OpenStack distribution upgrade is a marquee feature in VMware Integrated OpenStack version 2.0, as we discussed in a previous blog post. Juan Manuel Rey wrote-up a detailed walkthrough for this great feature and shared his insights with the post that follows:

In a previous article I showed the process to patch an existing VIO 1.0 installation, which, as you were able to see, is a clean and easy process. VMware announced VMware Integrated OpenStack 2.0 during VMworld US and it became GA shortly after the show.

This new version of VIO has all OpenStack code updated to the latest Kilo release and comes packaged with many interesting features like Load-Balancing-as-a-Service (LBaaS) and auto-scaling capabilities based on Heat and Ceilometer.

With a new VIO version hot of the press, you can upgrade your VIO 1.0.x environment to 2.0 and take advantage of all those new great goodies. The upgrade process is pretty straightforward and consists of three main stages.

  • Upgrade the VIO Management Server
  • Deploy a new VIO 2.0 environment
  • Perform the data migration

Keep in mind that you will need to have enough hardware resources in your management cluster to be able to temporarily host two full-fledged VIO installations at the same time during the migration process. Just for the sake of transparency, the lab environment where I test the upgrade is based on vSphere 5.5 Update 2, NSX for vSphere 6.1.4 and VIO 1.0.2.

Step 1 – Upgrade VIO Management Server

From the VMware website, download the .deb upgrade package and upload it to the VIO Management Server using SCP.

VIO 2.0 Download

VIO 2.0 Download

Stage the upgrade package.

viouser@vio-oms:~$ sudo viopatch add -l vio-1.0-upgrade_2.0.0.3037964_all.deb
[sudo] password for viouser:
vio-1.0-upgrade_2.0.0.3037964_all.deb patch has been added.
viouser@vio-oms:~$ viopatch list
Name            Version       Type   Installed
--------------- ------------- ------ -----------
vio-1.0-upgrade infra  No
vio-patch-2 infra  Yes

Upgrade the management server.

viouser@vio-oms:~$ sudo viopatch install -p vio-1.0-upgrade -v
Installing patch vio-1.0-upgrade version
Installation complete for patch vio-1.0-upgrade version

Go to the vSphere Web Client, logout and log back in to verify that the new version is correct.

VIO Management Server upgrade is complete!

VIO Management Server upgrade is complete

Step 2 – Deploy a new VIO 2.0 environment

With the VIO Management Server upgraded, it is now time to deploy a fresh 2.0 environment. In the VIO plugin, go to the Manage section in the right pane, and a new Upgrades tab will be available there.

VMware vSphere Web Client VIO Plugin Upgrades Tab

VMware vSphere Web Client VIO Plugin Upgrades Tab

Before starting with the deployment, check in the Networks tab that there are enough free IP addresses (18) for the new deployment. If there aren’t, then add a new IP address range in the same subnet.

VIO management network IP range extension

VIO management network IP range extension

Click on the Upgrade icon (VIO Upgrade Button). Indicate if you want to participate in the customer experience improvement program. My recommendation here is to say yes to help our engineering team to improve the VIO upgrade experience even more, and enter the name for the new deployment.

Updated VIO Deployment Name

Updated VIO Deployment Name

Enter the IP addresses for the public and private load balanced IP addresses. Keep in mind that these IP addresses must belong to the existing VIO 1.0 installation’s API and Management subnets, respectively.

Temporary Load Balancer Virtual IP Address

Temporary Load Balancer Virtual IP Address

In the next and final screen, review the configured values and click Finish. The new environment will be deployed and you will be able to monitor the progress from the Upgrades tab.

New Deployment Based On Kilo Launches

New Deployment Based On Kilo Launches

Step 3 – Migrate the data

With the new environment up and ready, we can start the OpenStack database migration process. From the Upgrades tab right-click on your existing VIO 1.0 installation and select Migrate Data.

Migrate existing OpenStack data to the database in the new deployment

Migrate existing OpenStack data to the database in the new deployment

The migration wizard will ask for confirmation, click OK. During the data migration, all OpenStack services will be unavailable. This will allow the migration process to maintain database consistency during the data transfer.

VIO database migration proceeds

VIO database migration proceeds

When the migration process is finished, the status of the new VIO 2.0 environment will appear as Migrated and the existing VIO 1.0 installation will appear as Stopped.

Database migration complete

Database migration complete

Open a browser and enter the VIO 2.0 Public Virtual IP to access the OpenStack Horizon interface. Login and verify that all your workloads, networks, images, etc. have been properly migrated. Logout from Horizon and go back to the VMware vSphere Web Client. Now that the data has been migrated, we need to migrate the original Public Virtual IP to the new environment.

Right-click on the VIO 1.0 deployment and select Switch To New Deployment.

Production Virtual IP Address Configured on the New Deployment

Production Virtual IP Address Configured on the New Deployment

A new pop-up will appear asking for confirmation since the OpenStack services will be unavailable during the IP reconfiguration.

After the reconfiguration, the new VIO 2.0 deployment will be in Running status and the Public Virtual IP will be the same as the former 1.0 deployment.

OpenStack Upgrade is Complete with a Functional Kilo Cloud!

OpenStack Upgrade is Complete with a Functional Kilo Cloud!

The upgrade procedure is finished. You can now access Horizon using the existing DNS name for your cloud. Verify that everything is still working as expected, and enjoy your new OpenStack Kilo environment!

The Kilo Version of the Horizon Dashboard

The Kilo Version of the Horizon Dashboard

With VIO, upgrading your OpenStack cloud does not have to be a painful experience, VIO provides the best OpenStack experience in a vSphere environment. Kudos to our Team OpenStack @ VMware.

Have fun and happy stacking!


Juan Manuel Rey is a Senior Consultant in the Professional Services Organization and a CTO Ambassador at VMware. He specializes in NSX and cloud architectures. Juan Manuel is highly experienced Unix and VMware professional and an OpenStack advocate internally and externally to VMware. In his spare time he is a Python developer, tries to contribute in some form to the broad OpenStack and VMware communities and blogs about Unix, NSX, OpenStack and VMware technical subjects.

VMware Integrated OpenStack 2.0 is Available Now!

Shortly before VMworld US 2015, we shared with you some of the great new features coming to VMware Integrated OpenStack 2.0. Today, we are excited to announce that VIO 2.0 is generally available. As before, this release is free for all Enterprise Plus customers, and there are two install options:

  1. Full install
  2. Upgrade

Yes, you read that right, it is possible to seamlessly upgrade your VMware Integrated OpenStack 1.0 (Icehouse) release to version 2.0 (Kilo). We modeled our upgrade process, summarized in Figure 1, after the Blue-Green strategy made popular by Jez Humble, Dave Farley, and Martin Fowler.


VMware Integrated OpenStack Blue-Green Upgrade Strategy

Figure 1: VMware Integrated OpenStack Blue-Green Upgrade Strategy

Check out the following video to see a VMware Integrated OpenStack upgrade in action:


You can learn more about how VMware Integrated OpenStack works on the VMware Product Walkthrough site and on the VMware Integrated OpenStack product page. Check it out today!