Table of Contents

Introduction

The rApp Manager is a lifecycle management service for rApps. It gets the rApp as ASD formatted package and lifecycle manages it based on it instance configuration. It uses ONAP ACM for lifecycle management operations and it integrates with other components for managing the rApp.

ASD package contains the details required to create and integrate the required services/components. Each ASD package contains only one rApp and One rApp can have any number of rApp instances.

Source code repository : https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric%2Fplt%2Frappmanager.git;a=summary

Architecture

Image Removed

Integrations

The rApp Manager integrated with the below components to support lifecycle managing the rApp.

ACM

Automation Composition Management (ACM) is a framework that supports Life Cycle Management of Automation Compositions. It supports deployment, monitoring, update and removal of Automation Compositions en-bloc, allowing users to manage their features, services, and capabilities as single logical units. More details about ACM can be found here.

ACM-R supports any number of participants and all the participants can be configured through the configuration in the rApp package.

List of participants used by rApp manager sample rApp.

A1PMS Participant - It interacts with A1PMS of NONRTRIC. It is capable of lifecycle managing A1PMS service.
Kserve Participant - It interacts with Kserve. It is capable of lifecycle managing Kserve inference service.
Kubernetes Participant - It interacts with Helm/Kubernetes. It is capable of lifecycle managing Helm charts.
DME Participant - It interacts with DME(ICS) of NONRTRIC. It is capable of lifecycle managing DME entities.

ACM composition and instance details can be provided as part of rApp package and the package structure can be found here.

DME

The DME(Information Coordination Service (ICS)) is a generic service that maintains data subscriptions. Its main purpose is to decouple data consumers and data producers in a multi vendor environment. A data consumer does not need to know anything about the producers of the data. More details about DME can be found here.

It integrates with rApp manager to enable the rApp produce/consume specific type of data(Information Type in DME terms).

Information type, Data producer/consumer information can be provided as part of rApp package and the package structure can be found here.

SME

The SME(CAPIF) stands for Common API framework and it was developed by 3GPP to enable a unified Northbound API framework across 3GPP network functions, and to ensure that there is a single and harmonized approach for API development. More details about DME can be found here.

It integrates with rApp manager to enable the rApp expose/access/discover endpoints.

Service exposure/access related configurations can be provided as part of rApp package and the package structure can be found here.

State Transitions

rApp States

The rApp lifecycle contains 4 states. The state and transitions are as follows,

COMMISSIONED
rApp will be in this state right after creation and 
once the DEPRIMING is completed

PRIMING
This is a transition state. rApp will be in this 
state once the PRIMING requested for rApp

PRIMED
rApp will be in this state once the PRIMING is 
completed. In this state rApp instances can be 
created

DEPRIMING
This is a transition state. rApp will be 
in this state once the DEPRIMING requested for rApp

...

Image Removed

rApp Instance States

The rApp Instance lifecycle contains 4 states. The state and transitions are as follows,

UNDEPLOYED
rApp instance gets created in this state and 
once the rApp Instance undeploy is completed

DEPLOYING
This is the transition state. rApp instance will
be in this state once DEPLOY is requested

DEPLOYED
rApp instance will be in this state once the 
rapp instance deployment is completed.

UNDEPLOYING
This is a transition state. rApp instance will
be in this state once UNDEPLOY requested for 
rApp instance

...

Image Removed

Flows

rApp flow

Create rApp

...

API user creates rApp by sending rApp package

...

rApp Manager validates the rApp

...

rApp Manager stores the rApp in the file system if the rApp is valid

...

Table of Contents

Introduction

The rApp Manager is a lifecycle management service for rApps. It gets the rApp as an ASD formatted package and lifecycle manages it based on it instance configuration. It uses ONAP ACM for lifecycle management operations and it integrates with other components for managing the rApp.

The ASD package contains the details required to create and integrate the required services/components. Each ASD package contains only one rApp and one rApp can have any number of rApp instances.

