Table of Contents

Building VMware Software-Defined Data Centers

Credits

About the Author

About the Reviewer

www.PacktPub.com

eBooks, discount offers, and more

Why subscribe?

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Downloading the color images of this book

Errata

Piracy

Questions

1. The Software-Defined Data Center

The demand for change

Business challenges:  The use case

The business view

The IT view

Tools to enable SDDC

The implementation journey

The process category

The process change example in Tom's organization

The people category

The people example in Tom's organization

The technology category

The technology example in Tom's organization

Why are these three topics so important?

Additional possibilities and opportunities

The self-healing data center

The self-scaling data center

Summary

2. Identify Automation and Standardization Opportunities

Automation principles

Day two automation

The 80:20 rule

Think big, start small

The efficiency bottleneck

Bringing it all together

Script or workflow

Identifying processes and how to automate them

IT delivery frameworks

What if no CMDB or ticket management is in place

Achieving standardization

Deployment standards

Organization automation examples

Simple VM deployment

The hybrid cloud deployment

The analysis of the hybrid cloud deployment

The better approach

Summary

3. VMware vSphere: The SDDC Foundation

Basics and recommendations for vSphere in the SDDC

Distributed Resource Scheduler

Resource pools

Storage DRS

Distributed Virtual Switch

Host Profiles

vSphere configuration considerations

Separate management cluster

Management cluster resource considerations

Separate management VDS

The payload cluster

The resource pool approach

The cluster approach

Storage Policy Based Management

SPBM definition

Integrated vSphere automation

Best practices and recommendations

Summary

4. SDDC Design Considerations

The business use case

The business challenge

The CIO challenge

Constraints, assumptions, and limitations

Constraints

Limits

Assumptions

Scalability and future growth

vRealize Automation

vRealize Code Stream

vRealize Orchestrator

vRealize Operations Manager

vRealize Business

vRealize Log Insight

NSX

Design and relations of SDDC components

Logical overview of the SDDC clusters

Logical overview of the solution components

The vRealize Automation design

Small

Enterprise

Infrastructure design examples

Network

Storage

Compute

Designing the tenants

Tenants, business groups, and infrastructure fabrics

What is a tenant?

What is a business group?

What is a fabric group?

What is the infrastructure fabric?

What must be included in the design

What if the vSphere environment is already running?

Summary

5. VMware vRealize Automation

vRA installation

First things first

Advanced installation configuration

vRA concepts

vRA's little helper

DEM

The IaaS server

vRealize Orchestrator

The Infrastructure tab

Endpoints

Compute Resources

Reservations

Managed Machines

The Administration tab

Approval Policies

Directories Management

Catalog Management

Property Dictionary

Reclamation

Branding

Notifications

Events

vRO configuration

vRA concepts

As a Service synonyms

IaaS

PaaS

XaaS

Blueprints

Single machine blueprints

Multimachine blueprints

Application automation

Sample configurations

Template preparation in vCenter

Creating a network pool

Creating a set of properties

Creating the IaaS blueprint

Publishing the blueprint as a service

Summary

6. vRealize Orchestrator

vRealize Orchestrator principles

Workflow elements and design

Attributes, inputs, and outputs

Inputs

Attributes

Outputs

Configurations

Workflow elements

Workflow creation 101

Creating the workflow

Integrating the workflow into vRA

Adding the properties to the blueprint

External services

Connecting vRO to vCenter

vRO context actions in vCenter

Finding and enabling context actions

Enabling a context-based workflow

Summary

7. Service Catalog Creation

Service catalogs

Defining a catalog

Multiple catalogs

Catalogs: As less as possible as many as required

Provide basic catalogs as well as specific catalogs

Choose a descriptive and short name

Outcome-oriented versus technology-oriented

Know your audience

Service catalog creation in vRA

First step: Creating the catalog

Second step: Publishing catalog items

Third step: Entitling a service

Multimachine blueprint design example

Software components

Sample application design

Defining the components

Apache web server

PHP web component

MySQL web component

FST Industries web component

FST Industries DB component

Defining the blueprint

Summary

8. Network Virtualization using NSX

Network Virtualization 101

Current networking infrastructures

VLAN: Network virtualization known for almost 30 years

Traditional routing and security

Modern network approach

L3 Networking - the new architecture

Network virtualization for the rescue

NSX terminology

VXLAN

EDGE

Logical Switches

VTEP

NSX controller

NSX setup and preparation

ESXi prerequisites for VXLAN / NSX

Network prerequisites for NSX

