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 bd0810495f Administrator quide and other documentation 1 month ago
devstack Correction of the auth_type option handling 6 months ago
doc Administrator quide and other documentation 1 month ago
fenix Detailed session information and enhancements 1 month ago
releasenotes Initial Cookiecutter Commit. 1 year ago
.coveragerc Initial Cookiecutter Commit. 1 year ago
.gitignore Initial Cookiecutter Commit. 1 year ago
.gitreview OpenDev Migration Patch 1 year ago
.mailmap Initial Cookiecutter Commit. 1 year ago
.stestr.conf Initial Cookiecutter Commit. 1 year ago
.zuul.yaml API schema validation 3 months ago
CONTRIBUTING.rst Sync Sphinx requirement 7 months ago
HACKING.rst Initial Cookiecutter Commit. 1 year ago
LICENSE Initial Cookiecutter Commit. 1 year ago
README.rst Administrator quide and other documentation 1 month ago
babel.cfg Initial Cookiecutter Commit. 1 year ago
lower-constraints.txt Add test cases 2 months ago
requirements.txt API schema validation 3 months ago
setup.cfg API schema validation 3 months ago
setup.py Initial Cookiecutter Commit. 1 year ago
test-requirements.txt Add test cases 2 months ago
tox.ini Add test cases 2 months ago

README.rst

Fenix

OpenStack host maintenance and upgrade in interaction with the application

Fenix implements rolling infrastructure maintenance and upgrade in interaction with the application on top of it. In Telco world we talk about VNFM, but one can implement his 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 the application manager 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 scaling applications or retirement will be possible.

As Fenix has project-specific messaging with information about instances affected towards the application manager, it will also have admin-level messaging. This messaging can tell what host is down for maintenance, back in use, added or retired. Any infrastructure component can catch this information as needed.

Fenix also works with "one-click". Infrastructure admin just creates the workflow session he wants and all needed software changes are automatically downloaded, the workflow is run to wanted hosts according to the request and depending on how the used workflow plug-in and action plug-ins are implemented.

In the NFV Fenix needs to be supported by infrastructure admin UI, VNFM and VNF implementation. Fenix itself should be integrated into infrastructure to be used it the infrastructure maintenance, upgrade, scaling and life-cycle operations.