Shared networks to support VNF high availability across OpenStack multi-region deployment
VNF components in OpenStack Tacker
-
Upload
bharath-thiruveedula -
Category
Software
-
view
118 -
download
0
Transcript of VNF components in OpenStack Tacker
![Page 1: VNF components in OpenStack Tacker](https://reader035.fdocuments.in/reader035/viewer/2022062218/58ee1db51a28abec398b462b/html5/thumbnails/1.jpg)
VNF Components in Tacker
![Page 2: VNF components in OpenStack Tacker](https://reader035.fdocuments.in/reader035/viewer/2022062218/58ee1db51a28abec398b462b/html5/thumbnails/2.jpg)
Agenda
Introduction
Why VNFC ??
Different drivers to implement VNFC in Tacker.
Quick Demo
Open Discussion
![Page 3: VNF components in OpenStack Tacker](https://reader035.fdocuments.in/reader035/viewer/2022062218/58ee1db51a28abec398b462b/html5/thumbnails/3.jpg)
Introduction
● VNF Provider models the VNF into various software components called as VNF Components.
● In the current state, Tacker depends on pre-built images in which Network function is embedded to build the VDUs.
● VNFs can be built from one or more VNFCs
![Page 4: VNF components in OpenStack Tacker](https://reader035.fdocuments.in/reader035/viewer/2022062218/58ee1db51a28abec398b462b/html5/thumbnails/4.jpg)
![Page 5: VNF components in OpenStack Tacker](https://reader035.fdocuments.in/reader035/viewer/2022062218/58ee1db51a28abec398b462b/html5/thumbnails/5.jpg)
Why VNFC ??
● To use vendor specific installation procedures to build network function.
● Loose coupling between image and network function which avoid dependency on the underlying image.
● Easy to upgrade the VNF.
![Page 6: VNF components in OpenStack Tacker](https://reader035.fdocuments.in/reader035/viewer/2022062218/58ee1db51a28abec398b462b/html5/thumbnails/6.jpg)
Different drivers to implement VNFC.
1.Cloud Init
2.Heat Software Deployment
3.SSH Driver
![Page 7: VNF components in OpenStack Tacker](https://reader035.fdocuments.in/reader035/viewer/2022062218/58ee1db51a28abec398b462b/html5/thumbnails/7.jpg)
Cloud Init
Tacker can leverage the Heat Software Config feature to achieve VNF components support in Tacker.
Pros :
Most of the cloud images have cloud-init installed.
Cons :
Hard to upgrade the VNFs on the fly.
![Page 8: VNF components in OpenStack Tacker](https://reader035.fdocuments.in/reader035/viewer/2022062218/58ee1db51a28abec398b462b/html5/thumbnails/8.jpg)
Heat Software Deployment
Tacker can leverage the Heat Software Deployment feature to achieve VNF components support in Tacker.
Pros :
Facilitates the upgrade functionality of the VNF.
Cons :
Heat agents needs to be installed as a prerequisite.
![Page 9: VNF components in OpenStack Tacker](https://reader035.fdocuments.in/reader035/viewer/2022062218/58ee1db51a28abec398b462b/html5/thumbnails/9.jpg)
SSH Driver
Introducing SSH driver in Tacker is nice to have feature where in tacker will have complete control on what needs to be installed as software component to bring up a VNFC.
Pros :
Facilitates the easy upgrade of the VNFs
Cons :
Credentials storage and security of VDU is pain area.
![Page 10: VNF components in OpenStack Tacker](https://reader035.fdocuments.in/reader035/viewer/2022062218/58ee1db51a28abec398b462b/html5/thumbnails/10.jpg)
Demo
1.Instantiate a VNF using Heat Software Deployment.
2.Instantiate a VNF using SSH Driver.
![Page 11: VNF components in OpenStack Tacker](https://reader035.fdocuments.in/reader035/viewer/2022062218/58ee1db51a28abec398b462b/html5/thumbnails/11.jpg)
Open Discussion
- Improvements & suggestions.
- Thoughts about other drivers.
- Future scope of VNFC.