Book Image

PowerCLI Essentials

By : Chris Halverson
Book Image

PowerCLI Essentials

By: Chris Halverson

Overview of this book

Have you ever wished you could automatically get a report with all the relevant information about your VMware environments in exactly the format you want? Or that you could automate a crucial task that needs to be performed on a regular basis? Powerful Command Line Interface (PowerCLI) scripts do all these things and much more for VMware environments. PowerCLI is a command-line interface tool used to automate VMware vSphere environments. It is used to handle complicated administration tasks through use of various cmdlets and scripts, which are designed to handle certain aspects of VSphere servers and to help you manage them. This book will show you the intricacies of PowerCLI through real-life examples so that you can discover the art of PowerCLI scripting. At the start, you will be taught to download and install PowerCLI and will learn about the different versions of it. Moving further, you will be introduced to the GUI of PowerCLI and will find out how to develop single line scripts to duplicate running tasks, produce simple reports, and simplify administration. Next, you will learn about the methods available to get information remotely. Towards the end, you will be taught to set up orchestrator and build workflows in PowerShell with update manager and SRM scripts.
Table of Contents (13 chapters)
PowerCLI Essentials
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Chapter 6. Running Workflows with Other VMware Products

After almost 3 months, the DevOps initiative using vRealize Orchestrator is speeding things up significantly. Mr. Mitchell, up to this point, has been pleased with the progress you and your group have been able to achieve and has been touting your team to the rest of the business units. The added pressure upon your, once small, agile team is beginning to show with bogged down deployments due to other teams, extensive changes outside of your control, and unrealistic customizations demanding application integration with your processes. In building a lifecycle management, one of the key requests is to control the build and the decommissioning process and with that, take into consideration which machines are in use or not, who owns it, and who requested it.

Your team is beginning to complain stating, "The network team is taking up to a week to process our requests, and we are being blamed for it!" and "The Virtualization team is asking for...