Source code repository : https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric%2Fplt%2Frappmanager.git;a=summary

Architecture

Image Added

rApp Data Model

Image Added

Integrations

The rApp Manager is integrated with the following components to support lifecycle managing the rApp.

ACM

Automation Composition Management (ACM) is a framework that supports Life Cycle Management of Automation Compositions. It supports deployment, monitoring, update and removal of Automation Compositions en-bloc, allowing users to manage their features, services, and capabilities as single logical units. More details about ACM can be found here.

ACM-R has the ability to support an unlimited number of participants and all the participants can be configured through the configuration in the rApp package.

List of participants used by rApp manager sample rApp.

A1PMS Participant - It interacts with A1PMS of NONRTRIC. It is capable of lifecycle managing A1PMS service.
Kserve Participant - It interacts with Kserve. It is capable of lifecycle managing Kserve inference service.
Kubernetes Participant - It interacts with Helm/Kubernetes. It is capable of lifecycle managing Helm charts. It expects the helm charts to be available in the mentioned repository as it doesn't handle the helm chart creation in the chart repository.
DME Participant - It interacts with DME(ICS) of NONRTRIC. It is capable of lifecycle managing DME entities.

ACM composition and instance details can be provided as part of the rApp package and the package structure can be found here.

DME

The DME(Information Coordination Service (ICS)) is a generic service that maintains data subscriptions. Its main purpose is to decouple data consumers and data producers in a multi vendor environment. A data consumer does not need to know anything about the producers of the data. More details about DME can be found here.

It is integrated with rApp manager to enable the rApp to produce/consume specific type of data(Information Type in DME terms).

Information type, and Data producer/consumer information can be provided as part of rApp package and the package structure can be found here.

SME

The CAPIF stands for Common API framework and it was developed by 3GPP to enable a unified Northbound API framework across 3GPP network functions, and to ensure that there is a single and harmonized approach for API development. More details about SME can be found here.

It is integrated with rApp manager to enable the rApp to expose/access/discover endpoints.

Service exposure/access related configurations can be provided as part of rApp package and the package structure can be found here.

State Transitions

rApp States

The rApp lifecycle contains 4 states. The state and transitions are as follows,

COMMISSIONED
rApp get created in this state and once the 
DEPRIMING is completed

PRIMING
This is a transition state. rApp will be in this 
state once the PRIMING requested for rApp

PRIMED
rApp will be in this state once the PRIMING is 
completed. In this state rApp instances can be 
created

DEPRIMING
This is a transition state. rApp will be 
in this state once the DEPRIMING requested for rApp

Image Added

rApp Instance States

The rApp Instance lifecycle contains 4 states. The state and transitions are as follows,

UNDEPLOYED
rApp instance gets created in this state and 
once the rApp Instance undeploy is completed

DEPLOYING
This is the transition state. rApp instance will
be in this state once DEPLOY is requested

DEPLOYED
rApp instance will be in this state once the 
rapp instance deployment is completed.

UNDEPLOYING
This is a transition state. rApp instance will
be in this state once UNDEPLOY requested for 
rApp instance

Image Added

Flows

rApp flow

Create rApp

API user creates rApp by sending rApp package

```
rApp Manager validates the rApp
```

rApp Manager stores the rApp in the file system if the rApp is valid

API user provided with the status of rApp creation.

```
API user request to Prime the rApp
```

rApp Manager fetches the ACM composition from rApp package and 
creates the ACM composition in ACM-R

rApp Manager gets the ACM composition creation status from ACM-R

rApp Manager request ACM-R to prime the ACM composition

rApp Manager gets the ACM composition priming status from ACM-R

rApp Manager checks with DME for the unknown information type from rApp package

rApp Manager get the information type availability from DME

API user provided with the status of rApp priming

Delete rApp

```
API user request to Deprime rApp
```

rApp Manager request ACM-R to deprime the ACM composition

rApp Manager get the status of ACM composition depriming.

rApp Manager requests ACM-R to delete the ACM composition

