From Fedora Project Wiki
(This should be more or less complete for now) |
mNo edit summary |
||
| Line 23: | Line 23: | ||
}} | }} | ||
[[Category:CoreOS Test Cases]] | |||
Latest revision as of 15:44, 13 October 2021
Description
Launch Fedora CoreOS in some instance of OpenStack from the next image.
Community resources
At the time of writing, there might be opportunities for Fedora contributors/packagers to access to OpenStack cluster(s) that are provided to Fedora. Reach out to #fedora-cores IRC/Matrix channel
At the time of writing, there might be opportunities for Fedora contributors/packagers to access to OpenStack cluster(s) that are provided to Fedora. Reach out to #fedora-cores IRC/Matrix channel
Setup
NOTE: You are not required to run this test case. If you don't already have an access to OpenStack cluster skip this test.
How to test
- Download the qcow2 images using the coreos-installer "coreos-installer download --decompress --architecture x86_64 -s next -p openstack -f qcow2.xz" or manually from FCOS OpenStack next images. For all architectures that instance of OpenStack that you have access to supports.
- Follow Provisioning Fedora CoreOS on OpenStack documentation to import and provision OpenStack based FCOS node(s). Do not forget to make sure that the image is decompressed before upload.
- Use the provided instructions to assign floating ip address and ssh in to the newly provisioned node(s).
- If you did not provide a custom Ignition file and only provided a SSH key-pair, then the default username to use is
core.
- If you did not provide a custom Ignition file and only provided a SSH key-pair, then the default username to use is
- Don't forget to terminate your instances after you're done with testing(and potentially delete the imported images), so you don't take up unnecessarily resources on the OpenStack cluster.
Expected Results
- The system launches in OpenStack according to the instructions.
- You can connect through SSH.
- The linked documentation is clear, all steps are understandable, and nothing important is missing from it.
Optional
- Instead of providing just a SSH key-pair, familiarize yourself with FCOS provisioning philosophy and create an Ignition file (copying the simplest example is fine). Then run this test case again, this time using your custom Ignition file.