Cisco Cisco Prime Virtual Network Analysis Module (vNAM) 6.3 White Paper
2-6
Cisco Virtualized Multiservice Data Center (VMDC) Virtual Services Architecture (VSA) 1.0
Design Guide
Chapter 2 VMDC VSA 1.0 Design Overview
VMDC Virtualized Containers
•
Placement—In the Compute tier of the infrastructure, instead of the traditional aggregation layer
•
Form-Factor—vApp, rather than physical
•
Application—Dedicated per-tenant or organizational entity, rather than shared
These characteristics provide for a "pay as you grow" model with significant CAPEX savings in upfront
deployment costs. In terms of redundance implications, dedication of resources to a specific tenant
means that strict 1:1 redundancy may no longer be the default mode of operation for these forms of
service nodes. Rather, administrators now has greater flexibility to fine-tune redundant services and
methods for those tenants or organizations who have mission-critical applications with high availability
requirements.
deployment costs. In terms of redundance implications, dedication of resources to a specific tenant
means that strict 1:1 redundancy may no longer be the default mode of operation for these forms of
service nodes. Rather, administrators now has greater flexibility to fine-tune redundant services and
methods for those tenants or organizations who have mission-critical applications with high availability
requirements.
VMDC Virtualized Containers
The VMDC architecture can support multiple virtual containers, referred to as cloud consumer models.
These models are described in greater detail later in this document, and in previous release material:
These models are described in greater detail later in this document, and in previous release material:
Because this release is based on unique, dedicated per-tenant security, load balancing and optimization
services, for validation purposes VMDC VSA 1.0 focuses only on containers that do not feature shared
(multi-tenant) security/services zones. High-level representations of these are highlighted in green in
services, for validation purposes VMDC VSA 1.0 focuses only on containers that do not feature shared
(multi-tenant) security/services zones. High-level representations of these are highlighted in green in
. While the “Gold” container does not feature a shared zone, it is excluded because it is a subset
of the “Expanded Gold” container.
Figure 2-3
VMDC Containers
As you move from left to right
, the validated VMDC VSA 1.0 containers, which are based
upon real-world, commonly deployed N-tiered application and security models, become increasingly
complex, growing from single to multiple security zones and policy enforcement points and from
application of single to multiple types of services. VMDC VSA 1.0 features additional dedicated service
options, such as network analysis and optimization. Although not shown in
complex, growing from single to multiple security zones and policy enforcement points and from
application of single to multiple types of services. VMDC VSA 1.0 features additional dedicated service
options, such as network analysis and optimization. Although not shown in
, these are
validated as part of the Expanded Gold container.