diff options
author | Stuart Mackie <wsmackie@juniper.net> | 2017-09-14 23:26:31 -0700 |
---|---|---|
committer | Stuart Mackie <wsmackie@juniper.net> | 2017-09-14 23:26:31 -0700 |
commit | fd876b7dbc7d517a706b22e52bf6f0e8f79a0b4b (patch) | |
tree | 996858dd4abe0221f8f9d54a2aeeb4ffb9971b8e /docs/development/scenario/scenariointro.rst | |
parent | fce102283bab73ed08c292fce03e39c52f4a1fe2 (diff) |
Docs
Change-Id: Iea3001f8414267f1535353f28d30d45daf9a3e66
Signed-off-by: Stuart Mackie <wsmackie@juniper.net>
Diffstat (limited to 'docs/development/scenario/scenariointro.rst')
-rw-r--r-- | docs/development/scenario/scenariointro.rst | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/docs/development/scenario/scenariointro.rst b/docs/development/scenario/scenariointro.rst deleted file mode 100644 index dd80843..0000000 --- a/docs/development/scenario/scenariointro.rst +++ /dev/null @@ -1,13 +0,0 @@ -OPNFV Scenarios ---------------- - -The OPNFV project provides an integration and deployment environment for a variety of components -that can make up a virtualisation platform. OPNFV identifies these variations on the composition of -the platform as scenarios. - -A scenario in OPNFV can be defined as "a deployment of a specific set of platform components". The -composition of a scenario may include specific SDN controller technologies, specific accelerate -switching technologies, or even specific configurations of components to achieve targeted platform -capabilities. Each scenario behaves differetly and it is important to understand the behaviour you -want in order to target the specific scenario you wish to deploy prior to working with the -OPNFV platform. |