Introduction of Okinawa Open Laboratory, used in the session of iPOP2015

1. Okinawa Open Laboratory 1
Introduction of Okinawa Open
Laboratory and it’s activities
Apr. 21, 2015
NEC Corporation
Takashi Torii

2. Okinawa Open Laboratory 2
Who I am?
 Platform Service Division in NEC, and
works about business of OpenStack
and Cloud
 Japan OpenStack User Group Board
Member
 Chief of Testbed WG, Okinawa Open
Laboratory

3. Okinawa Open Laboratory 3
https://www.openstack.org/summit/tokyo-2015/

4. Okinawa Open Laboratory 4
Agenda
 Our Motivation
 OOL Testbed Architecture
 Technology
 Activities
 Future Works

5. Okinawa Open Laboratory 5
Our Motivation

6. Okinawa Open Laboratory 6
Gartner Hype Cycle for Emerging Technologies
Source: Gartner (August 2014)

7. Okinawa Open Laboratory 7
Lifecycle Innovation

8. Okinawa Open Laboratory 8
How to make Innovations?

9. Okinawa Open Laboratory 9
Key Success Factor of Open Innovation
Open
Fast
Collaboration

10. Okinawa Open Laboratory 10
Activity Model
 OOL connects OSS development communities and market via use
cases and reference models to expand user base of next-
generation ICT platform in cooperation with members and
partners
 OOL Value Chain: Use Case  Verification  Ref. Model  Promotion
 PDCA Cycles: OOL  Market, OOL  OSS Development Communities
OSS Development Communities
Develop
-ment
Use
Case
Verifica
-tion
Ref.
Model
Promo
-tion
Issues/
Needs
Application/
Use
Okinawa Open Laboratory
(OOL)
Market/Users
Testbed
<Partners>
• Standardization/
Promotion Organization
- Linux Foundation
- OpenStack Foundation
- Open Networking
Foundation
- Japan OpenStack
User Group
- SDN Japan Executive
Committee
...
<Members>
• Widely from
- Industries
- Academia
• From Worldwide
- Japan
- Asian Countries
...
User Base
Joint Activity with OOL Collaboration with OOL

11. Okinawa Open Laboratory 11
Working Groups & Projects
 Working groups (WG) & Projects (PJ)
 WG: Improve efficiency of activities by showing activity policies and
consolidation of laboratory assets and resources
 PJ: Promote member participation, diversification and expansion of
member activities
 Operation process: Organize processes for formation approval and
progress management
<Operation Process>
インタークラウドPJ
インタークラウドPJ
Testbed WG
Education WG Education and Training PJ
International Conference PJ
Testbed
Platform Enhancement PJ
Testbed
Wide Area Expansion PJ
Testbed
Management & Operation PJ
PJ Formation
Approval Process
PJ Progress
Management Process

12. Okinawa Open Laboratory 12
Architecture

13. Okinawa Open Laboratory 13
Key Features
Online, Remote
On-Demand
Bare-metal
Zero-Touch

14. Okinawa Open Laboratory 14
Concept of OOL Testbed
server
SDN switch
OpenStack
Your Site
1. Choice!
Your
Cloud
2. Deploy!
Your APP
Backup &
Restore
Your
System
3. Run!
 Common platform developed, managed and operated by OOL for
OOL and Members activities
 Evaluation of new technologies
 Conformance, interoperability and performance testing
 Validation of SDN/Cloud technology integration, uses cases and reference models
(PoC: Proof of Concept)
 Always-on showcases and demonstration
 Hands-on training
 Easy to use by OpenStack with SDN as a Service (OS3)

15. Okinawa Open Laboratory 15
Testbed Service
 Offer member service of using bare metal resources in flexible topology online
 Possible to construct flexible topology by means of patch panel using OpenFlow
 Automatic configuration of environment that combines OpenStack and SDN

16. Okinawa Open Laboratory 16
How it works
16
1) Fully online
Site
(Servers)
Express 5800
(Tester)
IXIA
(Switches)
Centec V350
PF5240F
Riava
Your Site
Internet
BBA

17. Okinawa Open Laboratory 17
How it works
17
2) Resource and Network Topology can be designed

18. Okinawa Open Laboratory 18
How it works
18
3) Auto-deployment of OpenStack environment

19. Okinawa Open Laboratory 19
How it works
19
4) Full system backup and restore
Backup
Restore

20. Okinawa Open Laboratory 20
Technology

21. Okinawa Open Laboratory 21
Leaf-Spine Network
OF-Patch: OpenFlow-based Patch Panel
Spine x 4
Leaf x 48
Patches max 1920 port
SDN Application to control bare-metal connectivity
like patch panel
Multi switch configuration as Leaf-Spine GUI Proto type

22. Okinawa Open Laboratory 22
OF-Patch
OF-Patch Manager
User
OF-Patch GUI
OpenFlow Controller (Ryu)
OFS
Host
1
Host
2
Host
3
Connect ports by Flow
Other
Software
REST API

23. Okinawa Open Laboratory 23
Activities using
Testbed

24. Okinawa Open Laboratory 24
① Put load on virtual machines (VMs) in Okinawa from US
② Narrow down between US-Okinawa wide area network band frequencies
③ Wide area network monitoring alarms, adding VM in Tokyo
④ LB is newly activated in US, dispersing load between Okinawa and Tokyo
 Wide area automated scale control (Demonstrated at Interop Tokyo 2014)
Distributed Load Balancing
USA
Okinawa
Clients
Tokyo
③ VM is
automatically added
by wide area
network monitoring
④ LB is newly
activated
④ Does not go through
when LB in US is
activated
Wide area
network
monitoring
① Put load on VMs in
Okinawa from US
② Narrow down network
band frequencies
between US-Okinawa

25. Okinawa Open Laboratory 25
 Test tool for certificating OpenFlow Specification
 Running on the Testbed, and publish the result at
https://github.com/oolorg/ool-ryu-certification
Ryu Certification
http://osrg.github.io/ryu-book/en/html/switch_test_tool.html#test-execution-image

26. Okinawa Open Laboratory 26
Cloud Native Application Framework: RACK
options
(input)ライブラリ
プログラム compile
psコマンド
OS
middleware
libraries
source
表示内容
表示範囲
出力形式
option1
option2
option3
launch
openstack
shared memory/pipe
signal
filesystem
process process
VM
Template
executable
binary
process
forkfork
OpenStack Native Application with RACK

27. Okinawa Open Laboratory 27
RACK Test Suite Environment
OS Install
servers
10 x compute node
AMD/Seamicro SM15K
Ansible
CloudShell RackDeploy
Driver
OpenStack RACK
ServerAuto-deploy RACK environment
Auto-deployment
of RACK

28. Okinawa Open Laboratory 28
OpenDaylight Use Case
 In enterprise use case
 Private cloud is build by OpenStack
 Office user would like to connect virtual machine in private cloud by local
network
 All network is managed by single OpenDaylight controller
Private Cloud
Layer2 Switch
Office
vBridgeTenant 1
Tenant 2
VM
VM
OFS

29. Okinawa Open Laboratory 29
Future works

30. Okinawa Open Laboratory 30
Future Works
NFV Framework
White-box
Use cases

31. Okinawa Open Laboratory
31
Questions?