Book Image

VMware vRealize Operations Performance and Capacity Management

By : Iwan 'e1' Rahabok
Book Image

VMware vRealize Operations Performance and Capacity Management

By: Iwan 'e1' Rahabok

Overview of this book

Table of Contents (18 chapters)
VMware vRealize Operations Performance and Capacity Management
Credits
Foreword
Foreword
About the Author
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface
Index

Preface

I joined VMware in May 2008 as the first presales engineer (Account SE is the industry term) in ASEAN for VMware strategic accounts. That was more than 6 years ago—a long time in the rapidly-evolving world of virtualization. I have been fortunate to meet many different customers in the ASEAN region. In a sense, the book documents the lessons that my customers and I have learned in their journey to the fully virtualized data center. It is very rare for customers to master the virtual world, both architecturally and operationally, part of the reason for this is that Software-Defined Data Center (SDDC) is not yet matured. The biggest reason, however, is the lack of an in-depth understanding of what exactly virtualization means to IT.

There are, in fact, many misunderstandings of even the fundamentals. For example, almost all IT professionals will say they understand a Virtual Machine (VM). However, do they really understand the ramifications? A lot of CIOs still manage their virtual data centers the same way they manage their physical data centers. This creates a lot of complexity as the two platforms are radically different.

This book started many years ago with a presentation that I delivered to customers. Some of the presentations were eventually posted on my LinkedIn profile and at https://communities.vmware.com/ as customers ask for it. There have been requests to convert these presentations into a book, so they can share it with their peers. After a long time, I am both humbled and honored to present to you this book.

What this book covers

Content-wise, the book is split into two main parts. The first part provides the foundation and theory. The second part provides the solutions and sample use cases.

Chapter 1, Virtual Data Center – It's Not a Physical Data Center, Virtualized, aims to clear up the misunderstandings that customers have about SDDC. It explains why a VM is radically different from a physical server, and hence a virtual data center is fundamentally different from a physical data center. It then covers the aspects of management that are affected.

Chapter 2, Capacity Management in SDDC, takes the topic of the previous chapter further by discussing how capacity management should be done in a virtual data center. Together with Chapter 1, Virtual Data Center – It's Not a Physical Data Center, Virtualized, it is useful if you need to explain these topics to your peers, customers, or management.

Chapter 3, Mastering the Key Counters in SDDC, sets the technical foundations of performance and capacity management by giving you a tour of the four infrastructure elements (CPU, RAM, network, and storage). It also maps these four elements into all the vSphere objects, so you know what is available at each level.

Chapter 4, CPU Counters, covers CPU counters in detail. It is the first of four chapters that cover the core infrastructure element (CPU, RAM, network, and storage). If you do not fully understand the various counters in vSphere and vRealize Operations, how they impact one another, and what values you consider healthy, then these four chapters are good for you. They dive deep into the counters, comparing the counters in vCenter and vRealize Operations. Knowing the counters is critical, as choosing the wrong counters, or interpreting the values wrongly, will lead to a wrong conclusion.

Chapter 5, Memory Counters, continues the deep dive by covering memory counters. It explains why VM memory is one of the most complex area to monitor and troubleshoot.

Chapter 6, Network Counters, continues the deep dive by covering network counters.

Chapter 7, Storage Counters, completes the coverage by covering storage counters. It explains the multiple layers of storage that occur as a result of virtualization.

Chapter 8, Dashboard Examples and Ideas, covers the practical aspects of this book, as they show how sample solutions are implemented. This chapter provides both performance management and capacity management.

What this book is not

The book focuses on the management of the SDDC. It does not cover the architecture. So no vCloud Suite design best practices are present in this book. It also does not cover all aspects of operation. For example, it does cover processes, organizational structure, financial management, and audit. Specific to management, the book only focuses on the most fundamental areas, namely:

  • Performance

  • Capacity

