Cisco Cisco Prime Virtual Network Analysis Module (vNAM) 6.3 White Paper
3-42
Cisco Virtualized Multiservice Data Center (VMDC) Virtual Services Architecture (VSA) 1.0
Design Guide
Chapter 3 VMDC VSA 1.0 Design Details
System Level Design Considerations
customization. CLSA-VMDC offers real-time aggregated dashboards and reporting capabilities.
CLSA-VMDC can be deployed in centralized and distributed architectures, and supports incremental
deployment growth. While CLSA-VMDC offers rich functionality for IaaS domains, the solution is
lightweight and has open interfaces to enable simple integration into existing operations support system
(OSS) and ticketing systems with minimal cost. This solution is positioned not as a replacement, but as
a complement to existing Manager-of-Manager (MOM) systems (for example, IBM Netcool), ticketing
systems (for example, BMC Remedy), and so on. Additional documentation can be found on Design
Zone at
CLSA-VMDC can be deployed in centralized and distributed architectures, and supports incremental
deployment growth. While CLSA-VMDC offers rich functionality for IaaS domains, the solution is
lightweight and has open interfaces to enable simple integration into existing operations support system
(OSS) and ticketing systems with minimal cost. This solution is positioned not as a replacement, but as
a complement to existing Manager-of-Manager (MOM) systems (for example, IBM Netcool), ticketing
systems (for example, BMC Remedy), and so on. Additional documentation can be found on Design
Zone at
Storage QoS
Tenant workloads in the VMDC datacenter should be prevented from affecting each other. While this is
handled by QoS mechanisms at the network layer, those QoS mechanisms do not protect performance at
the storage layer. Because all storage I/O traffic is classed the same in the VMDC datacenter, all tenants
receive an equal share of the storage performance capacity unless controlled by some other mechanism.
Without implementing performance limits on storage I/O, the performance of one tenant workload may
suffer due to the overwhelming use of storage I/O by a neighboring tenant workload sharing the same
physical hardware.
handled by QoS mechanisms at the network layer, those QoS mechanisms do not protect performance at
the storage layer. Because all storage I/O traffic is classed the same in the VMDC datacenter, all tenants
receive an equal share of the storage performance capacity unless controlled by some other mechanism.
Without implementing performance limits on storage I/O, the performance of one tenant workload may
suffer due to the overwhelming use of storage I/O by a neighboring tenant workload sharing the same
physical hardware.
Additionally early adopter tenants' workloads may experience higher than normal performance early in
a PoD lifecycle due to the low number of tenants using the resources. Without setting storage
performance caps those tenants may perceive a decrease in storage performance once the tenant capacity
for their PoD has been reached. Even though the performance level they are receiving may be within the
bounds of the tenant's service level agreement, the tenant may perceive that performance has dropped
below the expected level.
a PoD lifecycle due to the low number of tenants using the resources. Without setting storage
performance caps those tenants may perceive a decrease in storage performance once the tenant capacity
for their PoD has been reached. Even though the performance level they are receiving may be within the
bounds of the tenant's service level agreement, the tenant may perceive that performance has dropped
below the expected level.
NetApp FAS controllers running clustered Data ONTAP prevent workloads from impacting each other
through the use of Storage Quality of Service (
through the use of Storage Quality of Service (
Figure 3-29
Application of Storage QoS
NetApp Storage QOS allows I/O ceilings do be defined in terms of IOPS. Those performance ceilings
can be applied to individual workloads or to groups of workloads. In a multi-tenant environment, a
tenant could have IOPS limits set across all workloads hosted within a particular ICS or could have limits
set on each deployed workload.
can be applied to individual workloads or to groups of workloads. In a multi-tenant environment, a
tenant could have IOPS limits set across all workloads hosted within a particular ICS or could have limits
set on each deployed workload.
For additional information on NetApp Storage QoS, see