From Fedora Project Wiki
m (some polish) |
(simpler expectations) |
||
| Line 10: | Line 10: | ||
|results= | |results= | ||
The following must be true to consider this a successful test run | The following must be true to consider this a successful test run: | ||
# Confirm that you can SSH successfully into the machine according to the instructions (and the contents of your Ignition file). | # Confirm that you can SSH successfully into the machine according to the instructions (and the contents of your Ignition file). | ||
# Verify the documentation | # Verify the linked documentation works without a hitch and all steps are understandable. | ||
# The virtual machine once destroyed, should deallocate all resources. | |||
# The virtual machine once destroyed, should deallocate all resources | |||
|optional=If you see some issues, investigate the logs in journal, make sure the services are running. | |optional=If you see some issues, investigate the logs in journal, make sure the services are running. | ||
# To be added | # To be added | ||
}} | }} | ||
Revision as of 20:59, 25 May 2020
Description
Install Fedora CoreOS in a libvirt. For the sake of the testing the freshly-oven-baked changes, we would be using the next image.
Setup
- Download and verify the latest FCOS next image for QEMU
How to test
- Prepare an Ignition file to configure your FCOS instance. Read Provisioning Philosophy
- Produce the ignition file.
- Follow Launching with QEMU or libvirt documentation to start up a virtual machine.
Expected Results
The following must be true to consider this a successful test run:
- Confirm that you can SSH successfully into the machine according to the instructions (and the contents of your Ignition file).
- Verify the linked documentation works without a hitch and all steps are understandable.
- The virtual machine once destroyed, should deallocate all resources.
Optional
If you see some issues, investigate the logs in journal, make sure the services are running.
- To be added