summaryrefslogtreecommitdiff
path: root/docs/podman.1.md
diff options
context:
space:
mode:
authorChris Evich <cevich@redhat.com>2018-11-07 09:35:18 -0500
committerChris Evich <cevich@redhat.com>2018-12-06 15:39:18 -0500
commitcb900798ce63d8655740f93e0d0b9cc0ebd8144f (patch)
tree4b1b58f330cdf03220332eba92bd3303c486526e /docs/podman.1.md
parent8d7fdc7d79e4de3e3ff5bb50e157d49a0bf8971e (diff)
downloadpodman-cb900798ce63d8655740f93e0d0b9cc0ebd8144f.tar.gz
podman-cb900798ce63d8655740f93e0d0b9cc0ebd8144f.tar.bz2
podman-cb900798ce63d8655740f93e0d0b9cc0ebd8144f.zip
Cirrus: Document and codify base-image production
A number of images required for future testing are not present in GCE. Importing them is a long proscribed process prone to errors and complications. Improve this situation by documenting, and encoding the majority of the steps required. Due to the required complexity, these are clearly identified as 'semi-automated'. This means a discerning eye is sometimes needed to address unforeseen problems (networking issues, format or packaging changes, etc). Nevertheless, having these steps in writing, will reduce current and future maintenance burden while supporting future testing needs of RHEL, Fedora and Fedora Atomic Host. Also: * Add necessary configuration, scripts, and Makefile updates needed to prepare RHEL, Fedora, & FAH cloud images for use in GCE. This is a complex, multi-step process where the cloud image is booted un a local user-mod qemu-kvm instance, where it can be modified. From there, it's converted into a specific format, and imported into GCE. Lastly, the imported raw disk data is made available as a GCE VM image. Note: As of this commit, the RHEL base-image builds (CentOS has native image), however neither RHEL or CentOS cache-images build correctly. * Left testing on FAH disabled, the GCE/Cirrus integration needs needs more work. Specifically, the python3-based google startup script service throws a permission-denied (as root) when trying to create a temp. directory. Did not investigate further, though manually running the startup script does allow the libpod tests to start running. * Enabled Fedora 29 image to execute tests and general use. * Utilize the standardized F28-based container image for gating of more the intensive unit and integration testing. Update documentation to reflect this as the standard platform for these checks. Rename tasks with shorter names and to better reflect their purpose. * Cirrus: Trim unnecessary env vars before testing since the vast majority are only required for orchestration purposes. Since most are defined within `.cirrus.yml`, it's a good place to store the list of undesirables. Since each of the cirrus-scripts runs in it's own shell, unsetting these near the end will have no consequence. Also trim down the number of calls to show_env_vars() Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'docs/podman.1.md')
0 files changed, 0 insertions, 0 deletions