Application of Virtualisation and CloudComputing for Development and Runtime Systems

Virtualisation and CloudComputing

acue ( Ingenieuburo Arno-Can Ustunsoz ) UnifiedSessionsManager 2012.03.01 1 / 18

UnifiedSessionsManagerApplication of Virtualisation and CloudComputing for Development and

Runtime Systems

Embedded World 2012Session 16:Internet Technology and M2M I

Arno-Can Ustunsoz

Ingenieuburo Arno-Can Ustunsoz

2012.03.01


Agenda

Evolution of Virtualisation and CloudComputingThis gives a short definition of the terms Virtualization andCloudComputing, and figures out an extended conceptual framework.

Requirements of distributed and mobile applicationsThis figures out a future design paradigm and its infrastructurerequirements.From single to many-core, stacks of c©’nested VMs’- c©vStacks defined by c©vComponents.

Management of modern Test and Development EnvironmentsThis defines issues for the the manufacturers production and testsystems.

Products targeting the overall Lifecykle - Current StatusThis gives an overview of the available full-scale products.


Agenda






Agenda






Agenda






Evolution of Virtualisation and CloudComputing

A conceptual blueprint of Virtualisation and CloudComputingThe underlying basic concept of CloudComputing is as stated bySun-Microsystems, Inc. in the 80s:

’The network is the computer.’

The mayor distinction results from the introduction of virtual machines:

+ ’ VMs.’

This enables the mobility of - even ’living’ - machines, resulting in theflexibility of the execution location.The introduction of multi-core systems, and particularly the upcomingmany-core systems extends the concept of software components tocomplete VMs.The introduction of virtual CPUs by hypervisors enables the scalabilityand embedded cross-execution.The enhanced processing capability of SOC devices includingmulticore-processors brings the former data-center ’into your pocket’.






+ ’ VMs.’







+ ’ VMs.’







+ ’ VMs.’







+ ’ VMs.’







+ ’ VMs.’



A conceptual blueprint



Nested VMs on Many-Core Systems - From single to many-core

The introduction of c©’nested VMs’ - build by the founding elementsof c©vStacks defined by c©vComponents - leads to the concept of thevirtual containment as a vertical logical tree structure.

The logical tree is mapped to a flat array of CPUs/Cores, resulting inneglible performance loss.



c©’nested VMs’ - c©vStacksThe introduction of c©’Nested VMs’ sets up a layerd architecturesimilar to the ITU-T ISO-Layering - c©vStacks.



c©’nested VMs’ - c©vStacksThe c©vStacks could be depicted similar to the ITU-T B-ISDNdepiction by panes.



Nested VMs on Many-Core Systems - continued

These concepts are now spreading datacenters and are already puttingtheir shadow on embedded systems.Two current examples are:

c©Smartphones e.g. by c©Apple, c©LG, c©Nokia, c©Samsung, ...c©’Raspberry IP’ for the scale of the next generation of home stations.

So it is going to be the paradigm of c©’nested VMs’ in your pocket.


Requirements of distributed and mobile applications

Application pattern - IThese concepts are of course going to be introduced into mashednetworks of embedded systems in all mobile and fixed platforms in nearfuture. E.g. including home-networks, pyhsical and virtualcommunications devices.Some mayor aspects of enhancements as ’killer-applications’ are herescalability, online-reconfiguration and self-healing onboard-networks inmission critical air, land and sea applications.E.g. one possible application is the reconfiguration of standby systemsby immediate arming additionaly processing resources in case of anurgent request.So it is going to be also the paradigm of c©’nested VMs’- seeminglyincluding whatever you use.


Requirements of distributed and mobile applications

Application pattern - IIThe introduction of c©’vComponents’ provides means of systemsmanagement by standard tools and interfaces, e.g. by standard IPmanagement tools and standard/proprietary hypervisor interfaces.This defines a runtime environment, where the administrator of thesystem could simply reconfigure a running distributed application orsystem.The c©’vComponents’ particularly contain any required dynamic sessiondata, e.g. including kerberos tickets, which enable for quite simplefailover concepts.The facilities for the dynamic reconfiguration are immanent, thus justrequire minor additional development costs.


Management of Test and Development Environments

Requirements for virtualized Embedded SystemsThe requirements for Development and Testsystems withindevelopment processes could be basically the same superset.Requirements involving extended systems components - either of actualsystems or simulated - may be added when required.Realtime requirements could be at least packaged and managed forembedded virtual systems similar to non-realtime systems by followingassumption:

Runtime images simulate loadable VMs by storing runtime images aspreloadable PMs.Thus realtime-systems and components could be handled virtuallyequal to VMs - as ’realtime vComponents’.


Management of Test and Development Environments

Resulting Requirements for Development and TestEnvironments

Vendor independent manageability of VMs and PMs.A common interface syntax for all supported components.Inventory management with support for versioningManagement of single machines and groups and nested groups asarbitrary sets.The definition of specific views to individual sets of machines.IP-Address-Management, additional protocols as required.Enhanced addressing-scheme covering vStacks.Interactive applicability by commandline interfaces as well as graphicaluser interfaces, including Web-frontends and server-based browseraccess.Simple extension interfaces for the introduction of custom components.Remote facilities for distributed operations.



A physical view on multiple instances



A logical view on multiple instances


Management of modern Test and DevelopmentEnvironments

An example OpenSource-Project - UnifiedSessionsManager Theimplementation of almost all of the above requirements is providedbeginning with 2/2008.

The current public version is provided as a ’production-prototype’ byshell scripts with minor Python components for Linux/BSD/SolarisPlatform. License if - GPL3 and/or CCL - UnifiedSessionsManager.orgThe current version touched it’s limits of perfomance when porting toMS-Windows(C) simply based on Cygwin.A complete refactoring with significant performance and applicabilityenhancements is currently going to be finished and will be availablesoon. The first new Version is a mainly Python based with additionalgraphical user interfaces based on Qt and Web-Browsers.Enhanced customization interfaces and a broad range of scalabilityincluding a server variant is provided.Soon available versions are GPL-3, CCL-2, and a proprietary enterprisevariant.


...

That brings me to the end of my presentation,thank for your attention.


Virtualisation and CloudComputing
