Bugs fixed on meep-dederation during TTF T043 validation

MEC Sandbox provides the user with a choice of scenarios combining different network technologies (4G, 5G, Wi-Fi) and

terminal types. Combining these assets in a geolocated environment, a user can gain hands-on experience on the behaviour

and capabilities of the Location (MEC013), Radio Network Information (MEC012), Traffic Management APIs (MEC015), Device Application Interface (MEC016),

WLAN Information (MEC028), Edge Platform Application Enablement (MEC011) and Application Mobility (MEC021) service APIs. Such contextual information can offer

WLAN Information (MEC028), Edge Platform Application Enablement (MEC011) and Application Mobility (MEC021) service APIs, V2X Information API (MEC030) service API and  MEC Federation Service API (MEC040) service APIs. Such contextual information can offer

significant differential performance for edge based MEC applications.

Application Enablement (MEC011) and Application Mobility (MEC021) service APIs. Such contextual information can offer

significant differential performance for edge based MEC applications.

     - Ubuntu 18.04: `sudo apt install python-pip`

     - Ubuntu 20.04: `sudo apt install python3-pip`

   - Install Pyyaml: `pip install pyyaml`

1. Host NFS server installation

In order to be deployed properly, MEC 016 service requires that an NFS server was deployed on the host. To achieve it, the followimg steps are required:

- Install the NFS server

```sh

$ sudo apt-get update

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

```

- Check that the NFS server is running on the host

```sh

$ sudo systemctl status nfs-server

```

The outpout looks like:

```

nfs-server.service - NFS server and services

     Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled)

     Active: active (exited) since Mon 2024-09-16 09:10:45 CEST; 42s ago

   Main PID: 923678 (code=exited, status=0/SUCCESS)

      Tasks: 0 (limit: 38358)

     Memory: 0B

     CGroup: /system.slice/nfs-server.service

```

- Create the NFS shared folder

```sh

$ sudo mkdir -p /mnt/nfs/mec_sandbox

$ sudo chmod -R 777 /mnt/nfs/

```

- Update the /etc/exports file by adding the following line:

```sh

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

```

- Export the NFS shared folder

```sh

$ sudo exportfs -rv

```

- Check that the NFS shared folder is exported

```sh

$ showmount -e

```

### Deploy Long-term Storage (MinIO + Thanos Compactor)

  description: "ETSI GS MEC 040 Federation enablement API, v3.2.1"

  url: https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.02.01_60/gs_MEC040v030201p.pdf

servers:

- url: https://localhost/sandboxname/fed_enablement/v1

- url: https://localhost/sandboxname/sandboxname/sandboxname/sandboxname/fed_enablement/v1

tags:

- name: systemInfo

- name: subscription

        x-exportParamName: Path.serviceId

      responses:

        "200":

          description: "Upon success, a response body containing data type describing the specific subscription data type is returned."

          description: "Upon success, a response body containing data type describing\

            \ the specific subscription data type is returned."

          content:

            application/json:

              schema:

        \ as a part of the \nUpdate of MEC system(s) to the federation.\n"

    EndPointInfo:

      title: EndPointInfo

      type: object

      properties:

        uris:

          type: array

          description: "Entry point information of the service as string, formatted\

            \ according to URI syntax (see IETF RFC 3986 [8]). Shall be used for REST\

            \ APIs. See note."

          items:

            type: string

      description: "Endpoint information (e.g. URI, FQDN, IP address) of MEC federator."

        fqdn:

          type: array

          description: Fully Qualified Domain Name of the service. See note.

          items:

            type: string

        addresses:

          type: array

          items:

            $ref: '#/components/schemas/Addresses'

        alternative:

          type: string

          description: "Entry point information of the service in a format defined\

            \ by an implementation, or in an external specification. See\_note."

      description: "NOTE: Exactly one of \"uris\", \"fqdn\", \"addresses\" or \"alternative\"\

        \ shall be present. \n"

      example:

        uris:

        - uris

        - uris

        addresses:

        - port: 0

          host: host

        - port: 0

          host: host

        fqdn:

        - fqdn

        - fqdn

        alternative: alternative

    Addresses:

      required:

      - host

      - port

      type: object

      properties:

        host:

          type: string

          description: Host portion of the address.

        port:

          type: integer

          description: Port portion of the address.

      description: Entry point information of the service as one or more pairs of

        IP address and port. See note.

      example:

        port: 0

        host: host

    SystemUpdateNotificationSubscription:

      title: SystemUpdateNotificationSubscription

      required:

/*

 * Copyright (c) 2022 ETSI.  All rights reserved.

 * Copyright (c) 2022-2025 ETSI.  All rights reserved.

 */

// Version

/*

 * Copyright (c) 2022 ETSI.  All rights reserved.

 * Copyright (c) 2022-2025 ETSI.  All rights reserved.

 */

import React, { Component } from 'react';

/*

 * Copyright (c) 2022 ETSI.  All rights reserved.

 * Copyright (c) 2022-2025 ETSI.  All rights reserved.

 */

import _ from 'lodash';