Management With Insight Dynamics-Vse; Hp Insight Dynamics - Vse Integrates Virtual And Physical Management - Compaq BL10e - HP ProLiant - 512 MB RAM Introduction Manual

Delivering an adaptive infrastructure with the hp bladesystem c-class architecture
Hide thumbs Also See for BL10e - HP ProLiant - 512 MB RAM:
Table of Contents

Advertisement

Management with Insight Dynamics-VSE

Embedded management capabilities in the BladeSystem platform and integrated management
software streamline operations and increase administrator productivity. Beyond the traditional role of
management, one of the key areas in an Adaptive Infrastructure includes virtualized infrastructure
management. Contrary to early buildup about virtual machines, they do not simplify the overall
environment except for a reduction in physical server inventory. Rather, they introduce a new layer of
management for the virtual machines, which has often required a completely separate set of
management tools in addition to the standard physical system management tools.
HP Insight Dynamics – VSE integrates virtual and physical management
A major goal of the HP Adaptive Infrastructure has been to integrate virtual and physical server
management into a single consistent environment. The first major deliverable of this effort has been
Insight Dynamics – VSE, a management suite incorporating virtual and physical management,
continuous optimization, and a unified GUI.
At the core of ID-VSE is a virtualization abstraction known as a template. A template is a universal
abstraction of a server consisting of the following elements:
• OS and application stack – The software environment for the server, represented as a link to the boot
path for the server. For example, a web server is different from an application server because links
are created to two different runtime environments for the same server hardware.
• Runtime entitlements – Description of resources needed at runtime, including memory, number of
cores, I/O bandwidth, and so on.
• User-specific data – Administrators must add in specific ID values to convert a template into a
specific logical server. For example, to take a "web server" template and convert it into a specific
instance of a departmental web server with its own content, administrators need to add user-specific
data, such as MAC addresses, WWNs, and global IDs.
A template can be deployed as either a virtual machine or a ProLiant c-Class server blade. Because
the physical and virtual servers are generated from a common set of metadata, templates provide the
foundation for a new set of merged physical and virtual management capabilities, including
transparent P2V and V2P migration
(Figure 8).
Once it is defined, a generic template can be reused for multiple servers and stored in a library of
templates. It can also be used as an element in the Insight Orchestration designer tool (see following
section) as part of a complex infrastructure.
9
The initial release of ID-VSE provides for V2V and P2P migration, but future versions will integrate the V2P and
P2V transitions. Currently P2V and V2P are available by means of an escape from the ID-VSE console to the HP
Server Migration Pack, a standalone utility for server migration.
9
and management integration into a common framework
17

Advertisement

Table of Contents
loading

Table of Contents