yast-cluster/master — Bengali @ openSUSE Weblate: Read the database

English

Bengali

Actions

<big>IP Version</big> Specifies version of IP to use for communication. Value can be one of ipv4 or ipv6. Default (if unspecified) is ipv4. 
<big>Bind Network Address</big> 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. 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. 
<big>Multicast Address</big> 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. 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.
<big>Port</big> 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. 
<big>Member Address</big> This list specifies all the nodes in the cluster by IP address. This could be configurable when using udpu(Unicast). 
<big>Node ID</big> 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. 
<big>rrp_mode</big> 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. 
<big>Cluster Name</big> 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. 
<big>Expected votes</big> 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. 
<big>Auto Generate Node ID</big> Nodeid is required when using IPv6. Auto node ID enabled will generate nodeid automatically.

<big>Model</big> Specifies the model to be used. This parameter is required. corosync-qdevice is modular and is able to support multiple different models. The model basically defines what type of arbitrator is used. Currently only 'net' is supported.
<big>Host</big> Specifies the IP address or host name of the qnetd server to be used. This parameter is required.
<big>Port</big> Specifies TCP port of qnetd server. Default is 5403.
<big>TLS</big> Can be one of 'on', 'off' or 'required' and specifies if tls should be used. 'on' means a connection with TLS is attempted first, but if the server doesn't advertise TLS support then non-TLS will be used. 'off' is used then TLS is not required and it's then not even tried. This mode is the only one which doesn't need a properly initialized NSS database. 'required' means TLS is required and if the server doesn't support TLS, qdevice will exit with error message. 'on' need manually change, refer to corosync-qdevice's man page for more details. Default is 'off' in yast.
<big>Algorithm</big> Decision algorithm. Can be one of the 'ffsplit' or 'lms'. (Actually there are also 'test' and '2nodelms', both of which are mainly for developers and shouldn't be used for production clusters, so yast will convert to 'ffsplit' automatically). For a description of what each algorithm means and how the algorithms differ see their individual sections. Default value is ffsplit.
<big>Tie breaker</big> Can be one of 'lowest', 'highest' or 'valid_node_id' (number) values. It's used as a fallback if qdevice has to decide between two or more equal partitions. 'lowest' means the partition with the lowest node id is chosen. 'highest' means the partition with highest node id is chosen. And 'valid_node_id' means that the partition containing the node with the given node id is chosen. Default is 'lowest'.
<big>Qdevice Heuristics</big> Subsection of Qdevice. Heuristics are set of commands executed locally on startup, cluster membership change, successful connect to corosync-qnetd and optionally also at regular times. Commands are executed in parallel. When *all* commands finish successfully (their return error code is zero) on time, heuristics have passed, otherwise they have failed. The heuristics result is sent to corosync-qnetd and there it's used in calculations to determine which partition should be quorate.
<big>Heuristics Mode</big> Can be one of on, sync or off and specifies mode of operation of heuristics. Default is off, which means heuristics are disabled. When sync is set, heuristics are executed only during startup, membership change and when connection to corosync-qnetd is established. When heuristics should be running also on regular basis, this option should be set to on value.
<big>Heuristics Timeout</big> Specifies maximum time in milliseconds. How long corosync-qdevice waits till the heuristics commands finish. If some command doesn't finish before the timeout, it's killed and heuristics fail. This timeout is used for heuristics executed at regular times. Default value is half of the quorum.device.timeout, so 5000.
<big>Heuristics Sync_timeout</big> Similar to quorum.device.heuristics.timeout but used during membership changes. Default value is half of the quorum.device.sync_timeout, so 15000.
<big>Heuristics Interval</big> Specifies interval between two regular heuristics execution. Default value is 3 * quorum.device.timeout, so 30000.
<big>Heuristics exec_NAME</big> Defines executables. *NAME* can be arbitrary valid cmap key name string and it has no special meaning. The value of this variable must contain a command to execute. The value is parsed (split) into arguments similarly as Bourne shell would do. Quoting is possible by using backslash and double quotes. For example, Name(exec_check_master), Value(/etc/corosync/qdevice/check_master.sh)

<big>Enable Security Auth</big> This specifies that HMAC/SHA1 authentication should be used to authenticate all messages. It further specifies that all data should be encrypted with the sober128 encryption algorithm to protect data from eavesdropping. Enabling this option adds a 36 byte header to every message sent by totem which reduces total throughput. Encryption and authentication consume 75% of CPU cycles in aisexec as measured with gprof when enabled. For 100Mbit networks with 1500 MTU frame transmissions: A throughput of 9Mb/s is possible with 100% cpu utilization when this option is enabled on 3GHz cpus. A throughput of 10Mb/s is possible wth 20% cpu utilization when this option is disabled on 3GHz cpus. For gig-e networks with large frame transmissions: A throughput of 20Mb/s is possible when this option is enabled on 3GHz cpus. A throughput of 60Mb/s is possible when this option is disabled on 3GHz cpus. The default is on.

<big>Cluster start at booting time enable/disable</big> Start or not start the whole cluster at booting time. Service include: pacemaker, corosync, corosync-qdevice(If enabled corosyncqdevice).
<big>Cluster start/stop now</big> Start or stop the whole cluster right now. Service include: pacemaker, corosync, corosync-qdevice(If enabled corosyncqdevice).
<big>Firewall Settings</big> Enable the port when Firewall is enabled

<big>Sync Host</big> The hostnames used here must be the local hostnames of the cluster nodes. That means you must use exactly the same string as printed out by the hostname command.
<big>Sync File</big> The full absolute filename to be synced.
<big>Pre-Shared-Keys</big> Authentication is performed using the IP addresses and pre-shared-keys in Csync2. The key file is generated with csync2 -k /etc/csync2/key_hagroup. The file key_hagroup should be copied to all members of the cluster manually after it's created.

<big>Dedicated Interface</big> A dedicated network interface for syncing. The interface must support multicast, and is UP for using. You may have to have it pre-configured. 
<big>IP</big> The IPv4 address assigned to the dedicated network interface. This is detected automatically.
<big>Multicast Address</big> The multicast address to be used for syncing.
<big>Group Number</big> A numeric ID indicate the group for syncing.

English	Bengali
No related strings found in the glossary.

English

Bengali

No related strings found in the glossary.

	English	Bengali	Actions
	The Multicast Address has to be fulfilled
	The Group Number must be a positive integer	ক্লক স্কিউ-এর মান অবশ্যই একটা যোগ সংখ্যা হতে হবে.
	<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 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> <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> <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> <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>
	<p><b><big>Model</big></b><br>Specifies the model to be used. This parameter is required. corosync-qdevice is modular and is able to support multiple different models. The model basically defines what type of arbitrator is used. Currently only 'net' is supported.</p> <p><b><big>Host</big></b><br>Specifies the IP address or host name of the qnetd server to be used. This parameter is required.</p> <p><b><big>Port</big></b><br>Specifies TCP port of qnetd server. Default is 5403.</p> <p><b><big>TLS</big></b><br>Can be one of 'on', 'off' or 'required' and specifies if tls should be used. 'on' means a connection with TLS is attempted first, but if the server doesn't advertise TLS support then non-TLS will be used. 'off' is used then TLS is not required and it's then not even tried. This mode is the only one which doesn't need a properly initialized NSS database. 'required' means TLS is required and if the server doesn't support TLS, qdevice will exit with error message. 'on' need manually change, refer to corosync-qdevice's man page for more details. Default is 'off' in yast.</p> <p><b><big>Algorithm</big></b><br>Decision algorithm. Can be one of the 'ffsplit' or 'lms'. (Actually there are also 'test' and '2nodelms', both of which are mainly for developers and shouldn't be used for production clusters, so yast will convert to 'ffsplit' automatically). For a description of what each algorithm means and how the algorithms differ see their individual sections. Default value is ffsplit.</p> <p><b><big>Tie breaker</big></b><br>Can be one of 'lowest', 'highest' or 'valid_node_id' (number) values. It's used as a fallback if qdevice has to decide between two or more equal partitions. 'lowest' means the partition with the lowest node id is chosen. 'highest' means the partition with highest node id is chosen. And 'valid_node_id' means that the partition containing the node with the given node id is chosen. Default is 'lowest'.</p> <p><b><big>Qdevice Heuristics</big></b><br>Subsection of Qdevice. Heuristics are set of commands executed locally on startup, cluster membership change, successful connect to corosync-qnetd and optionally also at regular times. Commands are executed in parallel. When all commands finish successfully (their return error code is zero) on time, heuristics have passed, otherwise they have failed. The heuristics result is sent to corosync-qnetd and there it's used in calculations to determine which partition should be quorate.</p> <p><b><big>Heuristics Mode</big></b><br>Can be one of on, sync or off and specifies mode of operation of heuristics. Default is off, which means heuristics are disabled. When sync is set, heuristics are executed only during startup, membership change and when connection to corosync-qnetd is established. When heuristics should be running also on regular basis, this option should be set to on value.</p> <p><b><big>Heuristics Timeout</big></b><br>Specifies maximum time in milliseconds. How long corosync-qdevice waits till the heuristics commands finish. If some command doesn't finish before the timeout, it's killed and heuristics fail. This timeout is used for heuristics executed at regular times. Default value is half of the quorum.device.timeout, so 5000.</p> <p><b><big>Heuristics Sync_timeout</big></b><br>Similar to quorum.device.heuristics.timeout but used during membership changes. Default value is half of the quorum.device.sync_timeout, so 15000.</p> <p><b><big>Heuristics Interval</big></b><br>Specifies interval between two regular heuristics execution. Default value is 3 * quorum.device.timeout, so 30000.</p> <p><b><big>Heuristics exec_NAME</big></b><br>Defines executables. NAME can be arbitrary valid cmap key name string and it has no special meaning. The value of this variable must contain a command to execute. The value is parsed (split) into arguments similarly as Bourne shell would do. Quoting is possible by using backslash and double quotes. <br>For example, Name(exec_check_master), Value(/etc/corosync/qdevice/check_master.sh)</p>
	<p><b><big>Enable Security Auth</big></b><br>This specifies that HMAC/SHA1 authentication should be used to authenticate all messages. It further specifies that all data should be encrypted with the sober128 encryption algorithm to protect data from eavesdropping. Enabling this option adds a 36 byte header to every message sent by totem which reduces total throughput. Encryption and authentication consume 75% of CPU cycles in aisexec as measured with gprof when enabled. For 100Mbit networks with 1500 MTU frame transmissions: A throughput of 9Mb/s is possible with 100% cpu utilization when this option is enabled on 3GHz cpus. A throughput of 10Mb/s is possible wth 20% cpu utilization when this option is disabled on 3GHz cpus. For gig-e networks with large frame transmissions: A throughput of 20Mb/s is possible when this option is enabled on 3GHz cpus. A throughput of 60Mb/s is possible when this option is disabled on 3GHz cpus. The default is on. <br></p>
	<p><b><big>Cluster start at booting time enable/disable</big></b><br>Start or not start the whole cluster at booting time. Service include: pacemaker, corosync, corosync-qdevice(If enabled corosyncqdevice).</p> <p><b><big>Cluster start/stop now</big></b><br>Start or stop the whole cluster right now. Service include: pacemaker, corosync, corosync-qdevice(If enabled corosyncqdevice).</p> <p><b><big>Firewall Settings</big></b><br>Enable the port when Firewall is enabled</p>
	<p><b><big>Sync Host</big></b><br>The hostnames used here must be the local hostnames of the cluster nodes. That means you must use exactly the same string as printed out by the hostname command.</p> <p><b><big>Sync File</big></b><br>The full absolute filename to be synced.</p> <p><b><big>Pre-Shared-Keys</big></b><br>Authentication is performed using the IP addresses and pre-shared-keys in Csync2. The key file is generated with csync2 -k /etc/csync2/key_hagroup. The file key_hagroup should be copied to all members of the cluster manually after it's created.</p>
	<p><b><big>Dedicated Interface</big></b><br>A dedicated network interface for syncing. The interface must support multicast, and is UP for using. You may have to have it pre-configured. </p> <p><b><big>IP</big></b><br>The IPv4 address assigned to the dedicated network interface. This is detected automatically.</p> <p><b><big>Multicast Address</big></b><br>The multicast address to be used for syncing.</p> <p><b><big>Group Number</big></b><br>A numeric ID indicate the group for syncing.</p>
	<p><b><big>Initializing cluster Configuration</big></b><br> Please wait...<br></p>	<p><b><big>কনফিগারেশন চালু করছে</big></b><br> অনুগ্রহ করে অপেক্ষা করুন...<br></p>
	<p><b><big>Aborting Initialization:</big></b><br> Safely abort the configuration utility by pressing <b>Abort</b> now.</p>	<p><b><big>চালু করা বাতিল হচ্ছে:</big></b><br> এখন <b>বাতিল করুন</b> টিপে নিরাপদে সংরূপণ উপকরণ বাতিল করুন.</p>
	<p><b><big>Saving cluster Configuration</big></b><br> Please wait...<br></p>	<p><b>কনফিগারেশন সংরক্ষন করা হচ্ছে</b><br>অনুগ্রহ করে অপেক্ষা করুন...</p>
	<p><b><big>Aborting Saving:</big></b><br> Abort the save procedure by pressing <b>Abort</b>. An additional dialog informs whether it is safe to do so. </p>	<p><b><big>সংরক্ষণ বাতিল করছে:</big></b><br> <b>বাতিল করুন</b> টিপে সংরক্ষণ প্রক্রিয়া বাতিল করুন. এটা করা নিরাপদ হবে কিনা একটি অতিরিক্ত আলাপচারিতা আপনাকে সেটা জানায়. </p>
	Cluster Configuration	শ্রেণী গঠন
	Initializing...	আরম্ভ করা হচ্ছে...
	Initializing cluster Configuration	সিস্টেম কনফিগারেশন চূড়ান্ত করো
	Read the database	প্যাকেজ ডাটাবেস পড়া হচ্ছে...
	Read the previous settings	আগের সেটিংগুলি পড়ুন
	Read Firewall Settings	পড়ুন ফায়ারওয়াল সেটিংগুলি
	Reading the database...	প্যাকেজ ডাটাবেস পড়া হচ্ছে...
	Reading the previous settings...	পূর্বের সেিটিংগুলি পড়ছি...
	Reading Firewall settings...	ফায়ারওয়াল সেটিংগুলি পড়ছি...
	Finished	শেষ
	Cannot install required package	প্রয়োজনীয় প্যাকেজগুলোর ইনস্টলেশন ব্যর্থ হয়েছে.
	Cannot load existing configuration	বিদ্যমান কনফিগারেশন পরিবর্তন করুন
	Cannot read database1.	ডাটাবেস1 পড়তে পারি না.
	Cannot read database2.	উত্‍স পড়া সম্ভব হচ্ছে না.
	Cannot detect devices.	ডিভাইসগুলি সনাক্ত করা যাচ্ছে না.
	Saving cluster Configuration	উত্‍‌সের কনফিগারেশন সংরক্ষণ করা হচ্ছে
	Write the settings	সেটিংগুলি লিখুন
	Save firewall changes
	Writing the settings...	বৈশিষ্ট্যাবলী লেখা হচ্ছে...

yast-cluster

master

Bengali

Translate

Translation

Things to check

Mismatched full stop

Reused translation

Glossary

String information

Source string description

Source string location

String age

Last updated

Source string age

Translation file