Draft.

Project Name:

• Proposed name for the project: ONAP Platform Containerization
• Proposed name for the repository: platform-containerization

Project description:

This project describes a supplementary deployment and management solution for ONAP platform components based on Docker containers and the open-source Kubernetes container management system. This solution removes the need for VMs to be deployed on the servers hosting ONAP components and allows Docker containers to directly run on the host operating system. As ONAP uses Docker containers presently, minimal changes to existing ONAP artifacts will be required.

• The primary benefits of this approach are as follows:

  • Life-cycle Management. Kubernetes is a comprehensive system for managing the life-cycle of containerized applications.  Its use as a platform manager will ease the deployment of ONAP, provide fault tolerance and horizontal scalability, and enable seamless upgrades.
  • Hardware Efficiency. As opposed to VMs that require a guest operating system be deployed along with the application, containers provide similar application encapsulation with neither the computing, memory and storage overhead nor the associated long term support costs of those guest operating systems. An informal goal of the project is to be able to create a development deployment of ONAP that can be hosted on a laptop.
  • Deployment Speed. Eliminating the guest operating system results in containers coming into service much faster than a VM equivalent. This advantage can be particularly useful for ONAP where rapid reaction to inevitable failures will be critical in production environments.
  • Cloud Provider Flexibility. A Kubernetes deployment of ONAP enables hosting the platform on multiple hosted cloud solutions like Google Compute Engine, AWS EC2, Microsoft Azure, CenturyLink Cloud, IBM Bluemix and more.

  In no way does this project impair or undervalue the VM deployment methodology currently used in ONAP.  Selection of an appropriate deployment solution is left to the ONAP user.

Scope:

• In scope: ONAP Platform Life-cycle Management through containers (automate the deployment/un-deployment of ONAP instance(s) and individual components through containers, health checks, fault tolerance, horizontal scalability, upgrades of all ONAP platform components)
• Out of scope: support of container networking for VNFs. The project is about containerization of the ONAP platform itself.
  
  

Architecture Alignment:

• How does this project fit into the rest of the ONAP Architecture?
  • Please Include architecture diagram if possible
  • What other ONAP projects does this project depend on?
• How does this align with external standards/specifications?
  • N/A
• Are there dependencies with other open source projects?
  • Docker
  • Kubernetes

Resources:

• Primary Contact Person: David Sauvageau, Bell Canada
• Jérôme Doucerain (Bell), 
• Roger Maitland (Amdocs), 
• Marc-Alexandre Choquette (Bell), 
• Mike Elliot (Amdocs)
• Catherine Lefebvre (AT&T)
• TBD (Orange)

Other Information:

• link to seed code (if applicable)
• Vendor Neutral
  • if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
• Meets Board policy (including IPR)

Use the above information to create a key project facts section on your project page

Key Project Facts

Project Name:

• JIRA project name:
• JIRA project prefix:

Repo name:
Lifecycle State:
Primary Contact:
Project Lead:
mailing list tag [Should match Jira Project Prefix] 
Committers:
foo@bar.com
baz@qux.com
*Link to TSC approval: 
Link to approval of additional submitters: