Zen

Source string Source string

169/10000 · 169

The string is read only.

English Actions
Provisioning Fedora CoreOS on Exoscale
This guide shows how to provision new Fedora CoreOS (FCOS) instances on https://exoscale.com[Exoscale] Cloud Hosting.
Prerequisites
Before provisioning an FCOS machine, it is recommended to have an Ignition configuration file containing your customizations. If you do not have one, see xref:producing-ign.adoc[Producing an Ignition File].
Fedora CoreOS has a default `core` user that can be used to explore the OS. If you want to use it, finalize its xref:authentication.adoc[configuration] by providing e.g. an SSH key.
If you do not want to use Ignition to get started, you can make use of the https://coreos.github.io/afterburn/platforms/[Afterburn support]..
You also need to have access to an Exoscale account. https://portal.exoscale.com/register[Register] if you don't have one.
Uploading an FCOS image as a custom Template
Exoscale offers official FCOS templates, but they are currently out of date. For now, we recommend creating your own template. Track progress on fixing this in https://github.com/coreos/fedora-coreos-tracker/issues/1166[#1166].
Exoscale provides https://community.exoscale.com/documentation/compute/custom-templates[Custom Templates] to be able to upload any cloud image. To create a Custom Template you first need to download and decompress the image.
Download and decompress the QCOW2 image with https://github.com/coreos/coreos-installer[coreos-installer]
STREAM="stable"
coreos-installer download -d -s $STREAM -p exoscale -f qcow2.xz
Alternatively, QCOW2 images can be downloaded from the https://fedoraproject.org/coreos/download/?stream=stable#cloud_images[download page] and manually decompressed.
Next you can https://community.exoscale.com/documentation/compute/custom-templates/#register-a-custom-template[Register a Custom Template]. This can be done from the https://portal.exoscale.com/compute/templates/add[Web Portal] or the https://community.exoscale.com/documentation/tools/exoscale-command-line-interface/[Exoscale CLI]. Either option requires the uncompressed image to be uploaded somewhere public and for the URL and an MD5 checksum to be provided during registration. One option is to use the object storage provided by Exoscale to host the image.
Upload to Object Storage and create Custom Template
# Set the version and calcuate the checksum
FCOS_VERSION='...'
FILE="fedora-coreos-${FCOS_VERSION}-exoscale.x86_64.qcow2"
CHECKSUM=$(md5sum "${FILE}" | cut -d " " -f 1)
# Upload to object storage
BUCKET='newbucket'
exo storage mb "sos://${BUCKET}"
exo storage upload --acl public-read "${FILE}" "sos://${BUCKET}/image-import/"
# Create the template using given URL and CHECKSUM
URL=$(exo storage show "sos://${BUCKET}/image-import/${FILE}" --output-template "{{.URL}}")
TEMPLATE="fedora-coreos-${FCOS_VERSION}"
exo compute instance-template register --boot-mode=uefi $TEMPLATE $URL $CHECKSUM
You can then view the template using `exo compute instance-template show --visibility=private $TEMPLATE`.
Launching a VM instance
You can provision a FCOS instance using the Exoscale https://portal.exoscale.com/compute/instances/add[Web Portal] or via the https://community.exoscale.com/documentation/tools/exoscale-command-line-interface/[Exoscale CLI].
You will need to use at least version https://github.com/exoscale/cli/releases/tag/v1.54.0[v1.54.0] of the Exoscale CLI.
Do not use the `--cloud-init-compress` argument to the CLI. It causes the Ignition config to be passed compressed to the instance and https://github.com/coreos/fedora-coreos-tracker/issues/1160[Ignition doesn't tolerate that].
Add your ssh-key
exo compute ssh-key register key-name /path/to/key
Launching a new instance with Exoscale CLI
NAME='worker'
TYPE='standard.medium'
DISK='10' # in GiB
SSHKEY='key-name'
TEMPLATE=$TEMPLATE # template name set above
exo compute instance create "${NAME}" \
--disk-size $DISK \
--ssh-key "${SSHKEY}" \
--template $TEMPLATE \
--template-visibility private \
--cloud-init "path/to/ignition-file.ign"
If just SSH access is desired and no further customization is required, you don't need to pass any Ignition file and can omit the `--cloud-init` argument.
You can find out the instance's assigned IP by running `exo compute instance show "${NAME}"`
You now should be able to SSH into the instance using the associated IP address.
Example connecting

Loading…

User avatar None

String added in the repository
# Set the version and calcuate the checksum
FCOS_VERSION='...'
FILE="fedora-coreos-${FCOS_VERSION}-exoscale.x86_64.qcow2"
CHECKSUM=$(md5sum "${FILE}" | cut -d " " -f 1)
# Set the version and calcuate the checksum
FCOS_VERSION='...'
FILE="fedora-coreos-${FCOS_VERSION}-exoscale.x86_64.qcow2"
CHECKSUM=$(md5sum "${FILE}" | cut -d " " -f 1)
2 weeks ago
Browse all string changes

Things to check

Ellipsis

The string uses three dots (...) instead of an ellipsis character (…)

Reset

Glossary

English English
No related strings found in the glossary.

18693935 String information

Source string description
type: delimited block -
Flags
no-wrap, placeholders:r"`[\w.\/\-_=@&*:$●+~()\] ]*`", read-only
Source string location
./pages/provisioning-exoscale.adoc:39
String age
2 weeks ago
Last updated
2 weeks ago
Source string age
2 weeks ago
Translation file
pot/master/pages/provisioning-exoscale.pot, string 16