Scenario-based Model-driven Configuration Management Proof-of-Concept

Fermín Galán Márquez (galan at dit.upm.es)
September 2009

In this page you will find a software package that can be used to check the feasibility of scenario-based model-driven configuration management for experimentation infrastructures (i.e., testbeds) based on TIM-to-TSM transformations.

Release Date Comments
TIMTransforms-v2009_09_02.tar.gz 02/Sep/2008
  • Upgrade base CIM Schema version (2.18.1 -> 2.22.0)
  • Changes in TIM:
    • TIM_TransmissionCharacteristics now derives from CIM_LogicalElemeent (former derivation from CIM_SettingData avoids defining new local and propagated keys)
    • Defined InstanceID as local key property in TIM_TransmissionCharacteristics
    • Defined LinkInstanceID as propagated key property in TIM_TransmissionCharacteristics
    • Removed GatewayIPv6Address from TIM_StaticIPv6AssignmentSettingData (it was not used)
TIMTransforms-v2008_10_15-p1.tar.gz 01/Dic/2008 very minor change: added a newline at the end of reset_cimon.sh script (we suspect of problems in some cases due to this in the previous version). Thanks to Walter Fuertes for the debugging and reports :)
TIMTransforms-v2008_10_15.tar.gz 15/Oct/2008 Initial release

Note that here we provide a software proof-of-concept, but not the details of the scenario-based model-driven configuration management approach. Such details (e.g., architecture, TIM-to-TSM transformations principles, the Testbed Independent Model semantics, information regarding VNUML-based and ADRENALINE testbeds, etc.) are provided elsewhere (although if you are reading this you maybe have come from some of those sources and you are already aware of the details :)

Within the .tar.gz package you will find:

Further details (prerequisites, installation, etc.) are provided in the README.txt that comes with the package. All the materials within the package can be used under the terms of GPL and Creative Commons Attribution-Share Alike 2.5 Spain licenses for software code and models/documentation, respectively.

Don't hesitate to contact me if you have problems using the software or any other question. In addition, feedback (regarding the software implementation or the ideas behind it) is highly appreciated!

Troubleshooting