Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Both Python and Java based Parser will not be updated in R6, the R6 release will use the same as previous release. 

  • The etsicatalog project provides package management service and parser service by Micro Service. It can be used to store packages distributed by the SDC, which then can be consumed by other projects or components, such as UUI, VF-C, SO etc. It also includes a TOSCA parser service.

Architecture  changes from E release:

VF-C catalog migrate to modeling etsicatalog repo which has reported in Architecture meeting 2019-10-15

Modeling project has created etsicatalog repo to intent to provide common ETSI catalog service, VF-C catalog migrates to modeling can help reduce duplication of work and promote unified architecture.

Migration plan:

  • VF-C catalog migrates to modeling etsicatalog repo and merges with modeling existing etsicatalog parser service and package management service.
  • To ensure compatibility, the APIs provided keep the same after migration , VF-C promises to update their interfaces call if needed.
  •  In F release, new requirements will be implemented in modeling etsicatalog , VF-C catalog is no longer maintained.

For more component description -  ARC Modeling Component Description – Frankfurt

New component capabilities for Frankfurt, i.e. the functional enhancements

...

  • Supports ETSI package APIs and storage for ETSI packages in runtime
  • Update version of Python as well as Django and djangorestframework
  • Improving platform maturity (TSC must have items) serverSystem JiraserverId4733707d-2057-3a0f-ae5e-4fd8aff50176key
    • SECCOM Perform Software Composition Analysis - Vulnerability tables(TSC must have) - 
    Jira Legacy 
    • SECCOM Password removal from OOM HELM charts(TSC must have) - 
    Jira LegacyserverSystem JiraserverId4733707d-2057-3a0f-ae5e-4fd8aff50176key 
    • SECCOM HTTPS communication vs. HTTP(TSC must have) -
    Based on the resource contribution -
    •  
    Jira LegacyserverSystem JiraserverId4733707d-2057-3a0f-ae5e-4fd8aff50176key 
    • Document current upgrade component strategy(TSC must have)  - 
    Jira LegacyserverSystem JiraserverId4733707d-2057-3a0f-ae5e-4fd8aff50176key

New or modified interfaces

...

  • Read vnfd:  GET /api/vnfpkgm/v1/vnf_packages/{vnfPkgId}/vnfd
  • Subscribe & Notify 

Modified interfaces:

  • Fetch VNF package from SDC:  POST /api/catalog/v1/vnfpackages, supports the ONBOARDING_PACKAGE directory for the original vendor ETSI package extraction
  • Update APIs to align SOL003/SOL005. 

...

Etsicatalog API naming is as followed:

  • Parser API: /api/parser/v1/

  • (etsicatalogAPIE-1) Catalog management API: /api/catalog/v1/

  • (etsicatalogAPIE-2) NSD management API: /api/nsd/v1 

  • (etsicatalogAPIE-3) VNF package management API: /api/vnfpkgm/v1

  • (etsicatalogAPIE-4) Parser API: /api/parser/v1/

Reference to the interfaces

etsicatalog_API_v1.yaml

What are the system limits

...