OpenStack Mitaka Design Summit

This session will illustrate a new network packet logging mechanism for security-group and FWaaS, and how it benefits the admin and tenant users.

The admin and tenant users of enterprise systems need to audit their network activity or investigate the network packet tracking when they see a problem.  Neutron, however, has no such a feature today.

We are developing a new feature that enables network packet logging for security-group and FWaaS.

This session will explain:

• How to setup and use the logging feature.


• What information to log for auditing and trouble shooting from our experiences on our public cloud.

本セッションでは、私たちがNeutronプロジェクトで開発中の、
ネットワークパケットのログ採取の機能についてご紹介します。

エンタープライズ向けシステムのネットワーク運用では、
運用中にフィルタリングの動作を確認できることや
障害発生時にパケットの流れを調査できることが、必須の要件です。
しかし現在、Neutronには、そのための機能が存在しません。

私たちは、これまでのパブリッククラウド運用の経験に基づいて、
セキュリティグループとFirewall as a Service向けの
新しいログ採取の機能を、Neutronプロジェクトで開発しています。

本セッションでは、以下についてご説明します。
・エンタープライズ向けクラウド運用に必要なログとはどういったものか
クラウド管理者とテナント管理者の双方の視点でご説明します。
・新しいログ採取機能を、Neutronでどのように実現するのか、
実際の開発経験に基づいて、具体的にご説明します。

One of benefits of OpenStack is that various systems can be built by combining each component, such server, storage and network, and tuning the parameters.

Thanks to it, a system corresponding to wide range of workloads can be deployed with a multi-hypervisor configuration, mixing VM and baremetal.

But, the actual usecases are rarely in public, and the know-how to deploy the system like tuning parameters is not enough.
Also, even though users in Enterprise desire to realize a high availability system failing over gracefully, some issues are remaining and we need to solve them.

Based on my actual experience, this session introduces requirements from users for multi-hypervisor system capable of the high availability, the know-how to deploy it, and issues to be solved.
These are examples of topics:

- Configuration for Nova and Neutron in a configuration mixing VM and Baremetal.
- Configuration for Cinder multi backend
- Graceful failover in case of hardware/software failure

OpenStackには、サーバ・ストレージ・ネットワークをはじめとした各コンポーネントを
組み合わせることで、用途にあった多種多様なシステムを構築することができる特徴が
あります。
この特徴により、例えば、仮想化環境と物理環境が混在したマルチハイパバイザ環境を
構築でき、ユーザから期待が大きな幅広いワークロードに対応したシステムを実現できます。

しかし、マルチハイパバイザ環境で本番稼働している事例は殆ど公開されておらず、
パラメタのチューニングノウハウなど、システム構築に必要な情報が不足しています。
また、エンタープライズのユーザが求める、障害時でもサービスを停止させない、高可用な
システムを実現するためには課題を解決する必要があります。

本セッションでは、高い可用性を備えたマルチハイパバイザ環境に対するユーザからの
要望、その構築ノウハウ、解決すべき課題を、以下のトピックを中心に実際の構築経験
を踏まえてご紹介します。

- 仮想/物理環境混在構成でのNova/Neutronの設定
- Cinderのマルチバックエンドの設定
- ハードウェア/ソフトウェア障害時の安全な切り替え

OpenStack has been gradually incorporated into the company.
Monitoring system for OpenStack has become important.
This talk will introduce our monitoring system . It uses OSS products.
This monitoring system can monitor both physical server and virtual machine.
When OpenStack creates a virtual machine, setting of monitoring is automatically incorporated into it.
And our monitoring system has function of collecting and analyzing the openstack logs.

・Monitoring for physical server in OpenStack.
・Monitoring for virtual machine using zabbix in each projects.
・The Log collect and analysis using Fluentd Elasticsearch kibana norikra.

OpenStackが成熟し企業にも取り入れられ始めたことにより、
OpenStackを日々正常に運用するための監視システムが重要な位置を占めています。
しかし、OpenStackの監視に何を使うか、どのように監視するかの方法はまだ確立していません。

今回は、OpenStackがOSS製品なので監視システムも全てOSS製品の組み合わせで、
OpenStackを維持するために必要な監視や、クラウド環境の監視で重要な仮想マシンの増減しても自動的に監視に組み込む機能、また、障害対応時に必要なログ収集解析機能を備えた監視システムを構築したのでご紹介いたします。

