The document outlines the agenda for Objective 2.4 of the VCAP6-DCV Design exam, which involves building manageability requirements into a vSphere 6.x logical design. It discusses evaluating management services, tools, and solutions based on customer requirements and defining processes for configuration, change, event, incident, problem and release management to integrate manageability into the logical design.

1. VCAP6-DCV Design 3V0-622
Objective 2.4 – Build Manageability Requirements into a vSphere 6.x Logical Design
Presented By: Jason Grierson & Ron Wedel
VCDX #206 VCDX #227
Virtualtiers@gmail.com rwedel@yahoo.com
JasonTweet7889 FD_Hauza

2. 2
Agenda
 VCAP-DCV Design Qualities Review
• Design Qualities Review
 Overview of Objective 2.4
• Evaluate which management services can be used with a given vSphere Solution.
• Differentiate infrastructure qualities related to management.
• Differentiate available command line-based management tools.
• Evaluate VMware Management solutions based on customer requirements.
• Build interfaces into the logical design for existing operations practices.
• Address identified operational readiness deficiencies
• Define Event, Incident and Problem Management practices.
• Analyze Release Management practices
• Determine request fulfillment and release management processes.
• Determine requirements for Configuration Management
• Define change management processes based on business requirements.
• Based on customer requirements, identify required reporting assets and processes

3. 3
VCAP-DCV Design Qualities - AMPRS
 Availability - Deliver highly available operation, as measured by percent uptime of relevant
components.
 Manageability - Provide ease of managing the environment and maintaining normal
operations. Subqualities may include scalability and flexibility.
 Performance - Deliver the standards of responsiveness of components of the desired environment to
meet the application workloads deployed and SLAs specified.
 Recoverability - Provide the capability to recover from an unexpected incident that affects the
availability of an environment
 Security - Provide overall data control, confidentiality, integrity, accessibility, governance, and risk
management, often including the capability to demonstrate or achieve compliance with regulation.

4. 4
How does section 2.4 tie into the VCAP-DCV Design?
Build Manageability Requirements into a vSphere
6.X Logical Design
• vMA
• vCenter
• PowerCLI
• vCLI
• vCenter Orchestrator
• vSphere API
• vSphere HA
• vSphere DRS
• Auto Deploy
• Scheduled Tasks
• Host Profiles
Define the management tools we have to work with
Availability
Performance
ManageabilityRecoverability
Security

5. 5
FAQ on Section 2.4?
• How do I score points in section 2.4?
• What will I be asked or quizzed on in 2.4?
• How do I study for section 2.4?

6. 6
Evaluate which management services can be used with a given vSphere Solution.
VCDX Example
How?
vCenter
PowerCLI scripts
vRO
Host Profiles
vDS
vUM
RQ13 Design should reduce administrative overhead
RQ08 Design must encompass all datacenters
C07 Enterprise + is highest available license
Image credit: https://www.vmware.com/pdf/vmware-validated-design-20-reference-architecture-guide.pdf

7. 7
Differentiate infrastructure qualities related to management.
Finding balance amongst our design qualities
• Single vCenter may not provide enough Availability
• Single datastore may not provide enough Performance
• Simple password policy may not provide enough Security
• Single datastore may not meet our Recoverability requirements
Availability
Performance
ManageabilityRecoverability
Security

8. 8
Differentiate available command line-based management tools
PowerCLI – Powershell cmdlets for vSphere
vCLI – command line utilities for ESXi
vMA – Appliance includes vCLI as well as logging and scripting tools
Credit: http://www.electricmonk.org.uk/2012/01/28/whats-the-diffference-between-vmware-vcli-and-vmware-powercli/

9. 9
Evaluate VMware Management solutions based on customer requirements.
VCDX Example
RQ13 Design should reduce administrative overhead
RQ08 Design must encompass all datacenters
C07 Enterprise is highest available license
What’s in?
vCenter
DRS
HA
What’s Out?
vROPS
vDS
Host Profiles
sDRS
Credit: http://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/whitepaper/vmware-vsphere_pricing-white-paper.pdf

10. 10
Build interfaces into the logical design for existing operations practices.
• Active directory
• Syslog
• CMDB
• SNMP
• Alerts / Ticketing
• Hardware Monitoring
• Certificates
• Maintenance windows