rApp Manager gets the status of ACM composition deletion

API user provided with the deprime rApp status.

```
API user request to delete the rApp
```

rApp Manager validates that the rApp is in COMMISSIONED state and 
there is no rApp Instances are available.

API User provided with delete rApp status

Image Added

rApp Instance flow

Create rApp Instance

API user request to create rApp Instance with the resource details from rApp package

API user get the rApp instance creation response

Deploy rApp Instance

```
API user request to 
```

Prime

deploy

the

rApp

rApp

instance rApp Manager fetches the

ACM

rApp

composition

package from

rApp

file

package

system and

creates

fetches the

ACM

resources

composition

mentioned in

ACM-R

the rApp instance. rApp Manager

gets the

request ACM-R

composition

with

creation

the

status from ACM-RrApp Manager request ACM-R to prime the ACM composition

necessary details from rApp package to Instantiate ACM instance rApp Manager gets

the

instantiate ACM

composition

instance

priming

response rApp

status

Manager

from

request ACM-R

rApp

Manager

to

checks

deploy

with DME for the unknown information type from rApp packagerApp Manager get

ACM instance ACM-R deploys the

information

A1PMS

type

instance

availability

if

from

it

DMEAPI

is

user

configured

provided with

in the

status of rApp priming

Delete rApp

```
API user request to Deprime rApp
```

rApp Manager request ACM-R to deprime the ACM composition

rApp Manager get the status of ACM composition depriming.

rApp Manager requests ACM-R to delete the ACM composition

rApp Manager gets the status of ACM composition deletion

API user provided with the deprime rApp status.

```
API user request to delete the rApp
```

rApp Manager validates that the rApp is in COMMISSIONED state and 
there is no rApp Instances are available.

API User provided with delete rApp status

Image Removed

rApp Instance flow

Create rApp Instance

API user request to create rApp Instance with the resource details from rApp package

API user get the rApp instance creation response

Deploy rApp Instance

API user request to deploy rApp instance

rApp Manager fetches the rApp package from file system and fetches the 
resources mentioned in the rApp instance.

rApp Manager request ACM-R with the necessary details from rApp package to 
Instantiate ACM instance

rApp Manager gets instantiate ACM instance responseACM instance

```
ACM-R gets the A1PMS deployment status
```

ACM-R deploys the Kserve instance if it is configured in the ACM instance

```
ACM-R gets the Kserve deployment status
```

ACM-R deploys the Kubernetes instance if it is configured in the ACM instance

ACM-R gets the Kubernetes deployment status

ACM-R deploys the DME instance if it is configured in the ACM instance

```
ACM-R gets the DME deployment status
```
```
rApp Manager gets ACM deployment status
```

rApp Manager request SME to create the entities in rApp instance

SME creates the entities provided by rApp Manager

rApp manager get the response of SME entities creation

API user provided with the status of rApp instance deployment. rApp Manager combines 
the status of ACM deployment and SME deployment to provide the rApp instance status.

Undeploy rApp Instance

API user request to undeploy rApp instance

rApp Manager fetches the rApp and rApp instance details

rApp Manager request ACM-R to undeploy deploythe ACM instance

ACM-R deploysundeploy the A1PMS instance if it is configured in the ACM instancealready deployed

ACM-R gets the A1PMS deploymentundeploy status

ACM-R deploysundeploy the Kserve instance if it is configured in the ACM instancealready deployed

ACM-R gets the Kserve deploymentundeploy status

ACM-R deploysundeploy the Kubernetes instance if it is configured in the ACM instancealready deployed

ACM-R gets the Kubernetes deploymentundeploy status

ACM-R deploysundeploy the DME instance if it is configured in the ACM instance already deployed

ACM-R gets the DME deploymentundeploy status

rApp Manager getsget ACM deploymentundeploy status

rApp Manager request SMEACM-R to createdelete the entities in rApp instanceSME creates ACM instance

rApp Manager get response of ACM instance deletion

rApp Manager request SME to delete SME entities

