diff options
| -rw-r--r-- | docs/sources/system-requirements.rst | 15 | ||||
| -rw-r--r-- | docs/sources/ux-requirements.rst | 22 |
2 files changed, 26 insertions, 11 deletions
diff --git a/docs/sources/system-requirements.rst b/docs/sources/system-requirements.rst index c48d759..7cb78d1 100644 --- a/docs/sources/system-requirements.rst +++ b/docs/sources/system-requirements.rst @@ -49,9 +49,13 @@ release SDN Controller: =============== + `GENESIS-6 <https://jira.opnfv.org/browse/GENESIS-6>`_: Installers support OpenDaylight Lithium Release +`GENESIS-49 <https://jira.opnfv.org/browse/GENESIS-49>`_: Installers support for ONOSFW + + VM Controller: ============== @@ -61,3 +65,14 @@ Hypervisor: Virtual forwarder: ================== +`GENESIS-46 <https://jira.opnfv.org/browse/GENESIS-46>`_: SFC support + The SFC project needs a version of OVS that supports Network Service Headers ' + (NSH). The required end-system state for the B-release will be an official + OVS patch that Intel is preparing that will provide full OVS 2.4 support. + This official OVS patch is not available yet. Until this official patch is + available, there is a patch available in a private branch that we will have + to use during the life cycle of the B release. This private OVS branch does + not support all of the OVS 2.4 features. The private OVS branch can be + obtained as follows: + git clone https://github.com/priteshk/ovs.git + git checkout nsh-v8 diff --git a/docs/sources/ux-requirements.rst b/docs/sources/ux-requirements.rst index a793c88..0214aa8 100644 --- a/docs/sources/ux-requirements.rst +++ b/docs/sources/ux-requirements.rst @@ -49,17 +49,15 @@ High availability requirements Network setup and configuration related requirements ---------------------------------------------------- -.. Please add the Jira story reference to each requirement. - Note that the below listed "GENESIS-3" Jira story are place holders - and are to be changed for the actual Jira reference. - -* `Jira GENESIS-3 <https://jira.opnfv.org/browse/GENESIS-3>`_: new requirement... - -* `Jira GENESIS-20 <https://jira.opnfv.org/browse/GENESIS-20>`_: Automatically populate discovered servers into install tool (reduce user-intervention to a minimum). +* `Jira GENESIS-20 <https://jira.opnfv.org/browse/GENESIS-20>`_: Automatically populate + discovered servers into install tool (reduce user-intervention to a minimum). -* `Jira GENESIS-28 <https://jira.opnfv.org/browse/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. -new requirement... +* `Jira GENESIS-28 <https://jira.opnfv.org/browse/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. +* `Jira GENESIS-43 <https://jira.opnfv.org/browse/GENESIS-43>`_: Neutron DHCP servers should + be configured in HA per tenant Versioning requirements ----------------------- @@ -85,7 +83,9 @@ System definition and system configuration requirements to servers, so that hardware and software can be configured according to the role. * `Jira GENESIS-19 <https://jira.opnfv.org/browse/GENESIS-19>`_: Deployment tool to provide for automatic device discovery. - +* `Jira GENESIS-25 <https://jira.opnfv.org/browse/GENESIS-25`_: + Installers should configure NTP servers on the servers for clock + synchronization. Requirements pertaining to the qualities of the deployment process ------------------------------------------------------------------ @@ -102,9 +102,9 @@ Security related requirements and are to be changed for the actual Jira reference. * `Jira GENESIS-3 <https://jira.opnfv.org/browse/GENESIS-3>`_: new requirement... +* `Jira GENESIS-23 <https://jira.opnfv.org/browse/GENESIS-23>`_: Enable Mandatory Access Control by default. Installer should enable MAC either using SElinux or AppArmour. * `Jira GENESIS-24 <https://jira.opnfv.org/browse/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 Jira story reference to each requirement. |