---
# System prepended metadata

title: Daily Note 11/08/2020
tags: [O-RAN, Daily Notes, Acumos]

---

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


---

## Schedule:
1. Study Detailed Works of VES Agents in Near- RT RIC.
2. Study Detailed Works of RIC Alarm systems.
3. Try Solve Open Shift Problem for Acumos AI


## Outcome : 
1. Explained Detailed Architectures of Sample Demo of Open Tracing using OpenTracing.
2. Explained Detailed Works of Near-RT RIC Internal Statistics Collections.
3. Solve Open Shift Cluster Issues in NTUST Server for Acumos AI.


## 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 VES Agent in Near- RT RIC. <mark>(9.00)</mark>
- Study more detail explanation in [Documentation](https://wiki.onap.org/display/DW/High+Volume+VES+Collector ) and other sources.

### 2.Study Detailed Works of RIC Alarm systems. <mark>(10.00)</mark>
- Study more detail explanation in [Documentation](https://wiki.o-ran-sc.org/display/RICP/RIC+Alarm+System) and other sources.


### 3.Try Solve Open Shift Problem for Acumos AI <mark>(15.00)</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. VES Agents

>In this note Writer use [Documentation](https://wiki.onap.org/display/DW/High+Volume+VES+Collector)  and [Ferlinda's Notes](https://hackmd.io/rchtITC_RgaMLpKDhC00Yg?view) as study sources.

#### What is VES Agent ?
From documentation, VES Agent is **a service acting as a bridge between Prometheus and ONAP’s VES Collector**. It act as a **Webhook** to Alertmanager, receives alerts, transform them to VES fault events and send them to VES collector

VES Agent periodically :
1. **Query configured metrics from prometheus**.
2.  **Map them into VES measurements event batch**.
3.  **Then send them to VES collector**.

#### VES Agent Architectures

From Documentation the detailed architectures of VES Agent can be seen as below.

![](https://i.imgur.com/ShLhmYr.png)

#### VES Agent Mapping Rules

From Ferlinda's notes, VES Agent mapping rules can be seen as below.

![](https://i.imgur.com/Fnn3Eq3.png)




---

### 2. RIC Alarm Systems

>In this note Writer use [Documentation](https://wiki.o-ran-sc.org/display/RICP/RIC+Alarm+System) and [Ferlinda's Notes](https://hackmd.io/rchtITC_RgaMLpKDhC00Yg?view) as study sources.

#### RIC Alarm Components

RIC Alarm Systems consisted of 2 components as below.

1. **Alarm Adapter**
2. **Application Library Interfaces**

The detailed can be seen as below.

##### 1. Alarm Adapter

- Alarm Adapter  is responsible for **managing alarm situations in RIC cluster and interfacing** with Northbound applications such as Prometheus AlertManager to post the alarms as alerts.
- It contains **Alert Manager** that  :
  - Post the alarms as alerts.
  - Takes care of deduplicating, silencing and inhibition (suppressing) of alerts, and routing them to the VESAgent, which, in turn, takes care of converting alerts to faults and sending them to ONAP as VES events.

##### 2. Application Library Interfaces

- Application Library Interfaces provides a simple interface for RIC applications (both platform application and xApps) to raise, clear and re-raise. 
- The **Alarm Library** interacts with the **AlarmAdapter** via **RMR interface**.

#### Alarm Library

##### Initializations

A new alarm instance is created with InitAlarm()-function. ManagedObject (mo) and Application (ap) identities are given as a parameter

##### Alarm Context and Format

From documentation , Alarm Library Context and Format can be seen as below.

1. **SpecificProblem***: Problem that is the cause of the alarm.
2. **PerceivedSeverity**: The severity of the alarm, see above for possible values.
3. **ManagedObjectId**: The name of the managed object that is the cause of the fault.
4. **ApplicationId**: The name of the process raised the alarm.
5. **AdditionalInfo**: Additional information given by the application
6. **IdentifyingInfo**: Identifying additional information, which is part of alarm identity.

:::info
**ManagedObjectId (mo), SpecificProblem (sp), ApplicationId (ap) and IdentifyingInfo (IdentifyingInfo)** make up the **identity of the alarm**. 
:::

:::info
Addressing the same alarm instance in a **clear()** or **reraise()** call is done by making sure that all four values are the **same is in the original raise / reraise call**.
:::

##### Alarm APIs

From documentation there are 4 kind of Alarm APIs as below.

1. **Raise**: Raises the alarm instance given as a parameter
2. **Clear**: Clears the alarm instance given as a parameter, if it the alarm active
3. **Reraise**: Attempts to re-raise the alarm instance given as a parameter
4. **ClearAll**: Clears all alarms matching moId and appId given as parameters

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

#### Example on how to use the API
![](https://i.imgur.com/WEFh73z.png)

#### Example VES event
![](https://i.imgur.com/F4u56cX.png)



---

### 3. Try Solve Open Shift Problem for Acumos AI

>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.

After checking the Open Shift cluster installation , there are issues when setting cluster up in Open Shift.

:::danger
In Writer's installation the setting freeze after installing kubeflow as below.

![](https://i.imgur.com/27U2fYv.png)

But after look at [reference](https://github.com/openshift/origin/issues/21253) , it should end up showing Open Shift user account and server as below..

![](https://i.imgur.com/WoHOBzT.png)
:::

:::warning
After Writer search in internet and from reference it found out this issue **often happens for CentOS with Open Shift veruson 3.11 like Writer's**.
:::

:::info
After search in internet , the issue **can be solve by configure the firewall ID in server**. The configuration can be [seen here]().
:::

:::info
**Next Writer Will Try to Solve the Privileged User Issues**
:::

---



## Reference
1. https://github.com/nokia/ONAP-VESPA
2. https://docs.o-ran-sc.org/projects/o-ran-sc-ric-plt-vespamgr/en/latest/overview.html
3. https://wiki.o-ran-sc.org/display/RICP/RIC+Alarm+System
4. https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=3604819
5. https://wiki.o-ran-sc.org/display/RICNR/Release+B
6. https://wiki.o-ran-sc.org/display/OAM/OAM+Architecture
7. https://wiki.onap.org/display/DW/High+Volume+VES+Collector
8. https://wiki.onap.org/display/DW/Architecture
9. https://prometheus.io/docs/introduction/overview/
10. https://promcon.io/2019-munich/talks/prometheus-and-jaeger-a-match-made-in-heaven/

