Professional Documents
Culture Documents
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 1/81
5/9/2019 Full text of "Virtualization at Fujitsu"
FUJITSU
White paper
Virtualization at Fujitsu
This whitepaper examines the various virtualization technologies and shows the range of ICT
infrastructure layers where they are applied. It also shows how Fujitsu incorporates these
technologies into end-to-end solutions as an essential part of its Dynamic Infrastructures strategy.
Page 1 of 32
www.fujitsu.com
Introduction
What is virtualization?
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 2/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Monitor
Application VM
= OS+App
Customer
Customer
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 3/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Application VM
= GS+App
Application
abstractions
Desktop
abstractions
Container
abstractions
OS-basedVM
abstractions
Hypervisor-based
VM abstractions
Physical
abstractions
Server I/O
abstractions
Network
abstractions
Storage
abstractions
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 4/81
5/9/2019 Full text of "Virtualization at Fujitsu"
1 Intel VirtualizationTechnology(VT),
1 AMDVirtualization(AMD-V)...
BpH 1
HM | tisco, Brocade...
Page 2 of 32
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 5/81
5/9/2019 Full text of "Virtualization at Fujitsu"
www.fujitsu.com
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 6/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Application
® ® ° 5 §> ®
UiardwanP
Traditional approach
Application
OS
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 7/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Virtualization layer
Hardware
Virtualization approach
In the past, the ability to run older OS versions on the latest hardware
was one key motivation for deploying hypervisor technology. Now
customers also expect further benefits from server virtualization; in
particular greater agility, higher availability and lower operating costs.
Page 3 of 32
www.fujitsu.com
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 8/81
5/9/2019 Full text of "Virtualization at Fujitsu"
App
App
OS
App
OS
App
OS
Hypervisor
Hardware
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 9/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Mid-sized businesses have the same expectations, but their top five
implementation priorities are different:
■ Consolidation: This is number one here too, but the level of savings is
lower due to the smaller server deployment scale.
Bare-metal environment
OS hosted environment
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 10/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Page 4 of 32
www.fujitsu.com
Virtual machines
Server virtualization tricks the virtual machine into only seeing the
same virtual hardware (CPU, memory and I/O devices) regardless of the
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 11/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Key features
Case studies
With three separate campuses in the greater Tokyo area, this science
and technology university was seeking a way to reduce their total
cost of ownership of ICT equipment. The existing UNIX servers at
each location required separate administration as well as local
Network Attached Storage (NAS). Introduction of 500 Mbps
inter-campus transmission speeds paved the way for a more
consolidated approach. The move to on-demand remote class work
has also put pressure on the inflexibility of the existing systems.
Initially they envisaged a virtual machine environment at each
campus. However, with the new communications backbone this
quickly developed into a centralization plan.
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 12/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Page 5 of 32
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 13/81
5/9/2019 Full text of "Virtualization at Fujitsu"
www.fujitsu.com
Hypervisors
General characteristics
Market relevance
Today over 20 hypervisors are available in the market, but the direction
is towards a few dominant hypervisor vendors. It is for this reason that
Fujitsu primarily focuses on a select few hypervisors for its
consolidation solutions. The following graphic from the Gartner
research company, shows the projected market share for virtualization
vendors in 2012, by number of VMs deployed.
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 14/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Red Hat
2% A Others 1%
Citrix6%_ \ |
Microsoft
27%
Vmware
64%
FY 201 2 (58MVMs)
Note that major ISVs now offer their products as appliances, i.e. the
application ships as part of the virtual machine and not in conventional
installation format. Conseguently, the application is independent of
the type of server it runs on. This reduces the time and effort ISVs need
to spend on Q&A. However, it can result in end customers using more
than one hypervisor. To minimize the complexity this involves, vendors
are working on standardizing VM formats (for example Microsoft and
Citrix) enabling virtual machines of a specific hypervisor to run on
another hypervisor, at no cost or effort. This feature is also important
when choosing a suitable hypervisor.
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 15/81
5/9/2019 Full text of "Virtualization at Fujitsu"
This was the catalyst for other hypervisor vendors to enter the market
with new offerings based on the "hardware assist" technology of the
processor vendors.
Page 6 of 32
www.fujitsu.com
1 . VMware vSphere
Service console
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 16/81
5/9/2019 Full text of "Virtualization at Fujitsu"
VM
VMM
VM VM VM
The VMware vSphere hypervisor runs directly on the hardware layer and
acts as an independent OS. The kernel takes care of all of the following:
The overall size (2GB) of the classic main version is due to the Linux
subsystem. The subsystem enables the installation of agents to
manage the underlying hardware. It also includes interfaces for
management of the hypervisor. VMware intends to phase out this
architecture in 201 1 and reduce the hypervisor back to its pure kernel
stack, with special interfaces for management. The future embedded
VMware architecture looks like this:
CIM
Client
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 17/81
5/9/2019 Full text of "Virtualization at Fujitsu"
VM VM VM VM
v5phere API
vSphere Client
vCLl, Power CLI
_ iostc
1 CIM 1
Provider 1
Network
stack
Virtual 1 n 1 Clustered 1 r
NICsS 1 °™ ce 1 VM file 1 5tora f 1
c t u 1 drivers 1 1 stack I
Switches 1 1 system 1
m '-,-oe H
vCenter
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 18/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Info box
With the removal of the subsystem in which agents can run, a new
interface is required. This now becomes the task of each hardware
vendor using the new Common Information Model (CIM) Interface.
CIM is an open standard that defines how computing resources are
represented and managed. It enables a new framework for
agent-less, standards-based, monitoring of hardware resources for
the vSphere hypervisor. This framework consists of a CIM object
manager, otherwise called a CIM broker, and a set of CIM providers.
Each hardware vendor will need to create specific CIM providers for
their hardware.
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 19/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Page 7 of 32
www.fujitsu.com
VMware management
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 20/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Vmware vCloud
■ vCloud Director
■ vCloud Express
VmwarevFabric
— vFablit tc Server
vFabric GemFire
vFablric RabbittMQ -£
i Performance monitoring
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 21/81
5/9/2019 Full text of "Virtualization at Fujitsu"
vCenter Qrchestrator
vCenter Server Heartbeat
vCenter Capacity IQ
vCenter AppSpeed
vCenter ChargeBack
vCenter Site Recovery Manager
vCenter Configuration Manager
■ VMware View
■ VMware ThinApp
■ VMware Workstation
■ VMware Fusion
■ VMware ACE
■ Zimbra
Vmware vSphere
hardware resources
applications
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 22/81
5/9/2019 Full text of "Virtualization at Fujitsu"
VMware vShield
— vShield Endpoint
vShield App
vShield Edge
Page 8 of 32
www.fujitsu.com
VM migration technology
Agility is the next benefit, in particular this covers the ability to move a
virtual machine from one server to another while it is running. All
hypervisor vendors deliver this functionality under various names
including, vMotion (VMware), XenMotion (Citrix) and Live Migration
(Microsoft). Here we will use a vMotion example, but the technology
and functions of each are very similar.
VMware vMotion
Secondly, the active memory and precise execution state of the virtual
machine is rapidly transferred over a high-speed network. This lets the
running virtual machine switch almost instantaneously from the source
vSphere host to the destination vSphere host. Users do not notice.
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 23/81
5/9/2019 Full text of "Virtualization at Fujitsu"
User benefits
■ Optimized workloads
App
1 |
■ I
App
OS
._.
App
OS
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 24/81
5/9/2019 Full text of "Virtualization at Fujitsu"
VMotion technology
vSphere hypervisor
Hardware
vSphere hypervisor
Hardware
Thirdly, the underlying vSphere host virtualizes the networks use by the
virtual machine. This ensures that even after migration, the network
identity and network connections of the virtual machine are preserved.
vMotion manages the virtual Media Access Control (MAC) address as
part of this process. Once it has activated the destination machine,
vMotion simply pings the network router to ensure it is aware of the
new physical location of the virtual MAC address. Since the migration of
the virtual machine using vMotion preserves the precise execution
state, network identity, and active network connections, the result is
zero downtime and no user disruption.
Page 9 of 32
www.fujitsu.com
2. CitrixXenServer
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 25/81
5/9/2019 Full text of "Virtualization at Fujitsu"
XenServer features
DomO
Linux
Doml
Linux
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 26/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Dom2
■\e:wa~e
Hypervisor
■ Datacenter automation
■ Citrix VMLogix
The high performance virtual infrastructure set is free and builds the
main base for virtualization, including the following function set:
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 27/81
5/9/2019 Full text of "Virtualization at Fujitsu"
■ XenServer hypervisor
■ XenMotion
■ Conversion tools
Page 10 of 32
www.fujitsu.com
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 28/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Datacenter automation
■ Site recovery
■ High availability
■ Auto-restart capability
■ Lifecycle management
■ Memory optimization
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 29/81
5/9/2019 Full text of "Virtualization at Fujitsu"
■ Provisioning services
■ Role-based administration
■ StorageLink
■ Heterogeneous pools
Live VM snapshot and revert, captures memory and disk state during a
snapshot. This speeds system provisioning and ensures periodic
backup.
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 30/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Page 11 of 32
www.fujitsu.com
CitrixVMLogix group
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 31/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Xen arena. Now Citrix has developed a new strategy around the Xen
product positioning XenServer as the elementary component of this
strategy.
Page 12 of 32
www.fujitsu.com
3. Microsoft Hyper-V
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 32/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Parentpartition
Child partitions
ii ir
■<■■■ Worker
Processes .. User
Windows
Kerne
Kerne
vmbus mode
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 33/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Windows hypervisor
Ring -
From a naming perspective, what was domain with Xen becomes the
parent partition with Hyper-V. Child partitions correspond to Xen
domains. One big advantage of this structure is that excellent Windows
driver support automatically applies to the virtualization layer. This
makes Hyper-V the server virtualization layer with the broadest driver
support. In addition, Hyper-V uses all the features of the new processor
families from Intel and AMD. There is optimized communication
between Windows Server 2003/Windows Server 2008 and the
hypervisor and physical components. Having a Windows based
hypervisor and using the VMBus make this possible. Even with Linux,
Hyper-V uses special hardware features from Intel (Hypercall Adapter)
to improve the performance of Linux OS based applications running in
Hyper-V virtual machines. This means Hyper-V, in addition to its other
capabilities, fits very nicely into virtualized Linux environments.
Microsoft Hyper-VServer
Hyper-V
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 34/81
5/9/2019 Full text of "Virtualization at Fujitsu"
MicrosoFt
Hyper-VserverR2
Windows Server
2008 R2 Enterprise
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 35/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Page 13 of 32
www.fujitsu.com
Administrator's Self-service
console Web Portal
Windows PowerShell
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 36/81
5/9/2019 Full text of "Virtualization at Fujitsu"
SDK connection
Operations Manager
server
^W SQLServer r^M
Management interfaces
SAN Storage
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 37/81
5/9/2019 Full text of "Virtualization at Fujitsu"
■ System Center Essentials (SCE, a special offering for the SME market)
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 38/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Page 14 of 32
www.fujitsu.com
Red Hat started virtualization using the open source product Xen.
However, following the acquisition of XenSource by Citrix, Red Hat
changed its virtualization strategy. In September 2008, Red Hat
announced the acquisition of Qumranet, Inc. The acquisition included
Qumranet's virtualization solutions, its KVM (Kernel Virtual Machine)
platform and SolidlCE, a virtual desktop infrastructure (VDI). Together
they provide a comprehensive virtualization platform for enterprise
customers. In addition, as part of the deal, Qumranet's team of
professionals who were developing, testing and supporting the
solutions, (and leaders in the open source community KVM project)
joined Red Hat. Red Hat subsequently focused on making the KVM
technology, which is actually part of every standard Linux operating
system, into its own virtualization strategy. Their approach uses
kernel-based VMs. This means each VM is mapped in a normal Linux
process that is managed using customary Linux mechanisms. A special
KVM driver is part of the Linux kernel and, among other things,
controls I/O communication between the VMs and the real hardware.
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 39/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Secondly, KVM applied a tried and true adage - "don't reinvent the
wheel". Hypervisors need many components in addition to virtualized
CPU and memory. For example, a memory manager, process scheduler,
I/O stack, device drivers, security manager, network stack, etc. In fact,
the hypervisor is really a specialized operating system, the only
difference being it runs virtual machines rather than applications. With
the Linux kernel already including the core features required by a
hypervisor, plus with the maturity and enterprise platform
performance, from over 1 5 years of support and development, it was
more efficient to build on that base rather than write all the same
components again for the hypervisor. In this regard, KVM benefited
from Red Hat's experience with Xen. One of the key challenges of Xen
is the split architecture of domainO and the Xen hypervisor. Since the
Xen hypervisor provides the core platform features within the stack, it
needed to implement the OS-like feature from scratch. However,
because the Linux kernel was already mature and had a proven
memory manager, including support for NUMA (Non-Uniform Memory
Access), large-scale systems, and power management; the decision
was made to incorporate the KVM into the upstream Linux kernel. Red
hat submitted the KVM code to the Linux kernel community in
December of 2006 and acceptance into the 2.6.20 kernel came in
January of 2007. It was at this point that KVM became part of the Linux
core and able to inherit all the key features in the Linux kernel.
KVM Architecture
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 40/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Drivers
VM
D" ve~s
VM
VM
Di vers
Hardware
Page 15 of 32
www.fujitsu.com
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 41/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Hardware support
Virtualization management
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 42/81
5/9/2019 Full text of "Virtualization at Fujitsu"
virtualization format)
■ V2V Conversion Tools to Import Red Hat Enterprise Linux guests from
Red Hat Enterprise Linux/Xen or VMware. Additional converters are
expected will be available in the future
Page 16 of 32
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 43/81
5/9/2019 Full text of "Virtualization at Fujitsu"
www.fujitsu.com
5. Oracle VM
The growing range of offerings in the market raises the question for ICT
organizations of which they should consider. Should it be one for all or
should it be a combination of several depending on use. At a first
glance, it sounds reasonable to go for a one-for-all and
follow-the-market-leader approach.
This is where the use of Oracle VM can be of great help. The complete
stack, above the server hardware, all comes from the one vendor, they
take responsibility for the entire support:
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 44/81
5/9/2019 Full text of "Virtualization at Fujitsu"
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 45/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Page 17 of 32
www.fujitsu.com
6. Novell
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 46/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Datacenter consolidation
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 47/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Page 18 of 32
www.fujitsu.com
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 48/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Summary
Page 1 9 of 32 www.fujitsu.com
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 49/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Hardware support
App
App
App
App Ring 3
(Ring 1&2)
Ring
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 50/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Ring is where the operating system (OS) runs with the OS kernel
controlling access to the underlying hardware. Rings 1, 2 and 3 operate
with lower privilege levels and are prevented from executing
instructions reserved for the operating system. In common operating
systems such as Linux and Windows, the operating system runs in ring
and the user applications run in ring 3. Rings 1 and 2 are not used by
modern commercial operating systems. This architecture ensures that
an application, running in ring 3, cannot make privileged system calls.
However, a an operating system running in ring hardware does
expose applications running in lower privilege levels. This model
provides benefits in traditional, "bare metal" deployments, but it does
present challenges in a virtualized environment.
Ring 3
Hypervisor
(Ring 1&2)
Ring
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 51/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Binary translation
Page 20 of 32
www.fujitsu.com
Paravirtualization
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 52/81
5/9/2019 Full text of "Virtualization at Fujitsu"
patches to the Linux kernel. Later they were incorporated into the
released Linux kernel.
The current generation of Intel and AMD CPUs, and chipsets, are now
adding support for I/O offloading. This includes secure PCI
pass-through, using Intel VT-D and AMD I0MMU. This allows PCI devices
on the host to be passed directly into the virtual machine. Single Root
I/O virtualization (SR/IOV) further extends those features to allow
special PCI devices to be split into multiple virtual PCI devices that can
also be passed through to individual virtual machines. These features
are allowing virtual machines to achieve the same I/O performance as
the original bare metal systems.
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 53/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Eventually, both Intel and AMD developed extensions for their x86
architecture to provide features for use by hypervisor vendors to
simplify CPU virtualization. The first CPUs with these features were
released in late 2005. Today most Intel and AMD CPUs include
hardware virtualization support, including desktop, laptop and server
product lines.
Page 21 of 32
www.fujitsu.com
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 54/81
5/9/2019 Full text of "Virtualization at Fujitsu"
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 55/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Page 22 of 32
www.fujitsu.com
■ Live migration of related file system entries of VMs (more flexible use
of different storage units)
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 56/81
5/9/2019 Full text of "Virtualization at Fujitsu"
VM VM VM
vSphere hypervisor
►j VM 1 1 VM
l ! I
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 57/81
5/9/2019 Full text of "Virtualization at Fujitsu"
vSphere hypervisor
VM VM VM
vSphere hypervisor
Every vSphere host has its own virtual switch, which manages the
network connection using the build-in LAN cards and present virtual
machines. Virtualization administrators typically manage virtual
machine networking at the physical server level, using virtual switches
inside the hypervisor. Virtual switches require consistent configuring
across many physical hosts, and aligned with the physical network. This
means virtualization and network administrators must work closely
together to ensure proper virtual machine connectivity. Once deployed,
both must continue the close working for joint troubleshooting and
monitoring of the virtualized datacenter.
For new VM's or when moving VM's from one host to another, network
connections need to be adjusted. This means a lot of complex
administration in large environments. VMware vNetwork Distributed
Switch provides a central point of control for such datacenter-level
virtual networking.
Page 23 of 32
www.fujitsu.com
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 58/81
5/9/2019 Full text of "Virtualization at Fujitsu"
VM
NET STATE
VM
NET STATE
VM
NET STATE
VMwarevSphene
VMwarevSphere
VMwarevSphene
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 59/81
5/9/2019 Full text of "Virtualization at Fujitsu"
virtual switches such as the Cisco Nexus 1000V virtual switch. The Cisco
Nexus 1 000V provides customers with virtual machine granularity and
control using familiar networking tools, allowing end-to-end network
management across both physical and virtual machine environments.
That means that users who have installed Cisco based network
environment have common and uniform network administration.
Production
Recovery
App
App
App
OS
Hypervisor
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 60/81
5/9/2019 Full text of "Virtualization at Fujitsu"
App App
App
OS
I Hypervis
w 1
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 61/81
5/9/2019 Full text of "Virtualization at Fujitsu"
I/O virtualization
Use of I/O virtualization will overcome these issues. MAC addresses and
WWN as shown to the network must stay fixed.
However, virtualizing the operational I/O addresses will enable dynamic
movement of I/O addresses between servers. If this is fully transparent
to the LAN and SAN domain there is no need to change any network
addresses, or create extra work for the network administrators. This I/O
virtualization reduces management complexity and provides greater
flexibility both when deploying new servers and services and when
replacing failed servers.
The basic idea of "HBA address rename" is the use of a "logical (virtual)
WWN", which overwrites the fixed (physical) factory-default WWN on
the HBA. The logical (virtual) WWN is used to map the HBA to the
system volume. This method sets the WWN of any spare server's HBA to
the same value as originally set on the production server. This allows
the spare server to connect to and boot from the same boot disk used
by the original production server.
Fujitsu ServerView VIOM takes care of both the virtual MAC (for NIC)
and virtual WWN (for HBA) as part of the server profile assigned to
each production server. If the production server fails, the WWN, MAC
address, boot configuration, and network configuration are simply
inherited by the spare server. Restart is then automatic using the same
SAN disk previously used by the production server.
Page 24 of 32
www.fujitsu.com
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 62/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Normal operation
NIC
HBA
NIC
HBA
MAC #1
WWN #1
NIC
HBA
MAC #1
WWN #1
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 63/81
5/9/2019 Full text of "Virtualization at Fujitsu"
NIC
HBA
NIC
HBA
Benefits:
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 64/81
5/9/2019 Full text of "Virtualization at Fujitsu"
This is why I/O virtualization was done first with blade servers. The
management blade (Note: Fujitsu PRIMERGY BX400 and BX900 blade
servers have two redundant management blades per chassis) is the
central point for collection, storage and management of each blades
status. Due to the homogenous blade architecture it is easy to
re-assign hardware addresses.
ServerView VOIM
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 65/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Page 25 of 32
www.fujitsu.com
VDI gives users the best of all three of these concepts. Virtual desktops
can be individualized and isolated. They also provide considerable
improvements in terms of availability, security, manageability, resource
utilization and energy consumption. One unique benefit of VDI is the
ability gain access to a users' desktop environment from anywhere.
This allows very flexible execution just by logging on at available
terminal. Finally, software lifecycles can be extended, as any previous
dependence between hardware and software is removed.
-it 3 -it
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 66/81
5/9/2019 Full text of "Virtualization at Fujitsu"
--
^
Apps
OS
Apps
OS
Apps
OS
Virtualization Layer
Info box
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 67/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Together with its full range of traditional Thin Clients, Fujitsu also
provides a range of innovative Zero Clients. These provide
clutter-free, space-saving productivity as well as complete silence in
the office. While, the low running costs of traditional Thin Clients
result from server based computing to minimize the computing
power (minimal CPU, memory and graphics processing) required at
the desktop; Zero Clients contain no computing power whatsoever.
This revolutionary front-end device has all the benefits of Thin
Clients, but further increases the manageability, security, and cost
benefits, of desktop virtualization.
Traditional
desktop environment
Virtual Desktop
Infrastructure (VDI)
Page 26 of 32
www.fujitsu.com
What is needed?
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 68/81
5/9/2019 Full text of "Virtualization at Fujitsu"
This situation remains very complicated for many users especially with
different hypervisor products in place. Taking advantage of each
hypervisor's specific management tools will mean embracing further
management complexity. The best advice therefore is to introduce a
hypervisor-aware management tool that handles the common basic
daily operations and only drop down to hypervisor specific
management tools for specific functionality.
ISetveiV
Status
Q0S
©<
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 69/81
5/9/2019 Full text of "Virtualization at Fujitsu"
[ Option... | | «- Date*! ]
- & System
Fa-,5
^ Temperature Sensors
r^ Power Supply
s^ Power Supply
& Power level
t^roass Storage
} System Processors
JBIOSSeNest
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 70/81
5/9/2019 Full text of "Virtualization at Fujitsu"
This is also true with the allocation of LAN and SAN addresses. When
one server assumes the role of another, especially with blade servers,
Fujitsu ServerView RCVE uses the very convenient I/O virtualization
functions of Fujitsu ServerView VIOM. As a result, long system
installation times needed for application relocation become a thing of
the past. Applications that run on multiple servers can be cloned and
then installed on the desired number of servers in a matter of minutes.
Page 27 of 32
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 71/81
5/9/2019 Full text of "Virtualization at Fujitsu"
www.fujitsu.com
r-,.
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 72/81
5/9/2019 Full text of "Virtualization at Fujitsu"
on demand, and just in time. This can happen when the service is
needed, after a failure, or in conjunction with a change in workload. It
means applications can run on servers without any fixed installation
concept. The architecture of this approach is as follows:
Server
Pool
Storage
Pool
Operating systems
Applications
□ □□□□
Luuuuu
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 73/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Page 28 of 32
www.fujitsu.com
Orchestration
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 74/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Resource
Management
Abstraction and
Virtualization
Server
Virtualization
I/O Address
Virtualization
Storage
Virtualization
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 75/81
5/9/2019 Full text of "Virtualization at Fujitsu"
When individual servers are assigned for every application, the typical
result is inefficient use of system resources and high administrative
overheads. The first step in optimization therefore, is the relocation of
applications from isolated servers to pooled architecture. The creation
of pools and the use of server virtualization, significantly increase
resource utilization and management efficiency, and reduce the server
count.
The use of Fujitsu PRIMERGY BX400 and BX900 systems for pool
creation makes handling of the physical servers very simple, especially
as I/O connections and cables are highly consolidated. In addition,
management of both physical and virtual servers is possible with just
one tool - Fujitsu ServerView RCVE. There is also no need to set up
separate resource pools forVMware, Hyper-V, Xen, Linux or Windows.
The one consolidated resource pool rationalizes and leverages all
assets. This also applies to high availability, as the N:1 failover
supported by Fujitsu ServerView RCVE ensures a minimum of standby
systems are required. To summarize:
Once the server pool is up and running, all resources become dynamic.
Changes are possible within minutes. Automated operation is also
possible. For example, moving server resources based on schedules
(for day and night or week/weekend operation) or even in response to
sudden changes in workload, becomes straightforward and automatic.
The dynamic server infrastructure created by Fujitsu PRIMERGY blade
servers, Fujitsu ServerView VIOM and Fujitsu ServerView RCVE make
these and other scenarios simple to handle. The main additional
benefits are:
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 76/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Dynamic Resourcing
Page 29 of 32
www.fujitsu.com
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 77/81
5/9/2019 Full text of "Virtualization at Fujitsu"
hardware. Many functions like vMotion, HA, FT, DRS, SRM cannot
happen without a central storage system. A storage system is the
center of any VM farm. The challenge for each storage vendor is to
support virtualization as best as possible. It therefore makes sense to
move storage intensive tasks of the hypervisor and perform them
directly in the storage system. To enable this, hypervisor vendors are
delivering APIs to allow greater interaction with storage system.
■ Storage vMotion
vStorage APIs for Data Protection are for use by enterprise backup
solutions to secure virtual machines during runtime. They allow
administrators to execute scalable backup without disrupting
applications or users. Fujitsu ETERNUS storage systems with vStorage
APIs for Data Protection become a very effective way to enable general
backup in medium to large datacenter environments.
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 78/81
5/9/2019 Full text of "Virtualization at Fujitsu"
systems, eliminating the need for vSphere servers to zero out large
numbers of storage system blocks. This reduces server workloads and
speeds up virtual machine provisioning.
Page 30 of 32
www.fujitsu.com
Conclusion
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 79/81
5/9/2019 Full text of "Virtualization at Fujitsu"
at the virtual level. Virtualization brings the same risk created by open
systems. Open systems flexibility enabled an explosion in server
deployments. The same could occur with virtual server instances,
especially if strict policies are not put in place to avoid virtual server
sprawl.
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 80/81
5/9/2019 Full text of "Virtualization at Fujitsu"
Page 31 of 32
www.fujitsu.com
Contact © Copyright 201 1 Fujitsu limited. Fujitsu, the Fujitsu logo are trademarks or registered tra
demarks of
FUJITSU LIMITED Fujitsu Limited in Japan and other countries. Other company, product and service name
s may be
201 1-03-01 WW-EN and delivery subject to availability. Any liability that the data and illustrations
are complete, actual or
correct is excluded. Designations may be trademarks and/or copyrights of the respective manufacturer,
the use of which by third parties for their own purposes may infringe the rights of such owner.
Page 32 of 32 www.fujitsu.com
https://archive.org/stream/WpVirtualization/wp-virtualization_djvu.txt 81/81