Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
opnfv-tht-pr: 48
JIRA: APEX-206
Change-Id: Icfb5356252f4e862f8a9cd4fd1914951ab45baf4
Signed-off-by: Tim Rozet <trozet@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>
|
|
We had a regression where we missed adding bgpvpn code back into master.
opnfv-tht-pr: 45
JIRA: APEX-200
Change-Id: I44da1d653e13c48f276ad29daac1eb6f4f2d629b
Signed-off-by: Tim Rozet <trozet@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>
|
|
add os-onos-sfc-ha.yaml for onos sfc function deployment.
opnfv-tht-pr: 27
JIRA: APEX-172
Change-Id: I07d708d201ef1d97efbfffd5aca85d8a284f7c96
Signed-off-by: bob zhou <bob.zh@huawei.com>
|
|
SFC for colorado will be based on OVS 2.5.90 which does not need 3.13
kernel. This patch removes 3.13 kernel updates, adds OVS 2.5.90 and
sets default odl_version to use boron (required for SFC with OVS
2.5.90). Also updates OVS build to a working one for ONOS.
JIRA: APEX-156
JIRA: APEX-199
Change-Id: I095290d925138122f24e891f8412497f9a2c3141
Signed-off-by: Tim Rozet <trozet@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>
|