Update docs

This clause provide a set of usefull K8s command lines for debugging micro-service and demo applications.

The commands (and their outputs) are just examples: 

- <i>yannsb</i> is the Sandbox named

- <i>demo4sb</i> is the Sandbox named

- <i>meep-dai</i> is the DAI (MEC-016) micro-services.

They have to be modified based of the existing list of pods.

- To retrieve pod descriptions such as internal IP address, Volumes...

```bash

$ kubectl describe pod meep-dai-8fb98975b-6jf9p -n yannsb

$ kubectl describe pod meep-dai-8fb98975b-6jf9p -n demo4sb

```

- To retrive pod logs into a text file named out_dai.txt

```bash

$ kubectl logs meep-dai-8fb98975b-6jf9p -n yannsb > out_dai.txt

$ kubectl logs meep-dai-8fb98975b-6jf9p -n demo4sb > out_dai.txt

```

- To retrive pod's container logs into a text file named out_demo.txt

```bash

$ kubectl logs demo4-ue1-7f8c7d8746-9vv7m demo4-ue1 -n yannsb > out_demo.txt

$ kubectl logs demo4-ue1-7f8c7d8746-9vv7m demo4-ue1 -n demo4sb > out_demo.txt

```

This request retrieves the UE application description

- GET /dai/apps

This request retrieves the list of the available onboarded MEC application (see MEC-016 Clause )

This request retrieves the list of the available onboarded MEC application (see MEC-016 Clause 5.1.2 User application look-up)

- POST /dai/instantiate

This is a request to create a new onboarded MEC application context and to instiate it (see MEC-016 Clause )

This is a request to create a new onboarded MEC application context and to instiate it (see MEC-016 Clause 5.1.3 Application context create)

- GET /dai/doping

This is a ping/pong request to the instantiated MEC application (see previous command)

- DELETE /dai/delete/{instance}

This is a request to delete the specified onboarded MEC application context and to un-instiate it (see MEC-016 Clause )

This is a request to delete the specified onboarded MEC application context and to un-instiate it (see MEC-016 Clause 5.1.4 Application context delete)

## Generate backend code

### Current issues

- demo4-ue: Swagger does not work (404 Not Found) for http://mec-platform.etsi.org/yannsb/demo4-ue/api/

- demo4-ue: Swagger does not work (404 Not Found) for http://mec-platform.etsi.org/demo4sb/demo4-ue/api/

- meep-dai-mgr testing to be enhanced with a fake onboarded MEC application

- meep-dai testing to be reviewed

- Enhancement of process execution (logging, termination...)

## Updating meep-dai/bin/onboardedapp

$ curl "http://mec-platform.etsi.org:31111/info/logs" -H "accept: application/json"

```

The following command retrieves the list of onboarded MEC applications (see MEC-016 Clause ):

The following command retrieves the list of onboarded MEC applications (see MEC-016 Clause 5.1.2 User application look-up):

```bash

$ curl "http://mec-platform.etsi.org:31111/dai/apps" -H "accept: application/json"

```

The following command request the creation of a new AppContext (see MEC-016 Clause ):

The following command request the creation of a new AppContext (see MEC-016 Clause 5.1.3 Application context create):

```bash

$ curl -X POST "http://mec-platform.etsi.org:31111/dai/instantiate" -H "accept: application/json"

```

The following command request the deletions of the specified onboarded MEC applications (see MEC-016 Clause ):

The following command request the deletions of the specified onboarded MEC applications (see MEC-016 Clause 5.1.4 Application context delete):

```bash

$ curl -X DELETE "http://mec-platform.etsi.org:31111/dai/delete/10" -H "accept: application/json"

```

TODO: /dai/doping

The following command request a ping and expect a "pong" response:

```bash

$ curl "http://mec-platform.etsi.org:31111/dai/doping" -H "accept: application/json"

```