Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
VMware Cross-Cloud Architecture

You're reading from   VMware Cross-Cloud Architecture Automate and orchestrate your Software-Defined Data Center on AWS

Arrow left icon
Product type Paperback
Published in Mar 2018
Publisher Packt
ISBN-13 9781787283435
Length 504 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Ajit Pratap Kundan Ajit Pratap Kundan
Author Profile Icon Ajit Pratap Kundan
Ajit Pratap Kundan
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. The Freedom with Cross-Cloud Architecture 2. Implementing Service Architecture for Cross-Cloud Services FREE CHAPTER 3. Transforming a Data Center from Silos to Software-Defined Services 4. Designing a Mixed Cloud Model with VMware 5. Implementing Service Redundancy Across All Layers 6. Designing Software-Defined Storage Services 7. VMware Cloud Assess, Design, and Deploy Services 8. Transforming Your Network Architecture 9. Dealing with Data Sovereignty 10. Designing Effective Compliance Regulations to Fix Violations 11. Lower TCO and Greater ROI with Maximum Agility 12. VMware Pricing and Licensing for a Cross-Cloud Model 13. The Economics of Cross-Cloud Services 14. Other Books You May Enjoy

Assumptions, risks, constraints, and use cases

During initial design workshops, baseline requirements were defined and recorded in the solution requirements document. The overall structure of this document is to describe various aspects of the solution designed to meet customer requirements. Throughout this document, key points of particular importance are highlighted and identified with one of the following icons.

The interpreting information about design requirements and decisions is as follows:

Icon

Label

Definition

Design Decision

Identifies a design decision that has been made

Constraint

Identifies constraints that have influenced design choices

Assumption

Identifies where an assumption has been made in the absence of factual data

Design Consideration

Identifies an area that requires further discussion with architecture and operations...

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 $19.99/month. Cancel anytime
Banner background image