Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
|
|
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>
|
|
|
|
Try moving mongo to be the first core service brought up, so that
it doesn't interfere with heartbeats on any active services
opnfv-tht-pr: 40
Change-Id: If166eae94712d3812f5c63ef0f63bc511f7d55d2
Signed-off-by: Michael Chapman <michapma@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>
|
|
opnfv-tht-pr:39
Change-Id: I0fc1f5ce008a93b9eaa37603086fbe785d40da20
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
- fd.io package repo & vpp
- puppet-fdio
JIRA: APEX-133
Change-Id: I32ee46b796983a114582ddad603c43eefe5f4dea
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>
|
|
|
|
python-redis is a dependency of ceilometer and aodh, but is missing
from mitaka overcloud builds. The package install is conditional so
that if this is fixed upstream the build won't break.
Change-Id: I22b62b77d774c4de3b9af57e8bbcb46e7393aa38
Signed-off-by: Michael Chapman <michapma@redhat.com>
|
|
- mock-detached will add or remove firewall rules to block
traffic that would pull resources from the internet durning a deploy
These firewall rule may need to be added to, just starting with
http and https traffic figuring that would block the majority of cases.
- making updates to util help message according to:
https://en.wikipedia.org/wiki/Usage_message
Change-Id: I3c90999f977dd8f49c48399d312ed128b37bea6d
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
|
|
Change-Id: Ibed808350163379fcfa5178c78fabe2f47e491fc
Signed-off-by: Dan Radez <dradez@redhat.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>
|
|
|
|
|
|
|
|
JIRA: APEX-196
Change-Id: I21f63e69ecc4d5b979ed4780c6e92e3ad272b8d7
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-152
Change-Id: Id64a42531711c53ad453cd176aab2a9773a71811
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-194
opnfv-tht-pr: 38
Change-Id: I039320496fb2c5ed6e8dd87aafb1fece1fc9717d
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
If the remote file is a binary or other junk, we don't want to
print it to the console, so just state it's not a match for now.
Add puppet logging hack to help debug CI
Change-Id: Ia4717ee0cf7a2fc01299d0819c49218487ffdf15
Signed-off-by: Michael Chapman <michapma@redhat.com>
|
|
|
|
opnfv-tht-pr: 37
JIRA: APEX-158
Change-Id: I079d22e8ee7798bddf7f2f1b6cc3f1b49f1d5773
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
opnfv-tht-pr: 35
Change-Id: I17fd58c3e3a8862e36e45c9c50e0119ca4a88f89
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
Change-Id: I37dd541d3ad413b76d94cbc89ab1b2c8e1a723f1
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
|
|
trying to reduce the monolith deploy.sh to smaller parts
Change-Id: Ie2d2d74de5b8cacbb1c57d3d397bede0b659c0af
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
trying to reduce the monolith deploy.sh to smaller parts
Change-Id: Ie7068473e4ddd8eeca28ebd03de57781222ad761
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
trying to reduce the monolith deploy.sh to smaller parts
Change-Id: Iceeda2be0539563163bceaacbb54c6cc2d07b87b
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Tested against Apex Brahmaputra as I have had many issues getting a Colorado environment up and running.
Moved Ansible playbooks and scripts from ci/smoke_tests/ to tests/smoke_tests/
Rebase to master...
Change-Id: I09273de659c76d32ccfb74a548dabf7f84c65d6d
Signed-off-by: spisarski <s.pisarski@cablelabs.com>
|
|
trying to reduce the monolith deploy.sh to smaller parts
Change-Id: Ia92c055021073dc72f46a970cd03206ddd8df8da
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
trying to reduce the monolith deploy.sh to smaller parts
Change-Id: Ic40a7327d95a290d83f9c0b18ad87a280b0da3c4
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
trying to reduce the monolith deploy.sh to smaller parts
Change-Id: Ic788748969819637171a51d10b87b018fe286ae1
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Change-Id: I88514fe95121ecc7e6e4cbb41f529404c815bf06
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
|
|
Trying to split the monolith deploy.sh
Change-Id: Ib145e01696384b1b27e8a79263647235e7d68e2a
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
After dpdk finishes install, br-phy needs to be brought up and ovs-agent
needs to be restarted. This cannot happen in tripleO because
os-collect-config will try to ping from dpdk interfaces to the
controller to validate network connectivity. This doesn't work with
dpdk, so we leave br-phy down until end of deployment.
JIRA: APEX-119
Change-Id: I3d36d02b773fcbb3c5527b85fd00a2fa1b3cc25d
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
Changes include:
- Copies root pub key to overcloud nodes
- Introduces overcloud util command to login control/computes
- Minor fixes to undercloud util command
JIRA: APEX-192
Change-Id: I903fda4b1d232fc623137490630ac905ebb781d7
Signed-off-by: Tim Rozet <trozet@redhat.com>
|