x
/
fenix
Code Issues Proposed changes
fenix/README.rst

2.2 KiB
Raw Blame History

Fenix

OpenStack host maintenance and upgrade in interaction with application

Fenix implements rolling infrastructure maintenance and upgrade in interaction with application on top of it. In Telco world we talk about VNFM, but one can implement own simple manager for any application.

Infrastructure admin can call Fenix API to start a maintenance workflow session. This session will make needed maintenance and upgrade operations to infrastructure in interaction with application manager to guarantee zero down time for its service. Interaction gives ability for application manager to know about new capabilities coming over maintenance to make his own upgrade. Application can have a time window to finish what he is doing, make own action to re-instantiate his instance or have Fenix to make migration. Also scaling application or retirement will be possible.

As Fenix has project specific messaging with information about instances affected towards application manager, it will also have admin level messaging. This messaging can tell what host is down for maintenance, back in use, added or retired. Any infrastructure component can catch this information as needed.

Fenix also work with "one click". Infrastructure admin just creates the workflow session he wants and all needed software changes are automatically downloaded, workflow is run to wanted hosts according the request and depending on how the used workflow plug-in and action plug-ins are implemented.

In the NFV Fenix needs to be supported by infrastructure admin UI, VNFM and VNF implementation. Fenix itself should be integrated to infrastructure to be used it the infrastructure maintenance, upgrade, scaling and life-cycle operations.