UnifiedSessionsManager

• 
  The UnifiedSessionsManager offers a vendorindependent integration platform for the application of arbitrary hypervisors, Operations Systems, and User-Interfaces.
  
  
  
  

UnifiedSessionsManager

• 
  The integrated database provides in combination with the automated scanners the 4-step integration and startup of arbitrary virtual and physical machines by a seamless User-Interface.
  
  
  
  Autonomous machines, GROUPs, or collections by standard shell scripts.
  
  

A consolidated workspace

• For example by: 'ctys demo/vm-desktop-01'
  
  
  
  Details see https://arnocan.wordpress.com - Menue:Screenshots

First Step:
Installation of the UnifiedSesionsManagers

• 
  
  The first step is the installation of the UnifiedSessionsManagers.
• 
  This could be processed alternatively either by usage of the provided tgz-archives, or by utilisation of the provided RPM packages.
• 
  In addition the installation could be performed solely by the usage of scp-based ctys-distribute.
• 
  The installation could be performed locally as well as remotely.

Second Step:
Configuration of the UnifiedSesionsManager

• 
  
  The second step is the configuration of the UnifiedSessionsManagers.
• 
  This includes the installation of eventually missing system components.
• 
  This process is supported by the contained analystics tool ctys-plugins with in depth detailed analysis and display.
• 
  For the automation of the installation of GuestOSs is the configuration of the storage paths for the installation media required.
• 
  A standard menu could be installed and configured by ctys-xdp, which is based on templates.

Third Step:
Automatic Inventory Management of present Machines

• 
  
  The third step is the automated collection of the inventory data for the virtual and physical machines.
• 
  The data is stored within a central database which could be queried by the utility ctys-vhost, fast and easy. The data contains address data and in conjunction attributes of the contained OSs and additional information related to the physical and virtual machines.
• 
  The database serves as a central instance for the mapping of address information as well as for the assignment of virtual and physical machines. E.g. for the implicit startup of sub-positioned 'Container-Machines'.

Forth Step:
Automatic Startup of present Maschines

• 
  
  The forth step to your personal virtual and physical machine - either by console or by login - is the graphical or script based startup.
  
  

Supported Systems

• 
  The current version supports:
  • KVM, QEMU, VirtualBox, VMware(Workstation/Server/Player), and Xen
  • Linux(CentOS, debian, Enterprise Linux/UnbreakableLinux(TM),Fedora, Mandriva, MeeGo, OpenSUSE, ScientificLinux, SuSE, Ubuntu),
    FreeBSD, OpenBSD, OpenSolaris, Solaris
    VMware-ESX-Login(CLI), XenServer-Login(CLI,X11,VNC)
  • Graphical Userinterfaces:
    Gnome, KDE, X11, Xfce, FVWM
    TightVN, TigerVNC, RealVNC, rdesktop/RDP, Xterm, Gnome-Terminal, CLI, and Emacs
    Native-Consoles of Hypervisors.
  
  
• The next versions are going to add support for:
  • OpenVZ, VMware(iESX), and XenServer
  • NetBSD, (ILLUMOS - when available)
  • QNX, and uCLinux - initially for X86 and ARM architectures, RTEMS.

Your personal CloudComposer

• 
  The UnifiedSessionsManager is designed as a general purpose toolset for distributed services and systems.
• 
  Therefore it perfectly fits to the seamless personal usage and management of private and public Cloud Services. The main areas of application are Systemadministration, Software-Development, Simulation, and Testautomation.
• 
  The provided facilities add extended features for virtual services, such as task distribution, virtual nameservices, and inventory management.
• 
  The inherent security concept based on OpenSSH provides reliable applicability for sessions to local and remote sites.

=> A Common View

• 
  
  The UnifiedSessionsManager does not distinguish between types of virtualization. The remaining distinction is a logical 3-layered approach of serving categories:
  
  
  • HOSTs: Native access to the contained Operating Systems.
  • VMs: Virtual Machines - Acces to Hypervisors.
  • PMs: Physical Machines - Management of physical machines.
• 
  Thus resulting in a unified interface as basic infrastructure element for simplified systems integration - e.g. into the first graphical application 'gnome-starter'.


• This founds the basic conceptual building block of v-components .

Copyright