Home > Blogs > OpenStack Blog for VMware


VMware Integrated OpenStack : First Look

Hello everyone,

We are very happy to announce the general availability of VMware Integrated OpenStack 1.0. Our engineering team worked very hard to deliver a beautiful OpenStack experience and we are very happy that we are finally able to share it with our customers and partner. Customers and partners with myvmware accounts can download it from here.

As of today, We are also starting a serious of blog posts with more technical details about the product, and we are kicking it off today with a guest blog post from our dear friend Juan Manuel Rey:

A first look into VMware Integrated #OpenStack 

VMware Integrated OpenStack,  beta announced during last year VMworld in San Francisco and has officially released last February by VMware, is now finally GA.

For me this is a very special release because I have been one of the lucky internal adopters and beta testers of VIO. I have spent many hours working with several VIO builds and trying to help our incredible engineering team. This is in my opinion a really solid and well designed product and will be a game changer in the OpenStack world. Honestly I cannot be more excited.

IMAGE01

VMware Integrated OpenStack is basically a VMware supported OpenStack distribution prepared to run on top of an existing VMware infrastructure. VMware Integrated OpenStack will empower any VMware Administrator to easily deliver and operate an Enterprise production grade OpenStack cloud on VMware components. This means that you will be able at to take advantage of all VMware vSphere great features like HA, DRS or VSAN for your OpenStack cloud and also extend and integrate it with other VMware management components like vRealize Operations and vRealize Log Insight.

VMware Integrated OpenStack components

VIO is made by two main building blocks, first the VIO Manager and second OpenStack components. It is packaged as an OVA file that contains the Manager server and an Ubuntu Linux virtual machine to be used as the template for the different OpenStack components.

The OpenStack services in VMware Integrated OpenStack are deployed as a distributed highly available solution formed by the following components:

  • OpenStack controllers. Two virtual machines running Horizon Dashboard, Nova (API, scheduler and VNC) services, Keystone, Heat, Glance, and Cinder services in an active-active cluster.
  • Memcached cluster.
  • RabbitMQ cluster, for messaging services used by all OpenStack services.
  • Load Balancer virtual machines, an active-active cluster managing the internal and public virtual IP addresses.
  • Nova Compute machine, running the n-cpu service.
  • Database cluster. A three node MariaDB Galera cluster that stores the OpenStack metadata.
  • Object Storage machine, running Swift services.
  • DHCP nodes. These nodes are only required if NSX is not selected as provider for Neutron.

Installation requirements

To be able to successfully deploy VMware Integrated OpenStack you will need at least the following:

  • One management cluster with two to three hosts, depending on the hardware resources of the hosts.
  • One Edge cluster. As with any NSX for vSphere deployment it is recommended to deploy a separate cluster to run all Edge gateway instances.
  • One compute cluster to be used by Nova to run instances. One ESXi host will be enough but again that will depend on how much resources are available and what kind of workloads you want to run.
  • Management network with at least 15 static IP addresses available.
  • External network with a minimum of two IP addresses available. This is the network where Horizon portal will be exposed and that will be used by the tenants to access OpenStack APIs and services.
  • Data network, only needed if NSX is going to be used. The different tenant logical network will be created on top of this, the management network can be used but it is recommended to have a separate network.
  • NSX for vSphere. It has to be setup prior to VIO deployment if NSX plugin is going to be used with Neutron.
  • Distributed Port Group. In case of choosing DVS-based networking a vSphere port-group tagged with VLAN 4095 must be setup. This port group will be used as the data network.

The hardware requirements are around 56 vCPU, 192GB of memory and 605GB of storage. To that you have to add NSX for vSphere required resources like the NSX Manager, the three NSX Controllers and the NSX Edge pool, if NSX is going to be used.

Anyway in a future post I will review in detail all the pre-requisites and their setup process for VMware Integrated OpenStack, and the integration between NSX-v and Neutron.

VMware Integrated OpenStack Installation

Now that we have seen a bit of VMware Integrated OpenStack I am going to show how to perform an installation.

Deploying VMware Integrated OpenStack Manager

The first step is to deploy VIO OVA on our management cluster. From vSphere Web Client launch the Deploy OVF Template wizard and enter the URL to the VIO OVA file.

IMAGE02

Accept the EULA and proceed to configure the template. First as with any OVA template enter the name and the folder,

IMAGE03

Select the datastore and the storage format.

IMAGE04

Select the network for VIO Manager.

IMAGE05

Now we will customize the template, this includes entering the VIO Manager server networking settings, NTP, SSO lookup service URL and Syslog server.

IMAGE06

