HA Proxmox

21.05.2014 / 13.40h / Classroom S07

workshop

Bare-Metal Hypervisors and High Availability Systems CIPFP AUSIÀS MARCH

J o s é

R a m ó n

R u i z

CENTRE INTEGRAT PÚBLIC DE FORMACIÓ PROFESSIONAL

Departamento de Informática y Comunicaciones

Index

• • • • • •

Workshop goals Type I (bare-metal) hypervisors An example: Proxmox Beyond virtualization Maintenance tasks: MV migration Setting up a HA environment

Bare-metal Hypervisors & High Availability Systems

2

Workshop goals

• To know how the production systems (really) work


3

Workshop goals

• To know how the production systems (really) work • To know and implement the production virtualization: type I (or bare-metal)


4

Workshop goals

• To know how the production systems (really) work • To know and implement the production virtualization: type I (or bare-metal) • To know a good (and free) virtualization platform: Proxmox


5

Workshop goals

• To know how the production systems (really) work • To know and implement the production virtualization: type I (or bare-metal) • To know a good (and free) virtualization platform: Proxmox • To test this platform setting up an approach to a production environment Bare-metal Hypervisors & High Availability Systems

6

Workshop goals

• Why?


7

• Why?

Workshop goals

• In my opinion most of us have never worked with this kind of systems


8

Workshop goals

• Why? • In my opinion most of us have never worked with this kind of systems • It is important to know how they work in order to provide a valid systems view to our pupils


9

Workshop goals

• Why? • In my opinion most of us have never worked with this kind of systems • It is important to know how they work in order to provide a valid systems view to our pupils • It would be an interesting end-ofyear project shared between different subjects Bare-metal Hypervisors & High Availability Systems

10

Type I (bare-metal) hypervisors


11

• Type I hypervisors structure


OS 1

OS 2

…

OS N

HYPERVISOR (really OS+hypervisor)

HARDWARE


12


• Advantages – Performance – Behaviour (less points of failure) – Production structures allowed

• Weak points – Non-obvious configuration – Dedicated server (of course)


13

• Main examples


– VMWare ESXi • Difficult to configure • Expensive licenses

– Proxmox • Good balance performance/effort • Free

– Microsoft Hyper-V • Poor performance • Easy configuration

– Parallels Server Bare Metal – Xen Server Bare-metal Hypervisors & High Availability Systems

14

Proxmox


15

• OS: – Debian

• Virtualization platform: – KVM+Containers

Proxmox

• Graphical remote access: – Java required


16

Proxmox. Installation

• Downloaded from www.proxmox.org


17

Installation. Key screens

e.g. ausiasHA


18

Installation. Key screens


19

After Installation. Web Access


20

Node1


21

Our first VM


22

• Structure

Our First VM

VM1

VM2

…

VMn


23

Our first VM. Upload an ISO


24

Our first VM. Settings


25



26



27



28



29

Our first VM


30

Our first VM. Console


31

Our first CT


32

Our first CT

• What is a ‘CT’? • OpenVZ Container – Instead of trying to run an entire guest OS, container virtualization isolates the guests, – It doesn't try to virtualize the hardware. – Recommended for running GNU/Linux – Fastest approach


33

Our first CT


34

Our first CT


35

Our first VM. Download


36

Our Frist CT. Settings


37



38



39



40

Our Frist CT


41

Statistics


42

Our first CT. Working


43

Our first cluster


44

• Update packages

Let’s create a cluster

– In each node: aptitude update && aptitude full-upgrade

• Create a cluster – Master node: pvecm create – Node2: pvecm add IPMaster

– Node3:

NameCluster

pvecm add IPMaster


45

Our first cluster

• Structure


46

Our first cluster


47

CT Migration


48

CT Migration process


49

CT Migration

Hot migration: it keeps working


50

CT Migration

• This is not HA • Too much meatware • HA automates the process


51

Our first HA cluster


52


• Structure

Management device

Network Shared storage

HA cluster Bare-metal Hypervisors & High Availability Systems

53


• Structure

Management device

There are several critical points Network Shared storage

HA cluster Bare-metal Hypervisors & High Availability Systems

54

Implementing HA

• Before starting • Remove any previous VM • Add the NAS to the cluster


55

Adding the NAS


56

Adding the NAS


57

Fencing

• Fencing?


58

Fencing

• Fencing


59

• If a node does not respond after a given time-threshold  non-operational

Fencing

• Two types of fencing – Disabling a node itself, – Disallowing access to resources such as shared disks


60

• If a node does not respond after a given time-threshold  non-operational

Fencing

• Two types of fencing

STONITH

– Disabling a node itself – Disallowing access to resources such as shared disks Resource Fencing


61

• In every node: nano /etc/default/redhat-cluster-pve

– Uncomment the line FENCE_JOIN="yes"

Fencing

– Join the fencing domain fence_tool join


62

Fencing. Only in the Master

cp /etc/pve/cluster.conf /etc/pve/cluster.conf.new

nano /etc/pve/cluster.conf.new

• Increase the version number

• Validate the configuration ccs_config_validate -v -f /etc/pve/cluster.conf.new


63

Fencing. Activate


64

HA managed CT


65

HA managed CT


66

HA managed CT


67

HA managed CT


68

• In each node:

HA managed CT

/etc/init.d/rgmanager start


69

HA managed CT

• Fencing devices – Managed switches – PS switches – Manual fencing – Scripting+pseudo manual fencing


70

HA managed CT

• Fencing devices – Managed switches – PS switches – Manual fencing – Scripting+pseudo manual fencing


71

/etc/pve/cluster.conf.new


72

/etc/pve/cluster.conf.new


73

Does it work?

• Start VM 100 in node1 • Poweroff node 1 (or disable the network) • Go to node2 or node3 • Manual fencing: fence_ack_manual node1

• Confirm with: absolutely


74

Does it work?


75

Thanks for your attendance Questions?

Slides available on: http://bit.ly/JRRuiz-HA


76

HA Proxmox

Recommend Documents