Wiki code for Cluster Agent: OpenSolaris xVM

Hide Line numbers
1: == Overview
2: 
3: The aim of this project is to provide a failover agent for OpenSolaris x86 Virtual Manager (xVM) and Logical Domains (LDoms) guest domains as part of the open-source code base for Solaris Cluster, namely Open High Availability Cluster (OHAC). Within this project the term xVM refers to the [[ OpenSolaris xVM project>>Community Group xen.WebHome]] and [[ LDoms>>http://www.sun.com/servers/coolthreads/ldoms/]]. It is intended that an OHAC failover agent for xVM guest domains will perform the following:
4: 
5: * Manage the start/stop and restart of xVM guest domains within an OHAC environment.
6: * Failover a xVM guest domain between OHAC nodes.
7: * Allow for strong positive and negative affinities between xVM guest domains across OHAC nodes.
8: * Allow for different failover techniques between OHAC nodes, i.e. Stop/Failover/Start or Live Migration.
9: 
10: == Project Goals
11: 
12: * Provide high availability for xVM guest domains in the event of an OHAC node failure. For example, if a node fails, the OHAC failover agent for xVM guest domains will relocate the guest domain onto another OHAC node. Note that OHAC supports upto 16 nodes, campus clusters (upto 40km separation), metro clusters (upto 400km separation) and Geographic Edition for Disaster Recovery (unlimited distance), Dual partition software upgrade / Live upgrade, to list just a few features of OHAC.
13: * Provide the ability to failover a xVM guest domain across OHAC nodes using live migration. In this scenario, both nodes are available and it is preferred to live migrate a xVM guest domain, using a cluster file system, between OHAC nodes.
14: * Provide the ability to favour one xVM guest domain over another. For example, assuming a 2-node cluster, under normal operations both nodes could be running several xVM guest domains. Some guest domains maybe more important than others and in the event of a node failure it maybe desirable to favour one guest domain over other guest domains. In this regard, before the favoured guest domain is started the less favoured guest domain would be shutdown thereby freeing system resources for the favoured guest domain.
15: 
16: == Status
17: 
18: * 26th June 2009
19: HA-xVM support for LDoms [[ webrev >>http://cr.opensolaris.org/~hnamachi/ha-ldom]]and [[ HA-LDoms design document>>attach:Project ha-xvm.WebHome@ha-ldoms-design-docv2.pdf]] following the open CLARC commitment review.
20: Here is a revised edition of man page for [[ccradm >>attach:Project ha-xvm.WebHome@ccradm.pdf]] to aid in the code review
21: * 5th Dec 2008
22: [[Addendum>>http://www.opensolaris.org/jive/thread.jspa?threadID=84832&tstart=0]] to HA-xVM to include [[ LDoms>>http://www.sun.com/servers/coolthreads/ldoms/]] guest domains.
23: * 2nd Dec 2008
24: HA-xVM [[ demo>>http://mediacast.sun.com/users/neilg/media/ohac/details]]. Hit the download button from that link to stream the demo.
25: The demo is based on snv_86 and SCX 2/08 simply to reflect the [[ cheat sheet>>Project ha-xvm.]]. The purpose of the demo was to show the following,
26: ** Show that an OHAC resource group managing an xVM guest domain via an OHAC resource can switch an xVM guest domain from one node to another using live migration. What’s not shown is that the OHAC interconnects are used for the live migration.
27: ** Show that an OHAC managed xVM guest domain can survive a node crash.
28: In particular within the demo, RG1 manages xVM domain domu1. RG1 is then switched from node podio2 to node podio1 and domu1 is subsequently live migrated between the two nodes. While RG1/domu1 is online on podio1 that node podio1 is crashed via uadmin 2 1. OHAC automatically detects that failure and restarts domu1 on podio2.
29: * 19th Nov 2008
30: HA-xVM [[ webrev >>http://cr.opensolaris.org/~neilg/ohacds-xvm-webrev3]]and [[ requirements specification>>attach:Project ha-xvm.WebHome@ha-xvm-req-spec-v1.2.pdf]] following the open CLARC inception review.
31: * 19th Mar 2008
32: HA-xVM [[ webrev>>http://cr.opensolaris.org/~neilg/ohacds-xvm-webrev2]], [[ agent>>attach:Project ha-xvm.WebHome@SUNWscxvm.tar]] and [[ cheat sheet>>Project ha-xvm.]].
33: * 15th Feb 2008
34: OHAC agent for HA-xVM Guest Domains [[ webrev>>http://cr.opensolaris.org/~neilg/ohacds-xvm-webrev1/]].
35: * 26th Sept 2007
36: Waiting for Nevada b75 to appear in the Solaris Express Community DVD so that we can provide a documented proof of concept using OHAC with xVM.
37: * 23rd Jul 2007 (Initial proof of concept).
38: Here we installed Nevada b66 with OHAC, then BFU’d the latest xVM bits. This allowed us to boot both nodes running OHAC and xVM in Domain-0. We then created a cluster file system and an xVM guest domain (running Nevada b63) which was manually failed over between the two OHAC nodes, afterwards a live migration was performed. A xVM guest domain was also manually failed over using a ZFS as a Virtual Block Device.
39: 
40: == Documentation
41: 
42: * [[Project Proposal>>http://www.opensolaris.org/jive/thread.jspa?threadID=36406&tstart=15]]
43: * [[Requirements Specification>>attach:Project ha-xvm.WebHome@ha-xvm-req-spec-v1.2.pdf]] [x86-64]
44: * [[Requirements Specification>>attach:Project ha-xvm.WebHome@req-spec-HA-Ldoms-4.0.pdf]] [LDoms]
45: * [[Design Document>>attach:Project ha-xvm.WebHome@design.pdf]] [x86-64]
46: * [[Design Document>>attach:Project ha-xvm.WebHome@ha-ldoms-design-doc.pdf]] [LDoms]
47: 
48: == Getting involved
49: 
50: * Talk with people or search the archives in the [[ha-clusters:discuss >>http://opensolaris.org/jive/forum.jspa?forumID=195]] discussion group
OpenSolaris

Top Menu

Wiki code for Cluster Agent: OpenSolaris xVM

Search

Collectives

Community Group

Project

User Group

Subsites

Project ha-xvm Pages
