The e2fsprogs package is mandatory if we want to create ext4
filesystem.
Story: 2007522
Task: 39312
Change-Id: I1f5fa1a15ec92ccb917670df8fc33abb83135ff9
Since more and more python libraries are removing support for
Python 2 in the latest versions, we need to force the version of
Python used to build the DIB Debian image to 3, at least until
DIB fully converts to Python 3.
Change-Id: I8e6f15635754ab917562d758c35a8c5f4629efdf
Adds ntpdate to the binary package list for the diskimage-builder
element, and added ntpclient to the tinycore package list and added
a small shim to wrap ntpclient as ntpdate is not a native tinycore
package.
For larger ramdisks, we attempt to use chrony, which superceeds the ntp
package as a combined time server and client.
Change-Id: If99f2df31af8e4d41ad7813d25f0d779abc23f7a
Needed-By: https://review.opendev.org/#/c/707911/
Using the virtualenv command will generate a virtualenv with the
default python exec for the entire system, that means that even
if DIB_PYTHON is python3, the virtualenv will use python2.
With this change we use the venv embedded command if the version
of Python is 3.x to generate a virtualenv with the correct
Python 3 version.
Change-Id: I8bec32c5e0dae2dee27615146f946a9649f23fd1
As found recently, pip with Python 3.6 and forward has some issues
installing tarballs that contain files with non-ascii characters
in their names.
This is due mainly to the fact that the default locale in the
system is set to C [1].
As a workaround, we run the installation of the packages in the
virtualenv forcing C.UTF-8 locale.
[1] https://github.com/pypa/pip/issues/7667
Change-Id: Idfb8b121a43a0bb74844fd63d5c2507d7b888b15
These systems use LIO via python-rtslib, and targetcli depends
on libX11 and other GUI packages. The target-restore package
(coming from python-rtslib) is enough to create the necessary
directories (e.g. /etc/target).
Change-Id: Ide0d23d3834c52edcbc569c05ce95ba78e1bf73d
For tinyIPA, migrate the generate_upper_constraints script in-tree.
For DIB, use a source repository with requirements to fetch
upper-constraints. As a nice side effect, it allows depending on
requirements patches in the CI.
Change-Id: I6be51b98adab641cfaa1613306cbdcc3b42de1c2
* Move remove-extra-packages to post-install since finalise.d
is running on the final image and the DIB documentation
recommends avoiding unnecessary actions there.
* Remove a few packages that used to be removed only for Fedora;
do not try to remove those that aren't on the cloud image.
* Do all uninstallations in pre-install phase, so that it doesn't try
to remove dependencies of already installed packages.
* Exclude more locale files from the image.
* Exclude the content of /var/log.
Change-Id: Idb7819b1d783f4f5f390cc7621019d3be2fa576f
This reduces the size of the image slightly. We don't need latest
versions since we update pip in our venv anyway.
Change-Id: I7729b8c286c641a7b70a775ffe73f9f1c9dbff2d
We don't (and shouldn't) copy /tmp to the final image.
Also fix the service file permissions - it is not executable.
Change-Id: I75e09662a63768627f8123a7fe7f5d9ca2d942c5
Apparently, DIB is sensitive to file names, at least the package-install
feature. Let us make sure we use ironic-python-agent-ramdisk, not ironic-agent.
Change-Id: I929c0652c320734ff82dd257180c4b7bd156c478
This patch starts "ansiblization" of the image building script, while
also cleaning it up. More importantly, it adds check and gate jobs
that verify the same playbooks as used in the post job.
Also correct source-repository for ironic-python-agent to use the
project name, not the old element name.
Change-Id: I9a404b24f95e47c84b22d4739fcf2b5b800886f9
Copies "ironic-agent" element from DIB and addition
of a new bash script to build the image using DIB.
Change-Id: If392f793ed1b5d902b541fe89299648fae16e427
Task: 30072
Story: 2005114
