Jump to: navigation, search

Difference between revisions of "Fenix"

(Contact Us)
(Meetings)
(28 intermediate revisions by 3 users not shown)
Line 2: Line 2:
 
==What is Fenix?==
 
==What is Fenix?==
 
Fenix implements rolling infrastructure maintenance, upgrade and scaling. It can do this also
 
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
+
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.
 
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
 
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.
+
optionally in interaction with the application manager to guarantee zero downtime for its service.
Interaction gives ability for application manager to know about new capabilities coming over
+
Interaction gives the 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
+
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 migration.
+
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.
+
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
 
application manager, it will also have admin level messaging. This messaging can tell what host
 
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
 
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.
 
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
+
The architecture is 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
+
be a plugin for workflow used and for the pre-, host- and post-actions.
upgrade.
 
  
Fenix is based on the work done in the OPNFV Doctor.<br />
+
Presentation in OIS Denver 2019:<br />
[https://wiki.opnfv.org/download/attachments/5046291/Planned%20Maintenance%20Design%20Guideline.pdf?version=1&modificationDate=1527183603000&api=v2 Doctor maintenance design guideline]<br />
+
[https://drive.google.com/file/d/1pKJWJCHhle7opP4_EURRv3Rg3doRibLP/view?usp=sharing Fenix Denver - forum presentation]
Doctor presentation in OpenStack Vancouver summit that lead to creation of the Fenix:
 
[https://etherpad.openstack.org/p/YVR-rolling-maintenance-with-VNFM How to gain VNF zero down-time during Infrastructure Maintenance and Upgrade]
 
  
==Planned Architecture==
+
==Development==
[[file: Fenix-architecture.png]]
+
* Storyboard: https://storyboard.openstack.org/#!/project/x/fenix
 +
* CLI: https://storyboard.openstack.org/#!/project/x/python-fenixclient
 +
* Source code:
 +
** https://opendev.org/x/fenix/
 +
** https://opendev.org/x/python-fenixclient
 +
 
 +
===Stein release notes ===
 +
During Stein release, Fenix most important new features were the stories below:
 +
<br><br/>
 +
* 2004147 Ability to download plug-ins and SW changes
 +
* 2004146 Support for one-click upgrade
 +
* 2003846 Support for action plug-in
 +
* 2003830 Fenix workflow error handling and use of database
 +
<br><br/>
 +
With these, Fenix is already usable for trialing. Anyhow it will be in Train priorities to have it more mature.
 +
 
 +
===Train priorities===
 +
There was a session in Denver PTG to define the priorities.
 +
<br><br/>
 +
As there were two non-Telco users wanting to start using Fenix, it was the most important thing driving the priorities:
 +
<br><br/>
 +
https://etherpad.openstack.org/p/DEN2019-fenix-PTG
 +
<br><br/>
 +
Also, there was a discussion about ETSI NFV harmonization:
 +
<br><br/>
 +
https://etherpad.openstack.org/p/DEN2019-fenix-ETSI-NFV-PTG
 +
<br><br/>
 +
This will still need more discussion and thinking. It is a very important topic, but not the first priority
  
==Development==
+
==Documentation==
* Storyboard: https://storyboard.openstack.org/#!/project/openstack/fenix
+
* https://fenix.readthedocs.io/en/latest/
* CLI: https://storyboard.openstack.org/#!/project/openstack/python-fenixclient
 
* Source code: https://git.openstack.org/cgit/openstack/fenix/ https://git.openstack.org/cgit/openstack/python-fenixclient
 
  
 
==Communication and Meetings==
 
==Communication and Meetings==
 
===Meetings===
 
===Meetings===
tbd
+
bi-weekly meeting on Monday 5 AM UTC ("odd" weeks on #openstack-Fenix)
 +
 
 +
<br /><br />
 +
Topics for next meeting
 +
Topics (feel free to add one):
 +
* Status
 +
* AoB
 +
 
 
===Contact Us===
 
===Contact Us===
 
* IRC channel for regular daily discussions: #openstack-fenix
 
* IRC channel for regular daily discussions: #openstack-fenix
* Use [Fenix] tag for Fenix emails on [http://lists.openstack.org/pipermail/openstack-dev/ OpenStack Mailing Lists]
+
* Use [fenix] tag for Fenix emails on [http://lists.openstack.org/pipermail/openstack-discuss/ OpenStack Mailing Lists]

Revision as of 04:47, 26 August 2019

Fenix-birdi 192x192.png

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.

Presentation in OIS Denver 2019:
Fenix Denver - forum presentation

Development

Stein release notes

During Stein release, Fenix most important new features were the stories below:

  • 2004147 Ability to download plug-ins and SW changes
  • 2004146 Support for one-click upgrade
  • 2003846 Support for action plug-in
  • 2003830 Fenix workflow error handling and use of database



With these, Fenix is already usable for trialing. Anyhow it will be in Train priorities to have it more mature.

Train priorities

There was a session in Denver PTG to define the priorities.

As there were two non-Telco users wanting to start using Fenix, it was the most important thing driving the priorities:

https://etherpad.openstack.org/p/DEN2019-fenix-PTG

Also, there was a discussion about ETSI NFV harmonization:

https://etherpad.openstack.org/p/DEN2019-fenix-ETSI-NFV-PTG

This will still need more discussion and thinking. It is a very important topic, but not the first priority

Documentation

Communication and Meetings

Meetings

bi-weekly meeting on Monday 5 AM UTC ("odd" weeks on #openstack-Fenix)



Topics for next meeting Topics (feel free to add one):

  • Status
  • AoB

Contact Us

  • IRC channel for regular daily discussions: #openstack-fenix
  • Use [fenix] tag for Fenix emails on OpenStack Mailing Lists