This solution guide describes the architecture, components, and operation of

VMware Integrated OpenStack on Federation Enterprise Hybrid Cloud.

February 2016

Copyright

2

Copyright © 2016 EMC Corporation. All rights reserved. Published in the USA.

Published February 2016

EMC believes the information in this publication is accurate as of its publication date. The information is subject to

change without notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any

kind with respect to the information in this publication, and specifically disclaims implied warranties of

merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in

this publication requires an applicable software license.

EMC2, EMC, ViPR, VMAX, VNX, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the

United States and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

Federation Enterprise Hybrid Cloud 3.5 VMware Integrated OpenStack Solution Guide

Part Number H14825

Contents

3

Executive summary ................................................................................. 4

We value your feedback! ......................................................................... 5

Solution architecture ............................................................................... 5

Co-existence architecture ........................................................................ 6

VMware Integrated OpenStack control plane .............................................. 9

Network design considerations ............................................................... 11

Software requirements .......................................................................... 12

Hardware requirements ......................................................................... 13

Day 2 Operations .................................................................................. 14

Monitoring ........................................................................................... 18

Conclusion ........................................................................................... 20

References ........................................................................................... 20

Executive summary

4

EMC II, Pivotal, RSA, VCE, Virtustream, and VMware form a unique Federation of

strategically aligned businesses that are free to run individually or together. The EMC

Federation businesses collaborate to research, develop, and validate superior, integrated

solutions and deliver a seamless experience to their collective customers. The Federation

provides customer solutions and choice for the software-defined enterprise and the

emerging third platform of mobile, cloud, Big Data, and social networking.

The Federation Enterprise Hybrid Cloud 3.5 solution is a completely virtualized data center,

fully automated by software. The solution starts with a foundation that delivers IT-as-a-

Service (ITaaS), with options for high availability, backup and recovery, and disaster

recovery. It also provides a framework and foundation for add-on modules such as

application services, Database-as-a-Service (DBaaS), Platform-as-a-Service (PaaS), and

cloud brokering.

This solution guide describes the co-existence architecture for VMware® Integrated

OpenStack (VIO) on Federation Enterprise Hybrid Cloud, which enables IT administrators to

deploy and manage a production grade OpenStack quickly and easily on top of Federation

Enterprise Hybrid Cloud. The guide introduces the architecture, features, and functionality of

the solution and shows the use cases enabled by the solution.

VIO is a VMware-supported OpenStack distribution that helps IT administrators to run a

production-grade OpenStack-based deployment on top of their existing VMware

infrastructure. Building on their existing expertise, IT administrators can foster innovation

and agility by providing their developers with simple vendor-neutral OpenStack application

performance interfaces (APIs) on top of VMware’s Software-Defined Data Center (SDDC)

infrastructure. Key administration capabilities, including install, upgrade, troubleshooting,

and cost-visibility are provided via deep integration with already familiar VMware

management tools, enabling quick implementation and lower total cost of ownership.

This guide is for cloud administrators and developers who want to create and manage

resources with an OpenStack deployment that is fully integrated with VMware vSphere on

Federation Enterprise Hybrid Cloud.

This guide is also intended for the stakeholders for OpenStack cloud, in which application

developers want to consume infrastructure resources in the fastest and quickest possible

way through OpenStack APIs. This solution intends to further build application lifecycle

management on top of these APIs using DevOps, continuous integration, and continuous

development tools and methods.

The following are some key benefits of this solution:

OpenStack Powered Platform Certified (DefCore 2015.04)

Enterprise-grade OpenStack cloud on Federation Enterprise Hybrid Cloud

Advanced knowledge of OpenStack is not required to implement this solution

Simplified OpenStack operations

Single vendor support

Multi-language support: English, German, French, Traditional Chinese, Simplified

Chinese, Japanese, and Korean

Free for all VMware vSphere Enterprise Plus Edition customers, including VMware

vSphere with Operations Management Enterprise Plus and VMware vCloud Suite

customers

Federation

solutions

Document

purpose

Solution purpose

Key benefits

We value your feedback!

5

The following documents describe the architecture, components, features, and functionality

of the Federation Enterprise Hybrid Cloud 3.5 solution:

Federation Enterprise Hybrid Cloud 3.5: Foundation Infrastructure Reference

Architecture Guide

Federation Enterprise Hybrid Cloud 3.5: Concepts and Architecture Guide

