Changes between Version 44 and Version 45 of WikiStart
- Timestamp:
- 10/04/11 18:31:02 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v44 v45 1 = Welcome to R ESILIREProject =1 = Welcome to Resilire Project = 2 2 3 High availability (HA) refers to a system and associated service implementation that is continuously operational for a long period of time. With respect to the clients, an ideal system never stops working, which also means the system will always respond to the clients’ requests. Whole-system replication is a conventional way to increase the system availability: once the primary machine fails, the running applications will be taken over by the backup machine. However, there are several limitations that make this method unattractive for deployment: it needs specialized hardware and software, which are usually expensive. The final system also requires complex customized configurations, which makes it hard to manage efficiently.3 High availability refers to a system and associated service implementation that is continuously operational for a long period of time. Whole-system replication is a conventional way to increase system availability -- once a primary machine fails, the running applications are migrated and resumed on backup machine(s). However, there are several limitations that make this method unattractive for deployment: it needs specialized hardware and software, which are usually expensive. Additionally, such a system may also require complex customized configurations, which are difficult to manage and maintain. 4 4 5 As virtualization becomes more and more prevalent, we can overcome these limitations in the virtual world. All the applications are running in the VM, so now it’s possible to implement the whole-system replication in an easy and efficient way — by saving the copy of the whole VM running on the system. As VMs are totally hardware-independent, the cost is much lower compared to the hardware expenses in traditional HA solutions. Besides, virtualization technology can facilitate the management of multiple VMs on a single physical machine. With virtual machine monitors (VMM), the service applications are separated from physical machines, thus provides increased flexibility and improved performance. 5 These limitations are efficiently overcome by virtualization: all applications now run on a virtual machine (VM). Thus, whole-system replication can easily and efficiently implemented -- a copy of the whole VM is continuously checkpointed and saved on a backup machine. As VMs are totally hardware-independent, the cost is much lower compared to the hardware expenses in traditional HA solutions. Besides, virtualization technology can facilitate the management of multiple VMs on a single physical machine. With virtual machine monitors (VMM), the service applications are separated from physical machines, providing increased flexibility and 6 improved performance. 6 7 7 RESILIRE consists of several finished and ongoing projects which aim on addressing the availability and reliability challenges in virtualized system. RESILIRE focus on providing transparent and comprehensive high availability (HA) to solo and multiple virtual machines (VM) running on [http://xen.org/ The Xen Hypervisor]. Most projects under RESILIRE are based on Xen 3.4 VMM but they can easily be ported to more recent releases of Xen. RESILIRE does not require any modification to the application and operating system (guest OS) inside the VMs, therefore although RESILIRE is developed based on Xen, the ideas in RESILIRE also benefit other VMMs with full virtualization. 8 The Resilire project is developing techniques and mechanisms for high availability through VM migration, from solo VMs to multiple VMs running on different physical hosts, interconnected by a virtual network (i.e., virtual distributed environments or VDEs). The effort is based on Xen 3.4 VMM, but is portable to more recent releases of Xen and other VMMs with full virtualization. The project's implementations do not require modifications to applications or guest OSes inside the VMs. 8 9 9 ''[wiki:teammember R ESILIRETeam]''10 ''[wiki:teammember Resilire Team]'' 10 11 11 == R ESILIREIn Progress ==12 == Resilire In Progress == 12 13 13 * [wiki:VDEchp VDEchp] -- Global Consistent Checkpoint for Virtual Distributed Environment14 * [wiki:VDEchp VDEchp] -- Globally Consistent Checkpoint for Virtual Distributed Environments 14 15 * [wiki:FGBI FGBI] -- Fine-Grained Block Identification 15 16 * [wiki:LLM LLM] -- Lightweight Live Migration