...
The guide covers the installation details which are related to Enterprise Applications on Lightweight 5G Telco Edge (EALTEdge) Blueprint.
This Blueprint is leveraging the Edge Gallery, an Open Source community which primarily focusses on the platform framework of the carrier network's edge. It builds the basic framework of MEC edge resources, applications, security and management and de facto standards of network openness services through open source collaboration and implements interconnection with the public cloud. For more details please refer https://www.edgegallery.org/en/This guide covers detailed information of the various types of deployments, detailed steps and what are the various components it will install. In addition, the guide provides information on hardware requirements, prerequisite software and minimum hardware requirements. On successful deployment, MECM and MEC Hosts will be installed. The number of nodes in MECM cluster and MEC Host cluster is configurable.
The MECM CENTER Node is a K8s Cluster and MEC host EDGE Node is a K3s Cluster.
How to use this document
...
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 R3 R4 - Test Documentation of Enterprise Applications on Lightweight 5G Telco Edge (EALTEdge) to get details on the tested deployment.
...
Minimum Hardware Requirements
MECMCENTER Node | |
---|---|
HW Aspect | Requirements |
# of Node(s) | A virtual machine hosted in any Cloud Provider having internet connectivity. |
# of CPU | 8 |
Architecture | x86_AMD64 or ARM64. |
RAM | 8 GB |
Disk | 120 GB ~ 512GB |
Networks | 1 |
MEC HostEDGE Node(s) | |
---|---|
HW Aspect | Requirements |
# of Node(s) | 1 MEC Host |
# of CPU | 4 |
Architecture | x86_AMD64 or ARM64. |
RAM | 4 GB |
Disk | 20 GB ~ 256 GB |
Network | 1 |
...
Recommended Hardware Requirements
MECMCENTER Node | |
---|---|
HW Aspect | Requirements |
# of Node(s) | A virtual machine hosted in any Cloud Provider having internet connectivity. |
# of CPU | 8 |
Architecture | x86_AMD64 or ARM64. |
RAM | 8 GB |
Disk | 120 GB ~ 512GB |
Networks | 1 |
MEC HostEDGE Node(s) | |
---|---|
HW Aspect | Requirements |
# of Node(s) | 1 MEC Host |
# of CPU | 4 |
Architecture | x86_AMD64 or ARM64. |
RAM | 4 GB |
Disk | 20 GB ~ 256 GB |
Network | 1 |
...
- Virtual Machines preinstalled with Ubuntu 16.04 /18.04 for MECM Node.
- Virtual Machines preinstalled with Ubuntu 16.04 / 18.04 or CentOS 7.X for MEC Host Nodes
- root user created in the Deployment Node, MEC Node and MEC Host Node.
- SSH Server running in all the Nodes.
- Ansible > 2.5 installed in One Click Deployment Node (Jump Host)
- git installed in Jump Host.
- Kubespray code is downloaded (https://github.com/kubernetes-sigs/kubespray.git)
- GO Lang (version greater than 1.1514.32) installed in Jump Host, required for CLI.
...
Network Requirements
- Internet connectivity in Jump OCD Host, MECM CENTER and MEC HostsEDGE Nodes.
- The MECM Master CENTER Node and MEP Master EDGE Node should be able to ping each other.
...
For Virtual Deployment minimum three Virtual machines, following are the virtual machines and their usage
No | Usage |
---|---|
1 | Jump Host (One Click Deployment Node) |
2 | Center CENTER Node |
3 | Edge EDGE Node |
All the nodes should have internet connectivity , network interface and network connectivity between the VM's.
...
- Install Ansible > 2.9.6 [ https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html]
- Install git
- Install GoLang > 1.1514+
- Git clone the Kubespray repo. [https://github.com/kubernetes-sigs/kubespray.git]
- Install python3 and pip3
- cd kubespray && pip install -r requirements.txt
...
3. Modify the Configuration File : ealt-inventory.ini with the details of MECM CENTER and MEC HostsEDGE Nodes.
root@akraino-mec-0002:~# vi ealt-inventory.ini
...
Once the execution is completed in console will see prompt "EALTEdge Environment Installed , Components Install MECM CENTER and MEC Hosts EDGE Nodes Successfully"
Other Options:
...
- Login to the Center Node and check whether K8S cluster is installed.
- Check the below mentioned components and services are running as Pods / Services in Kubernetes cluster
- PostgresSQL
- AppLCM
- Appo
- Inventory
- Apm
- MECM - FrontEnd
- Appstore
- Developer Portal
- Service Center
- User Management
- Login to Edge Host and check K3S is installed.
Components and Services running in CENTER Node
Components and Services running EDGE Node
Developer Guide and Troubleshooting
...
root@akraino-mec-0002:~#ealt clean all
root@akraino-mec-0002:~#ealt clean edgeServices Part Pod Snapshots Need to attach
Troubleshooting
Error Message Guide
...