Difference between revisions of "Fenix"
Tomi Juvonen (talk | contribs) (→Development) |
Tomi Juvonen (talk | contribs) (→What is Fenix?) |
||
| Line 1: | Line 1: | ||
[[File:Fenix-birdi 192x192.png|thumb|left]] | [[File:Fenix-birdi 192x192.png|thumb|left]] | ||
==What is Fenix?== | ==What is Fenix?== | ||
| − | Fenix implements rolling infrastructure maintenance, upgrade and scaling in interaction | + | Fenix implements rolling infrastructure maintenance, upgrade and scaling. It can do this also |
| − | with application on top of it. In Telco world we talk about VNFM, but one can implement | + | in interaction with application on top of it, if application supports it. In Telco world we talk |
| − | own simple manager for any application. | + | 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 | Infrastructure admin can call Fenix API to start a maintenance workflow session. This | ||
| − | session will make needed maintenance, upgrade and scaling operations to infrastructure in | + | session will make needed maintenance, upgrade and scaling operations to infrastructure |
| − | interaction with application manager to guarantee zero down time for its service. Interaction | + | optionally in interaction with application manager to guarantee zero down time for its service. |
| − | gives ability for application manager to know about new capabilities coming over maintenance | + | Interaction gives ability for application manager to know about new capabilities coming over |
| − | to make his own upgrade. Application can have a time window to finish what he is doing, make | + | maintenance to make his own upgrade. Application can have a time window to finish what |
| − | own action to re-instantiate his instance or have Fenix to make migration. Also seamless | + | he is doing, make own action to re-instantiate his instance or have Fenix to make migration. |
| − | application scaling or retirement will be possible. | + | Also seamless application scaling or retirement will be possible. |
As Fenix will have project specific messaging with information about instances affected towards | As Fenix will have project specific messaging with information about instances affected towards | ||
| Line 18: | Line 18: | ||
case for this would also be telling about adding or removing a host. | case for this would also be telling about adding or removing a host. | ||
| − | Architecture will be pluggable to manage different | + | Architecture will be pluggable to manage different use cases, clouds and payloads. There will |
| + | be plugin for workflow used and for the maintenance action for a host, like esw or OpenStack | ||
| + | upgrade. | ||
==Planned Architecture== | ==Planned Architecture== | ||
Revision as of 22:49, 11 September 2018
Contents
What is Fenix?
Fenix implements rolling infrastructure maintenance, upgrade and scaling. It can do this also in interaction with application on top of it, if 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 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 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.
Architecture will be pluggable to manage different use cases, clouds and payloads. There will be plugin for workflow used and for the maintenance action for a host, like esw or OpenStack upgrade.
Planned Architecture
Development
Soryboard: https://storyboard.openstack.org/#!/project/openstack/fenix CLI: https://storyboard.openstack.org/#!/project/openstack/fenix-client Source code: https://git.openstack.org/cgit/openstack/fenix/ https://git.openstack.org/cgit/openstack/python-fenixclient
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
