Book Image

Building VMware Software-Defined Data Centers

By : Valentin Hamburger
Book Image

Building VMware Software-Defined Data Centers

By: Valentin Hamburger

Overview of this book

VMware offers the industry-leading software-defined data center (SDDC) architecture that combines compute, storage, networking, and management offerings into a single unified platform. 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 a unified hybrid cloud based on 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, VCloud, and NSX. You will learn how to use vSphere virtualization in a software-defined approach, which will help you to achieve a fully-virtualized infrastructure and to extend this infrastructure for compute, network, and storage-related data center services. You will also learn how to use EVO:RAIL. Next, 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 you develop an SDDC approach for your datacenter that fulfills your organization's 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 datacenter and speed up IT delivery to meet your lines of businesses demands. At the end, you will build unified hybrid clouds that dramatically boost your IT outcomes.
Table of Contents (18 chapters)
Building VMware Software-Defined Data Centers
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface

SDDC and DevOps: A mixed world


The SDDC is perhaps one of the biggest enabler for DevOps as well as for running legacy applications more agile and dynamic. However, for most organizations, the SDDC is a way of running and deploying their well-established and often still required legacy applications.

Given all the changes a DevOps environment introduces, it will collide with established and required policies and processes in an enterprise environment. The classic approaches will not work since they possibly slow down DevOps operations and also create unnecessary overhead to such an environment.

An example for this will be an IPAM and CMDB solution. Given the short and temporary life of a development environment, it might not be necessary to track the hostname and IP address from all the VMs in the environment. Also, it might not be required to add all OS and software configuration items to the CMDB since they can change on a day-by-day basis. Therefore, all these processes have to be ignored...