Virtualization Versioning
We have configuration management for dealing with static items like source code and compiled binaries and even PDF documents.
However, there is, as far as I can tell, no version control for dynamic execution environment. In the days of virtualization (today), it is now possible to selectively specify the exact versions of kernel, dynamic libraries (DDL for Windows people) which are the ideal for a specific version of an application. This way, the application developer can specific the exact versions that will work with a given program. And then the user can mix and match newer or older versions of libraries and appropriate patches to ensure a reliable run-time of the application. The user can also control for variation of libraries for optimum memory usage or run-time performance or run-time stability.
Virtualization Run-Time Configuration Management (VRTCM or virtchim?) is what I have in mind.
Note that this would be a simple control of the various kernel and libraries out there that can be safely linked into a given app.
The next level would allow for virtualization of the kernel/library interfaces so that mismatched interfaces can be made to work dynamically (force incompatible versions to run together, in case one needs a newer/older library which is more secure or more reliable but not supported by the user's application).
Another level of virtualization would be to allow for user defined (for those roll-your-own hackers) patches to run in place of the official binaries available. I suppose those patches available online can be used by others as well. By using virtualized environment, the risks of virus and corruption can be much easier to control and be contained.
Copyright 2007, DannyHSDad, All Rights Reserved.
However, there is, as far as I can tell, no version control for dynamic execution environment. In the days of virtualization (today), it is now possible to selectively specify the exact versions of kernel, dynamic libraries (DDL for Windows people) which are the ideal for a specific version of an application. This way, the application developer can specific the exact versions that will work with a given program. And then the user can mix and match newer or older versions of libraries and appropriate patches to ensure a reliable run-time of the application. The user can also control for variation of libraries for optimum memory usage or run-time performance or run-time stability.
Virtualization Run-Time Configuration Management (VRTCM or virtchim?) is what I have in mind.
Note that this would be a simple control of the various kernel and libraries out there that can be safely linked into a given app.
The next level would allow for virtualization of the kernel/library interfaces so that mismatched interfaces can be made to work dynamically (force incompatible versions to run together, in case one needs a newer/older library which is more secure or more reliable but not supported by the user's application).
Another level of virtualization would be to allow for user defined (for those roll-your-own hackers) patches to run in place of the official binaries available. I suppose those patches available online can be used by others as well. By using virtualized environment, the risks of virus and corruption can be much easier to control and be contained.
Copyright 2007, DannyHSDad, All Rights Reserved.
Labels: virtualization, virtualization run-time configuration management
posted by DannyHSDad at
5:54 PM
