af81914ce7
The log extension is responsible for retrieving logs from the system, if journalctl is present the logs will come from it, otherwise we fallback to getting the logs from the /var/log directory + dmesg logs. In the coreos ramdisk, we need to bind mount /run/log in the container so the IPA service can have access to the journal. For the tinyIPA ramdisk, the logs from IPA are now being redirected to /var/logs/ironic-python-agent.log instead of only going to the default stdout. Inspector now shares the same method of collecting logs, extending its capabilities for non-systemd systems. Partial-Bug: #1587143 Change-Id: Ie507e2e5c58cffa255bbfb2fa5ffb95cb98ed8c4 |
||
---|---|---|
.. | ||
build_files | ||
.gitignore | ||
Makefile | ||
README.rst | ||
build-iso.sh | ||
build-tinyipa.sh | ||
finalise-tinyipa.sh | ||
install-deps.sh |
README.rst
Tiny Core Ironic Python Agent
Build script requirements
For the main build script:
- wget
- pip
- unzip
- sudo
- awk
- mksquashfs
For building an ISO you'll also need:
- genisoimage
Instructions:
To create a new ramdisk, run:
make
or:
./build-tinyipa.sh && ./finalise-tinyipa.sh
This will create two new files once completed:
- tinyipa.vmlinuz
- tinyipa.gz
These are your two files to upload to glance for use with Ironic.
Building an ISO from a previous make run:
Once you've built tinyipa it is possible to pack it into an ISO if required. To create a bootable ISO, run:
make iso
or:
./build-iso.sh
This will create one new file once completed:
- tinyipa.iso
To build a fresh ramdisk and build an iso from it:
Run:
make all
To clean up the whole build environment run:
Run:
make clean
For cleaning up just the iso or just the ramdisk build:
make clean_iso
or:
make clean_tinyipa
Advanced options
If you want the build script to preinstall everything into the ramdisk, instead of loading some things at runtime (this results in a slightly bigger ramdisk), before running make or build-tinyipa.sh run:
export BUILD_AND_INSTALL_TINYIPA=true