Table of Contents
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.
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.
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. 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/hosts-aio
- Here user can use the private IP as a master IP
ealt-edge/ocd/infra/playbooks/var.yml
...
- 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/hosts-aio
- Here user can use the private IP as of a MASTER_IP node
ealt-edge/ocd/infra/playbooks/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 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.
...
- 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 as a MASTER_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 master which is used for Edge to connectnode.
ealt-edge/ocd/infra/playbooks/muno-config/edge/hosts-muno-edge
...
- 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 as a MASTER_IP
- 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.
- of a edge node
- OCD_IP: Here user can use the private IP od of a Controller NodeNode which is used for Edge to connect
ealt-edge/ocd/infra/playbooks/password-var.yml
...
* Here user can put the public IP in center, edge, ocdhost node.
Installing Mode : EALTEdge using Ansible-Playbooks
...
Once the execution is completed in console will see prompt "EALTEdge Environment Installed , Components Install CENTER and EDGE Nodes Successfully"
...
Currently the verification is manually done.
In muno mode
1- Login to the Center Node and check whether K8S cluster is installed.
Components and Services running in CENTER Controller Node
Components and Services running EDGE Node
2- Login to the Center Node and check whether K8S cluster is installed in muno mode.
Components and Services running EDGE Node
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
1.2. click on Systems ->App Rule -> New Registration
Name: Apprule(any general name)
IP: applcm"public ip"
Port: 30206
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)
Repo Username: admin(harbor user name)
Repo Password: Harbor@edge(harbor password)
Vendor: vendor(any general name)
2. log in
Deploy Application in EALTEdge
- Login to MECM Portal https://ip:30093
...
2.1. Add k8s node: Click on Edge Nodes ->New Rgistration 1.1 click on Systems ->App LCM ->New Registration
System: k8s Name: Applcm(any general name)
Name: edge1(any general name) IP: applcm"public ip"
IP: edge public IP Port: 30204
Location: Select from the drop-down 1.2. click on Systems ->App Store ->New Registration
Architecture: x86 App Store Name: appstore(any general name)
Capabilities: select none IP: Appstore public ip
App LCM: Select edge IP from the drop-down box Port: 30099
App Rule MGR: Select edge IP from the drop-down box
Appstore Repo: {HarborIP:443}(192.168.1.1:443)
2.2. Download /root/.kube/config file from edge node Repo Name: appstore(any general name)
And click on Upload config file to upload.
3. log in to harbor Portal https://ip:443
Repo Username: admin(harbor user name)
3.1. Add three new projects
Repo Password: Harbor@edge(harbor password)
3.2. Those three projects' names are appstore, developer, and mecm. And select access level to the public.
3.3. Final page will look like the below screenshot.
4 Vendor: vendor(any general name)
2. log in to Developer Portal MECM Portal https://ip:3009230093
2.1. 4.1. Add sandbox env to deploy application before publishingAdd k8s node:
Click on Edge Nodes ->New Rgistration Click System ->Host Management ->Add Host
System: k8s
. Name: edge1(any general name)
System: k8s IP: edge public IP
Lcmip: sandbox ip(for testing purpose can provide edge ip, if no sandbox env) Location: Select from the drop-down
mecHost: sandbox ip(for testing purpose can provide edge ip, if no sandbox env) Architecture: x86
Port Capabilities: 30204select none
Protocol: https App LCM: Select edge IP from the drop-down box
Architecture: X86 Status: Normal App Rule MGR: Select edge IP from the drop-down box
Port Range: leave as it is 2.2. Download /root/.kube/config file from edge node
Address: Bangalore UploadConfig File: upload sandboxenvkubeconfig fileAnd click on Upload config file to upload.
3. log in to harbor Portal https://ip:443
4.2 Click on Workspace -> Create Project -> Application Integration -> Start
- Go to Application Integration
3.1. Add three new projects
- Provide App Name, Version, Provider, Workload Type, Architecture, Industry, Type. 3.2. Those three projects' names are appstore, developer, and mecm. And select access level to the public.
- Upload Icon, provide Description. And click on confirm.
3.3. Final page will look like the below screenshot.
4. log in to Developer Portal https://ip:30092
4 4.3. Now click on Deployment Test.1. Add sandbox env to deploy application before publishing
- Upload Docker images directly from the portal by clicking on Upload App Image.
- docker save -o <path-to-save>/<repo-name>.tar <repo-name>:<tag>
Click System ->Host Management ->Add Host
After that you can take tar file from path and upload image. .
Name: general name
Or, directly push Docker images to Harbor repo (takes lesser time, preferred). Following command for pushing an image in Harbor:
...
- Click next, upload deployment yaml file now.
System: k8s
Lcmip: sandbox ip(for testing purpose can provide edge ip, if no sandbox env)
mecHost: sandbox ip(for testing purpose can provide edge ip, if no sandbox env)
Port: 30204
- After config upload, click next and click start deployment Protocol: https
Architecture: X86
- After Deployment is successful, click on Release Recourses
Status: Normal
Port Range: leave as it is
Note Address: Bangalore
- UploadConfig File: upload sandboxenvkubeconfig file
While Deployment test if any error happens, open ATP portal (https://ip:30094) in another tab of the browser, sign in, come back to the developer portal and re run deployment test 4.2 Demonstration of application Development & Deployment
- gitee.com/edgegallery/applications repo provides A lot of applications with their logo, deployment YAML & user guides 3.4. Now click on Application Release Application Development
link - https://www.youtube.com/watch?v=AjQNG5d3p84&t=23s
Upload file for Application Description
Click save config
Application Deployment
Click Next Step, click Start Test, scroll down to find & click the Start Test button, then confirm. Once the testing is complete click on Next Step
click publish to publish an application to AppStore. Go to link - https://<IP>:30091 and App Warehouse to confirm that the application is successfully ported.
www.youtube.com/watch?v=PbxKpslVnmc&t=31s
Developer Guide and Troubleshooting
...
##Now get ca certificate use below command
```
curl http://10.43.130.35:8200/v1/pki/ca/pem
```
##10.43.130.35 is your vault ip, need to replace with latest vault ip
Troubleshooting
...
| S. No | Software | Type | Version | License | Remarks |
| 1. | Docker | CRI | 18.09 | Apache 2.0 license | No code modifications done |
| 2. | Kubernetes | Orchestration | v1.18.7 | Apache 2.0 license | No code modifications done |
| 3. | Edge Gallery | Opensource MEC Platform | 1.1.1 | Apache 2.0 license | No code modifications done |
...
| S. No | Software | Type | Version | License Information | Remarks |
| 1. | Docker | CRI | 18.09 | Apache 2.0 license | No code modifications done |
| 2. | K8s | Orchestration | 1.18.7 | Apache 2.0 license | No code modifications done |
| 3. | Edge Gallery | Opensource MEC platform | 1.1.1 | Apache 2.0 license | Open Source MEC Platform |
...