Book Image

The Complete VMware vSphere Guide

By : Mike Brown, Hersey Cartwright, Martin Gavanda, Andrea Mauro, Karel Novak, Paolo Valsecchi
Book Image

The Complete VMware vSphere Guide

By: Mike Brown, Hersey Cartwright, Martin Gavanda, Andrea Mauro, Karel Novak, Paolo Valsecchi

Overview of this book

vSphere 6.7 is the latest release of VMware's industry-leading virtual cloud platform. By understanding how to manage, secure, and scale apps with vSphere 6.7, you can easily run even the most demanding of workloads. This Learning Path begins with an overview of the features of the vSphere 6.7 suite. You'll learn how to plan and design a virtual infrastructure. You'll also gain insights into best practices to efficiently configure, manage, and secure apps. Next, you'll pick up on how to enhance your infrastructure with high-performance storage access, such as remote direct memory access (RDMA) and Persistent memory. The book will even guide you in securing your network with security features, such as encrypted vMotion and VM-level encryption. Finally, by learning how to apply Proactive High Availability and Predictive Distributed Resource Scheduler (DRS), you'll be able to achieve enhanced computing, storage, network, and management capabilities for your virtual data center. By the end of this Learning Path, you'll be able to build your own VMware vSphere lab that can run high workloads. This Learning Path includes content from the following Packt products: VMware vSphere 6.7 Data Center Design Cookbook - Third Edition by Mike Brown and Hersey Cartwright Mastering VMware vSphere 6.7 - Second Edition by Martin Gavanda, Andrea Mauro, Karel Novak, and Paolo Valsecchi
Table of Contents (21 chapters)

Architecture and logical design

You might have realized by now that building a lab isn't as simple as you might think. For those who are interested in how I built the lab that I used during the writing of this book, you can follow this detailed guide.

I chose to rent a dedicated server from OVH. This was for the following reasons:

  • For my on-site training, I needed a lot of resources (256 GB of RAM or more)
  • I did not need to run the server all the time
  • I did not want to pay any setup fees
  • I needed to be able to order as many public IP addresses as necessary for the project
  • There were months when I didn't need to run the lab at all
  • There were other months in which I needed a different hardware platform with different resources
  • I needed to access the lab from anywhere

Based on these requirements, I decided that it did not make sense to use my hardware because the costs...