Step 1: Installing NSX manager

Step 2: Setting up the components

Prepare the ESXi hosts

Deploy the NSX controller nodes

Defining the segment ID

Configuring the transport parameters

Set up the transport zone

Step 3: Virtual networking 101

Add a Logical Switch

Add a Distributed Logical Router

Add a EDGE services Gateway

Dynamic routing between virtual and physical

Connecting vRealize Automation

Network reservations

Setting up NSX network profiles

The external profile

The NAT profile

The routed profile

Using NSX network profiles in blueprint

Summary

9. DevOps Considerations

What is DevOps

Agility meets policies

How does DevOps work

What are containers

Containers are not VMs

Container host: Virtual or physical

DevOps and Shadow IT

Radical new IT approach

Cattle versus pets

Changing the organizational culture

PaaS as part of DevOps

The Cloud Foundry framework

Cloud Foundry and the SDDC

vRealize Code Stream: DevOps without containers

All about the pipeline

vRealize Code Stream integration

SDDC and DevOps: A mixed world

DevOps requirements

Enterprise requirements

Legacy and DevOps: Coexistence in one environment

Use DevOps principles to manage the SDDC

Summary

10. Capacity Management with vRealize Operations

Capacity monitoring in the SDDC

vRealize Operations Manager

vROps 6.3 deployment workflow

Capacity monitoring

Overprovisioning and resource allocation

Navigating vRealize Operations Manager

Capacity remaining

Capacity planning

Projects in vRealize Operations Manager

Reports in vRealize Operations Manager

Views in vRealize Operations Manager

Summary

11. Troubleshooting and Monitoring

Monitoring and analytics in the SDDC

The risk of false positives

Management versus payload monitoring

Management monitoring

Payload monitoring

KPIs versus thresholds

vRealize Operations Manager

Analytics using vRealize Operations Manager

Exploring vRealize Operations Manager anomalies

Badges and what they describe

The Health badge and how to read it

The Risk badge and how to read it

The Efficiency badge and how to read it

Service health information in vRealize Automation

Log management in the SDDC

Millions of log entries

Log management from the big data perspective

vRealize Log Insight

SDDC components to add to vRealize Log Insight

How to analyze logs using vRLI

Using the Interactive Analytics View

Creating and using dashboards

The pro-active analytics features

Summary

12. Continuous Improvement

Continual Service Improvement

Technical assurance

Reviewing blueprints

Reviewing automation and integration

Revisiting the business case

ITIL in the SDDC

Matching the requirements to the solution

Applying continuous service improvement to the SDDC

Summary

Building VMware Software-Defined Data Centers

Building VMware Software-Defined Data Centers

Copyright © 2016 Packt Publishing

All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews.

Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book.

Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information.

First published: December 2016

Production reference: 1061216

Published by Packt Publishing Ltd.

Livery Place

35 Livery Street

Birmingham 

B3 2PB, UK.

ISBN 978-1-78646-437-8

www.packtpub.com

Credits

About the Author

Valentin Hamburger was working at VMware for more than seven years. In his former role, he was a lead consulting architect and took care of the delivery and architecture of cloud projects in central EMEA. In his current role, he is EMEA solutions lead for VMware at Hitachi Data Systems (HDS). Furthermore he works as an advisor with HDS engineering on the Hitachi Enterprise Cloud, which is based on VMware vRealize technology. He holds many industry certifications in various areas such as VMware, Linux, and IBM Power compute environments.  He serves as a partner and trusted advisor to HDS customers primarily in EMEA. His main responsibilities are ensuring that HDS's future innovations align with essential customer needs and translating customer challenges to opportunities focused on virtualization topics. Valentin enjoys sharing his knowledge as a speaker at national and international conferences such as VMworld.

I want to personally thank Daniel Koeck for reviewing the technical content of this book and providing such valuable and productive inputs. Besides his technical expertise I am happy to have him as a friend and supporter for this book. Furthermore, I want to thank my beautiful wife and daughter for their patience and understanding while I was writing this book. Without their support and love, this wouldn’t have been possible at all. Finally I do want to thank Rashmi Suvarna who had patience with me as an author and supported me wherever she could in order to get all this work done.

About the Reviewer

Daniel Koeck has been working for 15 years in IT. He leaded large scale (more than 20,000 VMs) projects, reaching from Service Provider Clouds, to DevOps enabled large scale software solutions in the last 6 years. He holds a degree for applied computer science and IT-security. Daniel is an IBM Redbook Gold author, and co-authored other many other books and whitepapers about x86 virtualization. He is regularly invited as a speaker to different universities and technology conferences all over Europe and USA, and enjoys sharing his experience there. You can find him on twitter @Cloudsandwakes.

