...

...

Internship Projects/Mentors

...

ONAP, the Open Network Automation Platform has transformed the telecommunications industry forever and is a key component of the 5G story. But don't worry, this internship does not require any background or knowledge of the network or telecommunications industry.  It is instead about an experimental web application that provides high value when viewed in one context, causes redundancy when viewed from another perspective and a mutually agreed upon need for a solution to the same critical shared problem.

At a high level ONAP is a complex architecture with a myriad of interdependencies and relationships between ONAP's components, other open source projects and industry standard organizations.  For an engineer wanting more information on ONAP one of the first things they do is to pull up the architecture diagram and then go searching for the appropriate documentation set in relationship to it.  The feed back we've received from new users is that actually finding the correct documentation is often time consuming and confusing.   Making the correct documentation easier to find is the, "mutually agreed upon need" part.

ONAP documentation takes on 2 forms. First (and the most problematic) is development documentation on https://wiki.onap.org/ which highly uncontrolled tends to get obsolete rapidly.  The second is the official documentation at https://docs.onap.org/ which is curated content.  The latter is the realm of ONAP's Documentation project a hard working group of folks that are responsible for defining the guidelines and tooling for documentation handling across all ONAP projects and ensuring . The also help ensure that when we cut a release the documentation is in the best possible state.  They don't write the documentation per-se, but they make sure that the structure, look and feel and the like similar things are aligned and as complete as possible.

ONAP's Architecture Subcommittee also works across all of our projects.  This group spends most of its time evaluation of evaluating how the technical pierces of ONAP all work together and align.  The ONAP Architecture Navigator (ArchNav for short) is a web based Proof of Concept (PoC) developed by ONAP's Architecture Subcommittee for the purpose of quickly popping around the areas of ONAP documentation via the official architecture diagram for each release. This allows people to find information in a manner that is based upon a visual representation driven rather than than  being more menu driven. 

The time has come to transition ArchNav out of the lab an into a production environment for the Architecture Subcommittee.  This is a pretty straight forward technical effort for anyone with the "Must Have" skills listed below.

The potential exists for ArchNav to also play a role in ONAP's documentation, education and marketing efforts, but there are alternatives, integrations or and alignment that the Doc team also may want to pursue instead. So what is the right thing to do? 

Welcome to the world of project management and collaboration in opensource. That's what we do every day at the Linux Foundation and that's what the biggest thing you will learn with this internship.    You will be working with a truly international team which includes the Doc project team,  the Architecture Subcommittee and others from the ONAP community to coordinate the correct solution to our shared needs.   In this context you  You won't be making the decisions or necessarily evaluating figuring out what the best solution is yourself, but you will be an equal partner in the process as the person helping to coordinate all of that effort. 

Additional Information

• Current prototype site: https://safratech.net/onapdocs/
• Source code: https://github.com/ca2853/onapdocs (dev branch)

Learning Objectives

• Considerations and requirements for a production grade web based application
• Processes related to project management in an opensource community

Expected Outcome

• Open Source Project Management:  Agreement is reached on at least one of these three:
  1. ArchNav should be migrated to infrastructure managed by the Linux Foundation in a stand-alone context for the Subcommittee
  2. ArchNav should be migrated to infrastructure managed by the Linux Foundation as a shared resource for the Doc Team and Subcommittee
  3. ArchNav should not be migrated and a specific alternative solution will be implemented instead.
• Technical:  Regardless of the three above there will be some level of tooling and scripting as proof points or migration efforts to help move things forward as part of the team.

Relation to LF Networking 

ONAP

Education Level

Skills

• Must Have: Standard web development concepts and practices, JSON, PHP, HTML, CSS comfortable using Linux and script writing
• Extra Points: Rich Text Format, Read-The-Docs, Confluence, Jira, Git, GitHub, Gerrit and knowledge of the Apache2 webserver, 
• Level-up:  Multi-participant project management or coordination

Future plans

The intern can stay engaged as a Committer or code contributor to the project if desired as updates to the code will be required for each ONAP release.

Preferred Hours and Length of Internship

Full-Time

Mentor(s) Names and Contact Info

Technical: Chaker Al-Hakim Architecture Subcommittee Chair, Futurewei
Technical: Thomas Kulik, Doc Project Technical Lead,  Deutsche Telekom
Project Management: Kenny Paul, Technical Program Manager, The Linux Foundation

...