Unit Instance
Units API.
See the Weblate's Web API documentation for detailed description of the API.
GET /api/units/14448674/?format=api
{ "translation": "https://l10n.opensuse.org/api/translations/yast-cluster/master/es/?format=api", "source": [ "<p><b><big>IP Version</big></b><br>Specifies version of IP to use for communication. Value can be one of ipv4 or ipv6. Default (if unspecified) is ipv4.<br></p>\n<p><b><big>Bind Network Address</big></b><br>This specifies the address which the corosync executive should bind. This address should always end in zero. If the totem traffic should be routed over 192.168.5.92, set bindnetaddr to 192.168.5.0.<br>This may also be an IPV6 address, in which case IPV6 networking will be used. In this case, the full address must be specified and there is no automatic selection of the network interface within a specific subnet as with IPv4. If IPv6 networking is used, the nodeid field must be specified.<br></p>\n<p><b><big>Multicast Address</big></b><br>This is the multicast address used by corosync executive. The default should work for most networks, but the network administrator should be queried about a multicast address to use. Avoid 224.x.x.x because this is a \"config\" multicast address.<br>This may also be an IPV6 multicast address, in which case IPV6 networking will be used. If IPv6 networking is used, the nodeid field must be specified.</p>\n<p><b><big>Port</big></b><br>This specifies the UDP port number. It is possible to use the same multicast address on a network with the corosync services configured for different UDP ports.<br></p>\n<p><b><big>Member Address</big></b><br>This list specifies all the nodes in the cluster by IP address. This could be configurable when using udpu(Unicast). <br></p>\n<p><b><big>Node ID</big></b><br>This configuration option is optional when using IPv4 and required when using IPv6. This is a 32 bit value specifying the node identifier delivered to the cluster membership service. If this is not specified with IPv4, the node id will be determined from the 32 bit IP address the system to which the system is bound with ring identifier of 0. The node identifier value of zero is reserved and should not be used.<br></p>\n<p><b><big>rrp_mode</big></b><br>This specifies the mode of redundant ring, which may be none, active, or passive. Active replication offers slightly lower latency from transmit to delivery in faulty network environments but with less performance. Passive replication may nearly double the speed of the totem protocol if the protocol doesn't become cpu bound. The final option is none, in which case only one network interface will be used to operate the totem protocol. If only one interface directive is specified, none is automatically chosen. If multiple interface directives are specified, only active or passive may be chosen.<br></p>\n<p><b><big>Cluster Name</big></b><br>This specifies the name of cluster and it's used for automatic generating of multicast address. Default is hacluster. For a geo cluster, each cluster must have a unique name.<br></p>\n<p><b><big>Expected votes</big></b><br>Expect vote number for voting quorum. Will be automatically calculated when the nodelist {} section is present in corosync.conf (the list will be generated when using unicast transport) or can be specified in the quorum {} section (Expect votes should use the total node numble of the cluster). If Expected votes presents in unicast transport, the value will override the one automatically calculated. For safety, the Expected votes will be disabled once nodelist not empty, it's good for ignore the inappropriate Expected votes set.<br></p>\n<p><b><big>Auto Generate Node ID</big></b><br>Nodeid is required when using IPv6. Auto node ID enabled will generate nodeid automatically.<br></p>\n" ], "previous_source": "<p><b><big>IP Version</big></b><br>Specifies version of IP to use for communication. Value can be one of ipv4 or ipv6. Default (if unspecified) is ipv4.<br></p>\n<p><b><big>Bind Network Address</big></b><br>This specifies the address which the openais executive should bind. This address should always end in zero. If the totem traffic should be routed over 192.168.5.92, set bindnetaddr to 192.168.5.0.<br>This may also be an IPV6 address, in which case IPV6 networking will be used. In this case, the full address must be specified and there is no automatic selection of the network interface within a specific subnet as with IPv4. If IPv6 networking is used, the nodeid field must be specified.<br></p>\n<p><b><big>Multicast Address</big></b><br>This is the multicast address used by openais executive. The default should work for most networks, but the network administrator should be queried about a multicast address to use. Avoid 224.x.x.x because this is a \"config\" multicast address.<br>This may also be an IPV6 multicast address, in which case IPV6 networking will be used. If IPv6 networking is used, the nodeid field must be specified.</p>\n<p><b><big>Port</big></b><br>This specifies the UDP port number. It is possible to use the same multicast address on a network with the openais services configured for different UDP ports.<br></p>\n<p><b><big>Member Address</big></b><br>This list specifies all the nodes in the cluster by IP address. This could be configurable when using udpu(Unicast). <br></p>\n<p><b><big>Node ID</big></b><br>This configuration option is optional when using IPv4 and required when using IPv6. This is a 32 bit value specifying the node identifier delivered to the cluster membership service. If this is not specified with IPv4, the node id will be determined from the 32 bit IP address the system to which the system is bound with ring identifier of 0. The node identifier value of zero is reserved and should not be used.<br></p>\n<p><b><big>rrp_mode</big></b><br>This specifies the mode of redundant ring, which may be none, active, or passive. Active replication offers slightly lower latency from transmit to delivery in faulty network environments but with less performance. Passive replication may nearly double the speed of the totem protocol if the protocol doesn't become cpu bound. The final option is none, in which case only one network interface will be used to operate the totem protocol. If only one interface directive is specified, none is automatically chosen. If multiple interface directives are specified, only active or passive may be chosen.<br></p>\n<p><b><big>Cluster Name</big></b><br>This specifies the name of cluster and it's used for automatic generating of multicast address. Default is hacluster. For a geo cluster, each cluster must have a unique name.<br></p>\n<p><b><big>Expected votes</big></b><br>Expect vote number for voting quorum. Will be automatically calculated when the nodelist {} section is present in corosync.conf (the list will be generated when using unicast transport) or can be specified in the quorum {} section (Expect votes should use the total node numble of the cluster). If Expected votes presents in unicast transport, the value will override the one automatically calculated. For safety, the Expected votes will be disabled once nodelist not empty, it's good for ignore the inappropriate Expected votes set.<br></p>\n<p><b><big>Auto Generate Node ID</big></b><br>Nodeid is required when using IPv6. Auto node ID enabled will generate nodeid automatically.<br></p>\n", "target": [ "<p><b><big>Versión de IP</big></b><br>Especifica la versión de IP que se va a usar para la comunicación. El valor puede ser ipv4 o ipv6. El valor por defecto (si no se especifica ninguno) es ipv4.<br></p>\n<p><b><big>Dirección de red de enlace</big></b><br>Especifica la dirección con la que debe enlazarse la directiva corosync. Esta dirección siempre debe terminar en cero. Si el tráfico de totem debe redirigirse a través de 192.168.5.92, defina bindnetaddr como 192.168.5.0.<br>También puede ser una dirección IPV6, en cuyo caso se utilizará la red IPV6. En ese caso, es necesario especificar la dirección completa y no habrá selección automática de la interfaz de red dentro de una subred específica, como con IPv4. Si se utiliza una red IPv6, es necesario especificar el campo nodeid.<br></p>\n<p><b><big>Dirección multidifusión</big></b><br>Es la dirección de multidifusión empleada por la directiva corosync. El valor por defecto debería funcionar en la mayoría de las redes, pero es recomendable consultar al administrador de la red la dirección de multidifusión que se debe utilizar. No use 224.x.x.x, ya que es una dirección de multidifusión \"config\".<br>También puede ser una dirección de multidifusión IPV6, en cuyo caso se utilizará una red IPV6. Si se utiliza una red IPv6, es necesario especificar el campo nodeid.</p>\n<p><b><big>Puerto</big></b><br>Permite especificar el número de puerto UDP. Es posible utilizar la misma dirección de multidifusión en una red con los servicios corosync configurados para diferentes puertos UDP.<br></p>\n<p><b><big>Dirección de miembro</big></b><br>Esta lista especifica todos los nodos del clúster por direcciones IP. Puede ser configurable si se utiliza udpu (monodifusión). <br></p>\n<p><b><big>ID de nodo</big></b><br>Esta opción de configuración es opcional si se utiliza IPv4 y obligatoria si se utiliza IPv6. Es un valor de 32 bits que especifica el identificador de nodo enviado al servicio de pertenencia a clúster. Si no se especifica con IPv4, el ID de nodo se determinará a partir de la dirección IP de 32 bits con la que esté enlazado el sistema con un identificador de llamada de 0. El valor de identificador de nodo de cero está reservado y no debe utilizarse.<br></p>\n<p><b><big>rrp_mode</big></b><br>Especifica el modo de llamada redundante, que puede ser ninguno, activo o pasivo. La replicación activa ofrece una latencia ligeramente inferior de la transmisión a la entrega en entornos de red defectuosos, pero con menor rendimiento. La replicación pasiva puede casi duplicar la velocidad del protocolo totem si no se enlaza a la CPU. La última opción es ninguno, en cuyo caso solo se utilizará una interfaz de red para operar el protocolo totem. Si solo se especifica una directiva de interfaz, no se elige ninguna automáticamente. Si se especifican varias directivas de interfaz, solo podrán elegirse las activas o las pasivas.<br></p>\n<p><b><big>Nombre del clúster</big></b><br>Especifica el nombre del clúster y se usa para generar automáticamente direcciones de multidifusión. El valor por defecto es hacluster. Para un clúster geográfico, cada clúster debe tener un nombre exclusivo.<br></p>\n<p><b><big>Votos esperados</big></b><br>Número de votos esperados para el quorum de votación. Se calculará automáticamente si la sección nodelist {} se encuentra presente en corosync.conf (la lista se generará al usar el transporte de monodifusión) o puede especificarse en la sección quorum {} (los votos esperados deben usar el número total de nodos del clúster). Si hay un valor de votos esperados presente en el transporte de monodifusión, el valor anulará el que se ha calculado automáticamente. Por seguridad, el campo de votos esperados se inhabilitará si la lista de nodos no está vacía. Esto es práctico para ignorar los conjuntos de votos esperados no adecuados.<br></p>\n<p><b><big>Generar automáticamente ID de nodo</big></b><br>El valor nodeid es obligatorio si se utiliza IPv6. Si esta opción está habilitada, el valor nodeid se generará automáticamente.<br></p>\n" ], "id_hash": 3081110394975739161, "content_hash": 3081110394975739161, "location": "src/include/cluster/helps.rb:35", "context": "", "note": "All helps are here", "flags": "", "labels": [], "state": 20, "fuzzy": false, "translated": true, "approved": false, "position": 117, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 519, "source_unit": "https://l10n.opensuse.org/api/units/14448657/?format=api", "priority": 100, "id": 14448674, "web_url": "https://l10n.opensuse.org/translate/yast-cluster/master/es/?checksum=aac24d946e4add19", "url": "https://l10n.opensuse.org/api/units/14448674/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2023-04-03T20:19:48.251261Z" }