Federation Enterprise Hybrid Cloud 3.5: Operations Guide

Federation Enterprise Hybrid Cloud 3.5: Security Management Guide

This guide provides external references where applicable. EMC recommends that users

implementing this solution are familiar with these documents.

EMC and the authors of this document welcome your feedback on the solution and the

solution documentation. Contact EMC.Solution.Feedback@emc.com with your comments.

Authors: Shree Das, Traci Morrison.

VIO is a full OpenStack distribution that dramatically simplifies OpenStack deployment. It

allows developers to produce an operational cloud with a wide range of enterprise-grade

data center services in days instead of months.

VIO enables accelerated OpenStack deployment through integrated drivers for VMware

technologies and OpenStack source code that is optimized and hardened to run on VMware

products. IT developers therefore gain the benefits of a public cloud experience through

simple, vendor-neutral OpenStack APIs to a private VMware Software-Defined Data Center

(SDDC). Users also gain access to an ecosystem of development resources, and the freedom

to run workloads across a heterogeneous infrastructure.

VIO simplifies OpenStack operations by using tested VMware technologies such as VMware

vRealize® Operations Manager™ for monitoring and troubleshooting, and VMware vRealize®

Log Insight™ for diagnostics across OpenStack service logs. Users with VMware experience

can install and manage an OpenStack cloud from existing VMware vSphere® or VMware

vCenter Server™ interfaces without extensive OpenStack expertise.

As shown in Figure 1, the VIO architecture connects vSphere resources to the following

components:

Compute

Networking

Block Storage

Image Service

Object Storage

Identity Service

Horizon

Telemetry

Orchestration

Essential reading

Overview

Co-existence architecture

6

Figure 1. OpenStack Framework with VMware technologies

VIO is deployed through the VIO Manager vApp in vCenter. The VIO Manager provides a

workflow that guides you through and completes the VIO deployment process. With VIO

Manager, you can specify your management and compute clusters, configure networking,

and add resources. Post-deployment, you can use VIO Manager to add components or

otherwise modify the configuration of your VIO cloud infrastructure.

The use of OpenStack in the private cloud has grown tremendously. Customers want to

consume OpenStack for their DevOps to operate and manage the cloud. OpenStack provides

developers the ability and agility to innovate faster by maximizing the infrastructure.

Federation Enterprise Hybrid Cloud provides co-existence architecture to support VIO to

provide a programmable and API-friendly software defined IaaS.

This co-existence architecture provides both the cloud administrator and cloud developer a

way to operate and manage the two distinct platforms. A cloud administrator can use

vRealize Automation to fully operate and manage the cloud, whereas a cloud developer can

use OpenStack Horizon or OpenStack command line interfaces (CLIs) and APIs to operate

and manage the workloads.

Figure 2 shows the co-existence architecture of the solution, which is deployed on a

Federation Enterprise Hybrid Cloud platform. The solution adds three separate vSphere

clusters, VIO components, a dedicated vCenter, and VMware NSX®-v component specifically

related to co-existence architecture for VIO.

VIO is implemented as compute, edge, and management clusters in your vSphere

environment.

The compute cluster handles all tenant workloads. Your VIO deployment can have multiple

compute clusters. VIO Manager creates one compute driver instance in the management

cluster for each compute cluster.

The management cluster contains the virtual machines that comprise your OpenStack cloud

deployment. It also contains the memory cache (memcache), message queue (RabbitMQ),

load balancing, dynamic host configuration protocol (DHCP), and database services.

Co-existence architecture

7

Note: DHCP is only available when not using NSX.

This solution guide describes the following OpenStack-specific functionality, in addition to

the core Federation Enterprise Hybrid Cloud functionality:

Developer-friendly OpenStack services and application performance interfaces (APIs)

Simplified OpenStack deployment and implementation

“One call” support

Figure 2. VIO co-existence architecture

The Federation Enterprise Hybrid Cloud management, network, and tenant resources for the

solution are divided into several pods, as shown in Figure 2, with each pod performing a

solution-specific function.

Core Pod

The Core Pod hosts a core set of resources that must exist before the remainder of the cloud

can be deployed. These core resources include VMware vCenter Server, Microsoft SQL

Server 2012, and VMware® Manager™.

Automation Pod

The Automation Pod hosts the virtual machines that automate and manage the cloud

