summaryrefslogtreecommitdiffstats
path: root/apex
AgeCommit message (Collapse)AuthorFilesLines
2018-12-22Always update OVS to 2.9.2Tim Rozet2-18/+15
Right now RDO defaults to an old version of OVS. In Apex for non-sfc scenarios we were pulling a prebuilt RPM of OVS 2.9.0 that included a group tables fix needed for ODL. For SFC, we now just build OVS along with the kernel module from native OVS because NSH support exists upstream in that version. We can move to always doing this operation for all OVS based scenarios, which will bump our OVS and ensure the package we build at runtime will work with our kernel. Change-Id: If38d0b858878f1af66990d987612a8f8f6fa2718 Signed-off-by: Tim Rozet <trozet@redhat.com> (cherry picked from commit 4f988328adf5dd8735bbf0a9420528cd343cfcd3)
2018-12-21Disable NFS when all-in-one deploymentTim Rozet1-4/+14
No point in using NFS when we only have one node. Change-Id: Ic80f75913bf31c2e4a875146731d9c0d3483ae1b Signed-off-by: Tim Rozet <trozet@redhat.com> (cherry picked from commit 56a2abfb7a1b23e1716beb16702d130226e4778d)
2018-12-19Attempting to fix NFS issuesTim Rozet2-8/+38
Issues still persist where sometimes instances fail to start due to a failure with os.utime to read the file path. This could be some bad race condition between qemu/nova while copying images on the NFS. This patch adds more ports to open in firewall, and changes initial directory owner to nfsnobody. Also, includes a patch to fix an apparent race condition when nova sends a remote call to the privsep helper daemon to modify the time of the base file owned by qemu: https://review.openstack.org/#/c/625741/ Includes another fix for patching container images where the docker image was not being detected correctly because the full gerrit project name including 'openstack/' prefix was being used to search tripleo docker images. Additionally, there were more bugs around patching openstack python containers where the patch was not being applied correctly. JIRA: APEX-654 Change-Id: I1d011035486298d5906038922e69d478c383c3f7 Signed-off-by: Tim Rozet <trozet@redhat.com> (cherry picked from commit e1d286e89e04577bda2569a5909dfe8182d953ba)
2018-12-14Fix NFS issues with NovaTim Rozet2-7/+12
There are problems with Nova launching instantces due to permissions with nova being able to read/write certain directories on the NFS. The permissions are right on the NFS and the folders the NFS mounts to, but there still seems to be issues. The cause may be using a directory under /root as the NFS mount. This patch moves the NFS mounts to be individual folders under /. The patch also restart nova_compute docker container as NFS problems still persist unless this is done. JIRA: APEX-654 Change-Id: I25eee98c1a6516dfa44c686c2e614f6dc7000d98 Signed-off-by: Tim Rozet <trozet@redhat.com> (cherry picked from commit 32b3b5dd6290ae5c33edee2860a3edd9f3044d43)
2018-12-10Fix broken Gambia reposTim Rozet3-0/+18
The undercloud disk image repos look to be stale. This patch updates the repos at deploy time to ensure the latest repos are always used. Similar to what was done in: https://gerrit.opnfv.org/gerrit/#/c/64493/ JIRA: APEX-656 Change-Id: I4eb2d0a8486b47a583434a9b83e1cc9d7274d9ad Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-12-08Merge "Fix using ODL versions other than oxygen" into stable/gambiaTim Rozet3-4/+7
2018-12-08Fix using ODL versions other than oxygenTim Rozet3-4/+7
Fixes a bug where oxygen was always being used even if a different ODL version was specified in the deploy settings. Also updates the valid ODL versions with fluorine and neon. JIRA: APEX-648 Change-Id: Ie49c28d1757cd7e57802d67e48904ce04864feaf Signed-off-by: Tim Rozet <trozet@redhat.com> (cherry picked from commit 46bf00b967844dc712dfe409e55fc5fe18fa119f)
2018-12-08Enable CSIT deployments to use NFS backendTim Rozet1-0/+19
In order to support HA as well as live migration a shared storage backend needs to be used. This patch preps the overcloud image to start with an NFS server sharing out of /root/nfs. If csit environment file is used then NFS parameters will be passed to the deployment, configuring Nova and Glance to use NFS hosted by controller0. JIRA: APEX-654 Change-Id: I049d84bfd454013fc7ba5048939ee17100197624 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-12-07Upgrade OVS in undercloudTim Rozet2-6/+15
The OVS in the frozen undercloud disk image for Gambia is no longer working (perhaps due to kernel upgrade or package changes during deployment). This patch builds OVS the same way as is done for the SFC scenario in the undercloud disk image. JIRA: APEX-655 Change-Id: I6fa3e009a25806e299c7be88d6d3ee8db4c2648b Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-11-06Fix Undercloud URL pathTim Rozet2-1/+7
Modify the URL path for undercloud disk image to opnfv artifacts. The undercloud image was removed from upstream TripleO, so we need to use the latest known good version for Gambia release, stored in OPNFV artifacts. In the future we will remove downloading undercloud image and just use the overcloud image for undercloud. Change-Id: I17a3bbaf67d55de05c195712d7fee6e89676bc16 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-10-31Change OPNFV Artifacts URLTim Rozet1-1/+1
This change allows downloading of files larger than 20GB. Change-Id: I881ea35316e67980d4144e46bfbd41501e80f497 Signed-off-by: Tim Rozet <trozet@redhat.com> (cherry picked from commit 498356c9efb765a5714845ce8303dc8a264eb300)
2018-10-17Fixes undercloud accidentally using wrong images/containersTim Rozet2-3/+4
Our undercloud initial install was failing with queens because the --use-heat arg does not work the same way as master/rocky. Therefore the undercloud install would fail, and then try to reinstall on the next ansible task. This one would succeed, via container installation because we were using the wrong undercloud/overcloud disk images. Change-Id: Ifb829aeeec991ba6dbe582fda3e9ee6b9bc733df Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-09-28Migrates deploy settings for GambiaTim Rozet1-1/+1
With branching to gambia we need to move the settings back to their proper names and remove OpenStack branch as Queens is the default for Gambia. Change-Id: Ia6101289629d89fa349f6554436ccd7c0f8b3c0c Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-09-28Enable OVN scenariosTim Rozet4-3/+32
As of Queens only HA OVN deployments are supported. Change-Id: I184c5a096fec9cbc3cf2ec06218700138ea3ed57 Signed-off-by: Tim Rozet <trozet@redhat.com> (cherry picked from commit ee58a24647df8eec2418735b038e5035bdffe10d)
2018-09-06Updates Calipso deploy settingsTim Rozet3-0/+24
Change-Id: Ibfbd08dc2fa5fca95668fd0590707cfebd92099f Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-08-23Adds deployment via snapshotTim Rozet14-89/+1202
New arguments are added to allow snapshot deployment: --snapshot, --snap-cache The previous tripleo-quickstart code has been removed/replaced with the snapshot option. Snapshot deployments are supported on CentOS and Fedora, and snapshot artifacts use a similar caching system as the standard deployment. Snapshots are produced daily by Apex, and include latest as well as n-1 OpenStack versions. The os-odl-nofeature scenario is used for the snapshots. Additionally multiple topology verions of Snapshots are available. The Snapshot pulled at deploy time depends on the deploy-settings and number of virtual-computes used at deploy time. Since there is only one network used with snapshot deployments (admin), there is no reason to pass in network settings for snapshot deployments. That argument is now optional. Previously we required even in Standard virtual deployments that the network settings be provided. However that is also unnecessary, as we can default to the virtual network settings. Includes minor fix to the tox.ini to allow specifying test cases to run (useful for developers writing tests). Default behavior of tox is unchanged. JIRA: APEX-548 Change-Id: I1e08c4e54eac5aae99921f61ab7f69693ed12b47 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-08-23Recover fix to install custom OVSRicardo Noriega3-20/+47
Need this fix to make VLAN tenant networks to work. Change-Id: Ie2dea9f0145c576e1b36280e6340ed2cc0460179 Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
2018-08-22Merge "Enable SFC scenarios for Gambia"Tim Rozet6-26/+77
2018-08-22Enable SFC scenarios for GambiaRicardo Noriega6-26/+77
- This patch will install OVS 2.9.2 including its kernel module which allows native NSH headers. - Fix Custom OVS due to bug: https://bugzilla.redhat.com/show_bug.cgi?id=1544892 - Tacker is disable for the time being, tacker-conductor needs to be enabled. JIRA: APEX-630 Change-Id: Ia410309fd7053602ce78eae919839d0f57c9742a Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
2018-08-20Fixes unit test failuresTim Rozet1-0/+4
Adds mocking some file opens introduced by: https://gerrit.opnfv.org/gerrit/#/c/60991/ Change-Id: I013b9c96a7c3f678c6e227f98cd58f9547d79ecb Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-08-20Merge "Add Nova migration params to upstream env file"Tim Rozet1-0/+4
2018-08-20Add Nova migration params to upstream env fileRicardo Noriega1-0/+4
JIRA: APEX-635 Change-Id: I488dd5d9b114aba5f4bb4591a0cdd8c19b692ce9 Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
2018-08-17Fix ipv6 deployment failuresFeng Pan3-10/+8
- fix ipv6 enable command on bridge interfaces - fix external subnet creation command - enable NAT when admin is ipv4 - fix network settings file for ipv6 for br-ex interface type Change-Id: Ibd2dbe1d0c8e8df72ad1b0b3713a19f8bbc56eef Signed-off-by: Feng Pan <fpan@redhat.com>
2018-08-15Modify common patches schema to per branchTim Rozet4-10/+40
The common patch design doesn't really work across branches very well. This patch makes it so the common patches are specified in the same file, but on a per branch basis. Making it easier to manage common patches per branch. Also, includes a fix and adds test coverage to the prep_image method where we were referencing 'undercloud_admin_ip' before assignment in a case where we were not using ODL and had patches to overcloud. Change-Id: I7672947afd826fdc0042361a0139e22d6d5dd864 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-08-14Allow common patches fileTim Rozet9-5/+162
This patch adds allowing for common patches that should be applied to every scenario to be included. It by default pulls in a file in the deploy directory 'common-patches.yaml', but can optionally be overridden. This patch also includes a patch upstream to fix OSCLI not working anymore due to breakage with the Cinder version in the overcloudrc. Change-Id: I97b9efb937deff07e085b9ef75b9799fb65bfc57 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-08-10Allow all in one deploymentsTim Rozet6-35/+110
This patch adds the ability to deploy all in one single nodes (Control + Compute). To enable this functionality do the following for each deployment type: - Baremetal: do not tag any nodes as compute in the inventory file - Virtual: use argument '--virtual-computes 0' JIRA: APEX-548 Change-Id: I22525c9eb21d331129c819449316c26a6fcf522d Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-08-08Bump deploy timeoutTim Rozet2-2/+2
We are seeing queens baremetal deployments are all failing in step 5 due to timeout. Not sure why the sudden increase in deployment time, but we can try increasing the deploy timeout to see if it fixes it. Also includes a revert for a commit that broke OOO master: https://bugs.launchpad.net/tripleo/+bug/1785872 Change-Id: I0bcfd5b3ca49b176f901c13b8b432fa29c899188 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-08-02Enable BGPVPN for master deploymentsRicardo Noriega5-24/+87
- Injection of Quagga tarball via overcloud builder. - Extraction and installation of all related packages. - It uses SDNVPN artifact repository to download Quagga tarball, so there is only one source to test. - Modifies bgpvpn scenario files to use OS master branch, ODL master branch and containers. JIRA: APEX-627 Change-Id: Icdbc2853d9531048e23fd6d5e444bd68208d18fc Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
2018-07-27Merge "Increasing loop device size for baremetal deployments"Tim Rozet2-1/+6
2018-07-26Increasing loop device size for baremetal deploymentsRicardo Noriega2-1/+6
Change-Id: Ib3779733ac27183def6a59f3404cfbe9a3e9a211 Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
2018-07-26Update OVS in overcloudTim Rozet2-9/+26
This bug fix is not present in the RDO versions of OVS: https://bugzilla.redhat.com/show_bug.cgi?id=1544892 The impact of this is that traffic sent through a patch port (like from br-int to br-ex) will not be sent correctly with OF groups (which ODL uses). This would cause tenant vlan traffic not to work in our case. Change-Id: Ia477b174118dcd2d7fb24189c2d093218eb97053 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-07-26Merge "Remove obsolete Ceph tags"Tim Rozet4-19/+2
2018-07-26Remove obsolete Ceph tagsRicardo Noriega4-19/+2
This patch removes the logic to use an specific tag for Ceph containers. We will use whatever docker image TripleO upstream uses. For aarch64, an ansible task will replace the tag to pull the proper container image. This patch also refactors the preparation of the local registry. In Queens, there is no need to execute twice the overcloud container image prepare command. JIRA: APEX-622 Change-Id: I947d931609e58505675bb460a59d08c1d10d1d0b Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
2018-07-20Fixes for snapshotsTim Rozet2-1/+4
With deploying snapshots with a new ODL, we currently bring down the docker container and bring up the tar.gz distro of ODL on the Overcloud host itself (not rebuilding/using container). Therefore we need java installed so that ODL can run on the host. In the future this may change, but it works well and keeps things simple for now. Additionally, there was a change upstream to make the opendaylight container docker restart policy "unless-stopped" which means it will no longer restart automatically when docker is stopped/started. Therefore on first snapshot bring up (without the previously mentioned ODL reinstallation) the container does not start, and snapshot deployment fails. This patch includes a change to the restart policy to always restart it. Change-Id: Icc712ba147e578a28e371313154ae3190676f0dc Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-07-18Add tenant vlan supportFeng Pan3-52/+192
Introduces tenant vlan support through configuration of network settings file. JIRA: APEX-272 Change-Id: Ie8e20a92ca4ebb9e0de4c53b5e03856d19ff660c Signed-off-by: Feng Pan <fpan@redhat.com>
2018-07-18Add param for ODL password into overcloudrcTim Rozet1-2/+2
Recent changes upstream have removed the default 'admin' ODL password and now password is randomly generated: https://review.openstack.org/#/c/578505/ So in OPNFV we now store the password in overcloudrc as SDN_CONTROLLER_PASSWORD variable. Also includes minor fixes to unittests. Change-Id: Iabe7e4f902442c80af99ba1603a3927cf13d0393 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-07-17Update queens ODL to include OF table fixTim Rozet2-2/+2
Also includes minor fix to patching where stable was not being removed from the short hand branch name correctly. Includes fix where path was changed in queens for env files: https://review.openstack.org/#/c/567810/ Change-Id: Ia3a6769be70ea97c9bec9d5539c9ab0373fed30a Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-07-16Merge "Add support for kubernetes deployment"Tim Rozet8-12/+185
2018-07-12Merge "Removes OC condition in dhcp-all-interfaces"Tim Rozet1-0/+5
2018-07-06Add support for kubernetes deploymentZenghui Shi8-12/+185
This patch adds capability to deploy kubernetes cluster instead of openstack. Kubernetes will be deployed using kubespray and is run after TripleO bookstraps overcloud nodes. JIRA: APEX-574 Change-Id: If9c171620c933a052b719e7112a50e22bbab667f Signed-off-by: Feng Pan <fpan@redhat.com> Signed-off-by: Zenghui Shi <zshi@redhat.com>
2018-06-25Deprecates the use of '--upstream' argumentTim Rozet4-87/+68
We only support the use of upstream deployments from Gambia onwards. Therefore deprecating the parameter and forcing upstream to always be used. Change-Id: I7926a65a2c32bca2272855ba45fdb6005f67616f Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-06-25Ignore error if network already undefinedTim Rozet1-1/+7
In clean we destroy a network, then undefine it. When running snapshot deploy it uses manual virsh bash commands to create the networks and other virsh resources. This leaves an admin network which our clean eventually tries to delete. However when the libvirt api network destroy command is used it is somehow undefining the newtork at the same time. Therefore just catch that possible scenario and ignore the failure as the network has already been removed. Change-Id: Id1d861fbe2a338f0828e78721c09f110030d3a4a Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-06-19Merge "Fixes Ceph PG calculation"Feng Pan3-13/+13
2018-06-18Fixes Ceph PG calculationTim Rozet3-13/+13
Baremetal deployments were failing because the ceph PG size was exceeding the max allowed. Virtual was still working because we lower the number of pools and pg/osd. This patch changes the values to a number which should work for both virtual and baremetal. Also includes a fix which adds the controllers back as OSDs and a few other cleanup issues. JIRA: APEX-614 JIRA: APEX-569 Change-Id: I2ad65727ecdcaa0454eb53d25e32b7f1a53cd3a4 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-06-18Fetch mistral logs from undercloudTim Rozet1-1/+4
/var/lib/mistral path contains logs for when ansible is invoked by TripleO for Ceph configuration as well as config download. This patch now archives and fetches that directory. Logs in previous releases like Queens store the Ceph logs in /var/log/mistral. Change-Id: I50c43e55efaa5dbcf8b7fb00b0e11cd3288fdd05 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-06-14Fixes deployment failure with allNodesConfigTim Rozet5-44/+208
This pulls in upstream patch to revert a bad commit that causes the "Unknown Property controller_ips". Also includes a fix for being able to detect if patches that are merged upstream are also promoted into TripleO images or container images. This happens by comparing the time the patch was submitted to the time when the TripleO Image or Docker Image was last updated. JIRA: APEX-610 JIRA: APEX-612 Change-Id: I1c2ab7fb4425b407acd7b6d9ebab914ed3a24478 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-31Merge "Configure NAT with baremetal when necessary"Feng Pan2-1/+112
2018-05-30Merge "Updates configs for ODL CSIT deployments"Feng Pan1-1/+1
2018-05-30Configure NAT with baremetal when necessaryTim Rozet2-1/+112
We currently only enable NAT on undercloud for virtual deployments. However, there could be a case where a baremetal deployment also needs NAT as it is not using an interface on the overcloud nodes with external access. Therefore this patch changes the behavior to configure NAT when the gateway of either the external or admin (when external is disabled) network matches an IP assigned to the undercloud. JIRA: APEX-605 Change-Id: I9c79af371913e6e5f0d39b433f68205bc7e106c5 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-30Updates configs for ODL CSIT deploymentsTim Rozet1-1/+1
For ODL CSIT we want to deploy with: - Minimum services per role - 2 Compute nodes, 1 controller - Single network enabled Change-Id: If611c4c1ff68629670ef15904930124b5786a569 Signed-off-by: Tim Rozet <trozet@redhat.com>