| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
JIRA: GENESIS-34
JIRA: GENESIS-35
Change-Id: Ie43b76b5eb852d6731f9d5bb6f20795020baa6bc
Signed-off-by: Weidong Shao <weidong.shao@huawei.com>
|
|
Description: 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 -b nsh-v8 https://github.com/priteshk/ovs.git
JIRA:GENESIS-46
Change-Id: Iae5a102340ba5b7a75651c7efb9256566177ed8d
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
Project Name: (nfv-kvm)(NFV Hypervisors-KVM)
Project Lead: Don Dugger (donald.d.dugger@intel.com)
Target Release: B release
List of proposed requirements:
1) Install Kernel package with NFV enhancement support
2) Install QEMU package with NFV enhancement support
3) Provide a method so that user can input platform specific parameters.
OPNFV release: Brahmaputra
Timeline: In order to integrate into CI and fix bugs we would require implementation
at least 2 months prior to B-release
Purpose:
Special kernel/QEMU functions may be needed to meet advanced NFV usage requirements,
like real time, live migration etc. The nfv4kvm project provide such functionality,
so it will be good to integrate the kernel/QEMU into the installer.
Proposed requirements:
1) Nfv-kvm would provide kernel source and QEMU source that meet NFV requirement,
including real time, live migration etc. The installer can install the kernel/qemu
package build from the kernel/qemu repo code.
2) Grub entry would be updated to adding NFV specific kernel parameters like "isolcpus",
"nohz_full" etc. The installer should get input from user for such parameters.
JIRA: GENESIS-50
Change-Id: Ifb52d1bfeb60c79cbb51c9c6d16da204f652f467
Signed-off-by: Wei Shao <weidong.shao@huawei.com>
|
|
|
|
An installer should support the installation of KVM version 2.0 or newer.
JIRA: GENESIS-8
Change-Id: I2da8cd17b1a190cf805f5acadf72c3cf0bd460c0
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
This requirements proposes that installers for B-release support
ONOSFW.
Change-Id: Ia74dd5ba97a2319a318258a0a9bd560dfc34079e
JIRA: GENESIS-49
Signed-off-by: Weidong Shao <weidong.shao@huawei.com>
|
|
This requirement proposes that every installer MUST be capable of
installing OpenDaylight SDN Controller. The version that will be
required for Brahmaputra will be Lithium.
JIRA: GENESIS-6
Change-Id: I0efe7ddef52eb0c1c281071231c2ee2aec2cf7c9
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Adds Liberty requirement for all installers. Also cleans up the rst
structure to be valid.
JIRA: GENESIS-7
Change-Id: Ia1760d02119912163c86599cdee997596960a841
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
This requirement proposes that installers for B-release use at least
Centos 7 or Ubuntu 14.04 as their target OPNFV system base OS. Version
numbers may be higher, but must be at least be major versions listed
previously.
JIRA: GENESIS-4
Change-Id: I389b7b0f475c8eaf5c163c48e83d066d60119a59
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Base templates to articulate requirements which
are common and are to be followed by all installers
participating in Genesis. Template provided:
* Requirements for common system components
* Requirements for a common user experience
In additon, a high level directory structure is
put in place - to allow for later easy migration
of current BGS/Genesis common files.
Change-Id: I219246ee33eefe3a5b1cec421223d00745f0f910
Signed-off-by: Frank Brockners <fbrockne@cisco.com>
|
Weidong Shao
Jonas Bjurel
Tim Rozet
Frank Brockners