# Daily Note 07/08/2020
###### tags: `Daily Notes` , `O-RAN` , `Acumos`
## Name : Christofel Rio Goenawan
## University : Bandung Institute of Technology (ITB)

---

## Schedule:
1. Study Detailed Works of Routing Manager and Subscription Manager.
2. Study Detailed Works of Distributed Tracing Using OpenTracing in RIC.
3. Continue to try installing Acumos AI in NTUST Server.

## Outcome :
1. Explained Detailed Works of Routing Manager and Subscription Manager Case.
2. Explained Detailed Architectures of Distributed Tracing Using OpenTracing in RIC.
3. Still couldn't find server name that asked by command when try to set up needed services in NTUST server.

## Further Plan :
- Continue to deploy Acumos AIO in NTUST server
- Study more detailed about AIO Installation in Kubernets

---

## Daily Log

### 1.Study Detailed Works of Routing Manager and Subscription Manager. <mark>(9.00)</mark>
- Study more detail explanation in [Documentation](https://www.o-ran.org/s/ORAN-WG3E2GAP-v0100.docx ) and other sources.

### 2.Study Detailed Works of Distributed Tracing Using OpenTracing in RIC. <mark>()</mark>
- Study more detail explanation in [Reference](https://medium.com/opentracing/towards-turnkey-distributed-tracing-5f4297d1736) and other sources.

### 3.Continue to try deploying Acumos AIO in NTUST server. <mark>()</mark>
- Continue to try to deploy Acumos AIO in NTUST server using Prep- Deploy Process based one previous [study notes](https://hackmd.io/@christofel04/TEEP_Daily_Notes_10_7_2020).

---

## Report

### 1. Routing Manager and Subscribe Manager

>In this note Writer use [Documentation](https://www.o-ran.org/s/ORAN-WG3E2SM-v0100.docx) and [Ferlinda's Notes](https://hackmd.io/3b9cWIIDR9qjN2EVdS6HbQ?view) as study sources.

From Ferlinda's notes , we will use cases communication between Near-RT RIC to the gNB/eNB.

#### Initial Subscription

In initial subscription, the step can be explained as below.
- xApp sends MID and payload of **RICSubscriptionRequest**.
- Subscription Manager then **forward it to E2 Termination** and sending it to gNB/eNB through E2.
- Request and Response are send through **RMR**.

The detailed diagram can be seen as below.


#### Subscription Delete

In subscription delete, the step can be explained as below.
- xApp sends MID and payload of **RICSubscriptionRequest**.
- Subscription Manager then **forward it to E2 Termination** and sending it to gNB/eNB through E2.
- Request and Response are send through **RMR**.

The detailed diagram can be seen as below.


#### Subscription Merge

In subscription merge , Subscription Manager **generate its own RIC Subscription response**.
Request and Response are send through **RMR**

The detailed diagram can be seen as below.


#### Subscription Merge Delete

In subscription merge delete, Subscription Manager **generate its own RIC Subscription response**.
Request and Response are send through **RMR**

The detailed diagram can be seen as below.


---

### 2. Distributed Tracing Using OpenTracing in RIC

>In this note Writer use [Documentation](https://www.o-ran.org/s/ORAN-WG3E2SM-v0100.docx), [Reference](https://medium.com/opentracing/towards-turnkey-distributed-tracing-5f4297d1736) and [Ferlinda's Notes](https://hackmd.io/3b9cWIIDR9qjN2EVdS6HbQ?view) as study sources.

#### What is Open Tracing ?

OpenTracing is an **open distributed tracing standard for applications and OSS packages, it has no binding to any particular tracing vendor**.

:::info
Open Tracing by can be defined as below.

**1. Ben Sigelman** stated: per-process logging and metric monitoring have their place, but neither can reconstruct the elaborate journeys that transactions take as they propagate across a distributed system. Distributed traces **are** these journeys.

**2. Masroor Hasan** stated: Distributed tracing enables capturing requests and building a view of the entire chain of calls made all the way from user requests to interactions between hundreds of services. It also enables instrumentation of application latency (how long each request took), tracking the lifecycle of network calls (HTTP, RPC, etc) and also identify performance issues by getting visibility on bottlenecks.
:::

#### Open Tracing Specification

From documentation , Open Tracing Specification can be seen as below.


#### Open Tracing Architecture

From documentation , Open Tracing Architectures can be seen as below.


#### What is Jaeger?

Jaeger is an **open-source distributed tracing system that implements the OpenTracing specification mentioned above**. Jaeger includes components to **store, visualize and filter traces**.

### Jaeger Architecture

The Jaeger Architecture can be seen as below.


#### Distributed Tracing Infrastructure with Jaeger on Kubernetes

RIC was build on Kubernetes cluster.
In the [yesterday's note ](https://hackmd.io/@christofel04/TEEP_Daily_Notes_06_8_2020) we can see how it involves HTTP request to communicate with each services.

The simple RIC Clusters scheme can be seen as below.


:::info
**Next Writer Will Study More About Tracing Using Jaeger**
:::

---

### 3. Continue to try deploying Acumos AIO in NTUST server

>This deployment is continuation from [yesterday's notes]( https://hackmd.io/@christofel04/TEEP_Daily_Notes_30_7_2020 ).
In this note Writer use [Previous Notes](https://hackmd.io/@christofel04/TEEP_Daily_Notes_10_7_2020) as study sources.

Then Writer try to install needed services in server for Acumos AIO.

Writer use the next command as below.

bash system-integration/AIO/setup_prereqs.sh k8s ee705-7-ip113 $USER openshift 2>&1 | tee aio_prep.log


But when Writer use the command , the command ask for server's name that Writer don't know.

:::warning
After I discussed with Kevin, I try to find the server's name by command below.

But the command also ask for server's name
:::

:::info
**Next Writer Will Continue to Find the Server's Name For the Command**
:::

---



## Reference
1. https://www.o-ran.org/s/ORAN-WG3E2GAP-v0100.docx
2. https://docs.o-ran-sc.org/projects/o-ran-sc-ric-plt-jaegeradapter/en/latest/overview.html
3. https://medium.com/opentracing/towards-turnkey-distributed-tracing-5f4297d1736