diff options
author | 2017-09-01 10:12:47 +0800 | |
---|---|---|
committer | 2017-09-01 10:12:47 +0800 | |
commit | c68ec4198d86162dabcadb388a9f653784a731a5 (patch) | |
tree | 1279a7584016b18a3ba0194e4d6950c9d3737137 /docs/Chapter7.rst | |
parent | d21906736fcc735feb49b5243928c89eb9fcdf78 (diff) |
Move configuration part of seed doc of open-o
Change-Id: Icb15d3566f4f6d9bc804bc524c6c517601b9695a
Issue-Id: VNFRQTS-39
Signed-off-by: fengyuanxing <feng.yuanxing@zte.com.cn>
Diffstat (limited to 'docs/Chapter7.rst')
-rw-r--r-- | docs/Chapter7.rst | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/docs/Chapter7.rst b/docs/Chapter7.rst index dab0d61..6803197 100644 --- a/docs/Chapter7.rst +++ b/docs/Chapter7.rst @@ -526,9 +526,12 @@ VNF REST APIs Healthcheck is a command for which no NETCONF support exists. Therefore, this must be supported using a RESTful interface which we have defined. -The VNF must provide a REST formatted GET RPCs to support Healthcheck +The VNF via APP-C must provide a REST formatted GET RPCs to support Healthcheck queries via the GET method over HTTP(s). +The VNF via VF-C must provide REST APIs to make the configurations of +associated VNFs. + The port number, url, and other authentication information is provided by the VNF vendor. @@ -583,6 +586,9 @@ by the VNF vendor. | | | | | | | } | | | +-----------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------+------------+ +| REST APIs | **/configuration** This API executes a vendor-defined VNF configuration action over the scope of the entire VNF(e.g if there are multiple VMs, then run configuration on all VMs according to the input parameters). | Must | 12200 | +| | **/configuration** returns a 201 Created if the configuration succeeds or a 4XX/5XX response if it fails. A JSON object is returned indicating the outcome of the VNF configuration including all the necessary configuration info. | | | ++-----------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------+------------+ Chef Standards and Capabilities ------------------------------- |