From 1e949c15518a9f0d5f9b459b82a55d085859ceb8 Mon Sep 17 00:00:00 2001 From: Languages add-on Date: Feb 20 2024 17:13:50 +0000 Subject: Added translation using Weblate (Czech) Co-authored-by: Languages add-on --- diff --git a/po/cs/master/pages/provisioning-vmware.po b/po/cs/master/pages/provisioning-vmware.po new file mode 100644 index 0000000..cceb8e1 --- /dev/null +++ b/po/cs/master/pages/provisioning-vmware.po @@ -0,0 +1,610 @@ +# SOME DESCRIPTIVE TITLE +# Copyright (C) YEAR Free Software Foundation, Inc. +# This file is distributed under the same license as the PACKAGE package. +# Languages add-on , 2024. +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2024-02-01 22:24+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"Language: cs\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. type: Title = +#: ./pages/provisioning-vmware.adoc:1 +#, no-wrap +msgid "Provisioning Fedora CoreOS on VMware" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:4 +msgid "" +"This guide shows how to provision new Fedora CoreOS (FCOS) nodes on the " +"VMware hypervisor." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:7 +msgid "" +"Fedora CoreOS supports VMware ESXi ≥ 7.0, VMware Workstation ≥ 16, and " +"VMware Fusion ≥ 12. It may be possible to " +"xref:provisioning-vmware.adoc#_modifying_ovf_metadata[modify the metadata of " +"the OVF] to run in older VMware products, but compatibility and " +"supportability cannot be guaranteed." +msgstr "" + +#. type: Title == +#: ./pages/provisioning-vmware.adoc:8 +#, no-wrap +msgid "Prerequisites" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:11 +msgid "" +"Before provisioning an FCOS machine, you must have an Ignition configuration " +"file containing your customizations. If you do not have one, see " +"xref:producing-ign.adoc[Producing an Ignition File]." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:13 +msgid "" +"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." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:16 +msgid "" +"You also need to have access to a working VMware infrastructure, supporting " +"VMs with at least hardware version 13. The examples below use the " +"https://github.com/vmware/govmomi/blob/v0.29.0/govc/README.md[govc] " +"command-line tool for remote vSphere provisioning and the " +"https://code.vmware.com/web/tool/4.4.0/ovf[ovftool] for local Workstation or " +"Fusion provisioning." +msgstr "" + +#. type: Title === +#: ./pages/provisioning-vmware.adoc:17 +#, no-wrap +msgid "Downloading the OVA" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:21 +msgid "" +"Fedora CoreOS is designed to be updated automatically, with different " +"schedules per stream. Once you have picked the relevant stream, you can " +"download the latest OVA:" +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:26 +#, no-wrap +msgid "" +"STREAM=\"stable\"\n" +"coreos-installer download -s \"${STREAM}\" -p vmware -f ova\n" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:29 +msgid "" +"Alternatively, OVA images can be manually downloaded from the " +"https://fedoraproject.org/coreos/download/?stream=stable#baremetal[download " +"page]." +msgstr "" + +#. type: Title === +#: ./pages/provisioning-vmware.adoc:30 +#, no-wrap +msgid "Encoding Ignition configuration" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:33 +msgid "" +"For the `vmware` provider, Ignition requires two \"guestinfo\" fields to be " +"present when the VM is first booted:" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:35 +msgid "" +"`guestinfo.ignition.config.data.encoding`: the encoding of the Ignition " +"configuration." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:36 +msgid "" +"`guestinfo.ignition.config.data`: the content of the Ignition configuration, " +"encoded according to the format above." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:38 +msgid "" +"For maximum compatibility, it is recommended to use `base64` encoding and to " +"prepare the Ignition configuration as such:" +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:43 +#, no-wrap +msgid "" +"CONFIG_ENCODING='base64'\n" +"CONFIG_ENCODED=$(cat example.ign | base64 -w0 -)\n" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:46 +msgid "" +"An alternative to plain `base64` encoding is `gzip+base64` as described in " +"the https://coreos.github.io/ignition/supported-platforms/[Ignition " +"supported platforms]. This is especially useful when submitting the Ignition " +"config via `govc` as an _inline_ argument. In that case the encoded config " +"is limited to slightly under 128 KiB on Linux, 256 KiB on macOS, and 32 KiB " +"on Windows (8 KiB if using `cmd.exe` or PowerShell). If your config is " +"larger than that limit, you may be able to submit it inline after " +"compressing it with `gzip`." +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:51 +#, no-wrap +msgid "" +"CONFIG_ENCODING='gzip+base64'\n" +"CONFIG_ENCODED=$(cat example.ign | gzip -9 | base64 -w0 -)\n" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:54 +msgid "" +"If your generated Ignition configuration is still too large, you will " +"encounter an `Argument list too long` error or similar. The solution to that " +"problem depends on whether you are working with vSphere or " +"Workstation/Fusion." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:56 +msgid "" +"For vSphere the solution is simple because instead of inlining the " +"configuration file within your shell, `govc` allows you to specify a path to " +"a local file instead with the " +"https://github.com/vmware/govmomi/blob/main/govc/USAGE.md#vmchange[`vm.change`]-command " +"and will handle reading and writing it internally, circumventing any shell " +"limitations." +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:62 +#, no-wrap +msgid "" +"CONFIG_ENCODING=\"gzip+base64\"\n" +"CONFIG_FILE=\"example.ign\"\n" +"CONFIG_FILE_ENCODED=\"${CONFIG_FILE}.gzip.b64\"\n" +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:64 +#, no-wrap +msgid "gzip -9c \"${CONFIG_FILE}\" | base64 -w0 - > \"${CONFIG_FILE_ENCODED}\"\n" +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:67 +#, no-wrap +msgid "" +"govc vm.change -vm \"${VM_NAME}\" -e " +"\"guestinfo.ignition.config.data.encoding=${CONFIG_ENCODING}\"\n" +"govc vm.change -vm \"${VM_NAME}\" -f " +"\"guestinfo.ignition.config.data=${CONFIG_FILE_ENCODED}\" # using `-f` with " +"a file path instead of `-e`\n" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:70 +msgid "" +"Using `gzip` for this solution is optional and primarily used for consistent " +"examples." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:72 +msgid "" +"In the case of Workstation/Fusion, or as a last resort in general, there is " +"the option to use a configuration file. Instead of setting an environment " +"variable containing your Ignition configuration, create an `ovftool` " +"compatible configuration file in the directory you are invoking from like " +"so:" +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:76 +#, no-wrap +msgid "" +"printf \"extraConfig:guestinfo.ignition.config.data=$(cat example.ign | " +"base64 -w0 -)\\n\" > ovftool.cfg\n" +msgstr "" + +#. type: Title == +#: ./pages/provisioning-vmware.adoc:78 +#, no-wrap +msgid "Booting a new VM on Workstation or Fusion" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:81 +msgid "" +"This section shows how to use Workstation and Fusion facilities to configure " +"and run VMs from the command-line. Some steps can potentially be performed " +"via the graphical UI too." +msgstr "" + +#. type: Title === +#: ./pages/provisioning-vmware.adoc:82 +#, no-wrap +msgid "Importing the OVA" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:85 +msgid "" +"The downloaded OVA has to be imported into the Workstation or Fusion library " +"locally. At the same time the Ignition has to be provided for it to be " +"applied to the VM." +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:98 +#, no-wrap +msgid "" +"VM_NAME='fcos-node01'\n" +"FCOS_OVA='./ova-templates/fedora-coreos-31.20200210.3.0-vmware.x86_64.ova'\n" +"LIBRARY=\"$HOME/Virtual Machines.localized\"\n" +"ovftool \\\n" +" --powerOffTarget \\\n" +" --name=\"${VM_NAME}\" \\\n" +" --allowExtraConfig \\\n" +" " +"--extraConfig:guestinfo.ignition.config.data.encoding=\"${CONFIG_ENCODING}\" " +"\\\n" +" --extraConfig:guestinfo.ignition.config.data=\"${CONFIG_ENCODED}\" \\\n" +" \"${FCOS_OVA}\" \"${LIBRARY}\"\n" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:101 +msgid "" +"Afterwards you can refresh the list of VMs in the Workstation or Fusion UI " +"and the new `fcos-node01` VM should appear ready for booting. Its hardware " +"configuration can be further customized at this point, and then powered-up." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:103 ./pages/provisioning-vmware.adoc:138 +msgid "" +"If you set up an xref:authentication.adoc[SSH key] for the default `core` " +"user, you can SSH into the VM and explore the OS:" +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:107 ./pages/provisioning-vmware.adoc:142 +#, no-wrap +msgid "ssh core@\n" +msgstr "" + +#. type: Title == +#: ./pages/provisioning-vmware.adoc:109 +#, no-wrap +msgid "Booting a new VM on vSphere" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:112 +msgid "" +"This section shows how to use vSphere facilities to configure and run VMs " +"from the command-line. Similar steps can be performed via the graphical UI " +"too." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:114 +msgid "" +"While the examples below use `govc session.login` to authenticate, you can " +"also use environment variables to provide credentials. Check the " +"https://github.com/vmware/govmomi/tree/main/govc#usage[official " +"documentation] for details." +msgstr "" + +#. type: Title === +#: ./pages/provisioning-vmware.adoc:115 +#, no-wrap +msgid "Setting up a new VM" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:118 +msgid "" +"You can now deploy a new VM, starting from the OVA and the encoded Ignition " +"configuration:" +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:127 +#, no-wrap +msgid "" +"FCOS_OVA='./ova-templates/fedora-coreos-31.20200210.3.0-vmware.x86_64.ova'\n" +"VM_NAME='fcos-node01'\n" +"govc session.login -u 'user:password@host'\n" +"govc import.ova -name ${VM_NAME} ${FCOS_OVA}\n" +"govc vm.change -vm \"${VM_NAME}\" -e " +"\"guestinfo.ignition.config.data.encoding=${CONFIG_ENCODING}\"\n" +"govc vm.change -vm \"${VM_NAME}\" -e " +"\"guestinfo.ignition.config.data=${CONFIG_ENCODED}\"\n" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:130 +msgid "" +"A new `fcos-node01` VM is now available for booting. Its hardware " +"configuration can be further customized at this point, and then powered-up:" +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:135 +#, no-wrap +msgid "" +"govc vm.info -e \"${VM_NAME}\"\n" +"govc vm.power -on \"${VM_NAME}\"\n" +msgstr "" + +#. type: Title === +#: ./pages/provisioning-vmware.adoc:144 +#, no-wrap +msgid "Using the OVA from the vSphere library" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:147 +msgid "" +"In case you want to spawn multiple, different VMs based on the same base " +"image you can import it into the vSphere library for easy reuse:" +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:156 +#, no-wrap +msgid "" +"FCOS_OVA='./ova-templates/fedora-coreos-31.20200210.3.0-vmware.x86_64.ova'\n" +"LIBRARY='fcos-images'\n" +"TEMPLATE_NAME='fcos-31.20200210.3.0'\n" +"govc session.login -u 'user:password@host'\n" +"govc library.create \"${LIBRARY}\"\n" +"govc library.import -n \"${TEMPLATE_NAME}\" \"${LIBRARY}\" \"${FCOS_OVA}\"\n" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:159 +msgid "" +"Creating a new instance can now be done using the `govc library.deploy` " +"command:" +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:166 +#, no-wrap +msgid "" +"VM_NAME='fcos-node01'\n" +"govc library.deploy \"${LIBRARY}/${TEMPLATE_NAME}\" \"${VM_NAME}\"\n" +"govc vm.change -vm \"${VM_NAME}\" -e " +"\"guestinfo.ignition.config.data.encoding=${CONFIG_ENCODING}\"\n" +"govc vm.change -vm \"${VM_NAME}\" -e " +"\"guestinfo.ignition.config.data=${CONFIG_ENCODED}\"\n" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:169 +msgid "" +"Note: If the vCenter has multiple datacenters and datastores, you must " +"specify them explicitly:" +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:175 +#, no-wrap +msgid "" +"# Get resource pool using `$ govc find / -type ResourcePool`\n" +"RESOURCE_POOL=\"/Datacenter6.5/host/Cluster6.5/Resources\"\n" +"DATASTORE=\"datastore-129\"\n" +"govc library.deploy -pool=${RESOURCE_POOL} -ds=${DATASTORE} " +"\"${LIBRARY}/${TEMPLATE_NAME}\" \"${VM_NAME}\"\n" +msgstr "" + +#. type: Title === +#: ./pages/provisioning-vmware.adoc:177 +#, no-wrap +msgid "First-boot networking and Ignition" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:181 +msgid "" +"Ignition supports referencing remote content in configuration and fetching " +"it at provisioning time. For this reason, on first-boot FCOS instances try " +"to perform network autoconfiguration via DHCP." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:184 +msgid "" +"If your VMware setup employs static network configuration instead, you can " +"override this automatic DHCP setup with your own custom configuration. " +"Custom networking command-line `ip=` parameter can be configured via " +"guestinfo properties as shown below, before booting a VM for the first time." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:186 +msgid "" +"The provisioning flow follows the usual steps, plus an additional " +"`guestinfo.afterburn.initrd.network-kargs` entry." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:188 +msgid "" +"if you are using a provisioning method other than `govc`, make sure that the " +"guestinfo attribute is provisioned in the VM's Advanced Configuration " +"Parameters (also known as `ExtraConfig`). Some management tools may default " +"to a vApp Property instead, which does not work in this scenario." +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:194 +#, no-wrap +msgid "" +"VM_NAME='fcos-node02'\n" +"IFACE='ens192'\n" +"IPCFG=\"ip=192.0.2.42::192.0.2.1:255.255.255.0:${VM_NAME}:${IFACE}:off\"\n" +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:201 +#, no-wrap +msgid "" +"govc library.deploy \"${LIBRARY}/${TEMPLATE_NAME}\" \"${VM_NAME}\"\n" +"govc vm.change -vm \"${VM_NAME}\" -e " +"\"guestinfo.ignition.config.data.encoding=${CONFIG_ENCODING}\"\n" +"govc vm.change -vm \"${VM_NAME}\" -e " +"\"guestinfo.ignition.config.data=${CONFIG_ENCODED}\"\n" +"govc vm.change -vm \"${VM_NAME}\" -e " +"\"guestinfo.afterburn.initrd.network-kargs=${IPCFG}\"\n" +"govc vm.info -e \"${VM_NAME}\"\n" +"govc vm.power -on \"${VM_NAME}\"\n" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:204 +msgid "" +"The full syntax of the `ip=` parameter is documented in " +"https://www.man7.org/linux/man-pages/man7/dracut.cmdline.7.html[Dracut " +"manpages]." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:206 +msgid "" +"For further information on first-boot networking, see " +"https://coreos.github.io/afterburn/usage/initrd-network-cmdline/[Afterburn " +"documentation]." +msgstr "" + +#. type: Title == +#: ./pages/provisioning-vmware.adoc:207 +#, no-wrap +msgid "Troubleshooting First-boot Problems" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:210 +msgid "" +"You may encounter problems with your Ignition configuration that require " +"access to the system log which appears during first-boot. To make a copy of " +"the system log you can attach a serial device to the VM before " +"booting. vSphere as well as Workstation and Fusion allow this and will save " +"the output to a file of your choice." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:212 +msgid "" +"To attach a serial device simply modify the hardware settings of the powered " +"off VM and add a `Serial Port`. Select the destination and name of the file " +"to be created. Afterwards power on the VM. When encountering an error, check " +"the file you initially specified - it should contain a copy of the system " +"log." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:214 +msgid "" +"The serial device can also be added to the VM via `govc` as described in the " +"https://github.com/vmware/govmomi/blob/master/govc/USAGE.md#deviceserialconnect[official " +"usage documentation]:" +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:218 +#, no-wrap +msgid "VM_NAME='fcos-node01'\n" +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:221 +#, no-wrap +msgid "" +"govc device.serial.add -vm \"${VM_NAME}\"\n" +"govc device.serial.connect -vm \"${VM_NAME}\" \"[datastore] " +"${VM_NAME}/console.log\"\n" +msgstr "" + +#. type: Title == +#: ./pages/provisioning-vmware.adoc:223 +#, no-wrap +msgid "Modifying OVF metadata" +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:228 +msgid "" +"While we provide these instructions for modifying the OVF metadata, we " +"cannot guarantee that any modifications to the OVF metadata will result in a " +"usable guest VM." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:237 +msgid "" +"Fedora CoreOS is intended to run on https://lifecycle.vmware.com/[generally " +"supported] releases of VMware ESXi, VMware Workstation, and VMware " +"Fusion. Accordingly, the Fedora CoreOS VMware OVA image specifies a " +"https://kb.vmware.com/s/article/1003746[virtual hardware version] that may " +"not be compatible with older, unsupported VMware products. However, you can " +"modify the image's OVF metadata to specify an older virtual hardware " +"version." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:241 +msgid "" +"The VMware OVA is simply a tarball that contains the files `disk.vmdk` and " +"`coreos.ovf`. In order to edit the metadata used by FCOS as a guest VM, you " +"should untar the OVA artifact, edit the OVF file, then create a new OVA " +"file." +msgstr "" + +#. type: Plain text +#: ./pages/provisioning-vmware.adoc:244 +msgid "" +"The example commands below change the OVF hardware version from the " +"preconfigured value to hardware version `13`. (Note: the defaults in the OVF " +"are subject to change.)" +msgstr "" + +#. type: delimited block - +#: ./pages/provisioning-vmware.adoc:250 +#, no-wrap +msgid "" +"tar -xvf fedora-coreos-{stable-version}-vmware.x86_64.ova\n" +"sed -iE 's/vmx-[0-9]*/vmx-13/' coreos.ovf\n" +"tar -H posix -cvf fedora-coreos-{stable-version}-vmware-vmx-13.x86_64.ova " +"coreos.ovf disk.vmdk\n" +msgstr ""