@@ -82,10 +140,20 @@ Build and deploy the MEC Sandbox as follows:
- Place repo in home folder
- Checkout the required AdvantEDGE version tag
1. Configure MEC Sandbox:
- Configure object store:
-`vi ~/AdvantEDGE/config/thanos.yaml` and `vi ~/AdvantEDGE/config/thanos-archive.yaml`
- Set endpoint to long-term storage VM FQDN
-**NOTE:** Make sure _/etc/hosts_ file contains entry for VM FQDN that points to VM private IP address (if on same local network)
- Set access_key to object store access key value
- Set secret_key to object store secret key value
- Configure session & OAuth secrets:
-`vi ~/mec-sandbox/config/secrets.yaml`
- Set a unique session encryption key
- Set the OAuth provider client ID & secrets using the values from the OAuth Applications
- Configure deployment:
-`vi ~/mec-sandbox/config/.meepctl-repocfg.yaml`
- Set Prometheus external labels
-**NOTE:** This uniquely identifies Prometheus data sources in the long-term storage data buckets
- Configure Alert Manager slack channel webhook:
- Create incoming webhook:
- Create target slack channel in slack workspace
@@ -110,13 +178,16 @@ Build and deploy the MEC Sandbox as follows:
-`./deploy.sh`
-**NOTE:** This updates the `~/.meep/user/` folder with the user frontend, sandbox swagger UI, and user chart values.yaml overrides
-**NOTE:** This also copies the AdvantEDGE configuration files to their respective locations in your local AdvantEDGE clone `~/AdvantEDGE/`. Running `git status` in your AdvantEDGE clone will list the updated (or new) files.
-`python ~/AdvantEDGE/config/configure-secrets.py set ~/AdvantEDGE/config/secrets.yaml`
-**NOTE:** Once the kuberentes secrets have been created, it is recommended to remove the `secrets.yaml` config files containing the clear-text secrets