1.1 Overview
vCAT-SP has been developed so that each document can stand alone and provide guidance to the architect on implementing a specific part of the solution. For example, the Architecting VMware NSX for Service Providers document can be used by a service provider who has already implemented a core cloud product based on VMware vSphere® or VMware vCloud Director®, understands how this component fits into a wider solution, and knows how to design based on required outcomes and use cases.
The vCAT-SP documentation is organized as follows:
• General documents – Document map and introduction on how to consume and leverage vCAT-SP.
• Service definition documents – Documents that enable the consumer to effectively define requirements for the cloud platform and determine what services to offer to their end users.
• Architecture documents – Documents that highlight the logical design and operational considerations within a specific architectural domain.
• Solution architecture example documents – Documents that provide solution architecture examples of a cloud platform.
• Solutions and services examples – Documents that provide architecture guidance and implementation blueprints for value-add services and solutions that can be added to the core cloud platform.