SUSE has an in-house translations created by contracted translators in past. The work flow did not allow to merge translations between openSUSE and SLE trees up to now. It caused translation divergence. SLE Merge Robot is an output of the merge effort, and “suggests” to use SLE translation. Please review carefully, and keep standard terminology used in your language.

Initial import of yast was created from the community translations, but strings actually missing in the community translation were taken from the contracted SUSE Linux Enterprise translations. These translations are mixed in Weblate. If you are interested in the SUSE Linux Enterprise translations import review, go to <ftp://ftp.suse.com/pub/people/sbrabec/yast-translations-sle-contributions/>

yast2-cluster is not part of openSUSE Leap 15. It exists only in openSUSE Tumbleweed and enterprise products.

The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not merge the repository.

Overview

Project website github.com/yast/yast-cluster
Project maintainers User avatar ancorgonzalezsosa User avatar LubosKocman
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Translation license GNU General Public License v2.0 only
Source code repository git@github.com:yast/yast-translations.git
Repository branch master
Last remote commit New POT for text domain 'hana-ha'. 7869d671a6
YaST Jenkins authored 2 weeks ago
Last commit in Weblate Translated using Weblate (Portuguese (Brazil)) e558dad9ed
User avatar LuizFernandoRanghetti authored 7 months ago
Weblate repository https://l10n.opensuse.org/git/yast-base/master/
Filemask po/cluster/*.po
Translation file Download po/cluster/ru.po
Last change May 12, 2019, 1:21 p.m.
Last author Alex Minton

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 147 2,041 14,683
Translated 71% 105 34% 714 34% 5,111
Needs editing 10% 15 57% 1,172 56% 8,286
Failing checks 2% 3 52% 1,077 52% 7,707
Strings with suggestions 0% 0 0% 0 0% 0
Not translated strings 18% 27 7% 155 8% 1,286
Last year Previous

Activity in last 12 months

0 changes 0 changes 6 changes 0 changes 2 changes 0 changes 0 changes 0 changes 0 changes 3 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 2 changes 0 changes
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov

Quick numbers

2,041
Hosted words
147
Hosted strings
71%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
—
—
Hosted strings
—
—
Translated
—
—
Contributors
—
User avatar None

New string to translate

yast-cluster / master — Russian

New string to translate 8 months ago
User avatar None

Resource update

yast-cluster / master — Russian

File /var/lib/weblate/vcs/yast-base/master/po/cluster/ru.po was changed. 8 months ago
User avatar None

Source string changed

yast-cluster / master — Russian

<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>
<p><b><big>Bind Network Address</big></b><br>This specifies the address which the openaiscorosync 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>
<p><b><big>Multicast Address</big></b><br>This is the multicast address used by openaiscorosync 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>
<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 openaiscorosync services configured for different UDP ports.<br></p>
<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>
<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>
<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>
<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>
<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>
<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>
8 months ago
User avatar None

New string to translate

yast-cluster / master — Russian

New string to translate a year ago
User avatar None

Resource update

yast-cluster / master — Russian

File /var/lib/weblate/vcs/yast-base/master/po/cluster/ru.po was changed. a year ago
User avatar None

Resource update

yast-cluster / master — Russian

File /var/lib/weblate/vcs/yast-base/master/po/cluster/ru.po was changed. a year ago
User avatar None

Resource update

yast-cluster / master — Russian

File /var/lib/weblate/vcs/yast-base/master/po/cluster/ru.po was changed. a year ago
User avatar None

Resource update

yast-cluster / master — Russian

File /var/lib/weblate/vcs/yast-base/master/po/cluster/ru.po was changed. a year ago
User avatar None

Resource update

yast-cluster / master — Russian

File /var/lib/weblate/vcs/yast-base/master/po/cluster/ru.po was changed. a year ago
User avatar None

Resource update

yast-cluster / master — Russian

File /var/lib/weblate/vcs/yast-base/master/po/cluster/ru.po was changed. a year ago
Browse all translation changes