I plan to initially sort out this NFV specification this week, come on.
Summary of content:
This standard formulates the main business processes related to the Network Function Virtualization Orchestrator (NFVO), including the VNF life cycle management process and the network service life cycle management process.
1.1 System operation mode
Currently, there are two NFVO-VNFM-VIM interaction models based on resource configuration methods:
1) Indirect Mode (Indirect Mode)
VNFM uses NVFO as a proxy, and NFVO performs all work related to virtual network creation for VNFM.
——VNFM requests NFVO to perform tasks such as VM generation, expansion and contraction, and monitoring;
——After each operation is completed, NFVO notifies VNFM;
——NFVO has detailed information about the resource consumption of all components.
2) Direct Mode (Direct Mode)
In this mode, VNFM and the underlying VIM can interact directly:
——NFVO authorizes VNFM to perform specific life cycle management related to VNF resources;
——VNFM applies for resources from NFVO and obtains a tenant and feedback on related resources;
——NFVO reserves resources;
——VNFM and VIM interact directly, and VNFM performs VM generation, expansion and contraction, VNF monitoring, etc.; ——When
each action ends, VNFM notifies MANO.
2. VNF package management and VNF life cycle management process
2.1. VNF package management process
2.1.1. VNF package overview
The VNF package includes the following contents:
-VNFD file: metadata file for VNF package online and VNF management;
-Software image file: Software image used to run VNF;
- Manifest file: Provides VNF package consistency and authorization verification, etc.;
- Other files (optional): used to manage VNF, etc. (for example, script files, vendor-specific private files, etc.).
2.1.2. Upload VNF package process
The upload process refers to the process of submitting the VNF package to NFVO and including it in the directory. The
main steps in the signaling process are as follows:
1) The initiator sends the VNF package to be loaded (VNF description file VNFD , the application software image file, if it involves a database application, should include the database software image file/installation file, (optional) Guest OS image file/installation file) to NFVO; 2) NFVO checks and verifies the VNF package, including checking the
package Whether the attached required information such as network element identification, network element provider, description file version and network element version exists; 3) After passing the inspection
and verification, NFVO notifies the network element directory database to include the VNF package;
4) NFVO will The image file is uploaded to the image database managed by VIM;
5) After the upload is completed, VIM returns a response message;
6) NFVO notifies the operator that the operation is completed and carries the result.
5.1.3. Update VNF package process
The update VNF package process refers to the process of submitting the updated VNF package to NFVO and including it in the directory.
Process description:
1) The initiator sends an update package request to NFVO, carrying the package identifier to be updated;
2) NFVO checks and verifies the update VNF package request, including checking whether the sender has permissions, whether the VNF package to be updated exists, etc. ;
3) After passing the inspection and verification, NFVO notifies the network element directory database to update the VNF package;
4) If the image file is updated, NFVO needs to notify VIM to delete the original image file first and upload the new image file to VIM;
5) Upload After completion, VIM returns a response message;
6) NFVO notifies the operator that the operation is completed and carries the result.
5.1.4. VNF package deletion process
The VNF package deletion process refers to the process of submitting a deletion package request to NFVO and deleting it from the directory.
Process description:
1) The initiator sends a deletion package request to NFVO, carrying the package identifier to be deleted;
2) NFVO checks and verifies the VNF package deletion request, including checking whether the sender has permission and whether the VNF package to be deleted exists. Whether the package status is disabled and no longer in use, etc.;
3) After passing the inspection and verification, NFVO notifies Catolog to delete the VNF package;
4) NFVO goes to the mirror warehouse on VIM to delete it;
5) After the deletion is completed, a response is returned to NFVO;
6) NFVO notifies the operator that the operation is complete and carries the results.