1

Solutii Virtualizare

Virtualisation Solutions

• Short history

• Concepts and architecture

• Why?

• Bright Cluster Manager OpenStack and containers

• Demo - OpenStack install / manage

• SmartOS / Triton

• Demo Triton VM deploy / manage

• Questions / Answers

2

Agenda

Short history

• 1968-1972 IBM development of CP-67 mainframe, first commercial mainframe to support virtualisation implemented as

CP/CMS . CP Stands for Control Program, CMS stands for Console Monitor System.

• 1987 Insignia Solutions demonstrated a software emulator called SoftPC. SoftPC allowed users to run Dos applications on their Unix

workstations

• 1997, Apple created a

program called Virtual PC

• 1998, a company called

VMWare was established

• 2008 Citrix launch XenServer.

3

• Hypervisor or virtual machine monitor

(VMM) is computer software, firmware or hardware that creates and runs

virtual machines

The term hypervisor is a variant of supervisor, a traditional term for the kernel of an operating system: the hypervisor is the

supervisor of the supervisor.The term dates to circa 1970 , in the earlier CP/CMS (1968)

system the term Control Program was used instead.

Hypervisor Types

• Type 1: native or bare metal

Native hypervisors are software systems that run directly

on the host's hardware to control the hardware

Examples of this implementation of virtual machine

architecture are Oracle VM , Microsoft Hyper-V, VMWare

ESXI , Xen.

• Type 2: hosted

Hosted hypervisors are designed to run within a

traditional operating system.

Example this implementation are Oracle VM VirtualBox

,VMWare Workstation, KVM, QEMU and Parallels.

The distinction between these two types is not necessarily clear. Linux’s Kernel-based Virtual

Machine (KVM) and FreeBSD's bhyve are kernel modules that effectively convert the host operating system to a type-1 hypervisor.

Concept and Architecture

Market share Public Cloud

• Amazon

• Azure

• Google

Market share Private Cloud

• VMware Cloud

• OpenStack

• XenCloud

• Hyper-V ( Azure on premise)

Place of implementation

• Public —> Public Cloud

• On premise -> Private Cloud

• Mixt

Source code / Licensing

• Open Source

• Proprietary

Concept and Architecture (continued)

Why?

• Resource optimisation

• Consolidation

• Uptime / Availability

• Scaling (scale out, scale up , scale down)

• Protect from hardware failure

• Migrate Workloads

• Use legacy applications after hardware EOL

• Agility (fast deployment)

Bright Cluster Manager OpenStack

• Bright Computing = Cluster Expert

• Virtualisation on “Cloud” use clusters as “bricks” for infrastructure

• Bright Computing after evaluations select OpenStack

Why?

• Open source

• Strong backing from many “big boys” : Intel, Mellanox, RedHat, IBM, HP, NASA, Huawei…

• Flexible

• State of the art

• Fast development

• Big community

• Bright Cluster Manager OpenStack extension is born

• Tuned and optimised OpenStack distribution

• Easy deployment - Installation Wizard

• Graphical User Interface - intuitive interface for all OpenStack functionality

• Comprehensive Monitoring and Health Checking

• Ceph / RADOS /GPFS integration

• Comprehensive documentation and support

• Unified Management

Bright Cluster Manager Provides for OpenStack:

Bright Cluster Manager OpenStack

9

• OpenStack installation can be quite challenging because

OpenStack is a very large collection of separate components.

• You need a great deal of know-how to achieve an optimal installation.

• Because requirements for hardware and software are not trivial, is difficult to learn from experiments.

• YMMV

Bright Cluster Manager OpenStack

Tuned and optimised OpenStack distribution

10

Bright Cluster Manager OpenStack

Complexity of OpenStack

11

• Because of high complexity, Bright

created trusted and easy recipes for OpenStack deployments

• OpenStack deployment can be made from CLI or GUI

• Wizard save configuration to file, for easy reinstall

• You have choice of express install or fine-tuned one

Bright Cluster Manager OpenStack

Easy Deployment - Installation Wizard

12

Bright Cluster Manager OpenStack

Easy Deployment - Installation Wizard

13

Bright Cluster Manager OpenStack

Graphical User Interface

14

Bright Cluster Manager OpenStack

Comprehensive Monitoring and Health Checking

15

Bright Cluster Manager OpenStack

Unified Management

• Integrated on Bright • Horizon Dashboard available

• OpenStack is fully managed

Demo - OpenStack

install / manage

SmartOS / SDC

PRO SYS offer an alternative to classic virtualisationsolutions

• Thought from the ground up for cloud and containers

• SmartOS as a hypervisor and Triton as a full

integrated managed stack

• FAST , real FAAAST!

• Architected around KISS principle (Keep It Simple ,

Stupid)

• No string attached, open source 100 %

• Used in production for more than 10 years..

• Stable and with lowest level of maintenance

SmartOS / SDC

18

SmartOS is a specialised Type 1 Hypervisor

It supports two types of virtualisation:

• OS Virtual Machines (Zones): A light-weight virtualisation solution offering a complete and secure userland environment on a single global kernel, offering true bare metal performance

• KVM Virtual Machines: A full virtualisation solution for running a variety of guest OS’s

SmartOS is a "live OS"and runs entirely from memory

• This architecture has a variety of advantages including increased security, no need for patching, fast upgrades and recovery.

Concepts and architecture

SmartOS / SDC

19

Virtualisation in SmartOS builds on top of the technologies inherited from OpenSolaris :

• ZFS for storage virtualisation

• Crossbow for network virtualisation

• Zones for virtualisation and containment

• DTrace for introspection

• SMF for service management

• RBAC/BSM for auditing and role based security

In SmartOS both OS (Zones) and KVM virtual machines are built on Zones technology.

• In the case of OS Zones, the guest virtual machine is provided with a complete userland environment on which to run applications directly.

• In the case of KVM virtualisation, the KVM qemu process will run within a stripped down Zone. This provides KVM guests with an additional layer of security and isolation not offered by other KVM platforms.

Concepts and architecture

ZFS

20

ZFS is a revolutionary file system and logical volume manager that fundamentally

changes the way file systems are administered, with features and benefits not found in any other file system available today.

• Storage Pools

• Data Integrity

• Scrubbing

• Snapshots

• Clones

• Sending & Receiving Snapshots

• Caching

• Block Level Deduplication

• Compression

• Cross-platform (Linux,*BSD,*solaris,Mac OS…even an Windows port is in the work….)

21

SmartOS / SDCWhy??

• Hypervisor read-only -> increased security , ideal for critical environments

• Only ZFS local storage -> • max. performance (minimal data-path)

• guaranteed integrity ( Merkle tree based checksum)• inline compression/deduplication

• high resiliency (multiple levels of redundancy)• multiple levels of read/write cache

• minimal tuned kernel • smallest attack surface

• high performance• specialised hypervisor

• support full virtualisation• support OS virtualisation

• support docker (native support)• rich capabilities of dynamic and real-time tracing and debug , based on Dtrace

• created from the beginning for DEVOPS• full set of open API

• VM’s are described in JSON format• simple , consistent and programmatic interface

Demo - SmartOS / Triton

VM deploy / manage

Questions/Answers