DESKTOP VIRTUALIZATION WITH RHEV

Bart Janssens

37 years old

Live in Antwerp

Work at Kangaroot

→ Linux & Open Source Solutions

WHO AM I

What and why

Introducing RHEV

Desktop Virtualization

User and Permission Management

AGENDA

WHAT AND WHY

Desktop Virtualization using Red Hat Enterprise

Virtualization as a platform for on-demand

provisioning of desktops

WHAT

Traditional desktop is losing importance

On demand services & Platform independent

Flexible workplace

Central management

Easy upgrade path

WHY

workspaces that have a large amount of typical office desktop users:

office

mail

web-based apps

schools

migrating off Windows XP

FOR WHO

What solutions do we have available for desktop virtualization?

VMware Horizon

Citrix XenDesktop

linux

oVirt

Red Hat Enterprise Virtualization

OPTIONS

Open Source

No Vendor lock-in

Easy expansion

Red Hat Support

Easy to use interface

User Portal

Powerful permission managment

SPICE

Cost

WHY RHEV?

INTRODUCING RHEV

Red Hat Enterprise Virtualization consists of:

One RHEV manager machine

One or more Virtualization hosts

RHEV Hypervisor image

RHEL + rhev

RHEV

A CLOSER LOOK

Heart of RHEV

centralized management platform

registers & controls the state and events

view, manage and provision resources

graphical interface

cli shell

THE RHEV MANAGER

GRAPHICAL INTERFACE

A Data Center contains

Clusters contain

Hosts

Logical Networks

Storage Pools

LOGICAL RESOURCES

DESKTOP VIRTUALIZATION

CREATE A VM

SPICE

Simple Protocol for Independent Computing Environments allows:

video at more than 30 frames per second

bidirectional audio (for softphones/IP phones)

bidirectional video (for video telephony/video conferencing)

connection to multiple monitors with a single virtual machine

USB redirection from the client's USB port into the virtual machine

Templatescreate read-only copy of the vms disk

this base disk image is shared by the template and every vm created from it

VM TEMPLATES AND POOLS

Poolscontain multiple virtual machines based on a common template

provide generic virtual machines to end users on demand

set a number of prestarted vms

USER AND PERMISSION MANAGEMENT

Let's put those vms to use

there is only one internal user: admin

other users and groups are added from directory services:

Active Directory

Identity Management (IdM)

Red Hat Directory Server 9 (RHDS 9)

OpenLDAP

ADD USERS

USER MANAGEMENT

RHEV applies authorization controls based on the combination of the three components:

The user performing the action

The type of action being performed

The object on which the action is being performed

PERMISSIONS

Permissions are inherited by objects

lower on the hierarchy

PERMISSION HIERARCHY

Permissions can be grouped in

roles

USER PORTAL

POWER USER PORTAL

THANK YOU