x
/
fenix
Code Issues Proposed changes
OpenStack host maintenance and upgrade in interaction with application on top of it
51 Commits 1 Branch 0 Tags 1.1 MiB
Python 98.7%
Shell 1.1%
Mako 0.2%
Go to file
Tomi Juvonen 46e13601a5 Add live migration support 
story: 2005585
Task: #30774

Change-Id: I5dc6db643900a6bfcc427b4b9ee23b5557b091a4
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
 		2019-05-10 03:14:18 +00:00
doc bug: Download document nits 2019-05-02 22:52:41 +03:00
fenix Add live migration support 2019-05-10 03:14:18 +00:00
releasenotes Initial Cookiecutter Commit. 2018-06-27 12:30:02 +03:00
.coveragerc Initial Cookiecutter Commit. 2018-06-27 12:30:02 +03:00
.gitignore Initial Cookiecutter Commit. 2018-06-27 12:30:02 +03:00
.gitreview Migrate to opendev.org 2019-04-23 16:26:56 +09:00
.mailmap Initial Cookiecutter Commit. 2018-06-27 12:30:02 +03:00
.stestr.conf Initial Cookiecutter Commit. 2018-06-27 12:30:02 +03:00
.zuul.yaml Build readthedocs automatically 2018-12-13 08:04:17 +02:00
CONTRIBUTING.rst Initial Cookiecutter Commit. 2018-06-27 12:30:02 +03:00
HACKING.rst Initial Cookiecutter Commit. 2018-06-27 12:30:02 +03:00
LICENSE Initial Cookiecutter Commit. 2018-06-27 12:30:02 +03:00
README.rst Migrate to opendev.org 2019-04-23 16:26:56 +09:00
babel.cfg Initial Cookiecutter Commit. 2018-06-27 12:30:02 +03:00
lower-constraints.txt Fix tox python3 overrides & add lower-constraints 2018-09-10 15:47:12 +09:00
requirements.txt Initial Cookiecutter Commit. 2018-06-27 12:30:02 +03:00
setup.cfg Change openstack-dev to openstack-discuss 2018-12-05 13:10:57 +02:00
setup.py Initial Cookiecutter Commit. 2018-06-27 12:30:02 +03:00
test-requirements.txt Initial Cookiecutter Commit. 2018-06-27 12:30:02 +03:00
tox.ini bug: fix upper constraints url 2019-05-01 03:10:25 +03:00

README.rst

fenix

OpenStack host maintenance and upgrade in interaction with application

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 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.

  • TODO