uyuni/docs installation-and-upgrade-manager-4.3-MU-4.3.13 — Spanish @ openSUSE Weblate: For {suse} operating systems, the version and SP level must …

Translation

Source change

English type: delimited block =

Spanish

Needs editing

Skip

	English	Spanish	Actions
	xref:server-major-upgrade-uyuni.adoc[Server - Major Upgrade]	xref:server-setup.adoc[Configuración de Server]
	xref:proxy-intro.adoc[Upgrade the Proxy]	xref:proxy-setup.adoc[Configuración de Proxy]
	xref:proxy-uyuni.adoc[Proxy - Major Upgrade]	xref:proxy-setup.adoc[Configuración de Proxy]
	xref:proxy-minor-uyuni.adoc[Proxy - Minor Upgrade]	xref:proxy-setup.adoc[Configuración de Proxy]
	xref:proxy-x.adoc[Proxy - Major Version Upgrade]	xref:proxy-setup.adoc[Configuración de Proxy]
	xref:proxy-y-z.adoc[Proxy - Minor Version or Patch Level Upgrade]
	xref:db-intro.adoc[Upgrade the Database]
	xref:db-migration-xy.adoc[Database Migration to Latest Version]
	xref:client-intro.adoc[Upgrade the Clients]	xref:install-overview.adoc[Guía de instalación]
	Upgrade the Clients
	Clients use the versioning system of their underlying operating system. For clients using {suse} operating systems, you can perform upgrades within the {productname} {webui}.
	For more information about upgrading clients, see xref:client-configuration:client-upgrades.adoc[].	Para una lista complea de clientes y características soporados, vea xref:client-configuration:supported-features.adoc[].
	Supported Client Systems	Sistemas clientes soportados
	Supported operating systems for traditional and Salt clients are listed in this table.	Los sistemas operativos soportados como cliente tradicional y Salt se listan en esta tabla.
	In this table, {check} indicates that clients running the operating system are supported by {suse}, and {cross} indicates that it is not supported. Fields marked as {question} are under consideration, and may or may not be supported at a later date.	En esta tabla, {check} indica que los clientes que ejecutan el sistema operativo están soportados por {suse}, y {cross} indica que no están soportados. Los campos marcados con {question} están en evalución y podrían ser soportados en el futuro.
	For {suse} operating systems, the version and SP level must be under general support (normal or LTSS) to be supported with {productname}. For details on supported product versions, see:	En sistemas operativos {suse}, la versión y nivel de Pack de Servicio (SP) deben estar soportados con soporte general (normal o LTSS) para estar soportados con {productname}. Para más detalles sobre las versiones de producto soportadas, vea https://www.suse.com/lifecycle. Para sistemas operativos no-{suse}, incluyendo {rhel}, {centos}, y {oracle}, solo está soportada la última versión disponible.
	link:https://www.suse.com/lifecycle[]
	For non-{suse} operating systems, including {rhel}, {centos}, and {oracle}, only the latest available version is under general support.
	\| Operating System \| Architecture \| Traditional Clients \| Salt Clients \| {sle} 15, 12 \| {x86_64}, {ppc64le}, {ibmz}, {aarch64} \| {check} \| {check} \| {sles} for SAP 15, 12 \| {x86_64}, {ppc64le} \| {check} \| {check} \| {micro} \| {x86_64}, {aarch64}, {s390x} \| {cross} \| {check} \| {sl-micro} \| {x86_64}, {aarch64}, {s390x} \| {cross} \| {check} \| {opensuse} Leap 15 \| {x86_64}, {aarch64} \| {check} \| {check} \| {sll} 9, 8, 7 \| {x86_64} \| {cross} \| {check} \| {almalinux} 9, 8 \| {x86_64}, {aarch64} \| {cross} \| {check} \| {amazon} 2 \| {x86_64}, {aarch64} \| {cross} \| {check} \| {centos} 8, 7 \| {x86_64}, {aarch64} \| {cross} \| {check} \| {debian} 12, 11 \| {x86_64} \| {cross} \| {check} \| {oracle} 9, 8, 7 \| {x86_64}, {aarch64} \| {cross} \| {check} \| {rhel} 9, 8, 7 \| {x86_64} \| {cross} \| {check} \| {rocky} 9, 8 \| {x86_64}, {aarch64} \| {cross} \| {check} \| {ubuntu} 22.04, 20.04 \| {amd64} \| {cross} \| {check}	\| Sistema operativo \| Arquitectura \| Cliente tradicional \| Cliente Salt \| {sle} 15 \| {x86_64}, {ppc64le}, {ibmz}, ARM \| {check} \| {check} \| {sle} 12 \| {x86_64}, {ppc64le}, {ibmz}, ARM \| {check} \| {check} \| {sle} 11 \| {x86}, {x86_64}, {ppc64}, {ibmz} \| {check} \| {check} \| {sles}-ES 8 \| {x86_64} \| {check} \| {check} \| {sles}-ES 7 \| {x86_64} \| {check} \| {check} \| {sles}-ES 6 \| {x86}, {x86_64} \| {check} \| {check} \| {sles} for SAP \| {x86_64}, {ppc64le} \| {check} \| {check} \| {rhel} 8 \| {x86_64} \| {cross} \| {check} \| {rhel} 7 \| {x86_64} \| {check} \| {check} \| {rhel} 6 \| {x86}, {x86_64} \| {check} \| {check} \| CentOS 8 \| {x86_64} \| {cross} \| {check} \| CentOS 7 \| {x86_64} \| {check} \| {check} \| CentOS 6 \| {x86}, {x86_64} \| {check} \| {check} \| {oracle}{nbsp}8 \| {x86_64} \| {cross} \| {check} \| {oracle}{nbsp}7 \| {x86_64} \| {check} \| {check} \| {oracle}{nbsp}6 \| {x86}, {x86_64} \| {check} \| {check} \| {opensuse} Leap 15 \| {x86_64} \| {cross} \| {check} \| {ubuntu} 20.04 \| {x86_64} \| {cross} \| {check} \| {ubuntu} 18.04 \| {x86_64} \| {cross} \| {check} \| {ubuntu} 16.04 \| {x86_64} \| {cross} \| {check}
	Salt SSH is using [path]``/var/tmp`` to deploy Salt Bundle to and execute Salt commands on the client with the bundled Python. Therefore you must not mount [path]``/var/tmp`` with the [option]``noexec`` option. It is not possible to bootstrap the clients, which have [path]``/var/tmp`` mounted with [option]``noexec`` option, with the {webui} because the bootstrap process is using Salt SSH to reach a client.
	When you are setting up your client hardware, you need to ensure you have enough for the operating system and for the workload you want to perform on the client, with these additions for {productname}:
	Client Additional Hardware Requirements	Requisitos de software y hardware
	\| Hardware \| Additional Size Required \| RAM \| 512{nbsp}MB \| Disk Space: \| 200{nbsp}MB
	Connect {payg} instance
	In the three major public cloud providers (AWS, GCP and Azure), SUSE:
	provides customized {payg} product images for SLES, SLES for SAP, etc.
	operates per-region RMT Servers mirroring repositories for products available as {payg}
	This document describes how to connect existing {payg} instance to {productname} server, and gives basic information about credentials collection from the instance. The goal of this connection is to extract authentication data so the {productname} Server can connect to a cloud RMT host. Then the {productname} Server has access to products on the RMT host that are not already available with the {scc} organization credentials.
	Before using {payg} feature make sure that:
	The {payg} instance is launched from the correct SUSE product image (for example, SLES, SLES for SAP, or SLE HPC) to allow access to the desired repositories
	{productname} Server has connectivity to the {payg} instance (ideally in the same region) either directly or via a bastion

Loading…

None

String added in the repository

English

Spanish 401 characters edited Current translation Needs editing

3 weeks ago

None

Source string changed

English 168 characters edited Needs editing

3 weeks ago

Browse all string changes

Things to check

Mismatched colon

Source and translation do not both end with a colon

Reset

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Glossary

English	Spanish
SUSE	SUSE	uyuni

String information

Source string description

type: delimited block =

Source string location

modules/installation-and-upgrade/pages/client-requirements.adoc:4

String age

3 weeks ago

Last updated

3 weeks ago

Source string age

3 weeks ago

Translation file

l10n-weblate/installation-and-upgrade/es.po, string 61