・物理マシン監視のためのzabbix
・テナント毎の仮想マシン監視のためのzabbix
・複数のzabbixを一元管理するためのhatohol
・Fluentd Elasticsearch kibana norikraを使ったログ収集解析機能

我々はOpenStack上で大人数・同時・リアルタイムゲーム環境をOpenStack上で簡単に実現するためのゲームプラットフォームを開発しました。このゲーム環境はユーザのプレイ状態に応じて動的にクラウド上のリソースが確保され、常に最適なゲーム環境をOpenStack上で実現します。

オンラインゲームの通信の制御はとても難しい分野の一つです。1つは短時間での通信量の変動がとても大きいこと。そしてその通信が状態（non-stateless）を持っているためです。この場合、HeatやCeilometerを使った単純なWEBのオートスケールでは対応出来ません。これを実現するには、通信やそれを制御するアプリケーションの「状態」と連携してクラウド上のリソースをコントロールする手段が必要になります。しかし、このような技術を簡単に実現する方法はまだありません。

そこで我々はOpenStack上のリソースをプログラムリソースとして制御するための基礎技術RACKと(*1)、オープンなゲームプラットフォームであるMonobit-Engineを組み合わせて(*2)、この問題を解決する新しいゲームプラットフォームソフトウェアを開発しました。

本セッションでは、美しい＆楽しいゲームのデモを交えながら、この裏側を支える仕組みと原理について紹介します。

*1) RACK
https://wiki.openstack.org/wiki/RACK
https://github.com/stackforge/rack

*2) Monobit-Engine
http://www.monobitengine.com/

We successfuly developed a massively multiplayer online and realtime game platform on the OpenStack environment.
This platform archives an optimized gaming environment that dynamically controls openstack's resources by state of the gaming.

It's so hard to handle the online game traffic. Because the amount of traffic changes drastically in a short time, and communications are under a "state"(These are non-stateless).
In such case, we can't adopt a simple auto-scaling method with heat and ceilometer.
In order to solve this problem, we need a way of controlling openstack resources which cooperates with state of communications or applications.
But there was not a way to archive it.

We solved this problem by utilizing two technologies.
First one is RACK, the RACK is a way to control openstack's resources as an actual program resources easily(*1).
The another is Monobit-Engine. It's a free online game platform engine(*2).
We implemented RACK to Monobit-Engine, and they make a best "Gaming as a Service" platform.

In this session, we would like to share the structure and the principle of our "Gaming as a Service" platform while viewing a beautiful and funny gaming demo.

*1) RACK
https://wiki.openstack.org/wiki/RACK
https://github.com/stackforge/rack

*2) Monobit-Engine
http://www.monobitengine.com/

データセンター事業者が低コスト、かつ高性能なプライベートOpenStack環境を提供するためには、以下のような要件が必要です。

- 可能な限りシンプルな構成
- 汎用的なハードウェア
- 迅速なデプロイが可能なツール
- 高集積
- 十分なIO性能とネットワーク帯域

これを実現するために、私たちはハイパーコンバージドインフラとしてのOpenStackをOpenSouceで構成する為の検証を実施しました。

これを実現するためにわれわれが利用したアーキテクチャは以下の通りです。

- Network
- 40G/56G スイッチ ＆ NIC
- VXLAN offload
- DPDK

- Storage
- PCI Express SSD
- Ceph RDMA (Remote Direct Memory Access)

- Deploy
- Ubuntu Juju/MAAS と charm bundle

Many Datacenter providers are looking for proven and open-source hyper converged OpenStack solution so that they can provide simple, low-cost, high-performance and rapid-deployment OpenStack environment. To archive this goal, the followings topics become key considerations.
- Infrastructure should be simple as much as possible.
- Using commodity hardware and open source software.
- Using tool to help rapid and ease of deployment.
- High density.
- Secure performance and network bandwidth.

To address this challengs, in this session we will share the best practices and lesson learns about the idea to use OpenStack as hyper converged infrastructure with high standard technologies.
The key concept of this PoC is to evaluate OpenStack as hyper converged infrastructure with following key technologies.

- Network
- 40G/56G physical network
- DPDK
- VXLAN offload capability

- Storage
- PCI Express SSD
- Ceph RDMA (Remote Direct Memory Access)

- Deploy
- Ubuntu Juju/MAAS and publish charm bundle as executable whitepaper.

