fedora-docs-l10n/fedora-coreos/master/pages/provisioning-vmware — Portuguese (Brazil) @ Fedora Weblate: STREAM="stable" coreos-installer download -s "${STREAM}" -p vmware -f ova

Translation

Source change

English type: delimited block -

Portuguese (Brazil)

Needs editing

Skip

	English	Portuguese (Brazil)	Actions
	Provisioning Fedora CoreOS on VMware	Provisionando Fedora CoreOS no VMware
	This guide shows how to provision new Fedora CoreOS (FCOS) nodes on the VMware hypervisor.	Este guia mostra como provisionar novos nós de Fedora CoreOS (FCOS) no hipervisor VMware.
	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.
	Prerequisites	Pré-requisitos
	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].	Antes de provisionar uma máquina FCOS, você deve ter um arquivo de configuração do Ignition contendo suas personalizações. Se você não tiver um, consulte xref:producing-ign.adoc[Produzindo um arquivo de Ignition].
	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.	Fedora CoreOS tem um usuário padrão `core` que pode ser usado para explorar o sistema operacional. Se você quiser usá-lo, finalize sua xref:authentication.adoc[configuração] fornecendo, por exemplo, uma chave SSH.
	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.	Você também precisa ter acesso a uma infraestrutura VMware funcional, com suporte para VMs com pelo menos a versão de hardware 13. Os exemplos abaixo usam a ferramenta de linha de comando https://github.com/vmware/govmomi/blob/v0.22.2/govc/README.md[govc] para provisionamento remoto por vSphere e a https://code.vmware.com/web/tool/4.4.0/ovf[ovftool] para provisionamento local de Workstation ou Fusion.
	Downloading the OVA	Baixando o OVA
	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:	O Fedora CoreOS é projetado para ser atualizado automaticamente, com horários diferentes por fluxo. Depois de escolher o fluxo relevante, você pode baixar o OVA mais recente:
	STREAM="stable" coreos-installer download -s "${STREAM}" -p vmware -f ova	STREAM="stable" mkdir ova-templates coreos-installer download -s "${STREAM}" -p vmware -f ova -C ./ova-templates/
	Alternatively, OVA images can be manually downloaded from the https://fedoraproject.org/coreos/download/?stream=stable#baremetal[download page].	Alternativamente, as imagens OVA podem ser baixadas manualmente da https://getfedora.org/coreos/download/[página de download].
	Encoding Ignition configuration	Codificando a configuração do Ignition
	For the `vmware` provider, Ignition requires two "guestinfo" fields to be present when the VM is first booted:	Para o provedor `vmware`, o Ignition requer que dois campos "guestinfo" estejam presentes quando a VM for inicializada pela primeira vez:
	`guestinfo.ignition.config.data.encoding`: the encoding of the Ignition configuration.	`guestinfo.ignition.config.data.encoding`: a codificação da configuração do Ignition.
	`guestinfo.ignition.config.data`: the content of the Ignition configuration, encoded according to the format above.	`guestinfo.ignition.config.data`: o conteúdo da configuração do Ignition, codificado de acordo com o formato acima.
	For maximum compatibility, it is recommended to use `base64` encoding and to prepare the Ignition configuration as such:	Para compatibilidade máxima, é recomendado usar a codificação `base64` e preparar a configuração do Ignition da seguinte forma:
	CONFIG_ENCODING='base64' CONFIG_ENCODED=$(cat example.ign \| base64 -w0 -)	CONFIG_B64=`cat example.ign \| base64 -w0 -`
	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`.
	CONFIG_ENCODING='gzip+base64' CONFIG_ENCODED=$(cat example.ign \| gzip -9 \| base64 -w0 -)	CONFIG_B64=`cat example.ign \| base64 -w0 -`
	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.
	For vSphere, instead of inlining the configuration file within your shell, `govc` allows you to specify a path to a local file 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.
	CONFIG_ENCODING="gzip+base64" CONFIG_FILE="example.ign" CONFIG_FILE_ENCODED="${CONFIG_FILE}.gzip.b64"
	gzip -9c "${CONFIG_FILE}" \| base64 -w0 - > "${CONFIG_FILE_ENCODED}"
	govc vm.change -vm "${VM_NAME}" -e "guestinfo.ignition.config.data.encoding=${CONFIG_ENCODING}" govc vm.change -vm "${VM_NAME}" -f "guestinfo.ignition.config.data=${CONFIG_FILE_ENCODED}" # using `-f` with a file path instead of `-e`	VM_NAME='fcos-node01' govc library.deploy "${LIBRARY}/${TEMPLATE_NAME}" "${VM_NAME}" govc vm.change -vm "${VM_NAME}" -e "guestinfo.ignition.config.data.encoding=base64" govc vm.change -vm "${VM_NAME}" -e "guestinfo.ignition.config.data=${CONFIG_B64}"
	Using `gzip` for this solution is optional and primarily used for consistent examples.

Loading…

None

Suggestion added

English

Portuguese (Brazil) 81 characters edited

a year ago

None

String updated in the repository

English

Portuguese (Brazil) 114 characters edited Current translation Needs editing

2 years ago

None

Source string changed

English 40 characters edited

2 years ago

Browse all string changes

Things to check

Suggestions

There is 1 suggestion for this string.

View

Mismatching line breaks

Number of new lines in translation does not match source

Reset

Glossary

English	Portuguese (Brazil)
stream	fluxo	fedora-docs-l10n/fedora-coreos

String information

Source string description

type: delimited block -

Flags

no-wrap, placeholders:r"`[\w.\/\-_=@&*:$●+~()\] ]*`"

Source string location

pages/provisioning-vmware.adoc:26

String age

2 years ago

Last updated

10 months ago

Source string age

2 years ago

Translation file

po/pt_BR/master/pages/provisioning-vmware.po, string 10