From Fedora Project Wiki

(Created page with "{{QA/Test_Case |description=Launch Fedora CoreOS in [https://cloud.ibm.com/login IBM Cloud] [https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started VPC Gen2]. |setup= # Cre...")
 
m
 
(One intermediate revision by one other user not shown)
Line 3: Line 3:
  
 
|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.ibm.com/login IBM] account.
 
# Create a [https://cloud.ibm.com/login IBM] account.
 
# If you dont have an ignition file, produce it following [https://docs.fedoraproject.org/en-US/fedora-coreos/producing-ign/ these steps]
 
# If you dont have an ignition file, produce it following [https://docs.fedoraproject.org/en-US/fedora-coreos/producing-ign/ these steps]
Line 18: Line 19:
 
# The linked documentation is clear, all steps are understandable, and nothing important is missing from it.
 
# The linked documentation is clear, all steps are understandable, and nothing important is missing from it.
  
 
+
}}
 
[[Category:CoreOS Test Cases]]
 
[[Category:CoreOS Test Cases]]

Latest revision as of 14:21, 22 April 2021

Description

Launch Fedora CoreOS in IBM Cloud VPC Gen2.

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.

  1. Create a IBM account.
  2. If you dont have an ignition file, produce it following these steps
  3. Pre-configured VPC,SSH keys,networks,permissions,etc
    • ibmcloud CLI tool separtely installed

How to test

  1. Follow the Creating an Image documentation to create the latest image in the STREAM='next'.
  2. Follow the Launching Instances documentation to launch a VM from the image created above.
  3. 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

  1. The system launches in IBM cloud 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.