Press "Enter" to skip to content

Objective 2.4 – Build Manageability Requirements into the Logical Design


  • Understand what management services are provided by VMware solutions.
    • vMA
    • vCenter
    • PowerCLI
    • vCLI
    • vCenter Orchestrator
    • vSphere API
    • vSphere HA
    • vSphere DRS
    • Auto Deploy
    • Scheduled Tasks
    • Host Profiles
  • Identify and differentiate infrastructure qualities (Availability, Manageability, Performance, Recoverability, Security)

See Previous Objective 

Skills and Abilities

  • Build interfaces to existing operations practices into the logical design

After gathering all the information get whats is currently being used to manage the environment and integrate it into this design like integrating vCenter with LDAP so the existing user management will now be incorporated into the new vSphere design.

  • Address identified operational readiness deficiencies

Any deficiencies that are picked up during the current-state analysis can be addressed in the design. for example No monitoring is currently active, this can be enabled in vCenter to send emails when major issues occur.

  • Define Event, Incident and Problem Management practices

Most places these days are ITIL aligned and usually very loosely so they may follow the 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 standard operation and usually causes a service disruption to degrade functionality
    • Problem – The cause of one or more incidents.
  • Define Release Management practices

The Service Management process that encompasses the planning, design, build, configuration and testing of hardware and software releases to create a defined set of release components. Release activities also include the planning, preparation, scheduling, training, documentation, distribution and installation of the release to many users and locations. Release Management uses the controlling processes of Change and Configuration Management.

ITIL describes it:

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
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.

  • Determine Request Fulfillment processes

Again from ITIL:

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.

  • Design Service Asset and Configuration Management (CMDB) systems

Again from ITIL:

SACM supports the business by providing accurate information and control
across all assets and relationships that make up an organization’s
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).

Most places would use their ticketing system as their CMDB like BMC Remedy, CA Unicenter or HP Service Management System. These generally have the ability to track configuration items and will also track change tickets with those configuration items. There are plenty of over CMDB application out there.

VMware Configuration Manager can keep track of all changes in your environment

  • Define Change Management processes

Again from ITIL:

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. A Service Change is the addition, modification or removal of an authorised, planned or supported service or service component
and its associated documentation.

Therefore change management is relevant across the whole lifecycle, applying
to all levels of service management – strategic, tactical and operational.
Change management delivers, to the business, reduced errors in new or
changed services and faster, more accurate implementation of changes; it
allows restricted funds and resources to be focused on those changes to achieve
greatest benefit to the business.

  • Based on customer requirements, identify required reporting assets and processes

Determine what needs to be monitored, these could be defined by a requirement or SLAs, for example tracking how many VMs get deployed on a daily basis

Leave a Reply

Your email address will not be published. Required fields are marked *

Anti SPAM BOT Question * Time limit is exhausted. Please reload CAPTCHA.