Jump to: navigation, search

Difference between revisions of "Fenix"

(What is Fenix?)
(What is Fenix?)
(56 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
[[File:Fenix-birdi 192x192.png|thumb|left]]
 +
==What is Fenix?==
 +
Optimized rolling infrastructure pluggable one-click maintenance, upgrade, scaling and life-cycle
 +
workflow with VNFM interaction guaranteeing zero impact on VNF service.
 +
 +
Infrastructure admin can call Fenix API to start a pluggable workflow session. This
 +
session will make needed maintenance, upgrade and scaling operations to infrastructure
 +
optionally in interaction with the application manager (VNFM) to guarantee zero downtime for its
 +
service. Interaction gives the ability for the 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.
  
==What is Fenix?==
+
As Fenix has above described project-specific messaging with information about instances
Fenix implements rolling infrastructure maintenance and upgrade in interaction
+
affected towards application manager, it also has admin-level messaging. This messaging can
with application on top of it. In Telco world we talk about VNFM, but one can implement
+
tell what host is down for maintenance, so any infrastructure components can have this information.
own simple manager for any application.
+
Special case for this messaging would also be telling about adding or removing a host.
  
Infrastructure admin can call Fenix API to start a maintenance workflow session. This
+
The architecture is pluggable to manage different use cases, clouds and payloads. There is
session will make needed maintenance and upgrade operations to infrastructure in interaction
+
plugin for workflow used and for the pre-, host- and post-actions.
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 information about instances affected towards
+
The latest addition is also the ETSI FEAT03 defined constraints for instances and instance groups
application manager, it will also have admin level messaging. This messaging can tell what host
+
that can be used to optimize any rolling workflow to be done in the shortest possible time window,
is down for maintenance, so any infrastructure components can have this information. Special
+
while at the same time keeping zero impact on VNF service.
case for this would also be telling about adding or removing a host.
 
  
==Planned Architecture==
+
Presentation in OIS Denver 2019:<br />
[[file: Fenix-architecture.png]]
+
[https://drive.google.com/file/d/1pKJWJCHhle7opP4_EURRv3Rg3doRibLP/view?usp=sharing Fenix Denver - forum presentation]<br />
 +
Presentation in ONS Europe 2019:<br />
 +
[https://drive.google.com/open?id=1k6lcKF6n132qN-LMfxfcCxYk52nscfb8 Resiliency Closed Loop - Telco Self-healing and Maintenance]<br />
 +
Live demo in ONS Europe 2019:<br />
 +
[https://drive.google.com/file/d/1BkYciG7-ItpoZjMan1mPDsX7kWjGvBSl/view?usp=sharing Resiliency Closed Loop - Telco Self-healing and Maintenance]<br />
 +
Unconference in ONS Europe 2019:<br />
 +
[https://etherpad.opnfv.org/p/ONS-Ant2019-Fenix Host maintenance with Fenix]<br />
 +
OPNFV CLA WG March 2020:<br />
 +
[https://drive.google.com/file/d/1koNhGUlhuATZnt8C0jKmhfhbDe7i4C7Q/view Telco rolling maintenance and upgrade with ETSI FEAT03]
  
 
==Development==
 
==Development==
Project at Launchpad: https://launchpad.net/fenix
+
* Storyboard: https://storyboard.openstack.org/#!/project/x/fenix
CLI: https://launchpad.net/python-fenixclient
+
* CLI: https://storyboard.openstack.org/#!/project/x/python-fenixclient
[https://blueprints.launchpad.net/fenix Blueprints]
+
* Source code:
Source code:
+
** https://opendev.org/x/fenix/
tbd
+
** 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
 +
 
 +
===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/>
 +
https://etherpad.openstack.org/p/DEN2019-fenix-PTG
 +
<br><br/>
 +
Also, there was a discussion about ETSI NFV harmonization:
 +
<br />
 +
https://etherpad.openstack.org/p/DEN2019-fenix-ETSI-NFV-PTG
 +
 
 +
===Ussuri===
 +
Open Infrastructure Summit - Shanghai
 +
<br />
 +
PTG:https://etherpad.openstack.org/p/Shanghai2019-Fenix-PTG
 +
<br /><br />
 +
The main priority:
 +
<br />
 +
Specification to start implementing ETSI FEAT03: NFVI software modification.
 +
https://fenix.readthedocs.io/en/latest/specifications/ussuri-etsi-feat03.html
 +
<br />
 +
* Security
 +
* Update/continue failed session
 +
* Parallel execution
 +
* Kubernetes
 +
 
 +
==Documentation==
 +
* https://fenix.readthedocs.io/en/latest/
  
 
==Communication and Meetings==
 
==Communication and Meetings==
 
===Meetings===
 
===Meetings===
tbd
+
bi-weekly meeting on Monday 5 AM UTC ("odd" weeks on #openstack-Fenix)
 +
<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:34, 6 March 2020

Fenix-birdi 192x192.png

What is Fenix?

Optimized rolling infrastructure pluggable one-click maintenance, upgrade, scaling and life-cycle workflow with VNFM interaction guaranteeing zero impact on VNF service.

Infrastructure admin can call Fenix API to start a pluggable workflow session. This session will make needed maintenance, upgrade and scaling operations to infrastructure optionally in interaction with the application manager (VNFM) to guarantee zero downtime for its service. Interaction gives the ability for the 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 has above described project-specific messaging with information about instances affected towards application manager, it also has 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 messaging would also be telling about adding or removing a host.

The architecture is pluggable to manage different use cases, clouds and payloads. There is plugin for workflow used and for the pre-, host- and post-actions.

The latest addition is also the ETSI FEAT03 defined constraints for instances and instance groups that can be used to optimize any rolling workflow to be done in the shortest possible time window, while at the same time keeping zero impact on VNF service.

Presentation in OIS Denver 2019:
Fenix Denver - forum presentation
Presentation in ONS Europe 2019:
Resiliency Closed Loop - Telco Self-healing and Maintenance
Live demo in ONS Europe 2019:
Resiliency Closed Loop - Telco Self-healing and Maintenance
Unconference in ONS Europe 2019:
Host maintenance with Fenix
OPNFV CLA WG March 2020:
Telco rolling maintenance and upgrade with ETSI FEAT03

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

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

Ussuri

Open Infrastructure Summit - Shanghai
PTG:https://etherpad.openstack.org/p/Shanghai2019-Fenix-PTG

The main priority:
Specification to start implementing ETSI FEAT03: NFVI software modification. https://fenix.readthedocs.io/en/latest/specifications/ussuri-etsi-feat03.html

  • Security
  • Update/continue failed session
  • Parallel execution
  • Kubernetes

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