Demonstration
-
After running the main file (python3 ~/intent-layer/src/main.py), a database file called system.db (for store intents) will be created at main project folder. The vertical can submit a new intent using the new intent button at GUI. This PoC is basic and only considers the intent name and the number of virtual functions as customized options. After including a new intent, the vertical can see the created intent through list of intents button. The intent list shows the intent's name, the number of virtual functions and the status that can be: i) NOT INSTANTIATED (default value) or ii) INSTANTIATED (when the slice is created in OSM).
-
Similar to the work, every slice is composed at minimum of 1 Virtual Functions (VF), called VNF-SDN based, which requires 2vCPU, 2572MB of RAM and 20GB of storage and others N VFs (N corresponds to the number of virtual functions specified in intent's GUI by vertical) which requires each one 1vCPU, 512 MB of RAM and 10GB of storage. For testing purposes, when the intent is submitted, the Intent Engine is triggered.
-
Intent Engine module extracts the request from a vertical through database and transforms the intent into a intermediate representation called Network Intent LanguagE (NILE) . The Intent Translator module receives the intent expressed in NILE and extracts the name and the required number of VFs. The intent is then mapped to a set of descriptors, namely i) Virtual Network Function Descriptors (VNFDs), which define the behavior of each VF, and ii) one NSD, which defines how the VFs are connected in the network provided in the slice.
-
Once the descriptors are correctly associated to the vertical's intent, the OSM Handler module (osm_handler.py) interacts with OSM via its REST API to onboard the descriptors and deploy the Network Slice (NS) Instance. First, all NS, VNFd, and NSd are deleted from OSM. After, according to result of mapping between intent and descriptors, the VNFds and NSd are loaded into OSM. Next, the NS is created and initiated. The OSM processes the NS and if no errors are found, the slice instance is created at OpenStack. This finalizes the deployment process, which does not require any technical expertise or manual intervention from the vertical.
- a. Cleanning OSM
- b. Onboarding descriptors - VNF and NS
- c. Creation and instantiation network service instance
- d. Time results
- a. Onboarded VNFd descriptors
- b. Onboarded NS descriptor
- a. Status
- b. Details
- a. Created instances
- b. Network topology
