Unibo MEC API Tester

The Unibo MEC API Tester is a web-based application used to test the API capabilities of a MEC Platform. It could be a useful tool to quickly and easily test the compliance of the APIs provided by a MEC Platform with the ones ETSI standardized in the MEC ISG. Or simply to setup a basic MEC application to debug a MEC ready infrastructure. Right now only supports MEC 011 API calls.

Application design

This application is composed of a web server that communicates with the MEC platform, exposing an easy to use web interface.

The webserver does not need any configuration besides from the infrastructure ones such as application-id (an identifier the MEC platform assigns to the application once deployed) and the MEC endpoint (the MEC platform IP address and port in form of an HTTP URL) which are required to perform the API calls.

Installation

The application is built inside a Docker container image. Therefore to execute it you need to compile the docker images, put them on a reachable image repository (or use the local one)

$ sudo apt-get install docker.io

To do so you can use the helper script build.sh placed in the docker-application directory. You can use the run.sh or run-local.sh scripts to compile and run the application in a single step. Otherwise you can issue a docker build command in the docker-application directory

# ./run-local.sh

Kubernetes Build

The application has also a kubernetes descriptor unibo-test-mec.yml. You can import this file and modify it accordingly to put it on your Kubernetes cluster.

The run.sh script will generate the required image and instantiate it in the default Kubernetes cluster configured previously (a standard installation would be sufficient). The script runs without parameters:

# ./run.sh

Usage

The application is designed to be deplyed with small-to-any configuration. Besides that, a little configuration is required to make it interacts with the MEC platform. To do so, start the application using the preferred method described above. For instance, to start it with docker you can simply run:

# ./run-local.sh

After this step, navigate with a web browser to your docker container endpoint (usually it would be at the IP 172.17.0.2, but it can vary depending on your configuration).

After reaching the webserver, go to the configuration tab.

Configure all the fields according to your needs. After that you can start to check the functions of your MEC application or server using the various tabs and buttons.

For instance, if you want to retrieve the DNS configuration associated with your application you can click on the button "DNS Rules" in the "DNS rules" tab.

MEC simulation

To simulate a dummy MEC platform, you can use the docker-img-mec image which can be built and run using the run-mec.sh script with no parameters.

Implemented MEC 011 APIs

API Method and URL	Implemented	Notes	Description URL
GET /applications/{appInstanceId}/subscriptions	✔️		Forge ETSI
POST /applications/{appInstanceId}/subscriptions	✔️		Forge ETSI
GET /applications/{appInstanceId}/subscriptions/{subscriptionId}			Forge ETSI
DELETE /applications/{appInstanceId}/subscriptions/{subscriptionId}	✔️		Forge ETSI
GET /applications/{appInstanceId}/services	✔️		Forge ETSI
POST /applications/{appInstanceId}/services	✔️		Forge ETSI
GET /applications/{appInstanceId}/services/{serviceId}			Forge ETSI
PUT /applications/{appInstanceId}/services/{serviceId}			Forge ETSI
DELETE /applications/{appInstanceId}/services/{serviceId}	✔️		Forge ETSI
GET /services			Forge ETSI
GET /services/{serviceId}			Forge ETSI
GET /transports	✔️		Forge ETSI
GET /applications/{appInstanceId}/traffic_rules	✔️		Forge ETSI
GET /applications/{appInstanceId}/traffic_rules/{trafficRuleId}			Forge ETSI
PUT /applications/{appInstanceId}/traffic_rules/{trafficRuleId}	✔️	Supports only state modification	Forge ETSI
GET /applications/{appInstanceId}/dns_rules	✔️		Forge ETSI
GET /applications/{appInstanceId}/dns_rules/{dnsRuleId}			Forge ETSI
PUT /applications/{appInstanceId}/dns_rules/{dnsRuleId}	✔️	Supports only state modification	Forge ETSI
GET /applications/{appInstanceId}/subscriptions	✔️		Forge ETSI
POST /applications/{appInstanceId}/subscriptions	✔️		Forge ETSI
GET /applications/{appInstanceId}/subscriptions/{subscriptionId}			Forge ETSI
DELETE /applications/{appInstanceId}/subscriptions/{subscriptionId}	✔️		Forge ETSI
POST /applications/{appInstanceId}/confirm_termination			Forge ETSI
POST /applications/{appInstanceId}/confirm_ready	✔️	Notification via the red LED	Forge ETSI
GET /timing/timing_caps	✔️		Forge ETSI
GET /timing/current_time	✔️	Only application timestamp, no NTP and PTP support	Forge ETSI