fedora-docs-l10n/fedora-coreos/master/pages/provisioning-vmware — Portuguese (Brazil) @ Fedora Weblate: govc vm.info -e "${VM_NAME}" govc vm.power -on "${VM

Translation

English type: delimited block -

Portuguese (Brazil)

Needs editing

Skip

	English	Portuguese (Brazil)	Actions
	Booting a new VM on Workstation or Fusion	Inicializando uma nova VM no Workstation ou Fusion
	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.	Esta seção mostra como usar os recursos do Workstation e Fusion para configurar e executar VMs a partir da linha de comando. Algumas etapas podem, potencialmente, ser realizadas por meio da IU gráfica também.
	Importing the OVA	Importando o OVA
	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.	O OVA baixado deve ser importado para a estação de trabalho ou biblioteca Fusion localmente. Ao mesmo tempo, a Ignition deve ser fornecida para que seja aplicada à VM.
	VM_NAME='fcos-node01' FCOS_OVA='./ova-templates/fedora-coreos-31.20200210.3.0-vmware.x86_64.ova' LIBRARY="$HOME/Virtual Machines.localized" ovftool \ --powerOffTarget \ --name="${VM_NAME}" \ --allowExtraConfig \ --extraConfig:guestinfo.ignition.config.data.encoding="${CONFIG_ENCODING}" \ --extraConfig:guestinfo.ignition.config.data="${CONFIG_ENCODED}" \ "${FCOS_OVA}" "${LIBRARY}"	VM_NAME='fcos-node01' FCOS_OVA='./ova-templates/fedora-coreos-31.20200210.3.0-vmware.x86_64.ova' LIBRARY="$HOME/Virtual Machines.localized" ovftool \ --powerOffTarget \ --name="${VM_NAME}" \ --allowExtraConfig \ --extraConfig:guestinfo.ignition.config.data.encoding="base64" \ --extraConfig:guestinfo.ignition.config.data="${CONFIG_B64}" \ "${FCOS_OVA}" "${LIBRARY}"
	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.	Depois, você pode atualizar a lista de VMs na IU do Workstation ou Fusion e a nova VM `fcos-node01` deve aparecer pronta para inicialização. Sua configuração de hardware pode ser ainda mais personalizada neste ponto e, em seguida, ligada.
	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:	Se você configurar uma xref:authentication.adoc[chave SSH] para o usuário padrão `core`, poderá fazer um acesso via SSH para VM e explorar o sistema operacional:
	ssh core@<ip address>	ssh core@<endereço ip>
	Booting a new VM on vSphere	Inicializando uma nova VM no vSphere
	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.	Esta seção mostra como usar os recursos do vSphere para configurar e executar VMs a partir da linha de comando. Etapas semelhantes também podem ser realizadas por meio da IU gráfica.
	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.
	Setting up a new VM	Configurando uma nova VM
	You can now deploy a new VM, starting from the OVA and the encoded Ignition configuration:	Agora você pode implantar uma nova VM, começando com o modelo na biblioteca e a configuração codificada do Ignition:
	FCOS_OVA='./ova-templates/fedora-coreos-31.20200210.3.0-vmware.x86_64.ova' VM_NAME='fcos-node01' govc session.login -u 'user:password@host' govc import.ova -name ${VM_NAME} ${FCOS_OVA} govc vm.change -vm "${VM_NAME}" -e "guestinfo.ignition.config.data.encoding=${CONFIG_ENCODING}" govc vm.change -vm "${VM_NAME}" -e "guestinfo.ignition.config.data=${CONFIG_ENCODED}"	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}"
	A new `fcos-node01` VM is now available for booting. Its hardware configuration can be further customized at this point, and then powered-up:	Uma nova VM `fcos-node01` agora está disponível para inicialização. Sua configuração de hardware pode ser ainda mais personalizada neste ponto e, em seguida, ligada:
	govc vm.info -e "${VM_NAME}" govc vm.power -on "${VM_NAME}"	govc vm.info -e "${VM_NAME}" govc vm.power -on "${VM_NAME}"
	Using the OVA from the vSphere library
	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:
	FCOS_OVA='./ova-templates/fedora-coreos-31.20200210.3.0-vmware.x86_64.ova' LIBRARY='fcos-images' TEMPLATE_NAME='fcos-31.20200210.3.0' govc session.login -u 'user:password@host' govc library.create "${LIBRARY}" govc library.import -n "${TEMPLATE_NAME}" "${LIBRARY}" "${FCOS_OVA}"	FCOS_OVA='./ova-templates/fedora-coreos-31.20200210.3.0-vmware.x86_64.ova' LIBRARY='fcos-images' TEMPLATE_NAME='fcos-31.20200210.3.0' govc session.login -u 'user:password@host' govc library.create "${LIBRARY}" govc library.import -n "${TEMPLATE_NAME}" "${LIBRARY}" "${FCOS_OVA}"
	Creating a new instance can now be done using the `govc library.deploy` command:
	VM_NAME='fcos-node01' govc library.deploy "${LIBRARY}/${TEMPLATE_NAME}" "${VM_NAME}" govc vm.change -vm "${VM_NAME}" -e "guestinfo.ignition.config.data.encoding=${CONFIG_ENCODING}" govc vm.change -vm "${VM_NAME}" -e "guestinfo.ignition.config.data=${CONFIG_ENCODED}"	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}"
	Note: If the vCenter has multiple datacenters and datastores, you must specify them explicitly:
	# Get resource pool using `$ govc find / -type ResourcePool` RESOURCE_POOL="/Datacenter6.5/host/Cluster6.5/Resources" DATASTORE="datastore-129" govc library.deploy -pool=${RESOURCE_POOL} -ds=${DATASTORE} "${LIBRARY}/${TEMPLATE_NAME}" "${VM_NAME}"
	First-boot networking and Ignition	Rede da primeira inicialização e Ignition
	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.	O Ignition oferece suporte para referenciar conteúdo remoto na configuração e buscá-lo no momento do provisionamento. Por esse motivo, na primeira inicialização, as instâncias do FCOS tentam realizar a configuração automática da rede via DHCP.
	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.	Se sua configuração do VMware emprega configuração de rede estática, você pode substituir essa configuração DHCP automática com sua própria configuração personalizada. O parâmetro `ip=` de linha de comando de rede personalizado pode ser configurado por meio das propriedades guestinfo conforme mostrado abaixo, antes de inicializar uma VM pela primeira vez.
	The provisioning flow follows the usual steps, plus an additional `guestinfo.afterburn.initrd.network-kargs` entry.	O fluxo de provisionamento segue as etapas normais, além de uma entrada adicional `guestinfo.afterburn.initrd.network-kargs`.
	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.	se você estiver usando um método de provisionamento diferente de `govc`, certifique-se de que o atributo guestinfo seja provisionado nos parâmetros de configuração avançada da VM (também conhecido como `ExtraConfig`). Algumas ferramentas de gerenciamento podem usar como padrão uma propriedade vApp, o que não funciona neste cenário.
	VM_NAME='fcos-node02' IFACE='ens192' IPCFG="ip=192.0.2.42::192.0.2.1:255.255.255.0:${VM_NAME}:${IFACE}:off"	VM_NAME='fcos-node02' IFACE='ens192' IPCFG="ip=192.0.2.42::192.0.2.1:255.255.255.0:${VM_NAME}:${IFACE}:off"
	govc library.deploy "${LIBRARY}/${TEMPLATE_NAME}" "${VM_NAME}" govc vm.change -vm "${VM_NAME}" -e "guestinfo.ignition.config.data.encoding=${CONFIG_ENCODING}" govc vm.change -vm "${VM_NAME}" -e "guestinfo.ignition.config.data=${CONFIG_ENCODED}" govc vm.change -vm "${VM_NAME}" -e "guestinfo.afterburn.initrd.network-kargs=${IPCFG}" govc vm.info -e "${VM_NAME}" govc vm.power -on "${VM_NAME}"	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}" govc vm.change -vm "${VM_NAME}" -e "guestinfo.afterburn.initrd.network-kargs=${IPCFG}" govc vm.info -e "${VM_NAME}" govc vm.power -on "${VM_NAME}"
	The full syntax of the `ip=` parameter is documented in https://www.man7.org/linux/man-pages/man7/dracut.cmdline.7.html[Dracut manpages].	A sintaxe completa do parâmetro `ip =` está documentada nas https://www.man7.org/linux/man-pages/man7/dracut.cmdline.7.html[páginas man do Dracut].

Loading…

rffontenelle

Translation added

English

Portuguese (Brazil) 60 characters edited Current translation

4 years ago

Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English	Portuguese (Brazil)
No related strings found in the glossary.

String information

Source string description

type: delimited block -

Flags

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

Source string location

pages/provisioning-vmware.adoc:135

String age

4 years ago

Last updated

a year ago

Source string age

4 years ago

Translation file

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

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.