HA Proxmox

w
o
r
k
s
h
o
p
2
1
.
0
5
.
2
0
1
4

/

1
3
.
4
0
h

/

C
l
a
s
s
r
o
o
m
S
0
7
CENTRE INTEGRAT PBLIC
DE FORMACI PROFESSIONAL
Departamento de
Informtica y
Comunicaciones
CIPFP AUSIS MARCH
Bare-Metal
Hypervisors and
High Availability
Systems
J o s R a m n R u i z
I
n
d
e
x
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
W
o
r
k
s
h
o
p
g
o
a
l
s
To know how the production
systems (really) work
W
o
r
k
s
h
o
p
g
o
a
l
s
To know and implement the
production virtualization: type I (or
bare-metal)
W
o
r
k
s
h
o
p
g
o
a
l
s
bare-metal)
To know a good (and free)
virtualization platform: Proxmox
W
o
r
k
s
h
o
p
g
o
a
l
s
bare-metal)
To know a good (and free)
virtualization platform: Proxmox
To test this platformsetting up an
approach to a production
environment
W
o
r
k
s
h
o
p
g
o
a
l
s
Why?
W
o
r
k
s
h
o
p
g
o
a
l
s
Why?
In my opinion most of us have
never worked with this kind of
systems
W
o
r
k
s
h
o
p
g
o
a
l
s
Why?
systems
It is important to know how they
work in order to provide a valid
systems view to our pupils
W
o
r
k
s
h
o
p
g
o
a
l
s
Why?
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-of-
year project shared between
different subjects
Type I (bare-metal) hypervisors
T
y
p
e
I

(
b
a
r
e
-
m
e
t
a
l
)

h
y
p
e
r
v
i
s
o
r
s
Type I hypervisors structure
HARDWARE
HYPERVISOR (really OS+hypervisor)
OS 1 OS 2 OS N
T
y
p
e
I

(
b
a
r
e
-
m
e
t
a
l
)

h
y
p
e
r
v
i
s
o
r
s
Advantages
Performance
Behaviour (less points of failure)
Production structures allowed
Weak points
Non-obvious configuration
Dedicated server (of course)
T
y
p
e
I

(
b
a
r
e
-
m
e
t
a
l
)

h
y
p
e
r
v
i
s
o
r
s
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
Proxmox
P
r
o
x
m
o
x
OS:
Debian
Virtualization platform:
KVM+Containers
Graphical remote access:
Java required
P
r
o
x
m
o
x
.

I
n
s
t
a
l
l
a
t
i
o
n
Downloaded fromwww.proxmox.org
I
n
s
t
a
l
l
a
t
i
o
n
.

K
e
y

s
c
r
e
e
n
s
e.g. ausiasHA
I
n
s
t
a
l
l
a
t
i
o
n
.

K
e
y

s
c
r
e
e
n
s
A
f
t
e
r
I
n
s
t
a
l
l
a
t
i
o
n
.

W
e
b

A
c
c
e
s
s
N
o
d
e
1
Our first VM
O
u
r
F
i
r
s
t
V
M
Structure
VM1 VM2 VMn
O
u
r
f
i
r
s
t
V
M
.

U
p
l
o
a
d
a
n
I
S
O
O
u
r
f
i
r
s
t
V
M
.

S
e
t
t
i
n
g
s
O
u
r
f
i
r
s
t
V
M
.

S
e
t
t
i
n
g
s
O
u
r
f
i
r
s
t
V
M
.

S
e
t
t
i
n
g
s
Bare-metal Hypervisors & High Availability Systems 28 O
u
r
f
i
r
s
t
V
M
.

S
e
t
t
i
n
g
s
O
u
r
f
i
r
s
t
V
M
.

S
e
t
t
i
n
g
s
O
u
r
f
i
r
s
t
V
M
O
u
r
f
i
r
s
t
V
M
.

C
o
n
s
o
l
e
Our first CT
O
u
r
f
i
r
s
t
C
T
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
O
u
r
f
i
r
s
t
C
T
O
u
r
f
i
r
s
t
C
T
O
u
r
f
i
r
s
t
V
M
.

D
o
w
n
l
o
a
d
O
u
r
F
r
i
s
t
C
T
.

S
e
t
t
i
n
g
s
O
u
r
F
r
i
s
t
C
T
.

S
e
t
t
i
n
g
s
O
u
r
F
r
i
s
t
C
T
.

S
e
t
t
i
n
g
s
O
u
r
F
r
i
s
t
C
T
.

S
e
t
t
i
n
g
s
O
u
r
F
r
i
s
t
C
T
S
t
a
t
i
s
t
i
c
s
O
u
r
f
i
r
s
t
C
T
.

