diff options
| -rw-r--r-- | docs/Chapter5.rst | 61 |
1 files changed, 60 insertions, 1 deletions
diff --git a/docs/Chapter5.rst b/docs/Chapter5.rst index 5dbc6fe..13fc058 100644 --- a/docs/Chapter5.rst +++ b/docs/Chapter5.rst @@ -3201,4 +3201,63 @@ load balancer and “db” for database. properties: ... scheduler\_hints: - group: {get\_param: lb\_server\_group}
\ No newline at end of file + group: {get\_param: lb\_server\_group} + + +d. 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 +develop steps for VNF vendors will be introduced. + +First, using the VNF SDK tools to design the VNF with TOSCA model and +output the VNF TOSCA package. The VNF package can be validated, and +tested. + +Second, the VNF vendor should provide SVNFM Driver in the OpenO, which +is a micro service and in duty of translation interface from NFVO to +SVNFM. The interface of NFVO is aligned to the ETSI IFA interfaces and +can be gotten in the charter 5.5. The interface of SVNFM is provided by +the VNF vendor self. + +e. 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 +and svnfm. + +A svnfm adaptor is a micro service with unique name and an appointed +port, when started up, it must be auto registered to MSB(Micro server +bus),following describes an example rest of register to MSB: + +POST /openoapi/microservices/v1/services + + { + + "serviceName": "catalog", + + "version": "v1", + + "url": "/openoapi/catalog/v1", + + "protocol": "REST", + + "visualRange": "1", + + "nodes": [ + + { + + "ip": "10.74.56.36", + + "port": "8988", + + "ttl": 0 + + } + + ] + + }
\ No newline at end of file |