www.PacktPub.com

eBooks, discount offers, and more

Did you know that Packt offers eBook versions of every book published, with PDF and ePub files available? You can upgrade to the eBook version at www.PacktPub.com and as a print book customer, you are entitled to a discount on the eBook copy. Get in touch with us at customercare@packtpub.com for more details.

At www.PacktPub.com, you can also read a collection of free technical articles, sign up for a range of free newsletters and receive exclusive discounts and offers on Packt books and eBooks.

https://www2.packtpub.com/books/subscription/packtlib

Do you need instant solutions to your IT questions? PacktLib is Packt's online digital book library. Here, you can search, access, and read Packt's entire library of books.

Why subscribe?

Fully searchable across every book published by Packt

Copy and paste, print, and bookmark content

On demand and accessible via a web browser

Preface

This book uses the most up-to-date, cutting-edge VMware products to help you deliver a complete unified hybrid cloud experience within your infrastructure.

It will help you build an SDDC architecture and practices to deliver a fully virtualized infrastructure with cost-effective IT outcomes. In the process, you will use some of the most advanced VMware products such as vSphere, vRealize Automation and Orchestrator, and NSX. You will see how to provision applications and IT services on private clouds or IaaS with seamless accessibility and mobility across the hybrid environment.

This book will ensure that you develop an SDDC approach for your data center that fulfills your organization's business needs and tremendously boosts your agility and flexibility. It will also teach you how to draft, design, and deploy toolsets and software to automate your data center and speed up IT delivery to meet your lines of businesses demands. In the end, you will build unified hybrid clouds that dramatically boost your IT outcomes.

What this book covers

Chapter 1, The Software-Defined Data Center, discusses principles and basics about the SDDC. Besides the technical aspects, it will also highlight the organizational aspects and that the SDDC is a new way of managing and running a data center and therefore also an architectural change. Also, it will describe the implementation journey and what is necessary to take into account besides the technological aspects.

Chapter 2, Identify Automation and Standardization Opportunities, highlights the main principles of automation and standardization. The differences between scripts and workflows are described. Also, it will bring examples how to apply standardization and automation to the data center in order to make the SDDC flexible and agile as possible.

Chapter 3, VMware vSphere: The SDDC Foundation, covers important vSphere functions, which will decrease the amount of customization when it comes to automation. Since virtualization is the base of an SDDC, this chapter will focus on examples and configurations for vSphere. This chapter will discuss advanced vSphere functions and their importance for an SDDC.

Chapter 4, SDDC Design Considerations, explains the main principles of an SDDC design including detailed examples. Highlighted are also what assumptions, constraints and limits are and how they will influence a design.  Furthermore, it will show a simple–to-follow approach to translate business challenges in a technical solution and therefore an agile and efficient SDDC design.

Chapter 5, VMware vRealize Automation, introduces vRA (formally known as vCloud Automation Center) and its capabilities. The implementation of the design considerations of the former chapter will be discussed, and it will show other important configuration options, principles, and concepts. Also, it will focus on the creation of so-called blueprints and what is needed to prepare a VM template to be deployed.

Chapter 6, vRealize Orchestrator, touches on what workflows are and how they can be developed in a controlled and clean manner. It will highlight how to integrate those into vRealize Automation to create powerful services for almost any task in the SDDC. In addition, it will discuss what postdeployment third-party integration can be achieved using vRO (for example, IPAM and CMDB integration).

Chapter 7, Service Catalog Creation, brings up the basic service catalog design. Also, it bridges the business case to the service catalog and describes why that is important and how that sync can be achieved. It will explain  based on an example how to configure an outcome-focused service catalog in vRealize Automation.

Chapter 8, Network Virtualization using NSX, discusses software-defined networking principles. It highlights NSX basic functions and configurations and why it is a game changer within the SDDC. With NSX, broad data center automation can be fully achieved by gaining maximal flexibility and agility for service deployments. It will also cover the base configuration and integration with SDDC based on practical examples and detailed integration descriptions.

Chapter 9, DevOps Considerations, describes DevOps in general and what changes it brings to IT and the SDDC. It discusses most of the modern technologies to run DevOps including containers and container frameworks such as Pivotal Cloud Foundry. Furthermore, it describes a DevOps approach to run and manage the SDDC itself using VMware vRealize Code Stream Management Pack for IT DevOps. This will add additional agility and flexibility when it comes to managing and operating the SDDC.