W
o
r
k
i
n
g
Our first cluster
L
e
t
s
c
r
e
a
t
e
a

c
l
u
s
t
e
r
Update packages
In each node:
aptitude update && aptitude full-upgrade
Create a cluster
Master node: pvecm create NameCluster
Node2: pvecm add IPMaster
Node3: pvecm add IPMaster
O
u
r
f
i
r
s
t
c
l
u
s
t
e
r
Structure
O
u
r
f
i
r
s
t
c
l
u
s
t
e
r
C
T

M
i
g
r
a
t
i
o
n
C
T

M
i
g
r
a
t
i
o
n
p
r
o
c
e
s
s
C
T

M
i
g
r
a
t
i
o
n
Hot migration: it keeps working
C
T

M
i
g
r
a
t
i
o
n
This is not HA
Too much meatware
HA automates the process
Our first HA cluster
O
u
r
f
i
r
s
t
H
A

c
l
u
s
t
e
r
Structure
HA cluster
Network Shared storage
Management device
O
u
r
f
i
r
s
t
H
A

c
l
u
s
t
e
r
Structure
HA cluster
Network Shared storage
Management device
There are several critical points
I
m
p
l
e
m
e
n
t
i
n
g
H
A
Before starting
Remove any previous VM
Add the NAS to the cluster
A
d
d
i
n
g
t
h
e
N
A
S
A
d
d
i
n
g
t
h
e
N
A
S
F
e
n
c
i
n
g
Fencing?
F
e
n
c
i
n
g
Fencing
F
e
n
c
i
n
g
If a node does not respond
after a given time-threshold
non-operational
Two types of fencing
Disabling a node itself,
Disallowing access to resources
such as shared disks
F
e
n
c
i
n
g
If a node does not respond
after a given time-threshold
non-operational
Two types of fencing
Disabling a node itself
Disallowing access to resources
such as shared disks
STONITH
Resource Fencing
F
e
n
c
i
n
g
In every node:
nano /etc/default/redhat-cluster-pve
Uncomment the line
FENCE_JOIN="yes"
Join the fencing domain
fence_tool join
F
e
n
c
i
n
g
.

O
n
l
y
i
n

t
h
e
M
a
s
t
e
r
cp /etc/pve/cluster.conf /etc/pve/cluster.conf.new
nano /etc/pve/cluster.conf.new
Increase the version number
<cluster config_version="8" name="h1">
Validate the configuration
ccs_config_validate -v -f /etc/pve/cluster.conf.new
F
e
n
c
i
n
g
.

A
c
t
i
v
a
t
e
H
A

m
a
n
a
g
e
d
C
T
H
A

m
a
n
a
g
e
d
C
T
H
A

m
a
n
a
g
e
d
C
T
H
A

m
a
n
a
g
e
d
C
T
H
A

m
a
n
a
g
e
d
C
T
In each node:
/etc/init.d/rgmanager start
H
A

m
a
n
a
g
e
d
C
T
Fencing devices
Managed switches
PS switches
Manual fencing
Scripting+pseudo manual fencing
H
A

m
a
n
a
g
e
d
C
T
Fencing devices
Managed switches
PS switches
Manual fencing
Scripting+pseudo manual fencing
/
e
t
c
/
p
v
e
/
c
l
u
s
t
e
r
.
c
o
n
f
.
n
e
w
<?xml version="1.0"?>
<cluster config_version="8" name="h1">
<cman keyfile="/var/lib/pve-cluster/corosync.authkey expected_votes="1"/>
<fencedevices>
<fencedevice name="human" agent="fence_manual"/>
</fencedevices>
<clusternodes>
<clusternode name=node1" nodeid="1" votes="1">
<fence>
<method name="single">
<device name="human" nodename=node1"/>
</method>
</fence>
</clusternode>
<clusternode name=node2" nodeid="2" votes="1">
<fence>
</method>
</fence>
</clusternode>
/
e
t
c
/
p
v
e
/
c
l
u
s
t
e
r
.
c
o
n
f
.
n
e
w
<clusternode name=node3" nodeid=3" votes="1">
<fence>
</method>
</fence>
</clusternode>
</clusternodes>
<rm>
<pvevm autostart="1" vmid="100"/>
</rm>
</cluster>
D
o
e
s
i
t
w
o
r
k
?
Start VM 100 in node1
Poweroff node 1 (or disable
the network)
Go to node2 or node3
Manual fencing:
fence_ack_manual node1
Confirmwith: absolutely
D
o
e
s
i
t
w
o
r
k
?
Thanks for your attendance
Questions?
Slides available on:
http://bit.ly/JRRuiz-HA

HA Proxmox

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HA Proxmox

Uploaded by

Copyright:

Available Formats

w

You might also like