NTT West provides fixed communication services (such as fixed-line telephone and FTTH) in 30 prefectures in western Japan.
”FLET'S Hikari" is the name of FTTH service that NTT-West provides.
The services NTT-West provide is required to be "stable" and "high quality".
Our business challenge is the cost(CAPEX/OPEX) reduction.
We, The R&D center at NTT-West works to restructure the data center infrastructure of FLET'S services with virtual infrastructure technologies, aiming for cost reduction.
In order to overcome these challenge, we need to be further advanced our server infrastructure.

We have examined the OpenStack(Kiro)-based server infrastructure with general-purpose IA (Intel Architecture) server from six months ago, and are faced with several problems related to Neutron in our examine.
We will introduce these at our session.

First, we introduce the current situation and the next challenges about our server infrastructure, and the functions and performance requirements that require our next-generation server infrastructure in order to overcome the current challenges.

Second, in terms of functionality.
Our Service works on "dual stack" (IPv4/v6) and we need IPv6 implementation.
IPv4 exhaustion is becoming all the more a serious problem, due to the appearance of container technology and the advance of virtualization.
Neutron should be ready for IPv6 to provide functions such LBaaS and FWaaS.
We need UDP implementation on LBaaS.
LBaaS is not able to handle UDP traffic at the present moment.
There are many UDP-based applications (such as SIP and Radius) in our services.

Last, in terms of performance.
The transmission rate of network nodes is not enough for the SLA of IP-Phone (or fixed-line telephone) services.

For this evaluation and report, we've been cooperating with Canonical, VirtualTech Japan and NTT Software Innovation Center.
We show the details of the above, and expect to make progress on these studies through discussion with developers and contributors.

NTT西日本では日本国内の西日本エリア30府県で固定通信サービスを展開している。フレッツはブロードバンドIPアクセス、映像、電話等のサービスを提供し、そのバックグラウンドで大規模なインフラを運営している。サービスの提供にあたっては安定的かつ高品質なサービス提供が求められる一方、CAPEX/OPEXの削減が経営課題として常に掲げられている。

NTT西日本研究開発センタでは、フレッツサービスを提供するサーバ基盤の抜本的なCAPEX/OPEX削減を目指し、OpenStackに代表されるクラウド基盤技術をベースとしたサーバインフラへの移行に向けて検討を進め、調査・開発用トライアル基盤を構築して検証およびトライアルを開始した。この営みによって、（コミュニティの中では既に認識されている内容ではあるが）当方において主にNeutronの機能・性能面の課題に直面している。本セッションにおいては、これまでの検討ならびに評価によって得られた知見を紹介したい。

まず、NTT西日本におけるサーバ基盤の現状およびそれが抱える課題と、現在の課題を解決するためにOpenStackベースのサーバ基盤へ切り替えるに当たり必要とする機能・性能要件について紹介する。

次に機能面について、当方における喫緊の課題としてIPv6対応が挙げられる。仮想化やコンテナ技術の利用が進む中でIPv4アドレスの枯渇は今後ますます全世界的にも重大な課題であると考えられる。しかしLBaaSやFWaaSなどNeutronの各機能においてはIPv6対応はIPv4と同等に扱えるには至っておらず早期の対応が求められる。また、LBaaSに関して言えば、現状はIPv4においてもUDPは対象外となっているが、通信事業者網ではIP電話やユーザ認証等の機能でSIPやRadiusといったUDP通信が必要不可欠であり、負荷分散制御のUDPへの対応が望まれる。
本セッションでは上記を含めた検討・評価結果について報告する。

最後に性能面では、OVS(L2)およびNeutron(L3)のパケット転送性能が課題である。当方で実施した「コミュニティ版OpenStack(Kilo)＆汎用IAサーバ機＆ToR-SW」のみで構成された（いわゆる３台構成をベースとした）評価環境における性能検証結果を元に性能面における課題を改めて会場において共通認識化するとともに、これらに対する現時点での対策案などについて紹介・議論したい。

本セッションでの課題提起を通じ、Neutronの機能充足に向けてデベロッパ・コントリビュータの方々の協力を得ながらエンドユーザの立場から早期の実現化を推し進めていきたい。

It is said that OpenStack deployment in Japan is lagged behind compared to US. But there are web service companies and providers who has been driving their businesses by leveraging OpenStack for quite some time. In this session, Izumi Miki, an executive editor of IT Media, will talk about past, present and future of OpenStack in Japan, welcoming the guests from Japanese super users, Cyber Agend and DeNA.

