Introduction to OAV Automation and Orchestration in the GÉANT Community
•Descargar como PPTX, PDF•
0 recomendaciones•187 vistas
Presentació a càrrec de Maria Isabel Gandia, cap de Comunicacions del CSUC, duta a terme dins la sessió BoF: "Orchestration, Automation and Virtualisation: Focusing on the user" de la TNC21 Networking Conference de Géant el 25 de juny de 2021.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (9)
Similar a Introduction to OAV Automation and Orchestration in the GÉANT Community
Similar a Introduction to OAV Automation and Orchestration in the GÉANT Community (20)
Más de CSUC - Consorci de Serveis Universitaris de Catalunya
Más de CSUC - Consorci de Serveis Universitaris de Catalunya (20)
Último
Último (20)
Introduction to OAV Automation and Orchestration in the GÉANT Community
- 1. Introduction to OAV www.geant.org Susanne Naegele-Jackson, FAU/DFN Maria Isabel Gandia, CSUC/RedIRIS WP6-T2 TNC 25 June 2021
- 2. 2 www.geant.org OAV Survey - Sections Existing Network and Services Platform Current OAV Use Cases and Services OAV Challenges and Priorities Future OAV Use Cases and Services How can the GÉANT Community / the GÉANT Project help? *https://www.geant.org/Projects/GEANT_Project_GN4-3/GN43_deliverables/D6-2_Automation-and-Orchestration-of-Services-in-the-GEANT-Community.pdf
- 3. 3 www.geant.org Collaborative approach to OAV in the GÉANT Community Strong need for collaboration and exchange of knowledge and expertise Knowledge as a gap We speak different languages A generally accepted architecture blueprint needed NRENs are willing to share experiences and learn from others
- 4. 4 www.geant.org Consensus Building – OAV focus groups Architecture/ Mapping CNaaS (use case) Terminology OAV public wiki OAV Training DTN
- 5. 5 www.geant.org Terminology • Need for an agreement on common terminology. • The idea is to have a common ground of understanding.
- 6. 6 www.geant.org Terminology • The FG identified a list of relevant OAV terms and acronyms. • There aren’t any documents in the literature that include all this information. • For each term, a short definition with a reference link (source) was included. • We tried to use standard-based definitions whenever we could find them and listed internal definitions (based on the consensus of all team members) in cases where no standard definitions were found. • A survey was conducted for final adjustments. • It was adopted by the GNA-G team as a reference. https://wiki.geant.org/display/NETDEV/OAV+Terminology https://www.geant.org/Resources/Documents/GN4-3_White-Paper-Orchestration-Automation-Virtualisation-Terminology-1.1.pdf
- 7. 7 www.geant.org Terminology – Terms and Glossary https://wiki.geant.org/display/NETDEV/OAV+Terminology
- 8. 8 www.geant.org Architecture: Decoupled and Modular Systems www.geant.org Building blocks + Standard interfaces Easier Collaboration
- 9. 9 www.geant.org Architecture - The Vegas Rule
- 10. 10 www.geant.org Architecture Blueprint: TM Forum open Digital Architecture
- 11. 11 www.geant.org Whitepaper: An Analysis of Existing Architectures • ETSI (ZSM, OSM(MANO)/NFV, GANA) • MEF (LSO) • TMFORUM (ODA, ODF) • Anuta • Ciena • Cisco • GVM • SENSE • TALENT https://www.geant.org/Resources/Documents/GN4-3_White-Paper_OAV-Architectures%20(002).pdf https://wiki.geant.org/display/NETDEV/OAV+Architectures
- 12. 12 www.geant.org Architecture Mappings: SURF https://www.geant.org/Resources/Documents/GN4-3_White-Paper_SURFnet-OAV-Architecture-Analysis.pdf
- 13. 13 www.geant.org Architecture Mappings: CYNET https://www.geant.org/Resources/Documents/GN4-3_White-Paper_CYNET_OAV_Architecture_Analysis.pdf
- 14. 14 www.geant.org Architecture Mappings: CARNET https://www.geant.org/Resources/Documents/GN4-3_White-Paper_CARnet-OAV-Architecture-Analysis.pdf
- 15. 15 www.geant.org Architecture Mappings • Currently working on: • GÉANT • HEAnet • GRNET • PSNC • (your NREN here?)
- 16. 16 www.geant.org Training: The Need for OAV Training Survey implied many NRENs need knowledge Many NRENs not really started yet Tailored training for R&E networks Examples grounded in R&E By the community for the Community Powered by:
- 17. 17 www.geant.org Your Trainers Jasone Astorga (RedIRIS / UPV/EHU) Xavier Jeannin (RENATER) Estela Carmona (RedIRIS / i2CAT) Hamzeh Khalili (RedIRIS/i2CAT) Dónal Cunningham (HEAnet) Roman Łapacz (PSNC) Yuri Demchenko (SURFnet / UvA) Anastas Mishev (UKIM/MARNET) Aleksandra Dedinec (UKIM/MARNET) Susanne Naegele-Jackson (DFN / FAU) Martin Dunmore (Jisc) Simone Spinelli (GÉANT) Sonja Filiposka (MARNET / USC) Kostas Stamos (GRNET / CTI) Maria Isabel Gandia (RedIRIS/CSUC) Pavle Vuletić (AMRES) Eduardo Jacob (RedIRIS / UPV/EHU) Your name here? Iacovos Ioannou (CyNet)
- 18. 18 www.geant.org The OAV Training Map
- 19. 19 www.geant.org Open Window to the Trainers • By video conference on the first Tuesday every month. • Just drop us an e-mail: oav@lists.geant.org, we will send you the link. https://wiki.geant.org/display/NETDEV/OAV+Training+Portal
- 21. 21 www.geant.org OAV Wiki - Knowledge Sharing and Global Exchange • https://wiki.geant.org/display/NETDEV/OAV
- 22. 22 www.geant.org The OAV Community Portal • Each NREN or connected institution may present their OAV work or provide links. • NRENs willing to share information or find out more about OAV can reach the team at oav@lists.geant.org. https://wiki.geant.org/display/NETDEV/OAV+Community+Portal
- 23. 23 www.geant.org Use cases: CNaaS (Campus Network Management as a Service) NRENs offering CNaaS use OAV techniques As in OAV, there are many different approaches and targets Evidence of high level of NREN interest Clear need to share information Discussion channels cnass-discuss@lists.geant.org mailing list #cnaas slack channel Use cases sharing Infoshares Community Portal: https://wiki.geant.org/display/ OAV/OAV+Community+Portal Community meetings: • SIG-NOC meetings • NEMMO Beyond the technical stuff: Service definition https://www.geant.org/Resources/Documents/Campus_Network_Management_Service_Definition_Template_Checklist.docx
- 24. 24 www.geant.org • Tests on the GÉANT Testbed Service (GTS) – Up to 10 Gbps • Bare Metal Servers • Virtual Machines • Containerised infrastructure with Docker Easy way to set up DTNs and test software tools for “long-tail” science • Guidelines for tuning DTN parameters • Networking • Storage • Architecture Use cases: DTN (Data Transfer Nodes) https://wiki.geant.org/display/NETDEV/DTN
- 26. 26 www.geant.org
- 27. 27 www.geant.org
- 28. 28 www.geant.org Download it here: https://wiki.geant.org/display/OAV/?preview=/123792049/1 88907541/OAV_Arch_text_and_infographics.pdf
- 29. Thank you www.geant.org Any questions? Or email us: oav@lists.geant.org © GÉANT Association on behalf of the GN4 Phase 3 project (GN4-3). The research leading to these results has received funding from the European Union’s Horizon 2020 research and innovation programme under Grant Agreement No. 856726 (GN4-3).
Notas del editor
- Introduction to the OAV work done in the GÉANT project for the NRENs and the community
- When the project started, we knew we had to work on OAV, because we have received inputs form different stakeholders during the project preparation phase. But NRENs are at different stages of their journey to OAV. So, we needed to build consensus. But first, we needed to know what you planned and what you needed regarding OAV. Survey objectives - Learn about the strategy and actions of each NREN related to network and service orchestration, automation and virtualisation (OAV); - Explore if there are common use cases, ideas, needs and issues in the community in the areas of automation, orchestration and virtualisation; - Recognise possible areas of collaboration both amongst NRENs and between NRENs and GÉANT; - Determine and recommend possible future work within Work Package 6 (or other WPs) of the GÉANT GN4-3 project that could be of benefit to as many partners as possible for identified use case(s). The survey results are the input for our work. We also had an OAV meeting at TNC 2019 where we discussed about the next steps to take, as well as the GN4-3 Future Service Strategy Workshop, May 19 and the Network Management and Monitoring Workshop (NEMMO), Oct 19
- From this discussions and from the survey, we saw that there is scope for increased use of OAV in the community. We have, like a path to follow, but we have to resolve some things first: Knowledge was mentioned as a gap. Whereas some NRENs are very mature and offering orchestrated services to the users, other NRENs have not yet started this journey into OAV. We speak different languages. We don't have a common terminology. We don't have a common architecture either, but the good thing about this is that while we're trying to find some kind of consensus in terminology, in architecture and others, we are willing to share our experiences, the research and education world is very rich and has the will to share and to present what they are doing and learn from others, and this is very positive. It is something that you may not find in other environments. Our aim is to promote wider adoption of general OAV principles within the NREN community.
- With this aim, we established several focus groups around different topics that had to be short-lived and have specific outputs. Some of them have already finished their work. For instance, we had a terminology focus group that already finished the work and that created a glossary and a terminology document. We have an architecture focus group that worked to find a flexible blueprint where all the research and education institucions could map their own architecture. Campus network management as a service is a clear use case of the usage of OAV, because if you want to offer scalable network management services to your campuses, you need to automate and orchestrate. We also have a focus group on OAV wiki. We have an OAV training focus group where 12 trainers from different NRENs offer short learning units about. And finally we have the DTN focus group around data transfer nodes. How to automate them, how to test them with GTS and some tests we have done on the performance of this DTNs. More focus groups will be established when needed. For instance, the focus group on mapping architectures.
- We created a list of requirements with inputs from several NRENs and we made a list. One of our requirements we saw was that OAV architectures in the research and education world should be highly decoupled modular systems, like building blocks or pieces of a puzzle that can fit together having standardised interfaces. These modular components could be flexibly integrated, new components could be added without breaking existing solutions and the integration with customers and partners using the same rules would be possible. Requirements like flexibility, modularity, scalability or the support for innovative future development and research are key for any research and education network.
- Another requirement related to this one was that anythind that happened inside a domain should not affect others, or what we later knew as the Vegas Rule. With this list in mind, we compared several existing architectures from standardisation bodies, private companies and projects.
- We have analysed the requirements for building collaborative digital services and propose a high-level reference architecture that can help the community design and implement their digital platforms in an interoperable way. The flexibility of the proposed blueprint architecture is presented by mapping it against different architectural solutions proposed by standardisation bodies and research projects The idea behind this analysis was to provide a framework that could benefit the community for the development and implementation on future single and multi-domain digital services. We chose the TMForum Open Digital Architecture or ODA as the flexible blueprint for OAV. The TMForum Open Digital Architecture defines a list of principles and guidelines to help in high level architecture decisions that are aligned to the requirements of the research and education networks. The final architecture and the design in each institution, however, will depend on each case. ODA is a high-level functional architecture with five functional blocks, also called domains, and a decoupling and integration layer between them, as you can see in the picture. It is compatible with other architectures.
- The Focus Group on OAV Architectures in the GN4-3 project identified the aspects covered by existing architectures that aim to solve all or some of the aspects of OAV. It studied the main characteristics of these architectures, use-cases and relationships with other efforts. Then, it analysed how each architecture would fit in the list of requirements for the NRENs we saw. The group found that, although the approaches look different, there are a lot of commonalities.
- As we saw before, knowledge was mentioned as a gap in the survey, and we want to do something about it. We want to facilitate a knowledge transfer instead of having a knowledge gap. On the other hand, many NRENs have not really started automating yet. If you Google “network automation training”, more than 250 milion entries will show you that there is a lot of material out there. Many tools, platforms, programming languages, concepts like data formats and data modelling... There are excellent courses, but it’s easy to get lost. That’s why we planned to prepare a training focused on the research and education community, with external references that can be useful for us and examples that can be closer to our use cases. It’s a training by the community for the community. And we have done it in collaboration with the GÉANT Learning and Development Team, using the e-Academy platform and Moodle.
- These are your trainers. A group of people from several NRENs around Europe that have experience in OAV and can help you with the first steps of this journey to OAV. From university professors to network engineers and from managers to developers. If you have experience and you are wiling to share it, we will be happy to include collaborations from the community.
- We have prepared a phased approach to the training. The metro map lets you choose your path and follow the learning units that are more relevant for you. There are 11 learning units and 6 documents published so far.
- and we will have one hour per month for Questions and answers, like an open window to the trainers every first Tuesday, every month.
- The first link you see here is the OAV wiki. It’s for knowledge sharing and global exchange among the NRENs and research and education institutions. All about Orchestration, Automation and Virtualisation and classified in different sections, with dissemination documents, highlights, information about the Infoshares we have done, architectures, a community portal, literature, terminology and glossary, information on standardisation bodies and also events. There is a lot of information here and it’s constantly updated. So, maybe when you look at it it’s different to what you see here because it’s constantly updated as I said. But it’s important that you remember that you are also part of this community. So, if you have anything that you would like us to share in this wiki, do not hesitate to contact us.
- The wiki also contains a community portal where each NREN or connected institution can present what they have done in OAV. So, if you want to share your information, or find more about OAV, you can also reach us and we will include your examples here.
- GTS supports links up to 10Gbps
- Pamphlet that is delivered to the NRENs when approaching them for collaboration.