Introduction

...

Note: EALTEdge Blueprint Deployment has been tested on Cloud VM and is not tested on Bare-Metal Environment. Though, theoretically deployment should work in bare metal, provided hardware and software prerequisites are met. Kindly refer R5 R6 - Test Documentation of Enterprise Applications on Lightweight 5G Telco Edge (EALTEdge) to get details on the tested deployment.

...

EALTEdge Installation Mode:

EALTEdge supports 2 Mode of installation: Multi Node and All-In-One (AIO) Node deployment.

AIO(All in One) mode:

In this mode, all 3 nodes (OCD which is deployment node, Center node and Edge node) are deployed on single VM.

The logical deployment topology can be seen here.

Image Modified

MUNO(Multi Node) Mode:

In this mode, all 3 nodes (OCD which is deployment node, Center node and Edge node) can be deployed on multiple VM.

This mode can have a OCD node deployed on a VM, Center node deployed on same OCD VM or on different VM and EDGE node deployed on different VM.

The logical deployment topology can be seen here.

Image Modified

Bare Metal Deployment Guide

...

2. Setup password-less login from ocd to center and ocd to edge.

...

-

If you get authentication issue you can change the permission

# Open file: vi /etc/ssh/sshd_config

...

- sudo systemctl restart ssh.service # sshpass

For EdgeGallery AIO mode:

Login from ocd to center and ocd to edge in a single node.

sshpass -p <password> ssh-copy-id -p <ssh-port> -o StrictHostKeyChecking=no root@<node_

...

3. cp -p /etc/passwd /etc/passwd.bkp

cp -p /etc/group /etc/group.bkp

id ubuntu

groupmod -g 600 ubuntu

id ubuntu

4. Review and Change Parameters

For EdgeGallery MUNO Mode

ealt-edge/ocd/infra/playbooks/muno-config/controller/hosts-muno-controller

ealt-edge/ocd/infra/playbooks/muno-config/controller/var.yml

ealt-edge/ocd/infra/playbooks/muno-config/edge/hosts-muno-edge

ealt-edge/ocd/infra/playbooks/muno-config/edge/var.yml

ealt-edge/ocd/infra/playbooks/password-var.yml

For EdgeGallery AIO Mode:

ealt-edge/ocd/infra/playbooks/hosts-aio

Image Removed

...

ip>

For EdgeGallery Muno mode:

Login from ocd to center in a controller node

sshpass -p <password> ssh-copy-id -p <ssh-port> -o StrictHostKeyChecking=no root@<controller-node_ip>
sshpass -p <password> ssh-copy-id -p <ssh-port> -o StrictHostKeyChecking=no root@<edge-node_ip>

Login from ocd to edge in a edge node

sshpass -p <password> ssh-copy-id -p <ssh-port> -o StrictHostKeyChecking=no root@<controller-node_ip>
sshpass -p <password> ssh-copy-id -p <ssh-port> -o StrictHostKeyChecking=no root@<edge-node_ip>

3. These command are require in both AIO and MUNO(Controller and Edge Node ) mode.

cp -p /etc/passwd /etc/passwd.bkp

cp -p /etc/group /etc/group.bkp

id ubuntu

groupmod -g 600 ubuntu

id ubuntu

4. Review and Change Parameters

For EdgeGallery AIO Mode:

ealt-edge/ocd/infra/playbooks/var.ymlhosts-aio

Here user can use the private IP of a node

Image RemovedImage Added

ealt ealt-edge/ocd/infra/playbooks/password-var.yml

Image Removed

For EALT-EDGE stack:

...

NETWORK_INTERFACE: regex for network interface on the VM. (user can be check ineterrface name by ifconfig and provide inerface name accordingly for example like eth.* )
MASTER_IP: Here user can use the private IP of a node
PORTAL_IP: If portal need to be access over internet then uncomment the PORTAL_IP and use public IP as a PORTAL_IP otherwise portal will be accessible only on private IP default.

Image Removed

Installing Mode : EALTEdge using Ansible-Playbooks

1. git clone the ealt-edge repo, to download the software to install the EALTEdge Environment.

root@akraino-mec-0001:~# git clone "https://gerrit.akraino.org/r/ealt-edge"

2. go to the below directory

root@akraino-mec-0001:~# cd ealt-edge/ocd/infra/playbooks

3. Modify the Configuration File :

ealt-inventory.ini with the details of CENTER and EDGE Nodes.

For Edge Gallery installation:

MUNO-Mode:

Execute the below command:

cd ealtImage Added

ealt-edge/ocd/infra/playbooks/password-var.yml

All passwords must include capital letters, lowercase letters, numbers and special characters and whose length must be no less than 8 characters. Also there should be no special characters & in it. Otherwise, the deployment will failed because of these simple passwords.
A sample password could be "Harbor@12345"

Image Added

For EdgeGallery MUNO Mode:

ealt-edge/ocd/infra/playbooksansible-playbook -i /muno-config/controller/hosts-muno-controller ealt-eg-muno-controller.yml --extra-vars "operation=install" -e "ansible_user=root"