SME deletes the entities created as providedpart byof rApp Manager

rApp managerManager get the response of SME entities creationdeletion

API user provided withget the status of undeploy rApp instance deployment. rApp Manager combines 
the status of ACM deployment and SME deployment to provide the rApp instance status.

Undeploy rApp

Delete rApp Instance

API user request rApp Manager to delete rApp Instance

API user requestgets to undeploydelete rApp instance response

Image Added

Sample rApp package structure

Warning
This packaging structure is a prototype and subject to change

...

rApp Manager fetches the rApp and rApp instance details

...

rApp Manager request ACM-R to undeploy the ACM instance

...

ACM-R undeploy the A1PMS instance if it is already deployed

...

ACM-R gets the A1PMS undeploy status

...

ACM-R undeploy the Kserve instance if it is already deployed

...

ACM-R gets the Kserve undeploy status

...

ACM-R undeploy the Kubernetes instance if it is already deployed

...

ACM-R gets the Kubernetes undeploy status

...

ACM-R undeploy the DME instance if it is already deployed

...

ACM-R gets the DME undeploy status

...

rApp Manager get ACM undeploy status

...

rApp Manager request ACM-R to delete the ACM instance

...

rApp Manager get response of ACM instance deletion

...

rApp Manager request SME to delete SME entities

...

SME deletes the entities created as part of rApp

...

rApp Manager get the response of SME entities deletion

...

API user get the status of undeploy rApp instance

Delete rApp Instance

API user request rApp Manager to delete rApp Instance

API user gets delete rApp instance response

Image Removed

Sample rApp package structure

Warning
This packaging structure is a prototype and subject to change

The sample rApp package structure shown below and the location of relevant files for each integration is provided.

...

ACM (Files/Acm)

Definition - Files/Acm/Definition (Only one file)

```
Instances - Files/Acm/instances
```

DME (Files/Dme)

Consumer Information Types - Files/Dme/consumerinfotypes

Producer information Types -  Files/Dme/producerinfotypes

Information Consumers - Files/Dme/infoconsumers

Information Producers - Files/Dme/infoproducers

SME (Files/Sme)

Providers Functions - Files/Sme/providers

```
Service Api -  Files/Sme/serviceapis
```
```
Invokers - Files/Sme/invokers
```

...

Image Removed

CSAR File Generation

CSAR file generator is available in the rAppmanager repository here.

"rappmanager/csar-generator/resources" folder contains the resources to build the rApp package.

The contents of the "resources" directory can be modified as required and the package can be generated as shown The sample rApp package structure shown below and the location of relevant files for each integration is provided.

ACM (Files/Acm)

Definition - Files/Acm/Definition (Only one file)

```
Instances - Files/Acm/instances
```

DME (Files/Dme)

Consumer Information Types - Files/Dme/consumerinfotypes

Producer information Types -  Files/Dme/producerinfotypes

Information Consumers - Files/Dme/infoconsumers

Information Producers - Files/Dme/infoproducers

SME (Files/Sme)

Providers Functions - Files/Sme/providers

```
Service Api -  Files/Sme/serviceapis
```
```
Invokers - Files/Sme/invokers
```

Image Added

CSAR File Generation

CSAR file generator is available in the rAppmanager repository here (i-release).

"rappmanager/csar-generator/resources" folder contains the resources to build the rApp package.

The contents of the "resources" directory can be modified as required and the package can be generated as shown below,

Code Block

language	bash
title	Linux: Generate rApp package

> ./generate.sh

Code Block

language	powershell
title	Windows: Generate rApp package

> ./generate.bat

This will generate a package named "rapp.csar". It can be renamed as required.

This generated package can be used with rApp Manager to create rApp.

Deployment Instructions

The scripts for the deployments of rApp Manager and its dependent components are available here (i-release).

Tip
These scripts are specifically designed for a fresh environment. Some tweaks may be required to run these in an environment where there are some existing installations

Pre-requisites

