.
ctys-network-filesystem-design - Receipt for the setup of a network files system design
In distributed environments with a worker and storage architecture the common location independent
view of the processing nodes to the task data is the main design issue.
This could be easily provided by defining a directory structure stored on a network filesystem like NFS or AFS
with identical mount points on each machine.
This has to be provided for the hypervisor access points to the stored VMs as well as for
the contained filesystem structure of the GuestOSs.
The following figure depicts the views for Xen and QEMU based VMs.
Network filesystem design |
---|
The main aspect is here the provided flexibility for the almost location independent roaming of generic VMs.
Therefore two intermediate layers are introduced, first the interface of the hypervisors to stored VMs,
second the execution and low-level access of the VMs to and from the PMs.
Network filesystem design - access locations |
---|
The result is a common view to the filesystem directory tree for each VM and it's contained GuestOS.
Network filesystem design - directory tree |
---|
The required access functionality for the addressing of specific stored VMs is provided by the UnifiedSessionsManager. This is e.g. required for some hypervisors and which reuqire a storage addressing slightly different from common filesystem names. The eventualy required conversion functions due to proprietary addressing of the Vendors is provided by the UnifiedSessionsManager.
ctys-distribute(1) , ctys-plugins(1)
Written and maintained by Arno-Can Uestuensoez:
Maintenance: | <<acue_sf1 (a) users sourceforge net>> |
Homepage: | <https://arnocan.wordpress.com> |
Sourceforge.net: | <http://sourceforge.net/projects/ctys> |
Project moved from Berlios.de to OSDN.net: | <https://osdn.net/projects/ctys> |
Commercial: | <https://arnocan.wordpress.com> |
Copyright (C) 2008, 2009, 2010, 2011 Ingenieurbuero Arno-Can Uestuensoez
For BASE package following licenses apply,
This document is part of the DOC package,
For additional information refer to enclosed Releasenotes and License files.