Age | Commit message (Collapse) | Author | Files | Lines |
|
Also updated os-net-config to enable VPP service on startup,
as well as updating show interfaces command.
JIRA: APEX-407
os-net-config-pr: 6
opnfv-tht-pr: 129
Change-Id: I77c590e966d2532d894ec96bb60ffdf914a90f6d
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
JIRA: APEX-129
opnfv-tht-pr: 111
opnfv-puppet-tripleo-pr: 18
Change-Id: I71de5802ed476b6f78ad5a718ac15d9aec9a6a1d
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
This fixes nosdn OVS DPDK scenarios to work with OVS 2.6. It also adds
support for the ODL DPDK scenario. OVS DPDK configuration is done
during preconfig on compute nodes. All nodes make use of first boot
script to get kernel params like hugepages. The network settings are
modified to use real nic names for the virtual network settings file.
This is required due to a timing bug with os-net-config and using
first-boot script. The network settings file also contains the UIO
driver to use with DPDK.
JIRA: APEX-314
opnfv-tht-pr: 117
Change-Id: I46b6fca71ecec38981968133ba2411f64d7c6445
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
opnfv-tht-pr: 113
opnfv-puppet-tripleo-pr: 16
os-net-config-pr: 5
Change-Id: I0c34889db27fd71e1b73e860850b81a08707c324
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
This patch adds support for ODL L3 FDIO scenario.
Introduces a new deploy settings parameter, odl_routing_node, to
indicate the routing node's hostname. This parameter will only
be used for this scenario.
Change-Id: I8df3eb701299007761c6cec42c4ca318b124a0b8
opnfv-tht-pr: 108
os-net-config-pr: 4
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
opnfv-tht-pr: 97
opnfv-puppet-tripleo-pr: 10
Change-Id: Idfc109fc984f20b096a23d12864a027146a9c74c
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Changes:
- Kernel parameters are now set through first-boot.yaml during deployment. No custom
images will be built. Note that all nodes will be configured the same way, we only
use compute's kernel parameter settings currently (from deploy settings file)
- Add support for VPP interface type in network settings file, it is now possible
to specify vpp_interface type and uio_driver for tenant nic in network settings
file. A new example config, network_settings_vpp.yaml is added.
- Add support for odl_l2-fdio scenario.
Limitations:
- Physical NIC names must be specified in network settings file, numbered nic names
such as nic1 are not supported for fdio scenarios.
- The same kernel parameters will be configured for all nodes. The paramters will be
taken from compute kernel parameter section in deploy settings file.
opnfv-tht-pr: 104
opnfv-puppet-tripleo-pr: 12
os-net-config-pr: 3
Change-Id: Ie9d6151e6e58d11da3c66fbcabe4a0886c3fa152
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
opnfv-tht-pr: 98
opnfv-puppet-tripleo-pr: 11
Change-Id: I971bb2c94eb9500c81b25adf5019fd02f8e90053
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
In order to make gluon really deployable some more things
need to be done:
- Add pull request 103 which add yaml files which
point to gluon puppet
- Rename the scenario to odl-gluon similar to bgpvpn
scenario
- Add tht of gluon to overcloud-deploy-functions.sh
JIRA: APEX-379
opnfv-tht-pr: 103
opnfv-puppet-tripleo-pr: 13
Change-Id: I3ccfb5a279f1df21c4da79fc47039b3c0b6e5495
Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
|
|
This patch adds first version of gluon scenario config file,
as well as introducing etcd service in puppet-fdio and T-H-T.
JIRA: APEX-379
opnfv-tht-pr: 96
opnfv-puppet-tripleo-pr: 9
Change-Id: Icef29520d093e005dba9cbc5cf0e3fd1ed893cf4
Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
|
|
We need the default pool to match the default external network we create
so that using nova to create floating ip pools without specifying the
newtwork will work in temptest tests.
JIRA: APEX-380
Change-Id: Icbd8c3a3810bd93d71e9e5954c587455165a8445
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Without specifying the provider network type or physical network results
in the default tenant network type being used upon external network
creation (for us this means vxlan). Previously this worked fine because
Neutron L3 agent and ODL L3 would assume to use br-ex. This is no
longer true in ODL new nettvirt, and needs to be explicitly flat along
with the correct physical network.
Also includes minor fix for Manila service naming that was fixed
upstream.
JIRA: APEX-300
Change-Id: If5d467a811baafe01b725dd530938482fdd3fd03
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
os-odl_l2_nofeature is now deprecated since new netvirt only supports
odl_l3.
JIRA: APEX-299
Change-Id: I3557ecb85fa4cd11bba96aa9410e56a8e8cceb00
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-236
Change-Id: If237340529f2b9898d91c420b004770e0f883ce0
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-236
opnfv-tht-pr: 59
Change-Id: Ic8fad4abb3846c57d218b2b23ef44750a644fe73
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-225
Change-Id: Idd1d7ec895be2812475c086ea4ba67f7acae3003
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
opnfv-tht-pr: 49
JIRA: APEX-210
Change-Id: I9ed97588e8ae70d8ded6d2939c6a62d38393d8de
Signed-off-by: Michael Chapman <michapma@redhat.com>
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
SSH keys for the nova account are required for the nova resize
functionality. A new pair of keys is generated for each deploy.
In addition, host keys are populated and a shell is provided to
the nova user on all compute nodes via puppet.
opnfv-tht-pr: 43
Change-Id: Ibde6877d279bc0b87553301fbce44975286cb092
JIRA: APEX-147
Signed-off-by: Michael Chapman <michapma@redhat.com>
|
|
opnfv-tht-pr: 34
opnfv-puppet-tripleo-pr: 4
JIRA: APEX-126
Change-Id: I050e7ae2e94779c1886f670841aa4e2dec4aa8d2
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
|
|
Can be set by setting domain_name in network_settings. Defaults to
dummy opnfvapex.com.
JIRA: APEX-183
JIRA: APEX-182
Change-Id: Ib7c279a1c8432b8635f72e5cc667f16b9cd65159
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Changes include:
- Fixes bug where baremetal control nodes would deploy to ironic nodes
labeled 'compute', and cause deployment failure
- Makes virtual deployments also use flavor types when deploying
JIRA: APEX-205
Change-Id: I84e1a6d1e2ccc3391ad2b4e34ea6ca62d480d64f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-196
Change-Id: I21f63e69ecc4d5b979ed4780c6e92e3ad272b8d7
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-168
opnfv-tht-pr: 22
Change-Id: I224b16be24b34e245d22c9321ca94ebe52c52dfd
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Disables:
- swift
- tripleO ring builder
- Sahara
opnfv-tht-pr: 13
Change-Id: I50c3338f0b071787c277390b39d86a4e42d30a46
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
New param introduced into THT that exposes the image to use for the
Controller. The new var is defaulted to use overcloud-control and is
causing master to fail.
Changes Include:
- Adds opnfv-environment yaml file to use for common parameters
required in all deployments
- Defaults controllerImage to be overcloud-full
Change-Id: I5da8921d9c9efd167748a3d6f42866d18f46d2b7
Signed-off-by: Tim Rozet <trozet@redhat.com>
|