What’s ready for production and what’s not? What can you leverage and what should you avoid? One of the top writers will dig into the realities of deployments today in Japan.

OpenStackは日本においてどんな企業でどのように使われているのか、そして、これからどのように普及していくのか、またはしないのか。本講演では、＠ITの三木泉氏が、メディアという立場から俯瞰した日本のOpenStackクラウドの状況、過去～現在～未来、をお話するとともに、すでにOpenStackを使っているユーザーや現在検討中のユーザーをゲストに招いて事例紹介とリアルな声をお届けします。

事例紹介のゲストとしては、動きの速いウェブサービス業界で事業をドライブするITインフラ構築にOpenStackクラウドを活用・検討しているサイバーエージェントとディーエヌエーのリードエンジニアの例をご紹介します。OpenStackを導入した背景、メリット、障害や課題などについてSDNやセキュリティなど、導入時に考慮した技術にも触れながら、「実際のところどうなのか」をお話します。

Openstack Notifications can play a big role in extending capabilities of the Openstack. Most of the actions in Openstack which manipulate the system state generate notifications which is posted to the messaging component (e.g. RabbitMQ) and can be consumed by any service outside the Openstack. Some of these notifications are used by Ceilometer to provide chargeback related data. 

In this talk we examine some use cases where one can tap into OpenStack notifications layer and build real world use cases that are so often needed by enterprise IT. 

Specifically, we will cover the following: 

• High level overview of Openstack notifications
• Configuring Openstack services to enable notifications
• Live demo demonstrating tapping in to notifications related to Glance image creation, VM creation, Network creation etc.
• Auditing/Compliance solutions -- a few examples.
• Detect unauthorized Glance images in the system
• Inspecting newly created Glance image to detect infected OS images
• Auditing network access whenever a VM becomes externally accessible
• Running network access tools as soon as a new VM becomes available on the network
• Activity Feed of various Openstack activities which helps Admins to monitor their private cloud.

OpenStack and Hadoop ecosystems have been enjoying parallel amounts of rapid growth and adoption over the last few years. Project Sahara was established in the OpenStack community to drive the overall “Data processing on OpenStack” theme, while Hadoop-focused companies such as Cloudera and Hortonworks have been offering their vision of management frameworks and deployment models around Hadoop.

At Mirantis, we noticed that many people got quickly confused about different options for adopting Hadoop as a technology. In this talk, we’ll make an effort to address part of this confusion and set the stage for further deep-dive conversations into how OpenStack can actually help in adopting Hadoop in a particular organization. As always, we’ll keep things as vendor-neutral as possible. 

Specifically, we’ll talk about the following:

• An overview and roadmap of the Hadoop ecosystem -- components like YARN, Hive, HBase, and others that constitute a working Big Data solution


• Management frameworks and deployment models offered by different vendors such as Cloudera and Hortonworks


• Typical Hadoop logical and physical architecture deployment


• Architecting OpenStack for Hadoop workloads, including:
  
  
  
  • Picking the right hardware and sizing it properly
  
  
  • Doing Storage right (HDFS, Ceph, Swift, direct block device mapping?)
  
  
  • Doing Compute right (KVM or Baremetal? Making scheduling work)
  
  
  • Doing Networking right (Just Neutron, or do we need full-featured SDN?)
  
  
  • Leveraging extras that OpenStack has to offer (multi-tenancy, NUMA, CPU pinning)
  
  
  
  

By attending this presentation, you will gain a solid real-world understanding of the benefits and ways to build out a working Hadoop/Big Data solution on OpenStack.

If you have a service and want a UI for it, this session is for you! Come to this session to learn what all the fuss is all about. Learn how to write a dashboard plugin for your custom service as well as add visual enhancements to make your dashboard stand out.

Horizon is the official OpenStack dashboard providing access to your services via the web UI. One of its selling feature is its robust plugin mechanism. We will explore what you can do with our plugin model as well as discuss all of the options available to you for extensions. Furthermore, we will explain how the new client-side work will fit into this model and what best practices you should follow.

Finally, we will talk about the OpenStack services roadmap and plans we have for supporting it and where you help us make a difference by contributing! 

The OpenStack Brand has tremendous value—and our opportunity is to protect and enhance the brand through OpenStack Day events worldwide and user groups. Join this session to see new logos and graphic assets available to groups and events, how to get these assets and use them, and what additional resources and funding are available to branded groups and events in 2016. If you lead a user group or sponsor an OpenStack event, this session will help you make the most of our resources.

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.