Module testing. During the deployment of the two different blocks of Use Cases we have requested VMs to KVM-CRM in dif- ferent installations (mainly at PSNC and AIST islands); where all new features have been used. Specifically, the Infrastructure Domain Use Case required nested virtualisation to properly operate; and the Data Domain Use Case provisioned VMs in KVM-enabled islands, using specific disk image to account for the needs of some appli- cations, such as the controller and the SMOS viewer. Therefore the Use Cases, acting as ”clients” that request specific functionalities, have been used also to im- plicitly ensure the proper working of the new features in C-RM. After each provision, the VMs provisioned were started and accessible using the user’s public key passed along with the request. Once VMs were deleted, the hy- pervisor started the deletion of the machine and associated resources, allowing further similar requests in other experiments.
Module testing. In the same way as CRM, the SDN-RM module has been manually tested through the implementation of the XXXXX Use Cases. Every UC requested SDN resources which were correctly provisioned (to enable the chosen ports and matching conditions) and deleted (to free them immediately for other usage), and consequently there were no further feedback or improvement requests.
Module testing. The SE-RM module and the software associated (e.g. the OpenFlow controllers) were tested in three different ways: • Single module testing performed using OMNI-client and contacting directly SE-RM • Single module testing performed using the jFed GUI • XXXXX Use Case execution, where (M)RO has identified SE resources and configured in the SE-RM module SE-RM was deployed and validated with a set of physical switches (Juniper MX, NEC PF5240, HP Procurve) as well as with Open vSwitch. Validation was considered to be successful once i) the proper pair of ports of the stitching switch were reserved, ii) the proper OpenFlow flows were installed and iii) VLAN tag translation occurred in network frames going through the stitching switch.
Module testing. The TN-RM functions were validated by deploying the module in the XXXXX testbed and leaving it ready for internal experiments and the set up of the XXXXX Use Cases. TN-RM was successfully used to request and provision a NSI- based path between Japan and Poland. This path was subsequently used in the Infrastructure Domain Use Case. At the conclusion of the each experiment, the network link was terminated and could be re-provisioned for other experiments.
Module testing. The functions from (M)RO have been validated by making the module available per islands of the XXXXX test-bed, so it is used for experiments and Use Cases. Its northbound API has been used every time a slice was created across some of the islands in Europe and Japan. The feedback provided by the definition of the experiments has been key to improve the internal working of (M)RO, as well as the format of the RSpecs supported. The provisioning of the reserved resources has been performed using ad-hoc configuration parameters. The connectivity and reachability between the servers used to deploy (M)ROs have also been tested as well to assess successful interworking. The integration between (M)RO and the (Master) Monitoring System or (M)MS has been verified using the graphical section of Expedient implemented for the (M)MS module.
Module testing. The speaks-for functionality has been checked by generating the required ABAC credentials and then validating them at both local and foreign RMs, when sent along with requests. Similarly, the integration with jFed was tested by using the certificate and key issued by C-BAS to log onto jFed and then reserving successfully resources at different RMs. As for the Admin Tool, its functionality was tested in a number of ways: among others, ranging from log-in using appropriate and incorrect certificate and key to create slices, projects and members; or changing member privileges and their membership on slices and projects and verify the changes took place.
Module testing. In order to validate the (M)MS functions, the module has been deployed in the XXXXX test-bed and used to monitor several slices at a time, spanning both Japanese and European infrastructures. Project: Deliverable Number: XXXXX (Xxxxx Agr. No. 608638) D3.5 Since (M)RO implements new features, the integration between the Monitoring System and the up-to-date (M)RO was tested. On the other hand, the multiple MMS scenario was validated by using the Monitoring System within the Infrastructure Use Case.