11. 11
Address identified operational readiness deficiencies
Operational Readiness is defined as “the capability to routinely provision, consume and operate a
virtual datacenter in compliance with IT governance”
Reference: https://communities.vmware.com/docs/DOC-11457
• Fill out the OR self
assessment
• Find areas of deficiencies
• Resolve where you can
• Highlight risks/concerns
where you can’t

12. 12
Define Event, Incident and Problem Management practices
Event, Incident and Problem Management This concept is related to the well known ITIL
standard.
Event: A change of state which might have an influence for the management of a
service or system.
Incident: An event which is not part of the standard operation. It might cause a service
disruption or reduce the productivity.
Problem: The cause of one or more incidents. Problems are usually identified because
of multiple incidents.
Please note that an incident might give a hint to the investigation of a Problem, but never become a Problem. Even if the
incident is elevated to the 2nd level, it remains an incident. The problem management might manage the resolution of the
incident when the incident can only be closed by solving the Problem.

13. 13
Analyze Release Management practices
Release and Deployment Management: The goal of the Release and
Deployment Management process is to assemble and position all aspects of services into
production and establish effective use of new or changed services. Effective release and
deployment delivers significant business value by delivering changes at optimized speed,
risk and cost, and offering a consistent, appropriate and auditable implementation of
usable and useful business services. Release and Deployment Management covers the
whole assembly and implementation of new/changed services for operational use, from
release planning through to early life support.
• Define a process to get a service into
production
• Optimized, cost efficient, low risk,
consistent, auditable, usable and
useful for business service
deployment
• Tools at our disposal
• VMware templates
• Snapshots
• Scripting (vMA)
• vSphere Orchestrator
• vRealize Suite

14. 14
Determine request fulfillment and release management processes
Request Fulfillment Process: A service request is a request from a user for information or
advice, or for a standard change, or for access to an IT service.
The purpose of Request Fulfillment is to enable users to request and receive standard
services; to source and deliver these services; to provide information to users and customers
about services and procedures for obtaining them; and to assist with general information,
complaints and comments. All requests should be logged and tracked. The process should
include appropriate approval before fulfilling the request.
Translation: Assign roles within VMware environment / tools to roles
in the organization that can fulfill user requests
Tools at our disposal:
• vCenter Permissions to vCenter Infrastructure
• Tempaltes
• vSphere Orchestrator
• Self Service Portal
• Scripting

15. 15
Determine requirements for Configuration Management
Change Management: Ensures that changes are recorded, evaluated,
authorized, prioritized, planned, tested, implemented, documented and
reviewed in a controlled manner.
The purpose of the Change Management process is to ensure that standardized
methods are used for the efficient and prompt handling of all changes, that all
changes are recorded in the Configuration Management System and that
overall business risk is optimized.
The process addresses all service change.
Service Asset and Configuration Management (SACM)
SACM supports the business by providing accurate information and control
across all assets and relationships that make up an organization’s
infrastructure.
The purpose of SACM is to identify, control and account for service assets and
configuration items (CI), protecting and ensuring their integrity across the
service lifecycle.
The scope of SACM also extends to non-IT assets and to internal and external
service providers, where shared assets need to be controlled.
To manage large and complex IT services and infrastructures, SACM requires
the use of a supporting system known as the Configuration Management
System (CMS).
Key Notes
• Process to control
change.
Tools at our disposal
• vRealize Configuration
Manager
• Creating change control
roles to align with change
policices that can adjust
templates and other
request fulfillment tools
Key Notes
• Asset Management of IT
and non-IT business
Assets
• Service lifecycle

16. 16
Based on customer requirements, identify required reporting assets and processes
• Determine Monitoring requirements
• Determine Change control requirements
• Determine SLA for the infrastructure or different support
groups
• Determine what assests need to be kept track of and
monitored
• Determine how newly deployed VM's will stay consistent or be
deploy efficiently
• If this is a consulting engagement when you give the project
over to the customer how will they maintain the infrastructure /
VM’s and scale. (Change control / Documentation)

17. 17
Resources Used
• https://communities.vmware.com/docs/DOC-17410
• https://en.wikipedia.org/wiki/Event_Management_(ITIL)
• http://elatov.github.io/2012/08/vcap5-dcd-objective-2-4-build-
manageability-requirements-into-the-logical-design/
• https://communities.vmware.com/docs/DOC-11457
• https://www.vmware.com/pdf/vmware-validated-design-20-
reference-architecture-guide.pdf