Chapter 10, Capacity Management with vRealize Operations, mentions how important a proper capacity management is in a fully automated data center. It will highlight techniques and principles in regard to successfully plan infrastructure expansion. It provides practical configuration examples for resource planning and predictive capacity maintenance.

Chapter 11, Troubleshooting and Monitoring, explains the monitoring and analytics methods for the SDDC. Since an automated data center might have different challenges in terms of monitoring, it further highlights the differences to static infrastructure and why it is important to have a smart monitoring and analytics approach for the SDDC. It will describe how to limit the impact of issues with smart and predictive troubleshooting and analytics methods, including the use of vRealize Log Insight.

Chapter 12, Continuous Improvement, mentions the importance of continuously working on the services and processes within the SDDC. Once the SDDC is deployed and functions properly it is time to reflect and maybe update the created services. The chapter mentions how important it is to detect possible process flaws or glitches and update those. Furthermore, it summarizes the importance of ITIL in a modern data center and explains that the SDDC is basically the fully automated version of ITIL bringing all its benefits to life without all its drawbacks like the bureaucracy overhead.

What you need for this book

vRealize Automation

vRealize Orchestrator

vRealize Operations Manager

vRealize Log Insight

vRealize Code Stream

Management pack for IT DevOps

VMware vSphere

VMware NSX

Who this book is for

If you are an IT professional or VMware administrator who virtualizes data centers and IT infrastructures, this book is for you. Developers and DevOps engineers who deploy applications and services would also find this book useful. Data center architects and those at the CXO level who make decisions will appreciate the value in the content.

Conventions

In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: Provide a meaningful name such as Backup.

Any command-line input or output is written as follows:

msdtc –uninstall

A block of code is set as follows:

#!/bin/bash

#Turn off iptables for app server access

/sbin/service iptables stop

New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: Click OK to store the new property.

Note

Warnings or important notes appear in a box like this.

Tip

Tips and tricks appear like this.

Reader feedback

Feedback from our readers is always welcome. Let us know what you think about this book-what you liked or disliked. Reader feedback is important for us as it helps us develop titles that you will really get the most out of. To send us general feedback, simply e-mail feedback@packtpub.com, and mention the book's title in the subject of your message. If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide at www.packtpub.com/authors.

Customer support

Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.

Downloading the color images of this book

We also provide you with a PDF file that has color images of the screenshots/diagrams used in this book. The color images will help you better understand the changes in the output. You can download this file from https://www.packtpub.com/sites/default/files/downloads/BuildingVMwareSoftwaredefinedDataCenters_ColorImages.pdf.

Errata

Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books-maybe a mistake in the text or the code-we would be grateful if you could report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the Errata Submission Form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded to our website or added to any list of existing errata under the Errata section of that title.

To view the previously submitted errata, go to https://www.packtpub.com/books/content/support and enter the name of the book in the search field. The required information will appear under the Errata section.

Piracy

Piracy of copyrighted material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works in any form on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.

Please contact us at copyright@packtpub.com with a link to the suspected pirated material.

We appreciate your help in protecting our authors and our ability to bring you valuable content.

Questions

If you have a problem with any aspect of this book, you can contact us at questions@packtpub.com, and we will do our best to address the problem.

Chapter 1. The Software-Defined Data Center

Originally the term software-defined data center (SDDC) has been introduced by VMware, to further describe the move to a cloud-like IT experience. The term software-defined is an important bit of information. It basically means that every key function in the data center is performed and controlled by software, instead of hardware. This opens a whole new way of operating, maintaining but also innovating in a modern data center.

But how does a so-called SDDC look like, and why is a whole industry pushing so hard towards its adoption? This question might also be a reason why you are reading this book, which is meant to provide a deeper understanding of it and give practical examples and hints how to build and run such a data center. Meanwhile, it will also provide the knowledge of mapping business challenges with IT solutions. This is a practice which becomes more and more important these days.

IT has come a long way from a pure back office, task oriented role in the early days, to a business relevant asset, which can help organizations to compete with their competition. There has been a major shift from a pure infrastructure provider role to a business enablement function. Today, most organizations business is just as good as their internal IT agility and ability to innovate. There are many examples in various markets where a whole business branch was built on IT innovations such as Netflix, Amazon Web Services (AWS), Uber, Airbnb, just to name a few.

However, it is unfair to compare any startup with a traditional organization. A startup has one application to maintain and they have to build up a customer base.