infrastructure that supports the workloads consumed by cloud tenants. The Automation Pod

supports the components responsible for functions such as the user portal and automated

provisioning, monitoring, metering, and reporting.

NEI Pod

The Network Edge Infrastructure (NEI) Pod hosts the VMware NSX® Edge™ appliances and

VMware NSX Controller nodes and becomes the convergence point at which the physical and

virtual networks connect.

Workload Pods

The Workload Pods are configured and assigned in vRealize Automation as shared resources

to host application virtual machines deployed by the different business groups in the hybrid

Co-existence architecture

8

cloud environment. These Workload Pods are deployed as VMware vSphere clusters in

vCenter Server endpoints.

Capabilities and limitations

Table 1 lists some of the capabilities and limitations of the co-existence architecture within

Enterprise Hybrid Cloud.

Capabilities and limitations of the co-existence architecture Table 1.

Capabilities Limitations

Simplified OpenStack Deployment with a co-

existence architecture on Enterprise Hybrid Cloud

Requires a separate vCenter

Uses proven VMware Infrastructure Requires a dedicated NSX instance within

Enterprise Hybrid Cloud and ties to VIO vCenter

Enterprise-grade OpenStack Cloud with

developer friendly OpenStack services and APIs.

Does not support integration with vRealize

Automation and vRealize Orchestrator

Advanced virtualized network services

(private networks, floating IPs, logical routing, security groups) with NSX

Does not support integration with vRealize

Business

Unified Monitoring with vRealize Operations

and vRealize Log Insights

The management sizing provided by the

sizing tool will be based on the total number of virtual machines that you enter during sizing and is limited to 10, 000 virtual machines (as the vCenter powered-on limit). If you intend to monitor virtual machines from both vCenters, and that total exceeds 10, 000 virtual machines, then your management and monitoring sizing will be under-equipped for the combination of the Enterprise Hybrid Cloud and VIO vCenters.

Native backup and restore No Storage-as-a-Service (STaaS), Backup-

as-a-Service (BaaS), or Disaster Recovery-as-a-Service (DRaaS) for VIO

Single Vendor Support Out-of-box control plane supports thousands

of objects. Also, ties back to vCenter’s limit of 10,000 powered on virtual machines. For further scale and concurrency details, contact VMware sales.

Free for all VMware vSphere® Enterprise Plus Edition™ customers

Co-existence VIO environment

In the context of co-existence architecture VIO on Federation Enterprise Hybrid Cloud, in

addition to the pod architecture shown in Figure 2, you must dedicate three additional pods

to support VIO deployment, as shown in Figure 3.

VMware Integrated OpenStack control plane

9

Figure 3. vSphere network design

Management Pod

The Management Pod requires a minimum of three hosts to deploy the VIO components. It

has a core set of resources that must exist before OpenStack can be deployed. These core

resources include a dedicated vCenter Server, VIO management server, VMware NSX-v

Manager, and VIO components.

Edge Pod

The Edge Pod hosts the VMware NSX Edge appliances, logical distributed routers (LDRs),

and VMware NSX Controller nodes and becomes the convergence point at which the physical

and virtual networks connect.

Workload Pods

The Workload Pods are configured and assigned to tenant resources to host application

virtual machines in the OpenStack cloud environment. These Workload Pods are deployed as

compute nodes in VIO.

The VIO management component, as shown in Figure 4, contains the deployed OpenStack

component and management virtual machines.

VMware Integrated OpenStack control plane

10

Figure 4. VIO architecture management topology

VMware vSphere High Availability (HA) is built into the control plane. Instead of relying

solely on the vSphere HA features, the solution includes a pair of HAProxy load balancer

virtual machines, a pair of controller virtual machines, a pair of memcached virtual

machines, and a pair of RabbitMQ virtual machines. The database cluster consists of three

MariaDB virtual machines that implement a Galera cluster, which has a quorum of three

nodes.

The compute driver virtual machine is the only control plane component solely protected by

vSphere HA. There is one compute driver virtual machine per compute cluster managed by

OpenStack. In production, we expect that customers will have more than one cluster in the

OpenStack deployment. In the unlikely event of the failure of the hypervisor hosting the

Compute Driver1 virtual machine, the remaining cluster can service user requests in the

short amount of time that vSphere HA takes to recover the failed Compute driver virtual

machine.

