| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
[tool.setuptools.data-files] does not support recursive directory
installation. The old setup.cfg [files] worked because PBR's
FilesConfig.expand_globs() used os.walk() to expand docker/*, but
this hook is not triggered by the pbr.build PEP-517 backend.
Move docker/ into kolla/ and use [tool.setuptools.package-data]
instead. Update kolla_worker._get_images_dir() to check the kolla
package directory first so both editable and regular installs work.
Change-Id: I4fc452c03740ef22ebbb4e8d0d86c4f4783e2d09
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
The build-date label was rendered into a LABEL instruction on line
3 of every Dockerfile template, immediately after FROM.
Because Docker invalidates the cache for a changed instruction and
all subsequent layers, a date change caused a full rebuild of every
image on each new calendar day, even when nothing else had changed.
Fix this by removing build-date from the Dockerfile templates and
applying it as a --label argument at build time via image.labels.
Labels passed on the build command line are not part of the
Dockerfile cache key, so the date is still recorded in the image
metadata without affecting layer caching.
Change-Id: I8ef0d85bab1a999a4d09f7cbf0c088ca00fdcf77
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
RDO has staffing problems and has decided to only
support SLURP releases - let's drop reliance on that
repository.
Change-Id: I56f86a1c5262e3ee2bcbb52cae53c3b2655ed87f
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
ovn is running as root, and fluentd can't read it's log files,
so we need to precreate these.
Closes-Bug: #2115244
Change-Id: Icb0e47cf95a67cb4585c71f863e542bc59ff5009
|
|
This patch adds a way to patch files in a Docker
image built by Kolla. This is very useful for several
reasons, specifically:
- Custom modifications
- The stable branch of some library has a fix but no pip
package has been released
- Eliminates the need to package your own pip packages
- Eliminates the need to invent your own versioning to prevent
upstream versioning
- Eliminates the need to manage a pip server
- In other words, it eliminates the need to get a wheel into
the image and install it manually using any method not
previously mentioned
It is also highly desirable because, although Kolla can replace
the source for a service with a custom URL for a tarball or its
own Git repo, it cannot do this for dependencies pulled from pip.
I would also like to point out that this is a feature with its own
code path and works only if the user "inserts" a patch into the folder
patches/docker-image/something.patch and creates an analogous series
file for patch source code.
Simply said, this code will never interfere with the upstream build process
since this feature is not intended for use in upstream.
It is rather meant for downstream users who know what they are doing.
Now they just have an option to patch their images.
Everything works on all layers of the Docker image and stores a report
of applied patches which can then be seen in /etc.
This mechanism is similar as debian patch quilt.
Change-Id: I61d0790c5d4d070b7ea9e8c99c0a76ff5d22bf9d
|
|
We have one install_type only now so that infra stuff is not needed
anymore.
Change-Id: I60d50ba7699d46d001eaef365fb84b0ce8e9b262
|
|
Defaults to 'image_prefix' for now but shows which images gets their
names changed soon.
Change-Id: I0608e8f62f28d6667b4c8753c47553e4cbf75503
|
|
Change-Id: I9692dda817ef134d647247431565e1b58cf9da41
|
|
Using the ovn-ctl script to start the OVN ovsdb-server is the better
way. This script is used to start and stop all OVN systemd services.
This script takes care of creating the database from the schema,
updating the database from the schema when the schema version gets
updated.
The present scripts - start_nb_db_server.sh and start_sb_db_server.sh
doesn't take care of schema updates.
With this, we don't need extend_start.sh in ovn-nb-db-server/ovn-sb-db-server
to create the database from the schema.
This patch also deletes kolla_ovn_extend_start from the ovn-base image as it
is not required.
Closes-bug: 1850025
Change-Id: I31a372d801dace92950cd85b29b308431f78bbdb
|
|
OVN has been split out from openvswitch and it's code is here [1].
With the split we have changed the ovn runtime/data dirs to
/etc/ovn and /usr/share/ovn respectively.
If a user uses latest OVN (when used after the split from
openvswitch), then the extend_start.sh of ovn-nb-db-server and
ovn-sb-db-server will fail because the OVN schema files will be in different
location (new location is /usr/share/ovn/ovn-nb.ovschema and /usr/share/ovn/ovn-sb.ovschema)
The old location is - /usr/share/openvswitch/ovn-nb.ovschema and
/usr/share/openvswitch/ovn-sb.ovschema
This patch checks for the presence of the schema files in the old location before
accessing them.
For latest OVN, it is advisable to use the "ovn-ctl" script to start
and stop OVN ovsdb-servers. ovn-citl script takes care of creating the dbs
and updating the dbs if the schema is updated.
[1] - https://github.com/ovn-org/ovn
https://github.com/openvswitch/ovs/commit/f3e24610ea18eb873dc860f1710432e9aacd27fd
Change-Id: If2bab2fac5be28ae7e1cd02de13a2de94fe17bac
Closes-bug: 1849633
Signed-off-by: Numan Siddique <nusiddiq@redhat.com>
|
|
This change updates the docker files to use base_package_type instead
of doing specific distro checks for the rhel/deb generic cases. The
base_distro is still available and is used when a specific distro needs
a customization but if the differences are purely rpm vs deb, then the
base_package_type can be used.
Change-Id: I8d720bb185df65a0178061ccf20b1ab2265da2c5
|
|
This patch adds kolla images for
- ovn-northd
- ovn-controller
- ovsdb-server for Northbound DB
- ovsdb-server for Southbound DB
Change-Id: I97f82395cb14108bdff57543e4847a5ece17fe69
Implements: blueprint ovn-controller-neutron
Signed-off-by: Numan Siddique <nusiddiq@redhat.com>
|
