https://github.com/opencord/xos

1. XOS in OpenCORD
Mobile Convergence LAB,
Department of Computer Engineering,
Kyung Hee University.
Sangyun Han

2. Interests of Enterprise
2

3. Core Components
OpenStack
ONOS
XOS
OCP
3

4. Domain Services
 R-CORD
 vOLT, vSG, vRouter…
 E-CORD
 vCE, vOAM, vFirewall…
 M-CORD
 vBBU, vSGW, vPGW…
4

5. CORD project on Github
5

6. List of OpenCORD projects
 platform-install / service-profile / CORD
 XOS
 MaaS
 AAA / Mcast / IGMP / OLT / VTN / CordConfig
 Voltha
 OpenStack / vRouter / vSG / vMME / vBBU / onos-service [only xos interface ]
6
OLT : Optical Line Terminal
IGMP(Internet Group Message Protocol)
OLT access management

7. platform-install
 Contains Ansible playbooks for installing and configuring software components on a
CORD POD : OpenStack, ONOS, and XOS.
 Ansible
 application, library, configuration 배포 자동화 툴
 Agent 기반이 아닌 SSH 기반으로 SSH 연결을 통해 코드를 전송하고, 스크립트를 실행
 ansible playbook으로 관리
 This is a radically simple configuration management, deployment, and ad-hoc task execution tool. It
supports a wide variety of distributions, requires no software installed on managed machines, and
users can get going in minutes. Extension modules can be written in any language.
7

8. service-profile
 Contains service profiles which configures XOS with a graph of services to be
instantiated
 These configurations automate the creation of containers, loading things into the
onboarding synchronizer, and starting XOS.
 스크립트 파일 및 yaml 파일로 이뤄진 configuration 파일 포함
 YAML 이란?
 XML, C, Python, Perl, RFC2822에서 정의된 e-mail 양식에서 개념을 얻어 만들어진 ‘사람이 쉽게 읽을 수 있는
데이터 직렬화 양식‘
 가벼운 마크업 언어
 모든 데이터를 리스트, 해쉬, 스칼라 데이터의 조합으로 표현 가능
 Understandable, Readable 8

9. OpenCORD
 platform-install / service-profile / CORD
 XOS
 MaaS
 AAA / Mcast / IGMP / OLT / VTN / CordConfig
 Voltha
 OpenStack / vRouter / vSG / vMME / vBBU / onos-service [only xos interface ]
9
OLT : Optical Line Terminal
IGMP(Internet Group Message Protocol)
OLT access management
MaaS(Metal as a Service)
OpenCORD 는 Canonical의 MaaS 솔루션을 활용,
PXE boot 제공
Metal-as-a-Service is designed to help facilitate
and automate the deployment and dynamic
provisioning.

10. Bare metal provisioning flow
 1. Install and provisioning MAAS and other utilities on one compute node that will have the
head node role
 2. Boot the other component in a CORD POD (switches and other compute nodes)
 3. Once other components are operational perform some additional provisioning to prepare
them to be part of a CORD POD and to be compliant with best practices of a CORD POD
10
Compute node
(Head node)
MAAS
Utilities
Boot
Switches
other compute node
Be part of a CORD POD

11. CORD
 CORD’s open reference implementation
 POD hardware specifications
 A software platform that implements service-agnostic software infrastructure
 A few sample service implementations that can be readily deployed onto CORD
PODs
 A deployment automation framework that simplifies the installation of the platform
layers 11

12. CORD
 POD using Metal-as-a-Service, installs Ubuntu LTS 14.04 on the computer
nodes and Open Networking Linux on the white-box switches, and sets up
Docker, Maven, and Glance image repositories. And finally XOS starts up
12POD : an application deployment platform

13. OpenCORD
 platform-install / service-profile / CORD
 XOS
 MaaS
 AAA / Mcast / IGMP / OLT / VTN / CordConfig
 Voltha
 OpenStack / vRouter / vSG / vMME / vBBU / onos-service [only xos interface ]
13
OLT : Optical Line Terminal
IGMP(Internet Group Message Protocol)
OLT access management
.

14. XOS
 3 Core services (build using separate dockerfiles)
 Database backend (postgres)
 Webserver front end (Django)
 Synchronizer daemon (interacting with the OpenStack backend)
 Note that earlier versions of XOS referred to the “Synchronizer” as the “Observer”.
 데이터 모델의 상태를 설정하려면 Synchronizer가 필요
 Synchronizer는 데이터 모델의 변경을 기다렸다가 동기화해주고 트랜잭션 유지
14

15. XOS interface [OpenStack / vRouter / vSG / vMME / vBBU / onos-
service]
 {project}-onboard.yaml
 models.py
 admin.py
 tosca/resources
 templates
 api/service
 synchronizer
15

16. 16

17. Block diagram of the XOS software structure
17

18. CORD controller
18

19. XOS Internals : assembling a service
19

20. Synchronizer and State Management
20

21. End-to-End Control Flow
21

22. Core Models
22

23. From native to legacy
23

24. TOSCA (1)
 Topology and Orchestration Specification for Cloud Applications (TOSCA)
 클라우드 컴퓨팅의 상업화로 테넌트 환경 및 앱에 대한 관리가 필요
 OASIS open cloud standard language
 Standardize how we describe software application and everything that is required for them to
run in the cloud.
 Enabling portability and automated management across cloud providers regardless of
underlying platform or infrastructure.
24
OASIS (Organization for the Advancement of Structured Information Standards)

25. TOSCA (2)
 The structure of an IT Service(its topology model)
 How to orchestrate operational behavior
 service template – model based approach
 Nodes & Relationships
 Node : infrastructure component
 Relationship : how nodes are connected
to one another
25

26. [참고] YAML vs YANG
26