summaryrefslogtreecommitdiffstats
path: root/docs/installationprocedure/template-os-nosdn-nofeature-ha/introduction.rst
diff options
context:
space:
mode:
authorChristopherPrice <christopher.price@ericsson.com>2016-07-13 14:43:32 +0200
committerRyota Mibu <r-mibu@cq.jp.nec.com>2016-07-20 12:13:50 +0000
commit3ecf7ea5fe5611fea3550fb8065f5ffe0859f17d (patch)
treed06c6bba0e2acf43c74f9685464bc6291120ef78 /docs/installationprocedure/template-os-nosdn-nofeature-ha/introduction.rst
parentd4138a84179cfed379909578d65085cc5a197511 (diff)
Creating a template scenario installation file for Colorado.
Aside from my likely copywright infringements, please review/comment. The basic idea is we create a "master" versions for each colorado installer then each scenario derives from the master files to produce their own. The template is intentionally modular for that purpose. Change-Id: Ic5ca72ece8eb462e6e6e7307d3cde32ea7760b23 Signed-off-by: ChristopherPrice <christopher.price@ericsson.com>
Diffstat (limited to 'docs/installationprocedure/template-os-nosdn-nofeature-ha/introduction.rst')
-rw-r--r--docs/installationprocedure/template-os-nosdn-nofeature-ha/introduction.rst18
1 files changed, 18 insertions, 0 deletions
diff --git a/docs/installationprocedure/template-os-nosdn-nofeature-ha/introduction.rst b/docs/installationprocedure/template-os-nosdn-nofeature-ha/introduction.rst
new file mode 100644
index 000000000..fffe5e867
--- /dev/null
+++ b/docs/installationprocedure/template-os-nosdn-nofeature-ha/introduction.rst
@@ -0,0 +1,18 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International
+.. License. .. http://creativecommons.org/licenses/by/4.0 ..
+.. (c) Christopher Price (Ericsson AB) and others
+
+Introduction
+============
+
+This document provides guidelines on how to install and configure the
+<template> scenario of OPNFV including required software and hardware configurations.
+
+Although the available installation options give a high degree of
+freedom in how the system is set-up, including architecture, services
+and features, etc., said permutations may not provide an OPNFV
+compliant reference architecture. This instruction provides a
+step-by-step guide that results in an OPNFV Compliant deployment.
+
+The audience of this document is assumed to have good knowledge in
+networking and Unix/Linux administration.