x/fenix
Code Issues Proposed changes
OpenStack host maintenance and upgrade in interaction with application on top of it
79 Commits 1 Branch 0 Tags 1.1 MiB
Python 98.7%
Shell 1.1%
Mako 0.2%
d06820b452
Go to file
Tomi Juvonen d06820b452 Add test cases 
story: 2007441
Task: #39098

- Some initial test cases
- DB cases enhanced DB error handling
- API error handling also improved
- Tools README.md bug
- New requirements cahanges for testing

Change-Id: I7f83c6472d1a86fa62e38cab2856be6c0d6bb259
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
2020-03-19 16:17:56 +02:00
devstack Correction of the auth_type option handling 2019-11-08 03:40:47 +00:00
doc Kubernetes workflow 2020-03-13 12:42:56 +02:00
fenix Add test cases 2020-03-19 16:17:56 +02: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 OpenDev Migration Patch 2019-04-19 19:50:40 +00: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 API schema validation 2020-02-11 11:24:28 +02:00
babel.cfg Initial Cookiecutter Commit. 2018-06-27 12:30:02 +03:00
CONTRIBUTING.rst Sync Sphinx requirement 2019-10-09 05:29:22 +00: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
lower-constraints.txt Add test cases 2020-03-19 16:17:56 +02:00
README.rst Moved link to specifications 2020-01-28 14:40:14 +01:00
requirements.txt API schema validation 2020-02-11 11:24:28 +02:00
setup.cfg API schema validation 2020-02-11 11:24:28 +02:00
setup.py Initial Cookiecutter Commit. 2018-06-27 12:30:02 +03:00
test-requirements.txt Add test cases 2020-03-19 16:17:56 +02:00
tox.ini Add test cases 2020-03-19 16:17:56 +02: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.