What is Fenix?
Fenix implements rolling infrastructure maintenance, upgrade and scaling. It can do this also in interaction with the application on top of it if the application supports 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, upgrade and scaling operations to infrastructure optionally in interaction with the application manager to guarantee zero downtime for its service. Interaction gives the ability for application manager to know about new capabilities coming over maintenance to make his own upgrade. The 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 the migration. Also, seamless application scaling or retirement will be possible.
As Fenix will have 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, so any infrastructure components can have this information. Special case for this would also be telling about adding or removing a host.
The architecture is pluggable to manage different use cases, clouds and payloads. There will be a plugin for workflow used and for the pre-, host- and post-actions.
Architecture presentation about Fenix
Fenix - Rolling Upgrade, Maintenance and Scaling with Zero Impact to VNF
Fenix is based on the work done in the OPNFV Doctor.
Doctor maintenance design guideline
- Storyboard: https://storyboard.openstack.org/#!/project/x/fenix
- CLI: https://storyboard.openstack.org/#!/project/x/python-fenixclient
- Source code:
Stein release priority work
In Stein release, Fenix should implement workflow to have rolling OpenStack upgrade
done in interaction with the application on top. For this, we should implement the following
- Support for action plug-in
- Controller host support
- Support for one click upgrade
- Action plugins for OpenStack upgrade
- Ability to download plug-ins and SW changes
Other stories are nice to have, but not priority work.
Communication and Meetings
bi-weekly meeting on Monday 5 AM UTC.
Note! No meeting 6th May just after summit/PTG
Next meeting: 20th May Topics (feel free to add one):
11th March meeting minutes:
- Meeting minutes: http://paste.openstack.org/show/747586/
- IRC channel for regular daily discussions: #openstack-fenix
- Use [fenix] tag for Fenix emails on OpenStack Mailing Lists