:depth: 3
..
-\ **VNF Management Requirements for OpenO**
-
-**
-**
-
-**
-**
+**VNF Management Requirements for OpenO**
Introduction
============
1. .. rubric:: GVNFM Scenario
:name: gvnfm-scenario
- 1. \ **VNF Develop Steps**
+ 1. **VNF Develop Steps**
Aid to help the VNF vendor to fasten the integration with the GVNFM, the
OpenO provides the VNF SDK tools, and the documents. In this charter,
2. The monitoring and scale policy also be provide the next release.
- 1. \ **VNF Rest api**
+ 1. **VNF Rest api**
The VNF must provide a rest api to support initial configuration over
HTTP(s).
-1. \ **Set Initial Configuration**
+1. **Set Initial Configuration**
+-----------------+---------------------------------------------+
| If Definition | Description |
| | | | | VNF configurable properties. |
+-------------------+-------------+---------------+-----------------------------+---------------------------------------------+
-\ **CpConfiguration:**
+**CpConfiguration:**
+-------------+-------------+---------------+--------------+-----------------------------------------------------------------------------+
| Attribute | Qualifier | Cardinality | Content | Description |
| cpAddress | M | 1..N | CpAddress | Address and Port assigned to the CP. |
+-------------+-------------+---------------+--------------+-----------------------------------------------------------------------------+
-**
-**
**CpAddress:**
| | | | | Reserved |
+---------------------+-------------+---------------+------------------+-----------------------------------------------------------------------------------------------------+
-**
-**
-
**VnfConfigurableProperties:**
+----------------+-------------+---------------+-----------+-----------------------------------------------------------------------------------------------+
}
-1. \ **Response Code**
+1. **Response Code**
+-----------+-----------------------+-------------------------------------------------------+
| Code | Meaning | Description |
1. .. rubric:: SVNFM Scenario
:name: svnfm-scenario
- 1. \ **VNFM Driver Develop Steps**
+ 1. **VNFM Driver Develop Steps**
Aid to help the VNF vendor to fasten the integration with the NFVO via
Special VNFM, the OpenO provides the documents. In this charter, the
can be gotten in the charter 5.5. The interface of SVNFM is provided by
the VNF vendor self.
-1. \ **Create SVNFM Adaptor Mircoservice**
+1. **Create SVNFM Adaptor Mircoservice**
Some vnfs are managed by special vnfm, before add svnfm to openo, a
svnfm adaptor must be added to openo to adapter the interface of nfvo
A svnfm
-1. \ **Interfaces provided by SVNFM Driver**\
+1. **Interfaces provided by SVNFM Driver**
Interfaces use RESTful API and the format is as follows:
**juju**
-1. \ **Instantiate VNF**
+1. **Instantiate VNF**
+-----------------+--------------------------------------------------------------------+
| If Definition | Description |
| Direction | NSLCM->VNFMDriver |
+-----------------+--------------------------------------------------------------------+
-1. \ **Request**
+1. **Request**
+--------------------------+-------------+---------------+----------------------+---------------------------------------------------------------------------------------------------------------------------+
| Parameter | Qualifier | Cardinality | Content | Description |
| cpdId | M | 0..1 | String | Identifier of the external CPD in VNFD |
+----------------+-------------+---------------+-----------+------------------------------------------------------------------------------------------------------------------+
-**
-**
-
**VimInfo:**
+---------------------+---------------------+-----------------------+--------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
}
- “interfaceEndpoint”:”http://10.43.21.105:80/”
+ “interfaceEndpoint”:”<interface endpoint url>”
}
}
-1. \ **Response**
+1. **Response**
+-----------------+-------------+---------------+--------------+---------------------------------------------------------+
| Parameter | Qualifier | Cardinality | Content | Description |
}
-1. \ **Terminate VNF**
+1. **Terminate VNF**
+-----------------+----------------------------------------------------------------------------------------------+
| IF Definition | Description |
| Direction | NSLCM->VNFMDriver |
+-----------------+----------------------------------------------------------------------------------------------+
-1. \ **Request**
+1. **Request**
+------------------------------+-------------+---------------+----------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Qualifier | Cardinality | Content | Description |
}
-1. \ **Response**
+1. **Response**
+-------------+-------------+---------------+--------------+---------------------------------------------------------+
| Parameter | Qualifier | Cardinality | Content | Description |
}
-1. \ **Query VNF**
+1. **Query VNF**
+-----------------+------------------------------------------------------------------------------------+
| IF Definition | Description |
| Direction | NSLCM->VNFMDriver |
+-----------------+------------------------------------------------------------------------------------+
-1. \ **Request**
+1. **Request**
VNF filter: vnfInstanceId via url [R1]
-1. \ **Response**
+1. **Response**
+-------------+-------------+---------------+-----------+---------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Qualifier | Cardinality | Content | Description |
}
-1. \ **Get operation status**
+1. **Get operation status**
+-----------------+-------------------------------------------------------------------------------------------------------+
| IF Definition | Description |
| Direction | NSLCM->VNFMDriver |
+-----------------+-------------------------------------------------------------------------------------------------------+
-1. \ **Request**
+1. **Request**
None
-1. \ **Response**
+1. **Response**
+-----------------------+-------------+---------------+---------------+--------------------------------------------------------------------------------------+
| Parameter | Qualifier | Cardinality | Content | Description |
}
-1. \ **Scale VNF**
+1. **Scale VNF**
+-----------------+------------------------------------------------------------------------------------------+
| If Definition | Description |
| Direction | NSLCM->VNFMDriver |
+-----------------+------------------------------------------------------------------------------------------+
-**
-**
-
1. **Request**
+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+---------------+----------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| | | | | |
| | | | | **Reserved** |
+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+---------------+----------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| NOTE 1: ETSI GS NFV-IFA 010 `[2] <#_bookmark7>`__ specifies that the lifecycle management operations that expand or contract a VNF instance include scale in, scale out, scale up and scale down. Vertical scaling (scale up, scale down) is not supported in the present document. |
-| |
-| SCALE\_IN designates scaling in. |
-| |
-| SCALE\_OUT 1 designates scaling out. |
-| |
-| NOTE 2: A scaling step is the smallest unit by which a VNF can be scaled w.r.t a particular scaling aspect. |
+| NOTE 1: ETSI GS NFV-IFA 010 `[2] <#_bookmark7>`__ specifies that the lifecycle management operations that expand or contract a VNF instance include scale in, scale out, scale up and scale down. Vertical scaling (scale up, scale down) is not supported in the present document. |
+| |
+| SCALE\_IN designates scaling in. |
+| |
+| SCALE\_OUT 1 designates scaling out. |
+| |
+| NOTE 2: A scaling step is the smallest unit by which a VNF can be scaled w.r.t a particular scaling aspect. |
+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+---------------+----------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
{
“RequestId”:”8279-abcd-aksdj-19231”,
- “CallbackUrl”:”https://callback.onap:9333”
+ “CallbackUrl”:”<callback url>”
},
| | | | |
| | - It is recommended that the load Playbook API be a REST API. | | |
+----------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------+------------+
-| | Request API: The Ansible Server must expose a REST endpoint that accepts a POST message to request execution of the playbook (e.g., https://ansible.test.att.com:8080). The POST request must be a JSON block as outlined in Table D2. | Must | D1060 |
+| | Request API: The Ansible Server must expose a REST endpoint that accepts a POST message to request execution of the playbook. The POST request must be a JSON block as outlined in Table D2. | Must | D1060 |
+----------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------+------------+
| | When the Ansible server accepts an authenticated request to execute a playbook, it is required to send back an initial response indicating whether the request is accepted or rejected. The response must be a JSON Object with the key value pairs as described in Table D3. | Must | D1070 |
+----------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------+------------+
-| | Result API: If the Ansible Server accepts a request to execute a playbook, it must make available status of the execution of the playbook at a Results REST endpoint indexed by the Id in the request in the form <url>?Id=<RequestId>&Type=GetResult where <url> is the URL used for submitting requests. For example, https://ansible.test.att.com?Id=10&Type=GetResult. | Must | D1080 |
+| | Result API: If the Ansible Server accepts a request to execute a playbook, it must make available status of the execution of the playbook at a Results REST endpoint indexed by the Id in the request in the form <url>?Id=<RequestId>&Type=GetResult where <url> is the URL used for submitting requests. | Must | D1080 |
+----------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------+------------+
| | When a GET is invoked against the Results REST endpoint, the Ansible Server must reply with an appropriate response: | Must | D1090 |
| | | | |
Code Review / vnfrqts / guidelines.git / commitdiff