Computing Resource Manager Clause Samples
Computing Resource Manager. The Computing Resource Manager module (C-RM) is based on the ▇▇▇▇▇▇ Virtualisation Technology Aggregate Manager. The C-RM allows an experimenter to provision and manage VMs on different physical servers. The components and their functionality are explained in the Design section. There is some extra implemen- tation that extends the functionality of the C-RM in order the requirements from ▇▇▇▇▇: • Adopting the latest GENI testbed federation API (GENIv3) to allow allocation prior to provisioning. • Allowing user SSH keys contextualisation in the Virtual Machines to enable direct access through public keys. The latest additions collaborates in standardizing the access to the Resource Managers of the ▇▇▇▇▇ ▇▇▇▇▇- work and to the resources provided by them; not only internally but also looking to possible inter-testbed ▇▇▇▇▇- ations. This module contains a number of components and subcomponents that work together in order to reserve, create, manage and delete the requested Virtual Machine resources.
3.2.1 Design
Computing Resource Manager. The C-RM is a module developed using the Python language and the Django web framework, and it includes the components mentioned in the Design section: 1) the core, 2) the Agent, 3) the Policy Engine and 4) the web-based GUI. The core, the Agent and the web-based GUI are released together in the form of source code. On the other hand, the Policy Engine is designed as an external library which is released on its own and in the form a Debian package. Once the C-RM sources are downloaded and the installation or upgrade script is run, these scripts automate the installation and help with its configuration. This is performed this way because of the PE integration within C- RM. As for the Agent installation, it has different requirements (e.g. structure of folders, installation requirements and workflow). This installation is to be performed in a different machine, where the hypervisor is running. This is the list of requirements and dependencies to install C-RM. It is the basically the same as the needed for other ▇▇▇▇▇▇ Control Framework components (e.g. Expedient, OpenFlow AM) and thus almost the same for the ▇▇▇▇▇ RMs.
Computing Resource Manager. Similarly to the SDNRM, the Computing Resource Manager (CRM) is a ▇▇▇▇▇ soGware module based on a previ- ously existing component, called Virtualisation Technology Aggregate Manager (VTAM) and developed under the ▇▇▇▇▇▇ project. As such, its core functionalities were already tested there. The work in SDNRM performed in ▇▇▇▇▇ is related to the extension and the bug fixing of its northbound GENIv3 API [4] and of some of the internal submodules being used to attend the requests coming from the northbound interface. In the following sections we detail the validation and testing procedures carried out to ensure proper inter- working with GENI-compliant clients, whether third-party clients (OMNI, jFed) or other ▇▇▇▇▇ modules (Resource Orchestrator).