Table 2 lists the components of the management cluster.

Management cluster components Table 2.

Component Description Nodes

Load balancers Provide HA and enable

horizontal scale-out architecture

2 (1 active, 1 standby)

Databases Instances of MariaDB that

store OpenStack metadata

3 (1 active, 2 standby)

VIO controller Contains all OpenStack

services, including Compute, Block Storage, Image Service, Identity Service, and Object Storage

2 (both active)

Network design considerations

11

Component Description Nodes

Memcache Enables production-grade performance for the Identity Service

2 (both active)

Rabbit MQ The message queue service

used by all OpenStack services

2 (both active)

Compute driver Contains a subset of compute

processes that interact with the compute clusters to manage virtual machines

1 per compute cluster

VIO Manager Service vApp used to manage the

VIO vApp

1

VIO template Base template for creating all OpenStack service virtual

machines

1

Ceilometer databases (optional)

Instances of MongoDB or NoSQL databases for use by Ceilometer

3 (1 active, 2 standby)

Before you begin the VIO deployment, ensure that you have three VMware vSphere

Distributed Switches (VDSs). VMware typically recommends three possible configurations;

however, in this design we choose to have three VDSs to segregate the network traffic to

ensure more control and isolation for each type of network configuration. Refer to “Prepare

the vCenter Instance for NSX-V -Based Deployment” in the VMware Integrated OpenStack

Installation and Configuration Guide for more information on the configuration options.

Figure 5 describes each pod and the associated VDS with each network type and VLAN.

Figure 5. Network design considerations

Software requirements

12

For VIO deployments based on NSX-v, the API access, management, transport, and external

networks each require a separate and dedicated VLAN.

Request that your network administrator prepare the necessary VLANs, as described in

Table 3.

VLANs Table 3.

VLAN Description

API access network Provides access for users to the OpenStack services through APIs or the VIO dashboard:

Trunk all hosts in the Management cluster to this VLAN.

Make externally accessible.

Requires five or more continuous IP addresses.

Management network Carries traffic among the management components:

Trunk all hosts in the Management cluster to this VLAN.

Trunk all hosts in the Compute cluster to this VLAN.

Requires 18 or more continuous IP addresses (21 if you add the Ceilometer component).

Enable Layer 2 or Layer 3 access to this VLAN for the following components:

vCenter server

NSX-v Manager

NSX-v Controller

If you are deploying the NSX-v Manager and NSX-v Controller virtual machines on the Management cluster, you must trunk their hosts to the Management network.

Transport Carries traffic among the OpenStack

instances:

Trunk all hosts in the Compute cluster to this VLAN.

Trunk all hosts in the NSX-v Edge cluster to this VLAN.

External Provides external user access to the instances. Trunk all hosts in the NSX-v Edge cluster to this VLAN.

Note: The Maximum Transmission Unit (MTU) settings for the External VLAN must be configured to support 1600 bytes. See Configuring jumbo frame support on NSX for vSphere and VCNS for more information.

Metadata service Used for metadata proxy communication with

controller nodes.

Before you begin the VIO deployment on the Federation Enterprise Hybrid Cloud 3.5

environment, ensure that the software components align with the Federation Enterprise

Hardware requirements

13

Hybrid Cloud foundation. The version prerequisites for vSphere, ESXi hosts, and the NSX-v

product are described in Table 4.

Software requirements Table 4.

Software Version Description

VMware vSphere 6.0.U1a (Build 3073146) vSphere 6 Enterprise Plus

VMware vCenter Appliance 6.0.U1 (Build 3040890) VMware vCenter Server

VMware Integrated OpenStack

2.0 OpenStack Kilo release

VMware NSX 6.2.1 (Build 3300239) VMware NSX

VMware vRealize Operations Manager

6.1 (Build 3038036) vRealize Operations Manager

VMware vRealize Log Insight 3.0 (Build 3021606) vRealize Log Insight

The hardware requirements described in Table 5 are based on the number of virtual

machines used for each component. For example, two virtual machines are used for load

balancing. Each virtual machine requires two CPUs for a total requirement of four CPUs. The

requirements vary depending on whether your OpenStack deployment uses VDS or NSX-v

with the Networking component.

Hardware requirements Table 5.

Component Virtual

machines

CPU RAM (GB) Disk space (GB)

VMware Integrated

OpenStack Manager

