sonata-nfv / tng-api-gtw Goto Github PK

The feature is developed, we need to test it's integration

Was to tng-gtk-sp

These two need to be distinguished from the later to be added /records/test-results

Depends on #32

This endpoint shall provide to it's consumers a list of available endpoints.

This features creates a strong dependency with those modules... a WiP.

• add /services andpoint
• use /api/v1 (instead of v3)

To create an NST do this:

curl -i -H "Content-Type:application/json" -X POST -d'{"name":"Rubik_NST", "version":"<version_number>", "author":"<author_name>", "vendor":"<vendor_name>", "nstNsdIds":[{"NsdId":"<network_service_ID>"}]}' pre-int-sp-ath.5gtango.eu:32002/api/nst/v1/descriptors

Valid NST example:

{
  "designer": "Pol",
  "id": "30ef541d-24ee-4ec3-8c00-f53b4a3791cb",
  "name": "Rubik_NST",
  "notificationTypes": "",
  "nstNsdIds": [
    "6a01afdc-9d42-4bc9-866c-a8a3868fdf5e"
  ],
  "onboardingState": "ENABLED",
  "operationalState": "ENABLED",
  "usageState": "NOT_IN_USE",
  "userDefinedData": "",
  "vendor": "5gTango",
  "version": "1.0"
}

Endpoint agreed with @mpeuster: …/packages/status/:process_uuid (sonata-nfv/tng-sdk-package#49 and sonata-nfv/tng-gtk-common#22)

Depends on #32

E.g., http "pre-int-vnv-bcn.5gtango.eu:32002/api/v3/packages?name=ns-package-example&vendor=eu.5gtango&version=0.1" returns []

Include page and page_size query parameters

Depends on #32

When the path is not found, [400, {}, ["Error finding GET"]] is being returned, instead of raising an exception

From user story #225

Now that there's a basic capability of routing input to output, let's improve it

Depends on #32. Current implementation gives modules/mico-services the same mechanism as human users: a token that expires with time. This is not practical: we want users to be able to generate API tokens that can be used without such time restrictions. The user can renew his/her API keys in the Portal or through the API (with the old key). These API tokens can then be used to authenticate/authorize the user's module (e.g., SDK, OSS, ...) to access the V&V/SP.

Consider this endpoint: curl -H "Content-type:application/json" http://localhost:8080/tng-sla-mgmt/api/slas/v1/mgmt/guaranteesList

Currently still going to a file, we want it in the STDOUT (STDERR)

• update the README
• write integration tests

The Portal needs the options method. In SONATA we did the following:

    options '/?' do
      response.headers['Access-Control-Allow-Origin'] = '*'
      response.headers['Access-Control-Allow-Methods'] = 'POST,PUT'      
      response.headers['Access-Control-Allow-Headers'] = 'Content-Type, Access-Control-Allow-Headers, Authorization, X-Requested-With'
      halt 200
    end

According to the 2018-03-12 call:

• POST /descriptors (where JSON object is a nst_content)
• GET /descriptors/{nstId}
• DELETE /descriptors/{nstId}
• POST /nsi
• GET /nsi
• GET /nsi/{nsiId}
• DELETE /nsi/{nsiId}
• POST /nsi/{nsiId}/terminate

.../api/v3/packages/status/1234... is not being correctely translated into .../packages/status/1234...

Check w/ @peusterm how to deal with process_uuid simultaneously with package_uuid

Do a README-Driven-Design...

Extract son-gtkusr from son-gkeeper, as well as its dependencies, to be used here.

tng-sla-mgmt/api/slas/v1/agreements/
GET and DELETE

developer, customer or admin are currently hard-coded, and shouldn't