ansible-playbook -i muno-config/edge/hosts-muno-edge ealt-eg-muno-edge.yml --extra-vars "operation=install" -e "ansible_user=root"

For AIO mode:

Execute the below command

cd ealt-edge/ocd/infra/playbooks

ansible-playbook ealt-eg-aio-latest.yml -i hosts-aio --extra-vars "operation=install" -e "ansible_user=root"

Installation of ealt-edge stack:

ansible-playbook ealt-all.yml -i ealt-inventory.ini --extra-vars "operation=install"

Once the execution is completed in console will see prompt "EALTEdge Environment Installed , Components Install CENTER and EDGE Nodes Successfully"

Snapshot Deployment Overview

N/A

Special Requirements for Virtual Deployments

N/A

Install Jump Host

N/A

Verifying the Setup - VM's

N/A

Upstream Deployment Guide

Upstream Deployment Key Features

N/A

Special Requirements for Upstream Deployments

N/A

Scenarios and Deploy Settings for Upstream Deployments

N/A

Including Upstream Patches with Deployment

N/A

Running

N/A

Interacting with Containerized Overcloud

N/A

Verifying the Setup

Verifying EALTEdge Deployment

Currently the verification is manually done.

Login to the Center Node and check whether K8S cluster is installed.

Components and Services running in CENTER Node

Image Removed

Components and Services running EDGE Node

Image Removed

2- Login to the Center Node and check whether K8S cluster is installed in muno mode.

Image Removed

Components and Services running EDGE Node

Image Removed

Deploy Application in EALTEdge

Login to MECM Portal https://ip:30093

1.1 click on Systems ->App LCM ->New Registration

Name: Applcm(any general name)

IP: applcm"public ip"

Port: 30204

Image Removed

1.2. click on Systems ->App Rule -> New Registration

Name: Apprule(any general name)

IP: applcm"public ip"

Port: 30206

Image Removed

1.3. click on Systems ->App Store ->New Registration

App Store Name: appstore(any general name)

IP: Appstore public ip

Port: 30099

Appstore Repo: {HarborIP:443}(192.168.1.1:443)

Repo Name: appstore(any general name)

Here user can use the private IP as a master IP of a Controller node

Image Added

ealt-edge/ocd/infra/playbooks/muno-config/controller/var.yml

NETWORK_INTERFACE: regex for network interface on the VM. (user can be check ineterrface name by ifconfig and provide inerface name accordingly for example like eth.* )
MASTER_IP: Here user can use the private IP of a controller node
PORTAL_IP: If portal need to be access over internet then uncomment the PORTAL_IP and use public IP of a controller node as a PORTAL_IP otherwise portal will be accessible only on private IP default.
CONTROLLER_MASTER_IP: Private IP of the Controller node.

Image Added

ealt-edge/ocd/infra/playbooks/muno-config/edge/hosts-muno-edge

Here user can use the private IP as a master IP of a Edge node

Image Added

ealt-edge/ocd/infra/playbooks/muno-config/edge/var.yml

NETWORK_INTERFACE: regex for network interface on the VM. (user can be check ineterrface name by ifconfig and provide inerface name accordingly for example like eth.* )
MASTER_IP: Here user can use the private IP of a edge node
OCD_IP: Here user can use the private IP of a Controller Node which is used for Edge to connect

Image Added

ealt-edge/ocd/infra/playbooks/password-var.yml

All passwords must include capital letters, lowercase letters, numbers and special characters and whose length must be no less than 8 characters. Also there should be no special characters & in it. Otherwise, the deployment will failed because of these simple passwords.
A sample password could be "Harbor@12345"

Image Added

For EALT-EDGE stack:

ealt-edge/ocd/infra/playbooks/ealt-inventory.ini

* Here user can put the public IP in center, edge, ocdhost node.

Image Added

Installing Mode : EALTEdge using Ansible-Playbooks

1. git clone the ealt-edge repo, to download the software to install the EALTEdge Environment.

root@akraino-mec-0001:~# git clone "https://gerrit.akraino.org/r/ealt-edge"

2. go to the below directory

root@akraino-mec-0001:~# cd ealt-edge/ocd/infra/playbooks

3. Modify the Configuration File :

ealt-inventory.ini with the details of CENTER and EDGE Nodes.

For Edge Gallery installation:

MUNO-Mode:

Execute the below command:

cd ealt-edge/ocd/infra/playbooks

ansible-playbook -i muno-config/controller/hosts-muno-controller ealt-eg-muno-controller.yml --extra-vars "operation=install" -e "ansible_user=root"

ansible-playbook -i muno-config/edge/hosts-muno-edge ealt-eg-muno-edge.yml --extra-vars "operation=install" -e "ansible_user=root"

For AIO mode:

Execute the below command

cd ealt-edge/ocd/infra/playbooks

ansible-playbook ealt-eg-aio-latest.yml -i hosts-aio --extra-vars "operation=install" -e "ansible_user=root"

Installation of ealt-edge stack:

ansible-playbook ealt-all.yml -i ealt-inventory.ini --extra-vars "operation=install"

Once the execution is completed in console will see prompt "EALTEdge Environment Installed , Components Install CENTER and EDGE Nodes Successfully"