White Papers

Understanding OPNFV

Issue link: https://read.uberflip.com/i/1344850

Contents of this Issue


Page 31 of 144

Understanding OPNFV 31 a complete service. Bringing up the service often has dependencies whereby functions have to be provisioned in a certain order. Finally, the monitoring infrastructure for each VNF must be put in place. Once the service is up and running, "day-2" activities kick in in terms of updates, upgrades, scaling-out, scaling-in, self-healing, configuration changes, and so on (see Full Automation of NFV Software Lifecycle figure below). Doing this manually can take weeks or months of effort. That's where model driven architecture comes into the picture. Model driven templates describe the entire network service, with configurations for each VNF, its topology and connectivity, various dependencies and policies for triggering actions specified in a human-readable file. These templates can also capture management, monitoring and capability APIs. With the entire network service descriptor (NSD) available as code, there are no manual steps or tickets to provision services, and the service is created, composed and deployed in exactly the same manner, every time. This is true even across different environments ranging from dev/test to production, even with different underlying NFVI, VIM or SDN controller elements. Moreover, model driven templates can also be put in revision control for better tracking and compliance. Model Driven Architecture Fuels NFV If model driven templates are so useful, why stop with just network service descriptions? In fact, these templates are used for lower level components such as VNF descriptors, software application and infrastructure resources, and higher level items such as products (collections of services with commercial attributes) and offers (bundles of products with marketing configurations). While lower level templates concentrate on the resource, policy, topology, configurations and dependencies, higher-level templates include process, order, pricing and business rules. To sum it up, a model driven architecture vastly reduces the time it takes operators to deliver new products and services to their customers, and enables rapid onboarding

Articles in this issue

view archives of White Papers - Understanding OPNFV