Internship Projects/Mentors

Description 

Already familiar with things like PHP, JSON, HTML and CSS and ? Do you want to learn some of the non-technical skills needed to launch effectively collaborate in an entirely opensource project from scratchas more than just a code contributor?  If so this could be the perfect internship for you.

ONAP, the Open Network Automation Platform is the open source project that has  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 a an experimental web application and open source itself.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 The ONAP Architecture Navigator (ArchNav for short) is a web based application developed by Chaker Al-Hakim, the Chair of ONAP's Architecture Subcommittee.  The ArchNav provides a dynamically generated dashboard for drilling down into ONAP's complex architecture structure and the myriad of relationships between ONAP's components, other open source projects and industry standards.  The time has come to transition ArchNav from an experimental Proof Of Concept (PoC) in the lab and formalize it it as a key piece of ONAP's documentation, education and marketing efforts.   

In addition to the technical opportunity encompassed in the migration of the application to be a production service, this internship also provides the candidate with an extremely unique project management and leadership opportunity in launching the Architecture Navigator as a brand new open source project under ONAP.    In that context you will be working with Chaker Al-Hakim, the Architecture Subcommittee, members of the opensource community that will be contributing to and maintaining ArchNav and ultimately pitching the new project proposal directly to the  ONAP Technical Steering Committee (TSC) for approval.

Additional Information

standard organizations.  One of the first things a new user may do when investigating ONAP is look at the architecture diagram and then go searching for the appropriate documentation set in relationship to the picture.  The feedback we've received 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 previously mentioned.

ONAP documentation takes on 2 forms. First (and the most problematic) is our development documentation on https://wiki.onap.org/. This is highly uncontrolled and gets obsolete rapidly.  The second and more important part is the official documentation at https://docs.onap.org/ which is all 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. They also help ensure that when we cut a new 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 similar things are aligned and as complete as possible.

ONAP's Architecture Subcommittee also works across all of our projects. This group is focused on how the technical pieces of ONAP all fit work together. The ONAP Architecture Navigator (ArchNav for short) is a web based Proof of Concept (PoC) developed by the Subcommittee for the purpose of quickly moving around areas of ONAP documentation via the architecture diagram specific to each release. This allows people to find information in a manner that is based upon a visual representation of the architecture itself rather than being a more menu driven model. 

There were discussions underway to transition ArchNav out of the lab an into a production environment for the Architecture Subcommittee. That is a pretty straight forward technical effort for anyone with the "Must Have" skills listed below.

The Doc team also wants to pursue ArchNav like functionality however they feel there is no need for it to be a separate application. Instead they believe the same functionality can be implemented directly in ReadtheDocs which is the platform we use for our official documentation.   

So what is the right thing to do? 

Welcome to the world of project management and collaboration in open source. That's what we do every day at the Linux Foundation and if you that's 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.   You won't be making the decisions or 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

• ReadtheDocs 
• Current ArchNav Current prototype site: https://safratech.net/onapdocs/
• Repositories:
  • ArchNav
  Source code
  • : https://github.com/ca2853/onapdocs (dev branch)
  • ONAP Doc Project: https://github.com/onap/doc

Learning Objectives

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

Expected Outcome

...

• Open Source Project Management:  Consensus is reached on the most practical approach for the community::
  1. ArchNav will not be migrated and a solution will be implemented in ReadTheDocs infrastructure.
  2. ArchNav will be migrated to infrastructure managed by the Linux Foundation as a shared resource for the Doc Team and Subcommittee
  3. ArchNav will be migrated to
  The ArchNav application is established as a formal production service within
  1. infrastructure managed by the Linux Foundation
  (minimum)
• The current prototype instance of the application can be decommissioned with not adverse effects on the ONAP community
• 1. as a stand-alone solution for the Subcommittee
• Technical:  Regardless of the three possible project management outcomes above there will be tooling and scripting required throughout the course of this internship either as proof points, implementation and deployment or migration tasks to deliver the agreed upon solution.The Architecture Navigator is approved as an Incubation project by the ONAP TSC (ideal)

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, ReadTheDocs, 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

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

...