Difference between revisions of "Fenix"
Tomi Juvonen (talk | contribs) (→What is Fenix?) |
Tomi Juvonen (talk | contribs) (→Contact Us) |
||
(12 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
[[File:Fenix-birdi 192x192.png|thumb|left]] | [[File:Fenix-birdi 192x192.png|thumb|left]] | ||
==What is Fenix?== | ==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 | + | Infrastructure admin can call Fenix API to start a pluggable 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 the application manager to guarantee zero downtime for its service. | + | optionally in interaction with the application manager (VNFM) to guarantee zero downtime for its |
− | Interaction gives the ability for application manager to know about new capabilities coming over | + | service. Interaction gives the ability for the application manager to know about new capabilities |
− | maintenance to make his own upgrade. The application can have a time window to finish what | + | coming over maintenance to make his own upgrade. The application can have a time window to |
− | he is doing, make own action to re-instantiate his instance or have Fenix to make the migration. | + | finish what he is doing, make own action to re-instantiate his instance or have Fenix to make the |
− | Also, seamless application scaling or retirement will be possible. | + | migration. Also, seamless application scaling or retirement will be possible. |
− | As Fenix | + | As Fenix has above described project-specific messaging with information about instances |
− | application manager, it | + | affected towards application manager, it also has admin-level messaging. This messaging can |
− | is down for maintenance, so any infrastructure components can have this information. Special | + | tell what host is down for maintenance, so any infrastructure components can have this information. |
− | case for this would also be telling about adding or removing a host. | + | 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 | + | 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:<br /> | Presentation in OIS Denver 2019:<br /> | ||
Line 28: | Line 31: | ||
[https://drive.google.com/file/d/1BkYciG7-ItpoZjMan1mPDsX7kWjGvBSl/view?usp=sharing Resiliency Closed Loop - Telco Self-healing and Maintenance]<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 /> | Unconference in ONS Europe 2019:<br /> | ||
− | [https://etherpad.opnfv.org/p/ONS-Ant2019-Fenix Host maintenance with Fenix] | + | [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== | ||
Line 44: | Line 49: | ||
* 2003846 Support for action plug-in | * 2003846 Support for action plug-in | ||
* 2003830 Fenix workflow error handling and use of database | * 2003830 Fenix workflow error handling and use of database | ||
− | |||
− | |||
===Train priorities=== | ===Train priorities=== | ||
Line 51: | Line 54: | ||
<br><br/> | <br><br/> | ||
As there were two non-Telco users wanting to start using Fenix, it was the most important thing driving the priorities: | 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 | https://etherpad.openstack.org/p/DEN2019-fenix-PTG | ||
<br><br/> | <br><br/> | ||
Also, there was a discussion about ETSI NFV harmonization: | Also, there was a discussion about ETSI NFV harmonization: | ||
− | + | <br /> | |
https://etherpad.openstack.org/p/DEN2019-fenix-ETSI-NFV-PTG | https://etherpad.openstack.org/p/DEN2019-fenix-ETSI-NFV-PTG | ||
− | |||
− | |||
===Ussuri=== | ===Ussuri=== | ||
Open Infrastructure Summit - Shanghai | Open Infrastructure Summit - Shanghai | ||
− | |||
− | |||
<br /> | <br /> | ||
PTG:https://etherpad.openstack.org/p/Shanghai2019-Fenix-PTG | PTG:https://etherpad.openstack.org/p/Shanghai2019-Fenix-PTG | ||
Line 70: | Line 69: | ||
<br /> | <br /> | ||
Specification to start implementing ETSI FEAT03: NFVI software modification. | Specification to start implementing ETSI FEAT03: NFVI software modification. | ||
− | https:// | + | https://fenix.readthedocs.io/en/latest/specifications/ussuri-etsi-feat03.html |
+ | <br /> | ||
+ | * Security | ||
+ | * Update/continue failed session | ||
+ | * Parallel execution | ||
+ | * Kubernetes | ||
==Documentation== | ==Documentation== | ||
Line 78: | Line 82: | ||
===Meetings=== | ===Meetings=== | ||
bi-weekly meeting on Monday 5 AM UTC ("odd" weeks on #openstack-Fenix) | bi-weekly meeting on Monday 5 AM UTC ("odd" weeks on #openstack-Fenix) | ||
− | + | <br /> | |
− | |||
Topics for next meeting | Topics for next meeting | ||
Topics (feel free to add one): | Topics (feel free to add one): | ||
Line 88: | Line 91: | ||
* 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-discuss/ OpenStack Mailing Lists] | * Use [fenix] tag for Fenix emails on [http://lists.openstack.org/pipermail/openstack-discuss/ OpenStack Mailing Lists] | ||
+ | * PTL Tomi Juvonen (tojuvone) |
Latest revision as of 06:17, 14 April 2020
Contents
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
- Storyboard: https://storyboard.openstack.org/#!/project/x/fenix
- CLI: https://storyboard.openstack.org/#!/project/x/python-fenixclient
- Source code:
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
- PTL Tomi Juvonen (tojuvone)