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

Script or workflow


It is important to understand the differences between a workflow and a script. As mentioned earlier, scripts are well established in the IT and originally were created to complete smaller tasks faster than a human could. Typically, scripts provide a single scripting language like Bash scripts in UNIX or PowerShell scripts in Windows. They can also be used to address complex tasks calling other scripts introducing multiple layers of relations to successfully complete a task. By following this logic, it can get very confusing very soon.

These scripts have to have logic to wait for their subscripts to come back with status information (success/failure/idle). This status queries are not as simple as it sounds and sometimes requires an own script, just to take care of all the subscripts running. Also, they can't simply be stopped since they have no control over the subscripts running in the background.

Often scripts are maintained by a single admin, who is aware of their logic...