This book does not cover other areas of management, such as configuration management, compliance management, and availability management. For performance management, it focuses on the infrastructure only. It does not cover application management. So there is no discussion of monitoring databases, web, and application servers here.

This book is also a solutions book. It is not a product book. It uses vRealize Operations to apply the solutions. You can probably use other products to apply the use cases. Because it is not a product book, it does not cover all modules of vRealize Operations Suite. For examples, vCenter Infrastructure Navigator, Hyperic, and VMware Configuration Manager are not covered.

For the sake of the environment, I set a hard limit of 250 pages for this book. Plus, I wanted to provide a book that you can finish in one sitting and that is comfortable to hold with one hand. As a result, the book is light on the Capacity Management portion. vRealize Operations 6 introduces a brand new capacity management engine, so I expect that there will be a lot of write-up on it. I have not operationalized this revamped capacity management functionality for my customers. As a result, I am not qualified to write a book on it. Once I gain the implementation experience and see it being used by customers, I will update my blog (http://virtual-red-dot.info).

What you need for this book

Because it is not a product book, I assume that you have the products installed and configured. VMware vSphere and vRealize Operations are the products used in this book. There are many blog articles and YouTube videos on installation, configuration, and product overview. In the References section of the last chapter, I have provided a link to them as they get updated more frequently than a physical book. Some of the bloggers also have many other materials, which will complete your learning. At a personal level and as a father of two young kids, I'm not keen on killing trees unless it's really necessary.

Who this book is for

This book is for VMware professionals. This can be a VMware administrator, architect, consultant, engineer, or technical support. You may be working for VMware customers, partners, or VMware itself. You may be an individual contributor or a technical leader.

This book is an intermediate-level book. It assumes you have hands-on experience of vSphere 5.5 and vRealize Operations 6.0, and you are capable of performing some level of performance troubleshooting. You also have good overall knowledge of vCloud Suite, Virtual SAN, Horizon View, and NSX. You should also have some level of knowledge of operating systems, storage, network, disaster recovery, and data center.

This book is also for IT professionals who deal with VMware professionals. As such, there is a wide range of roles, as virtualization and VMware covers many aspects of IT. Depending on your role, certain chapters will be more useful to you. The following is the list of roles and the chapters that are relevant to them:

  • CIO, Head of Infrastructure, and other senior IT leader

    • Chapter 1, Virtual Data Center – It's Not a Physical Data Center, Virtualized

    • Chapter 2, Capacity Management in SDDC (the two-tier concept)

  • Capacity management team

    • Chapter 2, Capacity Management in SDDC

    • Chapter 8, Dashboard Examples and Ideas (capacity management portion)

  • Network team

    • Chapter 1, Virtual Data Center – It's Not a Physical Data Center, Virtualized

    • Chapter 2, Capacity Management in SDDC (network portion)

    • Chapter 3, Mastering the Key Counters in SDDC (network section)

    • Chapter 6, Network Counters

    • Chapter 8, Dashboard Examples and Ideas (network portion)

  • Storage team

    • Chapter 1, Virtual Data Center – It's Not a Physical Data Center, Virtualized

    • Chapter 2, Capacity Management in SDDC (storage portion)

    • Chapter 3, Mastering the Key Counters in SDDC (storage section)

    • Chapter 7, Storage Counters

    • Chapter 8, Dashboard Examples and Ideas (storage portion)

  • Application architect or developer

    • Chapter 3, Mastering the Key Counters in SDDC

    • Chapters 4 to 7

  • Enterprise architect

    • Chapter 1, Virtual Data Center – It's Not a Physical Data Center, Virtualized

    • Chapter 2, Capacity Management in SDDC

    • Chapter 3, Mastering the Key Counters in SDDC (first half)

  • Help desk and operations

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: "This includes the drive where the OS resides (the C:\ drive in Windows)."

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: "Notice that I did not select the Host to VM and VM to datastore relationship options, and it got way too complicated when I did."

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 , 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 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/1682EN_Graphics.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 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 , and we will do our best to address the problem.