Merge pull request #6 from idcc-dev/sp_sprint21_demo_app

# Demo1

A simple scenario used to showcase platform capabilities.

This has two applications _iperf server_ and _demo server_ deployed across multiple tiers of the network (fog/edge/cloud).

This scenario is composed of three applications (_iperf-server_, _iperf-proxy & _demo-server_) deployed across multiple tiers of the network (fog/edge/cloud).

- The _iperf-server_ is the standard open-source _iperf-server_ that is containerized; it runs in the AdvantEDGE platform. It is used to generate traffic between the internal & external UE. The demo scenario contains multiple instances of the _iperf-server_ deployed across various tiers of the network. The _iperf-server_ image form the public iperf registry is used in this demo.

- _iperf-proxy_ is a small server application runs on the host machine. It allows to control the local host iperf-client from the demo web-client. The demo scenario runs a single instance of the _iperf-proxy_. Source code is available in this repo; _iperf-proxy_ is built as part of this demo.

- _demo-server_ is an edge application that is containerized; it runs in the AdvantEDGE platform. It has been developed to demonstrate AdvantEDGE capabilities. The demo scenario contains multiple instances of _demo-server_ deployed across various tiers of the network. Source code is available in this repo;_demo-server_ is built as part of this demo.

It has two clients (internal & external) that communicate with the servers.

Internal client traffic is iperf only and has no GUI.

```

> Demo Application binaries are dockerized (containerized) and the container images are stored in the local Docker registry.<br> Next time you want to use the demo scenario; demo application containers will be available

#### Source code compilation

Compiling from source code is available through the command:

```

cd ~/AdvantEDGE/examples/demo1/

./build-demo1.sh

```

> As a result, both the iperf-proxy and demo-server app are compiled and demo-server is dockerized

#### Configure demo specific dashboards

Only need to do it once, or when the demo dashboard changes

Follow the procedure described in [Configuring Monitoring](../../docs/use/monitoring.md#configure-dashboards) and import the demo specific dashboard from `AdvantEDGE/examples/demo1/demo1-dashboards.json`

Follow the procedure described in [Configuring Monitoring](../../docs/use/monitoring.md#configure-dashboards). The demo specific dashboard that is loaded can also be found at `AdvantEDGE/examples/demo1/demo1-dashboards.json`

> Demo specific dashboards are stored in Kibana.<br> Next time you want to use the demo scenario; demo specific dashboard will be available.

#!/bin/sh

# Get full path to script directory

SCRIPT=$(readlink -f "$0")

BASEDIR=$(dirname "$SCRIPT")

# Set GO env variables

GOOS=linux

# Create vendor folder

cd $BASEDIR/../../src/demo-server

go mod vendor

# Build demo App server

echo "Building Demo Service Go Server"

cd $BASEDIR/../../src/demo-server

go build -o $BASEDIR/demo-server .

                        </div>

                        <div>

                                <img id="demo-svc-app-pic" src="xxxHTMLLINKxxx0.8942158728881140.49200954424091226xxx" alt="">

                                <img id="demo-svc-app-pic" src="xxxHTMLLINKxxx0.52067726991078960.42262496559595353xxx" alt="">

                        </div>

                    </div>

                </div>