White Papers

Understanding OPNFV

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

Contents of this Issue

Navigation

Page 26 of 144

Understanding OPNFV 26 area that still requires research. It involves the technical consequences that arise when the administrator of a VNF is meant to heave more secure access than the administrator of the overall system. (This situation comes up in cases of "lawful interception.") The problem is that in general, it's difficult to secure resources on a system from the system's administrator. The NFV Security Expert Group has presented these issues to the NFV ISG, which is working with other standards bodies to try and alleviate these problems. Performance NFV infrastructure is designed to emulate a hardware environment with one made up of software, but that doesn't mean that you can just drop the software into your cloud and go. Most of what NFV does requires extremely performant systems – but they're required in an environment where the VNF doesn't always know what it's getting. What this means is that it's up to the operator to configure and deploy the software in such a way as to take advantage of best practices when it comes to performance. In fact, according to the NFV ISG, the difference in speed between using NFV and using NFV correctly can be as much as 1000%. Needless to say, NFV's promise of reducing capital expenditures can quickly get eroded if instead of one proprietary box, you have to buy multiple industry standard servers that perform poorly. In short, as an industry, we need to close the gap between NFVI and physical network function price-performance. Interoperability NFV is meant to be an ecosystem that is occupied by multiple players, so it's especially important that all their solutions can work together. To that end, it's crucial to have specifications that define interoperability between the various portions of the overall system, such as the Orchestrator, the Virtualized Infrastructure Manager (VIM), the Virtual Network Function Manager (VNFM), the VNF, and the actual Network Functions Virtualization Infrastructure (NFVI). Also, interoperability with legacy OSS/BSS systems is just as important. In this case, both the open source approach and the encouragement of PoCs can help reach this goal, as multiple operators attempt to compose systems out of multiple components. Easy to Operate Amazon has an army of cloud specialists to operate Amazon Web Services. If we require the same of NFV deployments, we will either increase the operational cost dramatically and/or

Articles in this issue

Links on this page

view archives of White Papers - Understanding OPNFV