Go through the next two screens, click finish and start the deployment. Once it is finished you will have a new vApp with the two virtual machines. Our next step is to register the management server with vCenter, power on the OMS vApp and when the management server is fully started logout of vSphere Web Client. Log in back to vSphere Web Client, you will notice a new icon in the Home page.

IMAGE07

Access the VIO plugin interface and in the Summary you should see that VIO Manager has automatically registered itself with vCenter.

IMAGE08

From this screen you can also change the VIO Manager server in case you need to re-deploy a new one. To do so select the management server in the pop-up and click OK.

IMAGE09

Accept the SSL certificate to finish the procedure.

IMAGE10

VIO Manager Server will now be displayed as connected in the Summary tab.

IMAGE11

Deploying OpenStack

With VIO Manager running and connected to our vCenter it is time now to deploy OpenStack. Proceed to the Getting Started tab and click Deploy OpenStack.

IMAGE12

A new wizard will be launched. In the first screen we must select the deployment type. VIO allows deploying a new OpenStack installation or deploying from a previously saved template file.

IMAGE13

Provide the vCenter administrative credentials.

IMAGE14

Select the management cluster where we are going to deploy VIO.

IMAGE15

Next you need to configure the Management and External networks. Select the appropriate vSphere port-groups for each network and fill in the network ranges, gateway, netmask and DNS server fields.

IMAGE16

Enter the values for the load balancer configuration:

  • Public Virtual IP address
  • Public Hostname, this hostname must resolve to the Public IP address.

IMAGE17

Add a cluster to be used for Nova.

IMAGE18

Add the datastores to be used by Nova to store the different instances. If you have a VSAN datastore keep in mind that to be able to use it with Nova the images stored in Glance have to be streamOptimzed.

IMAGE19

Select the datastore to be used by Glance image service.

IMAGE20

Configure Neutron networking. For Neutron there are two different options:

  • DVS-based networking
  • NSX networking

For DVS simply select the Virtual Distributed Switch where you created the port-group for the data network with the VLAN 4095 configured.

For NSX deployment you must enter:

  • NSX Manager IP address.
  • NSX Manager administrative username.
  • NSX Manager administrative user password.
  • VDN Scope. Basically the Transport Zone in NSX-v to be used as transport layer for data traffic.
  • Edge Cluster. A vSphere cluster to deploy the NSX Edge instances.
  • Virtual Distributed Switch for NSX networking.
  • External Network. This a port group to be used as external network by instances in OpenStack via a virtual router. This port group should be accessible from compute, management and edge clusters.

IMAGE21

During the Neutron configuration the wizard will connect to the NSX Manager with the provided credentials and will ask to accept the SSL certificate.

IMAGE22

In the next screen the wizard will ask for the OpenStack admin user, password and project. Also you can select the Keystone type option:

  • Database
  • Active Directory as LDAP Server.

IMAGE23

Finally set the syslog server, it is not mandatory to set this value but it is highly recommended.

IMAGE24

Review the configuration and click Finish.

The deployment will take some time, depending on your storage backend. In my testing lab took around one hour, but it is a nested environment running on NFS so you can expect much better times deploying in a real world setup. When it is finished you can review the different components of VIO with vSphere Web Client in VMs and Templates, there would be a new folder structure containing all VIO virtual machines.

IMAGE25

 Validate your VIO installation

In your favorite browser open an HTTPS session against the public hostname or virtual IP address configured during VIO installation. The Horizon portal login page will display.

IMAGE26

Enter the admin credentials and OpenStack admin Overview page will show up. The access the Hypervisors area and check that the selected cluster for Nova appears there.

IMAGE27

At this point VIO is setup and you can start to work in Horizon or using the CLI as with any other OpenStack distribution.

Have fun and happy stacking!

Juanma.

“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.”

5 thoughts on “VMware Integrated OpenStack : First Look

  1. Pei Qian

    Hi,

    I’ve deployed VIO vAPP succesfully, but there is no VIO icon in home inventory. Do you know why? The vCenter I used is 6.0

    Reply
  2. Nhut

    I have installed VIO on my system. But I can’t connect with VIO API.
    Please help!!! Thanks in advance!

    Reply
  3. nashers

    Nice blog on what all the components of VMware Integrated OpenStack are, and how to install VMware Integrated OpenStack, the requirements are quite a lot thought

    Reply
    1. Trevor Roberts Jr.Trevor Roberts Jr.

      Hello NingZhou,

      Thank you for your question and for reading the blog post. With OpenStack, users are encouraged to use SSH keys they generate themselves or PEM files generated by OpenStack to login to their instances.

      We demonstrate how that works in our OpenStack Instance YouTube video.

      If you have any further questions after watching the video, please check out our OpenStack VMware Community where various members of the VIO team answer user questions!

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

*