Age | Commit message (Collapse) | Author | Files | Lines |
|
JIRA: APEX-443
opnfv-tht-pr: 133
Change-Id: I03b28bdcc6d0649920fd58fb3400b2a4e5891e68
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
opnfv-tht-pr: 131
Change-Id: I112d454078bd29a386b8557bf1d015d81f328d61
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
Interface options is needed for nosdn-fdio scenario to disable
vlan strip offloading for enic.
Change-Id: I7d7e3d7e6e0c822a13113911a41a3d076ecbd509
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
Change-Id: I7eb2d7bb62d61ca1ab7177332bb27329da85ad48
Signed-off-by: Dan Radez <dradez@redhat.com>
(cherry picked from commit a684f6b753749c355aee06412bd0f22779357089)
|
|
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>
(cherry picked from commit 7d994a3c3e18227c26bf58049e4d5780144ecf98)
|
|
Adding the support to run the "Real Time KVM" kernel in the compute
node(s) to reduce the network latency caused by the virtualization of
the network functions. Since the current "Real Time KVM" kernel
doesn't support physical to logical network interface mapping yet, we
need to use the real physical interface name rather than the logical
interface name for all compute interfaces in network_settings.yaml.
Also updates tests for the network settings changes and fixes a bug
where interface was being queried on the controller nics before it
interfaces were validated.
JIRA: APEX-128
Change-Id: Iccb6c9fbdcf7e3b482f4283039ef17c38e0a6df7
Signed-off-by: davidjchou <david.j.chou@intel.com>
Signed-off-by: Tim Rozet <trozet@redhat.com>
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
This patch adds dovetail option to deploy settings, installs
dovetail image to undercloud.
Change-Id: If7a763d9f6b27655dbb1f5855f438ab11bd88a82
Signed-off-by: zshi <zshi@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>
|
|
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>
|
|
This patch adds yardstick option to deploy settings, installs docker and
yardstick image to undercloud.
Change-Id: I3a2a1d6bcdfe5becd11d6d9f22218837c572d5da
Signed-off-by: Manjunath Ranganathaiah <manjunath.ranganathaiah@intel.com>
|
|
Since Boron ODL servers always the l3 usecase
so the l2 differentiation does not make sense
anymore.
Depends: https://gerrit.opnfv.org/gerrit/27605
Change-Id: I8bb55387001dfc81845134639ab4e913072f9a27
Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
|
|
|
|
|
|
Now in inventory file a user can declare 'disk_device' which will allow
the user to specify which disk on their overcloud server to use for
installation. The variable can be a comma delimited list, which will
search in order post-introspection for the first device on the node that
exists. The default disk used will be sda for deployments.
Currently defining a per node disk is not supported by OSCLI, so
although defined that way in Apex inventory, only the last definition
will be used for all nodes.
Other changes include:
- Various fixes in inventory parsing
- Makes bash writing a common function
- Introspection now enabled for baremetal deployments
JIRA: APEX-296
Change-Id: I330d91eb17408ccfceb7a99c25edbae5ce6d848d
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
At present, odl_version is case-sensitive hence opnfv-deploy fail
with 'odl_version: Boron'. So the change fix it.
Change-Id: Ifd611c56b9802b4c5033728e70cce03eb55985cf
Signed-off-by: Tomofumi Hayashi <tohayash@redhat.com>
|
|
Change-Id: I78bbc34aff1d00b4113cfb2ebedf7e24e317a358
Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
|
|
Introduces new (hidden) cli option to change composable env config.
This parameter then will use the provided file, for example,
csit-environment.yaml instead of the typical opnfv-environment.yaml.
The effect is using less services required for ODL CSIT snapshots.
Note: this will not work with perf options, but those are not required
currently for ODL CSIT.
CSIT also does not need ceph, so providing a new deploy option to
allow disabling it.
JIRA: APEX-362
Change-Id: If3833b1acceeb23ef9e12c90df6cc9607bd8c724
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
Also contains various network parsing fixes.
JIRA: APEX-361
Change-Id: I5e40ed67267d5ded85adc2982a8726ebbceaeae5
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-351
Change-Id: I9b8b74073287005221a7a3f6dfe2d52a7d1cf667
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
|
|
|
|
Change-Id: Iecf511aa48d3123b7a2ed445cc5ff6f5d462fb83
Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
|
|
'usable_ip_range' was confusing for a lot of users, and most thought it
encompassed all of the defined ranges in the network settings file (like
floating_ip_range and introspection_range). This renames it to be more
accurate.
JIRA: APEX-288
Change-Id: I2e106666df1bfd007f150279e2e0387a64cd0f48
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-346
Change-Id: I9ffa32da906f50441dfc05610d0668e84c992e81
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-347
Change-Id: Ibc6d141e20faf613e0f6314286b55aff01ce862e
Signed-off-by: Dan Radez <dradez@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-340
Change-Id: I3ddc2b28b46720ce1b9af28ae23f4a24690008e4
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
|
|
Also depend on https://github.com/radez/puppet-fdio/pull/14
JIRA: APEX-337
opnfv-tht-pr: 92
Change-Id: Ic3d2f04bfd1983c38e09a2bfa3992a572fc9c6c1
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
|
|
Also includes other various fixes.
JIRA: APEX-292
Change-Id: I5e8cedce5af43544963c1e7de582e7646b1c841a
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
This reverts commit 3228f00248cda32671fb0e6a02059bea6ae66c99.
There is more settings that will need to added for the functionality this patch it intending to add. The JIRA will be updated and the feature will be worked on for Danube.
Change-Id: I258ba552cbb49e6fa188a8dffe860e8dac2e3f5f
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
JIRA: APEX-335
Change-Id: I00b148e3f2a299b6e16a91f6e8e3ed447a86e117
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Add a new parameter 'vlan_id_range' for tenant vlan range, which can
set the 'network_vlan_ranges' for 'datacentre' network in ml2.ini on
both compute and controller.
Change-Id: I5c190fb2d5d582d0d5f56d4c18cf32502b758bd8
JIRA: APEX-272
Signed-off-by: Peng Liu <pliu@redhat.com>
|
|
- proposed in genesis
https://wiki.opnfv.org/display/genesis/Common+Network+Settings
- This patch updates the network_settings files in the config/network dir
and updates the associated bash, python and python tests relative to
the new yaml structure and nomenclature used in the proposed settings
file
JIRA: APEX-262
Change-Id: Ib0dc9d0f21465b38f2a53cff20f71fb9230bfc48
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
|
|
Add inline yaml to deploy_settings.yaml describing all the available options,
and mention this in the documentation.
JIRA: APEX-259
JIRA: APEX-256
Change-Id: If86b1b1d4db2701d1d584fcfd62d6f1b5d53014b
Signed-off-by: Michael Chapman <woppin@gmail.com>
|
|
We currently default that instances should be pinned to the first CPU of
the nova-compute host. We want to remove this default, and have the
default as all CPUs. This patch removes it for fdio and ovs-dpdk
scenarios.
opnfv-tht-pr: 74
JIRA: APEX-187
Change-Id: Iacaa699eb3948b58beff1628dfd1bf008c4c9c5a
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
2048 is the acceptable value where default Virtual deployments will
still work. A user can then modify deploy_settings in order to increase
number of huge pages to something other than the default.
JIRA: APEX-184
Change-Id: I7962c8e1ae09df60c51375b4ed343b44bce52b59
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
Changes include:
- starting vpp with pci addr of tenant nic
- setting performance options for fdio scenario
- creates nosdn fdio scenario (needs newtorking-vpp, etc)
- starts HC if ODL is used
opnfv-tht-pr: 46
JIRA: APEX-133
Change-Id: Ie7a7f1418b94dfb82255ec9aebc550a955dd696a
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
This patch contains the following:
- Add dns and nic information in network settings file
- Add ipv6 option for find_ip function in common-functions.sh
- Change neutron commands to handle IPv6 during post deploy,
skip NAT configuration if IPv6 is configured.
- Fix an error in python library when generating floating ip
range.
JIRA: APEX-130
Change-Id: I27da7f7a714f42ee827be7091fcb1a6d89a0aae8
Signed-off-by: Feng Pan <fpan@redhat.com>
|