diff options
| author |   rr929y <rr929y@att.com> | 2017-08-25 13:01:29 -0500 |
|---|---|---|
| committer | rr929y <rr929y@att.com> | 2017-08-25 13:01:29 -0500 |
| commit | 6d9c0db073dad028f60956f1be6887e64bf4e33b (patch) | |
| tree | b87ede8dbbcd4b987bacc00bfe2421bd530cd308 /docs | |
| parent | 5a0b2f1eff3cc48a0232ff71c8e4510a65713ccd (diff) | |
VNFRQTS Requirements - Chapter 2
VNFRQTS Requirements - Adding Chapter 2 content
Change-Id: Iff33df216517f3fe1dd41a069d09cea1eff52af6
Issue-ID:VNFRQTS-59
Signed-off-by: rr929y <rr929y@att.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/Chapter2.rst | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/docs/Chapter2.rst b/docs/Chapter2.rst index 42b13f2..a1effee 100644 --- a/docs/Chapter2.rst +++ b/docs/Chapter2.rst @@ -1,2 +1,7 @@ **2. Scope** -============
\ No newline at end of file +============ +- The audience for this document are VNF providers, NCSPs and other interested 3rd parties who need to know the design, build and lifecycle management requirements for VNFs to be compliant with ONAP. +- These requirements are strictly from a standpoint of what the VNF developer needs to know to operate and be compliant with ONAP. +- Requirements that are not applicable to VNF 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. +- Scope of the ONAP versions/release and future functionality
\ No newline at end of file |