x/fenix
Code Issues Proposed changes
Files
2eee99ae4e7f0f9e96b61c5d13de43d5a5d542a0
fenix/doc/source/api-ref/v1/index.rst
Gergely Csatari b3b534de79 Building api documentation with os-api-ref under the doc folder 
This change adds the usage of os-api-ref to the building of the
API documentation, but under the doc folder, so it is possible
to publish the result to readthedocs.org.

This change replaces [1] until the documentation is published
to readthedocs.org. Once Fenix becomes an official OpenStack
project [1] can be implemented.
For the moment I will abandon [1].

[1]: https://review.openstack.org/#/c/616868/

Story: 2004292
Task: #27862

Change-Id: I3144f812d0afd41d500ec7cd8fd4ba1d9c202366
Signed-off-by: Gergely Csatari <gergely.csatari@nokia.com>
2018-11-21 09:55:53 +01:00

730 B
Raw Blame History

tocdepth

2

Host Maintenance API v1

Admin

These APIs are meant for infrastructure admin who is in charge of triggering the rolling maintenance and upgrade workflows.

Project

These APIs are meant for projects having instances on top of the infrastructure under corresponding rolling maintenance or upgrade session. Usage of these APIs expects there is an application manager (VNFM) that can interact with Fenix workflow via these APIs. If this is not the case, workflow should have a default behavior for instances owned by projects, that are not interacting with Fenix.