From Fedora Project Wiki
(add info about the gcloud CLI) |
mNo edit summary |
||
(One intermediate revision by one other user not shown) | |||
Line 5: | Line 5: | ||
|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. | |||
# Create a [https://cloud.google.com/ GCP] account. | # Create a [https://cloud.google.com/ GCP] account. | ||
# Install the [https://cloud.google.com/sdk/gcloud gcloud CLI], unless you plan to use the web console. | # Install the [https://cloud.google.com/sdk/gcloud gcloud CLI], unless you plan to use the web console. |
Latest revision as of 14:01, 22 April 2021
Description
Launch Fedora CoreOS in Google Cloud Platform from the fedora-coreos-next
image family.
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.
- Create a GCP account.
- Install the gcloud CLI, unless you plan to use the web console.
- Note there is an option to run it from a container.
How to test
- Follow the Booting on GCP documentation to launch the latest image in the
fedora-coreos-next
image family. - Use the gcloud CLI or the web frontend to discover the IP address for the launched instance and then SSH into it using
ssh username@ipaddress
(replace username and ipaddress with actual values).- 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 instance after you're done with testing, so that you don't end up paying for an eternal-running machine.
Expected Results
- The system launches in GCP 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.
- Instead of launching the GCP instance from the command line, use GCP web console to launch it.