From 923a3c337a44ee44a5a673b0bec8fe46c4b24096 Mon Sep 17 00:00:00 2001 From: ChristopherPrice Date: Wed, 17 Feb 2016 17:22:54 +0100 Subject: Adding new structure for the genesis requirements doc. Also aligned heading levels for readability. Change-Id: I1e673637c044dc84201e922c9d8b4e3142a2ad27 Signed-off-by: ChristopherPrice --- docs/sources/ux-requirements.rst | 147 --------------------------------------- 1 file changed, 147 deletions(-) delete mode 100644 docs/sources/ux-requirements.rst (limited to 'docs/sources/ux-requirements.rst') diff --git a/docs/sources/ux-requirements.rst b/docs/sources/ux-requirements.rst deleted file mode 100644 index ec63d01..0000000 --- a/docs/sources/ux-requirements.rst +++ /dev/null @@ -1,147 +0,0 @@ -.. Copyright 2015 Open Platform for NFV Project, Inc. and its contributors - -.. This work is licensed under the -.. Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 - -=============== -UX requirements -=============== - -Release: OPNFV Brahmaputra - -Requirements for a common user-experience created by the deployment tools. - -High availability requirements ------------------------------- -.. Please add the story reference to each requirement. - -* `GENESIS-9 `_: - Installers shall support the deployment of OpenStack with - High-Availability (for those components that support it in - Liberty) on 3 or more control nodes. Functest tests should - be able to verify that the HA is enabled and functional. - -* `GENESIS-71 `_: - Hitless hardware upgrade: Increase size of a deployment in terms of compute - nodes (add additional compute nodes) without service interruption. - This requirement doesn't mandate upgrade/increasing the size of the control - node cluster. - - -Network setup and configuration related requirements ----------------------------------------------------- -* `GENESIS-20 `_: - Automatically populate discovered servers into install - tool (reduce user-intervention to a minimum). - -* `GENESIS-28 `_: - Installers should support a common configuration file (e.g. kickstart file) - per platform/role, so that the installed OS can be customized - for hardware and role. - -* `GENESIS-43 `_: - Neutron DHCP servers should be configured in HA per tenant. - -* `GENESIS-44 `_: - SDN Controller layer 3 forwarding support. - -* `GENESIS-61 `_: - Support layer 1/2 networking configuration. - -* `GENESIS-62 `_: - Support logical networks for target system. - -* `GENESIS-72 `_: - Support L3-neutron agent as an option for L3. - -* `GENESIS-69 `_: - Provide isolated compute node resources for CEPH OSD. - -Versioning requirements ------------------------ -.. Please add the story reference to each requirement. - -* `GENESIS-12 `_: - Installers should track/control all versions of all components pulled - from external sources (user should be able to identify - the versions and origins of all software components deployed). - -System definition and system configuration requirements -------------------------------------------------------- -.. Please add the story reference to each requirement. - -* `GENESIS-16 `_: - Common ability to input site, topology, and server information. -* `GENESIS-17 `_: - User-configurable parameters available via config files. -* `GENESIS-18 `_: - Allow assignment of different roles to servers, so that hardware and - software can be configured according to the role. -* `GENESIS-19 `_: - Deployment tool to provide for automatic device discovery. -* `GENESIS-25 `_: - Installers should configure NTP servers on the servers for clock - synchronization. -* `GENESIS-40 `_: - Hardware replacement. - -Requirements pertaining to the qualities of the deployment process ------------------------------------------------------------------- - -* `GENESIS-74 `_: - Installers which create a build for Brahmaputra, should create - the build as an "all-in-one" build. The the build process of - the installer creates a single entity (e.g. ISO) - which has - all the artifacts considered and required by all the projects - for Brahmaputra packaged in. Or in other terms and as an example: - If there are 4 different versions of OVS - all these 4 versions - would be contained in the "all in one build". - Note: This requirement only applies to installers which support - a "build" phase (i.e. create a bootable image, like an iso-image - from the different artifacts required). -* `GENESIS-31 `_: - Installers to be agnostic to type of hard drives used. - -Security related requirements ------------------------------ - -* `GENESIS-23 `_: - Installers should enable Mandatory Access Control by default. - Installers should enable MAC either using SElinux or AppArmour. -* `GENESIS-24 `_: - Installers should install ssh keys on servers so that key-based login - can be used for administration. - -Testing related requirements ----------------------------- -.. Please add the story reference to each requirement. - -Installation method related requirements ----------------------------------------- - -* `GENESIS-39 `_: - Ability to install with upstream artifacts. - -* `GENESIS-38 `_: - Installers should supply a script or set of scripts ("deploy.sh") to - automatically install the jumphost (from there, the - entire OPNFV system is automatically installed). - -* `GENESIS-42 `_: - Installers should support offline deployment. Jump host may have - Internet access, but the installers should support offline - installation on target hosts during the deployment phase (either - manually or automatically). - -Documentation related requirements ----------------------------------- - -* `GENESIS-34 `_: - Installers should provide a user guide. - -* `GENESIS-35 `_: - Installers should provide release notes for an OPNFV release as part of - the documentation provided. - - -- cgit 1.2.3-korg