We deployed vfc and modeling to confirm about the status of compliance with SOL003 of NFVO feature in ONAP.
We basically used the following page as a guide to deploy.
https://docs.onap.org/projects/onap-vfc-nfvo-lcm/en/montreal/platform/installation/installation/index.html

We confirmed the connectivity of the following interfaces required from VNFM to NFVO as defined in SOL003 v3.3.1.

• {apiRoot}/grant/v1/grants

• {apiRoot}/vnfpkgm/v2/vnf_packages

• {apiRoot}/vnfpkgm/v2/onboarded_vnf_packages

However, the result is that none of the above APIs are supported.

The following is a log of the actual API submission:

• grant

  root@k8s-masternode:~# curl http://10.10.0.50:30283/api/grant/v1/grants   502 Bad Gateway   error message:No route found for this request!   nginx

• vnfpkgm

  • vnf_packages

    root@k8s-masternode:~# curl http://10.10.0.50:30283/api/vnfpkgm/v2/vnf_packages     502 Bad Gateway     error message:No route found for this request!     nginx

•  

  • onboarded_vnf_packages

    root@k8s-masternode:~# curl http://10.10.0.50:30283/api/vnfpkgm/v2/onboarded_vnf_packages     502 Bad Gateway     error message:No route found for this request!     nginx

By the way, vnfpkgm seems to support vnf_packages URIs in v1, but not onboarded_vnf_packages URIs in v1.

The following is a log of the actual API submission:

• {apiRoot}/vnfpkgm/v1/vnf_packages

  root@k8s-masternode:~# curl http://10.10.0.50:30283/api/vnfpkgm/v1/vnf_packages/8cd8ab44-fa7d-4883-bb0d-f9edd5bf49b7   {"id":"8cd8ab44-fa7d-4883-bb0d-f9edd5bf49b7","vnfdId":null,"vnfProductName":null,"vnfSoftwareVersion":null,"vnfdVersion":null,    "softwareImages":null,"additionalArtifacts":null,"onboardingState":"CREATED","operationalState":"DISABLED","usageState":"NOT_IN_USE",    "userDefinedData":null,"_links":{"self":{"href":"/api/vnfpkgm/v1/vnf_packages/8cd8ab44-fa7d-4883-bb0d-f9edd5bf49b7"}}}

• {apiRoot}/vnfpkgm/v1/onboarded_vnf_packages

  root@k8s-masternode:~# curl http://10.10.0.50:30283/api/vnfpkgm/v1/onboarded_vnf_packages   Page not found (404)   Request Method: GET   Request URL: http://10.10.0.50:80/api/vnfpkgm/v1/onboarded_vnf_packages   Using the URLconf defined in catalog.urls, Django tried these URL patterns, in this order:   1. ^api/catalog/v1/admin   ...(omit)...   26. ^ ^api/vnfpkgm/v1/vnf_packages$ [name='vnf_packages_rc']   27. ^ ^api/vnfpkgm/v1/vnf_packages/(?P<vnfPkgId>[0-9a-zA-Z\-\_]+)$ [name='vnf_package_rd']   28. ^ ^api/vnfpkgm/v1/vnf_packages/(?P<vnfPkgId>[0-9a-zA-Z\-\_]+)/vnfd$ [name='vnfd_rd']   29. ^ ^api/vnfpkgm/v1/vnf_packages/(?P<vnfPkgId>[0-9a-zA-Z\-\_]+)/packa nt$ [name='package_content_ru']   30. ^ ^api/vnfpkgm/v1/vnf_packages/(?P<vnfPkgId>[0-9a-zA-Z\-\_]+)/packa nt/upload_from_uri$ [name='upload_from_uri_c']   31. ^ ^api/vnfpkgm/v1/subscriptions$ [name='subscriptions_create_query']   32. ^ ^api/vnfpkgm/v1/subscriptions/(?P<subscriptionId>[0-9a-zA-Z\-\_]+ [name='subscriptions_query_terminate']   33. ^ ^api/vnfpkgm/v1/vnf_packages/(?P<vnfPkgId>[0-9a-zA-Z\-\_]+)/artif <artifactPath>[0-9a-zA-Z\-\_.]+)$ [name='fetch_vnf_artifacts']   ...(omit)...   44. ^ ^api/catalog/v1/redoc$ [name='schema-redoc']   The current path, api/vnfpkgm/v1/onboarded_vnf_packages, didn't ma of these.