diff options
| author |   Stuart Mackie <wsmackie@juniper.net> | 2017-08-29 05:21:36 -0700 |
|---|---|---|
| committer | Stuart Mackie <wsmackie@juniper.net> | 2017-08-29 05:21:36 -0700 |
| commit | fce102283bab73ed08c292fce03e39c52f4a1fe2 (patch) | |
| tree | 299e9f8e5daca49f74f207cbe6699295b9115876 /docs/development/scenario/scenariointro.rst | |
| parent | 711967ae9639095ce41500bb0e6f80c8b80fab95 (diff) | |
Added doc directories
Change-Id: I671d7c3ad4f4e5e476c98f53780d867dc94b3089
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, 13 insertions, 0 deletions
diff --git a/docs/development/scenario/scenariointro.rst b/docs/development/scenario/scenariointro.rst new file mode 100644 index 0000000..dd80843 --- /dev/null +++ b/docs/development/scenario/scenariointro.rst @@ -0,0 +1,13 @@ +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. |