| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Installers should support multiple kinds of network configurations for
deployments. These shall include the following:
1) Multiple VLANs (untagged and tagged links)
2) NIC Bonding/Etherchannel
3) Multiple NICs
These types may also be in combination with one another. For example, if
a deployment uses 4 logical broadcast domains (VLANs) it may be split
into 4 sub-interfaces on a single interface, which is then mapped to a
bonded link consisting of 2 links.
JIRA: GENESIS-61
Change-Id: Id30cfe1c01c3b82d94aaf454d6496180c29732e9
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Installers must support being able to separate network traffic for
OpenStack + SDN controllers into these logical networks:
1) Admin network - used by OpenStack for Admin user traffic
2) Private network- used by OpenStack for inter-component traffic
3) Public network- user + internet access. References OpenStack public
network.
4) Storage network - for storage related traffic only
OpenStack is configurable in that it allows its components to be bound
to specific networks. Installers should also support configuring
OpenStack this way, and separating components/traffic across these
logical networks.
For example, keystone admin endpoint should only be available on the
Admin network. Access to keystone admin endpoint on Public network would
not be allowed.
Note: This requirement does not restrict installers from deploying other
types of logical network configurations such as combining all traffic
into a single logical network, or combining some logical networks into
one. The requirement simply states that the 4 listed above must be
supported and the default option.
An optional 5th network for lights out management (IPMI access) is also
typically used (especially with baremetal deployments), but it is beyond
the scope of this requirement (logical OpenStack networks), and it's
network definition/configuration should be defined by the
environment/POD being used.
JIRA: GENESIS-62
Change-Id: I3942bba91f0831a1f8088fa75968d23aa968eebe
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
|
|
|
|
JIRA: GENESIS-34
JIRA: GENESIS-35
Change-Id: Ie43b76b5eb852d6731f9d5bb6f20795020baa6bc
Signed-off-by: Weidong Shao <weidong.shao@huawei.com>
|
|
|
|
default"
|
|
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>
|
|
Because ODL Lithium doesn't support IPv6 in ODL-L3, in order to set up IPv6 in integrated
OS+ODL environment, we need to use neutron-l3-agent instead of odl-l3, and ODL will be
used only for L2 connectivity. See our gap analysis
https://wiki.opnfv.org/ipv6_opnfv_project/ipv6_gap_odl. Therefore we have created this JIRA
issue "Support L3-neutron agent as an option for L3 for setting up".
JIRA: GENESIS-72
Change-Id: I86d7cdf6b8a802a5766f57fe33e9c8b4b7916b78
Signed-off-by: Wei Shao <weidong.shao@huawei.com>
|
|
|
|
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>
|
|
|
|
We currently have most openstack services in HA, including
neutron-dhcp-agent service. Meaning that there are multiple neutron-dhcp-agent
processes running on the controllers. One of those is selected when
there is a request to create a dhcp server namespace. A single dhcp
server will be created for that tenant.
This issue is created as a proposal for requiring OPNFV Target System to
enable multiple dhcp servers per tenant in HA, so that a tenant would
have multiple dhcp servers in HA in case one goes down.
JIRA: GENESIS-43
Change-Id: I1386c790834c0924ec90eb505d14ca7c8449f408
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
JIRA: GENESIS-25
Change-Id: I9d97df251e5942cfa4a77af85aa45631ec836325
Signed-off-by: Weidong Shao <weidong.shao@huawei.com>
|
|
JIRA: GENESIS-23
Change-Id: Ic39bef4daa6dc80a2c00bc0f0ddf9f26b46da333
Signed-off-by: Narinder Gupta <narinder.gupta@canonical.com>
|
|
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)
Change-Id: Ie564897469a152f11a91b07339972d5e8c50f284
JIRA: GENESIS-38
|
|
UX Requirement. Also fixes various line length issues
JIRA: GENESIS-16
Change-Id: I071a4571b922b526abc8325c430b4b933f08d3c5
Signed-off-by: Tim Rozet <trozet@redhat.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>
|
|
Slogan: 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.
Change-Id: Ieab5adeb9938c99387527eeed3dfac1931890bf1
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
Description: 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.
JIRA: GENESIS-71
Change-Id: Ie716504ff58208394545e2ee47f347fb6dc3d53f
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
URL: https://jira.opnfv.org/browse/GENESIS-24
Description: Installers should install ssh keys on servers so that key-based
login can be used for administration
Change-Id: I7e04a09727f30c477332f870e43629943c4c0169
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
URL: https://jira.opnfv.org/browse/GENESIS-20
Description: Automatically populate discovered servers into install tool
(reduce user-intervention to a minimum).
Change-Id: I45d6291f5922ebfe81d7258943692b4786ee0326
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
Change-Id: Iacd33bb2b41158931242efb24d7762261170f034
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
URL: https://jira.opnfv.org/browse/GENESIS-18
Description: Allow assignment of different roles to servers, so that
hardware and software can be configured according to the role.
Change-Id: I769391dc3e82492439141b0d9fd9fdf9c29c7bb6
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
URL: https://jira.opnfv.org/browse/GENESIS-12
Description: Add a new requirement (UX / Versioning):
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)
Change-Id: I39884c4b26e32800f145c1b8013491019521de48
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
URL: https://jira.opnfv.org/browse/GENESIS-9
Description: Add a requirement: The installer 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.
Change-Id: I56c5e905bb27c19b4b25e9cd796c03ec10b5caa3
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.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>
|
Tim Rozet
Weidong Shao
Frank Brockners
Jonas Bjurel
Narinder Gupta
David Duffey