Updated Concept and Evaluation Results for SP-Devops

Updated Concept and Evaluation Results for SP-Devops

D4.3 Updated concept and evaluation results for SP-DevOps Dissemination level PU Version 1.2 Due date 30.04.2016 Version date 14.10.2016 This project is co-funded by the European Union Document information Editors and Authors: Editors: Guido Marchetto (Polito), Riccardo Sisto (Polito), Wolfgang John (EAB) Contributing Partners and Authors: ACREO Pontus Sköldström, Bertrand Pechenot BME Felicián Németh, István Pelle DTAG Juhoon Kim EAB Xuejun Cai, Chunyan Fu, Wolfgang John, Catalin Meirosu EICT Kostas<[email protected]> Pentikousis iMinds Sachin Sharma OTE Ioanna Papafili POLITO Guido Marchetto, Riccardo Sisto, Serena Spinoso, Matteo Virgilio SICS Rebecca Steinert, Per Kreuger, Shaoteng Liu, Jan Ekman TI Antonio Manzalini TUB Apoorv Shukla Project Coordinator Dr. András Császár Ericsson Magyarország Kommunikációs Rendszerek Kft. (ETH) AB KONYVES KALMAN KORUT 11 B EP 1097 BUDAPEST, HUNGARY Fax: +36 (1) 437-7467 Email: [email protected] Project funding 7th Framework Programme FP7-ICT-2013-11 Collaborative project Grant Agreement No. 619609 Legal Disclaimer The information in this document is provided ‘as is’, and no guarantee or warranty is given that the information is fit for any particular purpose. The above referenced consortium members shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials subject to any liability which is mandatory due to applicable law. © 2013 - 2016 by Participants of project UNIFY (as specified in the Partner and Author list above, on page ii) ii D4.3 14.10.2016 version 1.2 Table of contents 1 Introduction 2 2 Overview of UNIFY and relevant developments in other WPs 4 2.1 Summary of Use Cases and Architecture 4 2.2 Summary of results on Service Abstraction, Programmability and Orchestration 5 2.3 Summary of Universal Node development and benchmarking 6 3 Final SP-DevOps concept 8 3.1 UNIFY SP-DevOps concept 9 3.2 Functional components of UNIFY SP-DevOps 10 3.2.1 Integrated verification of service programming 10 3.2.2 Programmability of observability 11 3.2.3 Infrastructure and VNF Monitoring and Verification 11 3.2.4 Cross-layer observability data distribution 13 3.2.5 Troubleshooting automation 13 3.3 Assessment of the UNIFY SP-DevOps concept 13 3.3.1 SP-DevOps maturity level 14 3.3.2 OPEX saving potential of SP-DevOps 15 3.3.3 Gradual exploitation scenarios 19 4 SP-DevOps tools and functions 20 4.1 VeriGraph - Pre-deployment Verification 21 4.1.1 Purpose and problem statement 21 4.1.2 Brief technical description 21 4.1.3 Recent improvements concerning the tool implementation 21 4.1.4 Recent improvements concerning the tool integration 26 4.1.5 Evaluation results and conclusions 27 4.2 Verification of Path Functionality 29 4.2.1 Purpose and problem statement 29 4.2.2 Brief technical description 30 4.2.3 Evaluation results and conclusions 31 4.3 MEASURE – Expressing Measurement Intents, States and Reactions 37 iii D4.3 14.10.2016 version 1.2 4.3.1 Purpose and problem statement 37 4.3.2 Recent improvements concerning the tool implementation 38 4.3.3 Recent improvements concerning the tool integration 40 4.3.4 Evaluation results and conclusions 41 4.4 TWAMP – Legacy OAM protocol support 42 4.4.1 Purpose and problem statement 42 4.4.2 Brief technical description 43 4.4.3 Recent improvements concerning the tool implementation 43 4.4.4 Evaluation results and conclusions 43 4.5 RateMon – scalable congestion detector 43 4.5.1 Purpose and problem statement 43 4.5.2 Brief technical description 43 4.5.3 Recent improvements concerning the tool implementation 44 4.5.4 Recent improvements concerning the tool integration 45 4.5.5 Evaluation results and conclusions 45 4.6 Probabilistic delay monitoring 47 4.6.1 Purpose and problem statement 47 4.6.2 Brief technical description 47 4.6.3 Recent improvements concerning the tool implementation 50 4.6.4 Evaluation results and conclusion 50 4.7 EPLE – efficient SDN loss monitoring 53 4.7.1 Purpose and problem statement 53 4.7.2 Brief summary of concept and design choices 53 4.7.3 Description of prototype implementation 54 4.7.4 Evaluation results and conclusions 55 4.8 IPTV Quality Monitor 63 4.8.1 Purpose and problem statement 63 4.8.2 Brief Technical description 64 4.8.3 Recent improvement 64 4.8.4 Evaluation results and conclusions 64 4.9 AutoTPG - Verification of Flow Matching Functionality 65 4.9.1 Purpose and Problem Statement 65 4.9.2 Brief Technical description 65 4.9.3 Recent improvements concerning the tool integration 66 4.9.4 Evaluation results and conclusions 66 4.9.5 Conclusions 70 iv D4.3 14.10.2016 version 1.2 4.10 DoubleDecker messaging system 70 4.10.1 Purpose and problem statement 70 4.10.2 Technical description 70 4.10.3 Recent improvements concerning the tool implementation 71 4.10.4 Recent improvements concerning the tool integration 71 4.10.5 Evaluation results and conclusions 73 4.11 Recursive Query Language for monitoring results 73 4.11.1 Purpose and problem statement 73 4.11.2 Brief technical description 74 4.11.3 Recent improvements concerning the tool implementation 75 4.11.4 Recent improvements concerning the tool integration 77 4.11.5 Evaluation results and conclusions 77 4.12 EPOXIDE – Multicomponent troubleshooting 80 4.12.1 Purpose and problem statement 80 4.12.2 Brief technical description 80 4.12.3 Recent improvements concerning the tool implementation 81 4.12.4 Recent improvements concerning the tool integration 83 4.12.5 Evaluation results and conclusions 85 4.13 Final toolkit composition and status 86 5 SP-DevOps workflows and processes 88 5.1 Scopes and Roles of processes 88 5.2 Verification workflows 89 5.2.1 Pre-deployment verification 90 5.2.2 Post-deployment verification 92 5.3 Monitoring workflow 96 5.3.1 Service SLA monitoring process 96 5.3.2 Orchestration dynamicity support process 99 5.4 Troubleshooting workflows 102 5.4.1 Troubleshooting process for VNF development support 103 5.4.2 Service troubleshooting process 104 6 SP-DevOps use-cases and demo implementations 107 6.1 Integrated verification of NF-FGs 107 6.2 Elastic router monitoring and troubleshooting support 109 v D4.3 14.10.2016 version 1.2 6.2.1 Elastic Router use-case 110 6.2.2 Integration of monitoring components to an Elastic Router service 113 6.2.3 Integration of troubleshooting components to an Elastic Router service 115 7 Conclusions 118 List of abbreviations and acronyms 121 References 123 Annex 1: Mapping final SP-DevOps results on initially defined challenges 130 vi D4.3 14.10.2016 version 1.2 List of figures Figure 1 Softwarization as a systemic trend in Telecommunications and ICT. ..................................................................................... 2 Figure 2 SP-DevOps processes mapped on the UNIFY service lifecycle. ................................................................................................ 8 Figure 3 Architectural mapping of functional components of SP-DevOps (yellow) on the UNIFY architecture. ............... 9 Figure 4 (a – left): Average incident duration per category; (b-right): Potential gains per category. ...................................... 17 Figure 5 Modelled savings in incident occurrence. ............................................................................................................................................ 18 Figure 6 Combined modelled savings in incident occurrence and duration. ....................................................................................... 18 Figure 7 Verification Tool Architecture. ................................................................................................................................................................. 22 Figure 8 VeriGraph verification scenario. .............................................................................................................................................................. 27 Figure 9 VeriGraph phases (Chain1). ........................................................................................................................................................................ 28 Figure 10 VeriGraph phases (Chain2). ..................................................................................................................................................................... 28 Figure 11 Depiction of controller application and data plane approach for tagging. A Controller application on top of the SDN controller tags packet in the former whereas the switches (S1-3) tag packets in the latter approach. .............. 31 Figure 12 Wayup and Peacock reference setup with single network update round. ....................................................................... 31 Figure 13 Wayup2 with two rounds of network update. ................................................................................................................................. 31 Figure 14 Wayup3 with three rounds of network update. ............................................................................................................................ 32 Figure 15 Wayup4 with four rounds of network update. ............................................................................................................................... 32 Figure 16 Peacock3 with three rounds of network update.......................................................................................................................... 32 Figure 17 Peacock5 with five rounds of

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    141 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us