User-configurable parameters available via config files

User-configurable parameters available via config.yaml files - with all
defaults shown. Exact parameters and formats for these configuration
files are outside the scope of this requirement (and TBD by Genesis
team). The requirement is simply to be able to support parsing these
yaml config files as inputs to all installers.

JIRA: GENESIS-17

Change-Id: Id484d59205ce6b423329cfa0a86b7d6d22c04dba
Signed-off-by: Tim Rozet <trozet@redhat.com>

diff --git a/docs/sources/ux-requirements.rst b/docs/sources/ux-requirements.rst
index 596e79e..1fd251d 100644 (file)
--- a/docs/sources/ux-requirements.rst
+++ b/docs/sources/ux-requirements.rst
@@ -79,6 +79,8 @@ System definition and system configuration requirements
 * `Jira GENESIS-3 <https://jira.opnfv.org/browse/GENESIS-3>`_: new requirement...
 * `Jira GENESIS-16 <https://jira.opnfv.org/browse/GENESIS-16>`_: Common ability to input site,
   topology, and server information.
+* `Jira GENESIS-17 <https://jira.opnfv.org/browse/GENESIS-17>`_: User-configurable parameters
+  available via config files.
 * `Jira GENESIS-18 <https://jira.opnfv.org/browse/GENESIS-18>`_: Allow assignment of different roles
   to servers, so that hardware and software can be configured according to the role.
 * `Jira GENESIS-19 <https://jira.opnfv.org/browse/GENESIS-19>`_: