Difference between revisions of "Fenix"
Tomi Juvonen (talk | contribs) (→What is Fenix?) |
Tomi Juvonen (talk | contribs) (→What is Fenix?) |
||
| Line 2: | Line 2: | ||
==What is Fenix?== | ==What is Fenix?== | ||
Fenix implements rolling infrastructure maintenance and upgrade in interaction | Fenix implements rolling infrastructure maintenance and upgrade in interaction | ||
| − | with VNFM. Infrastructure admin can call Fenix API to start maintenance | + | with application on top of it. In Telco world we talk about VNFM, but one can implement |
| − | workflow session. This session will make needed maintenance and upgrade operations | + | own simple manager for any application. |
| − | to infrastructure in interaction with | + | |
| − | Interaction | + | Infrastructure admin can call Fenix API to start a maintenance workflow session. This |
| − | coming over maintenance | + | session will make needed maintenance and upgrade operations to infrastructure in interaction |
| − | admin level messaging, so infrastructure components will know certain host is under | + | with application manager to guarantee zero down time for its service. Interaction gives ability |
| − | maintenance. | + | 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 will have project specific messaging with instances affected towards application manager, | ||
| + | it will also have admin level messaging, so infrastructure components will know certain host is | ||
| + | under maintenance. This could also support adding or removing host. | ||
==Development== | ==Development== | ||
Revision as of 18:11, 24 May 2018
What is Fenix?
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 will have project specific messaging with instances affected towards application manager, it will also have admin level messaging, so infrastructure components will know certain host is under maintenance. This could also support adding or removing host.
Development
Project at Launchpad: https://launchpad.net/fenix CLI: https://launchpad.net/python-fenixclient Blueprints Source code: tbd
Communication and Meetings
Meetings
tbd
Contact Us
IRC channel for regular daily discussions: #openstack-fenix Use [Fenix] tag for Fenix emails on OpenStack Mailing Lists
