From 0f5bfd60319eac68b38830f8b49e19b6c03344a5 Mon Sep 17 00:00:00 2001 From: csatari Date: Tue, 2 Aug 2016 14:37:36 +0200 Subject: Explanatory figures Based on the comments of Fathemeh I've added 3 explanatory figures. Change-Id: Ica4a373ab88979162f064740c6020d0789b20cfe Signed-off-by: csatari --- docs/requirements/use_cases/georedundancy_cells.rst | 7 +++++++ .../use_cases/georedundancy_regions_insances.rst | 8 ++++++++ docs/requirements/use_cases/images/api-users.png | Bin 0 -> 21271 bytes .../use_cases/images/cells-architecture.png | Bin 0 -> 6465 bytes .../use_cases/images/instances-architecture.png | Bin 0 -> 7559 bytes .../use_cases/programmable_provisioning.rst | 8 ++++++++ 6 files changed, 23 insertions(+) create mode 100644 docs/requirements/use_cases/images/api-users.png create mode 100644 docs/requirements/use_cases/images/cells-architecture.png create mode 100644 docs/requirements/use_cases/images/instances-architecture.png (limited to 'docs/requirements/use_cases') diff --git a/docs/requirements/use_cases/georedundancy_cells.rst b/docs/requirements/use_cases/georedundancy_cells.rst index 36964ac..ad664e8 100644 --- a/docs/requirements/use_cases/georedundancy_cells.rst +++ b/docs/requirements/use_cases/georedundancy_cells.rst @@ -13,6 +13,13 @@ perspective as the sub-cells are using only the internal message bus and there is no API (and CLI) to do maintenance actions in case of a network connectivity problem between the main cell and the sub cells. +The following figure (:numref:`cells-architecture`) shows the architecture of +the most relevant OpenStack components in multi cell OpenStack environment. + +.. figure:: images/cells-architecture.png + :name: cells-architecture + :width: 50% + The functionality behind the API depends on the underlying network providers (SDN controllers) and the networking setup. (For example OpenDaylight has an API to add new BGP neighbor.) diff --git a/docs/requirements/use_cases/georedundancy_regions_insances.rst b/docs/requirements/use_cases/georedundancy_regions_insances.rst index 27eae65..995eb49 100644 --- a/docs/requirements/use_cases/georedundancy_regions_insances.rst +++ b/docs/requirements/use_cases/georedundancy_regions_insances.rst @@ -9,6 +9,14 @@ Description There should be an API to manage the infrastructure-s networks between two OpenStack regions or instances. +The following figure (:numref:`instances-architecture`) shows the architecture +of the most relevant OpenStack components in multi instance OpenStack +environment. + +.. figure:: images/instances-architecture.png + :name: instances-architecture + :width: 50% + The functionality behind the API depends on the underlying network providers (SDN controllers) and the networking setup. (For example OpenDaylight has an API to add new BGP neighbor.) diff --git a/docs/requirements/use_cases/images/api-users.png b/docs/requirements/use_cases/images/api-users.png new file mode 100644 index 0000000..1f08812 Binary files /dev/null and b/docs/requirements/use_cases/images/api-users.png differ diff --git a/docs/requirements/use_cases/images/cells-architecture.png b/docs/requirements/use_cases/images/cells-architecture.png new file mode 100644 index 0000000..476cf90 Binary files /dev/null and b/docs/requirements/use_cases/images/cells-architecture.png differ diff --git a/docs/requirements/use_cases/images/instances-architecture.png b/docs/requirements/use_cases/images/instances-architecture.png new file mode 100644 index 0000000..d70de02 Binary files /dev/null and b/docs/requirements/use_cases/images/instances-architecture.png differ diff --git a/docs/requirements/use_cases/programmable_provisioning.rst b/docs/requirements/use_cases/programmable_provisioning.rst index d66a54c..963451d 100644 --- a/docs/requirements/use_cases/programmable_provisioning.rst +++ b/docs/requirements/use_cases/programmable_provisioning.rst @@ -15,6 +15,14 @@ requires additional manual configuration work. It shall be possible to configure provider networks without administrative rights. It should be possible to assign the capability to create provider networks to any roles. +The following figure (:numref:`api-users`) shows the possible users of an +OpenStack API and the relation of OpenStack and ETSI NFV components. Boxes with +solid line are the ETSI NFV components while the boxes with broken line are the +OpenStack components. + +.. figure:: images/api-users.png + :name: api-users + :width: 50% Derived Requirements ~~~~~~~~~~~~~~~~~~~~~ -- cgit 1.2.3-korg