Kubernetes Cluster (V1.24.6)
GIT

Environment setup

The installation scripts shown here installs all the required components.

ACM components should be configured with couple of other components for the participants to work.

In case some of the installation is already setup or not set by the installation scripts, the below environment variables can be used to set the configurations ACM through installation scripts.

Tip
Ignore the below variables if the entire environment is being setup by the following installation scripts

Variable Name

Description

Default Value

A1PMS_HOST

Address of the A1PMS.

It will be accessed from A1PMS participant.

http://policymanagementservice.nonrtric:9080

CHART_REPO_HOST

Address of the chart repository.

It will be used by Kubernetes participant.

http://IP_ADDRESS:8879/charts

IP_ADDRESS: IP of the host in which

the installation scripts are running.

Installation

All components can be installed using the command below,

Code Block

language	bash
title	Linux: Generate rApp package

> ./generate.sh>./install-all.sh

Individual components can be installed using the commands below,

To install the tools required for other installer scripts.

Code Block

language	powershell	title	Windows: Generate rApp packagebash

> ./generate.bat

This will generate a package named "rapp.csar". It can be renamed as required.

This generated package can be used with rApp Manager to create rApp.

Deployment Instructions

The scripts for the deployments of rApp Manager and its dependent components are available here.

Tip
These scripts are specifically designed for a fresh environment. Some tweaks may be required to run these in an environment where there are some existing installations

Pre-requisites

Kubernetes Cluster(V1.24.6)
GIT

Installation

...

./install-base.sh

To install the ACM, and it's related components.

Code Block

language	bash

>./install-acm.sh

To install the Kserve, and it's related components.

Code Block

language	bash

>./install-kserve.sh

To installs the NONRTRIC components.

Code Block

language	bash

>./install-allnonrtric.sh

Installed Components

Individual The below components can be installed using the commands below,
To install the tools required for other installer scripts.

Code Block

language	bash

>./install-base.sh

...

Code Block

language	bash

>./install-acm.sh

...

Code Block

language	bash

>./install-kserve.sh

To installs the NONRTRIC components.should be up and running for the rApp Manager integrations to work properly.

Istio components

Image Added

Cert Manager components

Image Added

Kserve components

Kserve Components Image Added

ACM Components

Image Added

NONRTRIC Components

Image Added

Troubleshooting

If Kserve installation failed or end up in the below state after "install-all.sh", Try run "patch-kserve.sh" script after "install-all.sh"

Image Added

Image Added

Uninstallation

To uninstall all the components

Code Block

language	bash

>./install-nonrtric.sh

Uninstallation

...

./uninstall-all.sh

...

Version	Old Version 22	New Version Current
Changes made by	Aravindhan Ayyanathan	John Keeney (Ericsson EST)
Saved on	Nov 22, 2023	Jan 18, 2024

Page Comparison

Versions Compared

Key

Introduction

Architecture

Integrations

ACM

DME

SME

State Transitions

rApp States

rApp Instance States

Flows

rApp flow

Create rApp

Introduction

Architecture

rApp Data Model

Integrations

ACM

DME

SME

State Transitions

rApp States

rApp Instance States

Flows

rApp flow

Create rApp

Delete rApp

rApp Instance flow

Create rApp Instance

Deploy rApp Instance

Delete rApp

rApp Instance flow

Create rApp Instance

Deploy rApp Instance

Undeploy rApp Instance

Delete rApp Instance

Sample rApp package structure

Delete rApp Instance

Sample rApp package structure

ACM (Files/Acm)

DME (Files/Dme)

SME (Files/Sme)

CSAR File Generation

ACM (Files/Acm)

DME (Files/Dme)

SME (Files/Sme)

CSAR File Generation

Deployment Instructions

Pre-requisites

Environment setup

Installation

Deployment Instructions

Pre-requisites

Installation

Installed Components

Istio components

Cert Manager components

Kserve components

ACM Components

NONRTRIC Components

Troubleshooting

Uninstallation

Uninstallation