OpenStack Mitaka Design Summit

In this presentation, we will tell the stories of 3 top-tier telcos' journeys to OpenStack. We will discuss the opportunities (private cloud, public cloud, NFV), and challenges each telco faced, lessons learned, and current status of their OpenStack project.

NFV is moving from concept to reality and Openstack is a leading platform of choice for deploying NFV solutions. While there has been a lot of focus on building capabilities in openstack to enable it as the VIM, it is also possible to build enablers for key features like Service Orchestration, Lifecycle management, Diagnostic and fault monitoring capabilities and Service Chaining as apps on the Openstack platform.

In this session we will present the end-to-end deployment,service chaining, configuration, life-cycle management and diagnostic capabilities in an NFV scenario as Openstack Apps for an Openstack based NFVI. We will also share the key learnings that we have gained as part of this exercise.

OpenStack is adopted by enterprises, governments, and service providers who are building out public, private, and hybrid clouds.  As the fastest growing open source project, OpenStack is backed by more than 460 companies across 148 countries.  OpenStack clouds with unified compute, storage, and networking offer powerful XaaS that are enabling new business models.  
Join this session to learn with the help of specific use case example how the latest advances in OpenStack, SDN, NFV, and networking subsystem of the Linux Kernel can be leveraged to build highly available, resilient and scalable infrastructure to support network applications, such as vCPE. In-depth analysis of the details of implementation and configuration options will illustrate how to achieve performance and SLAs required by the demands of telecommunication and enterprise networks.

Cloud computing and mobile computing are two of the biggest forces in the marketplace today. OpenStack has a unique opportunity to become the dominant platform in the converged cloud-mobile world. At their convergence is an emerging new paradigm called edge computing, in which the resources of a small data center are placed in close proximity to mobile devices, sensors, and end users. Terms such as "cloudlets," "micro data centers," and "fog" have been used in the literature to refer to these small, edge-located data centers.

In this talk, Professor Satya will show how OpenStack can be extended to provide the capabilities needed for edge computing. Specifically, the Nova and Glance components of OpenStack need to be extended with support for 3 mechanisms: (a) cloudlet discovery; (b) rapid VM provisioning; and (c) cross-cloudlet VM handoff. The talk will first explain why these 3 mechanisms are necessary and sufficient, and then describe their implementation in the Kilo release of OpenStack. Most of the Kilo implementation remains unmodified. A number of companies such as Vodafone, Intel and Huawei are working together to catalyze an open ecosystem and business opportunities around this extended version of OpenStack. 

Beyond Cofee-shop Cloudlets and WiFi, Prakash Ramchnadran Sr Mobile Cloud Architect from Huawei will highlight the road map of how to enable Seamless Mobility across WiFi & Cellular domain  and push logical Applications to Edges from traditional IMS. How Subscribers can spot one wireless hop away, the Base-station Cloudlets, at the edge, an ideal placement for low-latency offload infrastructure to support emerging applications such as augmented reality and wearable cognitive assistance. The edge is an optimal site for aggregating, analyzing and distilling bandwidth-hungry sensor data from devices such as video cameras. In the Internet of Things, the edge offers a natural vantage point for organizational access control, privacy, administrative autonomy and responsive analytics.

Rolf Schuster as Head of Innovation at Vodafone will then show the business case of in-Vehicle Cloudlets . New challenges and opportunities that a Service Provider will need to bring to Platform like Global/Local Cloulet Service Catalog, cloudlet extensions to OpenStack to enable seamless optimal placement and execution of cloud services at any location ranging from a conventional cloud data center to locations such as homes, automobiles and cellular infrastructure, leading to 4.5G & 5G. The evolution of OpenStack to support 5G with mm-waves will be a challenge that will run through Cloudlets and Service Providers are already getting ready to move to OPNFV and gear up for Open Edge Computing through OpenStack.

The Speakers and Panel will than field questions from OpenStack community and seek ways to collaborate for betterment of Edge Comuting Cloudlet within and around Open Source Eco system. Lead Developer Kiryong Ha  the Cloudlet creator from CMU will be available to build community for Cloudlet in Openstack.

The telecoms industry is undergoing the biggest change in its history as Communication Service Providers (CSPs) move to new DevOps-like delivery models enabled by latest advances in technology such as Network Function Virtualization (NFV) or Cloud in general. OpenStack and other open source projects provide a solid foundation for building next generation Telco Clouds, but building a carrier-grade solution takes more than just picking up and assembling building blocks. 

In this session, we will present a top-down view from Telco cloud-based network service management strategies and the mapping to the underlying infrastructure services provided by OpenStack, based on a real-world implementation. We will outline the concepts of policy-based closed loop management of end-to-end network services, supported by examples, and we will discuss the role of service- and application level monitoring in this policy-based approach.

We will discuss how service-level policies can be broken down and mapped to capabilities provided in OpenStack today in a pluggable architecture, leveraging orchestration technology such as Heat or monitoring in Ceilometer. Based on the presented as-is solution, we will also consider potential future enhancements to OpenStack components, inspired by Telco use cases.