1 2 (2 per virtual machine) 4 (4 per virtual

machine)

25

Load balancing

service

2 4 (2 per virtual machine) 8 (4 per virtual

machine)

40 (20 per virtual

machine)

Database service 3 12 (4 per virtual machine) 48 (16 per virtual machine)

240 (80 per virtual machine)

Memory cache service

2 4 (2 per virtual machine) 32 (16 per virtual machine)

40 (20 per virtual machine)

Message queue service

2 8 (4 per virtual machine) 32 (16 per virtual machine)

40 (20 per virtual machine)

Controllers

2 16 (8 per virtual machine) 32 (16 per virtual machine)

160 (80 per virtual machine)

Compute service

(Nova CPU)

1 2 (2 per virtual machine) 4 (4 per virtual machine)

20 (20 per virtual machine)

DHCP service (VDS deployments only)

2 8 (4 per virtual machine) 32 (16 per virtual machine)

40 (20 per virtual machine)

TOTAL 15 56 192 605

Day 2 Operations

14

NSX-v components

Additional CPU, RAM, and disk space is required for the NSX-v components described in

Table 6 if they are deployed with VIO. It is a best practice to deploy the NSX-v Manager and

NSX-v Controller nodes in the Management cluster.

NSX-v components Table 6.

Component Virtual

machines

CPU RAM (GB) Disk space

(GB)

NSX-v

Controller

3 12 (4 per virtual

machine)

12 (4 per virtual

machine)

60 (20 per

virtual machine)

NSX-v Manager 1 4 (4 per virtual machine)

12 (12 per virtual machine)

60 (60 per virtual machine)

NSX-v Edge (see Note below)

Varies; created on demand

1 per Edge DHCP virtual machine, 2 per Edge router virtual machine

0.5 per Edge DHCP virtual machine, 1 per Edge router virtual machine

0.5 per Edge DHCP virtual machine, 1 per Edge router virtual machine

TOTAL 4 plus Edge requirements

16 plus Edge requirements

24 plus Edge requirements

120 plus Edge requirements

Note: When you create a logical subnet or logical router, a new Edge virtual machine is

dynamically created to serve this request if an existing Edge node cannot.

Update your VIO deployment using the VIO Manager vApp or CLI commands to install and

apply patches.

After installing a patch, you can revert to a previous version if required.

Install patch using the vSphere Web Client

VMware provides updates in the form of Debian patches. Patches that do not affect the

infrastructure of the VIO deployment can be applied using the VIO Manager vApp.

Prerequisites

vSphere Web Client

Some patches might require you to shut down the VIO service before continuing.

Procedure

To install a patch using the vSphere Web Client:

1. Download the Debian patch from VMware. If you do not know where to obtain the

patch, go to the VIO product page or consult with VMware.

2. In the vSphere Web Client, select Home > Inventories, and click the VMware

Integrated OpenStack icon.

3. Click the Manage tab.

4. Click the Updates tab.

5. Add the patch to VIO Manager by clicking the green plus sign and browsing to the

file location.

6. Select the patch and click Choose.

7. Install the patch.

Update VMware

Integrated

OpenStack

Day 2 Operations

15

If you can install the patch by using the VIO Manager vApp, the Apply option

appears in the Patch Action column on the Updates tab.

If the Apply option does not appear in the Patch Action column, click More details

in the Patch Description column to access instructions for installing patches using

the CLI.

After you install a patch, the value in the Patch Status column on the Updates tab

changes to Installed.

8. Log out of the vSphere Web Client.

9. Log in to the vSphere Web Client. Ignore any error messages when logging in.

10. Restart the VIO services.

It is a best practice to periodically back up your OpenStack management server and

database. Perform backup operations in the CLI for the VIO Manager.

Prerequisites

You must log in with administrative or super-user (sudo) privileges to perform backup

operations. You should have network file system (NFS) storage mount points and IP details

for the NFS storage.

Procedure

To back up VIO:

1. Using SSH, log in to the VIO Manager as viouser.

2. Switch to the root user.

3. At the command prompt, type sudo su-

4. Use the viocli backup management server command to back up the OpenStack

management serve, as shown in Figure 6:

Viocli backup –v mgmt_server [-d DEPLOYMENT_NAME] <NFS_VOLUME>

Figure 6. Command used to back up the management server

The backup file is automatically labeled with the timestamp vio_ms_yyyymmddhhmmss, as

