aboutsummaryrefslogtreecommitdiff
path: root/kolla/image
AgeCommit message (Collapse)AuthorFilesLines
2019-11-29Enable repos only when neededMarcin Juszkiewicz1-0/+1
Disable external repositories by default and enable only when needed. Depends-on: https://review.opendev.org/696480 Implements: blueprint repos-off-by-default Change-Id: Icf2a8397a8349e0fe849d88d160409fd234480a9
2019-11-13Merge "Remove deprecated images"Zuul1-4/+0
2019-11-13Remove deprecated imagesRadosław Piliszek1-4/+0
Change-Id: I2fe57f7cd79724fa8a36bd702d75b013a68ecd1b
2019-11-12Disable Searchlight for CentOS 7/sourceMarcin Juszkiewicz1-0/+5
Searchlight is Python 3 while CentOS 7/source images are Python 2 Change-Id: I9d2e4f3630efad91b5cc94085ad1dd1f6680e017
2019-10-23Do not build rally image for Ubuntu binaryRadosław Piliszek1-0/+1
UCA does not provide rally and the Ubuntu rally depends on python2 packages which conflict with python3 packages. Change-Id: I36c1feaecf2e07e2d9fb8a7f42e899477eaabae4 Closes-bug: #1848295
2019-10-16handle push error properlyMarcin Juszkiewicz1-2/+9
If there was some error during pushing then Kolla was greeting with "all went fine" message anyway: INFO:kolla.common.utils.aodh-api:Trying to push the image ERROR:kolla.common.utils.aodh-api:Get http://10.101.16.1:5000/v2/: dial tcp 10.101.16.1:5000: connect: no route to host INFO:kolla.common.utils.aodh-api:Pushed successfully This patch changes that. Now if there is an error during push then proper exception is raised to PushTask and image is marked with PUSH_ERROR status. This way at the end of build it is easy to spot which images did not got pushed to registry: INFO:kolla.common.utils:=========================== INFO:kolla.common.utils:Images that failed to build INFO:kolla.common.utils:=========================== ERROR:kolla.common.utils:base Failed with status: push_error ERROR:kolla.common.utils:nova-api Failed with status: push_error ERROR:kolla.common.utils:nova-base Failed with status: push_error ERROR:kolla.common.utils:nova-compute Failed with status: push_error ERROR:kolla.common.utils:nova-compute-ironic Failed with status: push_error ERROR:kolla.common.utils:nova-conductor Failed with status: push_error Closes-Bug: #1848019 Change-Id: Id2ab97bf4c0dc3423268a0ea435b56f4a65f7196
2019-10-02Merge "debian: enable congress and zaqar images"Zuul1-2/+0
2019-10-01mistral-event-engine: enable for Debian/UbuntuMarcin Juszkiewicz1-2/+0
Depends-On: https://review.opendev.org/685901 Change-Id: I0c5e5cc895238094e30fac49dfc6e7bd880ca55e
2019-10-01debian: enable congress and zaqar imagesMarcin Juszkiewicz1-2/+0
Change-Id: I331d8ed68ab32d7c56e891cf2e71c4a8157a26de
2019-09-26added broken images to UNBUILDABLE_IMAGESMarcin Juszkiewicz1-1/+3
Change-Id: I52933c535023e8681bbde887364a188450c15663
2019-09-20Merge "Fix retries when pushing images"Zuul1-0/+3
2019-09-19Merge "ppc64le: add UNBUILDABLE_IMAGES entries"Zuul1-1/+35
2019-09-19Fix retries when pushing imagesMark Goddard1-0/+3
Currently the retry mechanism is broken for pushing because the image state gets set to an error state, and is never reset to 'built'. This prevents the PushTask from setting success to True. This change sets the image state to 'built' if the push succeeds, ensuring it overrides any previous failures. Change-Id: I93fc0e383da8fec6b3ca31f8094321c2a0c3af71 Closes-Bug: #1844697
2019-09-19Merge "build.py: fix pep8 warnings"Zuul1-6/+6
2019-09-19ppc64le: add UNBUILDABLE_IMAGES entriesMarcin Juszkiewicz1-1/+35
Change-Id: I6b8f52a1f2227ecb74e3ae59ef1e67d5b5ce1886
2019-09-18Merge "build: enable Octavia for Ubuntu/binary"Zuul1-1/+0
2019-09-18Remove support for OracleLinuxMark Goddard1-8/+1
We have agreed to remove support for Oracle Linux. http://lists.openstack.org/pipermail/openstack-discuss/2019-June/006896.html Change-Id: I961dfba1aeef2c509ecdaf376dfe6928926ffb39 Depends-On: https://review.opendev.org/682858
2019-09-18build: enable Octavia for Ubuntu/binaryMarcin Juszkiewicz1-1/+0
Change-Id: Icc68b404d8713a9fcf0026374378d1645fe30d52
2019-09-17build.py: fix pep8 warningsMarcin Juszkiewicz1-6/+6
Change-Id: Ifaeed6917636e2bcb5ea3bda32ae0393ebb08a4f
2019-09-12Drop Percona XtraBackup in favour of MariaDB BackupMarcin Juszkiewicz1-2/+0
XtraBackup started failing to install on Ubuntu and does not support MariaDB 10.3 version. Related-Bug: #1843043 Change-Id: I9cf62c8e03a02574d85e5349df1d23a51d4c99be
2019-08-31disable 'hacluster-pcs' on aarch64 due to lack of packageMarcin Juszkiewicz1-0/+1
Change-Id: I3000136fa883f510b24133907a66efd194b40266
2019-08-19debian: add some images to unbuildable listMarcin Juszkiewicz1-1/+6
We do not have package repositories for opendaylight, telegraf, xtrabackup images. bifrost tries to install 'mysql-server' package which is not present in Debian 'buster' monasca-grafana has some SSL related issues Change-Id: I795771569a3dcb9730063bd951c230806a08b3c0
2019-08-08Bump up pkg versions in kolla-toolboxMichal Nasiadka1-0/+2
Currently we use Ansible 2.2 in kolla_toolbox, while lowest supported version is 2.6 - bumping up to 2.8. * Use upper constrains in Dockerfile.j2, instead of pinning them in here - Ansible is pinned to 2.8.* * Add no_log=True in kolla_keystone_user * Add endpoint_type as a param in kolla_keystone_service - now AnsibleModule requires all options to be defined, otherwise it throws an UnsupportedParameter error * Add openstack_release variable in kolla/common/config.py which is used for fetching upper-constraints.txt for desired release Change-Id: I2cb0ea2fde1b408d48b39bf7a54b898e850d31aa
2019-07-22Merge "Change how build process treats unbuildable images"Zuul1-36/+91
2019-07-22Merge "Allow building images if parent was skipped"Zuul1-1/+3
2019-07-21Change how build process treats unbuildable imagesMarcin Juszkiewicz1-36/+91
We have a list of images which are unbuildable for distro/buildtype/arch combos. This patch renames it from SKIPPED_IMAGES to UNBUILDABLE_IMAGES because 'skipped' images is something else in our code. Now all unbuildable images are marked as such and so are their children. At the end of build there is information provided about skipped images (due to --skip-parents or --skip-existing options) and then information about not buildable images. Both list should only contain entries related to requested build. Change-Id: If9b521339f564e483cba03d52e7c4eba271821a5
2019-07-17add some more not buildable imagesMarcin Juszkiewicz1-10/+5
Cyborg-agent binaries are only provided as x86-64 rpm packages. CentOS/aarch64 does not have 'mongodb' in EPEL. Ubuntu/aarch64 lacks 'sensu' package. Change-Id: I0fd668018b37e1d64782fd32ff3846a688c4e915
2019-07-11Add Masakari containersKien Nguyen1-0/+1
Masakari provides Instances High Availability Service for OpenStack clouds by automatically recovering failed Instances. Change-Id: I279d6b43f8e4d4e30b39deb607823ceca272a4b8 Implements: blueprint masakari-support
2019-07-03Merge "build: add timestamps to start/end of build"Zuul1-2/+5
2019-06-28Add more entries into SKIPPED_IMAGESMarcin Juszkiewicz1-0/+35
Did build of all images for AArch64, looked at failures and here is a list of ones which never build due to lack of packages. There are some images which could get to the list but there are already patches for them in Gerrit. Also added three more entries for Debian due to missing packages. Change-Id: Ie259a38aad84bd8f5392f19791edfbd1f8ec4b1a
2019-06-26build: add timestamps to start/end of buildMarcin Juszkiewicz1-2/+5
During recent CI issues I got an idea that it would be nice to have information how much time building specific image took. On local systems we can do log and then check 'modified_time - creation_time' but not on CI jobs. Fresh image: INFO:kolla.common.utils.base:Building started at 2019-06-26 13:53:08.393544 INFO:kolla.common.utils.base:Ended at 2019-06-26 13:56:40.354761 (took 0:03:31.961225) Rebuild: INFO:kolla.common.utils.base:Building started at 2019-06-26 14:00:34.913194 INFO:kolla.common.utils.base:Built at 2019-06-26 14:00:38.988874 (took 0:00:04.075686) Failed images do not get second line due to logger.exception() being used. Change-Id: Id13545224fa0fbb729d46386a10505e0989fc3c6
2019-06-19Make SKIPPED_IMAGES more flexibleRadosław Piliszek1-80/+43
With introduction of new architectures, it seems reasonable to allow skipping of images based on their architecture. Additionally, the existing framework had unneccessary duplication. This commit makes the feature more flexible and cleaner. Existing skips have been programmatically rewritten. Change-Id: I34c002a0ee605ca121d9d923b256e4fe1ea3d9aa Signed-off-by: Radosław Piliszek <radoslaw.piliszek@gmail.com>
2019-06-18Merge "Remove crane image"Zuul1-5/+0
2019-06-07Remove crane imageMark Goddard1-5/+0
This image was deprecated in the Stein cycle. Change-Id: I249b78cd263c97c4a9223523c77f8c325f3e649a
2019-06-07Merge "Debian/Ubuntu: move to Python 3 for source images"Zuul1-0/+4
2019-06-06Debian/Ubuntu: move to Python 3 for source imagesMarcin Juszkiewicz1-0/+4
Commit 43b74ccc157c0b50138c3785ed91dab504895571 enabled use of Python 3 based packages but not switched to use Python 3. Some of images still contain Python 2. There are two reasons: - Ceph (ceph-common depends on Py2) - python3-ldappool on Ubuntu 18.04 In Ceph situation Py3 packages were added. For second one we can not do anything - Py2 dependency got dropped in Ubuntu 18.10 version. Removed neutron-server-plugin-networking-infoblox due to being not maintained. Once https://review.opendev.org/#/c/657578/ get merged someone may revert that part. Implements: blueprint debian-ubuntu-python3 Depends-on: Ie2a1077f7def0743f1403341985e2109aa490026 Change-Id: Ibfe0c2b8be98db56c61f74fb0247488ab3749ef4
2019-06-05Allow building images if parent was skippedJason1-1/+3
This fixes a bug where if an image had a parent that was skipped, it would never get built. Normally when a parent finishes building it triggers the build of its children. This process is kicked off by Kolla finding the grandparents that have no parents above them. However, sometimes parents should be skipped, and in this case they would never get scheduled, and so their children would never build, producing a strange error without much information. Fix is to allow building an image if its parent is explicitly marked as having been skipped. The use-case for this is when you want to iterate on building an image without going through the cost of re-running the parent builds. In particular, if your builds are using Git sources, which break Docker caches, the cost of parent builds is high and the feedback loop during development has a much higher latency. Allowing some way for images to be rebuilt in a targeted manner is helpful when in the development phase. Change-Id: I6b6897d20626825bcd235b9a85859644effbd222 Closes-Bug: #1810979
2019-06-05Remove tripleo-uiAlex Schultz1-12/+0
The tripleo-ui project has been removed from the upstream. Remove the references to the tripleo-ui containers. Change-Id: I353ecd3ed04c78fd21f0108c5e1355280d3f3bb9 Closes-Bug: #1831478
2019-05-20Add Qinling containersGaetan Trellu1-0/+4
Add Qinling Dockerfile , Qinling is an OpenStack project to provide "Function as a service". This project aims to provide a platform to support serverless functions. Change-Id: Idebf5c8756a0d0225adcce29b45a399120bb5eb6 Implements: blueprint qinling-support
2019-04-03Add config option use_dumb_init to add it to container imagesRabi Mishra1-0/+2
Usage of dumb-init can also be disabled from cli with `--nouse-dumb-init` when building images. Also moves ENTRYPOINT outside of dumb_init_installation block. Change-Id: Id32d54fc9913b83cf121ede5a5e265e0772062ae Related-Bug: #1821970
2019-03-27Add cyborg to kollaBai Yongjun1-0/+6
Because kolla not have cyborg so should add this. Implements: blueprint add-cyborg Change-Id: I497e67e3a754fccfd2ef5a82f13ccfaf890a6fcd
2019-03-21Merge "Introduce clean_package_cache"Zuul1-1/+4
2019-03-18Properly set debian_arch for ppc64el hardwareMichael Turek1-0/+2
On Red Hat distros, ppc64el is referred to as ppc64le. This patch simply sets debian_arch to ppc64el if the base arch comes up as ppc64le. Change-Id: Idb9b30f792db11bea9b7d96025bd20a03fabc78a
2019-03-17Introduce clean_package_cacheEmilien Macchi1-1/+4
Default to true (to maintain backward compatibility), this parameter will allow to disable the Package cache cleaning when building the Kolla images. In TripleO, we are investigating how we can accelerate the builds by not cleaning the Yum cache and this patch will help us to do so. Also included same for deb package_install method. Co-Authored-By: Jon Schlueter <jschluet@redhat.com> Change-Id: I0adc85302dfe0411d362c899f3e0d6a0019680d4
2019-03-12Add distro_package_manager configurationAlex Schultz1-0/+13
Add configuration to allow the switch between dnf/yum or provide an alternative package manager. Change-Id: I913769fcf5875a12b4561958cf7c90b74cd116ea
2019-03-12replace 'distro_python3' variable with 'distro_python_version'Marcin Juszkiewicz1-7/+8
RHEL7 derived distros use Python 2.7 RHEL8 uses Python 3.6 Ubuntu 18.04 uses Python 3.6, but we haven't enabled it yet. Debian:buster uses Python 3.7, but we haven't enabled it yet. We have several places in code where "/lib/pythonX.Y/site-packages" is used so we need to know value of X.Y rather than py2/py3 switch. How to check for Python 2: {% if distro_python_version == '2.7' %} Breaks: Iad6b70b433a0dd1b0f8ae6790fd280594517661a Change-Id: Ie24f109af19ae0438c21e0d43cb3cc947812b4ce
2019-02-28debian/ubuntu: make use of Python3 based packagesMarcin Juszkiewicz1-1/+0
Both Ubuntu Stein UCA and Debian 'buster' migrated their OpenStack packages to Python 3. Note that Debian 'buster' is not released yet and contains Rocky packages. Stein ones will be available later. Co-Authored-By: Lee Yarwood <lyarwood@redhat.com> Co-Authored-By: Eduardo Gonzalez <dabarren@gmail.com> Change-Id: I160f79cc57f54ec3eac857c5babd1a6e2656d228
2019-02-19debian/ubuntu: introduce 'debian_arch' variableMarcin Juszkiewicz1-0/+6
Many images have 'if x86_64 then amd64 elif aarch64 then arm64' check to comply with Debian like architecture names in several projects. This patch creates 'debian_arch' variable which can be used in all Docker files (similar to 'base_arch' one). All required images got converted to use it. Change-Id: I9c5e6f13d6c9b24fe323408512bd5aef290111ad
2019-01-31build: exit if there is no Docker connectionMarcin Juszkiewicz1-1/+3
When user starts Kolla on system without Docker daemon running huge traceback is generated and then exit. Issue is because KollaWorker raises exception but no one catches it (then only call to it is in run_build() which assumes everything is ok). Change-Id: I68ea3f48c75b51dbbab3accbc531d2f73428c48f
2019-01-30Allow running more commands dockerlessMartin André1-1/+4
The `--save-dependency`, `--list-images`, and `--list-dependencies` options to the kolla-build commands do not actually require docker daemon running. This commit stop kolla-build from complaining when it is called with one of the above options without docker daemon started. Change-Id: I966587236aca363316db8abbfc04763655b4b68f
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-06 02:17:25 +0000