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>
|
|
Change-Id: I63606f7cc200ddbe35c6df2cbb56fa442c2bfb9b
Signed-off-by: Tim Rozet <trozet@redhat.com>
(cherry picked from commit e0eda9d2ce02eb0afddd66f328f8794b073a7958)
|
|
opnfv-tht-pr: 131
Change-Id: I112d454078bd29a386b8557bf1d015d81f328d61
Signed-off-by: Feng Pan <fpan@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>
|
|
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 yardstick option to deploy settings, installs docker and
yardstick image to undercloud.
Change-Id: I3a2a1d6bcdfe5becd11d6d9f22218837c572d5da
Signed-off-by: Manjunath Ranganathaiah <manjunath.ranganathaiah@intel.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>
|
|
JIRA: APEX-374
Change-Id: Id7509d6c6528310cefc62522d3a90ddee19146a9
Signed-off-by: Tim Rozet <trozet@redhat.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>
|
|
'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-347
Change-Id: Ibc6d141e20faf613e0f6314286b55aff01ce862e
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
The network_settings_file variable is actually the inventory file,
this patch renames it to match.
Change-Id: Id4d0b792b8426b4e0b1c61270fe2e6da89559413
Signed-off-by: Michael Chapman <michapma@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>
|
|
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>
|
|
configuration""
|
|
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>
|
|
Right now we use a ntp_server parameter set in deploy.sh, but since
new network_settings file contains ntp information already, we can
use those values instead.
JIRA: APEX-266
Change-Id: I717af80b967971ea9111002d657972efd94a163a
Signed-off-by: Feng Pan <fpan@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>
|
|
JIRA: APEX-294
Change-Id: I4b9aed3fc2ea35a918203a0edc995b73020d122c
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
VLAN support allows a set of nodes with a single nic to deploy removing
the need for --flat. flat was not well maintained or tested.
Change-Id: Ieae1c2350c83544ce50048b44300fa0b8e68dd43
Signed-off-by: Dan Radez <dradez@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>
|
|
Change-Id: I602279b30b035cfc667e4ee9b83905a638440abb
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Change-Id: Ib03728e8ffe9c65044b32b4348e9c1c88862c6e3
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Now if an inventory file is provided to clean, those nodes will be
powered off.
JIRA: APEX-250
Change-Id: I2d78285717726c3d1c9d7d88c38e706d4617e337
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
- increasing required test coverage to 90%
- also consolidating some repeated code into functions
Change-Id: I6b582478c509c24fce43224a516414e1ead6c8e4
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
The deploy settings values are embedded in a dictionary inside a
generic object. This patch makes the deploy settings object
a dictionary so the values can be accessed directly without
having to unnecessarily drill down through an empty object
to the dict that holds the content intended to be managed by
the deploy settings object.
- adding tests to cover DeploySettings 100%
Change-Id: I4ba625cd7b51cfb6c1f91c74f1d332d1e3dd9a8e
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Change-Id: I983f4483b328268413d4ec66c753f1219d59fd27
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Change-Id: Ib7fc4e9ca543a4c678576ea2119fa606ece0095c
Signed-off-by: Dan Radez <dradez@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>
|
|
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>
|
|
|
|
Currently there is no way to specify logically or physically the nic
order to be used on overcloud nodes. We always hardcode to use nic1 for
admin network, nic2 for private, etc. This patch allows a user to not
only decide which logical nics to use for which network, but also
specify physical interface names if they need to.
This is done on a per role basis, due to tripleO limitation. So a user
is able to specify nic order/names for compute and controller roles
separately.
If a user specifies nic order, they must specify it for all networks
other than admin network. We assume if admin network is unspecified it
uses "nic1", so that name is reserved in this case. A user is also
allowed to specify a mixture of logical and physical names, for example
"nic2" and "eth3" on another network.
JIRA: APEX-151
Change-Id: Ie9d4abb463cf8f8788913cb4bcf9486830adc449
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-141
Change-Id: I9983ec5583100b7c536524a01e64bb6884b38d1d
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
JIRA: APEX-201
Change-Id: I3ba8d5e38e203bb4f23679a3b91de97c591de146
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Ibed808350163379fcfa5178c78fabe2f47e491fc
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
- syntax updates to match pep8 standards
- tests to cover apex_python_utils.py
Change-Id: Ifac06fdbb97266f1b574b20610979b6965d6dd55
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
* changes:
Fixes IP failure during os-collect-config ping check
Adding VLAN support
|
|
JIRA: APEX-136
JIRA: APEX-30
Change-Id: I7cbbe11f4c1f1455dba253733c78fe8dc215de97
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
JIRA: APEX-133
opnfv-tht-pr: 29
Change-Id: I3080c91c3995ed946b902a75907ef11cb349fc33
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-177
Change-Id: I6ee95a3c525fb58699fb3af795a66639f217214c
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|