Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
When adding upstream packages to undercloud image, there is a conflict
between a new dependency python2-docker and already installed
python-docker. This patch removes the latter before trying to install
upstream packages.
Also, updates nic templates based on:
https://review.openstack.org/#/c/604943/
Change-Id: Ia7db0a3b37652d066bbe80478689f4d1ebaea560
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-652
Change-Id: I4651707265c1184026cf5ed06805997615d2db95
Signed-off-by: Daniel Balsiger <Daniel.Balsiger@swisscom.com>
|
|
|
|
|
|
Commit 1817e62 introduced a side effect for aarch64.
The undercloud and overcloud images are not the same for aarch64
due to differences in the partition table and they are not provided by RH
or tripleo. Helper scripts to build them are in this repository.
For aarch64 undercloud.qcow2,overcloud.tar and ironic-python-agent.tar
Are required.
Change-Id: Ia79de801e3cb33bbcc78cdc714cb1745c1b57d6b
Signed-off-by: Charalampos Kominos <Charalampos.Kominos@enea.com>
|
|
Change-Id: I0f4e26397267bff13d32a6ba765d3a09024d5656
Signed-off-by: Charalampos Kominos <Charalampos.Kominos@enea.com>
|
|
|
|
|
|
RDO builds packages which are aarch64 compatible but some configuration
is needed to succesfully deploy.
This change:
- Prepares the aarch64 docker.io repo as the source for Kolla Containers
- Configures VM sizing for aarch64 undercloud.
- Configures VM sizing for aarch64 virtual deploy targets.
Vms need to be larger on aarch64 compared to x86 to avoid
starvation of resources. (MYSQL)
- Configures vda2 as the location of the Linux Kernel in aarch64 in
an UEFI system
- Configures the vNICs to be on the pci-bus instead of the virtio-mmio
bus.This will enalbe the Nics to come up in the same order as the
x86 ones, so the extra configuration in ansible is not needed
- Configures apex to use a stable version of the ceph:daemon container
- Configure apex for containerized undercloud in Rocky
- Add extra ansible.cfg file for aarch64 which increases waiting
times in ansible for aarch64
- Provide helper scripts for DIB to create aarch64 UEFI images
Known limitations:
- Selinux is interfering with DHCP requests in ironic and ssh
so it must be disabled before the deploy command is ran.
- The aarch64 containers are frozen for in this commit:
https://trunk.rdoproject.org/centos7-rocky/f3/18/f3180de6439333a2813119ad4b00ef897fcd596f_70883030
- The 600s timeout defined in :
https://bugs.launchpad.net/tripleo/+bug/1789680 is not enough for
aarch64. A value of 1200s is recommended
JIRA: APEX-619
Change-Id: Ia3f067821e12bba44939bbf8c0e4676f2da70239
Signed-off-by: Charalampos Kominos <Charalampos.Kominos@enea.com>
Signed-off-by: ting wu <ting.wu@enea.com>
|
|
When deploying rocky, python2-tripleo-repos fails to install because of
a bad yum cache even after updating the repo. This patch just clears the
yum cache after updating the repo.
Change-Id: I94a68611faf1c3ff89d57c3d877d3336574ce8bb
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
OOO team is removing the undercloud disk image as it is no longer needed
for containerized undercloud deployments. Instead, we can just use the
overcloud image as the undercloud image.
Additionally, OOO team has recommended we use current-tripleo instead of
current-tripleo-rdo. current-tripleo-rdo was previously thought to be
more stable with more promotion checks, but now it seems that it is
older and current-tripleo now has the same stability/checks.
This patch also bumps the undercloud RAM from 8GB to 10GB. With the new
containerized undercloud there is more RAM consumption during
deployment.
Change-Id: I9e6bb2260dbe9f8796ee54d20527c0aad96476ec
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Changes-Include:
- Remove references to Apex ISO and disk image RPMs
- Update supported scenarios
- Update using upstream documentation
Change-Id: If2b66d1d5a861bd1f90b0e8829de37d84e656619
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-644
The grep command used in the original code matches multiple nodes
when deploying 10+ compute nodes. This makes opnfv-util fail to
connect to those nodes. Proposed fix is to grep for "$node "
instead.
Change-Id: I952664f6f3cab3a98681684cd354513bb3c0ab12
Signed-off-by: Daniel Balsiger <Daniel.Balsiger@swisscom.com>
|
|
Branch was being passed with the 'stable' prefix which was breaking the
docker URL.
Change-Id: I802492d407bc18ec2b47212edfe4bb4fde13002a
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
The neutron_driver for opendaylight needs to be set to 'odl' instead of
'opendaylight'
Change-Id: Ib9345d8b9fc8be5b7a49ac961a2499220c1c1bd6
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
The API has changed to create/upload the docker container images to be
used for deployment. In the past the prepare commands would read the THT
environment files passed, to determine which docker images to render
into an environment file. The new behavior uses a new
"containers-prepare-parameter.yaml" format (included in this patch),
which Apex will now configure for deployment. By default docker images
will be rendered for all TripleO services identified in the
roles_data.yaml file. Therefore we must use several excludes patterns to
only pull the docker images needed for a default deployment.
JIRA: APEX-642
Change-Id: Iab00fcb874554bb98540dc9a4c3051e58ea68a3b
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Functest needs these values to be set in overcloudrc to know which ports
to query ODL on.
JIRA: APEX-621
Change-Id: I41e34efccedc26edd98c6dd3f45e553ea76db195
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
It looks like the docker_container ansible module will recreate the
container if it fails to restart it. This is undesired behavior so
moving to use shell to restart the containers.
Also, fixes mistral executor container not properly mounting the
ceph-ansible playbook. Additionally fixes an issue with ceph-ansible by
downgrading the package. Related rhbz:
https://bugzilla.redhat.com/show_bug.cgi?id=1644713
Change-Id: I3199b4af11a4170d19419f70cb53f7d74def273c
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
This change allows downloading of files larger than 20GB.
Change-Id: I881ea35316e67980d4144e46bfbd41501e80f497
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
File was missing during python package install.
Change-Id: Icd8c22d45cac807ba5e5995fa0efea690e615cde
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
The delorean path does not have images for rocky, however they do exist
under the rdo_trunk path. Comparing the images for queens between the 2
paths looks the same, so switching to this URL.
Change-Id: I5d762af69b984c0fed1c79b73f2b4d61341298fa
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
Master code only supports containerized undercloud now, so this
migration is needed.
- Containerized services in undercloud
We can still apply patches to THT and other non-docker services, but
we will need to add support for patching openstack services on
undercloud.
Change-Id: I1ca4c6108f144efef7b5889503af265ef0fff8b2
Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
This adds configuration for performing local documentation builds
with the following simple command:
tox -e docs
This patch is part of our documentation effor to Move away from submodules
https://docs.opnfv.org/en/latest/how-to-use-docs/local-build-transition.html
added index.rst so that docs build succsesfully
Change-Id: I2d28f03ad4d5c9c14de095dc544257af9d1e51d9
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
For now we need to retain the ability to deploy odl-queens for CSIT.
Change-Id: Idea550ff5e7aeb230aa93d3575de11e5e9656302
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
As of Queens only HA OVN deployments are supported.
Change-Id: I184c5a096fec9cbc3cf2ec06218700138ea3ed57
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I9e01f1164fc72915b92dfb1c0aad7414c484567e
Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
|
|
Change-Id: Ibfbd08dc2fa5fca95668fd0590707cfebd92099f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
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>
|
|
Need this fix to make VLAN tenant networks
to work.
Change-Id: Ie2dea9f0145c576e1b36280e6340ed2cc0460179
Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
|
|
|
|
- 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>
|
|
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>
|
|
|
|
JIRA: APEX-635
Change-Id: I488dd5d9b114aba5f4bb4591a0cdd8c19b692ce9
Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
|
|
- 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>
|
|
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>
|
|
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>
|
|
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>
|
|
Apex clean is failing when trying to clean vbmcs because the function
was changed in new virtualbmc version. Adding the working version to our
constraints.
JIRA: APEX-631
Change-Id: I62971183669e4a51e841d79892e78b10ea380a1e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
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>
|
|
This reverts commit b88eb3c7a1578cb251282c358fad6d87e7439868.
Change-Id: If5a2548e647de099229824761c6c575ca4f2e815
Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
|
|
Change-Id: Id5b932246020676e1e53438db689e32bc124939e
Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
|
|
- 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>
|
|
Nova Placement should have been on controller.
Change-Id: I9279e56b5cf786c1153af4b09b29e2b215c2f248
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
There is an issue with loss of external network connectivity that
prevents cloud init to instances working. This becomes a big problem
with snapshots where there is no external network connectivity. Cloud
init fails because each request takes over 30 seconds to get a response.
This is because in the background neutron metadata agent is proxying the
request to nova metadata agent with an HTTP GET using the FQDN. For
whatever reason, a DNS lookup happens even though the entry exists for
the FQDN in /etc/hosts and waits 30 seconds until timing out. After this
timeout, a 200 OK is sent and metadata works.
This patch modifies the config file for metadata to use nova metadata
server's internal IP rather than FQDN as there is no option in OOO to
use IPs instead of FQDN.
Change-Id: I6960181a227d0002c99aeae5112f59807dc41d7a
Signed-off-by: Tim Rozet <trozet@redhat.com>
|