In this presentation, you will learn about microservices, containers, container orchestration, Kuberbetes orchestration, container adoption challenges, container networking, service mesh and integration with OpenDaylight. Learn more at www.luminanetworks.com/products
The document provides an overview of OpenStack networking and Neutron. It discusses Neutron's architecture and history. It describes several Neutron sub-projects like Midonet, OpenDaylight, OVN, and services like firewall-as-a-service and service function chaining. The document outlines Neutron roadmaps and focus areas. It discusses various working groups and collaboration efforts between OpenStack and other communities like OPNFV and the telecom industry. The document promotes involvement in OpenStack development, events, and training.
Gives an overview about MEC application requirements and microservice patters. Provides a sample app and application of patterns to better design the MEC app. Provides an overview about state management of MEC app
In this presentation, the SDN-Based Enterprise Connectivity Service Architecture of China Unicom will be introduced. And the four use cases will be discussed, including: “Flexible access for enterprise, Cloud access and resource centralized, High efficiency, elastic transport for DCI, Extensible VAS deployment for services”. Finally, some commercial experience in China Unicom will be shared.
Senior Network Analyst Tashi Phuntsho gives an overview of network automation at the fifth Bhutan Network Operators Group (btNOG 5) meeting on 4 June 2018.
This document discusses building a healthy open networking ecosystem through collaboration between communities, users, and vendors. It summarizes the challenges in harmonizing open source projects, the need for users to bring real use cases and commitment to production, and how vendors can deliver quality products and end-to-end solutions. A case study of China Unicom's DCI project is provided as an example of leveraging SDN controllers and common interfaces to automate service provisioning across multi-vendor networks.
This document provides an overview of Cisco Application Centric Infrastructure (ACI). ACI is an innovative datacenter architecture that removes complexity between applications and hardware. It centralizes management of physical and virtual resources to increase security. ACI uses application specific integrated circuits and a common policy-based model to simplify application deployment, reduce costs and complexity. Key ACI components include the Cisco Application Policy Infrastructure Controller (APIC), Application Network Profiles to group endpoints, and Cisco Nexus switches that make up the ACI fabric. The APIC provides centralized management of policies, health monitoring, and automation across physical and virtual environments. ACI simplifies operations through its common policy and management models.
This document provides an overview of service mesh and Istio on Kubernetes. It discusses microservices and the need for visibility, monitoring, and traffic management which a service mesh can provide. It then describes Kubernetes, Istio architecture including Pilot, Envoy proxy, and Mixer components. It covers how Istio provides mutual TLS, ingress/egress traffic routing, request routing to service versions, observability with metrics and tracing, and application resilience through features like timeouts and retries. The document concludes with instructions for deploying Kubernetes and getting started with Istio.
All about SDN/NFV developments within the Telecommunications sector. BSS/OSS evolutions and a drive towards intelligent IT systems.
This document discusses securing microservices in CloudFoundry. It begins by noting the need for microsegmentation as applications move to the cloud and become more elastic. Traditionally defining firewall rules by IP address becomes unmanageable in this environment. The document then proposes defining policies based on application roles and grouping endpoints into policy-defined segments. It provides examples of defining policies by application groups rather than individual IP addresses, avoiding state explosion. This group-based policy approach allows for secure, scalable and intent-based policy definition.