Here, in the XenServer R & D group I'm working on a new open-source based xen, the 'virtualization architecture (code -named "Windsor"). The aim is to exploit the impressive capabilities of the Xen hypervisor to a new generation platform for IaaS cloud computing.
Why I like xen?
Xen was originally created at the University of the draft xenoserver Cambridge Computer Lab, whose goal was:
to build a public infrastructure for wide area distributed computing
This was before. the days before "cloud" and "IaaS" became popular. The purpose was to be xen:
a high-performance hypervisor ... [which] form the core of each Xenoserver node, providing resource management, accounting and the audit that we need [
course xen was a great success making exactly what in the public cloud.
from the architectural point of view, xen is great because it is a job and does it well. Xen is a "Type 1" hypervisor or "bare metal" that is underneath all running virtual machines to isolate them from each other and control who comes to talk about the physical hardware. Xen is not an OS kernel; it was not a multitude of interfaces, VFS layers, blocks caches, etc. It focuses on being a great hypervisor
Windsor :. Exploit the capabilities of xen
The architecture Windsor operate the xen capabilities:
- increase the security of the host Service on the host will be divided into separate virtual machines and deprivileged to decrease the size of the Trusted Computing base (TCB). Xen will continue to provide rock solid isolation between virtual machines, limiting the impact of any compromise. In the Xen community this technique is known as "domain 0 disintegration"
- increase scalability host :. Just as modern applications can be designed to scale-automatically through a public cloud, Windsor Home services will be able to step across multiple virtual machines in the Windsor platform . for example, if the host storage service overloads, the host start a second service and load balancer transparent
- increase availability :. Since even the most robust systems still sometimes encounter bugs and fail, the services will be designed to Windsor to recover quickly. for example, device drivers are all handled as separate virtual machines (known as "areas of the pilot"). Each VM has access to a single piece of equipment. If a device driver crashes , xen contain the accident and the VM is restarted. Basically, all guest virtual machines remain running and only notice a small interruption of their network or storage I / O
- a better quality of service (QoS) :. The key to ensuring a good quality of service in the cloud is to prevent virtual machines from one tenant to interfere with the virtual machines to another tenant, for example by exhausting the number of available I / O buffers in shared storage stack. In Windsor, xen will isolate network stacks and storage ( "pilot areas") of each tenant so that requests I / O are kept apart until they reach the physical hardware.
The best is yet to come ...
Expect to see the technical details (including links to the code) in some future blog posts!
0 Komentar