1.9 KiB
Administrators guide
Fenix
Fenix itself should be deployed to the infrastructure controller- or manager-node and be used for any cloud infrastructure maintenance, upgrade, scaling or life-cycle operations.
VNF and VNFM
In NFV use case the VNF and VNFM need to support Fenix to optimize the workflows and to guarantee zero impact to VNF during different infrastructure operations. This means instance and instance group constraints and the interaction with Fenix. Best optimization will be if the VNF can be scaled according to its current utilization level. This will result to smallest possible maintenance window while keeping the zero impact on VNF service.
Infrastructure Admin UI
Infrastructure admin UI needs to support Fenix. UI needs to be able to call the Fenix admin APIs and preferably to listen Fenix admin events. UI should be able to call different infrastructure maintenance and upgrade workflows with needed parameters. APIs and events also give possibility to have a detailed information of the workflow progress and to troubleshoot possible errors. In complex clouds errors can be still simple and quickly corrected even manually. In this kind of special case the UI can also support updating Fenix workflow session to continue exactly to where it left.
Integration
The above mentioned UI, VNF and VNFM are currently not in scope of Fenix. The implementation should be in other open source project or own proprietary solution. Currently at least the OpenStack Tacker is looking to support Fenix.
Fenix itself also need to be tested and for that there is some kind of command-line implementation for the above functionality made under Fenix 'tools'. Implementation aims to have the ability to test the Fenix sample workflows with sample application (VNF). It also gives the idea what needs to be supported.