@@ -206,13 +206,14 @@ This deployment configuration will require two VMs, see [Prerequisites](#prerequ
6. Install maps for the front-end:
- Download the Monaco map tiles from [this link](https://data.maptiler.com/downloads/europe/france/monaco/)
- Copy the downloaded _.mbtiles_ file to the _~/.meep/omt/_ folder
- Restart the `open-map-tiles` container to load the maps
- Restart the `open-map-tiles-xxxx-yy` container to load the maps
- NOTE: _xxxx_ and _yy_ denote the hash for Kubernetes _deployment_ and _service_ objects respectively and their values will vary from cluster to cluster
7. Enable network scenarios in the frontend:
-TODO
-Refer to the [network scenarios](./network-scenarios.md) guide for creating or uploading network scenarios
## MEC Sandbox without Long-term Storage
This deployment configuration does not store metrics in a seperate Storage VM. Instead, short-term metrics are stored in the same VM that is running the MEC Sandbox.
This deployment configuration does not store metrics in a separate Storage VM. Instead, short-term metrics are stored in the same VM that is running the MEC Sandbox.
1. Clone MEC Sandbox & AdvantEDGE repositories:
- Fetch required MEC Sandbox baseline:
@@ -274,8 +275,10 @@ This deployment configuration does not store metrics in a seperate Storage VM. I
-**NOTE:** Once the kubernetes secrets have been created, it is recommended to remove the config files containing the clear-text secrets
5. Build & Deploy AdvantEDGE:
- For more details see [AdvantEDGE Deployment Workflow](https://interdigitalinc.github.io/AdvantEDGE/docs/platform-mgmt/mgmt-workflow/)
@@ -293,22 +296,7 @@ This deployment configuration does not store metrics in a seperate Storage VM. I
- Restart the `open-map-tiles-xxxx-yy` container to load the maps
- NOTE: _xxxx_ and _yy_ denote the hash for Kubernetes _deployment_ and _service_ objects respectively and their values will vary from cluster to cluster
7. Enable network scenarios in the frontend:
- Clone the MEC Sandbox frontend repo anywhere on any local system/laptop which can access the MEC Sandbox deployed. Cloning of the full repository is not required as only the `networks` folder in the repository is required.
- Before proceeding to upload the network scenarios files, GitHub user will need to be provisioned as admin. See [User Provisioning](#user-provisioning) for a step-by-step procedure.
- After successful user provisioning, admin users will have access to an _alternate frontend_ of the MEC Sandbox where admin users can access monitoring dashboard, configure existing network scenarios or even create new ones etc. To verify, sign into the MEC Sandbox UI using the the Github account that was made admin user in [User Provisioning](#user-provisioning). A new tab `Dashboard` should appear in the navigation bar.
- Now, open `http://<mec-sandbox-vm-ip>/alt` while being signed into the MEC Sandbox UI. This will open the AdvantEDGE dashboard.
- Click on `Configure` tab.
- Click on the `Import` button. Navigate to the _networks_ folder on the local system/laptop and upload any network scenario file.
- Click on the `Save` button. It will ask to name the network scenario. Keep the default name or give your own.
- Keep repeating the above two steps until all the network scenarios in the _networks_ folder have been uploaded and saved.
- To verify that all the network scenarios have been uploaded successfully, go to the MEC Sandbox UI. All the networks will appear in the dropdown menu on the right.
- Refer to the [network scenarios](./network-scenarios.md) guide for creating or uploading network scenarios
