diff options
| author |   Georg Kunz <georg.kunz@ericsson.com> | 2016-10-31 22:24:52 +0100 |
|---|---|---|
| committer | Georg Kunz <georg.kunz@ericsson.com> | 2016-11-11 09:19:30 +0000 |
| commit | 7e922675b35bab185ccf99a68637dbfdf877cdf4 (patch) | |
| tree | 5ddb71cd91bdc654a50dd987262d15b735928c6e /docs/requirements/use_cases/multiple_backends.rst | |
| parent | 01b644db5e301278aa4ab8863f8d439eb5a75b90 (diff) | |
Formatting changes and fixing of build warnings
Applying a different sphinx rendering theme to make the document
more readable (in my opinion). The Sphinx config file is based on
the config file of the Copper project. Moreover, this change
fixes a few build-time warnings.
Change-Id: I78f5268436edcfa8c71b8e85a99c7caa54a0e099
Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
(cherry picked from commit 12542964182af4da4daeb58219377a5d1f697ecf)
Diffstat (limited to 'docs/requirements/use_cases/multiple_backends.rst')
| -rw-r--r-- | docs/requirements/use_cases/multiple_backends.rst | 17 |
1 files changed, 8 insertions, 9 deletions
diff --git a/docs/requirements/use_cases/multiple_backends.rst b/docs/requirements/use_cases/multiple_backends.rst index 2aefe8a..a31d1ab 100644 --- a/docs/requirements/use_cases/multiple_backends.rst +++ b/docs/requirements/use_cases/multiple_backends.rst @@ -117,17 +117,16 @@ Given the use case description and the current implementation of OpenStack Neutron, we identify the following gaps: -[MB-GAP1] Limited support for multiple back-ends -''''''''''''''''''''''''''''''''''''''''''''''' +* **[MB-GAP1] Limited support for multiple back-ends** -As pointed out above, the Neutron core plugin mechanism only allows for one -active plugin at a time. The ML2 plugin allows for running multiple mechanism -drivers in parallel, however, successful inter-working strongly depends on the -individual driver. + As pointed out above, the Neutron core plugin mechanism only allows for one + active plugin at a time. The ML2 plugin allows for running multiple mechanism + drivers in parallel, however, successful inter-working strongly depends on the + individual driver. -Moreover, the ML2 plugin and its API is - by design - very layer 2 focused. For -NFV networking use cases beyond layer 2, for instance L3VPNs, a more flexible -API is required. + Moreover, the ML2 plugin and its API is - by design - very layer 2 focused. For + NFV networking use cases beyond layer 2, for instance L3VPNs, a more flexible + API is required. Conclusion |