shown in Figure 7.

Figure 7. Timestamp

You should also backup the OpenStack database, using the following options:

-d DEPLOYMENT: specifies the names of the deployment database to be backed up

NFS_VOLUME: Specifies the NFS volume for the backup file.

viocli backup openstack_db \

[-d DEPLOYMENT] \

<NFS_VOLUME>

Back up VMware

Integrated

OpenStack

Day 2 Operations

16

If a crash occurs, you can restore your VIO management server and OpenStack database

from a previous backup.

Procedure

To perform the restore operations in the CLI for the VIO Manager:

1. Using SSH, log in to the VIO Manager as viouser.

2. Switch to the root user.

3. At the command prompt, type sudo su-

4. Use the viocli restore mgmt_server command to restore the OpenStack

management server from the backup file, as shown in Figure 8:

Viocli restore mgmt_server [-d DEPLOYMENT] <BACKUP_NAME>

<NFS_VOLUME>

Figure 8. CLI restore

You should also use the viocli restore database command to restore the OpenStack

database, as shown in Figure 9:

Viocli restore openstack_db [-d DEPLOYMENT] <BACKUP_NAME> <NFS_VOLUME>

Figure 9. OpenStack database backup

It is a best practice to periodically back up your OpenStack management server and

database. Perform backup operations in the CLI for the VIO Manager. In the event of a disk

failure or another critical issue, you can recover the individual nodes in your VIO deployment

using the CLI.

When you recover a VIO node, it returns to the state of a newly deployed node. To recover

a database node, you must recover to a backup file. See Back up VMware Integrated

OpenStack for more information.

Procedure

To perform failure recovery:

1. Using SSH, log in to the VIO Manager.

2. Switch to root user sudo-su

3. Switch to verbose mode:

viocli recover <-v | -verbose>

4. View the help options:

viocli recover <-h | -help>

5. Recover the OpenStack nodes by node or by role:

a. Recover the database node:

viocli recover <[-r ROLE -dn BACKUP_NAME]|[-n NODE -dn

BACKUP_NAME]> -nfs NFS_VOLUME

Restore VMware

Integrated

OpenStack

Failure recovery

Day 2 Operations

17

Table 7 describes the command options.

Command options Table 7.

Option Description

-n NODE Recovers the database nodes specified by the virtual machine name recovered by node name. You can specify multiple nodes in one command.

Use the virtual machine name as it appears in VIO Manager (VMware Integrated OpenStack > OpenStack Deployments > [Deployment Name]).

For example, the following command recovers from the specified NFS backup file all named database nodes: VIO-DB-0, VIO-DB-1, and VIO-DB-2:

viocli recover –n VIO-DB-0 VIO-DB-1 VIO-DB-2 –dn vio_os_db_20150830215406 -nfs 10.146.29.123:/backups

-r ROLE Recovers all the database nodes in the specified group name. You can specify multiple roles in one command.

Use the group name as it appears in VIO Manager.

For example, the following command recovers from the specified NFS backup file all nodes in the database node group:

viocli recover -r DB –dn vio_os_db_20150830215406 –nfs 10.146.29.123:/backups

-dn BACKUP_NAME Indicates the timestamp label of the backup file to be used to

restore the database.

-nfs NFS_VOLUME Indicates the NFS host where the backup file is located.

b. Recover any non-database node:

viocli recover <[-r ROLE]|[-n NODE]>

Table 8 describes the command options.

Command options Table 8.

Option Description

-n NODE Recovers the nodes specified by virtual machine name. You can specify multiple nodes in one command. Use the virtual machine name as it appears in VIO Manager.

For example, the following command recovers the VIO-Memcache-0 node:

viocli recover -n VIO-Memcache-0

-r ROLE Recovers all the nodes in the specified group name. You

can specify multiple roles in one command. Use the group name as it appears in VIO manager.

For example, the following command recovers all nodes in the memcache node group:

viocli recover -r Memcache

Tip: You can use the viocli show command to list all nodes and their roles in your VIO

deployment.

Monitoring

18

6. Verify the node is running by checking its status in VIO Manager by selecting

VMware Integrated OpenStack > OpenStack Deployments > [Deployment

Name]. Depending on your deployment, the recovery process might take a few

minutes.

The VMware vRealize® Operations Management Pack™ provides comprehensive operational

