Challenge in asia region connecting each testbed and poc of distributed nfv use cases
1 like346 views
The document discusses the challenges and progress of connecting testbeds and proof of concepts (PoCs) for distributed NFV in the Asia-Pacific region, specifically focusing on a partnership between Okinawa and Taiwan. It outlines the objectives of the Okinawa Open Laboratory and the Institute for Information Industry, detailing their collaborative efforts in building an OPNFV environment and conducting tests. Key lessons learned include addressing skill gaps, the importance of pre-studies, and the necessity of establishing a robust testbed.
Challenge in asia region connecting each testbed and poc of distributed nfv use cases
- 2. Challenge in Asia Region: Connecting Each Testbed and POC of Distributed NFV Use Cases Shuya Nakama, Okinawa Open Laboratory / NEC Solution Innovators Eric Chang, Institute for Information Industry Hideyasu Hayashi, Okinawa Open Laboratory / NEC Solution Innovators
- 3. Agenda Introduction How to encourage and involve APAC areas? An example lab (APAC) ～Connecting OPNFV Testbed between Okinawa and Taiwan～ Lessons Learned 3
- 5. Introduction(OOL) Name Okinawa Open Laboratory, General Incorporated Association (abbreviation: Okinawa Open Lab, OOL, etc.) Foundation Founded on May 8, 2013 Location Okinawa, Japan Web http://www.okinawaopenlab.org/en/ Purposes Research and development activities for practical application and dissemination of SDN, NFV, cloud computing. 5
- 6. How to encourage and involve APAC areas? 6
- 7. Lower the hurdles to begin Teaching build know-how Operating, and try original modification Connecting and collaborating Communicate closely Joint troubleshooting by always-on connection such as Skype Encourage to be hub in that area III will become a hub in Taiwan. How to encourage and involve APAC areas? 7 We made such theory and tried it
- 8. 8 An example lab (APAC) ～Connecting OPNFV Testbed between Okinawa and Taiwan～
- 9. Introduction (III) Institute for Information Industry • Found in 1979,non-governmental organization • Location Taiwan, employees > 1000 • Research area: – Smart Network System – Innovative DigiTech-Enabled Applications & Services – Data Analytics Technology & Applications Research – Cybersecurity Technology – Digital Education • Our Objectives : To increase innovative applications of information technology and to facilitate the development of knowledge-based economy . • Web : http://www.iii.org.tw 9
- 10. Background of OPNFV in III • Start at the beginning of 2017 To share our OPNFV experience in Taiwan ( accelerate local Industry Growth) We involved NFV, SDN, 5G projects ( new architecture, service, deployment ). Contribute to open source community (contribution & experience sharing).OPNFV 10
- 11. NFV in Taiwan Operators Vendors NPO/NGO Universities CHT,FET,TWN… Collaborate with International operator or vendors for trial Trend Micro, NEXCOM, Foxconn, EstiNet, Xinguard... Develop VNF or Joint development SDN NFV alliance, III, ITRI Share information, Kicked off NFV research Projects NTU, NTHU, NCTU, NTUT…. Research SDN/NFV topic Operators and vendors are putting resource on NFV trial or partial development, the relevant organizations also work on this field. 11
- 12. Our steps in verification 12 Installation Testing Multisite Testing Hardware requirement: - Server spec. & qty. - Switch spec. - Cabling Installation documents - Layout of environment - Jump server - Fuel server - Colorado3.0 Hardware Installation - Server and switch connection - Internet connection Jump Sever and Fuel server - OS and software deployment Deploy Nodes - Controller & compute node Functest environment - Docker - Colorado3.0 Testing - vPing - vRouter - vims Configuration - Network Change - Openvpn connection Connection verification - Ping between OOL and III Testing - vRouter OOL shares the know how of building OPNFV and experience to III at every stage. - Reference documents - Errors in logs - Suggest the solution 12
- 13. OPNFV environment in III OPNFV environment Installer ： Fuel OPNFV version ： Colorado 3.0 Server configuration 1 Controller node, 1 Compute node. CPU ： 12 cores （6cores × 1thred/1core × 2sockets） Memory ： 32GB Jumpserver CPU ： 12 cores （6cores × 1thred/1core × 2sockets） Memory ： 32GB 13
- 14. OPNFV environment in III 14
- 15. Engineers are working on for build of environment Communication using Skype Input know-how of building OPNFV environment from OOL. Using Skype to cooperate and discuss with OOL for troubleshooting solution. Successful completion of building OPNFV environment. Build OPNFV environment in III 15
- 16. Tried the Functest in III Lab We tried running some test cases of Functest. • Test cases – vPing_ssh – vRouter – vIMS Jump , Fuel Server Control node Compute node Admin network Management net. Public network Private network Servers Switches Test bed in III Lab Internet 16
- 17. Tried the multisite vRouter testing Site#1(Master) Site#2 Functest (vrouter test in the Functest) Cloudify Manager (orchestrator) VNF VNF Site#3 VNF For each sites Deploying topology on Site#1 Deploying topology on Site#2 Deploying topology on Site#3 Requesting deployment Authenticatio n info (1) user (2) pass (3) URL Authenticatio n info (1) user (2) pass (3) URL OpenStack cr edential (1) user (2) pass (3) URL(IP) Blueprint (TOSCA based topology) Blueprint (TOSCA based topology) Modifying vRouter testing for multisite use case. Functest（vRouter test）have OpenStack credentials of each sites, And blueprints（Topology template、 Based TOSCA）. Deploy the test topology of each sites, by send Blueprint and OpenStack credentials to orchestra (Cloudify Manager). 17
- 18. vRouter test Overview VPN BGP Interconnectivity VNF under test （VyOS Router） Reference VNF （VyOS Router） Test Condition • OOL and III OPNFV Test bed • VPN Connection • VNF VyOS 1.1.7 Test items • BGP Interconnectivity • Peering status • Number of advertised route • Send Route information properly • Receive end Route information properly • Correct routing table or not 18
- 19. Connecting OOL and III Connected “Management network of OpenStack“ And “Public network（external network）” using OpenVPN. Jumpserver Site#1 OOL (master) Site#2 III Functest (vrouter test system in the Functest) Cloudify Manager VIM standard hardware NFVI OpenVPN OpenVPN Management network Public network VIM standard hardware NFVI 19
- 20. vRouter Architecture & Test Flow 1. Create tenant and user on OpenStack of OOL and III 2. Register OS image to OpenStack of OOL and III 3. Install Cloudify CLI module in the functest container 4. Deploy Cloudify Manager to OOL environment 5. Deploy test topology to environment of OOL and III 6. Execute BGP interconnectivity test a) Configuring to target vrouter b) Configuring to reference vrouter c) Collecting result from target vrouter 1 11 2 2 2 3 4 45 55 6.a 6.b6.c Architecture Test Flow 20
- 21. Demo video 21
- 22. Difficulties and solutions during testing No. Stages Difficulties Solutions １ Fuel Server Installation Repositories check fail when installing fuel server. Modify DNS setting. ２ OpenStack deployment 1. Network verification fail when deploying OPNFV environment. 2. Control nodes and compute nodes are not able to get private IP. 3. PxE boot fail. Modify NAT Setting of jump server. Change Gateway setting ３ Functest vIMS Fail to vIMS test, cloudify manager time out Use more compute nodes (Testing after new servers arrival). ４ OpenVPN Installation Cannot negotiate between OOL and III. Modify MTU to 1450. 22
- 23. Sharing experience • Pre-study OPNFV • Collaborate with OOL • Build OPNFV environment in practice • Share experience & discussion • Running test cases • Further test cases • Share know how to vendors & Taiwanese universities 23
- 24. OPNFV Continue working on 24 Further Testing • vIMS (Debugging) • vRouter (Master) • Others HUB • Vendors • Labs • Universities CAPACITY •More servers •Virtualization •Coding •Network Further Testing Capacity Enhancement Hub in Taiwan
- 26. Gaps existed in the knowledge and network skills, So it took time to solve the basic setting. There was a case that it did not work, Because, the number of nodes and specs were not enough. Stumbled point 26
- 27. Building testbed is good to start up Pre-study is important, especially for OpenStack and Network OPNFV Community work is next step It is important to choose a Hub Lessons Learned 27
- 28. Q&A 28
- 29. 29