Instead of maintaining several large specialised virtual host images, Radiator VNF is deployed on top of your existing Linux operating system. There is no need to change the operating system, you can continue using your familiar Linux distribution with its licences, update and security services.
The basic architecture of Radiator VNF combined with OpenStack is described in the image below.
Instead of replacing the existing OpenStack controller functions and components, Radiator VNF works together with them and extends the OpenStack components if needed. Radiator VNF Manager utilises Heat and other cloud infrastructure orchestrator APIs to create, delete, and scale VNF instances and components.
Using Radiator VNF Manager gives the additional flexibility and extended control granularity for scaling virtual AAA (authentication, authorisation, accounting) functions. It also makes it easier to adapt Radiator VNF to any cloud infrastructure. All Radiator VNF components are also designed and implemented to securely communicate across compute nodes, which makes it possible to distribute Radiator VNF components flexibly without limiting the components within a single compute node.
Configuring Radiator VNF components do not require any manual interaction. Every configuration task is done automatically via Radiator VNF configuration management system, not by configuring each Radiator VNF component individually. This, combined with flexible component scaling, makes Radiator a true NFV solution.
Would you like to know more?
The Radiator VNF brings its well-known flexibility and extendability to the NFV world. Enhanced with configuration provisioning, automated scaling, and platform independency, Radiator VNF continues to be the Swiss army knife of AAA software also inside cloud infrastructures. If you are interested to learn more, please contact email@example.com for more information.