From Fedora Project Wiki

(Initial page based on the AWS test case)
 
(Update all to Openstack relevant info.)
Line 4: Line 4:
|description=Launch Fedora CoreOS in some instance of [https://www.openstack.org/ OpenStack] from the <code>next</code> image.
|description=Launch Fedora CoreOS in some instance of [https://www.openstack.org/ OpenStack] from the <code>next</code> image.


{{admon/tip|Free of charge|At the time of writing this test case, FCOS could be launched free of charge in AWS, making it possible to run this test case without paying for it.}}
{{admon/tip|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}}


|setup=
|setup=
'''NOTE:''' You are not required to run this test case. If you don't already have an account or don't want to create one then skip this test.
'''NOTE:''' You are not required to run this test case. If you don't already have an access to OpenStack cluster skip this test.
# Create an [https://aws.amazon.com Amazon AWS] account.


|actions=
|actions=
# Pick the closest region in the list of [https://getfedora.org/coreos/download?tab=cloud_launchable&stream=next FCOS AWS '''next''' images] and copy the AMI image ID.
# Download the qcow2 images from [https://getfedora.org/coreos/download?tab=cloud_operators&stream=next&arch=x86_64 FCOS OpenStack '''next''' images] for all architectures that instance of OpenStack that you have access to supports.
# Follow [https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-aws/ Launching on Amazon Web Services (AWS)] documentation to launch the image in AWS using this AMI image ID.
# Follow [https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-openstack/ Provisioning Fedora CoreOS on OpenStack] documentation to import and provision OpenStack based FCOS node(s).
# Use the provided instructions in AWS to SSH to the new FCOS instance using `ssh username@ipaddress` (replace ''username'' and ''ipaddress'' with actual values).
# 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 `core`.
# Don't forget to terminate your instance after you're done with testing, so that you don't end up paying for an eternal-running machine.
# 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.


|results=
|results=

Revision as of 12:22, 5 October 2021

Warning.png
This in currently work in progress test scenario.


Description

Launch Fedora CoreOS in some instance of OpenStack from the next image.

Idea.png
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

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

  1. Download the qcow2 images from FCOS OpenStack next images for all architectures that instance of OpenStack that you have access to supports.
  2. Follow Provisioning Fedora CoreOS on OpenStack documentation to import and provision OpenStack based FCOS node(s).
  3. 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.
  4. 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

  1. The system launches in OpenStack according to the instructions.
  2. You can connect through SSH.
  3. The linked documentation is clear, all steps are understandable, and nothing important is missing from it.

Optional

  1. 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.