summary |
shortlog |
log |
commit | commitdiff |
review |
tree
raw |
patch |
inline | side by side (from parent 1:
107bef4)
Changing the release to refer to the current release.
Change-Id: I57018866aa955a0977e9471c07e41ce88fe0304c
Issue-ID: VNFRQTS-218
Signed-off-by: Bozawglanian, Hagop (hb755d) <hb755d@att.com>
developer needs to know to operate and be compliant with ONAP.
- Requirements that are not applicable to VNF/PNF providers such as those
that applicable to service providers are not included in this document.
developer needs to know to operate and be compliant with ONAP.
- Requirements that are not applicable to VNF/PNF providers such as those
that applicable to service providers are not included in this document.
-- These requirements are applicable to the Amsterdam release of ONAP.
+- These requirements are applicable to the current release of ONAP.
- Scope of the ONAP versions/release and future functionality
- The VNF Requirements should include support for the functionality of the
ONAP E-E use cases.
- Scope of the ONAP versions/release and future functionality
- The VNF Requirements should include support for the functionality of the
ONAP E-E use cases.