---
# System prepended metadata

title: Daily Note 21/08/2020
tags: [Daily Notes, Acumos]

---

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


---

## Schedule:
1. Study Detailed Works of Acumos AI Boreas Release Platforms Flow from Documentation.
2. Continue Study Detailed Components of Acumos AI Boreas Release from Documentation.
3. Try to Solve Connection Issue in Nexus Installation for Acumos AI.


## Outcome : 



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



---

## Daily Log


### 1.Study Detailed Works of Acumos AI Boreas Release Component Interactions from Documentation. <mark>(9.00)</mark>
- Study more detail explanation in [Documentation](https://docs.acumos.org/en/boreas/) and other sources.


### 2.Study Detailed Works of Acumos AI Boreas Release's Portal Marketplace from Documentation. <mark>(12.00)</mark>
- Study more detail explanation in [Documentation](https://docs.acumos.org/en/boreas/submodules/portal-marketplace/docs/developer-guide.html) and other sources.


### 3. Try to Solve Connection Issue in Nexus Installation for Acumos AI.<mark>(14.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).
- Try to solve Connection Issue in Nexus Installation for Acumos AI based one previous [study notes](https://hackmd.io/@christofel04/TEEP_Daily_Notes_18_8_2020).




---

## Report


### 1. Acumos AI Boreas Release Component Interactions

>In this note Writer use [Documentation](https://docs.acumos.org/en/boreas/) as reference.

#### 1. Acumos AI Boreas Releases Components
From documentation , Acumos AI Boreas Releases components can be explained as below.

1. **Core Component**
   - Components that are **developed/packaged by the Acumos project, and provide/enable core functions** of the Acumos platform as a service.
   - Example Components: **Azure, Kubernetes , OpenStack , ELK , Metric Beat**.
2. **Supplemental Component**
   - Components that are **integrated from upstream projects, in some cases packaged as Acumos images, and provide supplemental/optional support functions** for the platform. 
   - These functions may be **provided by other components, or omitted from the platform deployment**.
   - Example Components: **Azure, Kubernetes , OpenStack , ELK , Metric Beat**.
3. **Platform Dependency** 
   - Upstream components that are required to **support key platform functions such as relational database and docker image creation**. 
4. **External Dependency**
   - External systems/services that are **required for the related Acumos function to be fully usable**.

:::warning
The Detailed Components List can be seen in yesterday's notes , that divided into 2 part as below.
1. [**Part One**](https://hackmd.io/@christofel04/TEEP_Daily_Notes_19_8_2020) : Core Components , Model Execution Components and Third Party Services.
2. [**Part Two**](https://hackmd.io/@christofel04/TEEP_Daily_Notes_20_8_2020) : Supporting Libraries, Model Client Libraries , Models Runner.
:::

#### 2. Acumos AI Boreas Release Component Interactions Scheme

The following diagram shows the major dependencies among components of the Acumos architecture, and with external actors. The arrow represent dependency, e.g. upon APIs, user interfaces, etc. The arrows are directed at the provider of the dependency. Some dependencies are so common that they aren’t shown directly, for diagram clarity. These include:

- Collection of logs from all components
- Dependency upon the Common Data Service (CDS)

From documentation , the scheme can be seen as below.

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

:::info
**Next , Writer Will Study More About Acumos AI Boreas Release's Interfaces and APIs**
:::

---

### 2. Acumos AI Boreas Release's Portal Marketplace

>- In this note Writer use [Documentation](https://docs.acumos.org/en/boreas/) as study sources.

#### 1. What is Marketplace ?

From documentation, Acumos AI Marketplace can be explained as below.

1. **Data-powered decision making and artificial intelligence software models**.
2. It provides a means to **securely share AI microservices along with information on how they perform** such as ratings, popularity statistics and user-provided reviews to apply crowd sourcing to software development.
3. The platform provides **integration between model developers and applications in order to automate the process of user feedback, exception handling and software updates**.

#### 2. Acumos AI Marketplace Architectures

The high level diagram of Acumos AI Marketplace can be seen as below.

![](https://i.imgur.com/GYKy6iR.jpg)

![](https://i.imgur.com/wPN73KC.jpg)

#### 3. Acumos AI Marketplace Backend APIs

The list of Acumos AI Marketplace backend APIs can be seen as below.

- Admin Service
- Auth Service
- Market Place Catalog Service
- Notification Services
- Oauth User Service
- Publish Request Service
- Publish Solution Service
- Push And Pull Solution Service
- User Role Services
- User Service Services
- Validation Status Services
- Web Based Onboarding Services

#### 4. Acumos AI Marketplace Flows Structures

1. Page Name: **Acumos Home Screen**
   - User Authentication Required: NO
   - Page Visibility to User: ALL
   - Navigation Menu: Market Place, Manage Models, Docs, SIGN IN , SIGN UP
   - Page Content: Featured Machine Learning Models/Solutions along with option to view all Solutions.
   - When User open Acumos Page, He/she will be presented with Acumos Home Screen with Featured Machine Learning Solutions in catalog Format (Tiles)
   - Admin Role is created with name as Admin inside Role tables in CDS DB.
 
2. Page Name: **Model/Solution Landing Page**
   - Navigation: Acumos Home -> Market Place -> Model/Solution Landing Page
   - User Authentication Required: NO (Read Only), Yes (For Downloads, Deploy and to add Review Comment)
   - Page Visibility: ALL
   - Navigation Menu: Market Place, Manage Models, Docs, SIGN IN, SIGN UP
   - Page Content: Machine Learning Solution Landing Page with Title, Description, API Usage (Input & Output swagger UI format to test API), Images/Videos. Bottom of the screen should display ratings, reviews from other users and options to add review. 
    - Social Media Sharing options also need to be displayed. Deploy to Cloud should only provide MS Azure option.
   - Clicking on either of ``Download``,``Deploy to Clou`` or``Add review`` should prompt user to SIGN IN.
   - If User is already signed in, then clicking on:
``Download`` it should download the Machine Learning Solution to user laptop/computer.
    - ``Deploy to Cloud`` should prompt details about MS Azure (Inputs TBD)
    - ``Add Review Comment`` with text in the comment field should add the new comment.
    
3. Page Name: **My Models**
   - Under Manage Models Menu, Options available are: ``Add new Model``,``My Model`` or  ``Delete a Model``
   - Navigation: Acumos Home -> Manage Models -> My Models
   - User Authentication Required: Yes
   - Navigation Menu: Market Place, Manage Models, Docs, Notification, My Profile, Log Out
   - Page Content: Machine Learning Solutions and Composite Solutions are displayed in a catalog format. Icons on these solutions should allow to distinguish Single Modelled Solutions, Composite Solutions, Unpublished, published (Public Market Place & Company Market Place) as well as newly created Solutions which does not have any title/description etc.

4. Page Name: **Manage Models - My Models - Model Landing Page**
   - Under Manage Models Menu, Options available are: ``Add new Model``,``My Model`` and ``Delete a Model``.
   - User Authentication Required: Yes
   - Navigation Menu: Market Place, Manage Models, Docs, Notification, My Profile, Log Out
   - Page Content: If User has clicked on newly added Machine Learning Solution that does not have any Title/Description etc then Machine Learning Solution Landing Page with fields for Title, Description, API Usage (Input & Output swagger UI format to test API), Images/Videos will be displayed where User can add all the information using WYSIWYG editor.

:::info
**Then** :
- User can **save and view the preview of the Solutions like it would display** on the Market Place.

- Once Saved, User can then **Submit the Solution for publishing to Public Market Place or Company Market Place** by clicking buttons ``Publish to Public Market Place`` and ``Publish to Company Market Place``. Clicking on these two buttons will kick off the Certification Process which would **allow the Solution to be able to publish on Company Market Place** like local Market Place and it would also be allowed to be published on Public Market Place.

- User would also be **able to Share the Solutions with individuals or group or communities within the local Acumos instance** like Company Acumos by clicking on ``Share with Team`` which will open a pop up to lookup for the User/Group/Communities.

- **Certification Process requirements is later** and once available , the user experience/Wireframes can be discusses later.
:::

#### 5. Acumos AI Marketplace Flows Schemes

##### a. User Account Sign Up Flows Scheme

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

##### b. User Account Login Flows Schemes

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

##### c. Market Place Catalog Flows

![](https://i.imgur.com/i15KK2R.jpg)

##### d. Market Place Pages Flows

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


---

### 3. Try Solve NEXUS Installation for Acumos AI

>This deployment is continuation from [yesterday's notes]( https://hackmd.io/@christofel04/TEEP_Daily_Notes_11_8_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
**Next Writer Will Continue to Solve the Open Shift Issue in NTUST Server**
:::

---



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


