D6.2. Configuration of pilots and pre-validation

This deliverable presents the current status of pilots configuration and pre-validation activities. The deliverable comprises of two parts. The first part aims to renew information delivered in Deliverable 6.1, as a infrastructure deployment moved on and new configurations were put in place. The second part provides technical details on the pilot deployment and configuration as well as the preliminary implementation of VNFs. The summary this deliverable updates the information with respect to the deployed infrastructure supporting SONATA integration, qualification and demonstration environments. The demonstration infrastructure is now expanded via connection of remote testbeds to the original core infrastructure of SONATA in Athens. The remote testbeds (i.e. Aveiro, Paderborn, Tel-Aviv, and London) are interconnected via VPN connections and provide a more large scale view of the SONATA deployment. Under this prism, multiple configuration may be applied in order to conduct experimentations and realise the pilots. Detailed technical descriptions are provided for each testbed and the hosting infrastructure. Moreover, specific focus and role is initially assigned for each participating testbed. The final selections of pilots, according to the selection methodology followed in Deliverable 6.1 concluded to the: (i) Virtual Content Delivery Network pilot; (ii) Personal Security Application pilot and (iii) the Hierarchical Service Providers pilot. The detailed technical information about the above pilots is provided by this document taking into account the relative progress in its one. The documents also provides information on the VNFs and the Network Services that will be used to implement the pilots. Finally, the document concludes with the evaluation strategy of SONATA which is based on the approach proposed in ETSI NFV TST documents. The mapping of the pilots mapping to the elicited requirements of Deliverable D2.3 is updated as well as the metrics that should be used for the validation of non-functional requirements.