Commit 06d47519 authored by Yann Garcia's avatar Yann Garcia
Browse files

Update learning-guide with MEC-016

parent 2f71e8fa

Feature-Development-Guide/learning-guide.md

+37 −0
Original line number Diff line number Diff line
@@ -364,3 +364,40 @@ From learning perspective, developers can play around with the deployed MEC Sand 
There will be an added advantage of being able to inspect container logs from different micro-services in the backend, combined with monitoring dashboards for statistics in real time.



This level of understanding will provide a solid foundation for working on the development of a new feature, i.e., implementing a new MEC service in the MEC Sandbox. See [Development Guide](./development-guide.md) for the next steps in this feature development journey.



## Host NFS and k8s pods filesystem sharing



### Deploying NFS on host



1. Install the NFS server

```bash

$ sudo apt install nfs-kernel-server nfs-common portmap

```

2. Verift the installation

```bash

$ sudo systemctl status nfs-server

```

3. Create the shared folder

```bash

$ sudo mkdir -p /mnt/nfs/mec_sandbox

$ sudo chmod -R 777 /mnt/nfs/

```

4. Create the /etc/exports file 

```bash

$ sudo echo '/mnt/nfs/mec_sandbox  *(rw,sync,no_subtree_check,no_root_squash,insecure)' > /etc/exports

```

5. Apply the /etc/exports settings

```bash

$ sudo exportfs -rv

```

6. Verify the NFS exports

```bash

$ sudo showmount -e

```



### Creating Persistant Volume and Persistant Volume Claim







### Updating Deployment

Macro-Network-Scenario/MEC016.md

+3 −3
Original line number Diff line number Diff line 
# MEC016 - Device application interface

> _Updated by STF625_

> _Updated by STF678_



This section describes how MEC016, DAI operations within the MEC Sandbox.
@@ -10,12 +10,12 @@ Query endpoints and subscriptions that are not supported in the MEC Sandbox are 
| Yes | `/app_list`  | To retrieve information on available application information |

| Yes | `/app_contexts`   | To create a new application context. Upon success, the response contains entity body describing the created application context |

| Yes | `/app_contexts/{contextId}`   | To update an existing apllication context |

| Tes | `/obtain_app_loc_availability` | To allow a device application to obtain information on locations available for instantiation of a specific user application in the MEC system |

| Yes | `/obtain_app_loc_availability` | To allow a device application to obtain information on locations available for instantiation of a specific user application in the MEC system |



## MEC 016 v2.2.1 (published, available on forge)



References:

* https://www.etsi.org/deliver/etsi_gs/MEC/001_099/016/02.02.01_60/gs_MEC016v020201p.pdf

* https://www.etsi.org/deliver/etsi_gs/MEC/001_099/016/03.01.01_60/gs_mec016v030101p.pdf

* https://forge.etsi.org/rep/mec/gs016-dev-app-api.git

* https://redocly.github.io/redoc/?url=https://forge.etsi.org/rep/mec/gs016-dev-app-api/-/raw/v2.2.1-OAS3.1/UEAppInterfaceApi.yaml