VCF design guide

In the Ultra Transcenders books

2V0-13.25

Each book explains VCF design guide in context, with comparison tables and the common traps.

Terms in this definition

• VMware Cloud Foundation

  Broadcom's platform for private cloud. It unifies management of NSX, vSAN, vSphere, VCF Automation and VCF Operations as one fleet; VVF, by contrast, lacks automation and cloud management.

• Architectural Options

  The part of the VCF 9.0 design guide that sets the models available for each component side by side, with their benefits and implications, for components from fleet deployment and VCF Operations through to storage, the network fabric and NSX management. Each model's detailed design is in the Design Library.

• Blueprints

  Python v2 programming model objects (func.Blueprint) for splitting a function app's functions across several modules, which are then added to the main FunctionApp by calling app.register_functions().

• Design Library

  Where the VCF design guide keeps detailed designs, organised per component into alternative models that each have their own design elements. A blueprint's chosen model can be exchanged for any other in the same category.

• Design element

  A single entry in the VCF design guide, be it a requirement, a recommendation or a choice, labelled with an ID and accompanied by justification and implication text. Elements outside the chosen configuration are not implemented.

• Requirement

  A need that is stated clearly enough to be measured or tested, leaves no ambiguity and is essential for the result to be accepted.

Related terms

• Design blueprint

  Ready-made, opinionated fleet architecture from the VCF Design guide covering a typical layout, say one small site or many sites over several regions. Use it unchanged, or swap individual models from the design library.