OpenStack host maintenance and upgrade in interaction with application on top of it
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Tomi Juvonen ef8bbb388b Add instructions to test workflows 1 year ago
devstack Correction of the auth_type option handling 2 years ago
doc Kubernetes workflow 1 year ago
fenix Add instructions to test workflows 1 year ago
releasenotes Initial Cookiecutter Commit. 3 years ago
.coveragerc Initial Cookiecutter Commit. 3 years ago
.gitignore Initial Cookiecutter Commit. 3 years ago
.gitreview OpenDev Migration Patch 2 years ago
.mailmap Initial Cookiecutter Commit. 3 years ago
.stestr.conf Initial Cookiecutter Commit. 3 years ago
.zuul.yaml API schema validation 1 year ago
CONTRIBUTING.rst Sync Sphinx requirement 2 years ago
HACKING.rst Initial Cookiecutter Commit. 3 years ago
LICENSE Initial Cookiecutter Commit. 3 years ago
README.rst Moved link to specifications 1 year ago
babel.cfg Initial Cookiecutter Commit. 3 years ago
lower-constraints.txt Add test cases 1 year ago
requirements.txt API schema validation 1 year ago
setup.cfg API schema validation 1 year ago
setup.py Initial Cookiecutter Commit. 3 years ago
test-requirements.txt Add test cases 1 year ago
tox.ini Add test cases 1 year ago

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.