Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Open Source Approach to Design and Deployment of Microservices-based VNF

Prem Sankar's presentation from the 2017 Open Networking Summit.

Microservice is gaining increased adoption in the Telco NFV world. It is key to understand the design and deployment methodologies involved in developing Microservice based VNF. This talk provides an opensource practitioner approach to building and deploying a Microservice based VNF and includes the following: - Design patterns, workflow models - Design models for VNF placement, capacity management, scale-in/out and resiliency - Deployment considerations that includes handing of scale and fault tolerant VNF using well known Opensource tools

  • Login to see the comments

Open Source Approach to Design and Deployment of Microservices-based VNF

  1. 1. Open source Approach to Design and Deployment of Microservices based VNF Prem Sankar G, Ericsson
  2. 2. • Microservices – Intro, design patterns • ETSI NFV Architecture • VNF Characteristics • Opensource Ecosystem • Container Orchestration Engine Integration Agenda
  3. 3. What is Microservices? • Reference – Martin Fowler,
  4. 4. Principles that drive Microservices architecture • Services must be loosely coupled so that they can be developed, deployed and scaled independently • Organized around business capabilities • API Focused • Smart endpoints and dumb pipes • Decentralized Governance • Decentralized Data Management • Infrastructure Automation (infrastructure as code) • Design for failure • Evolutionary Design
  5. 5. Network Functions - Flavors PNF VNF Hypervisor Microservices VNF Hardware µs µs µs µs µs µs µs runtime engine
  6. 6. • Reference – Chris Richardson es.html Microservices Design Patterns
  7. 7. • Decomposition Pattern • Business Capability/Subdomain context • Service discovery Pattern • API Gateway Pattern • Database per service Pattern • Keep each microservice’s persistent data private to that service and accessible only via its API • RDBMS design approaches • Private-tables-per-service – each service owns a set of tables that must only be accessed by that service • Schema-per-service – each service has a database schema that’s private to that service • Database-server-per-service – each service has it’s own database server. • Circuit Breaker Microservices Design Patterns for VNF
  8. 8. • Elasticity • Fault Tolerance • Agility/ • API-based/End points • Infra and Location agnostic • Central Orchestration • Predictability • Business needs • 5G, IOT Key drivers for VNF
  9. 9. ETSI NFV Architecture
  10. 10. Workflow Manager and Orchestrator Continuous Integration Continuous Deployment Monitor Design and Creation Operation and Maintenance Deployment and Execution VNF Lifecycle
  11. 11. • Workflow Manager and Orchestrator • ONAP/TOSCA • Design and Deployment • CI/CD Pipelines • Jenkins • Fabric8 (Jenkins, Kubernetes and Docker) • Other options – goCD, • Ansible/Puppet/Chef • Execution/NFVi • Kubernetes with ODL, OPNFV • Monitoring • Prometheus and other alternatives ( • Tracing • Zipkin • Logging • ELK stack Opensource Ecosystem
  12. 12. Host OS Open vSwitch Host OS Open vSwitch Container Orchestration Engine - OpenDaylight VM Container App Container App Container App VLAN’s Orchestrator OpenDaylight Kubernetes / Docker Kuryr Neutron / Gluon Container App Container App Container App Container Mgt (docker, kube-pxy) Iptables / NAT/FW Integrated Native • Reference – ODL COE project,
  13. 13. Deployment Neutron Plugin or Gluon/Proton Linux Linux Linux Linux Kubernetes Datacenter Hardware Linux OpenStack OVS App OrchestrationSystems OpenStack APIs OpenDaylight Kubernetes APIs CNI Plugin KVM KVM ContainerRT Container RT App App App VM Application Container Application AppApp App VNF - Mixed deployment
  14. 14. Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure. -- Melvyn Conway, 1967