HYPER-V CLUSTERING

SOWMYA KRISHNAN

Who are we?

• Has been contributing and driving PRs / features in community

• Prior to that, through Citrix

• Committed to community

Hyper-V support evolvement over releases

CloudStack 4.3

Both Hyper-V Server(non GUI) and Windows Server

• Initial support

• SMB

• Basic support for VM, storage and networking

Hyper-V support evolvement over releases

CloudStack 4.4

• VPC

• Storage Migration

• Zone Wide Primary Storage

• Multiple Nics

Hyper-V Clustering

• HA using Failover Clusters

• Cluster Shared Volume

• iSCSI

Failover Cluster

- Independent nodes of a cluster working together to increase

availability of services

- In conjunction with Cluster Shared Volume

- Multiple nodes read from and write to the same Cluster Shared

Volume

- Multiple nodes can access files from same volume at the same time

Cluster Shared Volume

• Failover Cluster

• Volumes in CSV can be accessed by all nodes in the Failover Cluster

• All nodes in cluster have files in the same volume

Quorum Configuration

• To avoid single point of failure

• Number of failures that are allowed in a cluster

• Different Quorum choices based on capacity

Adding Hyper-V Failover Cluster to

CloudStack

• Failover Cluster created by Admin and added to CloudStack

• 1-1 mapping between Failover Cluster and CloudStack Cluster

• Hosts to be added to the Failover Cluster before adding to CloudStack

• Use PreSetup Option to add CSV

HA VMs have higher priority

Non HA VMs added to Cluster with priority: 0 (No Auto Start)

HIGH AVAILABILITY

Two node cluster

Priority is assigned to HA Virtual machines running on Hyper-V cluster

Possible priority values: High (3000), Medium (2000): The default setting, Low (1000) or No

Auto Start (0)

Node goes down

HA VMs get migrated to other Host

Live Migration from Event Viewer

HA VMs migrated to host13

2 0 1 7 - 0 5 - 1 1 1 4 : 4 1 : 4 7 , 6 7 8 I N F O [ c . c . v . V i r t u a l M a c h i n e M a n a g e r I m p l ] ( D i r e c t A g e n t C r o n J o b - 3 0 3 : c t x - 9 9 4 4 0 f a 4 )

( l o g i d : 7 4 9 b 2 5 6 2 ) Detec ted out o f band VM mig ra t ion f rom host 2 to hos t 1

2 0 1 7 - 0 5 - 1 1 1 4 : 4 1 : 4 7 , 6 9 2 D E B U G [ c . c . c . C a p a c i t y M a n a g e r I m p l ] ( D i r e c t A g e n t C r o n J o b - 3 0 3 : c t x - 9 9 4 4 0 f a 4 ) ( l o g i d : 7 4 9 b 2 5 6 2 ) V M s t a t e t r a n s i t t e d f r o m : R u n n i n g t o R u n n i n g w i t h e v e n t : F o l l o w A g e n t P o w e r O n R e p o r t v m ' s

o r i g i n a l h o s t i d : 1 new host id : 1 host id be fo re s ta te t rans i t i on : 2

2 0 1 7 - 0 5 - 1 1 1 4 : 4 1 : 4 7 , 6 9 2 D E B U G [ c . c . v . V i r t u a l M a c h i n e P o w e r S t a t e S y n c I m p l ] ( D i r e c t A g e n t C r o n J o b - 3 0 3 : c t x -9 9 4 4 0 f a 4 ) ( l o g i d : 7 4 9 b 2 5 6 2 ) V M s t a t e r e p o r t . h o s t : 1 , v m i d : 6 , p o w e r s t a t e : P o w e r O n

2 0 1 7 - 0 5 - 1 1 1 4 : 4 1 : 4 7 , 7 0 9 D E B U G [ c . c . v . V i r t u a l M a c h i n e P o w e r S t a t e S y n c I m p l ] ( D i r e c t A g e n t C r o n J o b - 3 0 3 : c t x -9 9 4 4 0 f a 4 ) ( l o g i d : 7 4 9 b 2 5 6 2 ) V M s t a t e r e p o r t i s u p d a t e d . h o s t : 1 , v m i d : 6 , p o w e r s t a t e : P o w e r O n

2 0 1 7 - 0 5 - 1 1 1 4 : 4 1 : 4 7 , 7 1 3 I N F O [ c . c . v . V i r t u a l M a c h i n e M a n a g e r I m p l ] ( D i r e c t A g e n t C r o n J o b - 3 0 3 : c t x - 9 9 4 4 0 f a 4 )

( l o g i d : 7 4 9 b 2 5 6 2 ) Detec ted out o f band VM mig ra t ion f rom host 2 to host 12 0 1 7 - 0 5 - 1 1 1 4 : 4 1 : 4 7 , 7 2 9 D E B U G [ c . c . c . C a p a c i t y M a n a g e r I m p l ] ( D i r e c t A g e n t C r o n J o b - 3 0 3 : c t x - 9 9 4 4 0 f a 4 ) ( l o g i d : 7 4 9 b 2 5 6 2 ) V M s t a t e t r a n s i t t e d f r o m : R u n n i n g t o R u n n i n g w i t h e v e n t : F o l l o w A g e n t P o w e r O n R e p o r t v m ' s

o r i g i n a l h o s t i d : 1 new host id : 1 host id be fo re s ta te t rans i t i on : 2

2 0 1 7 - 0 5 - 1 1 1 4 : 4 1 : 4 8 , 5 1 6 I N F O [ o . a . h . i . c . D e f a u l t H t t p C l i e n t ] ( D i r e c t A g e n t - 3 0 6 : c t x - 9 d d 9 c e 8 b ) ( l o g i d : a 5 2 a c 5 0 0 ) I / O e x c e p t i o n ( j a v a . n e t . N o R o u t e T o H o s t E x c e p t i o n ) c a u g h t w h e n c o n n e c t i n g t o { s } -

> h t t p s : / / 1 0 . 1 0 2 . 1 9 2 . 1 7 : 8 2 5 0 : No route to hos t

■ Admin needs to first add Host to the Failover Cluster

■ Use the ‘presetup’ option while adding CSV

■ When user creates HA VM it is added to Failover Cluster

■ When user creates non-HA VM it is added to Failover Cluster with priority as 0

■ VMs migrated (HA-ed) to other hosts will be automatically synced by VM Sync

■ Any other VM and Volume operations work normally

Thank You