NFV Orchestration involves more than lifecycle management of Virtualized Network Functions(VNFs). Going beyond the lifecycle management of virtualized components, it should:

-- manage complex network and storage configurations for the network functions
-- interface with one or more OSS/BSS systems
-- interface with one or more Element Managers for configuration management of traditional network elements

In this talk we will describe Ericsson’s approach to end to end management of VNFs.

Featuring Verizon, AT&T, Comcast, NTT, CableLabs, and SKT

Telcos all over the world have been considering or are deploying OpenStack for their IT and business transformation. There are use cases of telcos deploying OpenStack for their private cloud, public cloud, hybrid cloud, NFV, and other type of telco specific projects. Telcos sometimes have very unique requirements, which very often are more stringent than traditional enterprises, in the areas of performance, availability, scalability, manageability, and interoperability with other telco standards such as ETSI, OPNFV, etc.  In this panel, we have representatives from six major telcos to share with the audience their experience with OpenStack, and their vision on how OpenStack should evolve in order to meet their telco needs. We will also open up the discussion to include audience' participation.

A panel discussion with experts from HP, Ericsson, Brocade, Alcatel, Huawei and Juniper.

NFV (Network Functions Virtualization) has gotten much press in the past year or two.  First proposed in September 2010 by a subgroup of the European Telecommunications Standards Institute, NFV is emerging to address the need for better tools that provide the greater flexibility and more rigorous control needed to manage the thousands of separate virtual networks used in a cloud.  One way of thinking about NFV is to view the cloud as a set of services that need to be managed, rather than a set of physical and virtual resources.

Many vendors are jumping on the NFV bandwagon and are actively working to create tools based on this approach.  This panel discussion will bring some of the NFV vendors together, so the Open Stack community can see for themselves the maturity, similarities and differences between the products from experts from HP, Ericsson, Brocade, Alcatel, and Juniper.

This talk describes a new service management toolkit, called XOS, built on top of OpenStack and ONOS (Open Network Operating System) to manage scalable services running in a TelcoCentral Office Re-architected as a Datacenter (CORD). The goal of CORD is is to allow Telcos to benefit from both the economies of scale (infrastructure constructed from a few commodity building blocks) and the agility (the ability to rapidly deploy and elastically scale services) that cloud providers like Amazon, Google and Facebook enjoy today.

The first step in re-architecting the central office as a datacenter involves virtualizing the existing hardware devices, transforming each device into its software service counterpart running on merchant silicon (commodity servers, white-box switches, and commodity I/O blades). In the process, functionality is disaggregated and re-packaged in new ways. The current CORD proof-of-concept virtualizes three legacy Telco devices: Optical Line Termination (OLT), Customer Premises Equipment (CPE), and Broadband Network Gateways (BNG).

The second step in realizing CORD is orchestrating the virtualized devices (and other cloud services) to provide the end-to-end functionality subscribers require. To this end, the CORD software stack includes XOS, OpenStack, and ONOS. XOS provides explicit support for multi-tenant services, making it possible to create, name, operationalize, manage and compose services as first-class operations. In particular, it provides a framework for implementing and composing multi-tenant services that become part of the CORD service portfolio, thereby lowering the barrier for services to build on each other.

XOS builds on OpenStack, which manages virtual resources on a cluster of commodity servers. OpenStack is responsible for creating and provisioning virtual machines (VMs) and virtual networks (VNs), while XOS defines a service abstraction on top of these virtual resources. It also builds on top of ONOS, which manages the cluster's switching fabric. ONOS hosts a collection of network control applications, while XOS incorporates those applications into the overall portfolio of CORD services.

We have implemented and demonstrate a proof-of-concept of CORD, and are currently preparing a "CORD POD" for field trials with service providers. This work is being done in collaboration with AT&T, PMC, Sckipio, and Akamai.

Gohan is an API server for XaaS Services. Using gohan webui front-end, you can define new XaaS API on the fly. Resource status will be synced with agents, who will realize XaaS service, using etcd.

Gohan supports the following functionalities:

• Define resources by JSON Schema + Resource configuration


• REST API Server with RDBMS DB backend based on the schema


• etcd sync backend based on the schema


• Policy configuration


• Extension by Javascript


• Automatic API Generation

In this presentation, we will talk about motivation and background of Gohan development, and show how NTT is doing rapid service development such as NFV orchestration and data center network automation. 

Connecting an Enterprise Branch to the Enterprise Headquarters and Data Center in a seamless way, with centralized provisioning and monitoring, is something that all Telcos desire to accomplish for their enterprise customers in the immediate term. The drivers, of course, are rapid service delivery, lower total cost, and simplified and efficient operations. However, delivering such a solution in a fully automated fashion has its challenges.

In this session we will talk about one such large Tier-1 Telco implementation of the SD WAN / Branch Networking solution for its enterprise customers. The session will focus on:

(a) the business and technical requirements of the solution
(b) the components (including OpenStack and other open-source technologies) used to deliver the end to end solution
(c) Challenges encountered and how were they overcome / mitigated.