capabilities for managing an OpenStack environment. It provides out-of-the-box

dashboards, reports, inventory views, and alerts complete with remediation actions.

The vRealize OpenStack Management Pack collects data from OpenStack APIs through a

Hyperic agent for OpenStack Process data, and correlates OpenStack tenant and inventory

information with vSphere and NSX Management Packs.

Figure 10 shows the vRealize OpenStack Management Pack home page.

Figure 10. vRealize Operations Management Pack home page

The management pack is intended for administrators who are operating an OpenStack

cloud. It includes the following key features:

Performance and availability monitoring of OpenStack infrastructure and services

Pre-defined dashboards for:

Cloud controller’s health

Computer infrastructure

vCenter storage infrastructure

Network infrastructure

Tenant’s inventory, health, and quota usage

Visibility into cloud resources running on any VMware ESX

vRealize

Operations

Management

Monitoring

19

Advanced performance and capacity analytics for OpenStack inventory running on any

VMware ESX™ and NSX technologies.

Pre-defined alerts for several common OpenStack operational problems.

Report templates for the following objects:

OpenStack Tenant Inventory

OpenStack Infrastructure Capacity

OpenStack Alerts

You can download the management pack for OpenStack at

https://solutionexchange.vmware.com.

The VMware vRealize Log Insight Content Pack, shown in Figure 11, collects machine-

generated data from the various OpenStack components and graphically represents this

data with action-oriented dashboards. OpenStack administrators can quickly see which

components are failing, where there are abnormal activities, and via alerting, can be notified

of high severity level, and/or outage conditions. This content pack reduces the complexity of

checking log files within every component to determine where there are issues, thus offering

faster time to resolution.

Figure 11. vRealize Log Insight Content Pack dashboard

vRealize Log Insight key features:

Aggregates OpenStack logs in to 11 OpenStack specific dashboards with 59 widgets.

Monitors trends, critical events, and activities.

Intelligent analytics leverages machine learning of text-based machine messages, with

advanced search to help troubleshoot and isolate OpenStack problems quickly.

Compatible with current versions of VIO distributions.

The vRealize Log Insight Content Pack helps rationalize, structure, and analyze logs

uniformly, irrespective of whether the logs are coming from Cinder, Nova, Neutron,

Keystone, and other components. Log files are filtered via OpenStack regular expressions,

stored and structured in a human readable database-like repository, analyzed based on

high, medium, and low log activities, and are graphically displayed with charts, graphs, and

trend reports. Usage trends, API response times, error rates, log in activities, virtual CPU

vRealize Log

Insight

Conclusion

20

and memory consumption, images active versus inactive are all activities reported and

displayed with the vRealize Log Insight Content Pack.

While this content pack can work with the most current versions of OpenStack distribution,

there is an additional dashboard and set of widgets that have been developed for the VIO

distribution. This dashboard provides specific views on the number of API requests to the

compute, network, and storage subcomponents, VIO events, and VIO errors.

Federation Enterprise Hybrid Cloud enables customers to build an enterprise-class, scalable,

multitenant platform for complete infrastructure service lifecycle management. The solution

uses the best of EMC and VMware products and services to deliver VIO for developers on a

Federation Enterprise Hybrid Cloud deployment with the following principles:

Developer-friendly OpenStack services and APIs

Simplified OpenStack deployment and implementation

Security and compliance

Monitoring and service assurance

The following guides, available on EMC.com, provide information about various aspects of

the Federation Enterprise Hybrid Cloud solution:

Federation Enterprise Hybrid Cloud 3.5: Foundation Infrastructure Reference

Architecture Guide

Federation Enterprise Hybrid Cloud 3.5: Concepts and Architecture Guide

Federation Enterprise Hybrid Cloud 3.5: Administration Guide

Federation Enterprise Hybrid Cloud 3.5: Infrastructure and Operations Guide

Federation Enterprise Hybrid Cloud 3.5: Security Management Guide

Federation Enterprise Hybrid Cloud 3.5: Microsoft Applications Foundation Solution

Guide

The following documentation on the VMware website provides additional and relevant

information:

VMware Integrated OpenStack Installation and Configuration Guide

VMware Integrated OpenStack Quick Start Guide

VMware Integrated OpenStack Administrator Guide

VMware Integrated OpenStack User Guide

Federation

documentation

VMware

documentation