Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
JIRA: APEX-257
Change-Id: I21913a6e41a2fd1565b1950345d15d0b5d47cb9c
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I5dea9d61c2fc0b9d5af1ff88823f4ec3cb92c8d5
Signed-off-by: Michael Chapman <woppin@gmail.com>
|
|
L3 Agent needs to use OVS driver for external interfaces and NSDriver
for Internal interfaces.
JIRA: APEX-252
opnfv-tht-pr: 73
Change-Id: Ic96e30421a1f1308c358a644e5602ca738091695
Signed-off-by: Tim Rozet <trozet@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>
|
|
Bug where IP was being detected on DPDK interface, which is attached to
br-phy and has no IP. IP parsing is only needed on FDIO deployments -
so moving that part into the fdio clause.
JIRA: APEX-119
opnfv-tht-pr: 72
Change-Id: I7540a97de399271eebae907f868a7ed044f3aefe
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
|
|
This is added to the entire overcloud, because it only adds driver code
and will not impact other scenarios. It will also allow for CI coverage
of this commit. This driver is needed for FDIO to be able to use
Neutron DHCP agent.
JIRA: APEX-249
opnfv-tht-pr: 70
Change-Id: Id2eb55b68dd97c79dcb9e2fd3061a252965e66ae
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
VPP nodes were being mounted into ODL with hostname rather than FQDN,
which is required for matching nova/neutron services FQDN.
JIRA: APEX-247
opnfv-tht-pr: 69
Change-Id: I83c9128e7644bcf294ced2f93b6f4e7f7a156866
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
colorado branch.
Use GS_PATHNAME to make url to retrieve ovsnfv artifacts release independent.
JIRA: APEX-242
JIRA: APEX-119
Change-Id: I1a5b99ac6c8e60b49e7437b3f35d2833e71e050e
Signed-off-by: Thomas F Herbert <therbert@redhat.com>
|
|
|
|
|
|
There were syntax errors with "auth_url" and an extra double quote.
Also added logging to make it more clear when datasources get created.
JIRA: APEX-245
Change-Id: I554fb8195116dd71f4b34b8ccf6e969d9b2e7224
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
Neutron agents have a different host name on reboot, causing duplicate
entries in the agent list. This is corrected by locking the host name
to be the fqdn.
opnfv-tht-pr: 68
JIRA: APEX-239
Change-Id: Ia2026e0515cd2fd42a4a18cbd1e26d2864f31b28
Signed-off-by: Michael Chapman <woppin@gmail.com>
|
|
Change-Id: Icfeb02f73b18aa6dbcca449b83d2c8c8bf0f6dab
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
Previous behavior was detecting the total number of nodes in the
inventory file and defining number of compute nodes as total nodes,
minus 1 or 3 control nodes (depending on HA flag). This patch changes
the behavior to look explicitly for number of compute/control
nodes in the inventory file.
JIRA: APEX-244
Change-Id: I0191bb88e7dc5bebb5f7bfed39661f8047dbd476
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-243
Change-Id: I1ed843c316b840aa9c0f85ef250fcecc59197188
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
Change-Id: I1002eb3d2a6e58621582dd61348ffa2745c77655
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
opnfv-tht-pr: 67
JIRA: APEX-133
Change-Id: I73aa66925773eab392f8da8fb750fc7cb1b4d3e5
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I177066f2bd7be77feaa5618d2f09c1aac26cc953
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>
|
|
|
|
Change-Id: Ice02b4eabffc49f47185978b5068676ef095a647
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
JIRA: APEX-133
opnfv-tht-pr: 66
Change-Id: I4e529fa83330d090fc2bb42283d98f02cf1454eb
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-133
Change-Id: I96b278996edc6897408111d31b9effe472fb0d10
Signed-off-by: Feng Pan <fpan@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>
|
|
JIRA: APEX-240
Change-Id: Icd69c76b624182042aea67fd23ecd33241325e26
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-236
Change-Id: If237340529f2b9898d91c420b004770e0f883ce0
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
|
|
|
|
|
|
Defaults for virtual deployments was not correct, there were three baremetal
nodes being created by default for a noha deployment.
JIRA: APEX-221
Change-Id: I8b13ffb620d8ebaed4308725edbc7e84279872dd
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
NetworkSettings Object is being rendered and passed to net env object
already. We can get the enabled network list from the network settings object
instead of passing it in as an arg. Basically just removing duplicate
arguments to the network env object.
Change-Id: I828c60878a0432cae2b37c08ae1896dce49071d0
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
- Update DPDK and ovs-dpdk rpm links
- Change curl to wget to get proper error return code when failure
occurs.
JIRA: APEX-119
Change-Id: Icdd8e11f1fff9e20695780215dee357b0aca45a5
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
opnfv-tht-pr: 65
Change-Id: I47b773129636c541bdb0e93e88e334587ac7c2a0
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
Change-Id: I2ac2910eaecab1fc4fb9634b6af9bc7f454ff77a
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
|
|
Feng has contributed greatly to Apex C release.
Achievements/Conbributions include:
- OVS DPDK Integration
- FDIO/VPP Integration
- Converting portions of Apex code base to Python
- Implementing IPv6 in Apex
Change-Id: Ied0130b37b1c4fc89c72ccba83328d45d1375ff0
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>
|
|
Change-Id: I8970be0bcbed501e43d6fb76af1278881274f69a
Signed-off-by: Sofia Wallin <sofia.wallin@ericsson.com>
|
|
DHCP Metadata network was not being enabled because I missed passing it
in overcloud.yaml to controller.yaml.
JIRA: APEX-236
opnfv-tht-pr: 64
Change-Id: Ibfd69f5fe5c6f5f2e0bd9c7e47ce1b35e9bd050e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
opnfv-tht-pr: 62
Change-Id: If08e779e49afa217870124d1dc0deccd086bfa91
Signed-off-by: Michael Chapman <michapma@redhat.com>
|
|
opnfv-tht-pr: 63
Change-Id: Ie91809d222cae34b81f541bdbc83b6d0fe561973
Signed-off-by: Tim Rozet <trozet@redhat.com>
|