...
4. Execute the below command
root@akraino-mec-0002:~# ansible~# ansible-playbook ealt-all.yaml yml -i ealt-inventory.ini --extra-vars "operation=install"
Once the execution is completed in console will see prompt "EALT Environment Installed , Components Install MECM and MEP Nodes Successfully"
...
To Install only MECM Node
root@akraino-mec-0002:~# ansible~# ansible-playbook ealt-mecmall.yaml yml -i ealt-inventory.ini --tags "mecm" --extra-vars "operation=install"
To Install only MEP Node
root@akraino-mec-0002:~# ansible~# ansible-playbook ealt-mepall.yaml yml -i ealt-inventory.ini --tags "mep" --extra-vars "operation=install"
Installing Mode : EALT using CLI
...
root@akraino-mec-0002:~#cd ealt/infra/cli/
root@akraino-mec-0002:~#chmod +x build _cli.sh
root@akraino-mec-0002:~#source build_cli.sh
root@akraino-mec-0002:~#cd ~/ealt-edge/ocd/infra/playbooks
3. Edit the Configuration File : ealt-inventory.ini with the details of MECM and MEP Nodes.
root@akraino-mec-0002:~#vi ealt-inventory.ini
4. Execute the below command to install EALT Environment
...
S. No | Software | Type | Version | Remarks |
1. | Docker | CRI | 1819.0603 | |
2. | K3S | Orchestration | Lightweight Kubernetes | |
3. | Helm | 3.0.2 | ||
4. | cAdvisor | Container Metrics | Latest Container version in Docker Hub | Running as Docker Container. |
5 | RabbitMQ | Running as a pod in default namespace | ||
6 | Prometheus | Metrics Collector | Internally its installing following metrics exporter NodeExporter, alertManager, kubeStateMetrics, pushgateway | |
7 | Kong | API Gateway | Running as a POD in mep namespace | |
8 | Vault | Secret Management | Running as a Pod in default Namespace | |
9 | Cert-Manager | Certificate Management | Running as a Pod in Cert-manager |
Deploying Application Packages : Using CLI
Precondition : The EALT Environment should be installed. One MECM and one MEP Node atleast.
Pre-configuration : Need to set the below parameters as environment variables on VM where EALT CLI is being installed.
export ONBOARDPACKAGEPATH= <Path where Application CSAR Package is kept in the Node where CLI is running>
export MECMClusterIP=<IP of MECM Node> #IP of Node where MECM is installed.
export MECMClusterPort=30001 #(Node Port of applcm service running on MECM)
Command Supported:-
Application Package Management CLI Commands:
- Package On Boarding : root@akraino-mec-0002:~#ealt app create -f "sample_app.csar "
- Package Info Query: root@akraino-mec-0002:~#ealt app info -i "<package id number>"
- Package Delete: root@akraino-mec-0002:~#ealt app delete -i "<package id number>"
Application Life Cycle Management CLI Commands:
- Application Instance Creation on MEP Node: root@akraino-mec-0002:~#ealt applcm create -i appdid "<id>" -n "<name>" -d "<description>"
- To start the application instance on MEP Node: root@akraino-mec-0002:~#ealt applcm start -i appid "<id>" -n "<hostname>" -o "<hostip>"
- To get the application instance details : root@akraino-mec-0002:~#ealt applcm info -i appid "<id>"
- To terminate the application instance: root@akraino-mec-0002:~#ealt applcm kill -i appid "<id>"
- To delete the application on MEP Node: root@akraino-mec-0002:~#ealt applcm delete -i appid "<id>"
Snapshot Deployment Overview
...
Uninstall Guide
Using Ansible Playbooks
root@akraino-mec-0002:~#ansible-playbook ealt-all-uninstall.yml -i ealt-inventory.ini --extra-vars "operation=uninstall"
root@akraino-mec-0002:~# ansible~#ansible-playbook ealt-clearallall-uninstall.yaml yml -i ealt-inventory.ini --tags "infra" --extra-vars "operation=uninstall"
root@akraino-mec-0002:~# ansible~#ansible-playbook ealt-clearmecmall-uninstall.yaml yml -i ealt-inventory.ini --tags "mecm" --extra-vars "operation=uninstall"
root@akraino-mec-0002:~# ansible~#ansible-playbook ealt-clearmepall-uninstall.yaml yml -i ealt-inventory.ini --tags "mep" --extra-vars "operation=uninstall"
Using CLI
root@akraino-mec-0002:~#ealt clean all
root@akraino-mec-0002:~#ealt clean mecm
root@akraino-mec-0002:~#ealt clean mep
...