Uploaded image for project: 'Service Orchestrator'
  1. Service Orchestrator
  2. SO-2842

Support for SOL005 NBI API Handler

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Medium Medium
    • Guilin Release
    • None
    • Support for SOL005 NBI API Handler
    • To Do

      Preconditions:

      • ETSI SOL007 NS packages are onboarded into SDC and distributed to ETSI Catalog Manager.
      • In Guilin, we are testing SOL005-compliant requests, allowing the CLI-based SOL005 client sends SOL005 requests directly to SO NFVO in case the UUI - SO - E2E Workflows - NS Workflows - SOL005 Adapter sequences are NOT ready for Guilin.

      Provides SOL005-compliant Restful Northbound APIs for SO/SOL005 Adapter (P1)

      • Supports NS Lifecycle Management (LCM) APIs
        • Create NS  (POST “/api/nslcm/v1/ns_instances”)
        •  Instantiate NS (POST “/api/nslcm/v1/ns_instances/{nsInstanceId}/instantiate”)
        • Terminate NS (“/api/nslcm/v1/ns_instances/{nsInstanceId}/terminate”)
        • Delete NS (DELETE “/api/nslcm/v1/ns_instances/{nsInstanceId}”)
        • Get Operation Status ( GET /api/nslcm/v1/ns_lcm_op_occs, 
          • / api/nslcm/v1/ns_lcm_op_occs
      • Leverages SOL005 Swagger Files for SO NFVO SOL005 NBI API Handler
          • SOL005-NSLifecycleManagement-API.json
          • SOL005-NSLifecycleManagementNotification-API.json
        • This API Handler focuses on the SOL005 APIs, and its business logic is supplied by the NS LCM Microservice
      • Make SO-NFVO (so-etsi-nfvo) Pod is deployable in OOM

            byungwoojun byungwoojun
            byungwoojun byungwoojun
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: