Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Building VMware Software-Defined Data Centers

You're reading from   Building VMware Software-Defined Data Centers Make the most of software-defined data centers with revolutionary VMware technologies

Arrow left icon
Product type Paperback
Published in Dec 2016
Publisher
ISBN-13 9781786464378
Length 358 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
 Hamburger Hamburger
Author Profile Icon Hamburger
Hamburger
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Building VMware Software-Defined Data Centers
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
1. The Software-Defined Data Center 2. Identify Automation and Standardization Opportunities FREE CHAPTER 3. VMware vSphere: The SDDC Foundation 4. SDDC Design Considerations 5. VMware vRealize Automation 6. vRealize Orchestrator 7. Service Catalog Creation 8. Network Virtualization using NSX 9. DevOps Considerations 10. Capacity Management with vRealize Operations 11. Troubleshooting and Monitoring 12. Continuous Improvement

Radical new IT approach


DevOps is a radical and disruptive way of doing IT. It focuses on applications and it tends to ignore hardware beneath the app. This sounds harsh compared to the classic IT approach where servers and the OS is in focus in order to provide a good, secure, and scalable environment for the applications.

In DevOps, applications become stateless since they store the data elsewhere; that might be an object-based storage or a NAS/SAN mount into the container. This means the container can spin up wherever it needs to be, given that it can access its data. There is no means in patching containers - just the container definition (the package) will be updated. To deploy this patch the old container will be destroyed and a new container will be started with the updated service/application code.

Also, containers in DevOps are not a place to install an entire legacy app. Ideally, they house just parts of an app so-called microservices. These microservices can be used to form an app...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at £13.99/month. Cancel anytime
Visually different images