Redirect link: How to create and install OTF environmentOTF Instance: 1-click Installation
Delivery Status
| Warning |
|---|
|
Only the Integration PTL should edit the delivery status table to track the release validation progress |
| Warning |
|---|
| title | Code submission under review |
|---|
|
OTF codes are currently under review. It needs multiple iteration of further revision and integration until it is stable enough for release. |
| Info |
|---|
| title | Defer to Cherry Maintenance Release |
|---|
|
The OTF one-click deployment helm charts will be released in the Cherry maintenance release |
| Deployment scripts | E2E Flows | deploy one-click-dbs | deploy one-click-core | deploy otf-vths
|
| OTF | OAM | NONRTRIC | RICP | RICAPP | O-DU | O-CU | Test Result | Notes |
|---|
Deployment Artifacts
| Docker Container |
|
|
|
|
|
|
|
| O1-vTH images are missing |
| Helm Charts |
Need further automation (e.g., create PVs, set up helm repo, update helm dependency ) Have multiple bugs. | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | key in (INT-115, INT-116, INT-117, INT-118, INT-119, INT-120) |
|---|
| serverId | 3122c0e4-6090-3a7d-9725-8b5a32a8eaeb |
|---|
|
Helm charts values use parameters from AT&T internal environment. Correct configurations need to be further integrated | | Deployment scripts |
|
|
|
|
|
|
|
|
|
| E2E Flows | deploy one-click-dbs |
|
|
|
|
|
|
|
| |
| deploy one-click-core |
|
|
|
|
|
|
|
|
| deploy otf-vths |
|
|
|
|
|
|
|
|
Deploy one-click-dbs
Step 1: Git clone OTF repo
| Code Block |
|---|
git clone "https://gerrit.o-ran-sc.org/r/it/otf"
cd otf/one-click |
Step 2: Update Helm dependency
| Code Block |
|---|
helm dep build ./one-click-dbs |
Step 2: Install DBs without PV
| Code Block |
|---|
helm install one-click-dbs -n otf --set mongodb.persistence.enabled=false --set mysql.persistence.enabled=false ./one-click-dbs/ |