Commit f2e0e2b8 authored by Kevin Di Lallo's avatar Kevin Di Lallo
Browse files

demo3 documentation fixes

parent b998de3f
Loading
Loading
Loading
Loading
+11 −0
Original line number Diff line number Diff line
@@ -55,6 +55,7 @@ To use Demo3 as an AdvantEDGE scenario container:
- Build & dockerize Demo3 server & frontend
- Import the provided scenario _demo3-scenario.yaml_
- Create a sandbox & deploy Demo3 scenario
- Start Demo3 application frontend in browser

### Build from source
To build _demo-frontend_ & _demo-server_ from source code:
@@ -86,6 +87,16 @@ cd ~/AdvantEDGE/examples/demo3
./dockerize.sh
```

### Deploy Demo3 scenario
After building & dockerizing the Demo3 application, the Demo3 scenario must be imported in AdvantEDGE and deployed within a sandbox.

### Start Demo3 application frontend
After deploying the Demo3 scenario, the Demo3 application frontend can be accessed as follows:
- _demo3-mep1_: `http://<AdvantEDGE IP address>:31111`
- _demo3-mep2_: `http://<AdvantEDGE IP address>:31112`

Each Demo3 application instance provides a pre-configured frontend with controls to register/deregister the application instance to MEC011 and to track terminal devices using MEC021.

## Using Demo3 with ETSI MEC Sandbox
To use Demo3 as an external application that interacts with the ETSI MEC Sandbox
- Build Demo3 server & frontend