A traditional organization has a wide customer base and many applications to maintain. So they need to adapt their internal IT to become a digital enterprise, with all the flexibility and agility of a startup, but also maintaining the trust and control over their legacy services.

This chapter will cover the following points:

Why is there a demand for SDDC in IT

What is SDDC

Understand the business challenges and map it to SDDC deliverables

The relation of an SDDC and an internal private cloud

Identify new data center opportunities and possibilities

Become a center of innovation to empower your organization's business

The demand for change

Today organizations face different challenges in the market to stay relevant. The biggest move was clearly introduced by smartphones and tablets. It was not just a computer in a smaller device, they changed the way IT is delivered and consumed by end users. These devices proved that it can be simple to consume and install applications. Just search in an app store, choose what you like, use it as long as you like it. If you do not need it any longer, simply remove it. All with very simplistic commands and easy to use gestures.

More and more people relying on IT services by using a smartphone as their terminal to almost everything. These devices created a demand for fast and easy application and service delivery. So in a way, smartphones have not only transformed the whole mobile market, they also transformed how modern applications and services are delivered from organizations to their customers.

Although it would be quite unfair to compare a large enterprise data center with an app store or enterprise service delivery with any app installs on a mobile device, there are startups and industries, which rely solely on the smartphone as their target for services, such as Uber or WhatsApp.

On the other side, smartphone apps also introduce a whole new way of delivering IT services, since any company never knows how many people will use the app simultaneously. But in the backend, they still have to use web servers and databases to continuously provide content and data for these apps.

This also introduces a new value model for all other companies. People start to judge a company by the quality of their smartphone apps available. Also, people started to migrate to companies which might offer better smartphone integration as the previous one used. This is not bound to a single industry, but affects a broad spectrum of industries today such as the financial industry, car manufacturers, insurance groups, and even food retailers, just to name a few.

A classic data center structure might not be ideal for quick and seamless service delivery. These architectures are created by projects to serve a particular use case for a couple of years. An example of this bigger application environments is web server farms, traditional SAP environments, or a data warehouse.

Traditionally these were designed with an assumption about their growth and use. Special project teams have set them up across the data center pillars, as shown in the following figure. Typically, those project teams separate after such the application environment has been completed.

All these pillars in the data center are required to work together, but every one of them also needs to mind their own business. Mostly those different divisions also have their own processes which then may integrate into a data center wide process. There was a good reason to structure a data center in this way, the simple fact that nobody can be an expert in every discipline. Companies started to create groups to operate certain areas in a data center, each building their own expertise for their own subject.

This was evolving and became the most applied model for IT operations within organizations. Many, if not all, bigger organizations have adopted this approach and people build their careers on these definitions. It served IT well for decades and ensured that each party was adding its best knowledge to any given project.

However, this setup has one flaw, it has not been designed for massive change and scale. The bigger these divisions get, the slower they can react to request from other groups in the data center. This introduces a bi-directional issue, since all groups may grow at a similar rate, the overall service delivery time might also increase exponentially.

Unfortunately, this also introduces a cost factor when it comes to service deployments across these pillars. Each new service, an organization might introduce or develop, will require each area of IT to contribute. Traditionally, this is done by human handovers from one department to the other.

Each of these handovers will delay the overall project time or service delivery time, which is also often referred to as time to market. It reflects the needed time interval from the request of a new service to its actual delivery. It is important to mention that this is a level of complexity every modern organization has to deal with when it comes to application deployment today.

The difference between organizations might be in the size of the separate units, but the principle is always the same. Most organizations try to bring their overall service delivery time down to be quicker and more agile. This is often related to business reasons as well as IT cost reasons.

In some organizations, the time to deliver a brand new service from request to final roll out may take 90 working days. This means a requestor might wait 18 weeks or more than four and a half month from requesting a new business service to its actual delivery. Do not forget that this reflects the complete service delivery, over all groups until it is ready for production. Also, after these 90 days, the requirement of the original request might have changed which would lead into repeating the entire process.

Often a quicker time to market is driven by the lines of business (LOB) owners to respond to a competitor in the market, who might already deliver their services faster. This means that today's IT has changed from a pure internal service provider to a business enabler supporting its organization to fight the competition with advanced and innovative services.

While this introduces a great chance to the IT department to enable and support their organizations business, it also introduces a threat at the same time. If the internal IT struggles to deliver what the business is asking for, it may lead to leverage shadow IT within the organization.

The term shadow IT describes a situation where either the LOBs of an organization or its application developers have grown so disappointed with the internal IT delivery times, that they actually use an external provider