Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
JIRA: APEX-133
Change-Id: I7d87f2e463921369cd002b768976fd9cc06c8a91
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
JIRA: APEX-234
Change-Id: Ieb055d5de33177dd6f6b5286f3ff1608d62fbf60
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-227
Change-Id: I5f55f862e564205b2e426e60d741e60bc255f2f4
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
JIRA: APEX-228
Change-Id: I85e6794bf2371116facef60ef4e29c9c9ca79131
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
|
|
Change-Id: I983f4483b328268413d4ec66c753f1219d59fd27
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
- Move deploy option parsing to before network settings parsing,
as performance options are needed during networking setting
parsing.
- Fix numa fdio_enabled option setting
- Add numa to controller hiera hierarchy in tht
opnfv-tht-pr: 53
Change-Id: I0a87c557c8bf653d5a86eccdbb3172733c06716a
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
|
|
Change-Id: Ib7fc4e9ca543a4c678576ea2119fa606ece0095c
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
|
|
Bug where root password was not being set on overcloud nodes when perf
options were specified in deploy settings.
JIRA: APEX-224
Change-Id: I14b8240f40d5901aabdd53814143e0fa002df92b
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-222
Change-Id: I435852fbe1597bf03f617dc14a6718de699b648f
Signed-off-by: Feng Pan <fpan@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>
|
|
Changes include:
- RPM build for congress moved into Apex
- Fixes missing log dir for congress in spec
- Adds missing API network definition for Congress
- Fixes URL for getting doctor driver
- Increases controller default RAM to 10GB due to resource contention
with ODL
- Fixes Congress service config/db sync in THT to be in step 3
opnfv-tht-pr: 51
JIRA: APEX-212
Change-Id: I4a55646e7ef851782ae0d1963f7b479086958365
Signed-off-by: Carlos Goncalves <carlos.goncalves@neclab.eu>
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
For virtual deployment, we will attempt to enable nested kvm,
if that is not possible, qemu will be used instead. Only support
Intel for now.
Change-Id: I951835c3e3faedfc698a4c879366d6c96249e5c1
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
needed
JIRA: APEX-198
Adds support for baremetal deployments where external connectivity is only
provided via the jumphost. The connectivity test is done by pinging an
external IP (8.8.8.8 by default) for each node. If ping fails for any of
the nodes then NAT is added.
Change-Id: I8d59beb03c3b2998deaec5dc7536fa7a5b1f7718
Signed-off-by: Markus Kullberg <markus.kullberg@nokia.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>
|
|
Run a pcs cleanup before db sync and also at the end of the deployment.
This will give processes a chance to recover in case there has been
any kind of error that would lead to a process being scored -INFINITY
due to repeated failed startup that may have been caused by load during
the deployment, or another latent issue.
Print out any services that are failed in pcs at the end of deployments.
opnfv-tht-pr: 41
Change-Id: Idf4f03cd0463a3facd0726483091ac6f1b3bf000
Signed-off-by: Michael Chapman <michapma@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>
|
|
|
|
|
|
JIRA: APEX-207
Change-Id: I6fb8aa003ea485ce49d882b6c2a7842dc7b814cd
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-185
Change-Id: I1e281f5905cc1db05d0f654503d91acda853c183
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>
|
|
|
|
|
|
Previous patch set this to be the public IP of the first controller.
However we only allow ODL to bind to the admin/API IP of the first
controller for security reasons.
JIRA: APEX-152
Change-Id: I22addbb9e7c3fcd850b9695b846357bf9447cd50
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>
|
|
|
|
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>
|
|
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>
|
|
|
|
Apex Brahmaputra as I have had many issues getting a Colorado environment up and running."
|
|
JIRA: APEX-201
Change-Id: I3ba8d5e38e203bb4f23679a3b91de97c591de146
Signed-off-by: Tim Rozet <trozet@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>
|
|
Change-Id: Ibed808350163379fcfa5178c78fabe2f47e491fc
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
JIRA: APEX-152
Change-Id: Id64a42531711c53ad453cd176aab2a9773a71811
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
opnfv-tht-pr: 37
JIRA: APEX-158
Change-Id: I079d22e8ee7798bddf7f2f1b6cc3f1b49f1d5773
Signed-off-by: Dan Radez <dradez@redhat.com>
|