diff --git a/doc/Pacemaker_Explained/en-US/Ap-Changes.xml b/doc/Pacemaker_Explained/en-US/Ap-Changes.xml index 73d5c56005..60ce3f4ca8 100644 --- a/doc/Pacemaker_Explained/en-US/Ap-Changes.xml +++ b/doc/Pacemaker_Explained/en-US/Ap-Changes.xml @@ -1,86 +1,86 @@ What Changed in 1.0
New Failure timeouts. See New section for resource and operation defaults. See and Tool for making offline configuration changes. See Rules, instance_attributes, meta_attributes and sets of operations can be defined once and referenced in multiple places. See The CIB now accepts XPath-based create/modify/delete operations. See the cibadmin help text. Multi-dimensional colocation and ordering constraints. See and The ability to connect to the CIB from non-cluster machines. See Allow recurring actions to be triggered at known times. See
Changed Syntax All resource and cluster options now use dashes (-) instead of underscores (_) master_slave was renamed to master The attributes container tag was removed The operation field pre-req has been renamed requires All operations must have an interval, start/stop must have it set to zero The stonith-enabled option now defaults to true. The cluster will refuse to start resources if stonith-enabled is true (or unset) and no STONITH resources have been defined The attributes of colocation and ordering constraints were renamed for clarity. See and resource-failure-stickiness has been replaced by migration-threshold. See - The arguments for command-line tools has been made consistent + The arguments for command-line tools have been made consistent Switched to RelaxNG schema validation and libxml2 parser. id fields are now XML IDs which have the following limitations id's cannot contain colons (:) id's cannot begin with a number id's must be globally unique (not just unique for that tag) Some fields (such as those in constraints that refer to resources) are IDREFs. This means that they must reference existing resources or objects in order for the configuration to be valid. - Removing an object which is referenced elsewhere will therefor fail. + Removing an object which is referenced elsewhere will therefore fail. The CIB representation from which the MD5 digest used to verify CIBs has changed. This means that every CIB update will require a full refresh on any upgraded nodes until the cluster is fully upgraded to 1.0. - This will result in significant performance degradation and it is therefor highly inadvisable to run a mixed 1.0/0.6 cluster for any longer than absolutely necessary. + This will result in significant performance degradation and it is therefore highly inadvisable to run a mixed 1.0/0.6 cluster for any longer than absolutely necessary. Ping node information no longer needs to be added to ha.cf Simply include the lists of hosts in your ping resource(s).
Removed Syntax It is no longer possible to set resource meta options as top-level attributes. Use meta attributes instead. Resource and operation defaults are no longer read from crm_config. See and instead.
diff --git a/doc/Pacemaker_Explained/en-US/Ap-Install.xml b/doc/Pacemaker_Explained/en-US/Ap-Install.xml index f6fe4578f0..72341ba849 100644 --- a/doc/Pacemaker_Explained/en-US/Ap-Install.xml +++ b/doc/Pacemaker_Explained/en-US/Ap-Install.xml @@ -1,108 +1,108 @@ Installation
Choosing a Cluster Stack Ultimately the choice of cluster stack is a personal decision that must be made in the context of you or your company's needs and strategic direction. Pacemaker currently functions equally well with both stacks. Here are some factors that may influence the decision SUSE/Novell, Red Hat and Oracle are all putting their collective weight behind the Corosync cluster stack. Corosync is an OSI Certified implementation of an industry standard (the Service Availability Forum Application Interface Specification). Using Corosync gives your applications access to the following additional cluster services checkpoint service distributed locking service extended virtual synchrony service cluster closed process group service It is likely that Pacemaker, at some point in the future, will make use of some of these additional services not provided by Heartbeat To date, Pacemaker has received less real-world testing on Corosync than it has on Heartbeat.
Enabling Pacemaker
For Corosync The Corosync configuration is normally located in /etc/corosync/corosync.conf and an example for a machine with an address of 1.2.3.4 in a cluster communicating on port 1234 (without peer authentication and message encryption) is shown below. An example Corosync configuration file totem { version: 2 secauth: off threads: 0 interface { ringnumber: 0 bindnetaddr: 1.2.3.4 mcastaddr: 226.94.1.1 mcastport: 1234 } } logging { fileline: off to_syslog: yes syslog_facility: daemon } amf { mode: disabled } The logging should be mostly obvious and the amf section refers to the Availability Management Framework and is not covered in this document. - The interesting part of the configuration is the totem section. This is where we define the how the node can communicate with the rest of the cluster and what protocol version and options (including encryption + The interesting part of the configuration is the totem section. This is where we define how the node can communicate with the rest of the cluster and what protocol version and options (including encryption Please consult the Corosync website and documentation for details on enabling encryption and peer authentication for the cluster. ) it should use. Beginners are encouraged to use the values shown and modify the interface section based on their network. It is also possible to configure Corosync for an IPv6 based environment. Simply configure bindnetaddr and mcastaddr with their IPv6 equivalents. Eg Example options for an IPv6 environment bindnetaddr: fec0::1:a800:4ff:fe00:20 mcastaddr: ff05::1 To tell Corosync to use the Pacemaker cluster manager, add the following fragment to a functional Corosync configuration and restart the cluster. Configuration fragment for enabling Pacemaker under Corosync aisexec { user: root group: root } service { name: pacemaker ver: 0 } The cluster needs to be run as root so that its child processes (the lrmd in particular) have sufficient privileges to perform the actions requested of it. After-all, a cluster manager that can't add an IP address or start apache is of little use. The second directive is the one that actually instructs the cluster to run Pacemaker.
For Heartbeat Add the following to a functional ha.cf configuration file and restart Heartbeat Configuration fragment for enabling Pacemaker under Heartbeat crm respawn
diff --git a/doc/Pacemaker_Explained/en-US/Ap-OCF.xml b/doc/Pacemaker_Explained/en-US/Ap-OCF.xml index 9bfcf639d0..0fa9d7d2f6 100644 --- a/doc/Pacemaker_Explained/en-US/Ap-OCF.xml +++ b/doc/Pacemaker_Explained/en-US/Ap-OCF.xml @@ -1,208 +1,208 @@ More About OCF Resource Agents
Location of Custom Scripts OCF Resource Agents are found in /usr/lib/ocf/resource.d/provider. When creating your own agents, you are encouraged to create a new directory under /usr/lib/ocf/resource.d/ so that they are not confused with (or overwritten by) the agents shipped with Heartbeat. So, for example, if you chose the provider name of bigCorp and wanted a new resource named bigApp, you would create a script called /usr/lib/ocf/resource.d/bigCorp/bigApp and define a resource: <primitive id="custom-app" class="ocf" provider="bigCorp" type="bigApp"/>
Actions All OCF Resource Agents are required to implement the following actions Required Actions for OCF Agents Action Description Instructions start Start the resource Return 0 on success and an appropriate error code otherwise. Must not report success until the resource is fully active. stop Stop the resource Return 0 on success and an appropriate error code otherwise. Must not report success until the resource is fully stopped. monitor Check the resource's state Exit 0 if the resource is running, 7 if it is stopped and anything else if it is failed. NOTE: The monitor script should test the state of the resource on the local machine only. meta-data Describe the resource Provide information about this resource as an XML snippet. Exit with 0. NOTE: This is not performed as root. validate-all Verify the supplied parameters are correct Exit with 0 if parameters are valid, 2 if not valid, 6 if resource is not configured.
Additional requirements (not part of the OCF specs) are placed on agents that will be used for advanced concepts like clones and multi-state resources. Optional Actions for OCF Agents Action Description Instructions promote Promote the local instance of a multi-state resource to the master/primary state Return 0 on success demote Demote the local instance of a multi-state resource to the slave/secondary state Return 0 on success notify - Used by the cluster to send the agent pre and post notification events telling the resource what is or did just take place + Used by the cluster to send the agent pre and post notification events telling the resource what is or has just taken place Must not fail. Must exit 0
One action specified in the OCF specs is not currently used by the cluster recover - a variant of the start action, this should try to recover a resource locally. Remember to use ocf-tester to verify that your new agent complies with the OCF standard properly.
How Does the Cluster Interpret the OCF Return Codes? The first thing the cluster does is check the return code against the expected result. If the result does not match the expected value, then the operation is considered to have failed and recovery action is initiated. There are three types of failure recovery: Types of recovery performed by the cluster Recovery Type Description Action Taken by the Cluster soft A transient error occurred Restart the resource or move it to a new location hard A non-transient error that may be specific to the current node occurred Move the resource elsewhere and prevent it from being retried on the current node fatal A non-transient error that will be common to all cluster nodes (I.e. a bad configuration was specified) Stop the resource and prevent it from being started on any cluster node
Assuming an action is considered to have failed, the following table outlines the different OCF return codes and the type of recovery the cluster will initiate when it is received. OCF Return Codes and How They are Handled OCF Return Code OCF Alias Description Recovery Type 0 OCF_SUCCESS - Success. The command complete successfully. This is the expected result for all start, stop, promote and demote commands. + Success. The command completed successfully. This is the expected result for all start, stop, promote and demote commands. soft 1 OCF_ERR_GENERIC Generic "there was a problem" error code. soft 2 OCF_ERR_ARGS The resource's configuration is not valid on this machine. Eg. Refers to a location/tool not found on the node. hard 3 OCF_ERR_UNIMPLEMENTED The requested action is not implemented. hard 4 OCF_ERR_PERM The resource agent does not have sufficient privileges to complete the task. hard 5 OCF_ERR_INSTALLED The tools required by the resource are not installed on this machine. hard 6 OCF_ERR_CONFIGURED - The resource's configuration is invalid. Eg. A required parameters are missing. + The resource's configuration is invalid. Eg. A required parameter is missing. fatal 7 OCF_NOT_RUNNING The resource is safely stopped. The cluster will not attempt to stop a resource that returns this for any action. N/A 8 OCF_RUNNING_MASTER The resource is running in Master mode. soft 9 OCF_FAILED_MASTER The resource is in Master mode but has failed. The resource will be demoted, stopped and then started (and possibly promoted) again. soft other NA Custom error code. soft
Although counter intuitive, even actions that return 0 (aka. OCF_SUCCESS) can be considered to have failed. -This can happen when a resource that is expected to be in the Master state is found running as a Slave, or when a resource is found active on multiple machines..
Exceptions +This can happen when a resource that is expected to be in the Master state is found running as a Slave, or when a resource is found active on multiple machines.
Exceptions Non-recurring monitor actions (probes) that find a resource active (or in Master mode) will not result in recovery action unless it is also found active elsewhere The recovery action taken when a resource is found active more than once is determined by the multiple-active property of the resource Recurring actions that return OCF_ERR_UNIMPLEMENTED do not cause any type of recovery
diff --git a/doc/Pacemaker_Explained/en-US/Ap-Upgrade-Config.xml b/doc/Pacemaker_Explained/en-US/Ap-Upgrade-Config.xml index 8a7ff366d7..d9177d1230 100644 --- a/doc/Pacemaker_Explained/en-US/Ap-Upgrade-Config.xml +++ b/doc/Pacemaker_Explained/en-US/Ap-Upgrade-Config.xml @@ -1,93 +1,93 @@ Upgrading the Configuration from 0.6
Preparation Download the latest DTD from and ensure your configuration validates.
Perform the upgrade
Upgrade the software Refer to the appendix:
Upgrade the Configuration As XML is not the friendliest of languages, it is common for cluster administrators to have scripted some of their activities. In such cases, it is likely that those scripts will not work with the new 1.0 syntax. In order to support such environments, it is actually possible to continue using the old 0.6 syntax. The downside however, is that not all the new features will be available and there is a performance impact since the cluster must do a non-persistent configuration upgrade before each transition. So while using the old syntax is possible, it is not advisable to continue using it indefinitely. Even if you wish to continue using the old syntax, it is advisable to follow the upgrade procedure to ensure that the cluster is able to use your existing configuration (since it will perform much the same task internally). Create a shadow copy to work with crm_shadow --create upgrade06 Verify the configuration is valid crm_verify --live-check Fix any errors or warnings Perform the upgrade cibadmin --upgrade If this step fails, there are three main possibilities The configuration was not valid to start with - go back to step 2 The transformation failed - report a bug or email the project at pacemaker@oss.clusterlabs.org The transformation was successful but produced an invalid result The most common reason is ID values being repeated or invalid. Pacemaker 1.0 is much stricter regarding this type of validation If the result of the transformation is invalid, you may see a number of errors from the validation library. If these are not helpful, visit and/or try the following procedure described below under . Check the changes crm_shadow --diff If at this point there is anything about the upgrade that you wish to fine-tune (for example, to change some of the automatic IDs) now is the time to do so. Since the shadow configuration is not in use by the cluster, it is safe to edit the file manually: crm_shadow --edit Will open the configuration in your favorite editor (or whichever one is specified by the standard EDITOR environment variable). Preview how the cluster will react Test what the cluster will do when you upload the new configuration ptest -VVVVV --live-check --save-dotfile upgrade06.dot graphviz upgrade06.dot Verify that either no resource actions will occur or that you are happy with any that are scheduled. If the output contains actions you do not expect (possibly due to changes to the score calculations), you may need to make further manual changes. See for further details on how to interpret the output of ptest. Upload the changes crm_shadow --commit upgrade06 --force If this step fails, something really strange has occurred. You should report a bug.
Manually Upgrading the Configuration It is also possible to perform the configuration upgrade steps manually. To do this Locate the upgrade06.xsl conversion script or download the latest version from version control - xsltproc /path/tp/upgrade06.xsl config06.xml > config10.xml + xsltproc /path/to/upgrade06.xsl config06.xml > config10.xml Locate the pacemaker.rng script. - xmllint --relaxng /path/tp/pacemaker.rng config10.xml + xmllint --relaxng /path/to/pacemaker.rng config10.xml The advantage of this method is that it can be performed without the cluster running and any validation errors should be more informative (despite being generated by the same library!) since they include line numbers.
diff --git a/doc/Pacemaker_Explained/en-US/Ap-Upgrade.xml b/doc/Pacemaker_Explained/en-US/Ap-Upgrade.xml index 6e399d6a0e..5fc906182c 100644 --- a/doc/Pacemaker_Explained/en-US/Ap-Upgrade.xml +++ b/doc/Pacemaker_Explained/en-US/Ap-Upgrade.xml @@ -1,249 +1,249 @@ Upgrading Cluster Software
Version Compatibility When releasing newer versions we take care to make sure we are backwardly compatible with older versions. While you will always be able to upgrade from version x to x+1, in order to continue to produce high quality software it may occasionally be necessary to drop compatibility with older versions. There will always be an upgrade path from any series-2 release to any other series-2 release. There are three approaches to upgrading your cluster software Complete Cluster Shutdown Rolling (node by node) Disconnect and Reattach Each method has advantages and disadvantages, some of which are listed in the table below, and you should chose the one most appropriate to your needs. Summary of Upgrade Methodologies Type Available between all software versions Service Outage During Upgrade Service Recovery During Upgrade Exercises Failover Logic/Configuration Allows change of cluster stack type For example, switching from Heartbeat to Corosync. Consult the Heartbeat or Corosync documentation to see if upgrading them to a newer version is also supported Shutdown yes always N/A no yes Rolling no always yes yes no Reattach yes only due to failure no no yes
Complete Cluster Shutdown In this scenario one shuts down all cluster nodes and resources and upgrades all the nodes before restarting the cluster.
Procedure On each node: Shutdown the cluster stack (Heartbeat or Corosync) Upgrade the Pacemaker software. - This may also include upgrading the cluster stack and/or the underlying operating system.. + This may also include upgrading the cluster stack and/or the underlying operating system. Check the configuration manually or with the crm_verify tool if available. On each node: Start the cluster stack. This can be either Corosync or Heartbeat and does not need to be the same as the previous cluster stack.
Rolling (node by node) In this scenario each node is removed from the cluster, upgraded and then brought back online until all nodes are running the newest version. This method is currently broken between Pacemaker 0.6.x and 1.0.x Measures have been put into place to ensure rolling upgrades always work for versions after 1.0.0 If there is sufficient demand, the work to repair 0.6 -> 1.0 compatibility will be carried out. Otherwise, please try one of the other upgrade strategies. Detach/Reattach is a particularly good option for most people.
Procedure On each node: Shutdown the cluster stack (Heartbeat or Corosync) Upgrade the Pacemaker software. This may also include upgrading the cluster stack and/or the underlying operating system. On the first node, check the configuration manually or with the crm_verify tool if available. Start the cluster stack. This must be the same type of cluster stack (Corosync or Heartbeat) that the rest of the cluster is using. Upgrading Corosync/Heartbeat may also be possible, please consult the documentation for those projects to see if the two versions will be compatible. Repeat for each node in the cluster
Version Compatibility Version Compatibility Table Version being Installed Oldest Compatible Version Pacemaker 1.0.x Pacemaker 1.0.0 Pacemaker 0.7.x Pacemaker 0.6 or Heartbeat 2.1.3 Pacemaker 0.6.x Heartbeat 2.0.8 Heartbeat 2.1.3 (or less) Heartbeat 2.0.4 Heartbeat 2.0.4 (or less) Heartbeat 2.0.0 Heartbeat 2.0.0 None. Use an alternate upgrade strategy.
Crossing Compatibility Boundaries Rolling upgrades that cross compatibility boundaries must be preformed in multiple steps. For example, to perform a rolling update from Heartbeat 2.0.1 to Pacemaker 0.6.6 one must: Perform a rolling upgrade from Heartbeat 2.0.1 to Heartbeat 2.0.4 Perform a rolling upgrade from Heartbeat 2.0.4 to Heartbeat 2.1.3 Perform a rolling upgrade from Heartbeat 2.1.3 to Pacemaker 0.6.6
Disconnect and Reattach A variant of a complete cluster shutdown, but the resources are left active and re-detected when the cluster is restarted.
Procedure Tell the cluster to stop managing services. This is required to allow the services to remain active after the cluster shuts down. crm_attribute -t crm_config -n is-managed-default -v false For any resource that has a value for is-managed, make sure it is set to false (so that the cluster will not stop it) crm_resource -t primitive -r <rsc_id> -p is-managed -v false On each node: Shutdown the cluster stack (Heartbeat or Corosync) Upgrade the cluster stack program - This may also include upgrading the underlying operating system. Check the configuration manually or with the crm_verify tool if available. On each node: Start the cluster stack. This can be either Corosync or Heartbeat and does not need to be the same as the previous cluster stack. Verify the cluster re-detected all resources correctly Allow the cluster to resume managing resources again crm_attribute -t crm_config -n is-managed-default -v true For any resource that has a value for is-managed reset it to true (so the cluster can recover the service if it fails) if desired crm_resource -t primitive -r <rsc_id> -p is-managed -v false
Notes Always check your existing configuration is still compatible with the version you are installing before starting the cluster. The oldest version of the CRM to support this upgrade type was in Heartbeat 2.0.4
diff --git a/doc/Pacemaker_Explained/en-US/Ch-Advanced-Options.xml b/doc/Pacemaker_Explained/en-US/Ch-Advanced-Options.xml index 66a5988daf..3d5650e002 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Advanced-Options.xml +++ b/doc/Pacemaker_Explained/en-US/Ch-Advanced-Options.xml @@ -1,578 +1,578 @@ Advanced Configuration
Connecting to the Cluster Configuration from a Remote Machine Provided Pacemaker is installed on a machine, it is possible to connect to the cluster even if the machine itself is not a part of it. To do this, one simply sets up a number of environment variables and runs the same commands as you would when working on a cluster node. Environment Variables Used to Connect to Remote Instances of the CIB Environment Variable Description CIB_user The user to connect as. Needs to be part of the hacluster group on the target host. Defaults to $USER CIB_passwd The user's password. Read from the command line if unset CIB_server The host to contact. Defaults to localhost. CIB_port The port on which to contact the server. Required. CIB_encrypted Encrypt network traffic. Defaults to true.
So if c001n01 is an active cluster node and is listening on 1234 for connections, and someguy is a member of the hacluster group. Then the following would prompt for someguy's password and return the cluster's current configuration: export CIB_port=1234; export CIB_server=c001n01; export CIB_user=someguy; cibadmin -Q For security reasons, the cluster does not listen remote connections by default. If you wish to allow remote access, you need to set the remote-tls-port (encrypted) or remote-clear-port (unencrypted) top-level options (ie. those kept in the cib tag , like num_updates and epoch). Extra top-level CIB options for remote access Field Description remote-tls-port Listen for encrypted remote connections on this port. Default: none remote-clear-port Listen for plaintext remote connections on this port. Default: none
Specifying When Recurring Actions are Performed By default, recurring actions are scheduled relative to when the resource started. So if your resource was last started at 14:32 and you have a backup set to be performed every 24 hours, then the backup will always run at in the middle of the business day - hardly desirable. To specify a date/time that the operation should be relative to, set the operation's interval-origin. The cluster uses this point to calculate the correct start-delay such that the operation will occur at origin + (interval * N). So if the operation's interval is 24h, it's interval-origin is set to 02:00 and it is currently 14:32, then the cluster would initiate the operation with a start delay of 11 hours and 28 minutes. If the resource is moved to another node before 2am, then the operation is of course cancelled. The value specified for interval and interval-origin can be any date/time conforming to the ISO8601 standard. By way of example, to specify an operation that would run on the first Monday of 2009 and every Monday after that you would add: Specifying a Base for Recurring Action Intervals <op id="my-weekly-action" name="custom-action" interval="P7D" interval-origin="2009-W01-1"/>
Moving Resources
Manual Intervention There are primarily two occasions when you would want to move a resource from it's current location: when the whole node is under maintenance and when a single resource needs to be moved. In the case where everything needs to move, since everything eventually comes down to a score, you could create constraints for every resource you have preventing it from running on that node. While the configuration can seem convoluted at times, not even we would require this of administrators. Instead one can set a special node attribute which tells the cluster "don't let anything run here". There is even a helpful tool to help query and set it called crm_standby. To check the standby status of the current machine, simply run: crm_standby --get-value A value of true indicates that the node is NOT able to host any resources and a value of false indicates that it CAN. You can also check the status of other nodes in the cluster by specifying the --node-uname option. Eg. crm_standby --get-value --node-uname sles-2 To change the current node's standby status, use --attr-value instead of --get-value. Eg. crm_standby --attr-value Again, you can change another host's value by supplying a host name with --node-uname. When only one resource is required to move, we do this by creating location constraints. However once again we provide a user friendly shortcut as part of the crm_resource command which creates and modifies the extra constraints for you. If Email was running on sles-1 and you wanted it moved to a specific location, the command would look something like: crm_resource -M -r Email -H sles-2 Behind the scenes, the tool will create the following location constraint: <rsc_location rsc="Email" node="sles-2" score="INFINITY"/> It is important to note that subsequent invocations of crm_resource -M are not cumulative. So if you ran: crm_resource -M -r Email -H sles-2 crm_resource -M -r Email -H sles-3 then it is as if you had never performed the first command. To allow the resource to move back again, use: crm_resource -U -r Email Note the use of the word allow. The resource can move back to its original location but, depending on resource stickiness, it may stay where it is. To be absolutely certain that it moves back to sles-1, move it there before issuing the call to crm_resource -U: crm_resource -M -r Email -H sles-1 crm_resource -U -r Email Alternatively, if you only care that the resource should be moved from its current location, try crm_resource -M -r Email Which will instead create a negative constraint. Eg. <rsc_location rsc="Email" node="sles-1" score="-INFINITY"/> This will achieve the desired effect but will also have long-term consequences. As the tool will warn you, the creation of a -INFINITY constraint will prevent the resource from running on that node until crm_resource -U is used. This includes the situation where every other cluster node is no longer available. In some cases, such as when resource stickiness is set to INFINITY, it is possible that you will end up with the problem described in . The tool can detect some of these cases and deals with them by also creating both a positive and negative constraint. Eg. Email prefers sles-1 with a score of -INFINITY Email prefers sles-2 with a score of INFINITY which has the same long-term consequences as discussed earlier.
Moving Resources Due to Failure New in 1.0 is the concept of a migration threshold The naming of this option was unfortunate as it is easily confused with true migration, the process of moving a resource from one node to another without stopping it. Xen virtual guests are the most common example of resources that can be migrated in this manner. . Simply define migration-threshold=N for a resource and it will migrate to a new node after N failures. There is no threshold defined by default. To determine the resource's current failure status and limits, use crm_mon --failcounts By default, once the threshold has been reached, node will no longer be allowed to run the failed resource until the administrator manually resets the resource's failcount using crm_failcount (after hopefully first fixing the failure's cause). However it is possible to expire them by setting the resource's failure-timeout option. So a setting of migration-threshold=2 and failure-timeout=60s would cause the resource to move to a new node after 2 failures and potentially allow it to move back (depending on the stickiness and constraint scores) after one minute. There are two exceptions to the migration threshold concept and occur when a resource either fails to start or fails to stop. Start failures cause the failcount to be set to INFINITY and thus always cause the resource to move immediately. Stop failures are slightly different and crucial. If a resource fails to stop and STONITH is enabled, then the cluster will fence the node in order to be able to start the resource elsewhere. If STONITH is not enabled, then the cluster has no way to continue and will not try to start the resource elsewhere, but will try to stop it again after the failure timeout. Please read before enabling this option.
Moving Resources Due to Connectivity Changes Setting up the cluster to move resources when external connectivity is lost, is a two-step process.
Tell Pacemaker to monitor connectivity To do this, you need to add a ping resource to the cluster. The ping resource uses the system utility of the same name to a test if list of machines (specified by DNS hostname or IPv4/ IPv6 address) are reachable and uses the results to maintain a node attribute normally called pingd. The attribute name is customizable which allows multiple ping groups to be defined Older versions of Heartbeat required users to add ping nodes to ha.cf - this is no longer required. Older versions of Pacemaker used a custom binary called pingd for this functionality, this is now deprecated in favor of ping. If your version of Pacemaker does not contain the ping agent, you can download the latest version from: Normally the resource will run on all cluster nodes, which means that you'll need to create a clone. A template for this can be found below along with a description of the most interesting parameters. Common Options for a 'ping' Resource Field Description dampen The time to wait (dampening) for further changes occur. Use this to prevent a resource from bouncing around the cluster when cluster nodes notice the loss of connectivity at slightly different times. multiplier The number by which to multiply the number of connected ping nodes by. Useful when there are multiple ping nodes configured. host_list The machines to contact in order to determine the current connectivity status. Allowed values include resolvable DNS hostnames, IPv4 and IPv6 addresses.
An example ping cluster resource, checks node connectivity once every minute ]]> You're only half done. The next section deals with telling Pacemaker how to deal with the connectivity status that ocf:pacemaker:ping is recording.
Tell Pacemaker how to interpret the connectivity data NOTE: Before reading the following, please make sure you have read and understood above. There are a number of ways to use the connectivity data provided by Heartbeat. The most common setup is for people to have a single ping node and want to prevent the cluster from running a resource on any unconnected node. Don't run on unconnected nodes ]]> A more complex setup is to have a number of ping nodes configured. You can require the cluster to only run resources on nodes that can connect to all (or a minimum subset) of them Run only on nodes connected to 3 or more ping nodes (assumes <literal>multiplier</literal> is set to 1000) ]]> or instead you can tell the cluster only to prefer nodes with the most connectivity. Just be sure to set the multiplier to a value higher than that of resource-stickiness (and don't set either of them to INFINITY). Prefer the node with the most connected ping nodes ]]> It is perhaps easier to think of this in terms of the simple constraints that the cluster translates it into. For example, if sles-1 is connected to all 5 ping nodes but sles-2 is only connected to 2, then it would be as if you instead had the following constraints in your configuration:
How the cluster translates the pingd constraint ]]>
The advantage being that you don't have to manually update them whenever your network connectivity changes. You can also combine the concepts above into something even more complex. The example below shows how you can prefer the node with the most connected ping nodes provided they have connectivity to at least three (assuming multiplier is set to 1000). A more complex example of choosing a location based on connectivity ]]>
Resource Migration - Some resources, such as Xen virtual guests, are able to move to another location without lose of state. + Some resources, such as Xen virtual guests, are able to move to another location without loss of state. We call this resource migration and is different from the normal practice of stopping the resource on the first machine and starting it elsewhere. - Not all resources are able to migrate, see the Migration Checklist below, and those that can wont do so in all situations. + Not all resources are able to migrate, see the Migration Checklist below, and those that can won't do so in all situations. Conceptually there are two requirements from which the other prerequisites follow: the resource must be active and healthy at the old location everything required for the resource to run must be available on both the old and new locations The cluster is able to accommodate both push and pull migration models by requiring the resource agent to support two new actions: migrate_to (performed on the current location) and migrate_from (performed on the destination). In push migration, the process on the current location transfers the to the new location where is it later activated. In this scenario, most of the work would be done in the migrate_to action and, if anything, the activation would occur during migrate_from. Conversely for pull, the migrate_to action is practically empty and migrate_from does most of the work, extracting the relevant resource state from the old location and activating it. There is no wrong or right way to implement migration for your service, as long as it works.
Migration Checklist The resource may not be a clone. The resource must use an OCF style agent. The resource must not be in a failed or degraded state. The resource must not, directly or indirectly, depend on any primitive or group resources. The resources must support two new actions: migrate_to and migrate_from and advertise them in its metadata. The resource must have the allow-migrate meta-attribute set to true (not the default). If the resource depends on a clone, and at the time the resource needs to be move, the clone has instances that are stopping and instances that are starting, then the resource will be moved in the traditional manner. The Policy Engine is not yet able to model this situation correctly and so takes the safe (yet less optimal) path.
Reusing Rules, Options and Sets of Operations - Sometimes a number of constraints need to use the same set of rules and resources need to set the same options an parameters. + Sometimes a number of constraints need to use the same set of rules and resources need to set the same options and parameters. To simplify this situation, you can refer to an existing object using an id-ref instead of an id. So if for one resource you have ]]> Then instead of duplicating the rule for all your other resources, you can instead specify Referencing rules from other constraints ]]> The cluster will insist that the rule exists somewhere. Attempting to add a reference to a non-existing rule will cause a validation failure, as will attempting to remove a rule that is referenced elsewhere. The same principle applies for meta_attributes and instance_attributes as illustrated in the example below Referencing attributes, options and operations from other resources ]]>
Reloading Services After a Definition Change The cluster automatically detects changes to the definition of services it manages. However, the normal response is to stop the service (using the old definition) and start it again (with the new definition). This works well, but some services are smart and can be told to use a new set of options without restarting. To take advantage of this capability, your resource agent must: Accept the reload operation and perform any required actions. The steps required here depend completely on your application The DRBD Agent's Control logic for Supporting the <literal>reload</literal> Operation Advertise the reload operation in the actions section of its metadata The DRBD Agent Advertising Support for the <literal>reload</literal> Operation 1.1 Master/Slave OCF Resource Agent for DRBD This resource agent manages a DRBD resource as a master/slave resource. DRBD is a shared-nothing replicated storage device. The name of the drbd resource from the drbd.conf file. drbd resource name Full path to the drbd.conf file. Path to drbd.conf ]]> Advertise one or more parameters that can take effect using reload. Any parameter with the unique set to 0 is eligable to be used in this way. Parameter that can be changed using reload Full path to the drbd.conf file. Path to drbd.conf ]]> Once these requirements are satisfied, the cluster will automatically know to reload, instead of restarting, the resource when a non-unique fields changes. The metadata is re-read when the resource is started. This may mean that the resource will be restarted the first time, even though you changed a parameter with unique=0 If both a unique and non-unique field is changed simultaneously, the resource will still be restarted.
diff --git a/doc/Pacemaker_Explained/en-US/Ch-Advanced-Resources.xml b/doc/Pacemaker_Explained/en-US/Ch-Advanced-Resources.xml index 0ed6aee091..d70bfc1f43 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Advanced-Resources.xml +++ b/doc/Pacemaker_Explained/en-US/Ch-Advanced-Resources.xml @@ -1,897 +1,897 @@ Advanced Resource Types
Groups - A Syntactic Shortcut One of the most common elements of a cluster is a set of resources that need to be located together, start sequentially and stop in the reverse order. To simplify this configuration we support the concept of groups. An example group ]]> Although the example above contains only two resources, there is no limit to the number of resources a group can contain. The example is also sufficient to explain the fundamental properties of a group: Resources are started in the order they appear in (Public-IP first, then Email) Resources are stopped in the reverse order to which they appear in (Email first, then Public-IP) If a resource in the group can't run anywhere, then nothing after that is allowed to run If Public-IP can’t run anywhere, neither can Email If Email can’t run anywhere, this does not affect Public-IP in any way The group above is logically equivalent to writing: How the cluster sees a group resource ]]> Obviously as the group grows bigger, the reduced configuration effort can become significant.
Properties Properties of a Group Resource Field Description id Your name for the group
Options Options inherited from simple resources: priority, target-role, is-managed
Using Groups
Instance Attributes Groups have no instance attributes, however any that are set here will be inherited by the group's children.
Contents Groups may only contain a collection of primitive cluster resources. To refer to the child of a group resource, just use the child's id instead of the group's.
Constraints Although it is possible to reference the group's children in constraints, it is usually preferable to use the group's name instead. Example constraints involving groups ]]>
Stickiness Stickiness, the measure of how much a resource wants to stay where it is, is additive in groups. Every active member of the group will contribute its stickiness value to the group's total. So if the default resource-stickiness is 100 a group has seven members, five of which are active, then the group as a whole will prefer its current location with a score of 500.
Clones - Resources That Should be Active on Multiple Hosts Clones were initially conceived as a convenient way to start N instances of an IP resource and have them distributed throughout the cluster for load balancing. They have turned out to quite useful for a number of purposes including integrating with Red Hat's DLM, the fencing subsystem and OCFS2. You can clone any resource provided the resource agent supports it. Three types of cloned resources exist. Anonymous Globally Unique Stateful Anonymous clones are the simplest type. These resources behave completely identically everywhere they are running. Because of this, there can only be one copy of an anonymous clone active per machine. Globally unique clones are distinct entities. A copy of the clone running on one machine is not equivalent to another instance on another node. Nor would any two copies on the same node be equivalent. Stateful clones are covered later in . An example clone ]]>
Properties Properties of a Clone Resource Field Description id Your name for the clone
Options Options inherited from simple resources: priority, target-role, is-managed Clone specific configuration options Field Description clone-max How many copies of the resource to start. Defaults to the number of nodes in the cluster. clone-node-max How many copies of the resource can be started on a single node. Defaults to 1. notify When stopping or starting a copy of the clone, tell all the other copies beforehand and when the action was successful. Allowed values: true, false globally-unique Does each copy of the clone perform a different function? Allowed values: true, false ordered Should the copies be started in series (instead of in parallel). Allowed values: true, false interleave Changes the behavior of ordering constraints (between clones/masters) so that instances can start/stop as soon as their peer instance has (rather than waiting for every instance of the other clone has). Allowed values: true, false
Using Clones
Instance Attributes Clones have no instance attributes, however any that are set here will be inherited by the clone's children.
Contents Clones must contain exactly one group or one regular resource. You should never reference the name of a clone's child. If you think you need to do this, you probably need to re-evaluate your design.
Constraints In most cases, a clone will have a single copy on each active cluster node. However if this is not the case, you can indicate which nodes the cluster should to preferentially assign copies to with resource location constraints. These constraints are written no differently to those for regular resources except that the clone's id is used. Ordering constraints behave slightly differently for clones. In the example below, apache-stats will wait until all copies of the clone that need to be started have done so before being started itself. Only if no copies can be started will apache-stats be prevented from being active. Additionally, the clone will wait for apache-stats to be stopped before stopping the clone. Colocation of a regular (or group) resource with a clone means that the resource can run on any machine with an active copy of the clone. The cluster will choose a copy based on where the clone is running and the rsc resource's own location preferences. Colocation between clones is also possible. In such cases, the set of allowed locations for the rsc clone is limited to nodes on which the with clone is (or will be) active. Allocation is then performed as-per-normal. Example constraints involving clones ]]>
Stickiness To achieve a stable allocation pattern, clones are slightly sticky by default. If no value for resource-stickiness is provided, the clone will use a value of 1. Being a small value, it causes minimal disturbance to the score calculations of other resources but is enough to prevent Pacemaker from needlessly moving copies around the cluster.
Resource Agent Requirements Any resource can be used as an anonymous clone as it requires no additional support from the resource agent. Whether it makes sense to do so depends on your resource and its resource agent. Globally unique clones do require some additional support in the resource agent. In particular, it must only respond with ${OCF_SUCCESS} if the node has that exact instance active. All other probes for instances of the clone should result in ${OCF_NOT_RUNNING}. Unless of course they are failed, in which case they should return one of the other OCF error codes. Copies of a clone are identified by appending a colon and a numerical offset. Eg. apache:2 Resource agents can find out how many copies there are by examining the OCF_RESKEY_CRM_meta_clone_max environment variable and which copy it is by examining OCF_RESKEY_CRM_meta_clone. You should not make any assumptions (based on OCF_RESKEY_CRM_meta_clone) about which copies are active. In particular, the list of active copies will not always be an unbroken sequence, nor always start at 0.
Notifications Supporting notifications requires the notify action to be implemented. Once supported, the notify action will be passed a number of extra variables which, when combined with additional context, can be used to calculate the current state of the cluster and what is about to happen to it. Environment variables supplied with Clone notify actions Variable Description OCF_RESKEY_CRM_meta_notify_type Allowed values: pre, post OCF_RESKEY_CRM_meta_notify_operation Allowed values: start, stop OCF_RESKEY_CRM_meta_notify_start_resource Resources to be started OCF_RESKEY_CRM_meta_notify_stop_resource Resources to be stopped OCF_RESKEY_CRM_meta_notify_active_resource Resources the that are running OCF_RESKEY_CRM_meta_notify_inactive_resource Resources the that are not running OCF_RESKEY_CRM_meta_notify_start_uname Nodes on which resources will be started OCF_RESKEY_CRM_meta_notify_stop_uname Nodes on which resources will be stopped OCF_RESKEY_CRM_meta_notify_active_uname Nodes on which resources are running OCF_RESKEY_CRM_meta_notify_inactive_uname Nodes on which resources are not running
The variables come in pairs, such as OCF_RESKEY_CRM_meta_notify_start_resource and OCF_RESKEY_CRM_meta_notify_start_uname and should be treated as an array of whitespace separated elements. Thus in order to indicate that clone:0 will be started on sles-1, clone:2 will be started on sles-3, and clone:3 will be started on sles-2, the cluster would set OCF_RESKEY_CRM_meta_notify_start_resource="clone:0 clone:2 clone:3" OCF_RESKEY_CRM_meta_notify_start_uname="sles-1 sles-3 sles-2" Example notification variables
Proper Interpretation of Notification Environment Variables Pre-notification (stop) Active resources: $OCF_RESKEY_CRM_meta_notify_active_resource Inactive resources: $OCF_RESKEY_CRM_meta_notify_inactive_resource Resources to be started: $OCF_RESKEY_CRM_meta_notify_start_resource Resources to be stopped: $OCF_RESKEY_CRM_meta_notify_stop_resource Post-notification (stop) / Pre-notification (start) Active resources: $OCF_RESKEY_CRM_meta_notify_active_resource minus $OCF_RESKEY_CRM_meta_notify_stop_resource Inactive resources: $OCF_RESKEY_CRM_meta_notify_inactive_resource plus $OCF_RESKEY_CRM_meta_notify_stop_resource Resources that were started: $OCF_RESKEY_CRM_meta_notify_start_resource Resources that were stopped: $OCF_RESKEY_CRM_meta_notify_stop_resource Post-notification (start) Active resources: $OCF_RESKEY_CRM_meta_notify_active_resource minus $OCF_RESKEY_CRM_meta_notify_stop_resource plus $OCF_RESKEY_CRM_meta_notify_start_resource Inactive resources: $OCF_RESKEY_CRM_meta_notify_inactive_resource plus $OCF_RESKEY_CRM_meta_notify_stop_resource minus $OCF_RESKEY_CRM_meta_notify_start_resource Resources that were started: $OCF_RESKEY_CRM_meta_notify_start_resource Resources that were stopped: $OCF_RESKEY_CRM_meta_notify_stop_resource
Multi-state - Resources That Have Multiple Modes Multi-state resources are a specialization of Clones (please ensure you understand the section on clones before continuing) that allow the instances to be in one of two operating modes. These modes are called Master and Slave but can mean whatever you wish them to mean. The only limitation is that when an instance is started, it must come up in the Slave state.
Properties Properties of a Multi-State Resource Field Description id Your name for the multi-state resource
Options Options inherited from simple resources: priority, target-role, is-managed Options inherited from clone resources: clone-max, clone-node-max, notify, globally-unique, ordered, interleave Multi-state specific resource configuration options Field Description master-max How many copies of the resource can be promoted to master status. Defaults to 1. master-node-max How many copies of the resource can be promoted to master status on a single node. Defaults to 1.
Using Multi-state Resources
Instance Attributes Multi-state resources have no instance attributes, however any that are set here will be inherited by the master's children.
Contents Masters must contain exactly one group or one regular resource. You should never reference the name of a master's child. If you think you need to do this, you probably need to re-evaluate your design.
Monitoring Multi-State Resources The normal type of monitor actions you define are not sufficient to monitor a multi-state resource in the Master state. To detect failures of the master instance, you need to define an additional monitor action with role="Master". It is crucial that every monitor operation has a different interval Monitoring both states of a multi-state resource ]]>
Constraints In most cases, a multi-state resources will have a single copy on each active cluster node. However if this is not the case, you can indicate which nodes the cluster should to preferentially assign copies to with resource location constraints. These constraints are written no differently to those for regular resources except that the master's id is used. When considering multi-state resources in constraints, for most purposes it is sufficient to treat them as clones. The exception is when the rsc-role and/or with-rsc-role (for colocation constraints) and first-action and/or then-action (for ordering constraints) are used. Additional constraint options relevant to multi-state resources Field Description rsc-role An additional attribute of colocation constraints that specifies the role that rsc must be in. Allowed values: Started, Master, Slave with-rsc-role An additional attribute of colocation constraints that specifies the role that with-rsc must be in. Allowed values: Started, Master, Slave first-action An additional attribute of ordering constraints that specifies the action that the first resource must complete before executing the specified action for the then resource. Allowed values: start, stop, promote, demote then-action An additional attribute of ordering constraints that specifies the action that the then resource can only execute after the first-action on the first resource has completed. Allowed values: start, stop, promote, demote. Defaults to the value (specified or implied) of first-action
- In the example below, myApp will wait until one of database copies has been started and promoted to master before being started itself. + In the example below, myApp will wait until one of the database copies has been started and promoted to master before being started itself. Only if no copies can be promoted will apache-stats be prevented from being active. Additionally, the database will wait for myApp to be stopped before it is demoted. Colocation of a regular (or group) resource with a multi-state resource means that it can run on any machine with an active copy of the clone that is in the specified state (Master or Slave). In the example, the cluster will choose a location based on where database is running as a Master, and if there are multiple Master instances it will also factor in myApp‘s own location preferences when deciding which location to choose. Colocation with regular clones and other multi-state resources is also possible. In such cases, the set of allowed locations for the rsc clone is (after role filtering) limited to nodes on which the with-rsc clone is (or will be) in the specified role. Allocation is then performed as-per-normal. Example constraints involving multi-state resources ]]>
Stickiness To achieve a stable allocation pattern, clones are slightly sticky by default. If no value for resource-stickiness is provided, the clone will use a value of 1. Being a small value, it causes minimal disturbance to the score calculations of other resources but is enough to prevent Pacemaker from needlessly moving copies around the cluster.
Which Resource Instance is Promoted During the start operation, most Resource Agent scripts should call the crm_master utility. This tool automatically detects both the resource and host and should be used to set a preference for being promoted. Based on this, master-max, and master-node-max, the instance(s) with the highest preference will be promoted. The other alternative is to create a location constraint that indicates which nodes are most preferred as masters. Manually specifying which node should be promoted ]]>
Resource Agent Requirements Since multi-state resources are an extension of cloned resources, all the requirements of Clones are also requirements of multi-state resources. Additionally, multi-state resources require two extra actions demote and promote. These actions are responsible for changing the state of the resource. Like start and stop, they should return OCF_SUCCESS if they completed successfully or a relevant error code if they did not. The states can mean whatever you wish, but when the resource is started, it must come up in the mode called Slave. From there the cluster will then decide which instances to promote into a Master. In addition to the Clone requirements for monitor actions, agents must also accurately report which state they are in. The cluster relies on the agent to report its status (including role) accurately and does not indicate to the agent what role it currently believes it to be in. Role implications of OCF return codes Monitor Return Code Description OCF_NOT_RUNNING Stopped OCF_SUCCESS Running (Slave) OCF_RUNNING_MASTER Running (Master) OCF_FAILED_MASTER Failed (Master) Other Failed (Slave)
Notifications Like with clones, supporting notifications requires the notify action to be implemented. Once supported, the notify action will be passed a number of extra variables which, when combined with additional context, can be used to calculate the current state of the cluster and what is about to happen to it. Environment variables supplied with Master notify actions <footnote><para>Variables in bold are specific to Master resources and all behave in the same manner as described for Clone resources.</para></footnote> Variable Description OCF_RESKEY_CRM_meta_notify_type Allowed values: pre, post OCF_RESKEY_CRM_meta_notify_operation Allowed values: start, stop OCF_RESKEY_CRM_meta_notify_active_resource Resources the that are running OCF_RESKEY_CRM_meta_notify_inactive_resource Resources the that are not running OCF_RESKEY_CRM_meta_notify_master_resource Resources that are running in Master mode OCF_RESKEY_CRM_meta_notify_slave_resource Resources that are running in Slave mode OCF_RESKEY_CRM_meta_notify_start_resource Resources to be started OCF_RESKEY_CRM_meta_notify_stop_resource Resources to be stopped OCF_RESKEY_CRM_meta_notify_promote_resource Resources to be promoted OCF_RESKEY_CRM_meta_notify_demote_resource Resources to be demoted OCF_RESKEY_CRM_meta_notify_start_uname Nodes on which resources will be started OCF_RESKEY_CRM_meta_notify_stop_uname Nodes on which resources will be stopped OCF_RESKEY_CRM_meta_notify_promote_uname Nodes on which resources will be promoted OCF_RESKEY_CRM_meta_notify_demote_uname Nodes on which resources will be demoted OCF_RESKEY_CRM_meta_notify_active_uname Nodes on which resources are running OCF_RESKEY_CRM_meta_notify_inactive_uname Nodes on which resources are not running OCF_RESKEY_CRM_meta_notify_master_uname Nodes on which resources are running in Master mode OCF_RESKEY_CRM_meta_notify_slave_uname Nodes on which resources are running in Slave mode
Proper Interpretation of Notification Environment Variables Pre-notification (demote) Active resources: $OCF_RESKEY_CRM_meta_notify_active_resource Master resources: $OCF_RESKEY_CRM_meta_notify_master_resource Slave resources: $OCF_RESKEY_CRM_meta_notify_slave_resource Inactive resources: $OCF_RESKEY_CRM_meta_notify_inactive_resource Resources to be started: $OCF_RESKEY_CRM_meta_notify_start_resource Resources to be promoted: $OCF_RESKEY_CRM_meta_notify_promote_resource Resources to be demoted: $OCF_RESKEY_CRM_meta_notify_demote_resource Resources to be stopped: $OCF_RESKEY_CRM_meta_notify_stop_resource Post-notification (demote) / Pre-notification (stop) Active resources: $OCF_RESKEY_CRM_meta_notify_active_resource Master resources: $OCF_RESKEY_CRM_meta_notify_master_resource minus $OCF_RESKEY_CRM_meta_notify_demote_resource Slave resources: $OCF_RESKEY_CRM_meta_notify_slave_resource Inactive resources: $OCF_RESKEY_CRM_meta_notify_inactive_resource Resources to be started: $OCF_RESKEY_CRM_meta_notify_start_resource Resources to be promoted: $OCF_RESKEY_CRM_meta_notify_promote_resource Resources to be demoted: $OCF_RESKEY_CRM_meta_notify_demote_resource Resources to be stopped: $OCF_RESKEY_CRM_meta_notify_stop_resource Resources that were demoted: $OCF_RESKEY_CRM_meta_notify_demote_resource Post-notification (stop) / Pre-notification (start) Active resources: $OCF_RESKEY_CRM_meta_notify_active_resource minus $OCF_RESKEY_CRM_meta_notify_stop_resource Master resources: $OCF_RESKEY_CRM_meta_notify_master_resource minus $OCF_RESKEY_CRM_meta_notify_demote_resource Slave resources: $OCF_RESKEY_CRM_meta_notify_slave_resource minus $OCF_RESKEY_CRM_meta_notify_stop_resource Inactive resources: $OCF_RESKEY_CRM_meta_notify_inactive_resource plus $OCF_RESKEY_CRM_meta_notify_stop_resource Resources to be started: $OCF_RESKEY_CRM_meta_notify_start_resource Resources to be promoted: $OCF_RESKEY_CRM_meta_notify_promote_resource Resources to be demoted: $OCF_RESKEY_CRM_meta_notify_demote_resource Resources to be stopped: $OCF_RESKEY_CRM_meta_notify_stop_resource Resources that were demoted: $OCF_RESKEY_CRM_meta_notify_demote_resource Resources that were stopped: $OCF_RESKEY_CRM_meta_notify_stop_resource Post-notification (start) / Pre-notification (promote) Active resources: $OCF_RESKEY_CRM_meta_notify_active_resource minus $OCF_RESKEY_CRM_meta_notify_stop_resource plus $OCF_RESKEY_CRM_meta_notify_start_resource Master resources: $OCF_RESKEY_CRM_meta_notify_master_resource minus $OCF_RESKEY_CRM_meta_notify_demote_resource Slave resources: $OCF_RESKEY_CRM_meta_notify_slave_resource minus $OCF_RESKEY_CRM_meta_notify_stop_resource plus $OCF_RESKEY_CRM_meta_notify_start_resource Inactive resources: $OCF_RESKEY_CRM_meta_notify_inactive_resource plus $OCF_RESKEY_CRM_meta_notify_stop_resource minus $OCF_RESKEY_CRM_meta_notify_start_resource Resources to be started: $OCF_RESKEY_CRM_meta_notify_start_resource Resources to be promoted: $OCF_RESKEY_CRM_meta_notify_promote_resource Resources to be demoted: $OCF_RESKEY_CRM_meta_notify_demote_resource Resources to be stopped: $OCF_RESKEY_CRM_meta_notify_stop_resource Resources that were started: $OCF_RESKEY_CRM_meta_notify_start_resource Resources that were demoted: $OCF_RESKEY_CRM_meta_notify_demote_resource Resources that were stopped: $OCF_RESKEY_CRM_meta_notify_stop_resource Post-notification (promote) Active resources: $OCF_RESKEY_CRM_meta_notify_active_resource minus $OCF_RESKEY_CRM_meta_notify_stop_resource plus $OCF_RESKEY_CRM_meta_notify_start_resource Master resources: $OCF_RESKEY_CRM_meta_notify_master_resource minus $OCF_RESKEY_CRM_meta_notify_demote_resource plus $OCF_RESKEY_CRM_meta_notify_promote_resource Slave resources: $OCF_RESKEY_CRM_meta_notify_slave_resource minus $OCF_RESKEY_CRM_meta_notify_stop_resource plus $OCF_RESKEY_CRM_meta_notify_start_resource minus $OCF_RESKEY_CRM_meta_notify_promote_resource Inactive resources: $OCF_RESKEY_CRM_meta_notify_inactive_resource plus $OCF_RESKEY_CRM_meta_notify_stop_resource minus $OCF_RESKEY_CRM_meta_notify_start_resource Resources to be started: $OCF_RESKEY_CRM_meta_notify_start_resource Resources to be promoted: $OCF_RESKEY_CRM_meta_notify_promote_resource Resources to be demoted: $OCF_RESKEY_CRM_meta_notify_demote_resource Resources to be stopped: $OCF_RESKEY_CRM_meta_notify_stop_resource Resources that were started: $OCF_RESKEY_CRM_meta_notify_start_resource Resources that were promoted: $OCF_RESKEY_CRM_meta_notify_promote_resource Resources that were demoted: $OCF_RESKEY_CRM_meta_notify_demote_resource Resources that were stopped: $OCF_RESKEY_CRM_meta_notify_stop_resource
diff --git a/doc/Pacemaker_Explained/en-US/Ch-Basics.xml b/doc/Pacemaker_Explained/en-US/Ch-Basics.xml index 5132cdc220..12a5680d3b 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Basics.xml +++ b/doc/Pacemaker_Explained/en-US/Ch-Basics.xml @@ -1,308 +1,308 @@ Configuration Basics
Configuration Layout - The cluster is written using XML notation and divided into two main sections; configuration and status. + The cluster is written using XML notation and divided into two main sections: configuration and status. The status section contains the history of each resource on each node and based on this data, the cluster can construct the complete current state of the cluster. The authoritative source for the status section is the local resource manager (lrmd) process on each cluster node and the cluster will occasionally repopulate the entire section. For this reason it is never written to disk and admin's are advised against modifying it in any way. The configuration section contains the more traditional information like cluster options, lists of resources and indications of where they should be placed. The configuration section is the primary focus of this document. The configuration section itself is divided into four parts: Configuration options (called crm_config) Nodes Resources Resource relationships (called constraints) An empty configuration ]]>
The Current State of the Cluster Before one starts to configure a cluster, it is worth explaining how to view the finished product. For this purpose we have created the crm_mon utility that will display the current state of an active cluster. It can show the cluster status by node or by resource and can be used in either single-shot or dynamically-updating mode. There are also modes for displaying a list of the operations performed (grouped by node and resource) as well as information about failures. Using this tool, you can examine the state of the cluster for irregularities and see how it responds when you cause or simulate failures. Details on all the available options can be obtained using the crm_mon --help command.
Sample output from crm_mon # crm_mon ============ Last updated: Fri Nov 23 15:26:13 2007 Current DC: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec) 3 Nodes configured. 5 Resources configured. ============ Node: sles-1 (1186dc9a-324d-425a-966e-d757e693dc86): online 192.168.100.181 (heartbeat::ocf:IPaddr): Started sles-1 192.168.100.182 (heartbeat:IPaddr): Started sles-1 192.168.100.183 (heartbeat::ocf:IPaddr): Started sles-1 rsc_sles-1 (heartbeat::ocf:IPaddr): Started sles-1 child_DoFencing:2 (stonith:external/vmware): Started sles-1 Node: sles-2 (02fb99a8-e30e-482f-b3ad-0fb3ce27d088): standby Node: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec): online rsc_sles-2 (heartbeat::ocf:IPaddr): Started sles-3 rsc_sles-3 (heartbeat::ocf:IPaddr): Started sles-3 child_DoFencing:0 (stonith:external/vmware): Started sles-3
Sample output from crm_mon -n # crm_mon -n ============ Last updated: Fri Nov 23 15:26:13 2007 Current DC: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec) 3 Nodes configured. 5 Resources configured. ============ Node: sles-1 (1186dc9a-324d-425a-966e-d757e693dc86): online Node: sles-2 (02fb99a8-e30e-482f-b3ad-0fb3ce27d088): standby Node: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec): online Resource Group: group-1 192.168.100.181 (heartbeat::ocf:IPaddr): Started sles-1 192.168.100.182 (heartbeat:IPaddr): Started sles-1 192.168.100.183 (heartbeat::ocf:IPaddr): Started sles-1 rsc_sles-1 (heartbeat::ocf:IPaddr): Started sles-1 rsc_sles-2 (heartbeat::ocf:IPaddr): Started sles-3 rsc_sles-3 (heartbeat::ocf:IPaddr): Started sles-3 Clone Set: DoFencing child_DoFencing:0 (stonith:external/vmware): Started sles-3 child_DoFencing:1 (stonith:external/vmware): Stopped child_DoFencing:2 (stonith:external/vmware): Started sles-1
The DC (Designated Controller) node is where all the decisions are made and if the current DC fails a new one is elected from the remaining cluster nodes. The choice of DC is of no significance to an administrator beyond the fact that its logs will generally be more interesting.
How Should the Configuration be Updated? There are three basic rules for updating the cluster configuration: Rule 1 - Never edit the cib.xml file manually. Ever. I'm not making this up. Rule 2 - Read Rule 1 again. Rule 3 - The cluster will notice if you ignored rules 1 & 2 and refuse to use the configuration. Now that it is clear how NOT to update the configuration, we can begin to explain how you should. The most powerful tool for modifying the configuration is the cibadmin command which talks to a running cluster. With cibadmin, the user can query, add, remove, update or replace any part of the configuration and all changes take effect immediately so there is no need to perform a reload-like operation. The simplest way of using cibadmin is to use it to save the current configuration to a temporary file, edit that file with your favorite text or XML editor and then upload the revised configuration.
Safely using an editor to modify the cluster configuration cibadmin --query > tmp.xml vi tmp.xml cibadmin --replace --xml-file tmp.xml
Some of the better XML editors can make use of a Relax NG schema to help make sure any changes you make are valid. The schema describing the configuration can normally be found in /usr/lib/heartbeat/pacemaker.rng on most systems. If you only wanted to modify the resources section, you could instead do
Safely using an editor to modify a subsection of the cluster configuration cibadmin --query --obj_type resources > tmp.xml vi tmp.xml cibadmin --replace --obj_type resources --xml-file tmp.xml
to avoid modifying any other part of the configuration.
Quickly Deleting Part of the Configuration Identify the object you wish to delete. eg. - Next identify the resource's tag name and id (in this case we'll chose primitive and child_DoFencing). + Next identify the resource's tag name and id (in this case we'll choose primitive and child_DoFencing). Then simply execute: cibadmin --delete --crm_xml ‘<primitive id="child_DoFencing"/>'
Updating the Configuration Without Using XML Some common tasks can also be performed with one of the higher level tools that avoid the need to read or edit XML. To enable stonith for example, one could run: crm_attribute --attr-name stonith-enabled --attr-value true Or to see if somenode is allowed to run resources, there is: crm_standby --get-value --node-uname somenode Or to find the current location of my-test-rsc one can use: crm_resource --locate --resource my-test-rsc
Making Configuration Changes in a Sandbox Often it is desirable to preview the effects of a series of changes before updating the configuration atomically. For this purpose we have created crm_shadow which creates a "shadow" copy of the configuration and arranges for all the command line tools to use it. To begin, simply invoke crm_shadow and give it the name of a configuration to create Shadow copies are identified with a name, making it possible to have more than one and be sure to follow the simple on-screen instructions. Read the above carefully, failure to do so could result in you destroying the cluster's active configuration
Creating and displaying the active sandbox # crm_shadow --create test Setting up shadow instance Type Ctrl-D to exit the crm_shadow shell shadow[test]: shadow[test] # crm_shadow --which test
From this point on, all cluster commands will automatically use the shadow copy instead of talking to the cluster's active configuration. Once you have finished experimenting, you can either commit the changes, or discard them as shown below. Again, be sure to follow the on-screen instructions carefully. For a full list of crm_shadow options and commands, invoke it with the --help option. Using a sandbox to make multiple changes atomically shadow[test] # crm_failcount -G -r rsc_c001n01 name=fail-count-rsc_c001n01 value=0 shadow[test] # crm_standby -v on -n c001n02 shadow[test] # crm_standby -G -n c001n02 name=c001n02 scope=nodes value=on shadow[test] # cibadmin --erase --force shadow[test] # cibadmin --query ]]> shadow[test] # crm_shadow --delete test --force Now type Ctrl-D to exit the crm_shadow shell shadow[test] # exit # crm_shadow --which No shadow instance provided # cibadmin -Q ]]> Making changes in a sandbox and verifying the real configuration is untouched
Testing Your Configuration Changes We saw previously how to make a series of changes to a "shadow" copy of the configuration. Before loading the changes back into the cluster (eg. crm_shadow --commit mytest --force), it is often advisable to simulate the effect of the changes with ptest. Eg. ptest --live-check -VVVVV --save-graph tmp.graph --save-dotfile tmp.dot The tool uses the same library as the live cluster to show what it would have done given the supplied input. It's output, in addition to a significant amount of logging, is stored in two files tmp.graph and tmp.dot, both are representations of the same thing -- the cluster's response to your changes. In the graph file is stored the complete transition, containing a list of all the actions, their parameters and their pre-requisites. Because the transition graph is not terribly easy to read, the tool also generates a Graphviz dot-file representing the same information.
Small Cluster Transition An example transition graph as represented by Graphviz
Interpreting the Graphviz output Arrows indicate ordering dependencies Dashed-arrows indicate dependencies that are not present in the transition graph Actions with a dashed border of any color do not form part of the transition graph Actions with a green border form part of the transition graph Actions with a red border are ones the cluster would like to execute but are unrunnable Actions with a blue border are ones the cluster does not feel need to be executed Actions with orange text are pseudo/pretend actions that the cluster uses to simplify the graph Actions with black text are sent to the LRM Resource actions have text of the form rsc_action_interval node Any action depending on an action with a red border will not be able to execute. Loops are really bad. Please report them to the development team. In the above example, it appears that a new node, node2, has come online and that the cluster is checking to make sure rsc1, rsc2 and rsc3 are not already running there (Indicated by the *_monitor_0 entries). Once it did that, and assuming the resources were not active there, it would have liked to stop rsc1 and rsc2 on node1 and move them to node2. However, there appears to be some problem and the cluster cannot or is not permitted to perform the stop actions which implies it also cannot perform the start actions. For some reason the cluster does not want to start rsc3 anywhere. For information on the options supported by ptest, use ptest --help
Complex Cluster Transition Another, slightly more complex, transition graph that you're not expected to be able to read
Do I Need to Update the Configuration on all Cluster Nodes? No. Any changes are immediately synchronized to the other active members of the cluster. To reduce bandwidth, the cluster only broadcasts the incremental updates that result from your changes and uses MD5 sums to ensure that each copy is completely consistent.
diff --git a/doc/Pacemaker_Explained/en-US/Ch-Constraints.xml b/doc/Pacemaker_Explained/en-US/Ch-Constraints.xml index e042354012..ebf3552135 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Constraints.xml +++ b/doc/Pacemaker_Explained/en-US/Ch-Constraints.xml @@ -1,547 +1,547 @@ Resource Constraints
Scores Scores of all kinds are integral to how the cluster works. Practically everything from moving a resource to deciding which resource to stop in a degraded cluster is achieved by manipulating scores in some way. Scores are calculated on a per-resource basis and any node with a negative score for a resource can't run that resource. After calculating the scores for a resource, the cluster then chooses the node with the highest one.
Infinity Math INFINITY is currently defined as 1,000,000 and addition/subtraction with it follows the following 3 basic rules: Any value + INFINITY = INFINITY Any value - INFINITY = -INFINITY INFINITY - INFINITY = -INFINITY
Deciding Which Nodes a Resource Can Run On There are two alternative strategies for specifying which nodes a resources can run on. One way is to say that by default they can run anywhere and then create location constraints for nodes that are not allowed. The other option is to have nodes "opt-in"... to start with nothing able to run anywhere and selectively enable allowed nodes.
Options Options for Simple Location Constraints Field Description id A unique name for the constraint rsc A resource name node A node's uname score Positive values indicate the resource can run on this node. Negative values indicate the resource can not run on this node. Values of +/- INFINITY change "can" to "must".
Asymmetrical "Opt-In" Clusters To create an opt-in cluster, start by preventing resources from running anywhere by default crm_attribute --attr-name symmetric-cluster --attr-value false Then start enabling nodes. The following fragment says that the web server prefers sles-1, the database prefers sles-2 and both can failover to sles-3 if their most preferred node fails. Example set of opt-in location constraints ]]>
Symmetrical "Opt-Out" Clusters To create an opt-out cluster, start by allowing resources to run anywhere by default crm_attribute --attr-name symmetric-cluster --attr-value true Then start disabling nodes. The following fragment is the equivalent of the above opt-in configuration. Example set of opt-out location constraints ]]> Whether you should choose opt-in or opt-out depends both on your personal preference and the make-up of your cluster. If most of your resources can run on most of the nodes, then an opt-out arrangement is likely to result in a simpler configuration. On the other-hand, if most resources can only run on a small subset of nodes an opt-in configuration might be simpler.
What if Two Nodes Have the Same Score If two nodes have the same score, then the cluster will choose one. This choice may seem random and may not be what was intended, however the cluster was not given enough information to know what was intended. Example of two resources that prefer two nodes equally ]]> In the example above, assuming no other constraints and an inactive cluster, Webserver would probably be placed on sles-1 and Database on sles-2. It would likely have placed Webserver based on the node's uname and Database based on the desire to spread the resource load evenly across the cluster. However other factors can also be involved in more complex configurations.
Specifying the Order Resources Should Start/Stop In The way to specify the order in which resources should start is by creating rsc_order constraints. Properties of an Ordering Constraint Field Description id A unique name for the constraint first The name of a resource that must be started before the then resource is allowed to. then The name of a resource. This resource will start after the first resource. score If greater than zero, the constraint is mandatory. Otherwise it is only a suggestion. Default value: INFINITY symmetrical If true, which is the default, stop the resources in the reverse order. Default value: true
Mandatory Ordering When the then resource cannot run without the first resource being active, one should use mandatory constraints. To specify a constraint is mandatory, use a scores greater than zero. This will ensure that the then resource will react when the first resource changes state. If the first resource was running and is stopped, the then resource will also be stopped (if it is running) If the first resource was not running and cannot be started, the then resource will be stopped (if it is running) If the first resource is (re)started while the then resource is running, the then resource will be stopped and restarted
Advisory Ordering On the other-hand, when score="0" is specified for a constraint, the constraint is considered optional and only has an effect when both resources are stopping and or starting. Any change in state by the first resource will have no effect on the then resource. Example of an optional and mandatory ordering constraint ]]> Some additional information on ordering constraints can be found in the document Ordering Explained
Placing Resources Relative to other Resources When the location of one resource depends on the location of another one, we call this colocation. There is an important side-effect of creating a colocation constraint between two resources, that it affects the order in which resources are assigned to a node. If you think about it, its somewhat obvious. You can't place A relative to B unless you know where B is While the human brain is sophisticated enough to read the constraint in any order and choose the correct one depending on the situation, the cluster is not quite so smart. Yet. . So when you are creating colocation constraints, it is important to consider whether you should colocate A with B or B with A. Another thing to keep in mind is that, assuming A is collocated with B, the cluster will also take into account A's preferences when deciding which node to choose for B. For a detailed look at exactly how this occurs, see the Colocation Explained document.
Options Properties of a Collocation Constraint Field Description id A unique name for the constraint rsc The colocation source. If the constraint cannot be satisfied, the cluster may decide not to allow the resource to run at all. with-rsc The colocation target. The cluster will decide where to put this resource first and then decide where to put the resource in the rsc field score Positive values indicate the resource should run on the same node. Negative values indicate the resources should not run on the same node. Values of +/- INFINITY change "should" to "must".
Mandatory Placement Mandatory placement occurs any time the constraint's score is +INFINITY or -INFINITY. In such cases, if the constraint can't be satisfied, then the rsc resource is not permitted to run. For score=INFINITY, this includes cases where the with-rsc resource is not active. If you need resource1 to always run on the same machine as resource2, you would add the following constraint: An example colocation constraint <rsc_colocation id="colocate" rsc="resource1" with-rsc="resource2" score="INFINITY"/> Remember, because INFINITY was used, if resource2 can't run on any of the cluster nodes (for whatever reason) then resource1 will not be allowed to run. Alternatively, you may want the opposite... that resource1 cannot run on the same machine as resource2. In this case use score="-INFINITY" An example anti-colocation constraint <rsc_colocation id="anti-colocate" rsc="resource1" with-rsc="resource2" score="-INFINITY"/> Again, by specifying -INFINTY, the constraint is binding. So if the only place left to run is where resource2 already is, then resource1 may not run anywhere.
Advisory Placement If mandatory placement is about "must" and "must not", then advisory placement is the "I'd prefer if" alternative. For constraints with scores greater than -INFINITY and less than INFINITY, the cluster will try and accommodate your wishes but may ignore them if the alternative is to stop some of the cluster resources. Like in life, where if enough people prefer something it effectively becomes mandatory, advisory colocation constraints can combine with other elements of the configuration to behave as if they were mandatory. An example advisory-only colocation constraint <rsc_colocation id="colocate-maybe" rsc="resource1" with-rsc="resource2" score="500"/>
Ordering Sets of Resources A common situation is for an administrator to create a chain of ordered resources, such as: A chain of ordered resources ]]>
Ordered Set Visual representation of the four resources' start order for the above constraints
To simplify this situation, there is an alternate format for ordering constraints A chain of ordered resources expressed as a set ]]> Resource sets have the same ordering semantics as groups. A group resource with the equivalent ordering rules ]]> While the set-based format is not less verbose, it is significantly easier to get right and maintain. It can also be expanded to allow ordered sets of (un)ordered resources. In the example below, rscA and rscB can both start in parallel, as can rscC and rscD, however rscC and rscD can only start once both rscA and rscB are active. Ordered sets of unordered resources ]]>
Two Sets of Unordered Resources Visual representation of the start order for two ordered sets of unordered resources
Of course either or both sets of resources can also be internally ordered (by setting sequential="true") and there is no limit to the number of sets that can be specified. Advanced use of set ordering - Three ordered sets, two of which are internally unordered ]]>
Three Resources Sets Visual representation of the start order for the three sets defined above
Collocating Sets of Resources Another common situation is for an administrator to create a set of collocated resources. - Previously this possible either by defining a resource group (See ) which could not always accurately express the design; or by defining each relationship as an individual constraint, causing a constraint explosion as the number of resources and combinations grew. + Previously this was possible either by defining a resource group (See ) which could not always accurately express the design; or by defining each relationship as an individual constraint, causing a constraint explosion as the number of resources and combinations grew. A chain of collocated resources ]]> To make things easier, we allow an alternate form of colocation constraints using resource_sets. Just like the expanded version, a resource that can't be active also prevents any resource that must be collocated with it from being active. For example if B was not able to run, then both C (and by inference D) must also remain stopped. The equivalent colocation chain expressed using resource_sets ]]> Resource sets have the same colocation semantics as groups. A group resource with the equivalent colocation rules ]]> This notation can also be used in this context to tell the cluster that a set of resources must all be located with a common peer, but have no dependencies on each other. - In this scenario, unlike the previous on, B would be allowed to remain active even if A or C (or both) were inactive. + In this scenario, unlike the previous one, B would be allowed to remain active even if A or C (or both) were inactive. Using colocation sets to specify a common peer. ]]> Of course there is no limit to the number and size of the sets used. The only thing that matters is that in order for any member of set N to be active, all the members of set N+1 must also be active (and naturally on the same node), and that if a set has sequential="true", then in order for member M to be active, member M+1 must also be active. You can even specify the role in which the members of a set must be in using the set's role attribute. A colocation chain where the members of the middle set have no inter-dependencies and the last has master status. ]]>
Another Three Resources Sets Visual representation of a colocation chain where the members of the middle set have no inter-dependencies
diff --git a/doc/Pacemaker_Explained/en-US/Ch-Nodes.xml b/doc/Pacemaker_Explained/en-US/Ch-Nodes.xml index e374449b43..7245afd255 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Nodes.xml +++ b/doc/Pacemaker_Explained/en-US/Ch-Nodes.xml @@ -1,132 +1,132 @@ Cluster Nodes
Defining a Cluster Node Each node in the cluster will have an entry in the nodes section containing its UUID, uname and type. Example cluster node entry ]]> In normal circumstances, the admin should let the cluster populate this information automatically from the communications and membership data. However one can use the crm_uuid tool to read an existing UUID or define a value before the cluster starts.
Describing a Cluster Node Beyond the basic definition of a node, the administrator can also describe the node's attributes, such as how much RAM, disk, what OS or kernel version it has, perhaps even its physical location. This information can then be used by the cluster when deciding where to place resources. For more information on the use of node attributes, see the section on . Node attributes can be specified ahead of time or populated later, when the cluster is running, using crm_attribute. Below is what the node's definition would look like if the admin ran the command:
The result of using crm_attribute to specify which kernel pcmk-1 is running crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --attr-value `uname -r` ]]>
A simpler way to determine the current value of an attribute is to use crm_attribute command again: crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --get-value By specifying --type nodes the admin tells the cluster that this attribute is persistent. There are also transient attributes which are kept in the status section which are "forgotten" whenever the node rejoins the cluster. The cluster uses this area to store a record of how many times a resource has failed on that node but administrators can also read and write to this section by specifying --type status.
Adding a New Cluster Node
Corosync - Adding a new is as simple as installing Corosync and Pacemaker, and copying /etc/corosync/corosync.conf and /etc/ais/authkey (if it exists) from an existing node. + Adding a new node is as simple as installing Corosync and Pacemaker, and copying /etc/corosync/corosync.conf and /etc/ais/authkey (if it exists) from an existing node. You may need to modify the mcastaddr option to match the new node's IP address. If a log message containing "Invalid digest" appears from Corosync, the keys are not consistent between the machines.
Heartbeat - Provided you specified autojoin any in ha.cf, adding a new is as simple as installing heartbeat and copying ha.cf and authkeys from an existing node. + Provided you specified autojoin any in ha.cf, adding a new node is as simple as installing heartbeat and copying ha.cf and authkeys from an existing node. If not, then after setting up ha.cf and authkeys, you must use the hb_addnode command before starting the new node.
Removing a Cluster Node
Corosync Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a reliable solution. First one must arrange for heartbeat to forget about the node (pcmk-1 in the example below). On the host to be removed: Find and record the node's Corosync id: crm_node -i Stop the cluster: /etc/init.d/corosync stop Next, from one of the remaining active cluster nodes: Tell the cluster to forget about the removed host: crm_node -R COROSYNC_ID Only now is it safe to delete the node from the CIB with: cibadmin --delete --obj_type nodes --crm_xml '<node uname="pcmk-1"/>' cibadmin --delete --obj_type status --crm_xml '<node_state uname="pcmk-1"/>'
Heartbeat Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a reliable solution. First one must arrange for heartbeat to forget about the node (pcmk-1 in the example below). To do this, shut down heartbeat on the node and then, from one of the remaining active cluster nodes, run: hb_delnode pcmk-1 Only then is it safe to delete the node from the CIB with: cibadmin --delete --obj_type nodes --crm_xml '<node uname="pcmk-1"/>' cibadmin --delete --obj_type status --crm_xml '<node_state uname="pcmk-1"/>'
Replacing a Cluster Node
Corosync The five-step guide to replacing an existing cluster node: Make sure the old node is completely stopped Give the new machine the same hostname and IP address as the old one Install the cluster software :-) Copy /etc/corosync/corosync.conf and /etc/ais/authkey (if it exists) to the new node Start the new cluster node If a log message containing "Invalid digest" appears from Corosync, the keys are not consistent between the machines.
Heartbeat The seven-step guide to replacing an existing cluster node: Make sure the old node is completely stopped Give the new machine the same hostname as the old one Go to an active cluster node and look up the UUID for the old node in /var/lib/heartbeat/hostcache Install the cluster software Copy ha.cf and authkeys to the new node On the new node, populate it's UUID using crm_uuid -w and the UUID from step 2 Start the new cluster node
diff --git a/doc/Pacemaker_Explained/en-US/Ch-Stonith.xml b/doc/Pacemaker_Explained/en-US/Ch-Stonith.xml index ddefe09935..810c56d005 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Stonith.xml +++ b/doc/Pacemaker_Explained/en-US/Ch-Stonith.xml @@ -1,187 +1,187 @@ Protecting Your Data - STONITH
Why You Need STONITH STONITH is an acronym for Shoot-The-Other-Node-In-The-Head and it protects your data from being corrupted by rogue nodes or concurrent access. Just because a node is unresponsive, this doesn't mean it isn't accessing your data. The only way to be 100% sure that your data is safe, is to use STONITH so we can be certain that the node is truly offline, before allowing the data to be accessed from another node. STONITH also has a role to play in the event that a clustered service cannot be stopped. In this case, the cluster uses STONITH to force the whole node offline, thereby making it safe to start the service elsewhere.
What STONITH Device Should You Use It is crucial that the STONITH device can allow the cluster to differentiate between a node failure and a network one. The biggest mistake people make in choosing a STONITH device is to use remote power switch (such as many on-board IMPI controllers) that shares power with the node it controls. In such cases, the cluster cannot be sure if the node is really offline, or active and suffering from a network fault. Likewise, any device that relies on the machine being active (such as SSH-based "devices" used during testing) are inappropriate.
Configuring STONITH Find the correct driver: stonith_admin --list-installed Since every device is different, the parameters needed to configure it will vary. To find out the parameters associated with the device, run: stonith_admin --metadata --agent type The output should be XML formatted text containing additional parameter descriptions. We - will endevor to make the output more friendly in a later version. + will endeavour to make the output more friendly in a later version. Create a file called stonith.xml containing a primitive resource with a class of stonith, a type of type and a parameter for each of the values returned in step 2 If the device does not know how to fence nodes based on their uname, you may also need to set the special pcmk_host_map parameter. See man stonithd for details. If the device does not support the list command, you may also need to set the special pcmk_host_list and/or pcmk_host_check parameters. See man stonithd for details. If the device does not expect the victim to be specified with the port parameter, you may also need to set the special pcmk_host_argument parameter. See man stonithd for details. Upload it into the CIB using cibadmin: cibadmin -C -o resources --xml-file stonith.xml Once the stonith resource is running, you can test it by executing: stonith_admin --reboot nodename. Although you might want to stop the cluster on that machine first.
Example Assuming we have an chassis containing four nodes and an IPMI device active on 10.0.0.1, then we would chose the fence_ipmilan driver in step 2 and obtain the following list of parameters
Obtaining a list of STONITH Parameters # stonith_admin --metadata -a fence_ipmilan <?xml version="1.0" ?> <resource-agent name="fence_ipmilan" shortdesc="Fence agent for IPMI over LAN"> <longdesc> fence_ipmilan is an I/O Fencing agent which can be used with machines controlled by IPMI. This agent calls support software using ipmitool (http://ipmitool.sf.net/). To use fence_ipmilan with HP iLO 3 you have to enable lanplus option (lanplus / -P) and increase wait after operation to 4 seconds (power_wait=4 / -T 4)</longdesc> <parameters> <parameter name="auth" unique="1"> <getopt mixed="-A" /> <content type="string" /> <shortdesc lang="en">IPMI Lan Auth type (md5, password, or none)</shortdesc> </parameter> <parameter name="ipaddr" unique="1"> <getopt mixed="-a" /> <content type="string" /> <shortdesc lang="en">IPMI Lan IP to talk to</shortdesc> </parameter> <parameter name="passwd" unique="1"> <getopt mixed="-p" /> <content type="string" /> <shortdesc lang="en">Password (if required) to control power on IPMI device</shortdesc> </parameter> <parameter name="passwd_script" unique="1"> <getopt mixed="-S" /> <content type="string" /> <shortdesc lang="en">Script to retrieve password (if required)</shortdesc> </parameter> <parameter name="lanplus" unique="1"> <getopt mixed="-P" /> <content type="boolean" /> <shortdesc lang="en">Use Lanplus</shortdesc> </parameter> <parameter name="login" unique="1"> <getopt mixed="-l" /> <content type="string" /> <shortdesc lang="en">Username/Login (if required) to control power on IPMI device</shortdesc> </parameter> <parameter name="action" unique="1"> <getopt mixed="-o" /> <content type="string" default="reboot"/> <shortdesc lang="en">Operation to perform. Valid operations: on, off, reboot, status, list, diag, monitor or metadata</shortdesc> </parameter> <parameter name="timeout" unique="1"> <getopt mixed="-t" /> <content type="string" /> <shortdesc lang="en">Timeout (sec) for IPMI operation</shortdesc> </parameter> <parameter name="cipher" unique="1"> <getopt mixed="-C" /> <content type="string" /> <shortdesc lang="en">Ciphersuite to use (same as ipmitool -C parameter)</shortdesc> </parameter> <parameter name="method" unique="1"> <getopt mixed="-M" /> <content type="string" default="onoff"/> <shortdesc lang="en">Method to fence (onoff or cycle)</shortdesc> </parameter> <parameter name="power_wait" unique="1"> <getopt mixed="-T" /> <content type="string" default="2"/> <shortdesc lang="en">Wait X seconds after on/off operation</shortdesc> </parameter> <parameter name="delay" unique="1"> <getopt mixed="-f" /> <content type="string" /> <shortdesc lang="en">Wait X seconds before fencing is started</shortdesc> </parameter> <parameter name="verbose" unique="1"> <getopt mixed="-v" /> <content type="boolean" /> <shortdesc lang="en">Verbose mode</shortdesc> </parameter> </parameters> <actions> <action name="on" /> <action name="off" /> <action name="reboot" /> <action name="status" /> <action name="diag" /> <action name="list" /> <action name="monitor" /> <action name="metadata" /> </actions> </resource-agent>
from which we would create a STONITH resource fragment that might look like this Sample STONITH Resource ]]>
diff --git a/doc/Pacemaker_Explained/ro-RO/Ap-Changes.po b/doc/Pacemaker_Explained/ro-RO/Ap-Changes.po new file mode 100644 index 0000000000..2fb9237c33 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ap-Changes.po @@ -0,0 +1,155 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-19 01:54+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Bookmarks: 27,-1,-1,-1,-1,-1,-1,-1,-1,-1\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Ap-Changes.xml:2(title) +msgid "What Changed in 1.0" +msgstr "Ce S-a Schimbat în 1.0" + +# Plural is Noi +#: Ap-Changes.xml:4(title) +msgid "New" +msgstr "Nou" + +# Failure has several meanings in RO, either eşec, as in "he is such a failure, could not get his life toghether" or defecţiune, as in "there is a hardware malfunction". +# Timeout can be expirare, as in "expiry date" and temporizator, as in "something that keeps track of time, similar to stopwatch" +#: Ap-Changes.xml:6(para) +msgid "Failure timeouts. See " +msgstr "Intervalele de expirare în caz de defecţiune. Vedeţi " + +#: Ap-Changes.xml:7(para) +msgid "New section for resource and operation defaults. See and " +msgstr "O nouă secţiune pentru valorile implicite ale resurselor şi operaţiunilor. Vedeţi şi " + +#: Ap-Changes.xml:8(para) +msgid "Tool for making offline configuration changes. See " +msgstr "Utilitar pentru realizarea de modificări ale configuraţiei offline. Vedeţi " + +#: Ap-Changes.xml:9(para) +msgid "Rules, instance_attributes, meta_attributes and sets of operations can be defined once and referenced in multiple places. See " +msgstr "Regulile, atributele_instanţei, meta_atributele şi seturile de operaţiuni pot fi definite o dată iar apoi pot fi referenţiate în mai multe locuri. Vedeţi " + +#: Ap-Changes.xml:10(para) +msgid "The CIB now accepts XPath-based create/modify/delete operations. See the cibadmin help text." +msgstr "CIB-ul acum acceptă operaţiuni de creare/modificare/ştergere bazate pe tipul XPath. Vedeţi ajutorul textual pentru cibadmin." + +#: Ap-Changes.xml:11(para) +msgid "Multi-dimensional colocation and ordering constraints. See and " +msgstr "Restricţii de ordonare şi colocare multi-dimensională. Vedeţi şi " + +#: Ap-Changes.xml:12(para) +msgid "The ability to connect to the CIB from non-cluster machines. See " +msgstr "Posibilitatea de conectare la CIB de pe maşini care nu fac parte din cluster. Vedeţi " + +#: Ap-Changes.xml:13(para) +msgid "Allow recurring actions to be triggered at known times. See " +msgstr "Permite declanşarea de acţiuni recurente la intervale cunoscute de timp. Vedeţi " + +#: Ap-Changes.xml:17(title) +msgid "Changed" +msgstr "Modificat" + +#: Ap-Changes.xml:20(para) +#: Ap-Changes.xml:70(para) +msgid "Syntax" +msgstr "Sintaxă" + +#: Ap-Changes.xml:22(para) +msgid "All resource and cluster options now use dashes (-) instead of underscores (_)" +msgstr "Toate opţiunile şi resursele cluster-ului folosesc acum cratime (-) în loc de underscore (_)" + +#: Ap-Changes.xml:23(para) +msgid "master_slave was renamed to master" +msgstr "master_slave a fost redenumit în master" + +#: Ap-Changes.xml:24(para) +msgid "The attributes container tag was removed" +msgstr "Tag-ul attributes a fost scos" + +#: Ap-Changes.xml:25(para) +msgid "The operation field pre-req has been renamed requires" +msgstr "Câmpul operaţiunii pre-req fost redenumit în requires" + +#: Ap-Changes.xml:26(para) +msgid "All operations must have an interval, start/stop must have it set to zero" +msgstr "Toate operaţiunile trebuie să aibe un interval, cele de start/stop trebuie să îl aibe setat la zero" + +#: Ap-Changes.xml:29(para) +msgid "The stonith-enabled option now defaults to true." +msgstr "Opţiunea stonith-enabled are acum valoarea implicită setată pe true." + +#: Ap-Changes.xml:30(para) +msgid "The cluster will refuse to start resources if stonith-enabled is true (or unset) and no STONITH resources have been defined" +msgstr "Clusterul va refuza să pornească resurse dacă stonith-enabled este true (sau nu este setat) şi nici o resursă STONITH nu a fost definită" + +#: Ap-Changes.xml:31(para) +msgid "The attributes of colocation and ordering constraints were renamed for clarity. See and " +msgstr "Atributele restricţiilor de colocare şi ordonare au fost redenumite pentru o mai bună claritate. Vedeţi şi " + +#: Ap-Changes.xml:32(para) +msgid "resource-failure-stickiness has been replaced by migration-threshold. See " +msgstr "resource-failure-stickiness a fost înlocuită de migration-threshold. Vedeţi " + +#: Ap-Changes.xml:33(para) +msgid "The arguments for command-line tools have been made consistent" +msgstr "Argumentele pentru utilitarele folosite în linia de comandă au fost aduse la o formă consistentă" + +#: Ap-Changes.xml:35(para) +msgid "Switched to RelaxNG schema validation and libxml2 parser." +msgstr "Am trecut la RelaxNG pentru validarea schemei şi libxml2 ca parser." + +#: Ap-Changes.xml:38(para) +msgid "id fields are now XML IDs which have the following limitations" +msgstr "câmpurile id sunt acum ID-uri XML care au următoarele limitări" + +#: Ap-Changes.xml:40(para) +msgid "id's cannot contain colons (:)" +msgstr "id-urile nu pot conţine două puncte (:)" + +#: Ap-Changes.xml:41(para) +msgid "id's cannot begin with a number" +msgstr "id-urile nu pot începe cu un număr" + +#: Ap-Changes.xml:42(para) +msgid "id's must be globally unique (not just unique for that tag)" +msgstr "id-urile trebuie să fie unice la nivel global (nu unice doar pentru acel tag)" + +#: Ap-Changes.xml:46(para) +msgid "Some fields (such as those in constraints that refer to resources) are IDREFs. This means that they must reference existing resources or objects in order for the configuration to be valid. Removing an object which is referenced elsewhere will therefore fail." +msgstr "Unele câmpuri (cum ar fi acelea care fac parte din restricţii care fac referinţă la resurse) sunt IDREF-uri. Acest lucru înseamnă că ele trebuie să facă referinţă către resurse sau obiecte existente pentru a fi validă configurarea. Eliminarea unui obiect care este referenţiat altundeva prin urmare va eşua." + +#: Ap-Changes.xml:53(para) +msgid "The CIB representation from which the MD5 digest used to verify CIBs has changed. This means that every CIB update will require a full refresh on any upgraded nodes until the cluster is fully upgraded to 1.0. This will result in significant performance degradation and it is therefore highly inadvisable to run a mixed 1.0/0.6 cluster for any longer than absolutely necessary." +msgstr "Reprezentarea CIB-ului din care se generează hash-ul MD5 folosit pentru a verifica CIB-ul s-a schimbat. Acest lucru înseamnă că fiecare actualizare a CIB-ului va necesita o reîmprospătare completă pe oricare dintre nodurile îmbunătăţite până ce clusterul va fi modernizat complet la 1.0. Acest aspect va duce la o degradare semnificativă a performanţei şi prin urmare este total nerecomandată rularea unui cluster mixt 1.0/0.6 pentru o perioadă mai lungă decât este absolut necesar." + +#: Ap-Changes.xml:62(para) +msgid "Ping node information no longer needs to be added to ha.cf Simply include the lists of hosts in your ping resource(s)." +msgstr "Informaţii despre noduri către care se pot efectua verificări de tip ICMP (ping) nu mai trebuie adăugate în ha.cf Pur şi simplu includeţi lista de host-uri în resursa(ele) de tip ping." + +#: Ap-Changes.xml:67(title) +msgid "Removed" +msgstr "Scoase" + +#: Ap-Changes.xml:73(para) +msgid "It is no longer possible to set resource meta options as top-level attributes. Use meta attributes instead." +msgstr "Nu mai este posibil să fie setate meta opţiunile resursei ca attribute de nivel înalt. Folosiţi meta atributele în schimb." + +#: Ap-Changes.xml:78(para) +msgid "Resource and operation defaults are no longer read from crm_config. See and instead." +msgstr "Valorile implicite ale resurselor si operaţiunilor nu mai sunt citite din crm_config. Vedeţi şi în schimb." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ap-Changes.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ap-Debug.po b/doc/Pacemaker_Explained/ro-RO/Ap-Debug.po new file mode 100644 index 0000000000..767450b9f0 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ap-Debug.po @@ -0,0 +1,256 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-19 07:21+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Ap-Debug.xml:2(title) +msgid "Debugging Cluster Startup" +msgstr "Depanarea Pornirii Clusterului" + +#: Ap-Debug.xml:4(title) +msgid "Corosync" +msgstr "Corosync" + +#: Ap-Debug.xml:7(title) +msgid "Prerequisites" +msgstr "Premise" + +#: Ap-Debug.xml:9(title) +msgid "Minimum logging configuration" +msgstr "Configuraţia minim necesară pentru log-uri" + +#: Ap-Debug.xml:11(userinput) +#: Ap-Debug.xml:31(userinput) +#, no-wrap +msgid "" +"\n" +" # /etc/init.d/openais start\n" +"\t " +msgstr "" +"\n" +" # /etc/init.d/openais start\n" +"\t " + +#: Ap-Debug.xml:14(computeroutput) +#, no-wrap +msgid "" +"\n" +" logging {\n" +" to_syslog: yes\n" +" syslog_facility: daemon\n" +" }\n" +"\t " +msgstr "" +"\n" +" logging {\n" +" to_syslog: yes\n" +" syslog_facility: daemon\n" +" }\n" +"\t " + +#: Ap-Debug.xml:21(caption) +msgid "Whatever other logging you have, these two lines are required for Pacemaker clusters" +msgstr "Indiferent de ce alte log-uri aveţi, aceste două linii sunt necesare pentru clusterele de tip Pacemaker" + +#: Ap-Debug.xml:27(title) +msgid "Confirm Corosync Started" +msgstr "Confirmaţi că a Pornit Corosync" + +#: Ap-Debug.xml:29(title) +msgid "Expected output when starting openais" +msgstr "Rezultatul aşteptat la pornirea openais" + +#: Ap-Debug.xml:34(computeroutput) +#, no-wrap +msgid "" +"\n" +" Starting Corosync daemon (aisexec): starting... rc=0: OK\n" +"\t " +msgstr "" +"\n" +" Starting Corosync daemon (aisexec): starting... rc=0: OK\n" +"\t " + +#: Ap-Debug.xml:41(title) +msgid "Expected log messages - startup" +msgstr "Mesaje de log aşteptate - la pornire" + +#: Ap-Debug.xml:43(userinput) +#, no-wrap +msgid "" +"\n" +" # grep -e \"openais.*network interface\" -e \"AIS Executive Service\" /var/log/messages\n" +"\t " +msgstr "" +"\n" +" # grep -e \"openais.*network interface\" -e \"AIS Executive Service\" /var/log/messages\n" +"\t " + +#: Ap-Debug.xml:46(computeroutput) +#, no-wrap +msgid "" +"\n" +" Aug 27 16:23:37 test1 openais[26337]: [MAIN ] AIS Executive Service RELEASE 'subrev 1152 version 0.80'\n" +" Aug 27 16:23:38 test1 openais[26337]: [MAIN ] AIS Executive Service: started and ready to provide service.\n" +" Aug 27 16:23:38 test1 openais[26337]: [TOTEM] The network interface [192.168.9.41] is now up.\n" +"\t " +msgstr "" +"\n" +" Aug 27 16:23:37 test1 openais[26337]: [MAIN ] AIS Executive Service RELEASE 'subrev 1152 version 0.80'\n" +" Aug 27 16:23:38 test1 openais[26337]: [MAIN ] AIS Executive Service: started and ready to provide service.\n" +" Aug 27 16:23:38 test1 openais[26337]: [TOTEM] The network interface [192.168.9.41] is now up.\n" +"\t " + +#: Ap-Debug.xml:52(caption) +msgid "The versions may differ, but you should see Corosync indicate it started and sucessfully attached to the machine's network interface" +msgstr "Versiunile pot fi diferite, însă ar trebui să vedeţi Corosync indicând că a pornit şi s-a ataşat cu succes la interfaţa de reţea a maşinii" + +#: Ap-Debug.xml:58(title) +msgid "Expected log messages - membership" +msgstr "Mesaje de log aşteptate - apartenenţă" + +#: Ap-Debug.xml:60(userinput) +#, no-wrap +msgid "" +"\n" +" # grep CLM /var/log/messages\n" +"\t " +msgstr "" +"\n" +" # grep CLM /var/log/messages\n" +"\t " + +#: Ap-Debug.xml:63(computeroutput) +#, no-wrap +msgid "" +"\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] CLM CONFIGURATION CHANGE\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] New Configuration:\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Left:\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Joined:\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] CLM CONFIGURATION CHANGE\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] New Configuration:\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] r(0) ip(192.168.9.41) \n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Left:\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Joined:\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] r(0) ip(192.168.9.41) \n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] got nodejoin message 192.168.9.41\n" +"\t " +msgstr "" +"\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] CLM CONFIGURATION CHANGE\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] New Configuration:\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Left:\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Joined:\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] CLM CONFIGURATION CHANGE\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] New Configuration:\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] r(0) ip(192.168.9.41) \n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Left:\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Joined:\n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] r(0) ip(192.168.9.41) \n" +" Aug 27 16:53:15 test1 openais[2166]: [CLM ] got nodejoin message 192.168.9.41\n" +"\t " + +#: Ap-Debug.xml:77(caption) +msgid "The exact messages will differ, but you should see a new membership formed with the real IP address of your node" +msgstr "Mesajele exacte vor fi diferite, însă ar trebui sa vedeţi o nouă apartenenţă formată cu adresa IP reală a nodului vostru" + +#: Ap-Debug.xml:84(title) +msgid "Checking Pacemaker" +msgstr "Verificarea Pacemaker-ului" + +#: Ap-Debug.xml:85(para) +msgid "Now that we have confirmed that Corosync is functional we can check the rest of the stack." +msgstr "Acum că am confirmat că procesul Corosync este funcţional putem verifica restul stivei." + +#: Ap-Debug.xml:88(title) +msgid "Expected Pacemaker startup logging for Corosync" +msgstr "Log-urile aşteptate la pornirea Pacemaker pentru Corosync" + +#: Ap-Debug.xml:90(userinput) +#, no-wrap +msgid "" +"\n" +" # grep pcmk_plugin_init /var/log/messages\n" +"\t " +msgstr "" +"\n" +" # grep pcmk_plugin_init /var/log/messages\n" +"\t " + +#: Ap-Debug.xml:93(computeroutput) +#, no-wrap +msgid "" +"\n" +" Aug 27 16:53:15 test1 openais[2166]: [pcmk ] info: pcmk_plugin_init: CRM: Initialized\n" +" Aug 27 16:53:15 test1 openais[2166]: [pcmk ] Logging: Initialized pcmk_plugin_init\n" +" Aug 27 16:53:15 test1 openais[2166]: [pcmk ] info: pcmk_plugin_init: Service: 9\n" +" Aug 27 16:53:15 test1 openais[2166]: [pcmk ] info: pcmk_plugin_init: Local hostname: test1\n" +"\t " +msgstr "" +"\n" +" Aug 27 16:53:15 test1 openais[2166]: [pcmk ] info: pcmk_plugin_init: CRM: Initialized\n" +" Aug 27 16:53:15 test1 openais[2166]: [pcmk ] Logging: Initialized pcmk_plugin_init\n" +" Aug 27 16:53:15 test1 openais[2166]: [pcmk ] info: pcmk_plugin_init: Service: 9\n" +" Aug 27 16:53:15 test1 openais[2166]: [pcmk ] info: pcmk_plugin_init: Local hostname: test1\n" +"\t " + +#: Ap-Debug.xml:100(caption) +msgid "If you don't see these messages, or some like them, there is likely a problem finding or loading the pacemaker plugin." +msgstr "Dacă nu vedeţi aceste mesaje sau unele similare, este probabil o problemă în găsirea sau încărcarea plugin-ului pacemaker." + +#: Ap-Debug.xml:106(title) +msgid "Expected process listing on a 64-bit machine" +msgstr "Lista de procese aşteptate pe o maşină pe 64 de biţi" + +#: Ap-Debug.xml:108(userinput) +#, no-wrap +msgid "" +"\n" +" # ps axf\n" +"\t " +msgstr "" +"\n" +" # ps axf\n" +"\t " + +#: Ap-Debug.xml:111(computeroutput) +#, no-wrap +msgid "" +"\n" +" 3718 ? Ssl 0:05 /usr/sbin/aisexec\n" +" 3723 ? SLs 0:00 \\_ /usr/lib64/heartbeat/stonithd\n" +" 3724 ? S 0:05 \\_ /usr/lib64/heartbeat/cib\n" +" 3725 ? S 0:21 \\_ /usr/lib64/heartbeat/lrmd\n" +" 3726 ? S 0:01 \\_ /usr/lib64/heartbeat/attrd\n" +" 3727 ? S 0:00 \\_ /usr/lib64/heartbeat/pengine\n" +" 3728 ? S 0:01 \\_ /usr/lib64/heartbeat/crmd\n" +"\t " +msgstr "" +"\n" +" 3718 ? Ssl 0:05 /usr/sbin/aisexec\n" +" 3723 ? SLs 0:00 \\_ /usr/lib64/heartbeat/stonithd\n" +" 3724 ? S 0:05 \\_ /usr/lib64/heartbeat/cib\n" +" 3725 ? S 0:21 \\_ /usr/lib64/heartbeat/lrmd\n" +" 3726 ? S 0:01 \\_ /usr/lib64/heartbeat/attrd\n" +" 3727 ? S 0:00 \\_ /usr/lib64/heartbeat/pengine\n" +" 3728 ? S 0:01 \\_ /usr/lib64/heartbeat/crmd\n" +"\t " + +#: Ap-Debug.xml:121(caption) +msgid "On 32-bit systems the exact path may differ, but all the above processes should be listed." +msgstr "Pe sistemele pe 32 de biţi calea exactă poate fi diferită, dar toate procesele de mai sus ar trebui să fie listate." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ap-Debug.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ap-FAQ.po b/doc/Pacemaker_Explained/ro-RO/Ap-FAQ.po new file mode 100644 index 0000000000..5c687ac74d --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ap-FAQ.po @@ -0,0 +1,135 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-19 07:37+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Ap-FAQ.xml:2(title) +msgid "FAQ" +msgstr "FAQ" + +#: Ap-FAQ.xml:5(title) +msgid "History" +msgstr "Istoric" + +#: Ap-FAQ.xml:8(para) +msgid "Why is the Project Called Pacemaker?" +msgstr "De ce este Proiectul Numit Pacemaker?" + +#: Ap-FAQ.xml:11(para) +msgid "First of all, the reason its not called the CRM is because of the abundance of terms that are commonly abbreviated to those three letters." +msgstr "În primul rând, motivul pentru care nu este denumit CRM este datorită abundenţei de termeni care sunt asociaţi în mod obişnuit cu acele trei litere." + +#: Ap-FAQ.xml:12(para) +msgid "The Pacemaker name came from Kham, a good friend of mine, and was originally used by a Java GUI that I was prototyping in early 2007. Alas other commitments have prevented the GUI from progressing much and, when it came time to choose a name for this project, Lars suggested it was an even better fit for an independent CRM." +msgstr "Numele de Pacemaker a provenit de la Kham, un bun prieten de-al meu, şi a fost folosit iniţial de către un GUI Java pentru care am creat prototipul în prima parte a anului 2007. Alte angajamente au împiedicat progresul semnificativ al GUI-ului şi când a venit momentul să alegem un nume pentru acest proiect, Lars a sugerat că ar fi o potrivire şi mai bună pentru un CRM independent." + +#: Ap-FAQ.xml:16(para) +msgid "The idea stems from the analogy between the role of this software and that of the little device that keeps the human heart pumping. Pacemaker monitors the cluster and intervenes when necessary to ensure the smooth operation of the services it provides." +msgstr "Ideea provine din analogia dintre rolul acestui software şi acela al micului dispozitiv care menţine inima umană pompând. Pacemaker monitorizează clusterul şi intervine când este necesar pentru a asigura operarea fluentă a serviciilor pe care le furnizează." + +#: Ap-FAQ.xml:20(para) +msgid "There were a number of other names (and acronyms) tossed around, but suffice to say \"Pacemaker\" was the best" +msgstr "Au existat un număr de alte nume (şi acronime) aruncate de colo, colo, dar este suficient să spun că \"Pacemaker\" a fost cel mai bun" + +#: Ap-FAQ.xml:25(para) +msgid "Why was the Pacemaker Project Created?" +msgstr "De ce a fost Creat Proiectul Pacemaker?" + +#: Ap-FAQ.xml:28(para) +msgid "The decision was made to spin-off the CRM into its own project after the 2.1.3 Heartbeat release in order to" +msgstr "Decizia a fost luată de a crea un produs secundar din CRM prin a avea proiectul propriu după lansarea Heartbeat 2.1.3 pentru a" + +#: Ap-FAQ.xml:30(para) +msgid "support both the Corosync and Heartbeat cluster stacks equally" +msgstr "suporta ambele stive de cluster, Corosync şi Heartbeat, în mod egal" + +#: Ap-FAQ.xml:31(para) +msgid "decouple the release cycles of two projects at very different stages of their life-cycles" +msgstr "decupla ciclurile de lansare ale celor două proiecte aflate la stadii foarte diferite ale ciclului vieţii acestora" + +#: Ap-FAQ.xml:32(para) +msgid "foster the clearer package boundaries, thus leading to" +msgstr "adopta graniţe mai clare legate de pachete, tinzând către" + +#: Ap-FAQ.xml:33(para) +msgid "better and more stable interfaces" +msgstr "interfeţe mai bune şi mai stabile" + +#: Ap-FAQ.xml:39(title) +msgid "Setup" +msgstr "Instalare" + +#: Ap-FAQ.xml:42(para) +msgid "What Messaging Layers are Supported?" +msgstr "Care Straturi de Mesagerie sunt Suportate?" + +#: Ap-FAQ.xml:46(para) +msgid "Corosync ()" +msgstr "Corosync ()" + +#: Ap-FAQ.xml:47(para) +msgid "Heartbeat ()" +msgstr "Heartbeat ()" + +#: Ap-FAQ.xml:53(para) +msgid "Can I Choose which Messaging Layer to use at Run Time?" +msgstr "Pot Alege care Strat de Mesagerie să îl Folosesc la Momentul Rulării?" + +#: Ap-FAQ.xml:56(para) +msgid "Yes. The CRM will automatically detect who started it and behave accordingly." +msgstr "Da. CRM-ul va detecta în mod automat cine l-a pornit şi se va comporta în concordanţă." + +#: Ap-FAQ.xml:61(para) +msgid "Can I Have a Mixed Heartbeat-Corosync Cluster?" +msgstr "Pot Avea un Cluster Mixt Heartbeat-Corosync?" + +#: Ap-FAQ.xml:64(para) +msgid "No." +msgstr "Nu." + +#: Ap-FAQ.xml:69(para) +msgid "Which Messaging Layer Should I Choose?" +msgstr "Care Strat de Mesagerie ar trebui să îl aleg?" + +#: Ap-FAQ.xml:72(para) +msgid "This is discussed in ." +msgstr "Acest lucru este dscutat în ." + +#: Ap-FAQ.xml:77(para) +msgid "Where Can I Get Pre-built Packages?" +msgstr "De Unde Pot Obţine Pachete Pre-Compilate?" + +#: Ap-FAQ.xml:80(para) +msgid "Official packages for most major .rpm and based distributions are available from:" +msgstr "Pachete oficiale pentru majoritatea distribuţiilor bazate pe .rpm sunt disponibile la:" + +#: Ap-FAQ.xml:82(para) +msgid "For Debian packages, building from source and details on using the above repositories, see our installation page." +msgstr "Pentru pachete Debian, compilarea din sursă şi detalii asupra folosirii repositoarelor de mai sus, uitaţi-vă la pagina de instalare." + +#: Ap-FAQ.xml:87(para) +msgid "What Versions of Pacemaker Are Supported?" +msgstr "Care Versiuni de Pacemaker sunt Suportate?" + +#: Ap-FAQ.xml:90(para) +#, fuzzy +msgid "Please refer to the Releases page for an up-to-date list of versions supported directly by the project." +msgstr "Vă rugam să consultaţi pagina de Releases pentru o listă la zi a versiunilor suportate în mod direct de către proiect." + +#: Ap-FAQ.xml:91(para) +msgid "When seeking assistance, please try to ensure you have one of these versions." +msgstr "Când căutaţi asistenţă, vă rugăm să vă asiguraţi că aveţi una din versiunile acestea." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ap-FAQ.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ap-Install.po b/doc/Pacemaker_Explained/ro-RO/Ap-Install.po new file mode 100644 index 0000000000..c5ac05fcd6 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ap-Install.po @@ -0,0 +1,230 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-21 02:26+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Ap-Install.xml:2(title) +msgid "Installation" +msgstr "Instalare" + +#: Ap-Install.xml:4(title) +msgid "Choosing a Cluster Stack" +msgstr "Alegerea unei Stive de Cluster" + +#: Ap-Install.xml:5(para) +msgid "Ultimately the choice of cluster stack is a personal decision that must be made in the context of you or your company's needs and strategic direction. Pacemaker currently functions equally well with both stacks." +msgstr "În ultimă instanţă alegerea unei stive de cluster este o decizie personală care trebuie realizată în contextul vostru sau al nevoilor şi direcţiei strategice ale companiei voastre. În momentul de faţă Pacemaker funcţionează la fel de bine cu ambele stive." + +#: Ap-Install.xml:6(para) +msgid "Here are some factors that may influence the decision" +msgstr "În continuare sunt câţiva factori care ar putea influenţa decizia" + +#: Ap-Install.xml:9(para) +msgid "SUSE/Novell, Red Hat and Oracle are all putting their collective weight behind the Corosync cluster stack." +msgstr "SUSE/Novell, Red Hat şi Oracle îşi pun la contribuţie greutatea colectivă pentru a susţine stiva de cluster Corosync." + +#: Ap-Install.xml:12(para) +msgid "Corosync is an OSI Certified implementation of an industry standard (the Service Availability Forum Application Interface Specification)." +msgstr "Corosync este o implementare Certificată OSI a unui standard al industriei (Service Availability Forum Application Interface Specification)." + +#: Ap-Install.xml:15(para) +msgid "Using Corosync gives your applications access to the following additional cluster services" +msgstr "Folosirea Corosync oferă aplicaţiilor dvs. acces la următoarele servicii de cluster adiţionale" + +#: Ap-Install.xml:17(para) +msgid "checkpoint service" +msgstr "serviciu punct de control" + +#: Ap-Install.xml:20(para) +msgid "distributed locking service" +msgstr "serviciu de blocare distribuit" + +#: Ap-Install.xml:23(para) +msgid "extended virtual synchrony service" +msgstr "serviciu de sincronie virtuală extinsă" + +#: Ap-Install.xml:26(para) +msgid "cluster closed process group service" +msgstr "serviciu de grup de procese închise de cluster" + +#: Ap-Install.xml:32(para) +msgid "It is likely that Pacemaker, at some point in the future, will make use of some of these additional services not provided by Heartbeat" +msgstr "Este probabil ca Pacemaker, la un moment dat în viitor, să utilizeze o parte din aceste servicii adiţionale care nu sunt furnizate de Heartbeat" + +#: Ap-Install.xml:35(para) +msgid "To date, Pacemaker has received less real-world testing on Corosync than it has on Heartbeat." +msgstr "Până în acest moment, Pacemaker a avut parte de mai puţină testare \"real-world\" pe Corosync faţă de Heartbeat" + +#: Ap-Install.xml:40(title) +msgid "Enabling Pacemaker" +msgstr "Activarea Pacemaker" + +#: Ap-Install.xml:42(title) +msgid "For Corosync" +msgstr "Pentru Corosync" + +#: Ap-Install.xml:43(para) +msgid "The Corosync configuration is normally located in /etc/corosync/corosync.conf and an example for a machine with an address of 1.2.3.4 in a cluster communicating on port 1234 (without peer authentication and message encryption) is shown below." +msgstr "Fişierul de configurare al Corosync se găseşte în mod normal în /etc/corosync/corosync.conf şi un exemplu pentru o maşină cu adresa 1.2.3.4 într-un cluster care comunică pe portul 1234 (fără autentificarea partenerului sau criptarea mesajelor) este prezentată mai jos." + +#: Ap-Install.xml:45(title) +msgid "An example Corosync configuration file" +msgstr "Un exemplu de fişier de configurare al Corosync" + +#: Ap-Install.xml:46(programlisting) +#, no-wrap +msgid "" +"\n" +" totem {\n" +" version: 2\n" +" secauth: off\n" +" threads: 0\n" +" interface {\n" +" ringnumber: 0\n" +" bindnetaddr: 1.2.3.4\n" +" mcastaddr: 226.94.1.1\n" +" mcastport: 1234\n" +" }\n" +" }\n" +" logging {\n" +" fileline: off\n" +" to_syslog: yes\n" +" syslog_facility: daemon\n" +" }\n" +" amf {\n" +" mode: disabled\n" +" }\n" +"\t" +msgstr "" +"\n" +" totem {\n" +" version: 2\n" +" secauth: off\n" +" threads: 0\n" +" interface {\n" +" ringnumber: 0\n" +" bindnetaddr: 1.2.3.4\n" +" mcastaddr: 226.94.1.1\n" +" mcastport: 1234\n" +" }\n" +" }\n" +" logging {\n" +" fileline: off\n" +" to_syslog: yes\n" +" syslog_facility: daemon\n" +" }\n" +" amf {\n" +" mode: disabled\n" +" }\n" +"\t" + +#: Ap-Install.xml:68(para) +msgid "The logging should be mostly obvious and the amf section refers to the Availability Management Framework and is not covered in this document." +msgstr "Partea de loguri ar trebui să fie evidentă în cea mai mare parte şi secţiunea amf se referă la Availability Management Framework şi nu este acoperit în acest document." + +#: Ap-Install.xml:70(para) +msgid "Please consult the Corosync website and documentation for details on enabling encryption and peer authentication for the cluster." +msgstr "Vă rugăm să consultaţi website-ul Corosync şi documentaţia pentru detalii despre activarea criptării şi a autentificării partenerului pentru cluster." + +#: Ap-Install.xml:69(para) +msgid "The interesting part of the configuration is the totem section. This is where we define how the node can communicate with the rest of the cluster and what protocol version and options (including encryption) it should use. Beginners are encouraged to use the values shown and modify the interface section based on their network." +msgstr "Partea interesantă a configuraţiei o reprezintă secţiunea totem. Aici definim cum poate comunica un nod cu restul clusterului şi ce versiune de protocol şi opţiuni (incluzând criptarea) ar trebui să folosească. Începătorii sunt încurajaţi să folosească valorile prezentate şi să modifice secţiunea referitoare la interfaţă pe baza reţelei acestora." + +#: Ap-Install.xml:72(para) +msgid "It is also possible to configure Corosync for an IPv6 based environment. Simply configure bindnetaddr and mcastaddr with their IPv6 equivalents. Eg" +msgstr "Este totodată posibilă configurarea Corosync pentru un mediu bazat pe IPV6. Pur şi simplu configuraţi bindnetaddr şi mcastaddr cu echivalentele IPV6 ale acestora. Ex" + +#: Ap-Install.xml:74(title) +msgid "Example options for an IPv6 environment" +msgstr "Exemple de opţiuni pentru un mediu IPV6" + +#: Ap-Install.xml:75(programlisting) +#, no-wrap +msgid "" +"\n" +" bindnetaddr: fec0::1:a800:4ff:fe00:20 \n" +" mcastaddr: ff05::1\n" +"\t " +msgstr "" +"\n" +" bindnetaddr: fec0::1:a800:4ff:fe00:20 \n" +" mcastaddr: ff05::1\n" +"\t " + +#: Ap-Install.xml:80(para) +msgid "To tell Corosync to use the Pacemaker cluster manager, add the following fragment to a functional Corosync configuration and restart the cluster." +msgstr "Pentru a îi spune Corosync-ului să folosească Pacemaker ca şi manager al clusterului, adăugaţi următorul fragment la o configuraţie funcţională de Corosync şi reporniţi clusterul." + +#: Ap-Install.xml:82(title) +msgid "Configuration fragment for enabling Pacemaker under Corosync" +msgstr "Fragment de configurare pentru a activa Pacemaker sub Corosync" + +#: Ap-Install.xml:83(programlisting) +#, no-wrap +msgid "" +"\n" +" aisexec {\n" +" user: root\n" +" group: root\n" +" }\n" +" service {\n" +" name: pacemaker\n" +" ver: 0\n" +" }\n" +"\t " +msgstr "" +"\n" +" aisexec {\n" +" user: root\n" +" group: root\n" +" }\n" +" service {\n" +" name: pacemaker\n" +" ver: 0\n" +" }\n" +"\t " + +#: Ap-Install.xml:94(para) +msgid "The cluster needs to be run as root so that its child processes (the lrmd in particular) have sufficient privileges to perform the actions requested of it. After-all, a cluster manager that can't add an IP address or start apache is of little use." +msgstr "Clusterul trebuie să ruleze ca root pentru ca procesele copil ale acestuia (lrmd-ul în particular) să aibe suficiente privilegii pentru a îndeplini acţiunile care i s-au cerut. La urma urmei, un manager de cluster care nu poate să adauge o adresă IP sau să pornească apache este de puţin folos." + +#: Ap-Install.xml:95(para) +msgid "The second directive is the one that actually instructs the cluster to run Pacemaker." +msgstr "A doua directivă este cea care instruieşte de fapt clusterul să ruleze Pacemaker." + +#: Ap-Install.xml:98(title) +msgid "For Heartbeat" +msgstr "Pentru Heartbeat" + +#: Ap-Install.xml:99(para) +msgid "Add the following to a functional ha.cf configuration file and restart Heartbeat" +msgstr "Adăugaţi următoarele la un fişier de configurare ha.cf funcţional şi reporniţi Heartbeat" + +#: Ap-Install.xml:101(title) +msgid "Configuration fragment for enabling Pacemaker under Heartbeat" +msgstr "Fragment de configurare pentru a activa Pacemaker sub Heartbeat" + +#: Ap-Install.xml:102(programlisting) +#, no-wrap +msgid "" +"\n" +" crm respawn\n" +"\t " +msgstr "" +"\n" +" crm respawn\n" +"\t " + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ap-Install.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ap-LSB.po b/doc/Pacemaker_Explained/ro-RO/Ap-LSB.po new file mode 100644 index 0000000000..e72507a2fb --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ap-LSB.po @@ -0,0 +1,134 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-23 11:20+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Ap-LSB.xml:2(title) +msgid "Is This init Script LSB Compatible?" +msgstr "Este acest script compatibil LSB?" + +#: Ap-LSB.xml:3(para) +msgid "The relevant part of LSB spec can be found at: http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html. It includes a description of all the return codes listed here." +msgstr "Partea relevantă a specificaţiei LSB poate fi găsită la: http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html. Aceasta include o descriere a tuturor codurilor de ieşire listate aici." + +#: Ap-LSB.xml:7(para) +msgid "Assuming some_service is configured correctly and currently not active, the following sequence will help you determine if it is LSB compatible:" +msgstr "Sub presupunerea că un_serviciu este configurat corect şi nu este activ în momentul de faţă, următoarea secvenţă vă poate ajuta să determinaţi dacă este compatibil LSB:" + +#: Ap-LSB.xml:10(para) +msgid "Start (stopped):" +msgstr "Porneşte (oprit):" + +#: Ap-LSB.xml:11(command) +#: Ap-LSB.xml:26(command) +msgid "/etc/init.d/some_service start ; echo \"result: $?\"" +msgstr "/etc/init.d/un_serviciu start ; echo \"rezultat: $?\"" + +#: Ap-LSB.xml:13(para) +msgid "Did the service start?" +msgstr "A pornit serviciul?" + +#: Ap-LSB.xml:14(para) +#: Ap-LSB.xml:22(para) +#: Ap-LSB.xml:29(para) +#: Ap-LSB.xml:36(para) +#: Ap-LSB.xml:52(para) +msgid "Did the command print result: 0 (in addition to the regular output)?" +msgstr "A printat comanda rezultatul de ieşire: 0 (suplimentar faţă de rezultatul contextual normal)?" + +#: Ap-LSB.xml:17(para) +msgid "Status (running):" +msgstr "Status (rulând):" + +#: Ap-LSB.xml:18(command) +#: Ap-LSB.xml:40(command) +msgid "/etc/init.d/some_service status ; echo \"result: $?\"" +msgstr "/etc/init.d/un_serviciu status ; echo \"rezultatul: $?\"" + +#: Ap-LSB.xml:20(para) +#: Ap-LSB.xml:42(para) +msgid "Did the script accept the command?" +msgstr "A acceptat scriptul comanda?" + +#: Ap-LSB.xml:21(para) +msgid "Did the script indicate the service was running?" +msgstr "A indicat scriptul dacă serviciul rula?" + +#: Ap-LSB.xml:25(para) +msgid "Start (running):" +msgstr "Porneşte (rulând):" + +#: Ap-LSB.xml:28(para) +msgid "Is the service still running?" +msgstr "Serviciul încă rulează?" + +#: Ap-LSB.xml:32(para) +msgid "Stop (running):" +msgstr "Opreşte (rulând):" + +#: Ap-LSB.xml:33(command) +#: Ap-LSB.xml:49(command) +msgid "/etc/init.d/some_service stop ; echo \"result: $?\"" +msgstr "/etc/init.d/un_serviciu stop ; echo \"rezultatul: $?\"" + +#: Ap-LSB.xml:35(para) +msgid "Was the service stopped?" +msgstr "A fost oprit serviciul?" + +#: Ap-LSB.xml:39(para) +msgid "Status (stopped):" +msgstr "Status (oprit):" + +#: Ap-LSB.xml:43(para) +msgid "Did the script indicate the service was not running?" +msgstr "A indicat scriptul faptul că serviciul nu rula?" + +#: Ap-LSB.xml:44(para) +msgid "Did the command print result: 3 (in addition to the regular output)?" +msgstr "A printat comanda rezultatul de ieşire: 3 (suplimentar faţă de rezultatul contextual normal)?" + +#: Ap-LSB.xml:48(para) +msgid "Stop (stopped):" +msgstr "Opreşte (oprit):" + +#: Ap-LSB.xml:51(para) +msgid "Is the service still stopped?" +msgstr "Este serviciul în continuare oprit?" + +#: Ap-LSB.xml:56(para) +msgid "Status (failed):" +msgstr "Status (eşuat):" + +#: Ap-LSB.xml:57(para) +msgid "This step is not readily testable and relies on manual inspection of the script." +msgstr "Acest pas nu este gata pentru a fi testat şi se bazează pe inspecţia manuală a scriptului." + +#: Ap-LSB.xml:58(para) +msgid "The script can use one of the error codes (other than 3) listed in the LSB spec to indicate that it is active but failed." +msgstr "Scriptul poate folosi unul din codurile de eroare (altul decât 3) listate în specificaţia LSB pentru a indica faptul că este activ dar eşuat." + +#: Ap-LSB.xml:59(para) +msgid "This tells the cluster that before moving the resource to another node, it needs to stop it on the existing one first." +msgstr "Aceasta îi spune clusterului ca înainte de a muta resursa pe alt nod, trebuie să o oprească mai întâi pe cel existent." + +#: Ap-LSB.xml:62(para) +msgid "The script can use one of the error codes (other than 3) listed in the LSB spec to indicate that it is active but failed. This tells the cluster that before moving the resource to another node, it needs to stop it on the existing one first." +msgstr "Scriptul poate folosi unul din codurile de eroare (altul decât 3) listate în specificaţia LSB pentru a indica faptul că este activ dar eşuat. Acesta îi spune clusterului ca înainte de a muta resursa pe alt nod, trebuie să o oprească mai întâi pe cel existent." + +#: Ap-LSB.xml:63(para) +msgid "If the answer to any of the above questions is no, then the script is not LSB compliant. Your options are then to either fix the script or write an OCF agent based on the existing script." +msgstr "Dacă răspunsul la oricare din întrebările de mai sus este nu, atunci scriptul nu este compatibil LSB. Opţiunile disponibile în acel moment sunt fie de a repara scriptul fie de a scrie un agent OCF bazat pe scriptul existent." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ap-LSB.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ap-OCF.po b/doc/Pacemaker_Explained/ro-RO/Ap-OCF.po new file mode 100644 index 0000000000..d5bb3c6705 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ap-OCF.po @@ -0,0 +1,432 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-23 12:37+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Ap-OCF.xml:2(title) +msgid "More About OCF Resource Agents" +msgstr "Mai Multe Despre Agenţii de Resursă OCF" + +#: Ap-OCF.xml:4(title) +msgid "Location of Custom Scripts" +msgstr "Locaţia Scripturilor Personalizate" + +#: Ap-OCF.xml:5(para) +msgid "OCF Resource Agents are found in /usr/lib/ocf/resource.d/provider." +msgstr "Agenţii de Resursă OCF se găsesc în /usr/lib/ocf/resource.d/furnizor." + +#: Ap-OCF.xml:6(para) +msgid "When creating your own agents, you are encouraged to create a new directory under /usr/lib/ocf/resource.d/ so that they are not confused with (or overwritten by) the agents shipped with Heartbeat. So, for example, if you chose the provider name of bigCorp and wanted a new resource named bigApp, you would create a script called /usr/lib/ocf/resource.d/bigCorp/bigApp and define a resource:" +msgstr "Când vă creaţi proprii agenţi, sunteţi încurajaţi să creaţi un nou director sub /usr/lib/ocf/resource.d/ astfel încât aceştia să nu fie încurcaţi cu (sau suprascrişi de) agenţii livraţi împreună cu Heartbeat. Deci, de exemplu, dacă aţi fi ales numele de furnizor bigCorp şi aţi fi dorit o nouă resursă numită bigApp, aţi crea un script numit /usr/lib/ocf/resource.d/bigCorp/bigApp şi aţi defini o resursă:" + +#: Ap-OCF.xml:10(programlisting) +#, no-wrap +msgid "<primitive id=\"custom-app\" class=\"ocf\" provider=\"bigCorp\" type=\"bigApp\"/>" +msgstr "<primitive id=\"custom-app\" class=\"ocf\" provider=\"bigCorp\" type=\"bigApp\"/>" + +#: Ap-OCF.xml:13(title) +msgid "Actions" +msgstr "Acţiuni" + +#: Ap-OCF.xml:14(para) +msgid "All OCF Resource Agents are required to implement the following actions" +msgstr "Toţi Agenţii de Resursă OCF sunt obligaţi să implementeze următoarele acţiuni" + +#: Ap-OCF.xml:16(title) +msgid "Required Actions for OCF Agents" +msgstr "Acţiuni Necesare pentru Agenţii OCF" + +#: Ap-OCF.xml:20(entry) +#: Ap-OCF.xml:64(entry) +msgid "Action" +msgstr "Acţiune" + +#: Ap-OCF.xml:21(entry) +#: Ap-OCF.xml:65(entry) +#: Ap-OCF.xml:103(entry) +#: Ap-OCF.xml:130(entry) +msgid "Description" +msgstr "Descriere" + +#: Ap-OCF.xml:22(entry) +#: Ap-OCF.xml:66(entry) +msgid "Instructions" +msgstr "Instrucţiuni" + +#: Ap-OCF.xml:27(entry) +msgid "start" +msgstr "start" + +#: Ap-OCF.xml:28(entry) +msgid "Start the resource" +msgstr "Porneşte resursa" + +#: Ap-OCF.xml:29(entry) +msgid "Return 0 on success and an appropriate error code otherwise. Must not report success until the resource is fully active." +msgstr "Returnează 0 în caz de succes şi un cod de eroare potrivit în caz contrar. Nu trebuie să raporteze succes până ce resursa nu este complet activă." + +#: Ap-OCF.xml:32(entry) +msgid "stop" +msgstr "stop" + +#: Ap-OCF.xml:33(entry) +msgid "Stop the resource" +msgstr "Opreşte resursa" + +#: Ap-OCF.xml:34(entry) +msgid "Return 0 on success and an appropriate error code otherwise. Must not report success until the resource is fully stopped." +msgstr "Returnează 0 în caz de succes şi un cod de eroare potrivit în caz contrar. Nu trebuie să raporteze succes până ce resursa nu este complet oprită." + +#: Ap-OCF.xml:37(entry) +msgid "monitor" +msgstr "monitor" + +#: Ap-OCF.xml:38(entry) +msgid "Check the resource's state" +msgstr "Verifică starea resursei" + +#: Ap-OCF.xml:40(para) +msgid "Exit 0 if the resource is running, 7 if it is stopped and anything else if it is failed." +msgstr "Iese cu 0 dacă resursa rulează, 7 dacă este oprită şi orice altceva dacă a eşuat." + +#: Ap-OCF.xml:41(para) +msgid "NOTE: The monitor script should test the state of the resource on the local machine only." +msgstr "NOTĂ: Scriptul de monitorizare ar trebui să testeze starea resursei numai pe maşina locală." + +#: Ap-OCF.xml:45(entry) +msgid "meta-data" +msgstr "meta-data" + +#: Ap-OCF.xml:46(entry) +msgid "Describe the resource" +msgstr "Descrie resursa" + +#: Ap-OCF.xml:48(para) +msgid "Provide information about this resource as an XML snippet. Exit with 0." +msgstr "Furnizează informaţii despre această resursă ca un extras XML. Iese cu 0." + +#: Ap-OCF.xml:49(para) +msgid "NOTE: This is not performed as root." +msgstr "NOTĂ: Acest aspect nu este efectuat ca root." + +#: Ap-OCF.xml:53(entry) +msgid "validate-all" +msgstr "validate-all" + +#: Ap-OCF.xml:54(entry) +msgid "Verify the supplied parameters are correct" +msgstr "Verifică dacă parametrii furnizaţi sunt corecţi" + +#: Ap-OCF.xml:55(entry) +msgid "Exit with 0 if parameters are valid, 2 if not valid, 6 if resource is not configured." +msgstr "Iese cu 0 dacă parametrii sunt valizi, 2 dacă nu sunt valizi, 6 dacă resursa nu este configurată." + +#: Ap-OCF.xml:58(para) +msgid "Additional requirements (not part of the OCF specs) are placed on agents that will be used for advanced concepts like clones and multi-state resources." +msgstr "Cerinţe suplimentare (care nu sunt parte din specificaţia OCF) sunt plasate pe agenţi care vor fi folosiţi pentru concepte avansate cum ar fi clone şi resurse multi-state." + +#: Ap-OCF.xml:60(title) +msgid "Optional Actions for OCF Agents" +msgstr "Acţiuni Opţionale pentru Agenţi OCF" + +#: Ap-OCF.xml:69(entry) +msgid "promote" +msgstr "promote" + +#: Ap-OCF.xml:70(entry) +msgid "Promote the local instance of a multi-state resource to the master/primary state" +msgstr "Promovează instanţa locală a unei resurse multi-state la starea master/primară" + +#: Ap-OCF.xml:71(entry) +#: Ap-OCF.xml:76(entry) +msgid "Return 0 on success" +msgstr "Returnează 0 în caz de succes" + +#: Ap-OCF.xml:74(entry) +msgid "demote" +msgstr "demote" + +#: Ap-OCF.xml:75(entry) +msgid "Demote the local instance of a multi-state resource to the slave/secondary state" +msgstr "Retrogradează instanţa locală a unei resurse multi-state la starea slave/secundară" + +#: Ap-OCF.xml:79(entry) +msgid "notify" +msgstr "notify" + +#: Ap-OCF.xml:80(entry) +msgid "Used by the cluster to send the agent pre and post notification events telling the resource what is or has just taken place" +msgstr "Folosit de către cluster pentru a trimite agentului notificări pre şi post eveniment spunându-i resursei ceea ce se întâmplă sau ce tocmai s-a întâmplat" + +#: Ap-OCF.xml:81(entry) +msgid "Must not fail. Must exit 0" +msgstr "Nu trebuie să fie eşueze. Trebuie să iasă cu 0" + +#: Ap-OCF.xml:84(para) +msgid "One action specified in the OCF specs is not currently used by the cluster" +msgstr "O acţiune specificată în specificaţiile OCF nu este folosită de către cluster în mod curent" + +#: Ap-OCF.xml:86(para) +msgid "recover - a variant of the start action, this should try to recover a resource locally." +msgstr "recuperare - o variantă a acţiunii de pornire, aceasta ar trebui să recupereze o resursă local." + +#: Ap-OCF.xml:89(para) +msgid "Remember to use ocf-tester to verify that your new agent complies with the OCF standard properly." +msgstr "Nu uitaţi să folosiţi ocf-tester pentru a verifica dacă noul vostru agent este compatibil cu standardul OCF." + +#: Ap-OCF.xml:92(title) +msgid "How Does the Cluster Interpret the OCF Return Codes?" +msgstr "Cum Interpretează Clusterul Codurile de Ieşire OCF?" + +#: Ap-OCF.xml:93(para) +msgid "The first thing the cluster does is check the return code against the expected result. If the result does not match the expected value, then the operation is considered to have failed and recovery action is initiated." +msgstr "Primul lucru pe care îl face clusterul este să verifice codul de ieşire faţă de rezultatul aşteptat. Dacă rezultatul nu se potriveşte cu valoarea aşteptată, atunci este considerat că operaţiunea a eşuat şi acţiunea de recuperare este iniţiată." + +#: Ap-OCF.xml:96(para) +msgid "There are three types of failure recovery:" +msgstr "Sunt trei tipuri de recuperare în caz de eşec:" + +#: Ap-OCF.xml:98(title) +msgid "Types of recovery performed by the cluster" +msgstr "Tipuri de recuperare realizate de către cluster" + +#: Ap-OCF.xml:102(entry) +#: Ap-OCF.xml:131(entry) +msgid "Recovery Type" +msgstr "Tip de Recuperare" + +#: Ap-OCF.xml:104(entry) +msgid "Action Taken by the Cluster" +msgstr "Acţiunea Luată de către Cluster" + +#: Ap-OCF.xml:107(entry) +#: Ap-OCF.xml:137(entry) +#: Ap-OCF.xml:143(entry) +#: Ap-OCF.xml:185(entry) +#: Ap-OCF.xml:191(entry) +#: Ap-OCF.xml:197(entry) +msgid "soft" +msgstr "soft" + +#: Ap-OCF.xml:108(entry) +msgid "A transient error occurred" +msgstr "O eroare tranzientă a avut loc" + +#: Ap-OCF.xml:109(entry) +msgid "Restart the resource or move it to a new location" +msgstr "Reporneşte resursa sau mut-o într-o locaţie nouă" + +#: Ap-OCF.xml:112(entry) +#: Ap-OCF.xml:149(entry) +#: Ap-OCF.xml:155(entry) +#: Ap-OCF.xml:161(entry) +#: Ap-OCF.xml:167(entry) +msgid "hard" +msgstr "hard" + +#: Ap-OCF.xml:113(entry) +msgid "A non-transient error that may be specific to the current node occurred" +msgstr "O eroare non-tranzientă s-a produs care ar putea fi specifică nodului curent" + +#: Ap-OCF.xml:114(entry) +msgid "Move the resource elsewhere and prevent it from being retried on the current node" +msgstr "Mută resursa în altă parte şi previne reîncercarea acesteia pe nodul curent" + +#: Ap-OCF.xml:117(entry) +#: Ap-OCF.xml:173(entry) +msgid "fatal" +msgstr "fatal" + +#: Ap-OCF.xml:118(entry) +msgid "A non-transient error that will be common to all cluster nodes (I.e. a bad configuration was specified)" +msgstr "O eroare non-tranzientă care va fi comună pe toate nodurile clusterului (ex.: o configuraţie greşită a fost specificată)" + +#: Ap-OCF.xml:119(entry) +msgid "Stop the resource and prevent it from being started on any cluster node" +msgstr "Opreşte resursa si împiedică pornirea acesteia pe oricare nod al clusterului" + +#: Ap-OCF.xml:122(para) +msgid "Assuming an action is considered to have failed, the following table outlines the different OCF return codes and the type of recovery the cluster will initiate when it is received." +msgstr "Plecând de la presupunerea că o acţiune este considerată că ar fi eşuat, următorul tabel evidenţiază diferitele coduri de ieşire OCF şi tipul de recuperare pe care o va iniţia clusterul când acest cod este primit." + +#: Ap-OCF.xml:124(title) +msgid "OCF Return Codes and How They are Handled" +msgstr "Codurile de Ieşire OCF şi Cum Sunt Ele Gestionate" + +#: Ap-OCF.xml:128(entry) +msgid "OCF Return Code" +msgstr "Cod de Ieşire OCF" + +#: Ap-OCF.xml:129(entry) +msgid "OCF Alias" +msgstr "Alias OCF" + +#: Ap-OCF.xml:134(entry) +msgid "0" +msgstr "0" + +#: Ap-OCF.xml:135(entry) +msgid "OCF_SUCCESS" +msgstr "OCF_SUCCESS" + +#: Ap-OCF.xml:136(entry) +msgid "Success. The command completed successfully. This is the expected result for all start, stop, promote and demote commands." +msgstr "Succes. Comanda a fost rulată cu succes. Acesta este rezultatul aşteptat pentru toate comenzile start, stop, promote şi demote." + +#: Ap-OCF.xml:140(entry) +msgid "1" +msgstr "1" + +#: Ap-OCF.xml:141(entry) +msgid "OCF_ERR_GENERIC" +msgstr "OCF_ERR_GENERIC" + +#: Ap-OCF.xml:142(entry) +msgid "Generic \"there was a problem\" error code." +msgstr "Cod de eroare generic \"a fost o problemă\"" + +#: Ap-OCF.xml:146(entry) +msgid "2" +msgstr "2" + +#: Ap-OCF.xml:147(entry) +msgid "OCF_ERR_ARGS" +msgstr "OCF_ERR_ARGS" + +#: Ap-OCF.xml:148(entry) +msgid "The resource's configuration is not valid on this machine. Eg. Refers to a location/tool not found on the node." +msgstr "Configuraţia resursei nu este validă pe această maşină. Ex. Face referinţă la o/un locaţie/utilitar care nu a fost găsit/ă pe acest nod." + +#: Ap-OCF.xml:152(entry) +msgid "3" +msgstr "3" + +#: Ap-OCF.xml:153(entry) +msgid "OCF_ERR_UNIMPLEMENTED" +msgstr "OCF_ERR_UNIMPLEMENTED" + +#: Ap-OCF.xml:154(entry) +msgid "The requested action is not implemented." +msgstr "Acţiunea solicitată nu este implementată." + +#: Ap-OCF.xml:158(entry) +msgid "4" +msgstr "4" + +#: Ap-OCF.xml:159(entry) +msgid "OCF_ERR_PERM" +msgstr "OCF_ERR_PERM" + +#: Ap-OCF.xml:160(entry) +msgid "The resource agent does not have sufficient privileges to complete the task." +msgstr "Agentul de resursă nu are suficiente privilegii pentru a îndeplini sarcina." + +#: Ap-OCF.xml:164(entry) +msgid "5" +msgstr "5" + +#: Ap-OCF.xml:165(entry) +msgid "OCF_ERR_INSTALLED" +msgstr "OCF_ERR_INSTALLED" + +#: Ap-OCF.xml:166(entry) +msgid "The tools required by the resource are not installed on this machine." +msgstr "Utilitarele necesitate de către resursă nu sunt instalate pe această maşină." + +#: Ap-OCF.xml:170(entry) +msgid "6" +msgstr "6" + +#: Ap-OCF.xml:171(entry) +msgid "OCF_ERR_CONFIGURED" +msgstr "OCF_ERR_CONFIGURED" + +#: Ap-OCF.xml:172(entry) +msgid "The resource's configuration is invalid. Eg. A required parameter is missing." +msgstr "Configuraţia resursei este invalidă. Ex. Un parametru necesar lipseşte." + +#: Ap-OCF.xml:176(entry) +msgid "7" +msgstr "7" + +#: Ap-OCF.xml:177(entry) +msgid "OCF_NOT_RUNNING" +msgstr "OCF_NOT_RUNNING" + +#: Ap-OCF.xml:178(entry) +msgid "The resource is safely stopped. The cluster will not attempt to stop a resource that returns this for any action." +msgstr "Resursa a fost oprită cu succes. Clusterul nu va încerca să oprească o resursă care returnează acest cod pentru orice acţiune." + +#: Ap-OCF.xml:179(entry) +msgid "N/A" +msgstr "N/A" + +#: Ap-OCF.xml:182(entry) +msgid "8" +msgstr "8" + +#: Ap-OCF.xml:183(entry) +msgid "OCF_RUNNING_MASTER" +msgstr "OCF_RUNNING_MASTER" + +#: Ap-OCF.xml:184(entry) +msgid "The resource is running in Master mode." +msgstr "Resursa rulează în modul Master." + +#: Ap-OCF.xml:188(entry) +msgid "9" +msgstr "9" + +#: Ap-OCF.xml:189(entry) +msgid "OCF_FAILED_MASTER" +msgstr "OCF_FAILED_MASTER" + +#: Ap-OCF.xml:190(entry) +msgid "The resource is in Master mode but has failed. The resource will be demoted, stopped and then started (and possibly promoted) again." +msgstr "Resursa este în modul Master dar a eşuat. Resursa va fi retrogradată, oprită şi apoi pornită (şi posibil promovată) din nou." + +#: Ap-OCF.xml:194(entry) +msgid "other" +msgstr "other" + +#: Ap-OCF.xml:195(entry) +msgid "NA" +msgstr "NA" + +#: Ap-OCF.xml:196(entry) +msgid "Custom error code." +msgstr "Cod de eroare personalizat." + +#: Ap-OCF.xml:200(para) +msgid "Although counter intuitive, even actions that return 0 (aka. OCF_SUCCESS) can be considered to have failed. This can happen when a resource that is expected to be in the Master state is found running as a Slave, or when a resource is found active on multiple machines.." +msgstr "Deşi contra intuitiv, chiar şi acţiunile care returnează 0 (aka. OCF_SUCCESS) pot fi considerate că ar fi eşuat. Acest lucru se poate întâmpla când o resursă care este de aşteptat să fie în starea Master este găsită rulând ca Slave sau când o resursă este găsită activă pe mai multe maşini." + +#: Ap-OCF.xml:201(title) +msgid "Exceptions" +msgstr "Excepţii" + +#: Ap-OCF.xml:203(para) +msgid "Non-recurring monitor actions (probes) that find a resource active (or in Master mode) will not result in recovery action unless it is also found active elsewhere" +msgstr "Acţiunile de monitorizare nerecurente (probele) care găsesc o resursă activă (sau în starea Master) nu vor rezulta într-o acţiune de recuperare decât dacă este găsită activă în altă parte" + +#: Ap-OCF.xml:204(para) +msgid "The recovery action taken when a resource is found active more than once is determined by the multiple-active property of the resource" +msgstr "Acţiunea de recuperare luată când o resursă este găsită activă mai mult de o dată este determinată de proprietatea multiple-active a resursei" + +#: Ap-OCF.xml:205(para) +msgid "Recurring actions that return OCF_ERR_UNIMPLEMENTED do not cause any type of recovery" +msgstr "Acţiunile recurente care returnează OCF_ERR_UNIMPLEMENTED nu cauzează nici un fel de recuperare" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ap-OCF.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ap-Samples.po b/doc/Pacemaker_Explained/ro-RO/Ap-Samples.po new file mode 100644 index 0000000000..7bb9f0c546 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ap-Samples.po @@ -0,0 +1,50 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-23 12:47+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Ap-Samples.xml:1(title) +msgid "Sample Configurations" +msgstr "Exemple de Configurare" + +#: Ap-Samples.xml:3(title) +msgid "An Empty Configuration" +msgstr "O Configuraţie Goală" + +#: Ap-Samples.xml:5(title) +msgid "An empty configuration" +msgstr "O configuraţie goală" + +#: Ap-Samples.xml:22(title) +msgid "A Simple Configuration" +msgstr "O Configuraţie Simplă" + +#: Ap-Samples.xml:24(title) +msgid "2 nodes, some cluster options and a resource" +msgstr "2 noduri, câteva opţiuni de cluster şi o resursă" + +#: Ap-Samples.xml:63(para) +msgid "In this example, we have one resource (an IP address) that we check every five minutes and will run on host c001n01 until either the resource fails 10 times or the host shuts down." +msgstr "În acest exemplu, avem o resursă (o adresă IP) pe care o verificăm la fiecare cinci minute şi va rula pe host-ul c001n01 până fie resursa eşuează de 10 ori fie host-ul este închis." + +#: Ap-Samples.xml:66(title) +msgid "An Advanced Configuration" +msgstr "O Configuraţie Avansată" + +#: Ap-Samples.xml:69(title) +msgid "groups and clones with stonith" +msgstr "grupuri şi clone cu stonith" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ap-Samples.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ap-Upgrade-Config.po b/doc/Pacemaker_Explained/ro-RO/Ap-Upgrade-Config.po new file mode 100644 index 0000000000..13b08df431 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ap-Upgrade-Config.po @@ -0,0 +1,212 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-23 13:05+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Ap-Upgrade-Config.xml:2(title) +msgid "Upgrading the Configuration from 0.6" +msgstr "Actualizarea Configuraţiei de la 0.6" + +#: Ap-Upgrade-Config.xml:4(title) +msgid "Preparation" +msgstr "Pregătire" + +#: Ap-Upgrade-Config.xml:5(para) +msgid "Download the latest DTD from and ensure your configuration validates." +msgstr "Descărcaţi cel mai recent DTD de la şi asiguraţi-vă că, configuraţia se validează." + +#: Ap-Upgrade-Config.xml:8(title) +#: Ap-Upgrade-Config.xml:32(para) +msgid "Perform the upgrade" +msgstr "Realizaţi actualizarea" + +#: Ap-Upgrade-Config.xml:10(title) +msgid "Upgrade the software" +msgstr "Actualizaţi software-ul" + +#: Ap-Upgrade-Config.xml:11(para) +msgid "Refer to the appendix: " +msgstr "Consultaţi anexa: " + +#: Ap-Upgrade-Config.xml:14(title) +msgid "Upgrade the Configuration" +msgstr "Actualizaţi Configuraţia" + +#: Ap-Upgrade-Config.xml:15(para) +msgid "As XML is not the friendliest of languages, it is common for cluster administrators to have scripted some of their activities. In such cases, it is likely that those scripts will not work with the new 1.0 syntax." +msgstr "Cum XML-ul nu este cel mai prietenos dintre limbaje, este obişnuit pentru administratorii de cluster să fi scriptat unele dintre activităţile acestora. În astfel de cazuri, este probabil ca acele scripturi să nu funcţioneze cu noua sintaxă 1.0." + +#: Ap-Upgrade-Config.xml:16(para) +msgid "In order to support such environments, it is actually possible to continue using the old 0.6 syntax." +msgstr "Pentru a suporta astfel de medii, este chiar posibilă continuarea folosirii sintaxei vechi de 0.6." + +#: Ap-Upgrade-Config.xml:17(para) +msgid "The downside however, is that not all the new features will be available and there is a performance impact since the cluster must do a non-persistent configuration upgrade before each transition. So while using the old syntax is possible, it is not advisable to continue using it indefinitely." +msgstr "Partea nefastă însă, este că nu toate funcţionalităţile noi vor fi disponibile şi este un impact de performanţă din moment ce clusterul trebuie să execute o actualizare non-persistentă a configuraţiei înainte de fiecare tranziţie. Deci în timp ce folosirea sintaxei vechi este posibilă, nu este recomandată folosirea acesteia pe termen nelimitat." + +#: Ap-Upgrade-Config.xml:18(para) +msgid "Even if you wish to continue using the old syntax, it is advisable to follow the upgrade procedure to ensure that the cluster is able to use your existing configuration (since it will perform much the same task internally)." +msgstr "Chiar dacă doriţi să continuaţi folosirea sintaxei vechi, este recomandat să urmaţi procedura de actualizare pentru a vă asigura că clusterul este capabil să folosească configuraţia existentă (din moment ce va efectua în mare parte aceeaşi sarcină intern)." + +#: Ap-Upgrade-Config.xml:21(para) +msgid "Create a shadow copy to work with" +msgstr "Creaţi o copie ascunsă pe care să lucraţi" + +#: Ap-Upgrade-Config.xml:22(command) +msgid "crm_shadow --create upgrade06" +msgstr "crm_shadow --create upgrade06" + +#: Ap-Upgrade-Config.xml:25(para) +msgid "Verify the configuration is valid" +msgstr "Verificaţi că, configuraţia este validă" + +#: Ap-Upgrade-Config.xml:26(command) +msgid "crm_verify --live-check" +msgstr "crm_verify --live-check" + +#: Ap-Upgrade-Config.xml:29(para) +msgid "Fix any errors or warnings" +msgstr "Reparaţi orice erori sau avertismente" + +#: Ap-Upgrade-Config.xml:33(command) +msgid "cibadmin --upgrade" +msgstr "cibadmin --upgrade" + +#: Ap-Upgrade-Config.xml:34(para) +msgid "If this step fails, there are three main possibilities" +msgstr "Dacă acest pas eşuează, sunt trei posibilităţi principale" + +#: Ap-Upgrade-Config.xml:36(para) +msgid "The configuration was not valid to start with - go back to step 2" +msgstr "Configuraţia nu a fost validă de la început - mergeţi înapoi la pasul 2" + +#: Ap-Upgrade-Config.xml:37(para) +msgid "The transformation failed - report a bug or email the project at pacemaker@oss.clusterlabs.org" +msgstr "Transformarea a eşuat - raportaţi un bug sau trimite-ţi un email către proiect la pacemaker@oss.clusterlabs.org" + +#: Ap-Upgrade-Config.xml:40(para) +msgid "The most common reason is ID values being repeated or invalid. Pacemaker 1.0 is much stricter regarding this type of validation" +msgstr "Cel mai comun motiv îl reprezintă valorile ID-ului fiind repetate sau invalide. Pacemaker 1.0 este mult mai strict în privinţa acestui tip de validare" + +#: Ap-Upgrade-Config.xml:38(para) +msgid "The transformation was successful but produced an invalid result " +msgstr "Transformarea a reuşit dar a produs un rezultat invalid " + +#: Ap-Upgrade-Config.xml:44(para) +msgid "If the result of the transformation is invalid, you may see a number of errors from the validation library. If these are not helpful, visit and/or try the following procedure described below under ." +msgstr "Dacă rezultatul transformării este invalid, se pot observa un număr de erori de la biblioteca de validare. Dacă acestea nu sunt folositoare, vizitaţi şi/sau încercaţi următoarea procedură descrisă mai jos sub ." + +#: Ap-Upgrade-Config.xml:47(para) +msgid "Check the changes" +msgstr "Verificaţi modificările" + +#: Ap-Upgrade-Config.xml:48(command) +msgid "crm_shadow --diff" +msgstr "crm_shadow --diff" + +#: Ap-Upgrade-Config.xml:49(para) +msgid "If at this point there is anything about the upgrade that you wish to fine-tune (for example, to change some of the automatic IDs) now is the time to do so. Since the shadow configuration is not in use by the cluster, it is safe to edit the file manually:" +msgstr "Dacă la acest punct există orice legat de actualizare ce doriţi să reglaţi fin (de exemplu, să schimbaţi unele din ID-urile automate) acum este momentul să realizaţi acest lucru. Din moment ce configuraţia ascunsă nu este folosită de către cluster, este neprimejdios să editaţi fişierul manual:" + +#: Ap-Upgrade-Config.xml:50(command) +msgid "crm_shadow --edit" +msgstr "crm_shadow --edit" + +#: Ap-Upgrade-Config.xml:51(para) +msgid "Will open the configuration in your favorite editor (or whichever one is specified by the standard EDITOR environment variable)." +msgstr "Va deschide configuraţia în editorul vostru preferat (sau oricare este specificat de variabila standard de mediu EDITOR)" + +#: Ap-Upgrade-Config.xml:54(para) +msgid "Preview how the cluster will react" +msgstr "Previzualizaţi cum va reacţiona clusterul" + +#: Ap-Upgrade-Config.xml:55(para) +msgid "Test what the cluster will do when you upload the new configuration" +msgstr "Testaţi ce va face clusterul când încărcaţi noua configuraţie" + +#: Ap-Upgrade-Config.xml:56(filename) +msgid "upgrade06.dot" +msgstr "upgrade06.dot" + +#: Ap-Upgrade-Config.xml:56(command) +msgid "ptest -VVVVV --live-check --save-dotfile " +msgstr "ptest -VVVVV --live-check --save-dotfile " + +#: Ap-Upgrade-Config.xml:57(command) +msgid "graphviz upgrade06.dot" +msgstr "graphviz upgrade06.dot" + +#: Ap-Upgrade-Config.xml:58(para) +msgid "Verify that either no resource actions will occur or that you are happy with any that are scheduled. If the output contains actions you do not expect (possibly due to changes to the score calculations), you may need to make further manual changes. See for further details on how to interpret the output of ptest." +msgstr "Verificaţi că fie nu vor avea loc acţiuni ale resurelor sau că sunteţi mulţumiţi cu cele care sunt programate. Dacă rezultatul conţine acţiuni pe care nu le aşteptaţi (posibil datorită modificărilor în calculul scorurilor), ar putea fi necesar să realizaţi modificări suplimentare manual. Vedeţi pentru detalii suplimentare despre cum să interpretaţi rezultatul de ieşire al ptest." + +#: Ap-Upgrade-Config.xml:65(para) +msgid "Upload the changes" +msgstr "Încărcaţi modificările" + +#: Ap-Upgrade-Config.xml:66(command) +msgid "crm_shadow --commit upgrade06 --force" +msgstr "crm_shadow --commit upgrade06 --force" + +#: Ap-Upgrade-Config.xml:67(para) +msgid "If this step fails, something really strange has occurred. You should report a bug." +msgstr "Dacă acest pas eşuează, ceva cu adevărat ciudat s-a întâmplat. Ar trebui să raportaţi bug-ul." + +#: Ap-Upgrade-Config.xml:72(title) +msgid "Manually Upgrading the Configuration" +msgstr "Actualizarea Manuală a Configuraţiei" + +#: Ap-Upgrade-Config.xml:73(para) +msgid "It is also possible to perform the configuration upgrade steps manually. To do this" +msgstr "Este de asemenea posibil să efectuaţi paşii de actualizare ai configuraţiei manual. Pentru a realiza acest lucru" + +#: Ap-Upgrade-Config.xml:76(para) +msgid "Locate the upgrade06.xsl conversion script or download the latest version from version control" +msgstr "Localizaţi scriptul de conversie upgrade06.xsl sau descărcaţi cea mai recentă versiune de controlul versiunii" + +#: Ap-Upgrade-Config.xml:80(filename) +msgid "/path/to/upgrade06.xsl" +msgstr "/calea/către/upgrade06.xsl" + +#: Ap-Upgrade-Config.xml:80(filename) +msgid "config06.xml" +msgstr "config06.xml" + +#: Ap-Upgrade-Config.xml:80(filename) +#: Ap-Upgrade-Config.xml:86(filename) +msgid "config10.xml" +msgstr "config10.xml" + +#: Ap-Upgrade-Config.xml:80(command) +msgid "xsltproc > " +msgstr "xsltproc > " + +#: Ap-Upgrade-Config.xml:83(para) +msgid "Locate the pacemaker.rng script." +msgstr "Localizaţi scriptul pacemaker.rng." + +#: Ap-Upgrade-Config.xml:86(filename) +msgid "/path/to/pacemaker.rng" +msgstr "/calea/către/pacemaker.rng" + +#: Ap-Upgrade-Config.xml:86(command) +msgid "xmllint --relaxng " +msgstr "xmllint --relaxng " + +#: Ap-Upgrade-Config.xml:90(para) +msgid "The advantage of this method is that it can be performed without the cluster running and any validation errors should be more informative (despite being generated by the same library!) since they include line numbers." +msgstr "Avantajul acestei metode este acela că poate fi efectuată fară ca şi clusterul să funcţioneze şi orice erori de validare ar trebui să fie cu caracter mai informativ (în ciuda faptului că sunt generate de aceeaşi bibliotecă!) din moment ce includ numerele liniilor." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ap-Upgrade-Config.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ap-Upgrade.po b/doc/Pacemaker_Explained/ro-RO/Ap-Upgrade.po new file mode 100644 index 0000000000..aefee3caf0 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ap-Upgrade.po @@ -0,0 +1,328 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-23 19:24+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Ap-Upgrade.xml:2(title) +msgid "Upgrading Cluster Software" +msgstr "Actualizarea Soft-ului de Cluster" + +#: Ap-Upgrade.xml:4(title) +#: Ap-Upgrade.xml:140(title) +msgid "Version Compatibility" +msgstr "Compatibilitatea Versiunii" + +#: Ap-Upgrade.xml:5(para) +msgid "When releasing newer versions we take care to make sure we are backwardly compatible with older versions. While you will always be able to upgrade from version x to x+1, in order to continue to produce high quality software it may occasionally be necessary to drop compatibility with older versions." +msgstr "Când lansăm versiuni noi avem grijă că suntem compatibili invers cu versiunile anterioare. În timp ce veţi putea oricând să actualizaţi de la versiunea x la x+1, pentru a putea să continuăm producţia de soft de înaltă calitate ar putea fi necesar în mod ocazional să renunţăm la compatibilitatea cu versiunile mai vechi." + +#: Ap-Upgrade.xml:6(para) +msgid "There will always be an upgrade path from any series-2 release to any other series-2 release." +msgstr "Întotdeauna va exista o cale de actualizare de la oricare produs lansat în seria-2 la oricare alt produs lansat în aceeaşi serie-2." + +#: Ap-Upgrade.xml:7(para) +msgid "There are three approaches to upgrading your cluster software" +msgstr "Sunt trei alternative în scopul actualizării soft-ului de cluster" + +#: Ap-Upgrade.xml:9(para) +#: Ap-Upgrade.xml:65(title) +msgid "Complete Cluster Shutdown" +msgstr "Oprirea Completă a Clusterului" + +#: Ap-Upgrade.xml:10(para) +#: Ap-Upgrade.xml:101(title) +msgid "Rolling (node by node)" +msgstr "Secvenţial (nod după nod)" + +#: Ap-Upgrade.xml:11(para) +#: Ap-Upgrade.xml:186(title) +msgid "Disconnect and Reattach" +msgstr "Deconectează şi Reataşează" + +#: Ap-Upgrade.xml:13(para) +msgid "Each method has advantages and disadvantages, some of which are listed in the table below, and you should chose the one most appropriate to your needs." +msgstr "Fiecare metodă are avantaje şi dezavantaje, unele dintre acestea sunt listate în tabelul de mai jos şi ar trebui să o alegeţi pe aceea cel mai apropiată de nevoile voastre." + +#: Ap-Upgrade.xml:15(title) +msgid "Summary of Upgrade Methodologies" +msgstr "Sumar al Metodologiilor de Actualizare" + +#: Ap-Upgrade.xml:19(entry) +msgid "Type" +msgstr "Tip" + +#: Ap-Upgrade.xml:20(entry) +msgid "Available between all software versions" +msgstr "Disponibil între toate versiunile de soft" + +#: Ap-Upgrade.xml:21(entry) +msgid "Service Outage During Upgrade" +msgstr "Indisponibilitatea Serviciului pe Durata Actualizării" + +#: Ap-Upgrade.xml:22(entry) +msgid "Service Recovery During Upgrade" +msgstr "Recuperarea Serviciului pe Durata Actualizării" + +#: Ap-Upgrade.xml:23(entry) +msgid "Exercises Failover Logic/Configuration" +msgstr "Exersează Logica/Configuraţia de Failover" + +#: Ap-Upgrade.xml:27(para) +msgid "For example, switching from Heartbeat to Corosync. Consult the Heartbeat or Corosync documentation to see if upgrading them to a newer version is also supported" +msgstr "De exemplu, trecerea de la Heartbeat la Corosync. Consultaţi documentaţia de Heartbeat sau Corosync pentru vedea dacă actualizarea acestora la o versiune mai nouă este de asemenea suportată" + +#: Ap-Upgrade.xml:24(entry) +msgid "Allows change of cluster stack type " +msgstr "Permite schimbarea tipului de stivă de cluster " + +#: Ap-Upgrade.xml:37(entry) +msgid "Shutdown" +msgstr "Închidere" + +#: Ap-Upgrade.xml:38(entry) +#: Ap-Upgrade.xml:42(entry) +#: Ap-Upgrade.xml:48(entry) +#: Ap-Upgrade.xml:49(entry) +#: Ap-Upgrade.xml:54(entry) +#: Ap-Upgrade.xml:58(entry) +msgid "yes" +msgstr "da" + +#: Ap-Upgrade.xml:39(entry) +#: Ap-Upgrade.xml:47(entry) +msgid "always" +msgstr "întotdeauna" + +#: Ap-Upgrade.xml:40(entry) +msgid "N/A" +msgstr "N/A" + +#: Ap-Upgrade.xml:41(entry) +#: Ap-Upgrade.xml:46(entry) +#: Ap-Upgrade.xml:50(entry) +#: Ap-Upgrade.xml:56(entry) +#: Ap-Upgrade.xml:57(entry) +msgid "no" +msgstr "nu" + +#: Ap-Upgrade.xml:45(entry) +msgid "Rolling" +msgstr "Secvenţial" + +#: Ap-Upgrade.xml:53(entry) +msgid "Reattach" +msgstr "Reataşare" + +#: Ap-Upgrade.xml:55(entry) +msgid "only due to failure" +msgstr "doar din cauza eşecului" + +#: Ap-Upgrade.xml:66(para) +msgid "In this scenario one shuts down all cluster nodes and resources and upgrades all the nodes before restarting the cluster." +msgstr "În acest scenariu se închid toate nodurile şi resursele clusterului şi se actualizează toate nodurile înainte de a reporni clusterul." + +#: Ap-Upgrade.xml:67(title) +#: Ap-Upgrade.xml:115(title) +#: Ap-Upgrade.xml:189(title) +msgid "Procedure" +msgstr "Procedură" + +#: Ap-Upgrade.xml:70(para) +#: Ap-Upgrade.xml:87(para) +#: Ap-Upgrade.xml:116(para) +#: Ap-Upgrade.xml:203(para) +#: Ap-Upgrade.xml:217(para) +msgid "On each node:" +msgstr "Pe fiecare nod:" + +#: Ap-Upgrade.xml:73(para) +#: Ap-Upgrade.xml:119(para) +#: Ap-Upgrade.xml:206(para) +msgid "Shutdown the cluster stack (Heartbeat or Corosync)" +msgstr "Închideţi stiva de cluster (Heartbeat sau Corosync)" + +#: Ap-Upgrade.xml:76(para) +msgid "Upgrade the Pacemaker software. This may also include upgrading the cluster stack and/or the underlying operating system." +msgstr "Actualizaţi soft-ul Pacemaker. Acest lucru poate include actualizarea stivei de cluster şi/sau a sistemului de operare de bază." + +#: Ap-Upgrade.xml:84(para) +#: Ap-Upgrade.xml:214(para) +msgid "Check the configuration manually or with the crm_verify tool if available." +msgstr "Verificaţi configuraţia manual sau cu utilitarul crm_verify dacă este disponibil." + +#: Ap-Upgrade.xml:90(para) +#: Ap-Upgrade.xml:219(para) +msgid "Start the cluster stack. This can be either Corosync or Heartbeat and does not need to be the same as the previous cluster stack." +msgstr "Porniţi stiva de cluster. Aceasta poate fi oricare dintre Corosync sau Heartbeat şi nu trebuie să fie aceeaşi ca stiva anterioară de cluster." + +#: Ap-Upgrade.xml:102(para) +msgid "In this scenario each node is removed from the cluster, upgraded and then brought back online until all nodes are running the newest version." +msgstr "În acest scenariu fiecare nod este scos din cluster, actualizat şi apoi adus înapoi online până ce toate nodurile rulează pe cea mai recentă versiune." + +#: Ap-Upgrade.xml:104(para) +msgid "This method is currently broken between Pacemaker 0.6.x and 1.0.x" +msgstr "Această metodă este în prezent nefuncţională între Pacemaker 0.6.x şi 1.0.x" + +#: Ap-Upgrade.xml:107(para) +msgid "Measures have been put into place to ensure rolling upgrades always work for versions after 1.0.0 If there is sufficient demand, the work to repair 0.6 -> 1.0 compatibility will be carried out. Otherwise, please try one of the other upgrade strategies. Detach/Reattach is a particularly good option for most people." +msgstr "Măsuri au fost implementate pentru a asigura că actualizările secvenţiale vor funcţiona întotdeauna pentru versiunile după 1.0.0. Dacă există o cerere suficientă, munca necesară pentru a repara compatibilitatea între 0.6 -> 1.0 va fi dusă la final. În caz contrar, vă rugăm să încercaţi una din celelalte strategii de actualizare. Detaşare/Reataşare este o opţiune deosebit de bună pentru majoritatea persoanelor." + +#: Ap-Upgrade.xml:122(para) +msgid "Upgrade the Pacemaker software. This may also include upgrading the cluster stack and/or the underlying operating system." +msgstr "Actualizaţi soft-ul Pacemaker. Acest lucru poate include actualizarea stivei de cluster şi/sau a sistemului de operare de bază." + +#: Ap-Upgrade.xml:125(para) +msgid "On the first node, check the configuration manually or with the crm_verify tool if available." +msgstr "Pe primul nod, verificaţi configuraţia manual sau cu utilitarul crm_verify dacă este disponibil." + +#: Ap-Upgrade.xml:130(para) +msgid "Start the cluster stack. This must be the same type of cluster stack (Corosync or Heartbeat) that the rest of the cluster is using. Upgrading Corosync/Heartbeat may also be possible, please consult the documentation for those projects to see if the two versions will be compatible." +msgstr "Porniţi stiva de cluster. Aceasta trebuie să fie acelaşi tip de stivă de cluster (Corosync sau Heartbeat) care este folosită de către restul clusterului. Actualizarea Corosync/Heartbeat este posibilă de asemenea, vă rugăm să consultaţi documentaţia pentru acele proiecte pentru a vedea dacă cele două versiuni vor fi compatibile." + +#: Ap-Upgrade.xml:137(para) +msgid "Repeat for each node in the cluster" +msgstr "Repetaţi pentru fiecare nod din cluster" + +#: Ap-Upgrade.xml:142(title) +msgid "Version Compatibility Table" +msgstr "Tabel cu Compatibilitatea Versiunilor" + +#: Ap-Upgrade.xml:146(entry) +msgid "Version being Installed" +msgstr "Versiunea care este Instalată" + +#: Ap-Upgrade.xml:147(entry) +msgid "Oldest Compatible Version" +msgstr "Cea mai Veche Versiune Compatibilă" + +#: Ap-Upgrade.xml:150(entry) +msgid "Pacemaker 1.0.x" +msgstr "Pacemaker 1.0.x" + +#: Ap-Upgrade.xml:151(entry) +msgid "Pacemaker 1.0.0" +msgstr "Pacemaker 1.0.0" + +#: Ap-Upgrade.xml:154(entry) +msgid "Pacemaker 0.7.x" +msgstr "Pacemaker 0.7.x" + +#: Ap-Upgrade.xml:155(entry) +msgid "Pacemaker 0.6 or Heartbeat 2.1.3" +msgstr "Pacemaker 0.6 sau Heartbeat 2.1.3" + +#: Ap-Upgrade.xml:158(entry) +msgid "Pacemaker 0.6.x" +msgstr "Pacemaker 0.6.x" + +#: Ap-Upgrade.xml:159(entry) +msgid "Heartbeat 2.0.8" +msgstr "Heartbeat 2.0.8" + +#: Ap-Upgrade.xml:162(entry) +msgid "Heartbeat 2.1.3 (or less)" +msgstr "Heartbeat 2.1.3 (sau mai mică)" + +#: Ap-Upgrade.xml:163(entry) +msgid "Heartbeat 2.0.4" +msgstr "Heartbeat 2.0.4" + +#: Ap-Upgrade.xml:166(entry) +msgid "Heartbeat 2.0.4 (or less)" +msgstr "Heartbeat 2.0.4 (sau mai mică)" + +#: Ap-Upgrade.xml:167(entry) +#: Ap-Upgrade.xml:170(entry) +msgid "Heartbeat 2.0.0" +msgstr "Heartbeat 2.0.0" + +#: Ap-Upgrade.xml:171(entry) +msgid "None. Use an alternate upgrade strategy." +msgstr "Niciuna. Folosiţi o strategie de actualizare alternativă." + +#: Ap-Upgrade.xml:176(title) +msgid "Crossing Compatibility Boundaries" +msgstr "Trecerea Graniţelor de Compatibilitate" + +#: Ap-Upgrade.xml:177(para) +msgid "Rolling upgrades that cross compatibility boundaries must be preformed in multiple steps. For example, to perform a rolling update from Heartbeat 2.0.1 to Pacemaker 0.6.6 one must:" +msgstr "Actualizările secvenţiale care trec de graniţele compatibilităţii trebuie efectuate în paşi multipli. De exemplu, pentru a efectua o actualizare secvenţială de la Heartbeat 2.0.1 la Pacemaker 0.6.6 trebuie să:" + +#: Ap-Upgrade.xml:179(para) +msgid "Perform a rolling upgrade from Heartbeat 2.0.1 to Heartbeat 2.0.4" +msgstr "Efectueaze o actualizare secvenţială de la Heartbeat 2.0.1 la Heartbeat 2.0.4" + +#: Ap-Upgrade.xml:180(para) +msgid "Perform a rolling upgrade from Heartbeat 2.0.4 to Heartbeat 2.1.3" +msgstr "Efectueaze o actualizare secvenţială de la Heartbeat 2.0.4 la Heartbeat 2.1.3" + +#: Ap-Upgrade.xml:181(para) +msgid "Perform a rolling upgrade from Heartbeat 2.1.3 to Pacemaker 0.6.6" +msgstr "Efectueaze o actualizare secvenţială de la Heartbeat 2.1.3 la Pacemaker 0.6.6" + +#: Ap-Upgrade.xml:187(para) +msgid "A variant of a complete cluster shutdown, but the resources are left active and re-detected when the cluster is restarted." +msgstr "O variantă de închidere completă a clusterului, dar resursele sunt lăsate active şi re-detectate când clusterul este repornit." + +#: Ap-Upgrade.xml:192(para) +msgid "Tell the cluster to stop managing services. This is required to allow the services to remain active after the cluster shuts down." +msgstr "Spune clusterului să se oprească din gestionarea serviciilor. Acest lucru este necesar pentru a permite serviciilor să rămână active după ce clusterul este oprit." + +#: Ap-Upgrade.xml:196(command) +msgid "crm_attribute -t crm_config -n is-managed-default -v false" +msgstr "crm_attribute -t crm_config -n is-managed-default -v false" + +#: Ap-Upgrade.xml:199(para) +msgid "For any resource that has a value for is-managed, make sure it is set to false (so that the cluster will not stop it)" +msgstr "Pentru orice resursă care are o valoare pentru is-managed, vă rugăm să vă asiguraţi că este setată pe false (astfel încât clusterul să nu o oprească)" + +#: Ap-Upgrade.xml:200(command) +#: Ap-Upgrade.xml:234(command) +msgid "crm_resource -t primitive -r <rsc_id> -p is-managed -v false" +msgstr "crm_resource -t primitive -r <rsc_id> -p is-managed -v false" + +#: Ap-Upgrade.xml:209(para) +msgid "Upgrade the cluster stack program - This may also include upgrading the underlying operating system." +msgstr "Actualizaţi stiva de cluster - Acest lucru poate include actualizarea sistemului de operare de bază." + +#: Ap-Upgrade.xml:226(para) +msgid "Verify the cluster re-detected all resources correctly" +msgstr "Verificaţi că, clusterul a re-detectat toate resursele în mod corect" + +#: Ap-Upgrade.xml:229(para) +msgid "Allow the cluster to resume managing resources again" +msgstr "Permiteţi clusterului să reia gestionarea resurselor" + +#: Ap-Upgrade.xml:230(command) +msgid "crm_attribute -t crm_config -n is-managed-default -v true" +msgstr "crm_attribute -t crm_config -n is-managed-default -v true" + +#: Ap-Upgrade.xml:233(para) +msgid "For any resource that has a value for is-managed reset it to true (so the cluster can recover the service if it fails) if desired" +msgstr "Pentru orice resursă care are o valoare pentru is-managed resetaţi-o, dacă doriţi, pe true (astfel încât clusterul să poată recupera serviciul dacă acesta eşuează)" + +#: Ap-Upgrade.xml:239(title) +msgid "Notes" +msgstr "Menţiuni" + +#: Ap-Upgrade.xml:241(para) +msgid "Always check your existing configuration is still compatible with the version you are installing before starting the cluster." +msgstr "Întotdeauna verificaţi configuraţia existentă şi că este in continuare compatibilă cu versiunea pe care o instalaţi înainte de a porni clusterul." + +#: Ap-Upgrade.xml:245(para) +msgid "The oldest version of the CRM to support this upgrade type was in Heartbeat 2.0.4" +msgstr "Cea mai veche versiune de CRM care suportă acest tip de actualizare a fost Heartbeat 2.0.4" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ap-Upgrade.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Author_Group.po b/doc/Pacemaker_Explained/ro-RO/Author_Group.po new file mode 100644 index 0000000000..e48e7b91bc --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Author_Group.po @@ -0,0 +1,34 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-02 13:36+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Author_Group.xml:6(firstname) +msgid "Dan" +msgstr "Dan" + +#: Author_Group.xml:6(surname) +msgid "Frîncu" +msgstr "Frîncu" + +#: Author_Group.xml:7(orgname) +msgid "" +msgstr "" + +#: Author_Group.xml:8(email) +msgid "df.cluster@gmail.com" +msgstr "df.cluster@gmail.com" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Author_Group.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Book_Info.po b/doc/Pacemaker_Explained/ro-RO/Book_Info.po new file mode 100644 index 0000000000..9854b24d0b --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Book_Info.po @@ -0,0 +1,64 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-02 13:47+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: Book_Info.xml:31(None) +msgid "@@image: 'Common_Content/images/title_logo.svg'; md5=THIS FILE DOESN'T EXIST" +msgstr "@@image: 'Common_Content/images/title_logo.svg'; md5=ACEST FIŞIER NU EXISTĂ" + +#: Book_Info.xml:5(title) +msgid "Configuration Explained" +msgstr "Configuraţia Explicată" + +#: Book_Info.xml:6(subtitle) +msgid "An A-Z guide to Pacemaker's Configuration Options" +msgstr "Un ghid de la A la Z despre Opţiunile de Configurare ale Pacemaker" + +#: Book_Info.xml:7(productname) +msgid "Pacemaker" +msgstr "Pacemaker" + +#: Book_Info.xml:8(productnumber) +msgid "1.1" +msgstr "1.1" + +#: Book_Info.xml:9(edition) +msgid "1" +msgstr "1" + +#: Book_Info.xml:10(pubsnumber) +msgid "0" +msgstr "0" + +#: Book_Info.xml:12(para) +msgid "The purpose of this document is to definitively explain the concepts used to configure Pacemaker. To achieve this best, it will focus exclusively on the XML syntax used to configure the CIB." +msgstr "Scopul acestui document este de a explica în mod definitiv conceptele folosite pentru a configura Pacemaker. Pentru a reuşi acest lucru în cel mai bun mod, se va concentra în mod exclusiv pe sintaxa XML folosită pentru a configura CIB-ul." + +#: Book_Info.xml:19(para) +msgid "It is hoped however, that having understood the concepts explained here, that the functionality of these tools will also be more readily understood." +msgstr "Speranţa este totodată, ca odată ce conceptele explicate aici au fost înţelese, ca şi funcţionalitatea acestor utilitare să fie înteleasă mai prompt." + +#: Book_Info.xml:16(para) +msgid "For those that are allergic to XML, Pacemaker comes with a cluster shell and a Python based GUI exists, however these tools will not be covered at all in this document , precisely because they hide the XML." +msgstr "Pentru aceeia dintre voi care sunt alergici la XML, Pacemaker vine cu un shell de cluster şi un GUI bazat pe Python există, însă aceste utilitare nu vor fi acoperite în vreun fel în acest document , întocmai datorită faptului că acestea ascund XML-ul." + +#: Book_Info.xml:23(para) +msgid "Additionally, this document is NOT a step-by-step how-to guide for configuring a specific clustering scenario. Although such guides exist, the purpose of this document is to provide an understanding of the building blocks that can be used to construct any type of Pacemaker cluster." +msgstr "Pe deasupra, acest document NU este un ghid pas-cu-pas pentru configurarea unui scenariu specific de cluster. Deşi astfel de ghiduri există, scopul acestui document este acela de a furniza o înţelegere a elementelor de bază care pot fi folosite pentru a construi orice tip de cluster Pacemaker." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Book_Info.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ch-Advanced-Options.po b/doc/Pacemaker_Explained/ro-RO/Ch-Advanced-Options.po new file mode 100644 index 0000000000..356e32b628 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ch-Advanced-Options.po @@ -0,0 +1,623 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-24 06:46+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Ch-Advanced-Options.xml:1(title) +msgid "Advanced Configuration" +msgstr "Configuraţii Avansate" + +#: Ch-Advanced-Options.xml:3(title) +msgid "Connecting to the Cluster Configuration from a Remote Machine" +msgstr "Conectarea la Configuraţia Clusterului de pe o Maşină la Distanţă" + +#: Ch-Advanced-Options.xml:4(para) +msgid "Provided Pacemaker is installed on a machine, it is possible to connect to the cluster even if the machine itself is not a part of it. To do this, one simply sets up a number of environment variables and runs the same commands as you would when working on a cluster node." +msgstr "Cu condiţia ca Pacemaker să fie instalat pe o maşină, este posibilă conectarea la cluster chiar dacă maşina în sine nu este parte din el. Pentru a realiza acest lucru, nu trebuie decât să setaţi un număr de variabile de mediu şi să rulaţi aceleaşi comenzi ca şi când aţi lucra pe un nod din cluster." + +#: Ch-Advanced-Options.xml:9(title) +msgid "Environment Variables Used to Connect to Remote Instances of the CIB" +msgstr "Variabile de Mediu Folosite pentru Conectare la Instanţe la Distanţă ale CIB-ului" + +#: Ch-Advanced-Options.xml:13(entry) +msgid "Environment Variable" +msgstr "Variabilă de Mediu" + +#: Ch-Advanced-Options.xml:14(entry) +#: Ch-Advanced-Options.xml:60(entry) +#: Ch-Advanced-Options.xml:223(entry) +msgid "Description" +msgstr "Descriere" + +#: Ch-Advanced-Options.xml:17(entry) +msgid "CIB_user" +msgstr "CIB_user" + +#: Ch-Advanced-Options.xml:18(emphasis) +msgid "$USER" +msgstr "$USER" + +#: Ch-Advanced-Options.xml:18(entry) +msgid "The user to connect as. Needs to be part of the hacluster group on the target host. Defaults to " +msgstr "Userul sub care se va realiza conectarea. Trebuie să facă parte din grupul hacluster pe gazda destinaţie. Valoarea implicită este " + +#: Ch-Advanced-Options.xml:22(entry) +msgid "CIB_passwd" +msgstr "CIB_passwd" + +#: Ch-Advanced-Options.xml:23(entry) +msgid "The user's password. Read from the command line if unset" +msgstr "Parola utilizatorului. Este citită de la linia de comandă dacă nu este setată" + +#: Ch-Advanced-Options.xml:26(entry) +msgid "CIB_server" +msgstr "CIB_server" + +#: Ch-Advanced-Options.xml:27(emphasis) +msgid "localhost" +msgstr "localhost" + +#: Ch-Advanced-Options.xml:27(entry) +msgid "The host to contact. Defaults to ." +msgstr "Gazda care să fie contactată. Valoarea implicită este ." + +#: Ch-Advanced-Options.xml:30(entry) +msgid "CIB_port" +msgstr "CIB_port" + +#: Ch-Advanced-Options.xml:31(entry) +msgid "The port on which to contact the server. Required." +msgstr "Portul pe care să contacteze serverul. Cerinţă obligatorie." + +#: Ch-Advanced-Options.xml:34(entry) +msgid "CIB_encrypted" +msgstr "CIB_encrypted" + +#: Ch-Advanced-Options.xml:35(emphasis) +msgid "true" +msgstr "true" + +#: Ch-Advanced-Options.xml:35(entry) +msgid "Encrypt network traffic. Defaults to ." +msgstr "Criptează traficul de reţea. Valoarea implicită este ." + +#: Ch-Advanced-Options.xml:40(para) +msgid "So if c001n01 is an active cluster node and is listening on 1234 for connections, and someguy is a member of the hacluster group. Then the following would prompt for someguy's password and return the cluster's current configuration:" +msgstr "Deci dacă c001n01 este un nod activ de cluster şi ascultă pentru conexiuni pe 1234, iar vreun_tip este un membru al grupului hacluster. Atunci următoarele ar cere parola lui vreun_tip şi ar returna configuraţia curentă a clusterului:" + +#: Ch-Advanced-Options.xml:45(userinput) +#, no-wrap +msgid "" +"\n" +" export CIB_port=1234; export CIB_server=c001n01; export CIB_user=someguy;\n" +" cibadmin -Q\n" +"\t" +msgstr "" +"\n" +" export CIB_port=1234; export CIB_server=c001n01; export CIB_user=vreun_tip;\n" +" cibadmin -Q\n" +"\t" + +#: Ch-Advanced-Options.xml:50(para) +msgid "For security reasons, the cluster does not listen remote connections by default. If you wish to allow remote access, you need to set the remote-tls-port (encrypted) or remote-clear-port (unencrypted) top-level options (ie. those kept in the cib tag , like num_updates and epoch)." +msgstr "Din motive de securitate, clusterul nu ascultă pentru conexiuni la distanţă în mod implicit. Dacă doriţi să permiteţi accesul de la distanţă, trebuie să setaţi opţiunile primare remote-tls-port (criptat) sau remote-clear-port (necriptat) (ex. acelea stocate în tag-ul cib, precum num_updates şi epoch)." + +#: Ch-Advanced-Options.xml:55(title) +msgid "Extra top-level CIB options for remote access" +msgstr "Opţiuni primare suplimentare de CIB pentru acces la distanţă" + +#: Ch-Advanced-Options.xml:59(entry) +#: Ch-Advanced-Options.xml:222(entry) +msgid "Field" +msgstr "Câmp" + +#: Ch-Advanced-Options.xml:63(entry) +msgid "remote-tls-port" +msgstr "remote-tls-port" + +#: Ch-Advanced-Options.xml:64(emphasis) +#: Ch-Advanced-Options.xml:68(emphasis) +msgid "none" +msgstr "none" + +#: Ch-Advanced-Options.xml:64(entry) +msgid "Listen for encrypted remote connections on this port. Default: " +msgstr "Ascultă pentru conexiuni de la distanţă criptate pe acest port. Valoarea implicită: " + +#: Ch-Advanced-Options.xml:67(entry) +msgid "remote-clear-port" +msgstr "remote-clear-port" + +#: Ch-Advanced-Options.xml:68(entry) +msgid "Listen for plaintext remote connections on this port. Default: " +msgstr "Ascultă pentru conexiuni de la distanţă în clar pe acest port. Valoarea implicită: " + +#: Ch-Advanced-Options.xml:75(title) +msgid "Specifying When Recurring Actions are Performed" +msgstr "Specificând Când Acţiunile Recurente sunt Efectuate" + +#: Ch-Advanced-Options.xml:76(para) +msgid "By default, recurring actions are scheduled relative to when the resource started. So if your resource was last started at 14:32 and you have a backup set to be performed every 24 hours, then the backup will always run at in the middle of the business day - hardly desirable." +msgstr "În mod implicit, acţiunile recurente sunt programate în mod relativ faţă de când a fost pornită resursa. Deci dacă resursa voastră a fost pornită la 14:32 şi aveţi un backup setat să fie executat la fiecare 24 de ore, atunci backup-ul va rula întotdeauna în mijlocul zilei de lucru - deloc de dorit." + +#: Ch-Advanced-Options.xml:80(para) +msgid "To specify a date/time that the operation should be relative to, set the operation's interval-origin. The cluster uses this point to calculate the correct start-delay such that the operation will occur at origin + (interval * N)." +msgstr "Pentru a specifica un/o timp/dată faţă de care ar trebui să fie relativă operaţiunea, setaţi interval-origin pentru operaţiune. Clusterul foloseşte acest punct pentru a calcula un start-delay corect astfel încât operaţiunea să se întâmple la origine + (interval * N)." + +#: Ch-Advanced-Options.xml:84(para) +msgid "So if the operation's interval is 24h, it's interval-origin is set to 02:00 and it is currently 14:32, then the cluster would initiate the operation with a start delay of 11 hours and 28 minutes. If the resource is moved to another node before 2am, then the operation is of course cancelled." +msgstr "Deci dacă intervalul operaţiunii este de 24 de ore, parametrul interval-origin este setat la 02:00 şi acum este 14:32, atunci clusterul va iniţia operaţiunea cu un start-delay de 11 ore şi 28 de minute. Dacă resursa este mutată pe un alt nod înainte de ora 2 dimineaţa, atunci operaţiunea este desigur anulată." + +#: Ch-Advanced-Options.xml:88(para) +msgid "The value specified for interval and interval-origin can be any date/time conforming to the ISO8601 standard. By way of example, to specify an operation that would run on the first Monday of 2009 and every Monday after that you would add:" +msgstr "Valoarea specificată pentru interval şi interval-origin poate fi orice dată/timp ce se conformează cu standardul ISO8601. Spre exemplu, pentru a specifica o operaţiune care ar rula în prima zi de Luni din 2009 şi în fiecare zi de Luni de atunci înainte aţi adauga:" + +#: Ch-Advanced-Options.xml:93(title) +msgid "Specifying a Base for Recurring Action Intervals" +msgstr "Specificând o Bază pentru Intervalele Acţiunilor Recurente" + +#: Ch-Advanced-Options.xml:94(programlisting) +#, no-wrap +msgid "" +"\n" +" <op id=\"my-weekly-action\" name=\"custom-action\" interval=\"P7D\" interval-origin=\"2009-W01-1\"/>\n" +"\t" +msgstr "" +"\n" +" <op id=\"my-weekly-action\" name=\"custom-action\" interval=\"P7D\" interval-origin=\"2009-W01-1\"/>\n" +"\t" + +#: Ch-Advanced-Options.xml:100(title) +msgid "Moving Resources" +msgstr "Mutarea Resurselor" + +#: Ch-Advanced-Options.xml:102(title) +msgid "Manual Intervention" +msgstr "Intervenţie Manuală" + +#: Ch-Advanced-Options.xml:103(para) +msgid "There are primarily two occasions when you would want to move a resource from it's current location: when the whole node is under maintenance and when a single resource needs to be moved." +msgstr "Sunt în principal două ocazii în care aţi vrea să mutaţi o resursă de pe locaţia ei curentă: când întregul nod este sub mentenanţă şi când o singură resursă trebuie mutată." + +#: Ch-Advanced-Options.xml:104(para) +msgid "In the case where everything needs to move, since everything eventually comes down to a score, you could create constraints for every resource you have preventing it from running on that node. While the configuration can seem convoluted at times, not even we would require this of administrators." +msgstr "În cazul în care totul trebuie mutat, din moment ce totul ajunge eventual să ţină de un scor, aţi putea crea restricţii pentru fiecare resursă pe care o aveţi împiedicând-o din a mai rula pe acel nod. În timp ce configuraţia poate părea complicată în anumite momente, nici chiar noi nu am solicita acest lucru de la administratori." + +#: Ch-Advanced-Options.xml:108(para) +msgid "Instead one can set a special node attribute which tells the cluster \"don't let anything run here\". There is even a helpful tool to help query and set it called crm_standby. To check the standby status of the current machine, simply run:" +msgstr "În schimb aţi putea seta un atribut special de nod care îi spune clusterului \"nu lăsa nimic să ruleze aici\". Există chiar şi un utilitar pentru a ajuta la interogarea şi setarea acestuia numit crm_standby. Pentru a verifica status-ul stării de aşteptare pe maşina curentă, pur şi simplu rulaţi:" + +#: Ch-Advanced-Options.xml:113(command) +msgid "crm_standby --get-value" +msgstr "crm_standby --get-value" + +#: Ch-Advanced-Options.xml:114(para) +msgid "A value of true indicates that the node is NOT able to host any resources and a value of false indicates that it CAN. You can also check the status of other nodes in the cluster by specifying the --node-uname option. Eg." +msgstr "O valoare de adevăr indică faptul că nodul NU este capabil să găzduiască resurse şi o valoare de fals indică faptul că acesta POATE. Puteţi să verificaţi de asemenea status-ul celorlalte noduri din cluster specificând opţiunea --node-uname. Ex." + +#: Ch-Advanced-Options.xml:118(command) +msgid "crm_standby --get-value --node-uname sles-2" +msgstr "crm_standby --get-value --node-uname sles-2" + +#: Ch-Advanced-Options.xml:119(para) +msgid "To change the current node's standby status, use --attr-value instead of --get-value. Eg." +msgstr "Pentru a schimba status-ul stării de aşteptare a nodului curent, folosiţi --attr-value în loc de --get-value. Ex." + +#: Ch-Advanced-Options.xml:120(command) +msgid "crm_standby --attr-value" +msgstr "crm_standby --attr-value" + +#: Ch-Advanced-Options.xml:121(para) +msgid "Again, you can change another host's value by supplying a host name with --node-uname." +msgstr "Din nou, puteţi schimba valoarea altei gazde prin furnizarea unui hostname cu --node-uname." + +#: Ch-Advanced-Options.xml:122(para) +msgid "When only one resource is required to move, we do this by creating location constraints. However once again we provide a user friendly shortcut as part of the crm_resource command which creates and modifies the extra constraints for you. If Email was running on sles-1 and you wanted it moved to a specific location, the command would look something like:" +msgstr "Când doar o resursă este necesar a fi mutată, realizăm acest lucru prin crearea de restricţii de locaţie. În schimb încă o dată furnizăm utilizatorului o scurtătură prietenoasă ca parte din comanda crm_resource care creează şi modifică restricţiile suplimentare pentru voi. Dacă Email rula pe sles-1 şi doreaţi mutarea acesteia pe o locaţie specifică, comanda ar arăta ceva de genul:" + +#: Ch-Advanced-Options.xml:127(command) +#: Ch-Advanced-Options.xml:135(command) +msgid "crm_resource -M -r Email -H sles-2" +msgstr "crm_resource -M -r Email -H sles-2" + +#: Ch-Advanced-Options.xml:128(para) +msgid "Behind the scenes, the tool will create the following location constraint:" +msgstr "În culise, utilitarul va crea următoarea restricţie de locaţie:" + +#: Ch-Advanced-Options.xml:130(programlisting) +#, no-wrap +msgid "" +"\n" +" <rsc_location rsc=\"Email\" node=\"sles-2\" score=\"INFINITY\"/>\n" +"\t " +msgstr "" +"\n" +" <rsc_location rsc=\"Email\" node=\"sles-2\" score=\"INFINITY\"/>\n" +"\t " + +#: Ch-Advanced-Options.xml:134(para) +msgid "It is important to note that subsequent invocations of crm_resource -M are not cumulative. So if you ran:" +msgstr "Este important de menţionat că invocări ulterioare ale crm_resource -M nu sunt cumulative. Deci dacă aţi rula:" + +#: Ch-Advanced-Options.xml:136(command) +msgid "crm_resource -M -r Email -H sles-3" +msgstr "crm_resource -M -r Email -H sles-3" + +#: Ch-Advanced-Options.xml:137(para) +msgid "then it is as if you had never performed the first command." +msgstr "atunci ar fi ca şi când nu aţi fi efectuat niciodată prima comandă." + +#: Ch-Advanced-Options.xml:138(para) +msgid "To allow the resource to move back again, use:" +msgstr "Pentru a permite resursei să se mute înapoi, folosiţi:" + +#: Ch-Advanced-Options.xml:139(command) +#: Ch-Advanced-Options.xml:146(command) +msgid "crm_resource -U -r Email" +msgstr "crm_resource -U -r Email" + +#: Ch-Advanced-Options.xml:140(para) +msgid "Note the use of the word allow. The resource can move back to its original location but, depending on resource stickiness, it may stay where it is. To be absolutely certain that it moves back to sles-1, move it there before issuing the call to crm_resource -U:" +msgstr "Luaţi aminte de folosirea cuvântului allow. Resursa se poate muta înapoi la locaţia originală a acesteia însă, în funcţie de adezivitatea resursei, ar putea să rămână acolo unde este. Pentru a fi absolut siguri că se mută înapoi pe sles-1, mutaţi-o acolo înainte de a apela crm_resource -U:" + +#: Ch-Advanced-Options.xml:145(command) +msgid "crm_resource -M -r Email -H sles-1" +msgstr "crm_resource -M -r Email -H sles-1" + +#: Ch-Advanced-Options.xml:147(para) +msgid "Alternatively, if you only care that the resource should be moved from its current location, try" +msgstr "Ca alternativă, dacă vă pasă doar că resursa ar trebui să fie mutată din locaţia ei curentă, încercaţi" + +#: Ch-Advanced-Options.xml:148(command) +msgid "crm_resource -M -r Email" +msgstr "crm_resource -M -r Email" + +#: Ch-Advanced-Options.xml:149(para) +msgid "Which will instead create a negative constraint. Eg." +msgstr "Care va crea în schimb o restricţie negativă. Ex." + +#: Ch-Advanced-Options.xml:150(para) +msgid "<rsc_location rsc=\"Email\" node=\"sles-1\" score=\"-INFINITY\"/>" +msgstr "<rsc_location rsc=\"Email\" node=\"sles-1\" score=\"-INFINITY\"/>" + +#: Ch-Advanced-Options.xml:151(para) +msgid "This will achieve the desired effect but will also have long-term consequences. As the tool will warn you, the creation of a -INFINITY constraint will prevent the resource from running on that node until crm_resource -U is used. This includes the situation where every other cluster node is no longer available." +msgstr "Acest lucru va atinge efectul scontat dar va avea consecinţe pe termen lung. Aşa cum utilitarul vă va avertiza de altfel, crearea unei restricţii cu -INFINITY va împiedica resursa de a mai rula pe acel nod până ce comanda crm_resource -U va fi folosită. Acesta include situaţia în care oricare alt nod din cluster nu mai este disponibil." + +#: Ch-Advanced-Options.xml:156(para) +msgid "In some cases, such as when resource stickiness is set to INFINITY, it is possible that you will end up with the problem described in . The tool can detect some of these cases and deals with them by also creating both a positive and negative constraint. Eg." +msgstr "În anumite cazuri, precum cel în care adezivitatea resursei este setată la INFINITY, este posibil să ajungeţi la problema descrisă în . Utilitarul poate detecta unele din aceste cazuri şi le tratează prin crearea atât de restricţii pozitive cât şi negative. Ex." + +#: Ch-Advanced-Options.xml:160(para) +msgid "Email prefers sles-1 with a score of -INFINITY" +msgstr "Email preferă sles-1 cu un scor de -INFINITY" + +#: Ch-Advanced-Options.xml:161(para) +msgid "Email prefers sles-2 with a score of INFINITY" +msgstr "Email preferă sles-2 cu un scor de -INFINITY" + +#: Ch-Advanced-Options.xml:162(para) +msgid "which has the same long-term consequences as discussed earlier." +msgstr "care are aceleaşi consecinţe pe termen lung precum am discutat anterior." + +#: Ch-Advanced-Options.xml:165(title) +msgid "Moving Resources Due to Failure" +msgstr "Mutarea Resurselor Datorită Eşecului" + +#: Ch-Advanced-Options.xml:168(para) +msgid "The naming of this option was unfortunate as it is easily confused with true migration, the process of moving a resource from one node to another without stopping it. Xen virtual guests are the most common example of resources that can be migrated in this manner." +msgstr "Denumirea acestei opţiuni este nefericită deoarece este uşor confundată cu migrarea adevărată, procesul mutării unei resurse de pe un nod pe altul fără oprirea acesteia. Oaspeţii virtuali de Xen sunt cel mai comun exemplu de resurse care pot fi migrate în această manieră." + +#: Ch-Advanced-Options.xml:166(para) +msgid "New in 1.0 is the concept of a migration threshold . Simply define migration-threshold=N for a resource and it will migrate to a new node after N failures. There is no threshold defined by default. To determine the resource's current failure status and limits, use crm_mon --failcounts" +msgstr "Nou în 1.0 este conceptul unui prag de migrare . Pur şi simplu definiţi migration-threshold=N pentru o resursă şi aceasta va migra pe un nod nou după N eşecuri. Nu este definit nici un prag în mod implicit. Pentru a determina status-ul de eşec şi limitele curente ale resursei, folosiţi crm_mon --failcounts" + +#: Ch-Advanced-Options.xml:177(para) +msgid "By default, once the threshold has been reached, node will no longer be allowed to run the failed resource until the administrator manually resets the resource's failcount using crm_failcount (after hopefully first fixing the failure's cause). However it is possible to expire them by setting the resource's failure-timeout option." +msgstr "În mod implicit, odată ce pragul a fost atins, nodului nu îi va mai fi permisă rularea resursei care a eşuat până ce un administrator resetează manual failcount-ul resursei folosind crm_failcount (asta sperând după ce cauza eşecului resursei a fost reparată). Totodată este posibilă expirarea acestora prin setarea opţiunii failure-timeout resursei." + +#: Ch-Advanced-Options.xml:181(para) +msgid "So a setting of migration-threshold=2 and failure-timeout=60s would cause the resource to move to a new node after 2 failures and potentially allow it to move back (depending on the stickiness and constraint scores) after one minute." +msgstr "Prin urmare setarea migration-threshold=2 şi failure-timeout=60s ar conduce resursa la mutarea pe un nod nou după 2 eşecuri şi potenţial îi va permite să se mute înapoi (în funcţie de scorurile de adezivitate şi restrictie) după un minut." + +#: Ch-Advanced-Options.xml:182(para) +msgid "There are two exceptions to the migration threshold concept and occur when a resource either fails to start or fails to stop. Start failures cause the failcount to be set to INFINITY and thus always cause the resource to move immediately." +msgstr "Sunt două excepţii la conceptul de prag de migrare şi se întâmplă atunci când o resursă fie eşuează să pornească sau eşuează să se oprească. Eşecurile de pornire fac failcount-ul să fie setat la INFINITY şi prin urmare provoacă mutarea imediată a resursei." + +#: Ch-Advanced-Options.xml:186(para) +msgid "Stop failures are slightly different and crucial. If a resource fails to stop and STONITH is enabled, then the cluster will fence the node in order to be able to start the resource elsewhere. If STONITH is not enabled, then the cluster has no way to continue and will not try to start the resource elsewhere, but will try to stop it again after the failure timeout." +msgstr "Eşecurile la oprire sunt puţin diferite şi cruciale. Dacă o resursă eşuează de a se opri şi STONITH este activat, atunci clusterul va evacua nodul pentru a putea să pornească resursa în altă parte. Dacă STONITH nu este activat, atunci clusterul nu are nici o mod de a continua şi nu va încerca să pornească resursa în altă parte, dar va încerca să o oprească din nou după ce se depaşeşte timpul limită al eşecului." + +#: Ch-Advanced-Options.xml:191(para) +msgid "Please read before enabling this option." +msgstr "Vă rugăm să citiţi înainte de activarea acestei opţiuni." + +#: Ch-Advanced-Options.xml:194(title) +msgid "Moving Resources Due to Connectivity Changes" +msgstr "Mutarea Resurselor Din Cauza Schimbărilor de Conectivitate" + +#: Ch-Advanced-Options.xml:195(para) +msgid "Setting up the cluster to move resources when external connectivity is lost, is a two-step process." +msgstr "Setarea clusterului pentru a muta resursele când conectivitatea externă este pierdută, este un proces în doi paşi." + +#: Ch-Advanced-Options.xml:197(title) +msgid "Tell Pacemaker to monitor connectivity" +msgstr "Spuneţi Pacemaker-ului să monitorizeze conectivitatea" + +#: Ch-Advanced-Options.xml:202(para) +msgid "The attribute name is customizable which allows multiple ping groups to be defined" +msgstr "Numele atributului este personalizabil ceea ce vă permite definirea de grupuri multiple de ping" + +#: Ch-Advanced-Options.xml:198(para) +msgid "To do this, you need to add a ping resource to the cluster. The ping resource uses the system utility of the same name to a test if list of machines (specified by DNS hostname or IPv4/ IPv6 address) are reachable and uses the results to maintain a node attribute normally called pingd. " +msgstr "Pentru a realiza acest lucru, trebuie să adăugaţi o resursă ping la cluster. Resursa ping foloseşte utilitarul de sistem cu acelaşi nume pentru a testa dacă o listă de maşini (specificată după numele DNS sau adresa IPV4/IPV6) sunt accesibile şi foloseşte rezultatele pentru a menţine un atribut de nod numit în mod normal pingd. " + +#: Ch-Advanced-Options.xml:205(para) +msgid "Older versions of Heartbeat required users to add ping nodes to ha.cf - this is no longer required." +msgstr "Versiuni mai vechi de Heartbeat necesitau ca utilizatorii să adauge noduri de ping în ha.cf - acest lucru nu mai este necesar." + +#: Ch-Advanced-Options.xml:208(para) +msgid "Older versions of Pacemaker used a custom binary called pingd for this functionality, this is now deprecated in favor of ping. If your version of Pacemaker does not contain the ping agent, you can download the latest version from: " +msgstr "Versiuni mai vechi de Pacemaker foloseau un binar special numit pingd pentru această funcţionalitate, acest lucru este acum depreciat în favoarea comenzii ping. Dacă versiunea voastră de Pacemaker nu conţine agentul ping, puteţi descărca cea mai recentă versiune de la: " + +#: Ch-Advanced-Options.xml:213(para) +msgid "Normally the resource will run on all cluster nodes, which means that you'll need to create a clone. A template for this can be found below along with a description of the most interesting parameters." +msgstr "În mod normal resursa va rula pe toate nodurile clusterului, ceea ce înseamnă că va trebui să creaţi o clonă. Un template pentru aceasta poate fi găsit mai jos împreună cu o descriere ale parametrilor cei mai interesanţi." + +#: Ch-Advanced-Options.xml:218(title) +msgid "Common Options for a 'ping' Resource" +msgstr "Opţiuni Obişnuite pentru o Resursă 'ping'" + +#: Ch-Advanced-Options.xml:228(entry) +msgid "dampen" +msgstr "dampen" + +#: Ch-Advanced-Options.xml:229(entry) +msgid "The time to wait (dampening) for further changes occur. Use this to prevent a resource from bouncing around the cluster when cluster nodes notice the loss of connectivity at slightly different times." +msgstr "Timpul pe care să îl aştepte (atenuarea) pentru alte modificări să se întâmple. Folosiţi acesta pentru a preveni o resursă de a ricoşa de colo-colo prin cluster atunci când nodurile observă pierderea conectivităţii la intervale uşor diferite de timp." + +#: Ch-Advanced-Options.xml:232(entry) +msgid "multiplier" +msgstr "multiplier" + +#: Ch-Advanced-Options.xml:233(entry) +msgid "The number by which to multiply the number of connected ping nodes by. Useful when there are multiple ping nodes configured." +msgstr "Numărul cu care să se multiplice numărul de noduri ping conectate. Folositor când sunt mai multe noduri ping configurate." + +#: Ch-Advanced-Options.xml:236(entry) +msgid "host_list" +msgstr "host_list" + +#: Ch-Advanced-Options.xml:237(entry) +msgid "The machines to contact in order to determine the current connectivity status. Allowed values include resolvable DNS hostnames, IPv4 and IPv6 addresses." +msgstr "Maşinile pe care să le contacteze pentru a determina status-ul curent de conectivitate. Valorile permise includ hostname-uri DNS rezolvabile, adrese IPV4 şi IPV6." + +#: Ch-Advanced-Options.xml:243(title) +msgid "An example ping cluster resource, checks node connectivity once every minute" +msgstr "Un exemplu de resursă ping în cluster, verifică odată pe minut conectivatea nodului" + +#: Ch-Advanced-Options.xml:262(para) +msgid "You're only half done. The next section deals with telling Pacemaker how to deal with the connectivity status that ocf:pacemaker:ping is recording." +msgstr "Aţi terminat doar jumătate. Secţiunea următoare se ocupă cu informarea Pacemaker-ului despre cum să se comporte cu status-ul conectivităţii pe care ocf:pacemaker:ping îl înregistrează." + +#: Ch-Advanced-Options.xml:269(title) +msgid "Tell Pacemaker how to interpret the connectivity data" +msgstr "Spuneţi Pacemaker-ului cum să interpreteze datele de conectivitate" + +#: Ch-Advanced-Options.xml:270(para) +msgid "NOTE: Before reading the following, please make sure you have read and understood above." +msgstr "NOTĂ: Înainte de a citi următoarele, vă rugăm să vă asiguraţi că aţi citit şi aţi înteles de mai sus." + +#: Ch-Advanced-Options.xml:271(para) +msgid "There are a number of ways to use the connectivity data provided by Heartbeat. The most common setup is for people to have a single ping node and want to prevent the cluster from running a resource on any unconnected node." +msgstr "Sunt un număr de feluri în care se pot folosi datele de conectivitate furnizate de Heartbeat. Cel mai întâlnit setup este ca oamenii să aibe un singur nod de ping şi să împiedice clusterul de a rula o resursă pe orice nod neconectat." + +#: Ch-Advanced-Options.xml:276(title) +msgid "Don't run on unconnected nodes" +msgstr "Nu rula pe noduri neconectate" + +#: Ch-Advanced-Options.xml:287(para) +msgid "A more complex setup is to have a number of ping nodes configured. You can require the cluster to only run resources on nodes that can connect to all (or a minimum subset) of them" +msgstr "Un setup mai complex este acela de a avea un număr de noduri de ping configurate. Poţi solicita clusterului să ruleze resursele pe nodurile care se pot conecta la toate (sau doar un subset din) acestea" + +#: Ch-Advanced-Options.xml:292(title) +msgid "Run only on nodes connected to 3 or more ping nodes (assumes multiplier is set to 1000)" +msgstr "Rulează doar pe noduri conectate la 3 sau mai multe noduri de ping (presupune că multiplier este setat la 1000)" + +#: Ch-Advanced-Options.xml:303(para) +msgid "or instead you can tell the cluster only to prefer nodes with the most connectivity. Just be sure to set the multiplier to a value higher than that of resource-stickiness (and don't set either of them to INFINITY)." +msgstr "sau în schimb puteţi spune clusterului să prefere doar nodurile cu cea mai mare conectivitate. Doar să vă asiguraţi să setaţi multiplicatorul la o valoare mai mare decât cea a resource-stickiness (şi să nu setaţi oricare dintre acestea la INFINITY)." + +#: Ch-Advanced-Options.xml:308(title) +msgid "Prefer the node with the most connected ping nodes" +msgstr "Preferă nodul cu cele mai multe noduri de ping conectate" + +#: Ch-Advanced-Options.xml:319(para) +msgid "It is perhaps easier to think of this in terms of the simple constraints that the cluster translates it into. For example, if sles-1 is connected to all 5 ping nodes but sles-2 is only connected to 2, then it would be as if you instead had the following constraints in your configuration:" +msgstr "Este probabil mai simplu să vă gândiţi la acest lucru în termenii simplelor restricţii în care clusterul traduce acest lucru. De exemplu, dacă sles-1 este conectat la toate cele 5 noduri de ping dar sles-2 este conectat doar la 2, atunci ar fi la fel ca şi când aţi avea următoarele restricţii în configuraţia voastră:" + +#: Ch-Advanced-Options.xml:324(title) +msgid "How the cluster translates the pingd constraint" +msgstr "Cum traduce clusterul restricţia pingd" + +#: Ch-Advanced-Options.xml:332(para) +msgid "The advantage being that you don't have to manually update them whenever your network connectivity changes." +msgstr "Avantajul fiind că nu mai trebuie să le actualizaţi manual de fiecare dată când conectivitatea de reţea se schimbă." + +#: Ch-Advanced-Options.xml:333(para) +msgid "You can also combine the concepts above into something even more complex. The example below shows how you can prefer the node with the most connected ping nodes provided they have connectivity to at least three (assuming multiplier is set to 1000)." +msgstr "Puteţi de asemenea să combinaţi conceptele de mai sus în ceva chiar mai complex de atât. Exemplul de mai jos arată cum puteţi prefera nodul cu cele mai multe noduri de ping conectate cu cerinţa că acestea trebuie să aibe conectivitate la minim trei (presupunând că multiplicatorul este setat la 1000)." + +#: Ch-Advanced-Options.xml:338(title) +msgid "A more complex example of choosing a location based on connectivity" +msgstr "Un exemplu mai complex pentru alegerea locaţiei pe baza conectivităţii" + +#: Ch-Advanced-Options.xml:355(title) +msgid "Resource Migration" +msgstr "Migrarea Resurselor" + +#: Ch-Advanced-Options.xml:356(para) +msgid "Some resources, such as Xen virtual guests, are able to move to another location without lose of state. We call this resource migration and is different from the normal practice of stopping the resource on the first machine and starting it elsewhere." +msgstr "Unele resurse, precum oaspeţii virtuali de Xen, sunt capabili să se mute în altă locaţie fără pierderea stării. Numim acest lucru migrarea resurselor şi este diferit de practica normală a opririi resurselor pe prima maşină şi apoi pornirea acestora în altă parte." + +#: Ch-Advanced-Options.xml:360(para) +msgid "Not all resources are able to migrate, see the Migration Checklist below, and those that can won't do so in all situations. Conceptually there are two requirements from which the other prerequisites follow:" +msgstr "Nu toate resursele sunt capabile de migrare, vedeţi Lista de Migrare de mai jos, şi mai sunt cele care nu pot să facă acest lucru în toate situaţiile. În mod conceptual sunt două cerinţe din care celelalte necesităţi urmează:" + +#: Ch-Advanced-Options.xml:365(para) +msgid "the resource must be active and healthy at the old location" +msgstr "resursa trebuie să fie activă şi sănătoasă în locaţia veche" + +#: Ch-Advanced-Options.xml:366(para) +msgid "everything required for the resource to run must be available on both the old and new locations" +msgstr "tot ce este necesar pentru ca resursa să funcţioneze trebuie să fie disponibil atât la vechea cât şi la noua locaţie" + +#: Ch-Advanced-Options.xml:368(para) +msgid "The cluster is able to accommodate both push and pull migration models by requiring the resource agent to support two new actions: migrate_to (performed on the current location) and migrate_from (performed on the destination)." +msgstr "Clusterul este capabil să acomodeze atât modele de migrare de tip push cât şi pull prin solicitarea ca agentul de resursă să suporte două noi acţiuni: migrate_to (efectuată pe locaţia curentă) şi migrate_from (efectuată pe destinaţie)." + +#: Ch-Advanced-Options.xml:369(para) +msgid "In push migration, the process on the current location transfers the to the new location where is it later activated. In this scenario, most of the work would be done in the migrate_to action and, if anything, the activation would occur during migrate_from." +msgstr "În migrarea de tip push, procesul de pe locaţia curentă se transferă pe locaţia nouă unde este activat mai târziu. În acest scenariu, majoritatea muncii ar fi realizată în acţiunea migrate_to şi activarea ar avea loc în timpul migrate_from." + +#: Ch-Advanced-Options.xml:373(para) +msgid "Conversely for pull, the migrate_to action is practically empty and migrate_from does most of the work, extracting the relevant resource state from the old location and activating it." +msgstr "În egală măsură pentru pull, acţiunea migrate_to este practic fără conţinut şi migrate_from realizează majoritatea muncii, extrăgând starea relevantă a resursei de la locaţia veche şi activând-o." + +#: Ch-Advanced-Options.xml:374(para) +msgid "There is no wrong or right way to implement migration for your service, as long as it works." +msgstr "Nu există un mod greşit sau corect de a implementa migrarea serviciului vostru, atâta timp cât funcţionează." + +#: Ch-Advanced-Options.xml:376(title) +msgid "Migration Checklist" +msgstr "Lista de Migrare" + +#: Ch-Advanced-Options.xml:378(para) +msgid "The resource may not be a clone." +msgstr "Resursa nu poate fi o clonă." + +#: Ch-Advanced-Options.xml:379(para) +msgid "The resource must use an OCF style agent." +msgstr "Resursa trebuie să folosească un agent de stilul OCF." + +#: Ch-Advanced-Options.xml:380(para) +msgid "The resource must not be in a failed or degraded state." +msgstr "Resursa nu trebuie să fie într-o stare degradată sau să fi eşuat." + +#: Ch-Advanced-Options.xml:381(para) +msgid "The resource must not, directly or indirectly, depend on any primitive or group resources." +msgstr "Resursa trebuie să nu depindă, în mod direct sau indirect, de orice primitivă sau grup de resurse." + +#: Ch-Advanced-Options.xml:382(para) +msgid "The resources must support two new actions: migrate_to and migrate_from and advertise them in its metadata." +msgstr "Resursa trebuie să suporte două noi acţiuni: migrate_to şi migrate_from şi trebuie să le anunţe în meta-informaţiile proprii." + +#: Ch-Advanced-Options.xml:383(para) +msgid "The resource must have the allow-migrate meta-attribute set to true (not the default)." +msgstr "Resursa trebuie să aibe meta-atributul allow-migrate setat pe true (nu pe valoarea implicită)" + +#: Ch-Advanced-Options.xml:385(para) +msgid "If the resource depends on a clone, and at the time the resource needs to be move, the clone has instances that are stopping and instances that are starting, then the resource will be moved in the traditional manner. The Policy Engine is not yet able to model this situation correctly and so takes the safe (yet less optimal) path." +msgstr "Dacă resursa depinde de o clonă, iar la momentul când resursa trebuie să fie mutată, clona are instanţe care se opresc şi instanţe care pornesc, atunci resursa va fi mutată în modul tradiţional. Policy Engine-ul nu este capabil încă să modeleze această situaţie în mod corect aşa că ia calea (mai puţin optimă) dar mai sigură." + +#: Ch-Advanced-Options.xml:393(title) +msgid "Reusing Rules, Options and Sets of Operations" +msgstr "Refolosirea Regulilor, Opţiunilor şi a Setului de Operaţiuni" + +#: Ch-Advanced-Options.xml:394(para) +msgid "Sometimes a number of constraints need to use the same set of rules and resources need to set the same options and parameters. To simplify this situation, you can refer to an existing object using an id-ref instead of an id." +msgstr "Câteodată un număr de restricţii trebuie să folosească acelaşi set de reguli şi resursele trebuie sa seteze aceleaşi opţiuni şi parametri. Pentru a simplifica această situaţie, puteţi face referinţă la un obiect existent folosind un id-ref în loc de un id." + +#: Ch-Advanced-Options.xml:398(para) +msgid "So if for one resource you have" +msgstr "Deci dacă pentru o resursă aveţi" + +#: Ch-Advanced-Options.xml:408(para) +msgid "Then instead of duplicating the rule for all your other resources, you can instead specify" +msgstr "Atunci în loc să duplicaţi regula pentru toate celelalte resurse, puteţi specifica în schimb" + +#: Ch-Advanced-Options.xml:410(title) +msgid "Referencing rules from other constraints" +msgstr "Realizând referinţe către reguli din alte restricţii" + +#: Ch-Advanced-Options.xml:420(para) +msgid "The cluster will insist that the rule exists somewhere. Attempting to add a reference to a non-existing rule will cause a validation failure, as will attempting to remove a rule that is referenced elsewhere." +msgstr "Clusterul va insista că regula există undeva. Încercând să adaugaţi o referinţă către o regulă ce nu există va cauza un eşec al validării, la fel ca şi încercarea de a înlătura regula care este referenţiată în altă parte." + +#: Ch-Advanced-Options.xml:425(para) +msgid "The same principle applies for meta_attributes and instance_attributes as illustrated in the example below" +msgstr "Acelaşi principiu se aplică pentru meta_attributes şi pentru instance_attributes după cum este prezentat în exemplul de mai jos" + +#: Ch-Advanced-Options.xml:427(title) +msgid "Referencing attributes, options and operations from other resources" +msgstr "Referenţierea atributelor, opţiunilor şi operaţiunilor din alte resurse" + +#: Ch-Advanced-Options.xml:456(title) +msgid "Reloading Services After a Definition Change" +msgstr "Reîncărcarea Serviciilor După Schimbarea unei Definiţii" + +#: Ch-Advanced-Options.xml:457(para) +msgid "The cluster automatically detects changes to the definition of services it manages. However, the normal response is to stop the service (using the old definition) and start it again (with the new definition). This works well, but some services are smart and can be told to use a new set of options without restarting." +msgstr "Clusterul detectează în mod automat schimbări ale definiţiei serviciilor pe care le gestionează. Totuşi, răspunsul normal este să oprească serviciul (folosind definiţia veche) şi să îl pornească din nou (cu definiţia nouă). Acest lucru functionează bine, dar unele servicii sunt inteligente şi li se poate spune să folosească un set nou de opţiuni fară să repornească." + +#: Ch-Advanced-Options.xml:466(para) +msgid "Accept the reload operation and perform any required actions." +msgstr "Acceptă operaţiunea reload şi efectuează acţiunile necesare." + +#: Ch-Advanced-Options.xml:467(para) +msgid "The steps required here depend completely on your application" +msgstr "Paşii necesitaţi aici depind complet de aplicaţia voastră" + +#: Ch-Advanced-Options.xml:469(title) +msgid "The DRBD Agent's Control logic for Supporting the reload Operation" +msgstr "Logica de Control pentru Suportarea Operaţiunii de reload a Agentului DRBD" + +#: Ch-Advanced-Options.xml:496(para) +msgid "Advertise the reload operation in the actions section of its metadata" +msgstr "Anunţă operaţiunea reload în secţiunea de actions din meta-informaţiile proprii" + +#: Ch-Advanced-Options.xml:498(title) +msgid "The DRBD Agent Advertising Support for the reload Operation" +msgstr "Anunţarea Suportului Operaţiunii de reload a Agentului DRBD" + +#: Ch-Advanced-Options.xml:546(para) +msgid "Advertise one or more parameters that can take effect using reload." +msgstr "Promovaţi unul sau mai mulţi parametri care pot intra în vigoare folosing reload." + +#: Ch-Advanced-Options.xml:547(para) +msgid "Any parameter with the unique set to 0 is eligable to be used in this way." +msgstr "Orice parametru cu unique setat pe 0 este eligibil să fie folosit în acest fel." + +#: Ch-Advanced-Options.xml:549(title) +msgid "Parameter that can be changed using reload" +msgstr "Parametru care poate fi schimbat folosind reload" + +#: Ch-Advanced-Options.xml:462(para) +msgid "To take advantage of this capability, your resource agent must: " +msgstr "Pentru a profita de această capabilitate, agentul vostru de resursă trebuie să: " + +#: Ch-Advanced-Options.xml:563(para) +msgid "Once these requirements are satisfied, the cluster will automatically know to reload, instead of restarting, the resource when a non-unique fields changes." +msgstr "Odată ce aceste cerinţe au fost satisfăcute, clusterul automat va şti să reîncarce, în loc să restarteze, resursa când un câmp non-unic se schimbă." + +#: Ch-Advanced-Options.xml:567(para) +msgid "The metadata is re-read when the resource is started. This may mean that the resource will be restarted the first time, even though you changed a parameter with unique=0" +msgstr "Meta-informaţiile sunt recitite când resursa este pornită. Acest lucru înseamnă că resursa va fi restartată prima data, deşi aţi schimbat un parametru cu unique=0" + +#: Ch-Advanced-Options.xml:573(para) +msgid "If both a unique and non-unique field is changed simultaneously, the resource will still be restarted." +msgstr "Dacă atât un câmp unic si non-unic sunt schimbate simultan, resursa tot va fi restartată." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ch-Advanced-Options.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ch-Advanced-Resources.po b/doc/Pacemaker_Explained/ro-RO/Ch-Advanced-Resources.po new file mode 100644 index 0000000000..07d6a88c13 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ch-Advanced-Resources.po @@ -0,0 +1,1008 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-24 07:42+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Bookmarks: 5,-1,-1,-1,-1,-1,-1,-1,-1,-1\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Ch-Advanced-Resources.xml:1(title) +msgid "Advanced Resource Types" +msgstr "Tipuri Avansate de Resurse" + +#: Ch-Advanced-Resources.xml:3(title) +msgid "Groups - A Syntactic Shortcut" +msgstr "Grupuri - O Scurtătură Sintactică" + +#: Ch-Advanced-Resources.xml:4(para) +msgid "One of the most common elements of a cluster is a set of resources that need to be located together, start sequentially and stop in the reverse order. To simplify this configuration we support the concept of groups." +msgstr "Unul dintre cele mai comune elemente ale unui cluster este un set de resurse care trebuie plasate împreună, pornesc secvenţial şi se opres în ordine inversă. Pentru a simplifica această configuraţie suportăm conceptul de grupuri." + +#: Ch-Advanced-Resources.xml:9(title) +msgid "An example group" +msgstr "Un exemplu de grup" + +#: Ch-Advanced-Resources.xml:23(para) +msgid "Although the example above contains only two resources, there is no limit to the number of resources a group can contain. The example is also sufficient to explain the fundamental properties of a group:" +msgstr "Deşi exemplul de mai sus conţine doar două resurse, nu este nici o limită asupra numărului de resurse pe care le poate conţine un grup. Exemplul este de asemenea suficient pentru a explica proprietăţile fundamentale ale unui grup:" + +#: Ch-Advanced-Resources.xml:28(para) +msgid "Resources are started in the order they appear in (Public-IP first, then Email)" +msgstr "Resursele sunt pornite în ordinea în care apar (întâi Public-IP, apoi Email)" + +#: Ch-Advanced-Resources.xml:29(para) +msgid "Resources are stopped in the reverse order to which they appear in (Email first, then Public-IP)" +msgstr "Resursele sunt oprite în ordine inversă faţă de cea în care apar (întâi Email, apoi Public-IP)" + +#: Ch-Advanced-Resources.xml:31(para) +msgid "If a resource in the group can't run anywhere, then nothing after that is allowed to run" +msgstr "Dacă o resursă din grup nu poate rula nicăieri, atunci nimic din ce urmează după aceasta nu îi este permis să ruleze" + +#: Ch-Advanced-Resources.xml:33(para) +msgid "If Public-IP can’t run anywhere, neither can Email" +msgstr "Dacă Public-IP nu poate rula nicăieri, nici Email nu va putea" + +#: Ch-Advanced-Resources.xml:34(para) +msgid "If Email can’t run anywhere, this does not affect Public-IP in any way" +msgstr "Dacă Email nu poate rula nicăieri, acest lucru nu afectează Public-IP în nici un fel" + +#: Ch-Advanced-Resources.xml:38(para) +msgid "The group above is logically equivalent to writing:" +msgstr "Grupul de deasupra este echivalent logic cu a scrie:" + +#: Ch-Advanced-Resources.xml:40(title) +msgid "How the cluster sees a group resource" +msgstr "Cum vede clusterul un grup de resurse" + +#: Ch-Advanced-Resources.xml:60(para) +msgid "Obviously as the group grows bigger, the reduced configuration effort can become significant." +msgstr "În mod evident pe măsură ce grupul creşte, efortul de configurare redus poate deveni semnificativ." + +#: Ch-Advanced-Resources.xml:62(title) +#: Ch-Advanced-Resources.xml:160(title) +#: Ch-Advanced-Resources.xml:442(title) +msgid "Properties" +msgstr "Proprietăţi" + +#: Ch-Advanced-Resources.xml:64(title) +msgid "Properties of a Group Resource" +msgstr "Proprietăţile unui Grup de Resurse" + +#: Ch-Advanced-Resources.xml:68(entry) +#: Ch-Advanced-Resources.xml:166(entry) +#: Ch-Advanced-Resources.xml:185(entry) +#: Ch-Advanced-Resources.xml:448(entry) +#: Ch-Advanced-Resources.xml:468(entry) +#: Ch-Advanced-Resources.xml:536(entry) +msgid "Field" +msgstr "Câmp" + +#: Ch-Advanced-Resources.xml:69(entry) +#: Ch-Advanced-Resources.xml:167(entry) +#: Ch-Advanced-Resources.xml:186(entry) +#: Ch-Advanced-Resources.xml:311(entry) +#: Ch-Advanced-Resources.xml:449(entry) +#: Ch-Advanced-Resources.xml:469(entry) +#: Ch-Advanced-Resources.xml:537(entry) +#: Ch-Advanced-Resources.xml:650(entry) +#: Ch-Advanced-Resources.xml:688(entry) +msgid "Description" +msgstr "Descriere" + +#: Ch-Advanced-Resources.xml:74(entry) +#: Ch-Advanced-Resources.xml:170(entry) +#: Ch-Advanced-Resources.xml:452(entry) +msgid "id" +msgstr "id" + +#: Ch-Advanced-Resources.xml:75(entry) +msgid "Your name for the group" +msgstr "Numele pe care îl daţi grupului" + +#: Ch-Advanced-Resources.xml:82(title) +#: Ch-Advanced-Resources.xml:178(title) +#: Ch-Advanced-Resources.xml:460(title) +msgid "Options" +msgstr "Opţiuni" + +#: Ch-Advanced-Resources.xml:83(para) +msgid "Options inherited from simple resources: priority, target-role, is-managed" +msgstr "Opţiuni moştenite de la resurse simple: priority, target-role, is-managed" + +#: Ch-Advanced-Resources.xml:86(title) +msgid "Using Groups" +msgstr "Folosirea Grupurilor" + +#: Ch-Advanced-Resources.xml:88(title) +#: Ch-Advanced-Resources.xml:224(title) +#: Ch-Advanced-Resources.xml:484(title) +msgid "Instance Attributes" +msgstr "Atributele Instanţelor" + +#: Ch-Advanced-Resources.xml:89(para) +msgid "Groups have no instance attributes, however any that are set here will be inherited by the group's children." +msgstr "Grupurile nu au atribute de instanţă, totuşi oricare ar fi setate aici vor fi moştenite de către copiii grupului." + +#: Ch-Advanced-Resources.xml:92(title) +#: Ch-Advanced-Resources.xml:228(title) +#: Ch-Advanced-Resources.xml:488(title) +msgid "Contents" +msgstr "Conţinut" + +#: Ch-Advanced-Resources.xml:93(para) +msgid "Groups may only contain a collection of primitive cluster resources. To refer to the child of a group resource, just use the child's id instead of the group's." +msgstr "Grupurile pot conţine numai o colecţie de resurse de cluster de tip primitive . Pentru a face referinţă la copilul unei resurse dintr-un grup, folosiţi pur şi simplu id-ul copilului în locul celui al grupului." + +#: Ch-Advanced-Resources.xml:99(title) +#: Ch-Advanced-Resources.xml:238(title) +#: Ch-Advanced-Resources.xml:521(title) +msgid "Constraints" +msgstr "Restricţii" + +#: Ch-Advanced-Resources.xml:100(para) +msgid "Although it is possible to reference the group's children in constraints, it is usually preferable to use the group's name instead." +msgstr "Deşi este posibil să referenţiezi copiii grupului în restricţii, este în mod uzual preferabil să folosiţi numele grupului în schimb." + +#: Ch-Advanced-Resources.xml:102(title) +msgid "Example constraints involving groups" +msgstr "Exemple de restricţii care implică grupuri" + +#: Ch-Advanced-Resources.xml:115(title) +#: Ch-Advanced-Resources.xml:273(title) +#: Ch-Advanced-Resources.xml:600(title) +msgid "Stickiness" +msgstr "Adezivitate" + +#: Ch-Advanced-Resources.xml:116(para) +msgid "Stickiness, the measure of how much a resource wants to stay where it is, is additive in groups. Every active member of the group will contribute its stickiness value to the group's total. So if the default resource-stickiness is 100 a group has seven members, five of which are active, then the group as a whole will prefer its current location with a score of 500." +msgstr "Adezivitatea, măsura a cât de mult vrea o resursă să rămână acolo unde este, este aditivă în grupuri. Fiecare membru activ al grupului va contribui cu valoarea adezivităţii acestuia la totalul grupului. Deci dacă valoarea implicită a resource-stickiness este 100 şi grupul are şapte membri, cinci din aceştia fiind activi, atunci grupul ca întreg va prefera locaţia curentă cu un scor de 500." + +#: Ch-Advanced-Resources.xml:123(title) +msgid "Clones - Resources That Should be Active on Multiple Hosts" +msgstr "Clone - Resurse Care Trebuie să fie Active pe Gazde Multiple" + +#: Ch-Advanced-Resources.xml:124(para) +msgid "Clones were initially conceived as a convenient way to start N instances of an IP resource and have them distributed throughout the cluster for load balancing. They have turned out to quite useful for a number of purposes including integrating with Red Hat's DLM, the fencing subsystem and OCFS2." +msgstr "Clonele au fost concepute iniţial ca o modalitate convenientă de a porni N instanţe ale unei resurse IP şi de a le avea distribuite de-a lungul clusterului pentru partajarea nivelului de încărcare. S-au dovedit a fi chiar utile pentru un număr de scopuri incluzând integrarea cu DLM-ul de la Red Hat, subsistemul de evacuare şi OCFS2." + +#: Ch-Advanced-Resources.xml:128(para) +msgid "You can clone any resource provided the resource agent supports it." +msgstr "Puteţi clona orice resursă atâta timp cât agentul de resursă suportă acest lucru." + +#: Ch-Advanced-Resources.xml:129(para) +msgid "Three types of cloned resources exist." +msgstr "Există trei tipuri de resurse clonate." + +#: Ch-Advanced-Resources.xml:131(para) +msgid "Anonymous" +msgstr "Anonime" + +#: Ch-Advanced-Resources.xml:132(para) +msgid "Globally Unique" +msgstr "Unice la nivel global" + +#: Ch-Advanced-Resources.xml:133(para) +msgid "Stateful" +msgstr "Stateful" + +#: Ch-Advanced-Resources.xml:135(para) +msgid "Anonymous clones are the simplest type. These resources behave completely identically everywhere they are running. Because of this, there can only be one copy of an anonymous clone active per machine." +msgstr "Clonele anonime sunt tipul cel mai simplu. Aceste resurse se comportă absolut identic oriunde rulează. Din această cauză, poate exista doar o copie a unei clone anonime activă per maşină." + +#: Ch-Advanced-Resources.xml:140(para) +msgid "Globally unique clones are distinct entities. A copy of the clone running on one machine is not equivalent to another instance on another node. Nor would any two copies on the same node be equivalent." +msgstr "Clonele unice la nivel global sunt entităţi distincte. O copie a unei clone rulând pe o maşină nu este echivalentă cu o altă instanţă pe alt nod. Nici nu ar fi echivalente oricare două copii pe acelaşi nod." + +#: Ch-Advanced-Resources.xml:145(para) +msgid "Stateful clones are covered later in ." +msgstr "Clonele stateful sunt discutate mai târziu în ." + +#: Ch-Advanced-Resources.xml:147(title) +msgid "An example clone" +msgstr "Un exemplu de clonă" + +#: Ch-Advanced-Resources.xml:162(title) +msgid "Properties of a Clone Resource" +msgstr "Proprietăţile unei Resurse Clonă" + +#: Ch-Advanced-Resources.xml:171(entry) +msgid "Your name for the clone" +msgstr "Numele dat clonei" + +#: Ch-Advanced-Resources.xml:179(para) +#: Ch-Advanced-Resources.xml:461(para) +msgid "Options inherited from simple resources: priority, target-role, is-managed" +msgstr "Opţiunile moştenite de la resurse simple: priority, target-role, is-managed" + +#: Ch-Advanced-Resources.xml:181(title) +msgid "Clone specific configuration options" +msgstr "Opţiuni de configurare specifice clonei" + +#: Ch-Advanced-Resources.xml:191(entry) +msgid "clone-max" +msgstr "clone-max" + +#: Ch-Advanced-Resources.xml:192(entry) +msgid "How many copies of the resource to start. Defaults to the number of nodes in the cluster." +msgstr "Câte copii ale resursei să pornească. Valoarea implicită este egală cu numărul de noduri din cluster." + +#: Ch-Advanced-Resources.xml:195(entry) +msgid "clone-node-max" +msgstr "clone-node-max" + +#: Ch-Advanced-Resources.xml:196(entry) +msgid "How many copies of the resource can be started on a single node. Defaults to 1." +msgstr "Câte copii ale resursei pot fi pornite pe un singur nod. Valoarea implicită este 1." + +#: Ch-Advanced-Resources.xml:199(entry) +msgid "notify" +msgstr "notify" + +#: Ch-Advanced-Resources.xml:200(emphasis) +#: Ch-Advanced-Resources.xml:205(emphasis) +#: Ch-Advanced-Resources.xml:209(emphasis) +#: Ch-Advanced-Resources.xml:214(emphasis) +msgid "false" +msgstr "false" + +#: Ch-Advanced-Resources.xml:200(entry) +msgid "When stopping or starting a copy of the clone, tell all the other copies beforehand and when the action was successful. Allowed values: true, " +msgstr "Când este oprită sau pornită o copie a clonei, comunică tuturor celorlalte copii înainte şi după ce acţiunea a reuşit. Valori permise: true, " + +#: Ch-Advanced-Resources.xml:204(entry) +msgid "globally-unique" +msgstr "globally-unique" + +#: Ch-Advanced-Resources.xml:205(entry) +msgid "Does each copy of the clone perform a different function? Allowed values: true, " +msgstr "Efectuează fiecare copie a unei clone o funcţie diferită? Valori permise: true, " + +#: Ch-Advanced-Resources.xml:208(entry) +msgid "ordered" +msgstr "ordered" + +#: Ch-Advanced-Resources.xml:209(entry) +msgid "Should the copies be started in series (instead of in parallel). Allowed values: true, " +msgstr "Ar trebui copiile să fie pornite secvenţial (în loc de în paralel). Valori permise: true, " + +#: Ch-Advanced-Resources.xml:213(entry) +msgid "interleave" +msgstr "interleave" + +#: Ch-Advanced-Resources.xml:214(entry) +msgid "Changes the behavior of ordering constraints (between clones/masters) so that instances can start/stop as soon as their peer instance has (rather than waiting for every instance of the other clone has). Allowed values: true, " +msgstr "Schimbă comportamentul de ordonare al restricţiilor (între clone/masters) astfel încât instanţele să se poată porni/opri de îndată ce şi instanţa vecină a făcut-o (decât să aştepte pentru fiecare instanţă pe care o are clona cealaltă). Valori permise: true, " + +#: Ch-Advanced-Resources.xml:222(title) +msgid "Using Clones" +msgstr "Folosind Clonele" + +#: Ch-Advanced-Resources.xml:225(para) +msgid "Clones have no instance attributes, however any that are set here will be inherited by the clone's children." +msgstr "Clonele nu au atribute de instanţă, totuşi cele care sunt setate aici vor fi moştenite de copiii clonei." + +#: Ch-Advanced-Resources.xml:229(para) +msgid "Clones must contain exactly one group or one regular resource." +msgstr "Clonele trebuie să conţină fix un grup sau o resursă obişnuită." + +#: Ch-Advanced-Resources.xml:231(para) +msgid "You should never reference the name of a clone's child. If you think you need to do this, you probably need to re-evaluate your design." +msgstr "Nu ar trebui să referenţiaţi niciodată numele copilului unei clone. Dacă se consideră că este necesar acest lucru, probabil trebuie sa re-evaluaţi design-ul vostru." + +#: Ch-Advanced-Resources.xml:239(para) +msgid "In most cases, a clone will have a single copy on each active cluster node. However if this is not the case, you can indicate which nodes the cluster should to preferentially assign copies to with resource location constraints. These constraints are written no differently to those for regular resources except that the clone's id is used." +msgstr "În majoritatea cazurilor, o clonă va avea o singură copie pe fiecare nod activ din cluster. Totuşi dacă nu este cazul, puteţi indica prin restricţii de locaţie a resursei către care noduri ar trebui clusterul să asigneze în mod preferenţial copiile. Aceste restricţii nu sunt scrise în mod diferit faţă de cele pentru resurse obişnuite cu excepţia faptului că id-ul clonei este folosit." + +#: Ch-Advanced-Resources.xml:244(para) +msgid "Ordering constraints behave slightly differently for clones. In the example below, apache-stats will wait until all copies of the clone that need to be started have done so before being started itself. Only if no copies can be started will apache-stats be prevented from being active. Additionally, the clone will wait for apache-stats to be stopped before stopping the clone." +msgstr "Restricţiile de ordonare se comportă uşor diferit în cazul clonelor. În exemplele de mai jos, apache-stats va aştepta până ce toate copiile clonelor care trebuie să fie pornite au făcut acest lucru înainte ca aceasta să fie pornită la rândul ei. Doar dacă nici o copie nu poate fi pornită va fi împiedicată apache-stats din a fi activă. În plus, clona va aştepta ca apache-stats să fie oprită înainte de a opri clona." + +#: Ch-Advanced-Resources.xml:250(para) +msgid "Colocation of a regular (or group) resource with a clone means that the resource can run on any machine with an active copy of the clone. The cluster will choose a copy based on where the clone is running and the rsc resource's own location preferences." +msgstr "Colocarea unei resurse obişnuite (sau a unui grup) cu o clonă înseamnă că resursa poate rula pe orice maşină cu o copie activă a clonei. Clusterul va alege o copie ţinând cont unde rulează în mod curent clona şi de preferinţele proprii de locaţie ale resursei." + +#: Ch-Advanced-Resources.xml:254(para) +msgid "Colocation between clones is also possible. In such cases, the set of allowed locations for the rsc clone is limited to nodes on which the with clone is (or will be) active. Allocation is then performed as-per-normal." +msgstr "Colocarea între clone este posibilă de asemenea. În astfel de cazuri, setul de locaţii permise pentru clonă este limitat la nodurile pe care clona alături de care va fi colocată este (sau va fi) activă. Alocarea este mai apoi efectuată în mod normal." + +#: Ch-Advanced-Resources.xml:260(title) +msgid "Example constraints involving clones" +msgstr "Exemple de restricţii implicând clone" + +#: Ch-Advanced-Resources.xml:274(para) +#: Ch-Advanced-Resources.xml:601(para) +msgid "To achieve a stable allocation pattern, clones are slightly sticky by default. If no value for resource-stickiness is provided, the clone will use a value of 1. Being a small value, it causes minimal disturbance to the score calculations of other resources but is enough to prevent Pacemaker from needlessly moving copies around the cluster." +msgstr "Pentru a atinge un tipar de alocare stabil, clonele sunt uşor adezive în mod implicit. Dacă nu este furnizată nici o valoare pentru resource-stickiness, clona va folosi valoarea 1. Fiind o valoare mică, aceasta cauzează o perturbare minimală a calcului scorului celorlalte resurse dar este suficientă pentru a împiedica Pacemaker-ul de a muta inutil copiile prin cluster." + +#: Ch-Advanced-Resources.xml:281(title) +#: Ch-Advanced-Resources.xml:629(title) +msgid "Resource Agent Requirements" +msgstr "Cerinţele Agentului de Resursă" + +#: Ch-Advanced-Resources.xml:282(para) +msgid "Any resource can be used as an anonymous clone as it requires no additional support from the resource agent. Whether it makes sense to do so depends on your resource and its resource agent." +msgstr "Orice resursă poate fi utilizată ca o clonă anonimă deoarece nu necesită vreun suport adiţional din partea agentului de resursă. Dacă are logică să facă acest lucru depinde de resursa voastră şi de agentul de resursă aferent." + +#: Ch-Advanced-Resources.xml:286(para) +msgid "Globally unique clones do require some additional support in the resource agent. In particular, it must only respond with ${OCF_SUCCESS} if the node has that exact instance active. All other probes for instances of the clone should result in ${OCF_NOT_RUNNING}. Unless of course they are failed, in which case they should return one of the other OCF error codes." +msgstr "Clonele unice la nivel global necesită suport adiţional în agentul de resursă. În special, trebuie să răspundă doar cu ${OCF_SUCCESS} dacă nodul are exact acea instanţă activă. Tot restul de probe pentru instanţe ale clonei ar trebui să rezulte în ${OCF_NOT_RUNNING}. Cu excepţia cazului în care au eşuat, caz în care ar trebui să returneze unul din celelalte coduri de eroare OCF." + +#: Ch-Advanced-Resources.xml:292(para) +msgid "Copies of a clone are identified by appending a colon and a numerical offset. Eg. apache:2" +msgstr "Copiile unei clone sunt identificate prin sufixarea a două puncte şi a unui delimitator numeric. Ex. apache:2" + +#: Ch-Advanced-Resources.xml:293(para) +msgid "Resource agents can find out how many copies there are by examining the OCF_RESKEY_CRM_meta_clone_max environment variable and which copy it is by examining OCF_RESKEY_CRM_meta_clone." +msgstr "Agenţii de resursă pot afla câte copii există prin examinarea variabilei de mediu OCF_RESKEY_CRM_meta_clone_max şi a cărei copii este cea curentă examinând OCF_RESKEY_CRM_meta_clone." + +#: Ch-Advanced-Resources.xml:294(para) +msgid "You should not make any assumptions (based on OCF_RESKEY_CRM_meta_clone) about which copies are active. In particular, the list of active copies will not always be an unbroken sequence, nor always start at 0." +msgstr "Nu ar trebui să faceţi presupuneri (pe baza OCF_RESKEY_CRM_meta_clone) în privinţa căror copii sunt active. În special, lista de copii active nu va fi întotdeauna o secvenţă continuă, nici nu va începe întotdeauna de la 0." + +#: Ch-Advanced-Resources.xml:300(title) +#: Ch-Advanced-Resources.xml:675(title) +msgid "Notifications" +msgstr "Notificări" + +#: Ch-Advanced-Resources.xml:301(para) +msgid "Supporting notifications requires the notify action to be implemented. Once supported, the notify action will be passed a number of extra variables which, when combined with additional context, can be used to calculate the current state of the cluster and what is about to happen to it." +msgstr "Suportarea notificărilor necesită acţiunea notify să fie implementată. Odată ce este suportată, acţiunii de notificare îi vor fi trimise un număr de variabile suplimentare care, atunci când sunt combinate cu un context adiţional, pot fi folosite pentru a calcula starea curentă a clusterului şi ceea ce urmează să i se întâmple." + +#: Ch-Advanced-Resources.xml:306(title) +msgid "Environment variables supplied with Clone notify actions" +msgstr "Variabile de mediu furnizate împreună cu acţiunile de notificare ale Clonei" + +#: Ch-Advanced-Resources.xml:310(entry) +#: Ch-Advanced-Resources.xml:687(entry) +msgid "Variable" +msgstr "Variabilă" + +#: Ch-Advanced-Resources.xml:316(entry) +#: Ch-Advanced-Resources.xml:691(entry) +msgid "OCF_RESKEY_CRM_meta_notify_type" +msgstr "OCF_RESKEY_CRM_meta_notify_type" + +#: Ch-Advanced-Resources.xml:317(entry) +#: Ch-Advanced-Resources.xml:692(entry) +msgid "Allowed values: pre, post" +msgstr "Valori permise: pre, post" + +#: Ch-Advanced-Resources.xml:320(entry) +#: Ch-Advanced-Resources.xml:695(entry) +msgid "OCF_RESKEY_CRM_meta_notify_operation" +msgstr "OCF_RESKEY_CRM_meta_notify_operation" + +#: Ch-Advanced-Resources.xml:321(entry) +#: Ch-Advanced-Resources.xml:696(entry) +msgid "Allowed values: start, stop" +msgstr "Valori permise: start, stop" + +#: Ch-Advanced-Resources.xml:324(entry) +#: Ch-Advanced-Resources.xml:715(entry) +msgid "OCF_RESKEY_CRM_meta_notify_start_resource" +msgstr "OCF_RESKEY_CRM_meta_notify_start_resource" + +#: Ch-Advanced-Resources.xml:325(entry) +#: Ch-Advanced-Resources.xml:716(entry) +msgid "Resources to be started" +msgstr "Resursele care vor fi pornite" + +#: Ch-Advanced-Resources.xml:328(entry) +#: Ch-Advanced-Resources.xml:719(entry) +msgid "OCF_RESKEY_CRM_meta_notify_stop_resource" +msgstr "OCF_RESKEY_CRM_meta_notify_stop_resource" + +#: Ch-Advanced-Resources.xml:329(entry) +#: Ch-Advanced-Resources.xml:720(entry) +msgid "Resources to be stopped" +msgstr "Resursele care vor fi oprite" + +#: Ch-Advanced-Resources.xml:332(entry) +#: Ch-Advanced-Resources.xml:699(entry) +msgid "OCF_RESKEY_CRM_meta_notify_active_resource" +msgstr "OCF_RESKEY_CRM_meta_notify_active_resource" + +#: Ch-Advanced-Resources.xml:333(entry) +#: Ch-Advanced-Resources.xml:700(entry) +msgid "Resources the that are running" +msgstr "Resursele care rulează" + +#: Ch-Advanced-Resources.xml:336(entry) +#: Ch-Advanced-Resources.xml:703(entry) +msgid "OCF_RESKEY_CRM_meta_notify_inactive_resource" +msgstr "OCF_RESKEY_CRM_meta_notify_inactive_resource" + +#: Ch-Advanced-Resources.xml:337(entry) +#: Ch-Advanced-Resources.xml:704(entry) +msgid "Resources the that are not running" +msgstr "Resursele care nu rulează" + +#: Ch-Advanced-Resources.xml:340(entry) +#: Ch-Advanced-Resources.xml:731(entry) +msgid "OCF_RESKEY_CRM_meta_notify_start_uname" +msgstr "OCF_RESKEY_CRM_meta_notify_start_uname" + +#: Ch-Advanced-Resources.xml:341(entry) +#: Ch-Advanced-Resources.xml:732(entry) +msgid "Nodes on which resources will be started" +msgstr "Nodurile pe care resursele vor fi pornite" + +#: Ch-Advanced-Resources.xml:344(entry) +#: Ch-Advanced-Resources.xml:735(entry) +msgid "OCF_RESKEY_CRM_meta_notify_stop_uname" +msgstr "OCF_RESKEY_CRM_meta_notify_stop_uname" + +#: Ch-Advanced-Resources.xml:345(entry) +#: Ch-Advanced-Resources.xml:736(entry) +msgid "Nodes on which resources will be stopped" +msgstr "Nodurile pe care resursele vor fi oprite" + +#: Ch-Advanced-Resources.xml:348(entry) +#: Ch-Advanced-Resources.xml:747(entry) +msgid "OCF_RESKEY_CRM_meta_notify_active_uname" +msgstr "OCF_RESKEY_CRM_meta_notify_active_uname" + +#: Ch-Advanced-Resources.xml:349(entry) +#: Ch-Advanced-Resources.xml:748(entry) +msgid "Nodes on which resources are running" +msgstr "Nodurile pe care rulează resursele" + +#: Ch-Advanced-Resources.xml:352(entry) +#: Ch-Advanced-Resources.xml:751(entry) +msgid "OCF_RESKEY_CRM_meta_notify_inactive_uname" +msgstr "OCF_RESKEY_CRM_meta_notify_inactive_uname" + +#: Ch-Advanced-Resources.xml:353(entry) +#: Ch-Advanced-Resources.xml:752(entry) +msgid "Nodes on which resources are not running" +msgstr "Nodurile pe care nu rulează resursele" + +#: Ch-Advanced-Resources.xml:358(para) +msgid "The variables come in pairs, such as OCF_RESKEY_CRM_meta_notify_start_resource and OCF_RESKEY_CRM_meta_notify_start_uname and should be treated as an array of whitespace separated elements." +msgstr "Variabilele vin în perechi, cum ar fi OCF_RESKEY_CRM_meta_notify_start_resource şi OCF_RESKEY_CRM_meta_notify_start_uname şi ar trebui tratate ca un array de elemente separate de spaţiu." + +#: Ch-Advanced-Resources.xml:359(para) +msgid "Thus in order to indicate that clone:0 will be started on sles-1, clone:2 will be started on sles-3, and clone:3 will be started on sles-2, the cluster would set" +msgstr "Drept urmare pentru a indica faptul că, clone:0 va fi pornită pe sles-1, clone:2 va fi pornită pe sles-3 şi clone:3 va fi pornită pe sles-2, clusterul va seta" + +#: Ch-Advanced-Resources.xml:360(para) +msgid "OCF_RESKEY_CRM_meta_notify_start_resource=\"clone:0 clone:2 clone:3\"" +msgstr "OCF_RESKEY_CRM_meta_notify_start_resource=\"clone:0 clone:2 clone:3\"" + +#: Ch-Advanced-Resources.xml:361(para) +msgid "OCF_RESKEY_CRM_meta_notify_start_uname=\"sles-1 sles-3 sles-2\"" +msgstr "OCF_RESKEY_CRM_meta_notify_start_uname=\"sles-1 sles-3 sles-2\"" + +#: Ch-Advanced-Resources.xml:362(para) +msgid "Example notification variables" +msgstr "Exemple de variabile de notificare" + +#: Ch-Advanced-Resources.xml:365(title) +#: Ch-Advanced-Resources.xml:765(title) +msgid "Proper Interpretation of Notification Environment Variables" +msgstr "Interpretarea Corespunzătoare a Variabilelor de Mediu de Notificare" + +#: Ch-Advanced-Resources.xml:366(para) +msgid "Pre-notification (stop)" +msgstr "Pre-notificare (oprire)" + +#: Ch-Advanced-Resources.xml:369(para) +#: Ch-Advanced-Resources.xml:768(para) +#: Ch-Advanced-Resources.xml:780(para) +msgid "Active resources: $OCF_RESKEY_CRM_meta_notify_active_resource" +msgstr "Resurse active: $OCF_RESKEY_CRM_meta_notify_active_resource" + +#: Ch-Advanced-Resources.xml:372(para) +#: Ch-Advanced-Resources.xml:771(para) +#: Ch-Advanced-Resources.xml:787(para) +msgid "Inactive resources: $OCF_RESKEY_CRM_meta_notify_inactive_resource" +msgstr "Resurse inactive: $OCF_RESKEY_CRM_meta_notify_inactive_resource" + +#: Ch-Advanced-Resources.xml:375(para) +#: Ch-Advanced-Resources.xml:772(para) +#: Ch-Advanced-Resources.xml:788(para) +#: Ch-Advanced-Resources.xml:817(para) +#: Ch-Advanced-Resources.xml:849(para) +#: Ch-Advanced-Resources.xml:885(para) +msgid "Resources to be started: $OCF_RESKEY_CRM_meta_notify_start_resource" +msgstr "Resurse care vor fi pornite: $OCF_RESKEY_CRM_meta_notify_start_resource" + +#: Ch-Advanced-Resources.xml:378(para) +#: Ch-Advanced-Resources.xml:775(para) +#: Ch-Advanced-Resources.xml:791(para) +#: Ch-Advanced-Resources.xml:820(para) +#: Ch-Advanced-Resources.xml:852(para) +#: Ch-Advanced-Resources.xml:888(para) +msgid "Resources to be stopped: $OCF_RESKEY_CRM_meta_notify_stop_resource" +msgstr "Resurse care vor fi oprite: $OCF_RESKEY_CRM_meta_notify_stop_resource" + +#: Ch-Advanced-Resources.xml:382(para) +#: Ch-Advanced-Resources.xml:795(para) +msgid "Post-notification (stop) / Pre-notification (start)" +msgstr "Post-notificare (oprire) / Pre-notificare (pornire)" + +#: Ch-Advanced-Resources.xml:385(para) +#: Ch-Advanced-Resources.xml:409(para) +#: Ch-Advanced-Resources.xml:797(para) +#: Ch-Advanced-Resources.xml:826(para) +#: Ch-Advanced-Resources.xml:860(para) +msgid "Active resources:" +msgstr "Resurse active:" + +#: Ch-Advanced-Resources.xml:388(para) +#: Ch-Advanced-Resources.xml:412(para) +#: Ch-Advanced-Resources.xml:799(para) +#: Ch-Advanced-Resources.xml:828(para) +#: Ch-Advanced-Resources.xml:862(para) +msgid "$OCF_RESKEY_CRM_meta_notify_active_resource" +msgstr "$OCF_RESKEY_CRM_meta_notify_active_resource" + +#: Ch-Advanced-Resources.xml:389(para) +#: Ch-Advanced-Resources.xml:413(para) +#: Ch-Advanced-Resources.xml:800(para) +#: Ch-Advanced-Resources.xml:810(para) +#: Ch-Advanced-Resources.xml:829(para) +#: Ch-Advanced-Resources.xml:840(para) +#: Ch-Advanced-Resources.xml:863(para) +#: Ch-Advanced-Resources.xml:875(para) +msgid "minus $OCF_RESKEY_CRM_meta_notify_stop_resource" +msgstr "minus $OCF_RESKEY_CRM_meta_notify_stop_resource" + +#: Ch-Advanced-Resources.xml:392(para) +#: Ch-Advanced-Resources.xml:417(para) +#: Ch-Advanced-Resources.xml:812(para) +#: Ch-Advanced-Resources.xml:843(para) +#: Ch-Advanced-Resources.xml:879(para) +msgid "Inactive resources:" +msgstr "Resurse inactive:" + +#: Ch-Advanced-Resources.xml:395(para) +#: Ch-Advanced-Resources.xml:420(para) +#: Ch-Advanced-Resources.xml:814(para) +#: Ch-Advanced-Resources.xml:845(para) +#: Ch-Advanced-Resources.xml:881(para) +msgid "$OCF_RESKEY_CRM_meta_notify_inactive_resource" +msgstr "$OCF_RESKEY_CRM_meta_notify_inactive_resource" + +#: Ch-Advanced-Resources.xml:396(para) +#: Ch-Advanced-Resources.xml:421(para) +#: Ch-Advanced-Resources.xml:815(para) +#: Ch-Advanced-Resources.xml:846(para) +#: Ch-Advanced-Resources.xml:882(para) +msgid "plus $OCF_RESKEY_CRM_meta_notify_stop_resource" +msgstr "plus $OCF_RESKEY_CRM_meta_notify_stop_resource" + +#: Ch-Advanced-Resources.xml:399(para) +#: Ch-Advanced-Resources.xml:425(para) +#: Ch-Advanced-Resources.xml:853(para) +#: Ch-Advanced-Resources.xml:889(para) +msgid "Resources that were started: $OCF_RESKEY_CRM_meta_notify_start_resource" +msgstr "Resurse care au fost pornite: $OCF_RESKEY_CRM_meta_notify_start_resource" + +#: Ch-Advanced-Resources.xml:402(para) +#: Ch-Advanced-Resources.xml:428(para) +#: Ch-Advanced-Resources.xml:822(para) +#: Ch-Advanced-Resources.xml:855(para) +#: Ch-Advanced-Resources.xml:892(para) +msgid "Resources that were stopped: $OCF_RESKEY_CRM_meta_notify_stop_resource" +msgstr "Resurse care au fost oprite: $OCF_RESKEY_CRM_meta_notify_stop_resource" + +#: Ch-Advanced-Resources.xml:406(para) +msgid "Post-notification (start)" +msgstr "Post-notificare (pornire)" + +#: Ch-Advanced-Resources.xml:414(para) +#: Ch-Advanced-Resources.xml:830(para) +#: Ch-Advanced-Resources.xml:841(para) +#: Ch-Advanced-Resources.xml:864(para) +#: Ch-Advanced-Resources.xml:876(para) +msgid "plus $OCF_RESKEY_CRM_meta_notify_start_resource" +msgstr "plus $OCF_RESKEY_CRM_meta_notify_start_resource" + +#: Ch-Advanced-Resources.xml:422(para) +#: Ch-Advanced-Resources.xml:847(para) +#: Ch-Advanced-Resources.xml:883(para) +msgid "minus $OCF_RESKEY_CRM_meta_notify_start_resource" +msgstr "minus $OCF_RESKEY_CRM_meta_notify_start_resource" + +#: Ch-Advanced-Resources.xml:435(title) +msgid "Multi-state - Resources That Have Multiple Modes" +msgstr "Resurse cu stări multiple - Resurse Care Au Mai Multe Moduri" + +#: Ch-Advanced-Resources.xml:436(para) +msgid "Multi-state resources are a specialization of Clones (please ensure you understand the section on clones before continuing) that allow the instances to be in one of two operating modes. These modes are called Master and Slave but can mean whatever you wish them to mean. The only limitation is that when an instance is started, it must come up in the Slave state." +msgstr "Resursele cu stări multiple sunt o specializare a Clonelor (vă rugăm să vă asiguraţi că înţelegeţi secţiunea referitoare la clone înainte de a continua) care permite instanţelor să se afle în unul din două moduri operaţionale. Aceste moduri sunt numite Master şi Slave dar pot însemna orice doriţi să însemne. Singura limitare este că atunci când o instanţă este pornită, trebuie să o facă în starea Slave." + +#: Ch-Advanced-Resources.xml:444(title) +msgid "Properties of a Multi-State Resource" +msgstr "Proprietăţile unei Resurse cu Stări Multiple" + +#: Ch-Advanced-Resources.xml:453(entry) +msgid "Your name for the multi-state resource" +msgstr "Numele asignat pentru resursa cu stări multiple" + +#: Ch-Advanced-Resources.xml:462(para) +msgid "Options inherited from clone resources: clone-max, clone-node-max, notify, globally-unique, ordered, interleave" +msgstr "Opţiuni moştenite de la resursele clonate: clone-max, clone-node-max, notify, globally-unique, ordered, interleave" + +#: Ch-Advanced-Resources.xml:464(title) +msgid "Multi-state specific resource configuration options" +msgstr "Opţiuni specifice de configurare pentru resurse cu stări multiple" + +#: Ch-Advanced-Resources.xml:472(entry) +msgid "master-max" +msgstr "master-max" + +#: Ch-Advanced-Resources.xml:473(entry) +msgid "How many copies of the resource can be promoted to master status. Defaults to 1." +msgstr "Câte copii ale resursei pot fi promovate la statutul de master. Valoarea implicită este 1." + +#: Ch-Advanced-Resources.xml:476(entry) +msgid "master-node-max" +msgstr "master-node-max" + +#: Ch-Advanced-Resources.xml:477(entry) +msgid "How many copies of the resource can be promoted to master status on a single node. Defaults to 1." +msgstr "Câte copii ale resursei pot fi promovate la statutul de master pe un singur nod. Valoarea implicită este 1." + +#: Ch-Advanced-Resources.xml:482(title) +msgid "Using Multi-state Resources" +msgstr "Folosind Resursele cu Stări Multiple" + +#: Ch-Advanced-Resources.xml:485(para) +msgid "Multi-state resources have no instance attributes, however any that are set here will be inherited by the master's children." +msgstr "Resursele cu stări multiple nu au atribute de instanţă, însă oricare ar fi setate aici vor fi moştenite de către copiii master-ului." + +#: Ch-Advanced-Resources.xml:489(para) +msgid "Masters must contain exactly one group or one regular resource." +msgstr "Resursele Master trebuie să conţină exact un grup sau o resursă obişnuită." + +#: Ch-Advanced-Resources.xml:491(para) +msgid "You should never reference the name of a master's child. If you think you need to do this, you probably need to re-evaluate your design." +msgstr "Nu ar trebui să referenţiaţi niciodată copilul unui master. Dacă se consideră necesar acest aspect, atunci este probabil necesară re-evaluarea designului vostru." + +#: Ch-Advanced-Resources.xml:498(title) +msgid "Monitoring Multi-State Resources" +msgstr "Monitorizarea Resurselor cu Stări Multiple" + +#: Ch-Advanced-Resources.xml:499(para) +msgid "The normal type of monitor actions you define are not sufficient to monitor a multi-state resource in the Master state. To detect failures of the master instance, you need to define an additional monitor action with role=\"Master\"." +msgstr "Tipul normal de acţiune de monitorizare pe care îl definim nu este suficient pentru a monitoriza o resursă cu stări multiple în starea Master. Pentru a detecta eşecurile instanţei master, trebuie să definiţi o acţiune de monitorizare adiţională cu role=\"Master\"." + +#: Ch-Advanced-Resources.xml:503(para) +msgid "It is crucial that every monitor operation has a different interval" +msgstr "Este imperativ ca fiecare operaţiune de monitorizare să aibă un interval diferit" + +#: Ch-Advanced-Resources.xml:505(title) +msgid "Monitoring both states of a multi-state resource" +msgstr "Monitorizarea ambelor stări ale unei resurse cu stări multiple" + +#: Ch-Advanced-Resources.xml:522(para) +msgid "In most cases, a multi-state resources will have a single copy on each active cluster node. However if this is not the case, you can indicate which nodes the cluster should to preferentially assign copies to with resource location constraints. These constraints are written no differently to those for regular resources except that the master's id is used." +msgstr "În majoritatea cazurilor, o resursă cu stări multiple va avea o singură copie pe fiecare nod activ din cluster. Dacă nu este cazul însă, puteţi indica pe care noduri ar trebui clusterul să asigneze copii cu restricţii de locaţie ale resurselor. Aceste restricţii nu sunt scrise diferit faţă de cele pentru resursele obişnuite cu excepţia faptului că id-ul masterului este folosit." + +#: Ch-Advanced-Resources.xml:527(para) +msgid "When considering multi-state resources in constraints, for most purposes it is sufficient to treat them as clones. The exception is when the rsc-role and/or with-rsc-role (for colocation constraints) and first-action and/or then-action (for ordering constraints) are used." +msgstr "Când ţinem cont de resursele cu stări multiple în restricţii, pentru majoritatea scopurilor este suficient să le tratăm ca pe clone. Excepţia survine atunci când sunt folosite rsc-role şi/sau with-rsc-role (pentru restricţii de colocare) şi first-action şi/sau then-action (pentru restricţii de ordonare)." + +#: Ch-Advanced-Resources.xml:532(title) +msgid "Additional constraint options relevant to multi-state resources" +msgstr "Opţiuni de restricţionare adiţionale relevante la resurse cu stări multiple" + +#: Ch-Advanced-Resources.xml:540(entry) +msgid "rsc-role" +msgstr "rsc-role" + +#: Ch-Advanced-Resources.xml:542(para) +msgid "An additional attribute of colocation constraints that specifies the role that rsc must be in." +msgstr "Un atribut adiţional al restricţiilor de colocare care specifică rolul în care trebuie să se alfe rsc." + +#: Ch-Advanced-Resources.xml:543(para) +#: Ch-Advanced-Resources.xml:550(para) +msgid "Allowed values: Started, Master, Slave" +msgstr "Valori permise: Pornit, Master, Slave" + +#: Ch-Advanced-Resources.xml:547(entry) +msgid "with-rsc-role" +msgstr "with-rsc-role" + +#: Ch-Advanced-Resources.xml:549(para) +msgid "An additional attribute of colocation constraints that specifies the role that with-rsc must be in." +msgstr "Un atribut adiţional al restricţiilor de colocare care specifică rolul în care trebuie să se alfe with-rsc." + +#: Ch-Advanced-Resources.xml:554(entry) +msgid "first-action" +msgstr "first-action" + +#: Ch-Advanced-Resources.xml:556(para) +msgid "An additional attribute of ordering constraints that specifies the action that the first resource must complete before executing the specified action for the then resource." +msgstr "Un atribut adiţional al restricţiilor de ordonare care specifică acţiunea pe care resursa first trebuie să o termine înaintea executării acţiunii specificate pentru resursa then." + +#: Ch-Advanced-Resources.xml:557(para) +msgid "Allowed values: start, stop, promote, demote" +msgstr "Valori permise: start, stop, promote, demote" + +#: Ch-Advanced-Resources.xml:561(entry) +msgid "then-action" +msgstr "then-action" + +#: Ch-Advanced-Resources.xml:563(para) +msgid "An additional attribute of ordering constraints that specifies the action that the then resource can only execute after the first-action on the first resource has completed." +msgstr "Un atribut adiţional al restricţiilor de ordonare care specifică acţiunea pe care resursa then o va putea executa după ce first-action pe prima resursă a terminat." + +#: Ch-Advanced-Resources.xml:564(para) +msgid "Allowed values: start, stop, promote, demote. Defaults to the value (specified or implied) of first-action" +msgstr "Valori permise: start, stop, promote, demote. Valoarea implicită (specificată sau subînţeleasă) este cea dată de first-action" + +#: Ch-Advanced-Resources.xml:570(para) +msgid "In the example below, myApp will wait until one of the database copies has been started and promoted to master before being started itself. Only if no copies can be promoted will apache-stats be prevented from being active. Additionally, the database will wait for myApp to be stopped before it is demoted." +msgstr "În exemplul de mai jos, myApp va aştepta până când una din copiile bazei de date a fost pornită şi promovată la master înainte de a fi ea însăşi pornită. Doar dacă nici o copie nu poate fi promovată va fi împiedicată apache-stats de a fi activă. În mod adiţional, baza de date va aştepta ca myApp să fie oprită înainte să fie degradată." + +#: Ch-Advanced-Resources.xml:575(para) +msgid "Colocation of a regular (or group) resource with a multi-state resource means that it can run on any machine with an active copy of the clone that is in the specified state (Master or Slave). In the example, the cluster will choose a location based on where database is running as a Master, and if there are multiple Master instances it will also factor in myApp‘s own location preferences when deciding which location to choose." +msgstr "Colocarea unei resurse obişnuite (sau a unui grup) cu o resursă cu stări-multiple înseamnă că poate rula pe orice maşină cu o copie activă a clonei care se alfă în starea specificată (Master sau Slave). În exemplu, clusterul va alege o locaţie în funcţie de unde rulează baza de date în mod curent ca Master, şi dacă sunt mai multe instanţe de Master va lua în considerare şi preferinţele proprii de locaţie ale myApp când va decide care locaţie să aleagă." + +#: Ch-Advanced-Resources.xml:579(para) +msgid "Colocation with regular clones and other multi-state resources is also possible. In such cases, the set of allowed locations for the rsc clone is (after role filtering) limited to nodes on which the with-rsc clone is (or will be) in the specified role. Allocation is then performed as-per-normal." +msgstr "Colocarea alături de clone obişnuite şi alte resurse cu stări multiple este posibilă de asemenea. În astfel de cazuri, setul de locaţii permise pentru clona rsc este (după filtrarea rolului) limitat la nodurile pe care clona with-rsc există (sau va exista) în rolul specificat. Alocarea este atunci efectuată în mod normal." + +#: Ch-Advanced-Resources.xml:585(title) +msgid "Example constraints involving multi-state resources" +msgstr "Exemple de restricţii implicând resurse cu stări multiple" + +#: Ch-Advanced-Resources.xml:608(title) +msgid "Which Resource Instance is Promoted" +msgstr "Care Instanţă a Resursei este Promovată" + +#: Ch-Advanced-Resources.xml:609(para) +msgid "During the start operation, most Resource Agent scripts should call the crm_master utility. This tool automatically detects both the resource and host and should be used to set a preference for being promoted. Based on this, master-max, and master-node-max, the instance(s) with the highest preference will be promoted." +msgstr "În timpul operaţiunii de pornire, majoritatea scripturilor Agenţilor de Resursă ar trebui să apeleze utilitarul crm_master. Acesta detectează în mod automat atât resursa cât şi gazda şi ar trebui să fie folosit pentru a seta o preferinţă pentru a fi promovat. În funcţie de asta, de master-max şi de master-node-max, instanţa(ele) cu cea mai mare preferinţă va fi promovată." + +#: Ch-Advanced-Resources.xml:614(para) +msgid "The other alternative is to create a location constraint that indicates which nodes are most preferred as masters." +msgstr "Cealaltă alternativă să se creeze o restricţie de locaţie care să indice care noduri sunt cele mai preferate ca masteri." + +#: Ch-Advanced-Resources.xml:616(title) +msgid "Manually specifying which node should be promoted" +msgstr "Specificând manual care nod ar trebui să fie promovat" + +#: Ch-Advanced-Resources.xml:630(para) +msgid "Since multi-state resources are an extension of cloned resources, all the requirements of Clones are also requirements of multi-state resources. Additionally, multi-state resources require two extra actions demote and promote. These actions are responsible for changing the state of the resource. Like start and stop, they should return OCF_SUCCESS if they completed successfully or a relevant error code if they did not." +msgstr "Din moment ce resursele multi-state sunt o extensie a resurselor clonate, toate cerinţele Clonelor sunt de asemenea cerinţe ale resurselor multi-state. Adiţional, resursele multi-state necesită două acţiuni suplimentare promote şi demote. Aceste acţiuni sunt responsabile pentru schimbarea stării resursei. Precum start şi stop, acestea ar trebui să returneze OCF_SUCCESS dacă au terminat cu succes sau un cod de eroare relevant în caz contrar." + +#: Ch-Advanced-Resources.xml:636(para) +msgid "The states can mean whatever you wish, but when the resource is started, it must come up in the mode called Slave. From there the cluster will then decide which instances to promote into a Master." +msgstr "Stările pot însemna orice doriţi, dar atunci când resursa este pornită, trebuie să ajungă în modul numit Slave. De acolo clusterul va decide mai apoi care instanţe să promoveze într-un Master." + +#: Ch-Advanced-Resources.xml:640(para) +msgid "In addition to the Clone requirements for monitor actions, agents must also accurately report which state they are in. The cluster relies on the agent to report its status (including role) accurately and does not indicate to the agent what role it currently believes it to be in." +msgstr "În plus faţă de cerinţele Clonelor pentru acţiunile de monitorizare, agenţii trebuie să raporteze corespunzător starea în care sunt. Clusterul se bazează pe agent să-şi raporteze statusul (incluzând rolul) în mod corespunzător şi nu indică agentului în care rol crede acesta în mod curent că ar trebui să se afle." + +#: Ch-Advanced-Resources.xml:645(title) +msgid "Role implications of OCF return codes" +msgstr "Implicaţiile rolurilor codurilor returnate de OCF" + +#: Ch-Advanced-Resources.xml:649(entry) +msgid "Monitor Return Code" +msgstr "Cod de Monitorizare Returnat" + +#: Ch-Advanced-Resources.xml:653(entry) +msgid "OCF_NOT_RUNNING" +msgstr "OCF_NOT_RUNNING" + +#: Ch-Advanced-Resources.xml:654(entry) +msgid "Stopped" +msgstr "Oprit" + +#: Ch-Advanced-Resources.xml:657(entry) +msgid "OCF_SUCCESS" +msgstr "OCF_SUCCESS" + +#: Ch-Advanced-Resources.xml:658(entry) +msgid "Running (Slave)" +msgstr "Rulând (Slave)" + +#: Ch-Advanced-Resources.xml:661(entry) +msgid "OCF_RUNNING_MASTER" +msgstr "OCF_RUNNING_MASTER" + +#: Ch-Advanced-Resources.xml:662(entry) +msgid "Running (Master)" +msgstr "Rulează (Master)" + +#: Ch-Advanced-Resources.xml:665(entry) +msgid "OCF_FAILED_MASTER" +msgstr "OCF_FAILED_MASTER" + +#: Ch-Advanced-Resources.xml:666(entry) +msgid "Failed (Master)" +msgstr "Eşuat (Master)" + +#: Ch-Advanced-Resources.xml:669(entry) +msgid "Other" +msgstr "Altul" + +#: Ch-Advanced-Resources.xml:670(entry) +msgid "Failed (Slave)" +msgstr "Eşuat (Slave)" + +#: Ch-Advanced-Resources.xml:676(para) +msgid "Like with clones, supporting notifications requires the notify action to be implemented. Once supported, the notify action will be passed a number of extra variables which, when combined with additional context, can be used to calculate the current state of the cluster and what is about to happen to it." +msgstr "Ca şi în cazul clonelor, suportarea notificărilor necesită acţiunea notify să fie implementată. Odată ce este suportată, acţiunii notify îi vor fi trimise un număr de variabile suplimentare care, când sunt combinate cu un context suplimentar, pot fi folosite pentru a calcula starea curentă a clusterului şi ceea ce urmează să i se întâmple." + +#: Ch-Advanced-Resources.xml:682(para) +msgid "Variables in bold are specific to Master resources and all behave in the same manner as described for Clone resources." +msgstr "Variabilele îngroşate sunt specifice resurselor Master şi se comportă toate în acelaşi fel ca şi cel descris pentru resursele Clonă." + +#: Ch-Advanced-Resources.xml:681(title) +msgid "Environment variables supplied with Master notify actions " +msgstr "Variabilele de mediu furnizate cu acţiunile de notificare Master " + +#: Ch-Advanced-Resources.xml:707(emphasis) +msgid "OCF_RESKEY_CRM_meta_notify_master_resource" +msgstr "OCF_RESKEY_CRM_meta_notify_master_resource" + +#: Ch-Advanced-Resources.xml:708(entry) +msgid "Resources that are running in Master mode" +msgstr "Resursele care funcţionează în mod Master" + +#: Ch-Advanced-Resources.xml:711(emphasis) +msgid "OCF_RESKEY_CRM_meta_notify_slave_resource" +msgstr "OCF_RESKEY_CRM_meta_notify_slave_resource" + +#: Ch-Advanced-Resources.xml:712(entry) +msgid "Resources that are running in Slave mode" +msgstr "Resursele care funcţionează în mod Slave" + +#: Ch-Advanced-Resources.xml:723(emphasis) +msgid "OCF_RESKEY_CRM_meta_notify_promote_resource" +msgstr "OCF_RESKEY_CRM_meta_notify_promote_resource" + +#: Ch-Advanced-Resources.xml:724(entry) +msgid "Resources to be promoted" +msgstr "Resursele care vor fi promovate" + +#: Ch-Advanced-Resources.xml:727(emphasis) +msgid "OCF_RESKEY_CRM_meta_notify_demote_resource" +msgstr "OCF_RESKEY_CRM_meta_notify_demote_resource" + +#: Ch-Advanced-Resources.xml:728(entry) +msgid "Resources to be demoted" +msgstr "Resursele care vor fi degradate" + +#: Ch-Advanced-Resources.xml:739(emphasis) +msgid "OCF_RESKEY_CRM_meta_notify_promote_uname" +msgstr "OCF_RESKEY_CRM_meta_notify_promote_uname" + +#: Ch-Advanced-Resources.xml:740(entry) +msgid "Nodes on which resources will be promoted" +msgstr "Nodurile pe care resursele vor fi promovate" + +#: Ch-Advanced-Resources.xml:743(emphasis) +msgid "OCF_RESKEY_CRM_meta_notify_demote_uname" +msgstr "OCF_RESKEY_CRM_meta_notify_demote_uname" + +#: Ch-Advanced-Resources.xml:744(entry) +msgid "Nodes on which resources will be demoted" +msgstr "Nodurile pe care resursele vor fi degradate" + +#: Ch-Advanced-Resources.xml:755(emphasis) +msgid "OCF_RESKEY_CRM_meta_notify_master_uname" +msgstr "OCF_RESKEY_CRM_meta_notify_master_uname" + +#: Ch-Advanced-Resources.xml:756(entry) +msgid "Nodes on which resources are running in Master mode" +msgstr "Nodurile pe care resursele rulează în mod Master" + +#: Ch-Advanced-Resources.xml:759(emphasis) +msgid "OCF_RESKEY_CRM_meta_notify_slave_uname" +msgstr "OCF_RESKEY_CRM_meta_notify_slave_uname" + +#: Ch-Advanced-Resources.xml:760(entry) +msgid "Nodes on which resources are running in Slave mode" +msgstr "Nodurile pe care resursele rulează în mod Slave" + +#: Ch-Advanced-Resources.xml:766(para) +msgid "Pre-notification (demote)" +msgstr "Pre-notificare (degradează)" + +#: Ch-Advanced-Resources.xml:769(para) +msgid "Master resources: $OCF_RESKEY_CRM_meta_notify_master_resource" +msgstr "Resurse Master: $OCF_RESKEY_CRM_meta_notify_master_resource" + +#: Ch-Advanced-Resources.xml:770(para) +#: Ch-Advanced-Resources.xml:786(para) +msgid "Slave resources: $OCF_RESKEY_CRM_meta_notify_slave_resource" +msgstr "Resurse Slave: $OCF_RESKEY_CRM_meta_notify_slave_resource" + +#: Ch-Advanced-Resources.xml:773(para) +#: Ch-Advanced-Resources.xml:789(para) +#: Ch-Advanced-Resources.xml:818(para) +#: Ch-Advanced-Resources.xml:850(para) +#: Ch-Advanced-Resources.xml:886(para) +msgid "Resources to be promoted: $OCF_RESKEY_CRM_meta_notify_promote_resource" +msgstr "Resursele care vor fi promovate: $OCF_RESKEY_CRM_meta_notify_promote_resource" + +#: Ch-Advanced-Resources.xml:774(para) +#: Ch-Advanced-Resources.xml:790(para) +#: Ch-Advanced-Resources.xml:819(para) +#: Ch-Advanced-Resources.xml:851(para) +#: Ch-Advanced-Resources.xml:887(para) +msgid "Resources to be demoted: $OCF_RESKEY_CRM_meta_notify_demote_resource" +msgstr "Resursele care vor fi degradate: $OCF_RESKEY_CRM_meta_notify_demote_resource" + +#: Ch-Advanced-Resources.xml:778(para) +msgid "Post-notification (demote) / Pre-notification (stop)" +msgstr "Post-notificare (degradează) / Pre-notificare (oprire)" + +#: Ch-Advanced-Resources.xml:781(para) +#: Ch-Advanced-Resources.xml:802(para) +#: Ch-Advanced-Resources.xml:832(para) +#: Ch-Advanced-Resources.xml:866(para) +msgid "Master resources:" +msgstr "Resurse Master:" + +#: Ch-Advanced-Resources.xml:783(para) +#: Ch-Advanced-Resources.xml:804(para) +#: Ch-Advanced-Resources.xml:834(para) +#: Ch-Advanced-Resources.xml:868(para) +msgid "$OCF_RESKEY_CRM_meta_notify_master_resource" +msgstr "$OCF_RESKEY_CRM_meta_notify_master_resource" + +#: Ch-Advanced-Resources.xml:784(para) +#: Ch-Advanced-Resources.xml:805(para) +#: Ch-Advanced-Resources.xml:835(para) +#: Ch-Advanced-Resources.xml:869(para) +msgid "minus $OCF_RESKEY_CRM_meta_notify_demote_resource" +msgstr "minus $OCF_RESKEY_CRM_meta_notify_demote_resource" + +#: Ch-Advanced-Resources.xml:792(para) +#: Ch-Advanced-Resources.xml:821(para) +#: Ch-Advanced-Resources.xml:854(para) +#: Ch-Advanced-Resources.xml:891(para) +msgid "Resources that were demoted: $OCF_RESKEY_CRM_meta_notify_demote_resource" +msgstr "Resurse care au fost degradate: $OCF_RESKEY_CRM_meta_notify_demote_resource" + +#: Ch-Advanced-Resources.xml:807(para) +#: Ch-Advanced-Resources.xml:837(para) +#: Ch-Advanced-Resources.xml:872(para) +msgid "Slave resources:" +msgstr "Resurse Slave:" + +#: Ch-Advanced-Resources.xml:809(para) +#: Ch-Advanced-Resources.xml:839(para) +#: Ch-Advanced-Resources.xml:874(para) +msgid "$OCF_RESKEY_CRM_meta_notify_slave_resource" +msgstr "$OCF_RESKEY_CRM_meta_notify_slave_resource" + +#: Ch-Advanced-Resources.xml:824(para) +msgid "Post-notification (start) / Pre-notification (promote)" +msgstr "Post-notificare (pornire) / Pre-notificare (promovează)" + +#: Ch-Advanced-Resources.xml:858(para) +msgid "Post-notification (promote)" +msgstr "Post-notificare (promovează)" + +#: Ch-Advanced-Resources.xml:870(para) +msgid "plus $OCF_RESKEY_CRM_meta_notify_promote_resource" +msgstr "plus $OCF_RESKEY_CRM_meta_notify_promote_resource" + +#: Ch-Advanced-Resources.xml:877(para) +msgid "minus $OCF_RESKEY_CRM_meta_notify_promote_resource" +msgstr "minus $OCF_RESKEY_CRM_meta_notify_promote_resource" + +#: Ch-Advanced-Resources.xml:890(para) +msgid "Resources that were promoted: $OCF_RESKEY_CRM_meta_notify_promote_resource" +msgstr "Resursele care au fost promovate: $OCF_RESKEY_CRM_meta_notify_promote_resource" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ch-Advanced-Resources.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ch-Basics.po b/doc/Pacemaker_Explained/ro-RO/Ch-Basics.po new file mode 100644 index 0000000000..d4381f70de --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ch-Basics.po @@ -0,0 +1,577 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-25 03:36+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: Ch-Basics.xml:264(None) +msgid "@@image: 'images/Policy-Engine-small.png'; md5=THIS FILE DOESN'T EXIST" +msgstr "@@image: 'images/Policy-Engine-small.png'; md5=ACEST FIŞIER NU EXISTĂ" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: Ch-Basics.xml:296(None) +msgid "@@image: 'images/Policy-Engine-big.png'; md5=THIS FILE DOESN'T EXIST" +msgstr "@@image: 'images/Policy-Engine-big.png'; md5=ACEST FIŞIER NU EXISTĂ" + +#: Ch-Basics.xml:1(title) +msgid "Configuration Basics" +msgstr "Bazele Configurării" + +#: Ch-Basics.xml:3(title) +msgid "Configuration Layout" +msgstr "Aşezarea Configuraţiei" + +#: Ch-Basics.xml:4(para) +msgid "The cluster is written using XML notation and divided into two main sections: configuration and status." +msgstr "Clusterul este scris folosind notaţie XML şi este împărţit în două secţiuni principale: configurare şi status." + +#: Ch-Basics.xml:5(para) +msgid "The status section contains the history of each resource on each node and based on this data, the cluster can construct the complete current state of the cluster. The authoritative source for the status section is the local resource manager (lrmd) process on each cluster node and the cluster will occasionally repopulate the entire section. For this reason it is never written to disk and admin's are advised against modifying it in any way." +msgstr "Secţiunea de status conţine istoricul fiecărei resurse de pe fiecare nod şi pe baza acestor date, clusterul poate construi starea curentă completă a clusterului. Sursa autoritativă pentru secţiunea de status este procesul managerului de resurse local (lrmd) pe fiecare nod din cluster iar clusterul va repopula în mod ocazional întreaga secţiune. Din acest motiv nu este scris niciodată pe disc iar administratorii sunt sfătuiţi împotriva modificării în orice fel a acestuia." + +#: Ch-Basics.xml:10(para) +msgid "The configuration section contains the more traditional information like cluster options, lists of resources and indications of where they should be placed. The configuration section is the primary focus of this document." +msgstr "Secţiunea de configurare conţine informaţiile mai tradiţionale precum opţiuni ale clusterului, liste de resurse şi indicaţii despre unde ar trebui acestea plasate. Secţiunea de configurare este scopul primar al acestui document." + +#: Ch-Basics.xml:14(para) +msgid "The configuration section itself is divided into four parts:" +msgstr "Secţiunea de configurare în sine este împărţită în patru părţi:" + +#: Ch-Basics.xml:16(para) +msgid "Configuration options (called crm_config)" +msgstr "Opţiuni de configurare (numite crm_config)" + +#: Ch-Basics.xml:17(para) +msgid "Nodes" +msgstr "Noduri" + +#: Ch-Basics.xml:18(para) +msgid "Resources" +msgstr "Resurse" + +#: Ch-Basics.xml:19(para) +msgid "Resource relationships (called constraints)" +msgstr "Relaţii între resurse (numite restricţii)" + +#: Ch-Basics.xml:22(title) +msgid "An empty configuration" +msgstr "O configuraţie goală" + +#: Ch-Basics.xml:39(title) +msgid "The Current State of the Cluster" +msgstr "Starea Curentă a Clusterului" + +#: Ch-Basics.xml:40(para) +msgid "Before one starts to configure a cluster, it is worth explaining how to view the finished product. For this purpose we have created the crm_mon utility that will display the current state of an active cluster. It can show the cluster status by node or by resource and can be used in either single-shot or dynamically-updating mode. There are also modes for displaying a list of the operations performed (grouped by node and resource) as well as information about failures." +msgstr "Înainte de a începe să configurăm clusterul, merită explicat cum să vizualizăm produsul finit. Pentru acest scop am creat utilitarul crm_mon care va arăta starea curentă a unui cluster activ. Poate arăta status-ul clusterului după nod sau după resurse şi poate fi folosit fie în mod single-shot sau dynamically-updating. Sunt moduri pentru prezentarea unei liste de operaţiuni efectuate (grupată după nod si resursă) precum şi informaţii despre eşecuri." + +#: Ch-Basics.xml:46(para) +msgid "Using this tool, you can examine the state of the cluster for irregularities and see how it responds when you cause or simulate failures." +msgstr "Folosind acest utilitar, puteţi examina starea clusterului pentru neconcordanţe şi pentru a vedea cum răspunde atunci când provocaţi sau simulaţi eşecuri." + +#: Ch-Basics.xml:47(para) +msgid "Details on all the available options can be obtained using the crm_mon --help command." +msgstr "Detalii despre toate opţiunile disponibile pot fi obţinute folosind comanda crm_mon --help." + +#: Ch-Basics.xml:49(title) +msgid "Sample output from crm_mon" +msgstr "Exemplu de rezultat obţinut din crm_mon" + +#: Ch-Basics.xml:51(command) +msgid "# crm_mon" +msgstr "# crm_mon" + +#: Ch-Basics.xml:50(screen) +#, no-wrap +msgid "" +"\n" +" \n" +" ============\n" +" Last updated: Fri Nov 23 15:26:13 2007\n" +" Current DC: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec)\n" +" 3 Nodes configured.\n" +" 5 Resources configured.\n" +" ============\n" +"\n" +" Node: sles-1 (1186dc9a-324d-425a-966e-d757e693dc86): online\n" +" 192.168.100.181 (heartbeat::ocf:IPaddr): Started sles-1\n" +" 192.168.100.182 (heartbeat:IPaddr): Started sles-1\n" +" 192.168.100.183 (heartbeat::ocf:IPaddr): Started sles-1\n" +" rsc_sles-1 (heartbeat::ocf:IPaddr): Started sles-1\n" +" child_DoFencing:2 (stonith:external/vmware): Started sles-1\n" +" Node: sles-2 (02fb99a8-e30e-482f-b3ad-0fb3ce27d088): standby\n" +" Node: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec): online\n" +" rsc_sles-2 (heartbeat::ocf:IPaddr): Started sles-3\n" +" rsc_sles-3 (heartbeat::ocf:IPaddr): Started sles-3\n" +" child_DoFencing:0 (stonith:external/vmware): Started sles-3" +msgstr "" +"\n" +" \n" +" ============\n" +" Last updated: Fri Nov 23 15:26:13 2007\n" +" Current DC: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec)\n" +" 3 Nodes configured.\n" +" 5 Resources configured.\n" +" ============\n" +"\n" +" Node: sles-1 (1186dc9a-324d-425a-966e-d757e693dc86): online\n" +" 192.168.100.181 (heartbeat::ocf:IPaddr): Started sles-1\n" +" 192.168.100.182 (heartbeat:IPaddr): Started sles-1\n" +" 192.168.100.183 (heartbeat::ocf:IPaddr): Started sles-1\n" +" rsc_sles-1 (heartbeat::ocf:IPaddr): Started sles-1\n" +" child_DoFencing:2 (stonith:external/vmware): Started sles-1\n" +" Node: sles-2 (02fb99a8-e30e-482f-b3ad-0fb3ce27d088): standby\n" +" Node: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec): online\n" +" rsc_sles-2 (heartbeat::ocf:IPaddr): Started sles-3\n" +" rsc_sles-3 (heartbeat::ocf:IPaddr): Started sles-3\n" +" child_DoFencing:0 (stonith:external/vmware): Started sles-3" + +#: Ch-Basics.xml:72(title) +msgid "Sample output from crm_mon -n" +msgstr "Exemplu de rezultat obţinut din crm_mon -n" + +#: Ch-Basics.xml:74(command) +msgid "# crm_mon -n" +msgstr "# crm_mon -n" + +#: Ch-Basics.xml:73(screen) +#, no-wrap +msgid "" +"\n" +" \n" +" ============\n" +" Last updated: Fri Nov 23 15:26:13 2007\n" +" Current DC: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec)\n" +" 3 Nodes configured.\n" +" 5 Resources configured.\n" +" ============\n" +"\n" +" Node: sles-1 (1186dc9a-324d-425a-966e-d757e693dc86): online\n" +" Node: sles-2 (02fb99a8-e30e-482f-b3ad-0fb3ce27d088): standby\n" +" Node: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec): online\n" +"\n" +" Resource Group: group-1\n" +" 192.168.100.181 (heartbeat::ocf:IPaddr): Started sles-1\n" +" 192.168.100.182 (heartbeat:IPaddr): Started sles-1\n" +" 192.168.100.183 (heartbeat::ocf:IPaddr): Started sles-1\n" +" rsc_sles-1 (heartbeat::ocf:IPaddr): Started sles-1\n" +" rsc_sles-2 (heartbeat::ocf:IPaddr): Started sles-3\n" +" rsc_sles-3 (heartbeat::ocf:IPaddr): Started sles-3\n" +" Clone Set: DoFencing\n" +" child_DoFencing:0 (stonith:external/vmware): Started sles-3\n" +" child_DoFencing:1 (stonith:external/vmware): Stopped\n" +" child_DoFencing:2 (stonith:external/vmware): Started sles-1" +msgstr "" +"\n" +" \n" +" ============\n" +" Last updated: Fri Nov 23 15:26:13 2007\n" +" Current DC: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec)\n" +" 3 Nodes configured.\n" +" 5 Resources configured.\n" +" ============\n" +"\n" +" Node: sles-1 (1186dc9a-324d-425a-966e-d757e693dc86): online\n" +" Node: sles-2 (02fb99a8-e30e-482f-b3ad-0fb3ce27d088): standby\n" +" Node: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec): online\n" +"\n" +" Resource Group: group-1\n" +" 192.168.100.181 (heartbeat::ocf:IPaddr): Started sles-1\n" +" 192.168.100.182 (heartbeat:IPaddr): Started sles-1\n" +" 192.168.100.183 (heartbeat::ocf:IPaddr): Started sles-1\n" +" rsc_sles-1 (heartbeat::ocf:IPaddr): Started sles-1\n" +" rsc_sles-2 (heartbeat::ocf:IPaddr): Started sles-3\n" +" rsc_sles-3 (heartbeat::ocf:IPaddr): Started sles-3\n" +" Clone Set: DoFencing\n" +" child_DoFencing:0 (stonith:external/vmware): Started sles-3\n" +" child_DoFencing:1 (stonith:external/vmware): Stopped\n" +" child_DoFencing:2 (stonith:external/vmware): Started sles-1" + +#: Ch-Basics.xml:98(para) +msgid "The DC (Designated Controller) node is where all the decisions are made and if the current DC fails a new one is elected from the remaining cluster nodes. The choice of DC is of no significance to an administrator beyond the fact that its logs will generally be more interesting." +msgstr "Nodul DC (Desemnat Controlor) este locul unde toate deciziile sunt luate şi dacă DC-ul curent eşuează unul nou este ales din nodurile rămase în cluster. Alegerea unui DC nu are nici o semnificaţie pentru administrator dincolo de faptul că logurile acestuia vor fi în general mai interesante." + +#: Ch-Basics.xml:104(title) +msgid "How Should the Configuration be Updated?" +msgstr "Cum Ar Trebui să fie Actualizată Configuraţia" + +#: Ch-Basics.xml:105(para) +msgid "There are three basic rules for updating the cluster configuration:" +msgstr "Sunt trei reguli de bază pentru actualizarea configuraţiei clusterului:" + +#: Ch-Basics.xml:107(para) +msgid "Rule 1 - Never edit the cib.xml file manually. Ever. I'm not making this up." +msgstr "Regula 1 - Nu editaţi niciodată fişierul cib.xml manual. Niciodată. Nu inventez acest lucru." + +#: Ch-Basics.xml:108(para) +msgid "Rule 2 - Read Rule 1 again." +msgstr "Regula 2 - Citiţi Regula 1 din nou." + +#: Ch-Basics.xml:109(para) +msgid "Rule 3 - The cluster will notice if you ignored rules 1 & 2 and refuse to use the configuration." +msgstr "Regula 3 - Clusterul va detecta că aţi ignorat regulile 1 & 2 şi va refuza să folosească configuraţia." + +#: Ch-Basics.xml:111(para) +msgid "Now that it is clear how NOT to update the configuration, we can begin to explain how you should." +msgstr "Acum că este clar cum să NU actualizăm configuraţia, putem începe să explicăm cum ar trebui să realizăm acest lucru." + +#: Ch-Basics.xml:112(para) +msgid "The most powerful tool for modifying the configuration is the cibadmin command which talks to a running cluster. With cibadmin, the user can query, add, remove, update or replace any part of the configuration and all changes take effect immediately so there is no need to perform a reload-like operation." +msgstr "Cea mai puternică unealtă pentru modificarea configuraţiei este comanda cibadmin care comunică cu un cluster funcţional. Cu cibadmin, utilizatorul poate interoga, adăuga, înlătura, actualiza sau înlocui orice parte a configuraţiei şi toate modificările iau efect imediat aşa că nu este necesar să executaţi operaţiuni de tip reîncărcare." + +#: Ch-Basics.xml:116(para) +msgid "The simplest way of using cibadmin is to use it to save the current configuration to a temporary file, edit that file with your favorite text or XML editor and then upload the revised configuration." +msgstr "Cel mai simplu mod de a folosi cibadmin este de a-l folosi pentru a salva configuraţia curentă într-un fişier temporar, să editaţi acel fişier cu editorul de text sau XML favorit şi apoi să încărcaţi configuraţia revizuită." + +#: Ch-Basics.xml:118(title) +msgid "Safely using an editor to modify the cluster configuration" +msgstr "Folosind cu siguranţă un editor pentru a modifica configuraţia clusterului" + +#: Ch-Basics.xml:120(command) +msgid "cibadmin --query > tmp.xml" +msgstr "cibadmin --query > tmp.xml" + +#: Ch-Basics.xml:121(command) +#: Ch-Basics.xml:134(command) +msgid "vi tmp.xml" +msgstr "vi tmp.xml" + +#: Ch-Basics.xml:122(command) +msgid "cibadmin --replace --xml-file tmp.xml" +msgstr "cibadmin --replace --xml-file tmp.xml" + +#: Ch-Basics.xml:125(para) +msgid "Some of the better XML editors can make use of a Relax NG schema to help make sure any changes you make are valid. The schema describing the configuration can normally be found in /usr/lib/heartbeat/pacemaker.rng on most systems." +msgstr "Unele dintre editoarele mai bune de XML pot folosi schema Relax NG pentru a vă ajuta să fiţi siguri că modificările pe care le realizaţi sunt valide. Schema care descrie configuraţia poate fi găsită în mod normal în /usr/lib/heartbeat/pacemaker.rng pe majoritatea sistemelor." + +#: Ch-Basics.xml:129(para) +msgid "If you only wanted to modify the resources section, you could instead do" +msgstr "Dacă aţi dorit să modificaţi doar secţiunea de resurse, aţi putea alternativ să executaţi" + +#: Ch-Basics.xml:131(title) +msgid "Safely using an editor to modify a subsection of the cluster configuration" +msgstr "Folosind cu siguranţă un editor pentru a modifica o subsecţiune din configuraţia clusterlui" + +#: Ch-Basics.xml:133(command) +msgid "cibadmin --query --obj_type resources > tmp.xml" +msgstr "cibadmin --query --obj_type resources > tmp.xml" + +#: Ch-Basics.xml:135(command) +msgid "cibadmin --replace --obj_type resources --xml-file tmp.xml" +msgstr "cibadmin --replace --obj_type resources --xml-file tmp.xml" + +#: Ch-Basics.xml:138(para) +msgid "to avoid modifying any other part of the configuration." +msgstr "pentru a evita modificările survenite la orice altă parte a configuraţiei." + +#: Ch-Basics.xml:141(title) +msgid "Quickly Deleting Part of the Configuration" +msgstr "Ştergerea Rapidă a unei Părţi din Configuraţie" + +#: Ch-Basics.xml:142(para) +msgid "Identify the object you wish to delete. eg." +msgstr "Identificaţi obiectul pe care doriţi să îl ştergeţi. ex." + +#: Ch-Basics.xml:144(title) +msgid "Searching for STONITH related configuration items" +msgstr "Căutând pentru elemente de configurare legate de STONITH" + +#: Ch-Basics.xml:146(command) +msgid "# cibadmin -Q | grep stonith" +msgstr "# cibadmin -Q | grep stonith" + +#: Ch-Basics.xml:160(para) +msgid "Next identify the resource's tag name and id (in this case we'll choose primitive and child_DoFencing). Then simply execute:" +msgstr "Apoi identificaţi numele tag-ului resursei şi id-ul (în acest caz vom alege primitive şi child_DoFencing). Apoi executaţi:" + +#: Ch-Basics.xml:164(command) +msgid "cibadmin --delete --crm_xml ‘<primitive id=\"child_DoFencing\"/>'" +msgstr "cibadmin --delete --crm_xml ‘<primitive id=\"child_DoFencing\"/>'" + +#: Ch-Basics.xml:167(title) +msgid "Updating the Configuration Without Using XML" +msgstr "Updatând Configuraţia Fără să Folosim XML" + +#: Ch-Basics.xml:168(para) +msgid "Some common tasks can also be performed with one of the higher level tools that avoid the need to read or edit XML." +msgstr "Câteva task-uri comune pot fi efectuate de asemenea cu unul dintre utilitarele de nivel înalt pentru a evita nevoia de a citi sau edita XML." + +#: Ch-Basics.xml:169(para) +msgid "To enable stonith for example, one could run:" +msgstr "Pentru a activa stonith de exemplu, aţi putea rula:" + +#: Ch-Basics.xml:170(command) +msgid "crm_attribute --attr-name stonith-enabled --attr-value true" +msgstr "crm_attribute --attr-name stonith-enabled --attr-value true" + +#: Ch-Basics.xml:171(para) +msgid "Or to see if somenode is allowed to run resources, there is:" +msgstr "Sau pentru a vedea dacă unui nod îi este permis să ruleze resurse, există:" + +#: Ch-Basics.xml:172(command) +msgid "crm_standby --get-value --node-uname somenode" +msgstr "crm_standby --get-value --node-uname somenode" + +#: Ch-Basics.xml:173(para) +msgid "Or to find the current location of my-test-rsc one can use:" +msgstr "Sau pentru a afla locaţia curentă a my-test-rsc aţi putea folosi:" + +#: Ch-Basics.xml:174(command) +msgid "crm_resource --locate --resource my-test-rsc" +msgstr "crm_resource --locate --resource my-test-rsc" + +#: Ch-Basics.xml:177(title) +msgid "Making Configuration Changes in a Sandbox" +msgstr "Realizând Modificări de Configurare într-un Sandbox" + +#: Ch-Basics.xml:178(para) +msgid "Often it is desirable to preview the effects of a series of changes before updating the configuration atomically. For this purpose we have created crm_shadow which creates a \"shadow\" copy of the configuration and arranges for all the command line tools to use it." +msgstr "Deseori este de dorit să previzualizaţi efectele unei serii de modificări înainte să actualizaţi configuraţia în mod atomic. Pentru acest scop am creat crm_shadow care creează o copie \"ascunsă\" a configuraţiei şi aranjează astfel încât toate utilitarele din linia de comandă să o folosească." + +#: Ch-Basics.xml:185(para) +msgid "Shadow copies are identified with a name, making it possible to have more than one" +msgstr "Copiile ascunse sunt identificate cu un nume, fiind posibil să avem mai mult de una" + +#: Ch-Basics.xml:187(para) +msgid "Read the above carefully, failure to do so could result in you destroying the cluster's active configuration" +msgstr "Citiţi cele de mai sus cu atenţie, nerespectarea acestora poate rezulta în distrugerea de către voi a configuraţiei active a clusterului " + +#: Ch-Basics.xml:182(para) +msgid "To begin, simply invoke crm_shadow and give it the name of a configuration to create and be sure to follow the simple on-screen instructions. " +msgstr "Pentru a începe, invocaţi pur şi simplu crm_shadow şi daţi-i numele unei configuraţii pe care să o creeze şi asiguraţi-vă că urmaţi simplele instrucţiuni de pe ecran. " + +#: Ch-Basics.xml:190(title) +msgid "Creating and displaying the active sandbox" +msgstr "Crearea şi prezentarea sandbox-ului activ" + +#: Ch-Basics.xml:191(programlisting) +#, no-wrap +msgid "" +"\n" +" # crm_shadow --create test\n" +" Setting up shadow instance\n" +" Type Ctrl-D to exit the crm_shadow shell\n" +" shadow[test]: \n" +" shadow[test] # crm_shadow --which\n" +" test" +msgstr "" +"\n" +" # crm_shadow --create test\n" +" Setting up shadow instance\n" +" Type Ctrl-D to exit the crm_shadow shell\n" +" shadow[test]: \n" +" shadow[test] # crm_shadow --which\n" +" test" + +#: Ch-Basics.xml:199(para) +msgid "From this point on, all cluster commands will automatically use the shadow copy instead of talking to the cluster's active configuration. Once you have finished experimenting, you can either commit the changes, or discard them as shown below. Again, be sure to follow the on-screen instructions carefully." +msgstr "Din acest punct înainte, toate comenzile clusterului vor folosi copia ascunsă în loc să comunice cu copia activă a configuraţiei clusterului. Odată ce aţi terminat de experimentat, puteţi fie să aplicaţi modificările sau să le înlăturaţi după cum este prezentat mai jos. Din nou, asiguraţi-vă că urmaţi instrucţiunile de pe ecran cu grijă." + +#: Ch-Basics.xml:204(para) +msgid "For a full list of crm_shadow options and commands, invoke it with the --help option." +msgstr "Pentru o listă completă de opţiuni şi comenzi ale crm_shadow, apelaţi-l cu opţiunea --help." + +#: Ch-Basics.xml:206(title) +msgid "Using a sandbox to make multiple changes atomically" +msgstr "Folosirea unui sandbox pentru a realiza mai multe modificări în mod atomic" + +#: Ch-Basics.xml:207(programlisting) +#, no-wrap +msgid "" +"\n" +" shadow[test] # crm_failcount -G -r rsc_c001n01\n" +" name=fail-count-rsc_c001n01 value=0\n" +" shadow[test] # crm_standby -v on -n c001n02\n" +" shadow[test] # crm_standby -G -n c001n02\n" +" name=c001n02 scope=nodes value=on\n" +" shadow[test] # cibadmin --erase --force\n" +" shadow[test] # cibadmin --query\n" +"\n" +" \n" +" \n" +" \n" +" \n" +" \n" +" \n" +" \n" +" \n" +"]]>\n" +" shadow[test] # crm_shadow --delete test --force\n" +" Now type Ctrl-D to exit the crm_shadow shell\n" +" shadow[test] # exit\n" +" # crm_shadow --which\n" +" No shadow instance provided\n" +" # cibadmin -Q\n" +"\n" +" \n" +" \n" +" \n" +" \n" +" \n" +"]]>\n" +"\t" +msgstr "" +"\n" +" shadow[test] # crm_failcount -G -r rsc_c001n01\n" +" name=fail-count-rsc_c001n01 value=0\n" +" shadow[test] # crm_standby -v on -n c001n02\n" +" shadow[test] # crm_standby -G -n c001n02\n" +" name=c001n02 scope=nodes value=on\n" +" shadow[test] # cibadmin --erase --force\n" +" shadow[test] # cibadmin --query\n" +"\n" +" \n" +" \n" +" \n" +" \n" +" \n" +" \n" +" \n" +" \n" +"]]>\n" +" shadow[test] # crm_shadow --delete test --force\n" +" Now type Ctrl-D to exit the crm_shadow shell\n" +" shadow[test] # exit\n" +" # crm_shadow --which\n" +" No shadow instance provided\n" +" # cibadmin -Q\n" +"\n" +" \n" +" \n" +" \n" +" \n" +" \n" +"]]>\n" +"\t" + +#: Ch-Basics.xml:243(para) +msgid "Making changes in a sandbox and verifying the real configuration is untouched" +msgstr "Realizarea de modificări într-un sandbox şi apoi verificarea că, configuraţia reală nu este atinsă." + +#: Ch-Basics.xml:247(title) +msgid "Testing Your Configuration Changes" +msgstr "Testarea Modificărilor Voastre de Configurare" + +#: Ch-Basics.xml:248(para) +msgid "We saw previously how to make a series of changes to a \"shadow\" copy of the configuration. Before loading the changes back into the cluster (eg. crm_shadow --commit mytest --force), it is often advisable to simulate the effect of the changes with ptest. Eg." +msgstr "Am văzut anterior cum să realizăm o serie de modificări într-o copie \"ascunsă\" a configuraţiei. Înainte de a încărca modificările înapoi în cluster (ex. crm_shadow --commit mytest --force), este adeseori recomandat să simulaţi efectul modificărilor cu ptest. Ex." + +#: Ch-Basics.xml:252(filename) +msgid "tmp.dot" +msgstr "tmp.dot" + +#: Ch-Basics.xml:252(command) +msgid "ptest --live-check -VVVVV --save-graph tmp.graph --save-dotfile " +msgstr "ptest --live-check -VVVVV --save-graph tmp.graph --save-dotfile " + +#: Ch-Basics.xml:253(para) +msgid "The tool uses the same library as the live cluster to show what it would have done given the supplied input. It's output, in addition to a significant amount of logging, is stored in two files tmp.graph and tmp.dot, both are representations of the same thing -- the cluster's response to your changes. In the graph file is stored the complete transition, containing a list of all the actions, their parameters and their pre-requisites. Because the transition graph is not terribly easy to read, the tool also generates a Graphviz dot-file representing the same information." +msgstr "Utilitarul foloseşte aceeaşi bibliotecă precum clusterul activ pentru a arăta ce ar fi realizat cu informaţiile primite. Rezultatul de ieşire, suplimentar la o cantitate semnificativă de loguri, este stocat în două fişiere tmp.graph şi tmp.dot, ambele sunt reprezentări ale aceluiaşi lucru -- răspunsul clusterului la modificările voastre. În fişierul graf este stocată tranziţia completă, conţinând o listă cu toate acţiunile, parametrii acestora şi cerinţele premergătoare ale acestora. Pentru că graful de tranziţie nu este foarte uşor de citit, utilitarul generează un fişier Graphviz dot de asemenea reprezentând aceleaşi informaţii." + +#: Ch-Basics.xml:261(title) +msgid "Small Cluster Transition" +msgstr "Tranziţia unui Cluster Mic" + +#: Ch-Basics.xml:266(caption) +msgid "An example transition graph as represented by Graphviz" +msgstr "Un exemplu de graf de tranziţie aşa cum este reprezentat de Graphviz" + +#: Ch-Basics.xml:270(para) +msgid "Interpreting the Graphviz output" +msgstr "Interpretarea rezultatului de ieşire al Graphviz" + +#: Ch-Basics.xml:272(para) +msgid "Arrows indicate ordering dependencies" +msgstr "Săgeţile indică dependinţele de ordonare" + +#: Ch-Basics.xml:273(para) +msgid "Dashed-arrows indicate dependencies that are not present in the transition graph" +msgstr "Săgeţile întrerupte de cratime indică dependinţe care nu sunt prezente în graful de tranziţie" + +#: Ch-Basics.xml:274(para) +msgid "Actions with a dashed border of any color do not form part of the transition graph" +msgstr "Acţiunile cu o margine întreruptă cu cratime de orice culoare nu se formează ca parte a grafului de tranziţie" + +#: Ch-Basics.xml:275(para) +msgid "Actions with a green border form part of the transition graph" +msgstr "Acţiunile cu o margine verde se formează ca parte a grafului de tranziţie" + +#: Ch-Basics.xml:276(para) +msgid "Actions with a red border are ones the cluster would like to execute but are unrunnable" +msgstr "Acţiunile cu o margine roşie sunt cele pe care clusterul ar dori să le execute dar sunt neexecutabile" + +#: Ch-Basics.xml:277(para) +msgid "Actions with a blue border are ones the cluster does not feel need to be executed" +msgstr "Acţiunile cu o margine albastră sunt cele pe care clusterul nu consideră că trebuie executate" + +#: Ch-Basics.xml:278(para) +msgid "Actions with orange text are pseudo/pretend actions that the cluster uses to simplify the graph" +msgstr "Acţiunile cu text portocaliu sunt acţiuni pseudo/de prefacere pe care clusterul le foloseşte pentru a simplifica graful" + +#: Ch-Basics.xml:279(para) +msgid "Actions with black text are sent to the LRM" +msgstr "Acţiunile cu text negru sunt trimise la LRM" + +#: Ch-Basics.xml:280(para) +msgid "Resource actions have text of the form rsc_action_intervalnode" +msgstr "Acţiunile resurselor au textul de forma rsc_action_intervalnode" + +#: Ch-Basics.xml:281(para) +msgid "Any action depending on an action with a red border will not be able to execute." +msgstr "Orice acţiune care depine de o acţiune cu o margine roşie nu va putea să se execute." + +#: Ch-Basics.xml:282(para) +msgid "Loops are really bad. Please report them to the development team." +msgstr "Buclele de execuţie sunt foarte rele. Vă rugăm să le raportaţi echipei de dezvoltare." + +#: Ch-Basics.xml:284(para) +msgid "In the above example, it appears that a new node, node2, has come online and that the cluster is checking to make sure rsc1, rsc2 and rsc3 are not already running there (Indicated by the *_monitor_0 entries). Once it did that, and assuming the resources were not active there, it would have liked to stop rsc1 and rsc2 on node1 and move them to node2. However, there appears to be some problem and the cluster cannot or is not permitted to perform the stop actions which implies it also cannot perform the start actions. For some reason the cluster does not want to start rsc3 anywhere." +msgstr "În exemplul de mai sus, se pare că un nod nou, node2, a ajuns online şi clusterul verifică să se asigure că rsc1, rsc2 şi rsc3, nu rulează deja acolo (aspect indicat de intrările *_monitor_0). Odată ce a realizat acest lucru şi mergând pe presupunerea că resursele nu erau active acolo, ar fi preferat să oprească rsc1 şi rsc2 pe node1 şi să le mute pe node2. Totuşi se pare că există o problemă şi clusterul nu poate sau nu îi este permis să execute operaţiunile de oprire, fapt care implică neputinţa de a efectua acţiunile de pornire de asemenea. Pentru un motiv anume clusterul nu vrea să pornească rsc3 nicăieri." + +#: Ch-Basics.xml:290(para) +msgid "For information on the options supported by ptest, use ptest --help" +msgstr "Pentru informaţii legate de opţiunile suportate de ptest, folosiţi ptest --help" + +#: Ch-Basics.xml:293(title) +msgid "Complex Cluster Transition" +msgstr "Tranziţii Complexe ale Clusterului" + +#: Ch-Basics.xml:298(caption) +msgid "Another, slightly more complex, transition graph that you're not expected to be able to read" +msgstr "Un alt graf de tranziţie, ceva mai complex, pe care nu sunteţi aşteaptaţi să îl puteţi citi" + +#: Ch-Basics.xml:304(title) +msgid "Do I Need to Update the Configuration on all Cluster Nodes?" +msgstr "Trebuie să Actualizez Configuraţia pe toate Nodurile Clusterului?" + +#: Ch-Basics.xml:305(para) +msgid "No. Any changes are immediately synchronized to the other active members of the cluster." +msgstr "Nu. Orice modificări sunt sincronizate imediat către ceilalţi membri activi ai clusterului." + +#: Ch-Basics.xml:306(para) +msgid "To reduce bandwidth, the cluster only broadcasts the incremental updates that result from your changes and uses MD5 sums to ensure that each copy is completely consistent." +msgstr "Pentru a reduce consumul de lăţime de bandă, clusterul transmite numai actualizările incrementale care rezultă din modificările realizate de voi şi foloseşte hash-uri MD5 pentru a se asigura că fiecare copie este complet consistentă." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ch-Basics.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ch-Constraints.po b/doc/Pacemaker_Explained/ro-RO/Ch-Constraints.po new file mode 100644 index 0000000000..65bc98cc87 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ch-Constraints.po @@ -0,0 +1,533 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-25 04:54+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: Ch-Constraints.xml:321(None) +msgid "@@image: 'images/resource-set.png'; md5=THIS FILE DOESN'T EXIST" +msgstr "@@image: 'images/resource-set.png'; md5=ACEST FIŞIER NU EXISTĂ" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: Ch-Constraints.xml:387(None) +msgid "@@image: 'images/two-sets.png'; md5=THIS FILE DOESN'T EXIST" +msgstr "@@image: 'images/two-sets.png'; md5=ACEST FIŞIER NU EXISTĂ" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: Ch-Constraints.xml:422(None) +msgid "@@image: 'images/three-sets.png'; md5=THIS FILE DOESN'T EXIST" +msgstr "@@image: 'images/three-sets.png'; md5=ACEST FIŞIER NU EXISTĂ" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: Ch-Constraints.xml:540(None) +msgid "@@image: 'images/three-sets-complex.png'; md5=THIS FILE DOESN'T EXIST" +msgstr "@@image: 'images/three-sets-complex.png'; md5=ACEST FIŞIER NU EXISTĂ" + +#: Ch-Constraints.xml:1(title) +msgid "Resource Constraints" +msgstr "Restricţiile Resurselor" + +#: Ch-Constraints.xml:3(title) +msgid "Scores" +msgstr "Scoruri" + +#: Ch-Constraints.xml:4(para) +msgid "Scores of all kinds are integral to how the cluster works. Practically everything from moving a resource to deciding which resource to stop in a degraded cluster is achieved by manipulating scores in some way." +msgstr "Scorurile de toate tipurile sunt parte integrală din cum funcţionează clusterul. Practic orice de la mutarea unei resurse la a decide care resursă să fie oprită într-un cluster degradat este atinsă prin manipularea scorurilor în vreun fel." + +#: Ch-Constraints.xml:8(para) +msgid "Scores are calculated on a per-resource basis and any node with a negative score for a resource can't run that resource. After calculating the scores for a resource, the cluster then chooses the node with the highest one." +msgstr "Scorurile sunt calculate la nivel de resursă şi orice nod cu un scor negativ pentru o resursă nu poate rula acea resursă. După calcularea scorurilor pentru o resursă, clusterul alege mai apoi nodul cu scorul cel mai mare." + +#: Ch-Constraints.xml:13(title) +msgid "Infinity Math" +msgstr "Matematica Infinitului" + +#: Ch-Constraints.xml:14(para) +msgid "INFINITY is currently defined as 1,000,000 and addition/subtraction with it follows the following 3 basic rules:" +msgstr "INFINITY este definit în mod curent ca 1,000,000 şi adunarea/scăderea din acesta urmează următoarele 3 reguli de bază:" + +#: Ch-Constraints.xml:16(para) +msgid "Any value + INFINITY = INFINITY" +msgstr "Orice valoare + INFINITY = INFINITY " + +#: Ch-Constraints.xml:17(para) +msgid "Any value - INFINITY = -INFINITY" +msgstr "Orice valoare - INFINITY = -INFINITY" + +#: Ch-Constraints.xml:18(para) +msgid "INFINITY - INFINITY = -INFINITY" +msgstr "INFINITY - INFINITY = -INFINITY" + +#: Ch-Constraints.xml:23(title) +msgid "Deciding Which Nodes a Resource Can Run On" +msgstr "Decizând pe Care Noduri Poate Rula o Resursă" + +#: Ch-Constraints.xml:24(para) +msgid "There are two alternative strategies for specifying which nodes a resources can run on. One way is to say that by default they can run anywhere and then create location constraints for nodes that are not allowed. The other option is to have nodes \"opt-in\"... to start with nothing able to run anywhere and selectively enable allowed nodes." +msgstr "Sunt două strategii pe alternative pentru specificarea nodurilor pe care poate rula o resursă. Un mod este acela de a spune că în mod implicit acestea pot rula oriunde şi apoi să se creeze restricţii de locaţie pentru nodurile pe care acestea nu sunt permise. Cealaltă opţiune este cea de \"opt-in\" ... de a porni cu nimic fiind permis de a rula nicăieri şi de a activa în mod selectiv nodurile permise." + +#: Ch-Constraints.xml:31(title) +#: Ch-Constraints.xml:224(title) +msgid "Options" +msgstr "Opţiuni" + +#: Ch-Constraints.xml:33(title) +msgid "Options for Simple Location Constraints" +msgstr "Opţiuni pentru Restricţii Simple de Locaţie" + +#: Ch-Constraints.xml:37(entry) +#: Ch-Constraints.xml:144(entry) +#: Ch-Constraints.xml:230(entry) +msgid "Field" +msgstr "Câmp" + +#: Ch-Constraints.xml:38(entry) +#: Ch-Constraints.xml:145(entry) +#: Ch-Constraints.xml:231(entry) +msgid "Description" +msgstr "Descriere" + +#: Ch-Constraints.xml:41(entry) +#: Ch-Constraints.xml:150(entry) +#: Ch-Constraints.xml:236(entry) +msgid "id" +msgstr "id" + +#: Ch-Constraints.xml:42(entry) +#: Ch-Constraints.xml:151(entry) +#: Ch-Constraints.xml:237(entry) +msgid "A unique name for the constraint" +msgstr "Un nume unic pentru restricţie" + +#: Ch-Constraints.xml:45(entry) +#: Ch-Constraints.xml:240(entry) +msgid "rsc" +msgstr "rsc" + +#: Ch-Constraints.xml:46(entry) +msgid "A resource name" +msgstr "Un nume de resursă" + +#: Ch-Constraints.xml:49(entry) +msgid "node" +msgstr "nod" + +#: Ch-Constraints.xml:50(entry) +msgid "A node's uname" +msgstr "uname-ul unui nod" + +#: Ch-Constraints.xml:53(entry) +#: Ch-Constraints.xml:162(entry) +#: Ch-Constraints.xml:248(entry) +msgid "score" +msgstr "scor" + +#: Ch-Constraints.xml:54(literal) +#: Ch-Constraints.xml:163(emphasis) +#: Ch-Constraints.xml:249(literal) +msgid "INFINITY" +msgstr "INFINIT" + +#: Ch-Constraints.xml:54(entry) +msgid "Positive values indicate the resource can run on this node. Negative values indicate the resource can not run on this node. Values of +/- change \"can\" to \"must\"." +msgstr "Valorile pozitive indică faptul că resursa poate rula pe acest nod. Valorile negative indică faptul că resursa nu poate rula pe acest nod. Valorile +/- schimbă \"poate\" în \"trebuie\"." + +#: Ch-Constraints.xml:61(title) +msgid "Asymmetrical \"Opt-In\" Clusters" +msgstr "Clustere Asimetrice \"Opt-In\"" + +#: Ch-Constraints.xml:62(para) +msgid "To create an opt-in cluster, start by preventing resources from running anywhere by default" +msgstr "Pentru a crea un cluster opt-in, porniţi prin a împiedica resursele din a rula oriunde în mod implicit" + +#: Ch-Constraints.xml:63(command) +msgid "crm_attribute --attr-name symmetric-cluster --attr-value false" +msgstr "crm_attribute --attr-name symmetric-cluster --attr-value false" + +#: Ch-Constraints.xml:64(para) +msgid "Then start enabling nodes. The following fragment says that the web server prefers sles-1, the database prefers sles-2 and both can failover to sles-3 if their most preferred node fails." +msgstr "Apoi începeţi să activaţi noduri. Fragmentul următor spune că serverul web preferă sles-1, baza de date preferă sles-2 şi ambele pot face failover pe sles-3 dacă nodul lor cu cea mai mare preferinţă eşuează." + +#: Ch-Constraints.xml:69(title) +msgid "Example set of opt-in location constraints" +msgstr "Exemplu de restricţii de locaţie opt-in" + +#: Ch-Constraints.xml:83(title) +msgid "Symmetrical \"Opt-Out\" Clusters" +msgstr "Clustere Simetrice \"Opt-Out\"" + +#: Ch-Constraints.xml:84(para) +msgid "To create an opt-out cluster, start by allowing resources to run anywhere by default" +msgstr "Pentru a crea un cluster opt-out, începeţi prin a permite resurselor să ruleze oriunde în mod implicit" + +#: Ch-Constraints.xml:85(command) +msgid "crm_attribute --attr-name symmetric-cluster --attr-value true" +msgstr "crm_attribute --attr-name symmetric-cluster --attr-value true" + +#: Ch-Constraints.xml:86(para) +msgid "Then start disabling nodes. The following fragment is the equivalent of the above opt-in configuration." +msgstr "Apoi începeţi să dezactivaţi noduri. Următorul fragment este echivalentul configuraţiei opt-in de mai sus." + +#: Ch-Constraints.xml:91(title) +msgid "Example set of opt-out location constraints" +msgstr "Exemplu de restricţii de locaţie opt-out" + +#: Ch-Constraints.xml:103(para) +msgid "Whether you should choose opt-in or opt-out depends both on your personal preference and the make-up of your cluster. If most of your resources can run on most of the nodes, then an opt-out arrangement is likely to result in a simpler configuration. On the other-hand, if most resources can only run on a small subset of nodes an opt-in configuration might be simpler." +msgstr "Fie că ar trebui să alegeţi opt-in sau opt-out depinde atât de preferinţele voastre personale cât şi de structura clusterului vostru. Dacă majoritatea resurselor pot rula pe majoritatea nodurilor, atunci un aranjament opt-out va rezulta într-o configuraţie mai simplă. Pe partea cealaltă, dacă majoritatea resurselor pot rula doar pe un subset mic de noduri o configuraţie opt-in ar putea fi mai simplă." + +#: Ch-Constraints.xml:110(title) +msgid "What if Two Nodes Have the Same Score" +msgstr "Dacă Două Noduri Au Acelaşi Scor" + +#: Ch-Constraints.xml:111(para) +msgid "If two nodes have the same score, then the cluster will choose one. This choice may seem random and may not be what was intended, however the cluster was not given enough information to know what was intended." +msgstr "Dacă două noduri au acelaşi scor, atunci clusterul va alege unul. Această alegere poate părea aleatorie şi ar putea să nu fie ceea ce s-a intenţionat, în schimb clusterului nu i-a fost dată suficientă informaţie pentru a şti care a fost intenţia." + +#: Ch-Constraints.xml:116(title) +msgid "Example of two resources that prefer two nodes equally" +msgstr "Exemplu de două resurse care preferă două noduri în mod egal" + +#: Ch-Constraints.xml:129(para) +msgid "In the example above, assuming no other constraints and an inactive cluster, Webserver would probably be placed on sles-1 and Database on sles-2. It would likely have placed Webserver based on the node's uname and Database based on the desire to spread the resource load evenly across the cluster. However other factors can also be involved in more complex configurations." +msgstr "În exemplul de mai sus, mergând pe presupunerea că nu sunt alte restricţii şi un cluster inactiv, Webserver ar fi probabil plasat pe sles-1 şi Database pe sles-2. Este probabil să fi plasat Webserver pe baza uname-ului nodului şi Database bazat pe dorinţa de a împrăştia încărcarea cu resurse în mod egal de-a lungul clusterului. Totuşi alţi factori pot fi implicaţi de asemenea în configuraţii mai complexe." + +#: Ch-Constraints.xml:137(title) +msgid "Specifying the Order Resources Should Start/Stop In" +msgstr "Specificând Ordinea în care Resursele ar Trebui să Pornească/Oprească" + +#: Ch-Constraints.xml:138(para) +msgid "The way to specify the order in which resources should start is by creating rsc_order constraints." +msgstr "Modul în care se poate specifica ordinea în care resursele ar trebui să pornească este prin crearea de restricţii rsc_order" + +#: Ch-Constraints.xml:140(title) +msgid "Properties of an Ordering Constraint" +msgstr "Proprietăţile unei Restricţii de Ordonare" + +#: Ch-Constraints.xml:154(entry) +msgid "first" +msgstr "întâi" + +#: Ch-Constraints.xml:155(entry) +msgid "The name of a resource that must be started before the then resource is allowed to." +msgstr "Numele unei resurse care trebuie pornită înainte de a îi permite resursei apoi să pornească" + +#: Ch-Constraints.xml:158(entry) +msgid "then" +msgstr "apoi" + +#: Ch-Constraints.xml:159(entry) +msgid "The name of a resource. This resource will start after the first resource." +msgstr "Numele unei resurse. Această resursă va porni după resursa întâi." + +#: Ch-Constraints.xml:163(entry) +msgid "If greater than zero, the constraint is mandatory. Otherwise it is only a suggestion. Default value: " +msgstr "Dacă este mai mare decât zero, restricţia este obligatorie. Altfel este doar o sugestie. Valoarea implicită: " + +#: Ch-Constraints.xml:167(entry) +msgid "symmetrical" +msgstr "simetric" + +#: Ch-Constraints.xml:168(emphasis) +msgid "true" +msgstr "adevărat" + +#: Ch-Constraints.xml:168(entry) +msgid "If true, which is the default, stop the resources in the reverse order. Default value: " +msgstr "Dacă este adevărat, care este şi valoarea implicită, opreşte resursele în ordine inversă. Valoarea implicită: " + +#: Ch-Constraints.xml:174(title) +msgid "Mandatory Ordering" +msgstr "Ordonarea Obligatorie" + +#: Ch-Constraints.xml:175(para) +msgid "When the then resource cannot run without the first resource being active, one should use mandatory constraints. To specify a constraint is mandatory, use a scores greater than zero. This will ensure that the then resource will react when the first resource changes state." +msgstr "Când resursa apoi nu poate rula fără ca resursa întâi să fie activă, ar trebui să folosiţi restricţii obligatorii. Pentru a specifica faptul că o restricţie este obligatorie, folosiţi scoruri mai mari decât zero. Acest lucru va asigura că resursa apoi va reacţiona atunci când resursa întâi îşi schimbă starea." + +#: Ch-Constraints.xml:181(para) +msgid "If the first resource was running and is stopped, the then resource will also be stopped (if it is running)" +msgstr "Dacâ resursa întâi rula şi este oprită, resursa apoi va fi oprită de asemenea (dacă rulează)" + +#: Ch-Constraints.xml:182(para) +msgid "If the first resource was not running and cannot be started, the then resource will be stopped (if it is running)" +msgstr "Dacă resursa întâi nu rula şi nu poate fi pornită, resursa apoi va fi oprită (dacă rulează)" + +#: Ch-Constraints.xml:183(para) +msgid "If the first resource is (re)started while the then resource is running, the then resource will be stopped and restarted" +msgstr "Dacă resursa întâi este (re)pornită în timp ce resursa apoi rulează, resursa apoi va fi oprită şi repornită" + +#: Ch-Constraints.xml:187(title) +msgid "Advisory Ordering" +msgstr "Ordonare Recomandată" + +#: Ch-Constraints.xml:188(para) +msgid "On the other-hand, when score=\"0\" is specified for a constraint, the constraint is considered optional and only has an effect when both resources are stopping and or starting. Any change in state by the first resource will have no effect on the then resource." +msgstr "Pe altă parte, când score=\"0\" este specificat pentru o restricţie, restricţia este considerată opţională şi are efect doar când ambele resurse sunt oprite sau pornite. Orice modificare a stării resursei întâi nu va avea nici un efect asupra resursei apoi." + +#: Ch-Constraints.xml:193(title) +msgid "Example of an optional and mandatory ordering constraint" +msgstr "Exemplu de restricţie de ordonare obligatorie şi recomandată" + +#: Ch-Constraints.xml:203(para) +msgid "Some additional information on ordering constraints can be found in the document Ordering Explained" +msgstr "Informaţii adiţionale despre restricţiile de ordonare pot fi găsite în documentul Ordonarea Explicată" + +#: Ch-Constraints.xml:208(title) +msgid "Placing Resources Relative to other Resources" +msgstr "Plasarea Resurselor Relativă la alte Resurse" + +#: Ch-Constraints.xml:209(para) +msgid "When the location of one resource depends on the location of another one, we call this colocation." +msgstr "Când locaţia unei resurse depinde de locaţia altei resurse, numim acest lucru colocare." + +#: Ch-Constraints.xml:215(para) +msgid "While the human brain is sophisticated enough to read the constraint in any order and choose the correct one depending on the situation, the cluster is not quite so smart. Yet." +msgstr "În timp ce creierul uman este destul de sofisticat pentru a citi o restricţie în orice ordine şi de a alege pe cea corectă în funcţie de situaţie, clusterul nu este atât de inteligent. Încâ." + +#: Ch-Constraints.xml:210(para) +msgid "There is an important side-effect of creating a colocation constraint between two resources, that it affects the order in which resources are assigned to a node. If you think about it, its somewhat obvious. You can't place A relative to B unless you know where B is . So when you are creating colocation constraints, it is important to consider whether you should colocate A with B or B with A." +msgstr "Există un efect secundar important ca urmare a creării unei restricţii de colocare între două resurse, şi anume acela că afectează ordinea în care resursele sunt asignate unui nod. Dacă stai să te gândeşti, este oarecum evident. Nu poţi plasa A relativ la B decât dacă ştii unde B este . Aşa că atunci când creaţi restricţii de colocare, este important să ţineţi cont de dacă vreţi să colocaţi A cu B sau B cu A." + +#: Ch-Constraints.xml:219(para) +msgid "Another thing to keep in mind is that, assuming A is collocated with B, the cluster will also take into account A's preferences when deciding which node to choose for B. For a detailed look at exactly how this occurs, see the Colocation Explained document." +msgstr "Un alt aspect care merită reţinut este acela că, presupunând că A este colocat cu B, clusterul va lua în considerare preferinţele lui A când va decide care nod să aleagă pentru B. Pentru o vedere detaliată asupra modului exact în care se întâmplă acest lucru, vedeţi documentul Colocarea Explicată." + +#: Ch-Constraints.xml:226(title) +msgid "Properties of a Collocation Constraint" +msgstr "Proprietăţile unei Restricţii de Colocare" + +#: Ch-Constraints.xml:241(entry) +msgid "The colocation source. If the constraint cannot be satisfied, the cluster may decide not to allow the resource to run at all." +msgstr "Sursa colocării. Dacă restricţia nu poate fi satisfăcută, clusterul poate decide să nu permită resursei să ruleze deloc." + +#: Ch-Constraints.xml:244(entry) +msgid "with-rsc" +msgstr "with-rsc" + +#: Ch-Constraints.xml:245(entry) +msgid "The colocation target. The cluster will decide where to put this resource first and then decide where to put the resource in the rsc field" +msgstr "Destinaţia colocării. Clusterul va decide unde să plaseze această resursă mai întâi şi apoi va decide unde să plaseze resursa din câmpul rsc" + +#: Ch-Constraints.xml:249(entry) +msgid "Positive values indicate the resource should run on the same node. Negative values indicate the resources should not run on the same node. Values of +/- change \"should\" to \"must\"." +msgstr "Valorile pozitive indică faptul că resursa ar trebui să ruleze pe acelaşi nod. Valorile negative indică faptul că resursele ar trebui să nu ruleze pe acelaşi nod. Valorile +/- schimbâ \"ar trebui\" în \"trebuie\"." + +#: Ch-Constraints.xml:256(title) +msgid "Mandatory Placement" +msgstr "Plasament Obligatoriu" + +#: Ch-Constraints.xml:257(para) +msgid "Mandatory placement occurs any time the constraint's score is +INFINITY or -INFINITY. In such cases, if the constraint can't be satisfied, then the rsc resource is not permitted to run. For score=INFINITY, this includes cases where the with-rsc resource is not active." +msgstr "Plasamentul obligatoriu se întâmplă oricând scorul restricţiei este +INFINITY sau -INFINITY. În astfel de cazuri, dacă restricţia poate fi satisfăcută, atunci resursei rsc nu îi este permis să ruleze. Pentru scor=INFINITY, acest aspect include cazuri în care resursa with-rsc nu este activă." + +#: Ch-Constraints.xml:262(para) +msgid "If you need resource1 to always run on the same machine as resource2, you would add the following constraint:" +msgstr "Dacă aveţi nevoie ca resource1 să ruleze întotdeauna pe aceeaşi maşină ca şi resource2, aţi adăuga următoarea restricţie:" + +#: Ch-Constraints.xml:264(title) +msgid "An example colocation constraint" +msgstr "Un exemplu de restricţie de colocare" + +#: Ch-Constraints.xml:265(programlisting) +#, no-wrap +msgid "" +"\n" +" <rsc_colocation id=\"colocate\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"INFINITY\"/>\n" +"\t " +msgstr "" +"\n" +" <rsc_colocation id=\"colocate\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"INFINITY\"/>\n" +"\t " + +#: Ch-Constraints.xml:269(para) +msgid "Remember, because INFINITY was used, if resource2 can't run on any of the cluster nodes (for whatever reason) then resource1 will not be allowed to run." +msgstr "Ţineţi minte, datorită faptului că INFINITY a fost folosit, dacă resursa2 nu poate rula pe nici unul din nodurile clusterului (indiferent de motiv) atunci resource1 nu îi va fi permis să ruleze." + +#: Ch-Constraints.xml:270(para) +msgid "Alternatively, you may want the opposite... that resource1 cannot run on the same machine as resource2. In this case use score=\"-INFINITY\"" +msgstr "Alternativ, aţi putea dori opusul... ca resource1 să nu poată rula pe aceeaşi maşină ca resource2. În acest caz folosiţi scor=\"-INFINITY\"" + +#: Ch-Constraints.xml:276(title) +msgid "An example anti-colocation constraint" +msgstr "Un exemplu de restricţie anti-colocare" + +#: Ch-Constraints.xml:277(programlisting) +#, no-wrap +msgid "" +"\n" +" <rsc_colocation id=\"anti-colocate\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"-INFINITY\"/> \n" +"\t " +msgstr "" +"\n" +" <rsc_colocation id=\"anti-colocate\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"-INFINITY\"/> \n" +"\t " + +#: Ch-Constraints.xml:281(para) +msgid "Again, by specifying -INFINTY, the constraint is binding. So if the only place left to run is where resource2 already is, then resource1 may not run anywhere." +msgstr "Din nou, specificând -INFINTY, restricţia este imutabilă. Deci singurul loc rămas pentru a rula este cel unde resource2 este deja, atunci resource1 nu poate rula nicăieri." + +#: Ch-Constraints.xml:287(title) +msgid "Advisory Placement" +msgstr "Plasament Recomandat" + +#: Ch-Constraints.xml:288(para) +msgid "If mandatory placement is about \"must\" and \"must not\", then advisory placement is the \"I'd prefer if\" alternative. For constraints with scores greater than -INFINITY and less than INFINITY, the cluster will try and accommodate your wishes but may ignore them if the alternative is to stop some of the cluster resources." +msgstr "Dacă plasamentul obligatoriu se referă la \"trebuie\" şi \"nu trebuie\", atunci plasamentul recomandat este alternativa \"aş prefera dacă\". Pentru restricţii cu scoruri mai mari decât -INFINITY şi mai mici decât INFINITY, clusterul va încerca să acomodeze dorinţele voastre dar le-ar putea ignora dacă alternativa este să oprească unele din resursele clusterului." + +#: Ch-Constraints.xml:292(para) +msgid "Like in life, where if enough people prefer something it effectively becomes mandatory, advisory colocation constraints can combine with other elements of the configuration to behave as if they were mandatory." +msgstr "Ca şi în viaţă, unde dacă destule persoane preferă ceva acest lucru devine obligatoriu, restricţiile de colocare recomandate se pot combina cu alte elemente ale configuraţiei pentru a se comporta ca şi cum ar fi obligatorii." + +#: Ch-Constraints.xml:294(title) +msgid "An example advisory-only colocation constraint" +msgstr "Un exemplu de restricţie de colocare doar recomandată" + +#: Ch-Constraints.xml:295(programlisting) +#, no-wrap +msgid "" +"\n" +" <rsc_colocation id=\"colocate-maybe\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"500\"/>\n" +"\t " +msgstr "" +"\n" +" <rsc_colocation id=\"colocate-maybe\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"500\"/>\n" +"\t " + +#: Ch-Constraints.xml:302(title) +msgid "Ordering Sets of Resources" +msgstr "Ordonarea Seturilor de Resurse" + +#: Ch-Constraints.xml:303(para) +msgid "A common situation is for an administrator to create a chain of ordered resources, such as:" +msgstr "O situaţie comună este ca un administrator să creeze un lanţ de resurse ordonate, precum:" + +#: Ch-Constraints.xml:305(title) +msgid "A chain of ordered resources" +msgstr "Un lanţ de resurse ordonate" + +#: Ch-Constraints.xml:318(title) +msgid "Ordered Set" +msgstr "Set Ordonat" + +#: Ch-Constraints.xml:323(caption) +msgid "Visual representation of the four resources' start order for the above constraints" +msgstr "Reprezentarea vizuală a ordinii de pornire a celor patru resurse pentru restricţiile de mai sus" + +#: Ch-Constraints.xml:327(para) +msgid "To simplify this situation, there is an alternate format for ordering constraints" +msgstr "Pentru a simplifica această situaţie, există un format alternativ pentru ordonarea restricţiilor" + +#: Ch-Constraints.xml:329(title) +msgid "A chain of ordered resources expressed as a set" +msgstr "Un lanţ de resurse ordonate exprimate ca un set" + +#: Ch-Constraints.xml:345(para) +msgid "Resource sets have the same ordering semantics as groups." +msgstr "Seturile de resurse au aceeaşi semantică de ordonare ca şi grupurile." + +#: Ch-Constraints.xml:347(title) +msgid "A group resource with the equivalent ordering rules" +msgstr "Un grup de resurse cu regulile de ordonare echivalente" + +#: Ch-Constraints.xml:359(para) +msgid "While the set-based format is not less verbose, it is significantly easier to get right and maintain. It can also be expanded to allow ordered sets of (un)ordered resources. In the example below, rscA and rscB can both start in parallel, as can rscC and rscD, however rscC and rscD can only start once both rscA and rscB are active." +msgstr "În timp ce formatul bazat pe seturi nu este mai puţin verbose, este semnificativ mai uşor de a nimeri şi menţine. Poate fi extins pentru a permite seturi ordonate de resurse (ne)ordonate. În exemplul de mai jos, rscA şi rscB pot porni ambele în paralel, la fel pot si rscC şi rscD, însă rscC şi rscD pot porni doar odată ce ambele rscA şi rscB sunt active." + +#: Ch-Constraints.xml:364(title) +msgid "Ordered sets of unordered resources" +msgstr "Seturi ordonate de resurse neordonate" + +#: Ch-Constraints.xml:384(title) +msgid "Two Sets of Unordered Resources" +msgstr "Două Seturi de Resurse Neordonate" + +#: Ch-Constraints.xml:389(caption) +msgid "Visual representation of the start order for two ordered sets of unordered resources" +msgstr "Reprezentarea vizuală a ordinii de pornire pentru două seturi de resurse neordonate" + +#: Ch-Constraints.xml:393(para) +msgid "Of course either or both sets of resources can also be internally ordered (by setting sequential=\"true\") and there is no limit to the number of sets that can be specified." +msgstr "Desigur că oricare sau ambele seturi de resurse pot de asemenea să fie ordonate intern (prin setarea sequential=\"true\") şi nu este nici o limită asupra numărului de seturi care poate fi specificat." + +#: Ch-Constraints.xml:395(title) +msgid "Advanced use of set ordering - Three ordered sets, two of which are internally unordered" +msgstr "Utilizări avansate ale ordonării seturilor - Trei seturi ordonate, două din care sunt neordonate intern" + +#: Ch-Constraints.xml:419(title) +msgid "Three Resources Sets" +msgstr "Trei Seturi de Resurse" + +#: Ch-Constraints.xml:424(caption) +msgid "Visual representation of the start order for the three sets defined above" +msgstr "Reprezentarea vizuală a ordinii de pornire pentru cele trei seturi definite mai sus" + +#: Ch-Constraints.xml:430(title) +msgid "Collocating Sets of Resources" +msgstr "Colocarea Seturilor de Resurse" + +#: Ch-Constraints.xml:431(para) +msgid "Another common situation is for an administrator to create a set of collocated resources. Previously this was possible either by defining a resource group (See ) which could not always accurately express the design; or by defining each relationship as an individual constraint, causing a constraint explosion as the number of resources and combinations grew." +msgstr "O altă situaţie comună este ca un administrator să creeze un set de resurse colocate. Anterior acest lucru era posibil fie prin definirea unui grup de resurse (Vedeţi ) care nu putea întotdeauna să exprime design-ul în mod corect; sau prin definirea fiecărei relaţii ca o restricţie individuală, cauzând o explozie de restricţii pe măsură ce numărul resurselor şi al combinaţiilor creştea." + +#: Ch-Constraints.xml:436(title) +msgid "A chain of collocated resources" +msgstr "Un lanţ de resurse colocate" + +#: Ch-Constraints.xml:447(para) +msgid "To make things easier, we allow an alternate form of colocation constraints using resource_sets. Just like the expanded version, a resource that can't be active also prevents any resource that must be collocated with it from being active. For example if B was not able to run, then both C (and by inference D) must also remain stopped." +msgstr "Pentru a face lucrurile mai uşoare, permitem o altă formă de restricţii de colocare folosind resource_sets (seturi de resurse). La fel ca şi versiunea extinsă, o resursă care nu poate fi activă împiedică de asemenea orice resursă care trebuie colocată cu aceasta de a fi activă. De exemplu dacă B nu era capabil să ruleze, atunci atât C (şi prin alianţă D) trebuie să rămână oprite." + +#: Ch-Constraints.xml:453(title) +msgid "The equivalent colocation chain expressed using resource_sets" +msgstr "Lanţul echivalent de restricţii de colocare exprimat folosind resource_sets" + +#: Ch-Constraints.xml:469(para) +msgid "Resource sets have the same colocation semantics as groups." +msgstr "Seturile de resurse au aceleaşi restricţii semantice ca şi grupurile." + +#: Ch-Constraints.xml:471(title) +msgid "A group resource with the equivalent colocation rules" +msgstr "O resursă de grup cu regulile echivalente de colocare" + +#: Ch-Constraints.xml:483(para) +msgid "This notation can also be used in this context to tell the cluster that a set of resources must all be located with a common peer, but have no dependencies on each other. In this scenario, unlike the previous one, B would be allowed to remain active even if A or C (or both) were inactive." +msgstr "Această notaţie poate fi folosită de asemenea în acest context pentru a spune clusterului că un set de resurse trebuie să fie toate amplasate pe un nod comun, dar că nu au dependinţe unele de altele. În acest scenariu, contrar faţă de cel anterior, lui B i-ar fi permis să rămână activă chiar dacă A sau C (sau ambele) ar fi fost inactive." + +#: Ch-Constraints.xml:488(title) +msgid "Using colocation sets to specify a common peer." +msgstr "Folosirea seturilor de colocare pentru a specifica un nod comun." + +#: Ch-Constraints.xml:506(para) +msgid "Of course there is no limit to the number and size of the sets used. The only thing that matters is that in order for any member of set N to be active, all the members of set N+1 must also be active (and naturally on the same node), and that if a set has sequential=\"true\", then in order for member M to be active, member M+1 must also be active. You can even specify the role in which the members of a set must be in using the set's role attribute." +msgstr "Desigur nu există nici o limită asupra numărului şi mărimii seturilor folosite. Singurul lucru care contează este ca pentru orice membru al setului N să fie activ, toţi membrii setului N+1 trebuie să fie activi de asemenea (şi evident pe acelaşi nod) şi dacă un set are sequential=\"true\", atunci pentru ca membrul M să fie activ, membrul M+1 trebuie să fie activ de asemenea. Puteţi specifica chiar rolul în care membrii unui set trebuie să fie folosind atributele de rol ale setului." + +#: Ch-Constraints.xml:512(title) +msgid "A colocation chain where the members of the middle set have no inter-dependencies and the last has master status." +msgstr "Un lanţ de colocare unde membrii setului mijlociu nu au interdependenţe şi ultimul are statutul de master." + +#: Ch-Constraints.xml:537(title) +msgid "Another Three Resources Sets" +msgstr "Încă Trei Seturi de Resurse" + +#: Ch-Constraints.xml:542(caption) +msgid "Visual representation of a colocation chain where the members of the middle set have no inter-dependencies" +msgstr "Reprezentarea vizuală a unui lanţ de colocare unde membrii setului mijlociu nu au interdependenţe" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ch-Constraints.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ch-Intro.po b/doc/Pacemaker_Explained/ro-RO/Ch-Intro.po new file mode 100644 index 0000000000..7a3cec1c48 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ch-Intro.po @@ -0,0 +1,267 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-25 08:09+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: Ch-Intro.xml:55(None) +msgid "@@image: 'images/pcmk-active-passive.png'; md5=THIS FILE DOESN'T EXIST" +msgstr "@@image: 'images/pcmk-active-passive.png'; md5=ACEST FIŞIER NU EXISTĂ" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: Ch-Intro.xml:66(None) +msgid "@@image: 'images/pcmk-shared-failover.png'; md5=THIS FILE DOESN'T EXIST" +msgstr "@@image: 'images/pcmk-shared-failover.png'; md5=ACEST FIŞIER NU EXISTĂ" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: Ch-Intro.xml:77(None) +msgid "@@image: 'images/pcmk-active-active.png'; md5=THIS FILE DOESN'T EXIST" +msgstr "@@image: 'images/pcmk-active-active.png'; md5=ACEST FIŞIER NU EXISTĂ" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: Ch-Intro.xml:109(None) +msgid "@@image: 'images/pcmk-overview.png'; md5=THIS FILE DOESN'T EXIST" +msgstr "@@image: 'images/pcmk-overview.png'; md5=ACEST FIŞIER NU EXISTĂ" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: Ch-Intro.xml:129(None) +msgid "@@image: 'images/pcmk-stack.png'; md5=THIS FILE DOESN'T EXIST" +msgstr "@@image: 'images/pcmk-stack.png'; md5=ACEST FIŞIER NU EXISTĂ" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +#: Ch-Intro.xml:149(None) +msgid "@@image: 'images/pcmk-internals.png'; md5=THIS FILE DOESN'T EXIST" +msgstr "@@image: 'images/pcmk-internals.png'; md5=ACEST FIŞIER NU EXISTĂ" + +#: Ch-Intro.xml:1(title) +msgid "Read-Me-First" +msgstr "Citeşte-mă-Întâi-pe-Mine" + +#: Ch-Intro.xml:3(title) +msgid "The Scope of this Document" +msgstr "Raza de Acoperire a acestui Document" + +#: Ch-Intro.xml:4(para) +msgid "The purpose of this document is to definitively explain the concepts used to configure Pacemaker. To achieve this best, it will focus exclusively on the XML syntax used to configure the CIB." +msgstr "Scopul acestul document este să explice în mod definitiv conceptele folosite pentru a configura Pacemaker. Pentru a atinge cât mai bine acest lucru, se va concentra exclusiv pe sintaxa XML folosită pentru a configura CIB-ul." + +#: Ch-Intro.xml:11(para) +msgid "It is hoped however, that having understood the concepts explained here, that the functionality of these tools will also be more readily understood." +msgstr "Este de sperat totuşi, ca odată înţelese conceptele explicate aici, ca funcţionalitatea acestor utilitare va fi se asemenea înţeleasă mai bine." + +#: Ch-Intro.xml:8(para) +msgid "For those that are allergic to XML, Pacemaker comes with a cluster shell and a Python based GUI exists, however these tools will not be covered at all in this document , precisely because they hide the XML." +msgstr "Pentru aceia dintre voi care sunt alergici la XML, Pacemaker vine cu un shell de cluster şi un GUI bazat pe Python există, însă aceste utilitare nu vor fi acoperite în vreun fel în acest document , întocmai datorită faptului că acestea ascund XML-ul." + +#: Ch-Intro.xml:15(para) +msgid "Additionally, this document is NOT a step-by-step how-to guide for configuring a specific clustering scenario. Although such guides exist, the purpose of this document is to provide an understanding of the building blocks that can be used to construct any type of Pacemaker cluster." +msgstr "Pe deasupra, acest document NU este un ghid pas-cu-pas pentru configurarea unui scenariu specific de cluster. Deşi astfel de ghiduri există, scopul acestui document este acela de a furniza o înţelegere a elementelor de bază care pot fi folosite pentru a construi orice tip de cluster Pacemaker." + +#: Ch-Intro.xml:21(title) +msgid "What Is Pacemaker?" +msgstr "Ce este Pacemaker?" + +#: Ch-Intro.xml:22(para) +msgid "Pacemaker is a cluster resource manager. It achieves maximum availability for your cluster services (aka. resources) by detecting and recovering from node and resource-level failures by making use of the messaging and membership capabilities provided by your preferred cluster infrastructure (either Corosync or Heartbeat)." +msgstr "Pacemaker este un gestionar de resurse de cluster. Atinge disponibilitatea maximă pentru serviciile voastre de cluster (resursele) prin detectarea şi recuperarea din eşecuri la nivel de nod sau de resursă prin folosirea capabilităţilor de mesagerie şi apartenenţă furnizate de infrastructura de cluster preferată (fie Corosync sau Heartbeat)." + +#: Ch-Intro.xml:26(para) +msgid "Pacemaker's key features include:" +msgstr "Caracteristicile cheie ale Pacemaker includ:" + +#: Ch-Intro.xml:28(para) +msgid "Detection and recovery of node and service-level failures" +msgstr "Detectarea şi recuperarea eşecurilor la nivel de nod şi serviciu" + +#: Ch-Intro.xml:29(para) +msgid "Storage agnostic, no requirement for shared storage" +msgstr "Agnostic d.p.d.v. al stocării, nu sunt cerinţe pentru spaţiu de stocare partajat" + +#: Ch-Intro.xml:30(para) +msgid "Resource agnostic, anything that can be scripted can be clustered" +msgstr "Agnostic d.p.d.v. al resurselor, orice poate fi scriptat poate fi folosit într-un cluster" + +#: Ch-Intro.xml:31(para) +msgid "Supports STONITH for ensuring data integrity" +msgstr "Suportă STONITH pentru asigurarea integrităţii datelor" + +#: Ch-Intro.xml:32(para) +msgid "Supports large and small clusters" +msgstr "Suportă clustere mici şi mari" + +#: Ch-Intro.xml:33(para) +msgid "Supports both quorate and resource driven clusters" +msgstr "Suportă atât quorate cât şi clustere conduse de resurse" + +#: Ch-Intro.xml:34(para) +msgid "Supports practically any redundancy configuration" +msgstr "Suportă practic orice configuraţie redundantă" + +#: Ch-Intro.xml:35(para) +msgid "Automatically replicated configuration that can be updated from any node" +msgstr "Configuraţie replicată în mod automat care poate fi actualizată de pe orice nod" + +#: Ch-Intro.xml:36(para) +msgid "Ability to specify cluster-wide service ordering, colocation and anti-colocation" +msgstr "Abilitatea de a specifica ordonare, colocare şi anti-colocare la nivelul întregului cluster" + +#: Ch-Intro.xml:39(para) +msgid "Clones: for services which need to be active on multiple nodes" +msgstr "Clone: pentru servicii care trebuie să fie active pe mai multe noduri" + +#: Ch-Intro.xml:40(para) +msgid "Multi-state: for services with multiple modes (eg. master/slave, primary/secondary)" +msgstr "Stări-multiple: pentru servicii cu mai multe moduri de operare (ex. master/slave, primar/secundar)" + +#: Ch-Intro.xml:37(para) +msgid "Support for advanced services type " +msgstr "Suport pentru tipuri de servicii avansate " + +#: Ch-Intro.xml:43(para) +msgid "Unified, scriptable, cluster shell" +msgstr "Shell de cluster unificat, scriptabil" + +#: Ch-Intro.xml:47(title) +msgid "Types of Pacemaker Clusters" +msgstr "Tipuri de Clustere Pacemaker" + +#: Ch-Intro.xml:48(para) +msgid "Pacemaker makes no assumptions about your environment, this allows it to support practically any redundancy configuration including Active/Active, Active/Passive, N+1, N+M, N-to-1 and N-to-N." +msgstr "Pacemaker nu face nici un fel de presupuneri despre mediul vostru, acest aspect îi permite să suporte practic orice configuraţie redundantă incluzând Activ/Activ, Activ/Pasiv, N+1, N+M, N-la-1 şi N-la-N." + +#: Ch-Intro.xml:52(title) +msgid "Active/Passive Redundancy" +msgstr "Redundanţă Activă/Pasivă" + +#: Ch-Intro.xml:57(caption) +msgid "Two-node Active/Passive clusters using Pacemaker and DRBD are a cost-effective solution for many High Availability situations." +msgstr "Clusterele Active/Pasive formate din două noduri care folosesc Pacemaker şi DRBD sunt o soluţie eficientă d.p.d.v. al costului pentru multe situaţii de Disponibilitate Crescută." + +#: Ch-Intro.xml:63(title) +msgid "Shared Failover" +msgstr "Failover Partajat" + +#: Ch-Intro.xml:68(caption) +msgid "By supporting many nodes, Pacemaker can dramatically reduce hardware costs by allowing several active/passive clusters to be combined and share a common backup node" +msgstr "Prin suportarea de multe noduri, Pacemaker poate reduce costurile hardware în mod dramatic permiţând mai multor clustere active/pasive să fie combinate şi să împartă un nod comun de backup" + +#: Ch-Intro.xml:74(title) +msgid "N to N Redundancy" +msgstr "Redundanţă N la N" + +#: Ch-Intro.xml:79(caption) +msgid "When shared storage is available, every node can potentially be used for failover. Pacemaker can even run multiple copies of services to spread out the workload." +msgstr "Când un mediu de stocare partajat este disponibil, fiecare nod poate fi folosit în mod potenţial pentru failover. Pacemaker poate chiar rula mai multe copii ale serviciilor pentru a distribui sarcina de lucru." + +#: Ch-Intro.xml:88(title) +msgid "Pacemaker Architecture" +msgstr "Arhitectura Pacemaker" + +#: Ch-Intro.xml:89(para) +msgid "At the highest level, the cluster is made up of three pieces:" +msgstr "La cel mai înalt nivel, clusterul este compus din trei părţi:" + +#: Ch-Intro.xml:91(para) +msgid "Core cluster infrastructure providing messaging and membership functionality (illustrated in red)" +msgstr "Nucleul infrastructurii de cluster care furnizează funcţionalitatea de mesagerie şi apartenenţă (ilustrată cu roşu)" + +#: Ch-Intro.xml:94(para) +msgid "Non-cluster aware components (illustrated in blue). In a Pacemaker cluster, these pieces include not only the scripts that knows how to start, stop and monitor resources, but also a local daemon that masks the differences between the different standards these scripts implement." +msgstr "Componente fără apartenenţă la cluster (ilustrate în albastru). Într-un cluster Pacemaker, aceste părţi includ nu numai scripturile care ştiu să pornească, oprească şi să monitorizeze resurse, dar şi un daemon local care maschează diferenţele între standardele diferite pe care aceste scripturi le implementează." + +#: Ch-Intro.xml:98(para) +msgid "A brain (illustrated in green) that processes and reacts to events from the cluster (nodes leaving or joining) and resources (eg. monitor failures) as well as configuration changes from the administrator. In response to all of these events, Pacemaker will compute the ideal state of the cluster and plot a path to achieve it. This may include moving resources, stopping nodes and even forcing them offline with remote power switches." +msgstr "Un creier (ilustrat cu verde) care procesează şi reacţionează la evenimente din partea clusterului (noduri care pleacă sau se alătură) şi resursele (ex. eşecuri de monitorizare) la fel ca şi schimbări de configuraţie din partea administratorului. Ca răspuns la aceste evenimente, Pacemaker va calcula starea ideală a clusterului şi va cartografia o cale de a atinge ţelul. Acest lucru ar putea include mutarea resurselor, oprirea nodurilor sau chiar oprirea acestora forţat cu switch-uri de curent la distanţă." + +#: Ch-Intro.xml:106(title) +msgid "Conceptual Stack Overview" +msgstr "Vedere Conceptuală a Stivei" + +#: Ch-Intro.xml:111(caption) +msgid "Conceptual overview of the cluster stack" +msgstr "Vederea conceptuală a stivei de cluster" + +#: Ch-Intro.xml:117(para) +msgid "Even though Pacemaker also supports Heartbeat, the filesystems need to use the stack for messaging and membership and Corosync seems to be what they're standardizing on. Technically it would be possible for them to support Heartbeat as well, however there seems little interest in this." +msgstr "Deşi Pacemaker suportă şi Heartbeat, sistemele de fişiere care trebuie să folosească stiva pentru mesagerie şi apartenenţă şi Corosync par să fie ţinta standardizării. Tehnic vorbind ar fi posibil ca acestea să suporte Heartbeat de asemenea, însă există puţin interes pentru acest aspect." + +#: Ch-Intro.xml:115(para) +msgid "When combined with Corosync, Pacemaker also supports popular open source cluster filesystems Due to recent standardization within the cluster filesystem community, they make use of a common distributed lock manager which makes use of Corosync for its messaging capabilities and Pacemaker for its membership (which nodes are up/down) and fencing services." +msgstr "În combinaţie cu Corosync, Pacemaker suportă de asemenea sistemele de fişiere de cluster populare open source Datorită standardizării recente dinăuntrul comunităţii de sisteme de fişiere de cluster, acestea folosesc un manager de blocare distribuit care foloseşte la rândul său Corosync pentru capabilităţile acestuia de mesagerie şi Pacemaker pentru apartenenţă (care noduri sunt funcţionale şi care nu) şi pentru servicii de evacuare." + +#: Ch-Intro.xml:126(title) +msgid "The Pacemaker Stack" +msgstr "Stiva Pacemaker" + +#: Ch-Intro.xml:131(caption) +msgid "The Pacemaker stack when running on Corosync" +msgstr "Stiva Pacemaker atunci când rulează pe Corosync" + +#: Ch-Intro.xml:136(title) +#: Ch-Intro.xml:146(title) +msgid "Internal Components" +msgstr "Componente Interne" + +#: Ch-Intro.xml:137(para) +msgid "Pacemaker itself is composed of four key components (illustrated below in the same color scheme as the previous diagram):" +msgstr "Pacemaker însuşi este compus din patru componente cheie (ilustrate mai jos cu aceeaşi schemă de culori ca şi în diagrama anterioară):" + +#: Ch-Intro.xml:139(para) +msgid "CIB (aka. Cluster Information Base)" +msgstr "CIB (Cluster Information Base)" + +#: Ch-Intro.xml:140(para) +msgid "CRMd (aka. Cluster Resource Management daemon)" +msgstr "CRMd (aka. Cluster Resource Management daemon)" + +#: Ch-Intro.xml:141(para) +msgid "PEngine (aka. PE or Policy Engine)" +msgstr "PEngine (aka. PE sau Policy Engine)" + +#: Ch-Intro.xml:142(para) +msgid "STONITHd" +msgstr "STONITHd" + +#: Ch-Intro.xml:151(caption) +msgid "Subsystems of a Pacemaker cluster running on Corosync" +msgstr "Subsisteme ale unui cluster Pacemaker rulând pe Corosync" + +#: Ch-Intro.xml:155(para) +msgid "The CIB uses XML to represent both the cluster's configuration and current state of all resources in the cluster. The contents of the CIB are automatically kept in sync across the entire cluster and are used by the PEngine to compute the ideal state of the cluster and how it should be achieved." +msgstr "CIB-ul foloseşte XML pentru a reprezenta atât configuraţia clusterului cât şi starea curentă a tuturor resurselor din cluster. Conţinutul CIB-ului este ţinut sincronizat în mod automat pe tot clusterul şi este folosit de către PEngine pentru a calcula starea ideală a clusterului şi de a arăta cum poate fi atinsă." + +#: Ch-Intro.xml:159(para) +msgid "This list of instructions is then fed to the DC (Designated Co-ordinator). Pacemaker centralizes all cluster decision making by electing one of the CRMd instances to act as a master. Should the elected CRMd process, or the node it is on, fail... a new one is quickly established." +msgstr "Lista de instrucţiuni este apoi furnizată către DC (Coordonatorul Desemnat). Pacemaker centralizează toate deciziile clusterului prin alegerea uneia dintre instanţele de CRMd de a se comporta ca master. Dacă procesul ales de CRMd sau nodul pe care acesta există eşuează ... unul nou este stabilit repede." + +#: Ch-Intro.xml:165(para) +msgid "The DC carries out the PEngine's instructions in the required order by passing them to either the LRMd (Local Resource Management daemon) or CRMd peers on other nodes via the cluster messaging infrastructure (which in turn passes them on to their LRMd process)." +msgstr "DC-ul îndeplineşte instrucţiunile PEngine-ului în ordinea necesară prin pasarea acestora fie către LRMd (Local Resource Managemen daemon) fie altor noduri pe care rulează CRMd prin infrastructura de mesagerie a clusterului (care la rândul ei le pasează către procesul lor LRMd)." + +#: Ch-Intro.xml:166(para) +msgid "The peer nodes all report the results of their operations back to the DC and based on the expected and actual results, will either execute any actions that needed to wait for the previous one to complete, or abort processing and ask the PEngine to recalculate the ideal cluster state based on the unexpected results." +msgstr "Nodurile vecine raportează toate rezultatele operaţiunilor înapoi către DC şi pe baza rezultatelor aşteptate şi a rezultatelor actuale, fie va executa acţiuni care necesitau să aştepte ca şi cele anterioare să termine, sau va anula procesarea şi va ruga PEngine-ul să recalculeze starea ideală a clusterului pe baza rezultatelor neaşteptate." + +#: Ch-Intro.xml:167(para) +msgid "In some cases, it may be necessary to power off nodes in order to protect shared data or complete resource recovery. For this Pacemaker comes with STONITHd. STONITH is an acronym for Shoot-The-Other-Node-In-The-Head and is usually implemented with a remote power switch. In Pacemaker, STONITH devices are modeled as resources (and configured in the CIB) to enable them to be easily monitored for failure, however STONITHd takes care of understanding the STONITH topology such that its clients simply request a node be fenced and it does the rest." +msgstr "În anumite cazuri, ar putea fi necesar să oprească alimentarea nodurilor pentru a proteja datele partajate sau pentru a termina recuperarea de resurse. Pentru acest lucru Pacemaker vine cu STONITHd. STONITH este un acronim pentru Shoot-The-Other-Node-In-The-Head (împuşcă celălalt nod în cap) şi este implementat de obicei cu un switch de alimentare cu curent controlat de la distanţă. În Pacemaker, dispozitivele STONITH sunt modelate precum resursele (şi configurate în CIB) pentru a permite monitorizarea facilă a acestora în caz de eşec, totuşi STONITHd se ocupă de înţelegerea topologiei STONITH astfel încât clienţii acestuia să solicite pur şi simplu ca un nod să fie evacuat şi acesta se va ocupa de rest." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ch-Intro.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ch-Nodes.po b/doc/Pacemaker_Explained/ro-RO/Ch-Nodes.po new file mode 100644 index 0000000000..bfe40206c7 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ch-Nodes.po @@ -0,0 +1,227 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-25 09:02+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Ch-Nodes.xml:2(title) +msgid "Cluster Nodes" +msgstr "Nodurile Clusterului" + +#: Ch-Nodes.xml:4(title) +msgid "Defining a Cluster Node" +msgstr "Definirea unui Nod de Cluster" + +#: Ch-Nodes.xml:5(para) +msgid "Each node in the cluster will have an entry in the nodes section containing its UUID, uname and type." +msgstr "Fiecare nod în cluster va avea o intrare în secţiunea de noduri conţinând UUID-ul, uname-ul şi tipul acestuia." + +#: Ch-Nodes.xml:7(title) +msgid "Example cluster node entry" +msgstr "Exemplu de intrare de nod de cluster" + +#: Ch-Nodes.xml:12(para) +msgid "In normal circumstances, the admin should let the cluster populate this information automatically from the communications and membership data. However one can use the crm_uuid tool to read an existing UUID or define a value before the cluster starts." +msgstr "În circumstanţe normale, admin-ul ar trebui să lase clusterul să populeze această informaţie în mod automat din datele de comunicare şi apartenenţă. Totuşi cineva poate folosi utilitarul crm_uuid pentru a citi un UUID existent sau pentru a defini o valoare înainte să pornească clusterul." + +#: Ch-Nodes.xml:18(title) +msgid "Describing a Cluster Node" +msgstr "Descrierea unui Nod de Cluster" + +#: Ch-Nodes.xml:19(para) +msgid "Beyond the basic definition of a node, the administrator can also describe the node's attributes, such as how much RAM, disk, what OS or kernel version it has, perhaps even its physical location. This information can then be used by the cluster when deciding where to place resources. For more information on the use of node attributes, see the section on ." +msgstr "Dincolo de definiţia de bază a unui nod, administratorul poate descrie de asemenea şi atributele nodului, cum ar fi cât de mult RAM, disc are, care OS sau versiune de kernel are, poate chiar şi locaţia fizică. Această informaţie poate fi utilizată mai apoi de către cluster când va decide unde să plaseze resursele. Pentru mai multe informaţii referitoare la folosirea atributelor nodului, vedeţi secţiunea despre ." + +#: Ch-Nodes.xml:24(para) +msgid "Node attributes can be specified ahead of time or populated later, when the cluster is running, using crm_attribute." +msgstr "Atributele nodului pot fi specificate în avans sau populate ulterior, când clusterul rulează, folosind crm_attribute." + +#: Ch-Nodes.xml:25(para) +msgid "Below is what the node's definition would look like if the admin ran the command:" +msgstr "Mai jos este prezentat cum ar arăta definiţia nodului dacă administratorul ar executa comanda:" + +#: Ch-Nodes.xml:27(title) +msgid "The result of using crm_attribute to specify which kernel pcmk-1 is running" +msgstr "Rezultatul folosirii crm_attribute pentru a specifica pe ce kernel rulează pcmk-1" + +#: Ch-Nodes.xml:29(userinput) +#, no-wrap +msgid "crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --attr-value `uname -r` " +msgstr "crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --attr-value `uname -r` " + +#: Ch-Nodes.xml:39(para) +msgid "A simpler way to determine the current value of an attribute is to use crm_attribute command again:" +msgstr "O metodă mai simplă de a determina valoarea curentă a unui atribut este de a folosi comanda crm_attribute din nou:" + +#: Ch-Nodes.xml:40(command) +msgid "crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --get-value" +msgstr "crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --get-value" + +#: Ch-Nodes.xml:42(para) +msgid "By specifying --type nodes the admin tells the cluster that this attribute is persistent. There are also transient attributes which are kept in the status section which are \"forgotten\" whenever the node rejoins the cluster. The cluster uses this area to store a record of how many times a resource has failed on that node but administrators can also read and write to this section by specifying --type status." +msgstr "Prin specificarea --type noduri administratorul îi spune clusterului că acest atribut este persistent. Există de asemenea atribute tranzitive care sunt păstrate în secţiunea de status şi care sunt \"uitate\" oricând nodul se realătură clusterului. Clusterul foloseşte această zonă pentru a stoca o înregistrare despre de câte ori a eşuat o resursă pe acel nod însâ administratorii pot citi şi scrie în această secţiune prin specificarea a --type status." + +#: Ch-Nodes.xml:49(title) +msgid "Adding a New Cluster Node" +msgstr "Adăugarea unui Nou Nod în Cluster" + +#: Ch-Nodes.xml:51(title) +#: Ch-Nodes.xml:65(title) +#: Ch-Nodes.xml:107(title) +msgid "Corosync" +msgstr "Corosync" + +#: Ch-Nodes.xml:52(para) +msgid "Adding a new node is as simple as installing Corosync and Pacemaker, and copying /etc/corosync/corosync.conf and /etc/ais/authkey (if it exists) from an existing node. You may need to modify the mcastaddr option to match the new node's IP address." +msgstr "Adăugarea unui nou nod este la fel de simplă ca instalarea Corosync şi Pacemaker şi copierea /etc/corosync/corosync.conf şi a /etc/ais/authkey (dacă există) de pe un nod existent. Ar putea fi necesar să modificaţi opţiunea mcastaddr pentru a se potrivi cu adresa IP a noului nod." + +#: Ch-Nodes.xml:54(para) +#: Ch-Nodes.xml:116(para) +msgid "If a log message containing \"Invalid digest\" appears from Corosync, the keys are not consistent between the machines." +msgstr "Dacă apare în log-uri un mesaj de la Corosync conţinând \"Invalid digest\", cheile nu sunt consistente între maşini." + +#: Ch-Nodes.xml:57(title) +#: Ch-Nodes.xml:92(title) +#: Ch-Nodes.xml:119(title) +msgid "Heartbeat" +msgstr "Heartbeat" + +#: Ch-Nodes.xml:58(para) +msgid "Provided you specified autojoin any in ha.cf, adding a new node is as simple as installing heartbeat and copying ha.cf and authkeys from an existing node." +msgstr "Dacă aţi specificat autojoin any în ha.cf, adăugarea unui nod nou este la fel de simpla ca şi instalarea Heartbeat şi copierea ha.cf şi a authkeys de pe un nod existent." + +#: Ch-Nodes.xml:59(para) +msgid "If not, then after setting up ha.cf and authkeys, you must use the hb_addnode command before starting the new node." +msgstr "În caz contrar, după setarea ha.cf şi a authkeys, trebuie să folosiţi comanda hb_addnode înainte de a porni noul nod." + +#: Ch-Nodes.xml:63(title) +msgid "Removing a Cluster Node" +msgstr "Înlăturarea unui Nod din Cluster" + +#: Ch-Nodes.xml:66(para) +msgid "Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a reliable solution. First one must arrange for heartbeat to forget about the node (pcmk-1 in the example below)." +msgstr "Datorită faptului că straturile de mesagerie şi apartenenţă sunt surse autoritative pentru nodurile clusterului, ştergerea acestoa din CIB nu este o soluţie de încredere. Întâi cineva trebuie să facă astfel încât heartbeat să uite de nod (pcmk-1 în exemplul de mai jos)." + +#: Ch-Nodes.xml:70(para) +msgid "On the host to be removed:" +msgstr "Pe gazda care va fi înlăturată:" + +#: Ch-Nodes.xml:73(para) +msgid "Find and record the node's Corosync id: crm_node -i" +msgstr "Găsiţi şi înregistraţi id-ul Corosync al nodului: crm_node -i" + +#: Ch-Nodes.xml:76(para) +msgid "Stop the cluster: /etc/init.d/corosync stop" +msgstr "Opriţi clusterul: /etc/init.d/corosync stop" + +#: Ch-Nodes.xml:79(para) +msgid "Next, from one of the remaining active cluster nodes:" +msgstr "Ulterior, de pe unul din nodurile rămase active ale clusterului:" + +#: Ch-Nodes.xml:82(para) +msgid "Tell the cluster to forget about the removed host: crm_node -R COROSYNC_ID" +msgstr "Comunicaţi clusterului să uite despre gazda înlăturată: crm_node -R COROSYNC_ID" + +#: Ch-Nodes.xml:85(para) +msgid "Only now is it safe to delete the node from the CIB with:" +msgstr "Doar acum este în siguranţă să ştergeţi nodul din CIB cu:" + +#: Ch-Nodes.xml:86(replaceable) +#: Ch-Nodes.xml:87(replaceable) +msgid "pcmk-1" +msgstr "pcmk-1" + +#: Ch-Nodes.xml:86(command) +msgid "cibadmin --delete --obj_type nodes --crm_xml '<node uname=\"\"/>'" +msgstr "cibadmin --delete --obj_type nodes --crm_xml '<node uname=\"\"/>'" + +#: Ch-Nodes.xml:87(command) +msgid "cibadmin --delete --obj_type status --crm_xml '<node_state uname=\"\"/>'" +msgstr "cibadmin --delete --obj_type status --crm_xml '<node_state uname=\"\"/>'" + +#: Ch-Nodes.xml:93(para) +msgid "Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a reliable solution. First one must arrange for heartbeat to forget about the node (pcmk-1 in the example below). To do this, shut down heartbeat on the node and then, from one of the remaining active cluster nodes, run:" +msgstr "Datorită faptului că straturile de mesagerie şi apartenenţă sunt surse autoritative pentru nodurile clusterului, ştergerea acestoa din CIB nu este o soluţie de încredere. Întâi cineva trebuie să facă astfel încât heartbeat să uite de nod (pcmk-1 în exemplul de mai jos). Pentru a realiza acest lucru, opriţi heartbeat pe nod şi apoi, de pe unul din nodurile rămase active în cluster, rulaţi:" + +#: Ch-Nodes.xml:98(command) +msgid "hb_delnode pcmk-1" +msgstr "hb_delnode pcmk-1" + +#: Ch-Nodes.xml:99(para) +msgid "Only then is it safe to delete the node from the CIB with:" +msgstr "Doar acum este în siguranţă să ştergeţi nodul din CIB cu:" + +#: Ch-Nodes.xml:100(command) +msgid "cibadmin --delete --obj_type nodes --crm_xml '<node uname=\"pcmk-1\"/>'" +msgstr "cibadmin --delete --obj_type nodes --crm_xml '<node uname=\"pcmk-1\"/>'" + +#: Ch-Nodes.xml:101(command) +msgid "cibadmin --delete --obj_type status --crm_xml '<node_state uname=\"pcmk-1\"/>'" +msgstr "cibadmin --delete --obj_type status --crm_xml '<node_state uname=\"pcmk-1\"/>'" + +#: Ch-Nodes.xml:105(title) +msgid "Replacing a Cluster Node" +msgstr "Înlocuirea unui Nod din Cluster" + +#: Ch-Nodes.xml:108(para) +msgid "The five-step guide to replacing an existing cluster node:" +msgstr "Ghidul în cinci paşi pentru înlocuirea unui nod existent din cluster:" + +#: Ch-Nodes.xml:110(para) +#: Ch-Nodes.xml:122(para) +msgid "Make sure the old node is completely stopped" +msgstr "Asiguraţi-vă că nodul vechi este oprit de tot." + +#: Ch-Nodes.xml:111(para) +msgid "Give the new machine the same hostname and IP address as the old one" +msgstr "Daţi maşinii noi acelaşi hostname şi adresă IP ca celei vechi" + +#: Ch-Nodes.xml:112(para) +msgid "Install the cluster software :-)" +msgstr "Instalaţi soft-ul de cluster :-)" + +#: Ch-Nodes.xml:113(para) +msgid "Copy /etc/corosync/corosync.conf and /etc/ais/authkey (if it exists) to the new node" +msgstr "Copiaţi /etc/corosync/corosync.conf şi /etc/ais/authkey (dacă există) pe nodul nou" + +#: Ch-Nodes.xml:114(para) +#: Ch-Nodes.xml:128(para) +msgid "Start the new cluster node" +msgstr "Porniţi noul nod în cluster" + +#: Ch-Nodes.xml:120(para) +msgid "The seven-step guide to replacing an existing cluster node:" +msgstr "Ghidul în şapte paşi pentru înlocuirea unui nod existent din cluster" + +#: Ch-Nodes.xml:123(para) +msgid "Give the new machine the same hostname as the old one" +msgstr "Daţi maşinii noi acelaşi hostname ca şi celei vechi" + +#: Ch-Nodes.xml:124(para) +msgid "Go to an active cluster node and look up the UUID for the old node in /var/lib/heartbeat/hostcache" +msgstr "Mergeţi pe un nod activ din cluster şi căutaţi UUID-ul nodului vechi în /var/lib/heartbeat/hostcache" + +#: Ch-Nodes.xml:125(para) +msgid "Install the cluster software" +msgstr "Instalaţi soft-ul de cluster" + +#: Ch-Nodes.xml:126(para) +msgid "Copy ha.cf and authkeys to the new node" +msgstr "Copiaţi ha.cf şi authkeys pe nodul nou" + +#: Ch-Nodes.xml:127(para) +msgid "On the new node, populate it's UUID using crm_uuid -w and the UUID from step 2" +msgstr "Pe nodul nou, populaţi UUID-ul acestuia folosind crm_uuid -w şi UUID-ul prelevat de la pasul 2" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ch-Nodes.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ch-Options.po b/doc/Pacemaker_Explained/ro-RO/Ch-Options.po new file mode 100644 index 0000000000..f18e4102c4 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ch-Options.po @@ -0,0 +1,444 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-25 15:18+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Ch-Options.xml:2(title) +#: Ch-Options.xml:118(title) +#: Ch-Options.xml:126(title) +msgid "Cluster Options" +msgstr "Opţiunile Clusterului" + +#: Ch-Options.xml:4(title) +msgid "Special Options" +msgstr "Opţiuni Speciale" + +#: Ch-Options.xml:5(para) +msgid "The reason for these fields to be placed at the top level instead of with the rest of cluster options is simply a matter of parsing. These options are used by the configuration database which is, by design, mostly ignorant of the content it holds. So the decision was made to place them in an easy to find location." +msgstr "Motivul pentru care aceste câmpuri să fie plasate la nivelul cel mai înalt în loc să fie cu restul opţiunilor clusterului este pur şi simplu legat de parsare. Aceste opţiuni sunt folosite de către baza de date cu configuraţii care este, prin design, în principal ignorantă faţă de conţinutul pe care îl deţine. Aşa că decizia a fost luată de a le plasa într-o locaţie uşor de găsit." + +#: Ch-Options.xml:11(title) +msgid "Configuration Version" +msgstr "Versiunea Configuraţiei" + +#: Ch-Options.xml:12(para) +msgid "When a node joins the cluster, the cluster will perform a check to see who has the best configuration based on the fields below. It then asks the node with the highest (admin_epoch, epoch, num_updates) tuple to replace the configuration on all the nodes - which makes setting them and setting them correctly very important." +msgstr "Când un nod aderă la cluster, clusterul va efectua o verificare pentru a vedea cine are cea mai bună configuraţie bazată pe câmpurile de mai jos. Apoi întreabă nodul cu cea mai mare tuplă (admin_epoch, epoch, num_updates) să înlocuiască, configuraţia pe toate nodurile - fapt care face setarea acestora şi setarea lor corectă foarte important." + +#: Ch-Options.xml:17(title) +msgid "Configuration Version Properties" +msgstr "Proprietăţi ale Versiunii Configuraţiei" + +#: Ch-Options.xml:22(entry) +#: Ch-Options.xml:53(entry) +#: Ch-Options.xml:76(entry) +msgid "Field" +msgstr "Câmp" + +#: Ch-Options.xml:23(entry) +#: Ch-Options.xml:54(entry) +#: Ch-Options.xml:77(entry) +#: Ch-Options.xml:132(entry) +msgid "Description" +msgstr "Descriere" + +#: Ch-Options.xml:28(entry) +msgid "admin_epoch" +msgstr "admin_epoch" + +#: Ch-Options.xml:30(para) +msgid "Never modified by the cluster. Use this to make the configurations on any inactive nodes obsolete." +msgstr "Niciodată modificat de către cluster. Folosiţi acesta pentru a face configuraţiile pe nodurile inactive să fie învechite." + +#: Ch-Options.xml:31(para) +msgid "Never set this value to zero, in such cases the cluster cannot tell the difference between your configuration and the \"empty\" one used when nothing is found on disk." +msgstr "Nu setaţi niciodată această valoare la zero, în astfel de cazuri clusterul nu poate face diferenţa între configuraţia voastră şi cea \"goală\" folosită atunci când nu este găsit nimic pe disc." + +#: Ch-Options.xml:35(entry) +msgid "epoch" +msgstr "epoch" + +#: Ch-Options.xml:36(entry) +msgid "Incremented every time the configuration is updated (usually by the admin)" +msgstr "Incrementată de fiecare dată când configuraţia este actualizată (de obicei de către administrator)" + +#: Ch-Options.xml:39(entry) +msgid "num_updates" +msgstr "num_updates" + +#: Ch-Options.xml:40(entry) +msgid "Incremented every time the configuration or status is updated (usually by the cluster)" +msgstr "Incrementată de fiecare dată când configuraţia sau status-ul este actualizat (de obicei de către cluster)" + +#: Ch-Options.xml:47(title) +msgid "Other Fields" +msgstr "Alte Câmpuri" + +#: Ch-Options.xml:49(title) +msgid "Properties Controling Validation" +msgstr "Proprietăţi care Controlează Validarea" + +#: Ch-Options.xml:59(entry) +msgid "validate-with" +msgstr "validate-with" + +#: Ch-Options.xml:60(entry) +msgid "Determines the type of validation being done on the configuration. If set to \"none\", the cluster will not verify that updates conform the the DTD (nor reject ones that don't). This option can be useful when operating a mixed version cluster during an upgrade." +msgstr "Determină tipul de validare care este realizat pe configuraţie. Dacă este setat la \"none\", clusterul nu va verifica dacă actualizările sunt conforme cu DTD (nici nu le va respinge pe cele care nu sunt). Această opţiune poate fi utilă când lucraţi cu o versiune combinată a clusterului în timpul unei actualizări." + +#: Ch-Options.xml:70(title) +msgid "Fields Maintained by the Cluster" +msgstr "Câmpuri Menţinute de către Cluster" + +#: Ch-Options.xml:72(title) +msgid "Properties Maintained by the Cluster" +msgstr "Proprietăţi Menţinute de către Cluster" + +#: Ch-Options.xml:82(entry) +msgid "crm-debug-origin" +msgstr "crm-debug-origin" + +#: Ch-Options.xml:83(entry) +msgid "Indicates where the last update came from. Informational purposes only." +msgstr "Indică de unde a provenit ultima actualizare. Numai cu scop informaţional." + +#: Ch-Options.xml:86(entry) +msgid "cib-last-written" +msgstr "cib-last-written" + +#: Ch-Options.xml:87(entry) +msgid "Indicates when the configuration was last written to disk. Informational purposes only." +msgstr "Indică momentul când configuraţia a fost scrisă ultima oară pe disc. Numai cu scop informaţional." + +#: Ch-Options.xml:90(entry) +msgid "dc-uuid" +msgstr "dc-uuid" + +#: Ch-Options.xml:91(entry) +msgid "Indicates which cluster node is the current leader. Used by the cluster when placing resources and determining the order of some events." +msgstr "Arată care dintre nodurile clusterului este conducătorul curent. Folosit de către cluster când plasează resurse şi determină ordinea anumitor evenimente." + +#: Ch-Options.xml:94(entry) +msgid "have-quorum" +msgstr "have-quorum" + +#: Ch-Options.xml:95(entry) +msgid "Indicates if the cluster has quorum. If false, this may mean that the cluster cannot start resources or fence other nodes. See no-quorum-policy below." +msgstr "Indică dacă clusterul are quorum. Dacă este fals, acest lucru ar putea însemna că, clusterul nu poate porni resurse sau evacua alte noduri. Vedeţi no-quorum-policy mai jos." + +#: Ch-Options.xml:100(para) +msgid "Note that although these fields can be written to by the admin, in most cases the cluster will overwrite any values specified by the admin with the \"correct\" ones. To change the admin_epoch, for example, one would use:" +msgstr "Luaţi aminte că deşi aceste câmpuri pot fi scrise de către administrator, în majoritatea cazurilor clusterul va suprascrie orice valoare specificată de către administrator cu cele \"corecte\". Pentru a schimba admin_epoch de exemplu, cineva ar putea folosi:" + +#: Ch-Options.xml:104(command) +msgid "cibadmin --modify --crm_xml ‘<cib admin_epoch=\"42\"/>'" +msgstr "cibadmin --modify --crm_xml ‘<cib admin_epoch=\"42\"/>'" + +#: Ch-Options.xml:105(para) +msgid "A complete set of fields will look something like this:" +msgstr "Un set complet de câmpuri ar arăta ceva de genul acesta:" + +#: Ch-Options.xml:107(title) +msgid "An example of the fields set for a cib object" +msgstr "Un exemplu al câmpurilor setate pentru un obiect CIB" + +#: Ch-Options.xml:119(para) +msgid "Cluster options, as you'd expect, control how the cluster behaves when confronted with certain situations." +msgstr "Opţiunile clusterului, aşa cum v-aţi aştepta, controlează cum se comportă clusterul când se confruntă cu anumite situaţii." + +#: Ch-Options.xml:121(para) +msgid "This will be described later in the section on where we will show how to have the cluster use different sets of options during working hours (when downtime is usually to be avoided at all costs) than it does during the weekends (when resources can be moved to the their preferred hosts without bothering end users)" +msgstr "Acest aspect va fi descris mai târziu în secţiunea despre unde vă vom arăta cum să punem clusterul să folosească diferite seturi de opţiuni în timpul orelor de lucru (când nefuncţionarea este de evitat cu orice preţ) faţă de cele folosite în timpul weekend-urilor (când resursele pot fi mutate pe gazdele preferate fără să deranjeze utilizatorii finali)" + +#: Ch-Options.xml:120(para) +msgid "They are grouped into sets and, in advanced configurations, there may be more than one. For now we will describe the simple case where each option is present at most once." +msgstr "Sunt grupate în seturi şi, în configuraţii avansate, ar putea fi mai mult de una. Momentan vom descrie cazul simplu în care fiecare opţiune este prezentă cel mult o dată." + +#: Ch-Options.xml:124(title) +msgid "Available Cluster Options" +msgstr "Opţiuni Disponibile ale Clusterului" + +#: Ch-Options.xml:130(entry) +msgid "Option" +msgstr "Opţiune" + +#: Ch-Options.xml:131(entry) +msgid "Default" +msgstr "Valoare implicită" + +#: Ch-Options.xml:137(entry) +msgid "batch-limit" +msgstr "batch-limit" + +#: Ch-Options.xml:138(entry) +msgid "30" +msgstr "30" + +#: Ch-Options.xml:139(entry) +msgid "The number of jobs that the TE is allowed to execute in parallel. The \"correct\" value will depend on the speed and load of your network and cluster nodes." +msgstr "Numărul de sarcini pe care TE-ul este permis să le execute în paralel. Valoarea \"corectă\" va depinde de viteza şi de încărcarea reţelei şi a nodurilor voastre din cluster." + +#: Ch-Options.xml:142(entry) +msgid "no-quorum-policy" +msgstr "no-quorum-policy" + +#: Ch-Options.xml:143(entry) +msgid "stop" +msgstr "stop" + +#: Ch-Options.xml:148(para) +msgid "ignore - continue all resource management" +msgstr "ignore - continuă toată gestionarea resurselor" + +#: Ch-Options.xml:149(para) +msgid "freeze - continue resource management, but don't recover resources from nodes not in the affected partition" +msgstr "freeze - continuă gestionarea resurselor, dar nu recupera resurse de pe noduri care nu sunt în partiţia afectată" + +#: Ch-Options.xml:150(para) +msgid "stop - stop all resources in the affected cluster parition" +msgstr "stop - opreşte toate resursele în partiţia de cluster afectată" + +#: Ch-Options.xml:151(para) +msgid "suicide - fence all nodes in the affected cluster partition" +msgstr "suicide - evacuează toate nodurile din partiţia de cluster afectată" + +#: Ch-Options.xml:144(entry) +msgid "What to do when the cluster does not have quorum. Allowed values: " +msgstr "Ce este de făcut atunci când clusterul nu are quorum. Valori permise: " + +#: Ch-Options.xml:156(entry) +msgid "symmetric-cluster" +msgstr "symmetric-cluster" + +#: Ch-Options.xml:157(entry) +#: Ch-Options.xml:162(entry) +#: Ch-Options.xml:180(entry) +#: Ch-Options.xml:185(entry) +#: Ch-Options.xml:190(entry) +msgid "TRUE" +msgstr "TRUE" + +#: Ch-Options.xml:158(entry) +msgid "Can all resources run on any node by default?" +msgstr "Pot rula toate resursele pe orice nod în mod implicit?" + +#: Ch-Options.xml:161(entry) +msgid "stonith-enabled" +msgstr "stonith-enabled" + +#: Ch-Options.xml:164(para) +msgid "Should failed nodes and nodes with resources that can't be stopped be shot? If you value your data, set up a STONITH device and enable this." +msgstr "Ar trebui nodurile care au eşuat şi nodurile cu resurse care nu pot fi oprite să fie împuşcate? Dacă ţineţi la datele voastre, setaţi un dispozitiv STONITH şi activaţi această opţiune." + +#: Ch-Options.xml:165(para) +msgid "If true, or unset, the cluster will refuse to start resources unless one or more STONITH resources have been configured also." +msgstr "Dacă este adevărat, sau nu este setată, clusterul va refuza să pornească resurse decât dacă unul sau mai multe dispozitive STONITH au fost configurate de asemenea." + +#: Ch-Options.xml:169(entry) +msgid "stonith-action" +msgstr "stonith-action" + +#: Ch-Options.xml:170(entry) +msgid "reboot" +msgstr "reboot" + +#: Ch-Options.xml:171(entry) +msgid "Action to send to STONITH device. Allowed values: reboot, poweroff." +msgstr "Acţiunea care să fie trimisă către dispozitivul STONITH. Valori permise: reboot, poweroff." + +#: Ch-Options.xml:174(entry) +msgid "cluster-delay" +msgstr "cluster-delay" + +#: Ch-Options.xml:175(entry) +msgid "60s" +msgstr "60s" + +#: Ch-Options.xml:176(entry) +msgid "Round trip delay over the network (excluding action execution). The \"correct\" value will depend on the speed and load of your network and cluster nodes." +msgstr "Întârzierea dus-întors experimentată pe reţea (excluzând timpul necesar executării acţiunii). Valoarea \"corectă\" va depinde de viteza şi de nivelul de încărcare al reţelei şi al nodurilor voastre din cluster." + +#: Ch-Options.xml:179(entry) +msgid "stop-orphan-resources" +msgstr "stop-orphan-resources" + +#: Ch-Options.xml:181(entry) +msgid "Should deleted resources be stopped" +msgstr "Ar trebui să fie oprite resursele şterse" + +#: Ch-Options.xml:184(entry) +msgid "stop-orphan-actions" +msgstr "stop-orphan-actions" + +#: Ch-Options.xml:186(entry) +msgid "Should deleted actions be cancelled" +msgstr "Ar trebui anulate acţiunile şterse" + +#: Ch-Options.xml:189(entry) +msgid "start-failure-is-fatal" +msgstr "start-failure-is-fatal" + +#: Ch-Options.xml:191(entry) +msgid "When set to FALSE, the cluster will instead use the resource's failcount and value for resource-failure-stickiness" +msgstr "Când este setat pe FALSE, clusterul va folosi în schimb failcount-ul şi valoarea resursei pentru resource-failure-stickiness" + +#: Ch-Options.xml:194(entry) +msgid "pe-error-series-max" +msgstr "pe-error-series-max" + +#: Ch-Options.xml:195(entry) +#: Ch-Options.xml:200(entry) +#: Ch-Options.xml:205(entry) +msgid "-1 (all)" +msgstr "-1 (all)" + +#: Ch-Options.xml:196(entry) +msgid "The number of PE inputs resulting in ERRORs to save. Used when reporting problems." +msgstr "Numărul de intrări PE care rezultă în ERROR(i) de a salva. Folosite când se raporteazâ probleme." + +#: Ch-Options.xml:199(entry) +msgid "pe-warn-series-max" +msgstr "pe-warn-series-max" + +#: Ch-Options.xml:201(entry) +msgid "The number of PE inputs resulting in WARNINGs to save. Used when reporting problems." +msgstr "Numărul de intrări PE care rezultă în WARNING-uri de a salva. Folosite când se raportează probleme." + +#: Ch-Options.xml:204(entry) +msgid "pe-input-series-max" +msgstr "pe-input-series-max" + +#: Ch-Options.xml:206(entry) +msgid "The number of \"normal\" PE inputs to save. Used when reporting problems." +msgstr "Numărul de intrări PE \"normale\" care să fie salvate. Folosite când se raportează probleme." + +#: Ch-Options.xml:211(para) +msgid "You can always obtain an up-to-date list of cluster options, including their default values by running the pengine metadata command." +msgstr "Puteţi întotdeauna să obţineţi o listă actualizată a opţiunilor clusterului, incluzând valorile implicite ale acestora prin rularea comenzii pengine de metadata." + +#: Ch-Options.xml:214(title) +msgid "Querying and Setting Cluster Options" +msgstr "Interogând şi Setând Opţiunile Clusterului" + +#: Ch-Options.xml:215(para) +msgid "Cluster options can be queried and modified using the crm_attribute tool. To get the current value of cluster-delay, simply use:" +msgstr "Opţiunile clusterului pot fi interogate şi modificate folosind utilitarul crm_attribute. Pentru a obţine valoarea curentă a cluster-delay, pur şi simplu folosiţi:" + +#: Ch-Options.xml:219(command) +msgid "crm_attribute --attr-name cluster-delay --get-value" +msgstr "crm_attribute --attr-name cluster-delay --get-value" + +#: Ch-Options.xml:220(para) +msgid "which is more simply written as" +msgstr "care este scrisă mai simplu ca" + +#: Ch-Options.xml:221(command) +msgid "crm_attribute --get-value -n cluster-delay" +msgstr "crm_attribute --get-value -n cluster-delay" + +#: Ch-Options.xml:222(para) +msgid "If a value is found, the you'll see a result such as this" +msgstr "Dacă o valoare este găsită, atunci veţi vedea un rezultat ca acesta" + +#: Ch-Options.xml:224(command) +msgid "# crm_attribute --get-value -n cluster-delay" +msgstr "# crm_attribute --get-value -n cluster-delay" + +#: Ch-Options.xml:223(screen) +#, no-wrap +msgid "" +"\n" +" \n" +" name=cluster-delay value=60s" +msgstr "" +"\n" +" \n" +" name=cluster-delay value=60s" + +#: Ch-Options.xml:226(para) +msgid "However if no value is found, the tool will display an error:" +msgstr "Însă dacă nici o valoare nu este găsită, utilitarul va arăta o eroare:" + +#: Ch-Options.xml:228(command) +msgid "# crm_attribute --get-value -n clusta-deway" +msgstr "# crm_attribute --get-value -n clusta-deway" + +#: Ch-Options.xml:227(screen) +#, no-wrap +msgid "" +"\n" +" \n" +" name=clusta-deway value=(null)\n" +" Error performing operation: The object/attribute does not exist" +msgstr "" +"\n" +" \n" +" name=clusta-deway value=(null)\n" +" Error performing operation: The object/attribute does not exist" + +#: Ch-Options.xml:231(para) +msgid "To use a different value, eg. 30s, simply run:" +msgstr "Pentru a folosi o altă valoare, ex. 30s, pur şi simplu rulaţi:" + +#: Ch-Options.xml:232(command) +msgid "crm_attribute --attr-name cluster-delay --attr-value 30s" +msgstr "crm_attribute --attr-name cluster-delay --attr-value 30s" + +#: Ch-Options.xml:233(para) +msgid "To go back to the cluster's default value, you can then delete the value with:" +msgstr "Pentru a reveni la valoarea implicită a clusterului, puteţi ştergeţi ulterior valoarea cu: " + +#: Ch-Options.xml:234(command) +msgid "crm_attribute --attr-name cluster-delay --delete-attr" +msgstr "crm_attribute --attr-name cluster-delay --delete-attr" + +#: Ch-Options.xml:237(title) +msgid "When Options are Listed More Than Once" +msgstr "Când Opţiunile sunt Listate Mai Mult De O Dată" + +#: Ch-Options.xml:238(para) +msgid "If you ever see something like the following, it means that the option you're modifying is present more than once." +msgstr "Dacă vedeţi vreodată ceva precum următoarele, înseamnă că opţiunea pe care o modificaţi este prezentă mai mult de o dată." + +#: Ch-Options.xml:240(title) +msgid "Deleting an option that is listed twice" +msgstr "Ştergerea unei opţiuni care este listată de două ori" + +#: Ch-Options.xml:242(command) +msgid "# crm_attribute --attr-name batch-limit --delete-attr" +msgstr "# crm_attribute --attr-name batch-limit --delete-attr" + +#: Ch-Options.xml:241(screen) +#, no-wrap +msgid "" +"\n" +" \n" +" Multiple attributes match name=batch-limit in crm_config:\n" +" Value: 50 (set=cib-bootstrap-options, id=cib-bootstrap-options-batch-limit)\n" +" Value: 100 (set=custom, id=custom-batch-limit)\n" +" Please choose from one of the matches above and supply the 'id' with --attr-id" +msgstr "" +"\n" +" \n" +" Multiple attributes match name=batch-limit in crm_config:\n" +" Value: 50 (set=cib-bootstrap-options, id=cib-bootstrap-options-batch-limit)\n" +" Value: 100 (set=custom, id=custom-batch-limit)\n" +" Please choose from one of the matches above and supply the 'id' with --attr-id" + +#: Ch-Options.xml:248(para) +msgid "In such cases follow the on-screen instructions to perform the requested action. To determine which value is currently being used by the cluster, please refer to the the section on ." +msgstr "În astfel de cazuri urmaţi instrucţiunile de pe ecran pentru a efectua acţiunea cerută. Pentru a determina care valoare este folosită în mod curent de către cluster, vă rugăm să faceţi referinţă la secţiunea despre ." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ch-Options.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ch-Resources.po b/doc/Pacemaker_Explained/ro-RO/Ch-Resources.po new file mode 100644 index 0000000000..d88ab4f12d --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ch-Resources.po @@ -0,0 +1,632 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-29 22:35+0100\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Ch-Resources.xml:2(title) +msgid "Cluster Resources" +msgstr "Resursele Clusterului" + +#: Ch-Resources.xml:4(title) +msgid "What is a Cluster Resource" +msgstr "Ce este o Resursă de Cluster" + +#: Ch-Resources.xml:5(para) +msgid "The role of a resource agent is to abstract the service it provides and present a consistent view to the cluster, which allows the cluster to be agnostic about the resources it manages. The cluster doesn't need to understand how the resource works because it relies on the resource agent to do the right thing when given a start, stop or monitor command." +msgstr "Rolul agentului de resursă este de a abstractiza serviciul pe care îl furnizează şi de a prezenta o viziune consistentă clusterului, care îi permite clusterului să fie agnostic cu resursele pe care le gestionează. Clusterul nu trebuie să înţeleagă cum funcţionează resursa pentru că se bazează pe agentul de resursă să efectueze ceea ce trebuie atunci când îi este trimisă o comandă de start, stop sau monitor." + +#: Ch-Resources.xml:9(para) +msgid "For this reason it is crucial that resource agents are well tested." +msgstr "Din acest motiv este imperativ ca agenţii de resursă să fie testaţi corespunzător." + +#: Ch-Resources.xml:10(para) +msgid "Typically resource agents come in the form of shell scripts, however they can be written using any technology (such as C, Python or Perl) that the author is comfortable with." +msgstr "În mod normal agenţii de resursă vin sub forma de scripturi de shell, însă aceştia pot fi scrişi folosind orice limbaj de programare (cum ar fi C, Python sau Perl) cu care este confortabil autorul." + +#: Ch-Resources.xml:13(title) +msgid "Supported Resource Classes" +msgstr "Clase de Resurse Suportate" + +#: Ch-Resources.xml:14(para) +msgid "There are three basic classes of agents supported by Pacemaker. In order of encouraged usage they are:" +msgstr "Există trei clase de bază de agenţi suportate de Pacemaker. În ordinea în care este încurajată folosirea acestora ele sunt:" + +#: Ch-Resources.xml:19(title) +msgid "Open Cluster Framework" +msgstr "Open Cluster Framework" + +#: Ch-Resources.xml:21(para) +msgid "Note: The Pacemaker implementation has been somewhat extended from the OCF Specs, but none of those changes are incompatible with the original OCF specification" +msgstr "Notă: Implementarea Pacemaker a fost oarecum extinsă din Specificaţiile OCF, dar nici una dintre modificările acelea sunt incompatibile cu specificaţia OCF originală." + +#: Ch-Resources.xml:20(para) +msgid "The OCF Spec (as it relates to resource agents) can be found at: and is basically an extension of the Linux Standard Base conventions for init scripts to" +msgstr "Specificaţia OCF (în conjunctura agenţilor de resursă) poate fi găsită la: şi este în linii mari o extensie a convenţiilor stabilite de Linux Standard Base pentru scripturi de init ca să" + +#: Ch-Resources.xml:23(para) +msgid "support parameters" +msgstr "suporte parametri" + +#: Ch-Resources.xml:24(para) +msgid "make them self describing, and" +msgstr "să îi facă auto descriptivi şi" + +#: Ch-Resources.xml:25(para) +msgid "extensible" +msgstr "extensibili" + +#: Ch-Resources.xml:30(para) +msgid "Included with the cluster is the ocf-tester script which can be useful in this regard." +msgstr "Inclus cu clusterul este scriptul ocf-tester care poate fi folositor în această privinţă." + +#: Ch-Resources.xml:27(para) +msgid "OCF specs have strict definitions of what exit codes actions must return The cluster follows these specifications exactly, and exiting with the wrong exit code will cause the cluster to behave in ways you will likely find puzzling and annoying. In particular, the cluster needs to distinguish a completely stopped resource from one which is in some erroneous and indeterminate state." +msgstr "Specificaţiile OCF au definiţii stricte asupra căror coduri de ieşire trebuie să returneze acţiunile Clusterul urmează aceste specificaţii întocmai, iar ieşirea din execuţie cu codul de eroare greşit va cauza clusterul să se comporte în feluri pe care le puteţi găsi enervante şi lipsite de sens. În mod special, clusterul trebuie să poată distinge între o resursă oprită complet şi una care se află într-o stare eronată sau nedeterminată." + +#: Ch-Resources.xml:35(para) +msgid "Parameters are passed to the script as environment variables, with the special prefix OCF_RESKEY_. So, if you need to be given a parameter which the user thinks of as ip it will be passed to the script as OCF_RESKEY_ip. The number and purpose of the parameters is completely arbitrary, however your script should advertise any that it supports using the meta-data command." +msgstr "Parametrii sunt pasaţi scriptului ca variabile de mediu, cu prefixul special OCF_RESKEY_. Deci, dacă trebuie să vi se dea un parametru pe care utilizatorul îl consideră ca fiind ip, acesta va fi pasat către script ca OCF_RESKEY_ip. Numărul şi scopul parametrilor este complet arbitrar, însă scriptul vostru ar trebui să îi anunţe pe toţi pe care îi suportă folosind comanda meta-data." + +#: Ch-Resources.xml:40(para) +msgid "For more information, see and ." +msgstr "Pentru mai multe informaţii, vedeţi şi ." + +#: Ch-Resources.xml:43(title) +msgid "Linux Standard Base" +msgstr "Linux Standard Base" + +#: Ch-Resources.xml:44(para) +msgid "LSB resource agents are those found in /etc/init.d. Generally they are provided by the OS/distribution and in order to be used with the cluster, must conform to the LSB Spec." +msgstr "Agenţii de resursă LSB sunt cei găsiţi în /etc/init.d. În mod normal aceştia sunt furnizaţi de către OS/distribuţie şi pentru a putea fi folosiţi împreună cu clusterul, trebuie să se conforme Specificaţiilor LSB." + +#: Ch-Resources.xml:48(para) +msgid "The LSB Spec (as it relates to init scripts) can be found at: " +msgstr "Specificaţiile LSB (în conjunctura scripturilor de init) pot fi găsite la: " + +#: Ch-Resources.xml:50(para) +msgid "Many distributions claim LSB compliance but ship with broken init scripts. To see if your init script is LSB-compatible, see the FAQ entry . The most common problems are:" +msgstr "Multe distribuţii afirmă compatibilitatea LSB dar livrează scripturi de init nefuncţionale din acest punct de vedere. Pentru a vedea dacă scriptul vostru de init este compatibil LSB, vedeţi intrarea din FAQ referitoare la . Cele mai comune probleme sunt:" + +#: Ch-Resources.xml:56(para) +msgid "Not implementing the status operation at all" +msgstr "Neimplementarea în vreun fel a operaţiunii status" + +#: Ch-Resources.xml:57(para) +msgid "Not observing the correct exit status codes for start/stop/status actions" +msgstr "Neobservarea status-urilor corecte de ieşire pentru acţiuni start/stop/status" + +#: Ch-Resources.xml:58(para) +msgid "Starting a started resource returns an error (this violates the LSB spec)" +msgstr "Pornirea unei resurse deja pornite returnează o eroare (acest aspect încalcă specificaţia LSB)" + +#: Ch-Resources.xml:59(para) +msgid "Stopping a stopped resource returns an error (this violates the LSB spec)" +msgstr "Oprirea unei resurse deja oprită returnează o eroare (acest aspect încalcă specificaţia LSB)" + +#: Ch-Resources.xml:63(title) +msgid "Legacy Heartbeat" +msgstr "Moştenirea Heartbeat" + +#: Ch-Resources.xml:64(para) +msgid "Version 1 of Heartbeat came with its own style of resource agents and it is highly likely that many people have written their own agents based on its conventions. To enable administrators to continue to use these agents, they are supported by the new cluster manager." +msgstr "Versiunea 1 de Heartbeat venea cu propriul stil de agenţi de resursă şi este foarte probabil că mulţi oameni şi-au scris proprii agenţi de resursă pe baza convenţiilor acestuia. Pentru a permite administratorilor să continue folosirea acestor agenţi, aceştia sunt suportaţi de către noul manager de cluster." + +#: Ch-Resources.xml:68(para) +msgid "For more information, see: " +msgstr "Pentru mai multe informaţii, vedeţi: " + +#: Ch-Resources.xml:69(para) +msgid "The OCF class is the most preferred one as it is an industry standard, highly flexible (allowing parameters to be passed to agents in a non-positional manner) and self-describing." +msgstr "Clasa OCF este cea mai preferată din moment ce este un standard al industriei, foarte flexibilă (permiţând parametrii să fie pasaţi agenţilor într-o manieră care nu ţine cont de poziţia acestora) şi auto-descriptivă." + +#: Ch-Resources.xml:70(para) +msgid "There is also an additional class, STONITH, which is used exclusively for fencing related resources. This is discussed later in ." +msgstr "Mai există o clasă adiţională, STONITH, care este folosită exclusiv pentru resurse relevante în procesul de evacuare. Acest aspect este discutat mai târziu în ." + +#: Ch-Resources.xml:77(title) +msgid "Properties" +msgstr "Proprietăţi" + +#: Ch-Resources.xml:78(para) +msgid "These values tell the cluster which script to use for the resource, where to find that script and what standards it conforms to." +msgstr "Aceste valori îi spun clusterului care script să îl folosească pentru resursă, unde să găsească acel script şi care sunt standardele sub care acesta aderă." + +#: Ch-Resources.xml:80(title) +msgid "Properties of a Primitive Resource" +msgstr "Proprietăţile unei Resurse Primitive" + +#: Ch-Resources.xml:84(entry) +#: Ch-Resources.xml:160(entry) +#: Ch-Resources.xml:349(entry) +msgid "Field" +msgstr "Câmp" + +#: Ch-Resources.xml:85(entry) +#: Ch-Resources.xml:162(entry) +#: Ch-Resources.xml:350(entry) +msgid "Description" +msgstr "Descriere" + +#: Ch-Resources.xml:90(entry) +#: Ch-Resources.xml:353(entry) +msgid "id" +msgstr "id" + +#: Ch-Resources.xml:91(entry) +msgid "Your name for the resource" +msgstr "Numele pe care îl daţi resursei" + +#: Ch-Resources.xml:94(entry) +msgid "class" +msgstr "clasa" + +#: Ch-Resources.xml:95(entry) +msgid "The standard the script conforms to. Allowed values: heartbeat, lsb, ocf, stonith" +msgstr "Standardul la care aderă scriptul. Valori permise: heartbeat, lsb, ocf, stonith" + +#: Ch-Resources.xml:98(entry) +msgid "type" +msgstr "tipul" + +#: Ch-Resources.xml:99(entry) +msgid "The name of the Resource Agent you wish to use. eg. IPaddr or Filesystem" +msgstr "Numele Agentului de Resursă pe care doriţi să îl folosiţi. ex. IPaddr sau Filesystem" + +#: Ch-Resources.xml:102(entry) +msgid "provider" +msgstr "furnizor" + +#: Ch-Resources.xml:103(entry) +msgid "The OCF spec allows multiple vendors to supply the same Resource Agent. To use the OCF resource agents supplied with Heartbeat, you should specify heartbeat here." +msgstr "Specificaţia OCF permite mai multor entităţi să furnizeze acelaşi Agent de Resursă. Pentru a folosi agenţii de resursă OCF furnizaţi împreună cu Heartbeat, ar trebui să specificaţi heartbeat aici." + +#: Ch-Resources.xml:108(para) +msgid "Resource definitions can be queried with the crm_resource tool. For example" +msgstr "Definiţiile resurselor pot fi interogate cu utilitarul crm_resource. De exemplu" + +#: Ch-Resources.xml:109(command) +msgid "crm_resource --resource Email --query-xml" +msgstr "crm_resource --resource Email --query-xml" + +#: Ch-Resources.xml:110(para) +msgid "might produce" +msgstr "ar putea produce următorul text de ieşire" + +#: Ch-Resources.xml:112(title) +msgid "An example LSB resource" +msgstr "Un exemplu de resursă LSB" + +#: Ch-Resources.xml:117(para) +msgid "One of the main drawbacks to LSB resources is that they do not allow any parameters" +msgstr "Una din principalele aspecte negative ale resurselor LSB este acela că nu permit parametri" + +#: Ch-Resources.xml:118(para) +msgid "or, for an OCF resource:" +msgstr "sau pentru o resursă OCF:" + +#: Ch-Resources.xml:120(title) +msgid "An example OCF resource" +msgstr "Un exemplu de resursă OCF" + +#: Ch-Resources.xml:131(para) +msgid "or, finally for the equivalent legacy Heartbeat resource:" +msgstr "sau în sfârşit pentru echivalentul unei resurse din moştenirea Heartbeat: " + +#: Ch-Resources.xml:133(title) +msgid "An example Heartbeat resource" +msgstr "Un exemplu de resursă Heartbeat" + +#: Ch-Resources.xml:145(para) +msgid "Heartbeat resources take only ordered and unnamed parameters. The supplied name therefore indicates the order in which they are passed to the script. Only single digit values are allowed." +msgstr "Resursele Heartbeat primesc doar parametri ordonaţi şi fără denumire. Numele furnizat indică prin urmare ordinea în care sunt pasaţi către script. Doar valori formate dintr-o singură cifră sunt permise." + +#: Ch-Resources.xml:153(title) +msgid "Resource Options" +msgstr "Opţiuni ale Resurselor" + +#: Ch-Resources.xml:154(para) +msgid "Options are used by the cluster to decide how your resource should behave and can be easily set using the --meta option of the crm_resource command." +msgstr "Opţiunile sunt folosite de către cluster pentru a decide cum ar trebui să se comporte resursa voastră şi pot fi setate facil folosind opţiunea --meta a comenzii crm_resource." + +#: Ch-Resources.xml:156(title) +msgid "Options for a Primitive Resource" +msgstr "Opţiuni pentru o Resursă Primitivă" + +#: Ch-Resources.xml:161(entry) +msgid "Default" +msgstr "Valoarea implicită" + +#: Ch-Resources.xml:165(entry) +msgid "priority" +msgstr "prioritate" + +#: Ch-Resources.xml:166(entry) +msgid "0" +msgstr "0" + +#: Ch-Resources.xml:167(entry) +msgid "If not all resources can be active, the cluster will stop lower priority resources in order to keep higher priority ones active." +msgstr "Dacă nu pot fi active toate resursele , clusterul va opri resursele cu prioritate mai mică pentru a păstra resursele cu o prioritate mai mare active." + +#: Ch-Resources.xml:170(entry) +msgid "target-role" +msgstr "target-role" + +#: Ch-Resources.xml:171(entry) +msgid "Started" +msgstr "Pornit" + +#: Ch-Resources.xml:173(para) +msgid "What state should the cluster attempt to keep this resource in? Allowed values:" +msgstr "În ce stare ar trebui să încerce clusterul să menţină această resursă? Valori permise:" + +#: Ch-Resources.xml:175(para) +msgid "Stopped - Force the resource to be stopped" +msgstr "Oprită - Forţează resursa să fie oprită" + +#: Ch-Resources.xml:176(para) +msgid "Started - Allow the resource to be started (In the case of multi-state resources, they will not promoted to master)" +msgstr "Pornită - Permite resursei să fie pornită (În cazul resurselor cu multi-state, acestea nu vor fi promovate la master)" + +#: Ch-Resources.xml:177(para) +msgid "Master - Allow the resource to be started and, if appropriate, promoted" +msgstr "Master - Permite resursei să fie pornită, iar dacă este adecvat, promovată" + +#: Ch-Resources.xml:182(entry) +msgid "is-managed" +msgstr "is-managed" + +#: Ch-Resources.xml:183(entry) +msgid "TRUE" +msgstr "TRUE" + +#: Ch-Resources.xml:184(entry) +msgid "Is the cluster allowed to start and stop the resource? Allowed values: true, false" +msgstr "Îi este permis clusterului să pornească şi să oprească resursa? Valori permise: adevărat, fals" + +#: Ch-Resources.xml:190(entry) +msgid "resource-stickiness" +msgstr "resource-stickiness" + +#: Ch-Resources.xml:191(entry) +msgid "Inherited" +msgstr "Moştenită" + +#: Ch-Resources.xml:192(entry) +msgid "How much does the resource prefer to stay where it is? Defaults to the value of resource-stickiness in the rsc_defaults section" +msgstr "Cât de mult preferă resursa să rămână acolo unde este? Valoarea implicită este cea a resource-stickiness din secţiunea rsc_defaults" + +#: Ch-Resources.xml:198(entry) +msgid "migration-threshold" +msgstr "migration-threshold" + +#: Ch-Resources.xml:199(entry) +msgid "INFINITY (disabled)" +msgstr "INFINIT (dezactivat)" + +#: Ch-Resources.xml:200(entry) +msgid "How many failures should occur for this resource on a node before making the node ineligible to host this resource." +msgstr "Câte eşecuri ar trebui să se întâmple acestei resurse pe un nod înainte de face nodul ineligibil de a mai găzdui această resursă." + +#: Ch-Resources.xml:203(entry) +msgid "failure-timeout" +msgstr "failure-timeout" + +#: Ch-Resources.xml:204(entry) +msgid "0 (disabled)" +msgstr "0 (dezactivat)" + +#: Ch-Resources.xml:205(entry) +msgid "How many seconds to wait before acting as if the failure had not occurred (and potentially allowing the resource back to the node on which it failed)." +msgstr "Câte secunde să aştepte înainte să se comporte ca şi cum eşecul nu s-ar fi întâmplat (şi potenţial să permită resursei să revină pe nodul pe care a eşuat)." + +#: Ch-Resources.xml:208(entry) +msgid "multiple-active" +msgstr "multiple-active" + +#: Ch-Resources.xml:209(entry) +msgid "stop_start" +msgstr "stop_start" + +#: Ch-Resources.xml:211(para) +msgid "What should the cluster do if it ever finds the resource active on more than one node. Allowed values:" +msgstr "Ce ar trebui să realizeze clusterul dacă găseşte vreodată o resursă activă pe mai mult de un nod. Valori permise:" + +#: Ch-Resources.xml:213(para) +msgid "block - mark the resource as unmanaged" +msgstr "block - marchează resursa ca fiind negestionată" + +#: Ch-Resources.xml:214(para) +msgid "stop_only - stop all active instances and leave them that way" +msgstr "stop_only - opreşte toate instanţele active şi lasă-le în acest fel" + +#: Ch-Resources.xml:215(para) +msgid "stop_start - stop all active instances and start the resource in one location only" +msgstr "stop_start - opreşte toate instanţele active şi porneşte resursa doar într-o singură locaţie" + +#: Ch-Resources.xml:222(para) +msgid "If you performed the following commands on the previous LSB Email resource" +msgstr "Dacă aţi efectuat următoarele comenzi pe resursa LSB Email anterioară" + +#: Ch-Resources.xml:224(command) +msgid "crm_resource --meta --resource Email --set-parameter priority --property-value 100" +msgstr "crm_resource --meta --resource Email --set-parameter priority --property-value 100" + +#: Ch-Resources.xml:225(command) +msgid "crm_resource --meta --resource Email --set-parameter multiple-active --property-value block" +msgstr "crm_resource --meta --resource Email --set-parameter multiple-active --property-value block" + +#: Ch-Resources.xml:227(para) +msgid "the resulting resource definition would be" +msgstr "definiţia rezultantă a resursei ar fi" + +#: Ch-Resources.xml:229(title) +msgid "An LSB resource with cluster options" +msgstr "O resursă LSB cu opţiuni ale clusterului" + +#: Ch-Resources.xml:243(title) +msgid "Setting Global Defaults for Resource Options" +msgstr "Setarea de Valori Implicite Globale pentru Opţiunile Clusterului" + +#: Ch-Resources.xml:244(para) +msgid "To set a default value for a resource option, simply add it to the rsc_defaults section with crm_attribute. Thus," +msgstr "Pentru a seta o valoare implicită pentru o opţiune a resursei, pur şi simplu adăugaţi-o la secţiunea rsc_defaults cu crm_attribute. Astfel," + +#: Ch-Resources.xml:245(command) +msgid "crm_attribute --type rsc_defaults --attr-name is-managed --attr-value false" +msgstr "crm_attribute --type rsc_defaults --attr-name is-managed --attr-value false" + +#: Ch-Resources.xml:246(para) +msgid "would prevent the cluster from starting or stopping any of the resources in the configuration (unless of course the individual resources were specifically enabled and had is-managed set to true)." +msgstr "ar preveni clusterul de a porni sau opri orice resurse din configuraţie (cu excepţia cazului când resursele individuale au fost activate în mod specific şi aveau is-managed setat pe true)." + +#: Ch-Resources.xml:249(title) +msgid "Instance Attributes" +msgstr "Atributele Instanţelor" + +#: Ch-Resources.xml:250(para) +msgid "The scripts of some resource classes (LSB not being one of them) can be given parameters which determine how they behave and which instance of a service they control." +msgstr "Scripturile unor clase de resurse (LSB nefiind una dintre acestea) pot primi parametri care determină cum se comportă şi care instanţe ale unui serviciu controlează acestea." + +#: Ch-Resources.xml:251(para) +msgid "If your resource agent supports parameters, you can add them with the crm_resource command. For instance" +msgstr "Dacă agentul vostru de resursă suportă parametri, îi puteţi adăuga cu comanda crm_resource. De exemplu" + +#: Ch-Resources.xml:252(command) +msgid "crm_resource --resource Public-IP --set-parameter ip --property-value 1.2.3.4" +msgstr "crm_resource --resource Public-IP --set-parameter ip --property-value 1.2.3.4" + +#: Ch-Resources.xml:253(para) +msgid "would create an entry in the resource like this" +msgstr "ar crea o intrare în resursă precum aceasta" + +#: Ch-Resources.xml:255(title) +msgid "An example OCF resource with instance attributes" +msgstr "Un exemplu de resursă OCF cu atribute de instanţă" + +#: Ch-Resources.xml:266(para) +msgid "For an OCF resource, the result would be an environment variable called OCF_RESKEY_ip with a value of 1.2.3.4" +msgstr "Pentru o resursă OCF, rezultatul ar fi o variabilă de mediu numită OCF_RESKEY_ip cu o valoare de 1.2.3.4" + +#: Ch-Resources.xml:267(para) +msgid "The list of instance attributes supported by an OCF script can be found by calling the resource script with the meta-data command. The output contains an XML description of all the supported attributes, their purpose and default values." +msgstr "Lista de atribute de instanţă suportate de un script OCF poate fi găsită apelând scriptul resursei cu comanda meta-data. Rezultatul de ieşire conţine o descriere XML a tuturor atributelor suportate, scopul acestora şi valori implicite." + +#: Ch-Resources.xml:272(title) +msgid "Displaying the metadata for the Dummy resource agent template" +msgstr "Afişarea metadata pentru template-ul agentului de resursă Dummy" + +#: Ch-Resources.xml:274(userinput) +#, no-wrap +msgid "export OCF_ROOT=/usr/lib/ocf; $OCF_ROOT/resource.d/pacemaker/Dummy meta-data" +msgstr "export OCF_ROOT=/usr/lib/ocf; $OCF_ROOT/resource.d/pacemaker/Dummy meta-data" + +#: Ch-Resources.xml:322(title) +msgid "Resource Operations" +msgstr "Operaţiile Resurselor" + +#: Ch-Resources.xml:324(title) +msgid "Monitoring Resources for Failure" +msgstr "Monitorizarea Resurselor pentru Defecţiuni" + +#: Ch-Resources.xml:325(para) +msgid "By default, the cluster will not ensure your resources are still healthy. To instruct the cluster to do this, you need to add a monitor operation to the resource's definition." +msgstr "În mod implicit, clusterul nu va asigura că resursele voastre sunt încă sănătoase. Pentru a instrui clusterul să realizeze acest lucru, trebuie să adăugaţi o operaţiune de monitorizare la definiţia resursei." + +#: Ch-Resources.xml:330(title) +msgid "An OCF resource with a recurring health check" +msgstr "O resursă OCF cu o verificare recurentă a sănătăţii" + +#: Ch-Resources.xml:345(title) +msgid "Properties of an Operation" +msgstr "Proprietăţile unei Operaţii" + +#: Ch-Resources.xml:354(entry) +msgid "Your name for the action. Must be unique." +msgstr "Numele dat acţiunii. Trebuie să fie unic." + +#: Ch-Resources.xml:357(entry) +msgid "name" +msgstr "nume" + +#: Ch-Resources.xml:358(entry) +msgid "The action to perform. Common values: monitor, start, stop" +msgstr "Acţiunea pe care să o execute. Valori obişnuite: monitor, start, stop" + +#: Ch-Resources.xml:361(entry) +msgid "interval" +msgstr "interval" + +#: Ch-Resources.xml:362(entry) +msgid "How frequently (in seconds) to perform the operation. Default value: 0" +msgstr "Cât de frecvent (în secunde) să efectueze operaţiunea. Valoarea implicită: 0" + +#: Ch-Resources.xml:365(entry) +msgid "timeout" +msgstr "interval" + +#: Ch-Resources.xml:366(entry) +msgid "How long to wait before declaring the action has failed." +msgstr "Cât de mult să aştepte înainte de a declara că acţiunea a eşuat." + +#: Ch-Resources.xml:369(entry) +msgid "requires" +msgstr "necesită" + +#: Ch-Resources.xml:371(para) +msgid "What conditions need to be satisfied before this action occurs. Allowed values:" +msgstr "Care condiţii trebuie să fie satisfăcute înainte ca această acţiune să se întâmple. Valori permise:" + +#: Ch-Resources.xml:373(para) +msgid "nothing - The cluster may start this resource at any time" +msgstr "nothing - Clusterul poate porni această resursă oricând" + +#: Ch-Resources.xml:374(para) +msgid "quorum - The cluster can only start this resource if a majority of the configured nodes are active" +msgstr "quorum - Clusterul poate porni această resursă dacă o majoritate a nodurilor configurate este activă" + +#: Ch-Resources.xml:375(para) +msgid "fencing - The cluster can only start this resource if a majority of the configured nodes are active and any failed or unknown nodes have been powered off." +msgstr "fencing - Clusterul poate porni această resursă doar dacă o majoritate a nodurilor configurate este activă şi orice noduri necunoscute sau defectate au fost deconectate de la reţeaua de alimentare." + +#: Ch-Resources.xml:377(para) +msgid "STONITH resources default to nothing, and all others default to fencing if STONITH is enabled and quorum otherwise." +msgstr "Resursele STONITH nu au valori implicite, iar toate celelalte au ca valoare implicită evacuarea din cluster dacă STONITH este activat şi quorum în caz contrar." + +#: Ch-Resources.xml:381(entry) +msgid "on-fail" +msgstr "on-fail" + +#: Ch-Resources.xml:383(para) +msgid "The action to take if this action ever fails. Allowed values:" +msgstr "Acţiunea pe care să o execute dacă vreodată această acţiune eşuează. Valori permise:" + +#: Ch-Resources.xml:385(para) +msgid "ignore - Pretend the resource did not fail" +msgstr "ignore - Consideră că acţiunea nu a eşuat" + +#: Ch-Resources.xml:386(para) +msgid "block - Don't perform any further operations on the resource" +msgstr "block - Nu mai efectua operaţiuni ulterioare pe resursă" + +#: Ch-Resources.xml:387(para) +msgid "stop - Stop the resource and do not start it elsewhere" +msgstr "stop - Opreşte resursa şi nu o mai porni în altă parte" + +#: Ch-Resources.xml:388(para) +msgid "restart - Stop the resource and start it again (possibly on a different node)" +msgstr "restart - Opreşte resursa şi porneşte-o din nou (posibil pe un nod diferit)" + +#: Ch-Resources.xml:389(para) +msgid "fence - STONITH the node on which the resource failed" +msgstr "fence - STONITH nodul pe care resursa a eşuat" + +#: Ch-Resources.xml:390(para) +msgid "standby - Move all resources away from the node on which the resource failed" +msgstr "standby - Mută toate resursele de pe nodul pe care resursa a eşuat" + +#: Ch-Resources.xml:392(para) +msgid "The default for the stop operation is fence when STONITH is enabled and block otherwise. All other operations default to stop." +msgstr "Valoarea implicită pentru operaţiunea stop este evacuarea din cluster atunci când STONITH este activat şi block în caz contrar. Toate celelalte operaţiuni au valoarea implicită stop." + +#: Ch-Resources.xml:396(entry) +msgid "enabled" +msgstr "activat" + +#: Ch-Resources.xml:397(emphasis) +msgid "true" +msgstr "adevărat" + +#: Ch-Resources.xml:397(entry) +msgid "If false, the operation is treated as if it does not exist. Allowed values: , false" +msgstr "Dacă este setat pe fals, operaţiunea este tratată ca şi când nu ar exista. Valori permise: , false" + +#: Ch-Resources.xml:405(title) +msgid "Setting Global Defaults for Operations" +msgstr "Setarea de Valori Implicite Globale pentru Operaţiuni" + +#: Ch-Resources.xml:406(para) +msgid "To set a default value for a operation option, simply add it to the op_defaults section with crm_attribute. Thus," +msgstr "Pentru a seta valoarea implicită pentru opţiunea unei operaţiuni, pur şi simplu adăuga-ţi-o la secţiunea op_defaults cu crm_attribute. Prin urmare," + +#: Ch-Resources.xml:407(command) +msgid "crm_attribute --type op_defaults --attr-name timeout --attr-value 20s" +msgstr "crm_attribute --type op_defaults --attr-name timeout --attr-value 20s" + +#: Ch-Resources.xml:408(para) +msgid "would default each operation's timeout to 20 seconds. If an operation's definition also includes a value for timeout, then that value would be used instead (for that operation only)." +msgstr "ar seta valoarea implicită a intervalului de expirare al fiecărei operaţiuni la 20 de secunde. Dacă definiţia unei operaţiuni include de asemenea o valoare pentru timeout, atunci acea valoare ar fi folosită în schimb (numai pentru acea operaţiune)." + +#: Ch-Resources.xml:413(title) +msgid "When Resources Take a Long Time to Start/Stop" +msgstr "Când Resursele Durează Mult Timp să Pornească/Oprească" + +#: Ch-Resources.xml:414(para) +msgid "There are a number of implicit operations that the cluster will always perform - start, stop and a non-recurring monitor operation (used at startup to check the resource isn't already active). If one of these is taking too long, then you can create an entry for them and simply specify a new value." +msgstr "Sunt un număr de operaţiuni implicite pe care clusterul pe va efectua întotdeauna - start, stop şi o operaţiune monitor nerecurentă (folosită la pornire pentru a verifica dacă resursa nu este deja activă). Dacă una din aceste operaţiuni durează prea mult, atunci puteţi crea o intrare pentru acestea şi să specificaţi o valoarea nouă." + +#: Ch-Resources.xml:419(title) +msgid "An OCF resource with custom timeouts for its implicit actions" +msgstr "O resursă OCF cu intervale customizate pentru acţiunile implicite ale acesteia" + +#: Ch-Resources.xml:437(title) +msgid "Multiple Monitor Operations" +msgstr "Operaţiuni de Monitorizare Multiple" + +#: Ch-Resources.xml:438(para) +msgid "Provided no two operations (for a single resource) have the same name and interval you can have as many monitor operations as you like. In this way you can do a superficial health check every minute and progressively more intense ones at higher intervals." +msgstr "Atâta timp cât o pereche de două operaţiuni (pentru o singură resursă) nu au acelaşi nume sau acelaşi interval puteţi avea cât de multe operaţiuni de monitorizare pe cât doriţi. În acest fel puteţi realiza o verificare superficială a stării de sănătate la fiecare minut şi unele progresiv mai intense la intervale mai mari." + +#: Ch-Resources.xml:442(para) +msgid "To tell the resource agent what kind of check to perform, you need to provide each monitor with a different value for a common parameter. The OCF standard creates a special parameter called OCF_CHECK_LEVEL for this purpose and dictates that it is made available to the resource agent without the normal OCF_RESKEY_ prefix." +msgstr "Pentru a spune agentului ce fel de verificare să efectueze, trebuie să furnizaţi fiecărei operaţiuni monitor o valoare diferită pentru un parametru comun. Standardul OCF creează un parametru special numit OCF_CHECK_LEVEL pentru acest scop şi dictează că este făcut disponibil agentului de resursă fără obişnuitul prefix OCF_RESKEY_ ." + +#: Ch-Resources.xml:446(para) +msgid "Whatever name you choose, you can specify it by adding an instance_attributes block to the op tag. Note that it is up to each resource agent to look for the parameter and decide how to use it." +msgstr "Indiferent de ce nume alegeţi, puteţi să îl specificaţi adăugând un bloc instance_attributes la tag-ul op. Ţineţi cont că acest lucru este datoria fiecărui agent de resursă să verifice dacă parametrul există şi să decidă cum să îl folosească." + +#: Ch-Resources.xml:451(title) +msgid "An OCF resource with two recurring health checks performing different levels of checks" +msgstr "O resursă OCF cu două verificări de sănătate recurente efectuând nivele diferite de verificări" + +#: Ch-Resources.xml:476(title) +msgid "Disabling a Monitor Operation" +msgstr "Dezactivarea unei Operaţiuni de Monitorizare" + +#: Ch-Resources.xml:477(para) +msgid "The easiest way to stop a recurring monitor is to just delete it. However there can be times when you only want to disable it temporarily. In such cases, simply add disabled=\"true\" to the operation's definition." +msgstr "Cel mai simplu mod de a opri un monitor recurent este să îl ştergeţi. Însă pot exista momente când vreţi doar să îl dezactivaţi temporar. În astfel de cazuri, pur şi simplu adăugaţi disabled=\"true\" la definiţia operaţiunii." + +#: Ch-Resources.xml:483(title) +msgid "Example of an OCF resource with a disabled health check" +msgstr "Exemplu de resursă OCF cu o verificare a sănătăţii dezactivată" + +#: Ch-Resources.xml:497(para) +msgid "This can be achieved from the command-line by executing" +msgstr "Acest lucru poate fi realizat din linia de comanda executând" + +#: Ch-Resources.xml:498(command) +msgid "cibadmin -M -X ‘<op id=\"public-ip-check\" disabled=\"true\"/>'" +msgstr "cibadmin -M -X ‘<op id=\"public-ip-check\" disabled=\"true\"/>'" + +#: Ch-Resources.xml:499(para) +msgid "Once you've done whatever you needed to do, you can then re-enable it with" +msgstr "Odată ce aţi făcut ceea ce aveaţi nevoie să faceţi, îl puteţi reactiva cu" + +#: Ch-Resources.xml:500(command) +msgid "cibadmin -M -X ‘<op id=\"public-ip-check\" disabled=\"false\"/>'" +msgstr "cibadmin -M -X ‘<op id=\"public-ip-check\" disabled=\"false\"/>'" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ch-Resources.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ch-Rules.po b/doc/Pacemaker_Explained/ro-RO/Ch-Rules.po new file mode 100644 index 0000000000..f52c9b3348 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ch-Rules.po @@ -0,0 +1,492 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-11-02 18:46+0100\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Ch-Rules.xml:2(title) +msgid "Rules" +msgstr "Reguli" + +#: Ch-Rules.xml:3(para) +msgid "Rules can be used to make your configuration more dynamic. One common example is to set one value for resource-stickiness during working hours, to prevent resources from being moved back to their most preferred location, and another on weekends when no-one is around to notice an outage." +msgstr "Regulile pot fi folosite pentru a face configuraţia voastră mai dinamică. Un exemplu comun este de a seta o valoare pentru resource-stickiness în timpul orelor de program, pentru a împiedica resursele de a fi mutate înapoi la locaţia cea mai preferată a acestora, iar altă valoare în weekend-uri când nu este nimeni în preajmă să detecteze o întrerupere a serviciului." + +#: Ch-Rules.xml:7(para) +msgid "Another use of rules might be to assign machines to different processing groups (using a node attribute) based on time and to then use that attribute when creating location constraints." +msgstr "O altă utilizare a regulilor ar putea fi pentru a asigna maşini la grupuri de procesare diferite (folosind un atribut de nod) bazat pe timp şi mai apoi să folosească acel atribut pentru a crea o restricţie de locaţie." + +#: Ch-Rules.xml:8(para) +msgid "Each rule can contain a number of expressions, date-expressions and even other rules. The results of the expressions are combined based on the rule's boolean-op field to determine if the rule ultimately evaluates to true or false. What happens next depends on the context in which the rule is being used." +msgstr "Fiecare regulă poate conţine un număr de expresii, expresii de dată şi chiar si alte reguli. Rezultatele expresiilor sunt combinate pe baza câmpului boolean op al regulii pentru a determina dacă regula în ultimă instanţă este evaluată ca adevărat sau fals. Ce se întâmplă mai departe depinde de contextul în care regula este folosită." + +#: Ch-Rules.xml:14(title) +msgid "Properties of a Rule" +msgstr "Proprietăţile unei Reguli" + +#: Ch-Rules.xml:18(entry) +#: Ch-Rules.xml:51(entry) +#: Ch-Rules.xml:97(entry) +#: Ch-Rules.xml:141(entry) +msgid "Field" +msgstr "Câmp" + +#: Ch-Rules.xml:19(entry) +#: Ch-Rules.xml:52(entry) +#: Ch-Rules.xml:98(entry) +#: Ch-Rules.xml:142(entry) +msgid "Description" +msgstr "Descriere" + +#: Ch-Rules.xml:24(entry) +msgid "role" +msgstr "rol" + +#: Ch-Rules.xml:25(emphasis) +msgid "Started" +msgstr "Pornită" + +#: Ch-Rules.xml:25(entry) +msgid "Limits the rule to only apply when the resource is in that role. Allowed values: , Slave, Master. NOTE: A rule with role=\"Master\" can not determine the initial location of a clone instance. It will only affect which of the active instances will be promoted." +msgstr "Limitează regula pentru a se aplica numai când resursa se află în acel rol. Valori permise: , Slave, Master. NOTĂ: O regulă cu rolul=\"Master\" nu poate determina locaţia iniţială a unei instanţe ale unei clone. Va afecta numai care dintre instanţele active va fi promovată." + +#: Ch-Rules.xml:28(entry) +msgid "score" +msgstr "scor" + +#: Ch-Rules.xml:29(entry) +msgid "The score to apply if the rule evaluates to \"true\". Limited to use in rules that are part of location constraints." +msgstr "Scorul pe care să îl aplice în cazul în care regula este evaluată la \"true\". Limitată la folosirea în reguli care sunt parte din restricţiile de locaţie." + +#: Ch-Rules.xml:32(entry) +msgid "score-attribute" +msgstr "score-attribute" + +#: Ch-Rules.xml:33(entry) +msgid "The node attribute to look up and use as a score if the rule evaluates to \"true\". Limited to use in rules that are part of location constraints." +msgstr "Atributul nodului pe care să îl caute şi pe care să îl folosească drept scor dacă regula se evaluează la \"true\". Limitată la folosirea în reguli care sunt parte din restricţii de locaţie." + +#: Ch-Rules.xml:36(entry) +msgid "boolean-op" +msgstr "boolean-op" + +#: Ch-Rules.xml:37(emphasis) +msgid "and" +msgstr "şi" + +#: Ch-Rules.xml:37(entry) +msgid "How to combine the result of multiple expression objects. Allowed values: , or" +msgstr "Cum să combinaţi rezultatul mai multor obiecte de expresii. Valori permise: , sau" + +#: Ch-Rules.xml:43(title) +msgid "Node Attribute Expressions" +msgstr "Expresiile Atributelor de Nod" + +#: Ch-Rules.xml:44(para) +msgid "Expression objects are used to control a resource based on the attributes defined by a node or nodes. In addition to any attributes added by the administrator, each node has a built-in node attribute called #uname that can also be used." +msgstr "Obiectele de expresie sunt folosite pentru a controla o resursă pe baza atributelor definite de un nod sau de mai multe noduri. Adiţional la orice atribute adăugate de administrator, fiecare nod are un atribut de nod predefinit numit #uname care poate fi folosit de asemenea." + +#: Ch-Rules.xml:47(title) +msgid "Properties of an Expression" +msgstr "Proprietăţile unei Expresii" + +#: Ch-Rules.xml:55(entry) +msgid "value" +msgstr "valoarea" + +#: Ch-Rules.xml:56(entry) +msgid "User supplied value for comparison" +msgstr "Valorea furnizată de utilizator pentru comparaţie" + +#: Ch-Rules.xml:59(entry) +msgid "attribute" +msgstr "atributul" + +#: Ch-Rules.xml:60(entry) +msgid "The node attribute to test" +msgstr "Atributul nodului care să fie testat" + +#: Ch-Rules.xml:63(entry) +msgid "type" +msgstr "tipul" + +#: Ch-Rules.xml:64(emphasis) +msgid "string" +msgstr "şir" + +#: Ch-Rules.xml:64(entry) +msgid "Determines how the value(s) should be tested. Allowed values: integer, , version" +msgstr "Determină cum ar trebui să fie testate valorile. Valori permise: întreg, , versiune" + +#: Ch-Rules.xml:67(entry) +#: Ch-Rules.xml:109(entry) +msgid "operation" +msgstr "operaţiune" + +#: Ch-Rules.xml:69(para) +msgid "The comparison to perform. Allowed values:" +msgstr "Comparaţia pe care să o efectueze. Valori permise:" + +#: Ch-Rules.xml:71(para) +msgid "lt - True if the node attribute's value is less than value" +msgstr "lt - Adevărat dacă valoarea atributului nodului este mai mică decât valoare" + +#: Ch-Rules.xml:72(para) +msgid "gt - True if the node attribute's value is greater than value" +msgstr "gt - Adevărat dacă valoarea atributului nodului este mai mare decât valoare" + +#: Ch-Rules.xml:73(para) +msgid "lte - True if the node attribute's value is less than or equal to value" +msgstr "lte - Adevărat dacă valoarea atributului nodului este mai mică sau egală cu valoare" + +#: Ch-Rules.xml:74(para) +msgid "gte - True if the node attribute's value is greater than or equal to value" +msgstr "gte - Adevărat dacă valoarea atributului nodului este mai mare sau egală cu valoare" + +#: Ch-Rules.xml:75(para) +msgid "eq - True if the node attribute's value is equal to value" +msgstr "eq - Adevărat dacă valoarea atributului nodului este egală cu valoare" + +#: Ch-Rules.xml:76(para) +msgid "ne - True if the node attribute's value is not equal to value" +msgstr "ne - Adevărat dacă valoarea atributului nodului nu este egală cu valoare" + +#: Ch-Rules.xml:77(para) +msgid "defined - True if the node has an the named attribute" +msgstr "defined - Adevărat dacă nodul are un atribut numit" + +#: Ch-Rules.xml:78(para) +msgid "not_defined - True if the node does not have the named attribute" +msgstr "not_defined - Adevărat dacă nodul nu are un atribut numit" + +#: Ch-Rules.xml:87(title) +msgid "Time/Date Based Expressions" +msgstr "Expresii Bazate pe Timp/Dată" + +#: Ch-Rules.xml:88(para) +msgid "As the name suggests, date_expressions are used to control a resource or cluster option based on the current date/time. They can contain an optional date_spec and/or duration object depending on the context." +msgstr "După cum sugerează numele, date_expressions sunt folosite pentru a controla o resursă sau opţiune a clusterului pe baza timpului/dăţii curente. Acestea pot conţine opţional obiecte date_spec şi/sau duration în funcţie de context." + +#: Ch-Rules.xml:93(title) +msgid "Properties of a Date Expression" +msgstr "Proprietăţile unei Expresii de Dată" + +#: Ch-Rules.xml:101(entry) +msgid "start" +msgstr "început" + +#: Ch-Rules.xml:102(entry) +msgid "A date/time conforming to the ISO8601 specification." +msgstr "O dată/oră conformă cu specificaţia ISO8601." + +#: Ch-Rules.xml:105(entry) +msgid "end" +msgstr "sfârşit" + +#: Ch-Rules.xml:106(entry) +msgid "A date/time conforming to the ISO8601 specification. Can be inferred by supplying a value for start and a duration." +msgstr "O dată/oră conformă cu specificaţia ISO8601. Poate fi omisă dacă se furnizează o valoare pentru început şi o durată." + +#: Ch-Rules.xml:111(para) +msgid "Compares the current date/time with the start and/or end date, depending on the context. Allowed values:" +msgstr "Compară data/ora curentă cu data de început şi/sau sfârşit, în funcţie de context. Valori permise:" + +#: Ch-Rules.xml:113(para) +msgid "gt - True if the current date/time is after start" +msgstr "gt - Adevărat dacă data/ora curentă este după început" + +#: Ch-Rules.xml:114(para) +msgid "lt - True if the current date/time is before end" +msgstr "lt - Adevărat dacă data/ora curentă este înainte de sfârşit" + +#: Ch-Rules.xml:115(para) +msgid "in-range - True if the current date/time is after start and before end" +msgstr "in-range - Adevărat dacă data/ora curentă este după început şi înainte de sfârşit" + +#: Ch-Rules.xml:116(para) +msgid "date-spec - performs a cron-like comparison between the contents of date_spec and now" +msgstr "date-spec - efectuează o comparaţie similară cron-ului între conţinutul date_spec şi acum" + +#: Ch-Rules.xml:123(para) +msgid "Because the comparisons (except for date_spec) include the time, the eq, neq, gte and lte operators have not been implemented." +msgstr "Deoarece comparaţiile (cu excepţia date_spec) includ timpul, operatorii eq, neq, gte şi lte nu au fost implementaţi." + +#: Ch-Rules.xml:125(title) +msgid "Date Specifications" +msgstr "Specificaţiile Datei" + +#: Ch-Rules.xml:126(para) +msgid "date_spec objects are used to create cron-like expressions relating to time. Each field can contain a single number or a single range. Instead of defaulting to zero, any field not supplied is ignored." +msgstr "Obiectele date_spec sunt folosite pentru a crea expresii similare cu cele create de cron în relaţie cu timpul. Fiecare câmp poate conţine un singur număr sau un singur şir. În loc să aibe valoarea implicită zero, orice câmp a cărui valoare nu este furnizată este ignorat." + +#: Ch-Rules.xml:131(para) +msgid "For example, monthdays=\"1\" matches the first day of every month and hours=\"09-17\" matches the hours between 9am and 5pm inclusive. However at this time one cannot specify weekdays=\"1,2\" or weekdays=\"1-2,5-6\" since they contain multiple ranges. Depending on demand, this may be implemented in a future release." +msgstr "De exemplu, monthdays=\"1\" se potriveşte pentru prima zi din fiecare lună şi hours=\"09-17\" se potriveşte orelor între 9am şi 5pm inclusiv. Însă la acest moment nu se poate specifica weekdays=\"1,2\" sau weekdays=\"1-2,5-6\" din moment ce conţin şiruri multiple. În funcţie de cerere, acest aspect ar putea fi implementat într-un release viitor." + +#: Ch-Rules.xml:137(title) +msgid "Properties of a Date Spec" +msgstr "Proprietăţile unei Specificaţii de Dată" + +#: Ch-Rules.xml:147(entry) +msgid "id" +msgstr "id" + +#: Ch-Rules.xml:148(entry) +msgid "A unique name for the date" +msgstr "Un nume unic pentru dată" + +#: Ch-Rules.xml:151(entry) +msgid "hours" +msgstr "hours" + +#: Ch-Rules.xml:152(entry) +msgid "Allowed values: 0-23" +msgstr "Valori permise: 0-23" + +#: Ch-Rules.xml:155(entry) +msgid "monthdays" +msgstr "monthdays" + +#: Ch-Rules.xml:156(entry) +msgid "Allowed values: 0-31 (depending on current month and year)" +msgstr "Valori permise: 0-31 (în funcţie de luna curentă şi an)" + +#: Ch-Rules.xml:159(entry) +msgid "weekdays" +msgstr "weekdays" + +#: Ch-Rules.xml:160(entry) +msgid "Allowed values: 1-7 (1=Monday, 7=Sunday)" +msgstr "Valori permise: 1-7 (1=Luni, 7=Duminică)" + +#: Ch-Rules.xml:163(entry) +msgid "yeardays" +msgstr "yeardays" + +#: Ch-Rules.xml:164(entry) +msgid "Allowed values: 1-366 (depending on the current year)" +msgstr "Valori permise: 1-366 (în funcţie de anul curent)" + +#: Ch-Rules.xml:167(entry) +msgid "months" +msgstr "months" + +#: Ch-Rules.xml:168(entry) +msgid "Allowed values: 1-12" +msgstr "Valori permise: 1-12" + +#: Ch-Rules.xml:171(entry) +msgid "weeks" +msgstr "weeks" + +#: Ch-Rules.xml:172(entry) +msgid "Allowed values: 1-53 (depending on weekyear)" +msgstr "Valori permise: 1-53 (în funcţie câte săptămâni are anul)" + +#: Ch-Rules.xml:175(entry) +msgid "years" +msgstr "years" + +#: Ch-Rules.xml:176(entry) +msgid "Year according the Gregorian calendar" +msgstr "Anul conform calendarului Gregorian" + +#: Ch-Rules.xml:179(entry) +msgid "weekyears" +msgstr "weekyears" + +#: Ch-Rules.xml:181(para) +msgid "May differ from Gregorian years." +msgstr "Ar putea fi diferit de anii Gregorieni." + +#: Ch-Rules.xml:182(para) +msgid "Eg. \"2005-001 Ordinal\" is also \"2005-01-01 Gregorian\" and is also \"2004-W53-6 Weekly\"" +msgstr "Ex. \"2005-001 Ordinal\" este de asemenea \"2005-01-01 Gregorian\" şi de asemenea \"2004-W53-6 Weekly\"" + +#: Ch-Rules.xml:186(entry) +msgid "moon" +msgstr "moon" + +#: Ch-Rules.xml:187(entry) +msgid "Allowed values: 0..7 (0 is new, 4 is full moon). Seriously, you can use this. This was implemented to demonstrate the ease with which new comparisons could be added." +msgstr "Valori permise: 0..7 (0 este pentru lună nouă, 4 pentru pentru lună plină). Nu glumesc, puteţi folosi asta. Acest lucru a fost implementat ca să demonstreze uşurinţa cu care se pot adăuga comparaţii noi." + +#: Ch-Rules.xml:194(title) +msgid "Durations" +msgstr "Durate" + +#: Ch-Rules.xml:195(para) +msgid "Durations are used to calculate a value for end when one is not supplied to in_range operations. They contain the same fields as date_spec objects but without the limitations (ie. you can have a duration of 19 days). Like date_specs, any field not supplied is ignored." +msgstr "Duratele sunt folosite pentru a calcula valoarea pentru sfârşit atunci când una nu este furnizată în operaţiunile in_range. Acestea conţin aceleaşi câmpuri ca şi obiectele date_spec dar fără limitări (ex. puteţi avea o durată de 19 zile). Ca şi în cazul date_specs, orice câmp care nu este furnizat este ignorat." + +#: Ch-Rules.xml:201(title) +msgid "Sample Time Based Expressions" +msgstr "Exemple de Expresii Bazate pe Timp" + +#: Ch-Rules.xml:203(title) +msgid "True if now is any time in the year 2005" +msgstr "Adevărat dacă acum este oricând în anul 2005" + +#: Ch-Rules.xml:215(title) +msgid "Equivalent expression." +msgstr "Expresie echivalentă." + +#: Ch-Rules.xml:227(title) +msgid "9am-5pm, Mon-Friday" +msgstr "9am-5pm, Lun-Vineri" + +#: Ch-Rules.xml:239(title) +msgid "9am-6pm, Mon-Friday, or all day saturday" +msgstr "9am-6pm, Lun-Vineri sau toată ziua sâmbătă" + +#: Ch-Rules.xml:254(title) +msgid "9am-5pm or 9pm-12pm, Mon-Friday" +msgstr "9am-5pm sau 9pm-12pm, Lun-Vineri" + +#: Ch-Rules.xml:274(title) +msgid "Mondays in March 2005" +msgstr "Zilele de Luni în Martie 2005" + +#: Ch-Rules.xml:286(para) +msgid "NOTE: Because no time is specified, 00:00:00 is implied." +msgstr "NOTĂ: Pentru că nici un timp nu este specificat, 00:00:00 este subînţeles." + +#: Ch-Rules.xml:287(para) +msgid "This means that the range includes all of 2005-03-01 but none of 2005-04-01." +msgstr "Acest lucru înseamnă că şirul include tot din 2005-03-01 dar nimic din 2005-04-01." + +#: Ch-Rules.xml:288(para) +msgid "You may wish to write end=\"2005-03-31T23:59:59\" to avoid confusion." +msgstr "Aţi dori să scrieţi end=\"2005-03-31T23:59:59\" pentru a evita confuzia." + +#: Ch-Rules.xml:290(title) +msgid "A full moon on Friday the 13th" +msgstr "O lună plină pe data de Vineri 13" + +#: Ch-Rules.xml:305(title) +msgid "Using Rules to Determine Resource Location" +msgstr "Folosind Reguli pentru a Determina Locaţia Resurselor" + +#: Ch-Rules.xml:306(para) +msgid "If the constraint's outer-most rule evaluates to false, the cluster treats the constraint as if it was not there. When the rule evaluates to true, the node's preference for running the resource is updated with the score associated with the rule." +msgstr "Dacă regula cea mai exterioară a unei restricţii este evaluată la fals, clusterul se poartă cu restricţia ca şi cum nu ar fi fost acolo. Când regula este evaluată ca adevărat, preferinţa nodului pentru rularea resursei este actualizată cu scorul asociat cu această regulă." + +#: Ch-Rules.xml:310(para) +msgid "If this sounds familiar, its because you have been using a simplified syntax for location constraint rules already. Consider the following location constraint:" +msgstr "Dacă acest lucru sună cunoscut, este datorită faptului că deja folosiţi o sintaxă simplificată pentru regulile de restricţie a locaţiei. Consideraţi următoarea restricţie de locaţie:" + +#: Ch-Rules.xml:315(title) +msgid "Prevent myApacheRsc from running on c001n03" +msgstr "Împiedică myApacheRsc de a rula pe c001n03" + +#: Ch-Rules.xml:316(programlisting) +#, no-wrap +msgid "" +"\n" +" <rsc_location id=\"dont-run-apache-on-c001n03\" rsc=\"myApacheRsc\" score=\"-INFINITY\" node=\"c001n03\"/>\n" +"\t" +msgstr "" +"\n" +" <rsc_location id=\"dont-run-apache-on-c001n03\" rsc=\"myApacheRsc\" score=\"-INFINITY\" node=\"c001n03\"/>\n" +"\t" + +#: Ch-Rules.xml:320(para) +msgid "This constraint can be more verbosely written as:" +msgstr "Aceaastă restricţie poate fi scrisă mai elaborat ca:" + +#: Ch-Rules.xml:322(title) +msgid "Prevent myApacheRsc from running on c001n03 - expanded version" +msgstr "Împiedică myApacheRsc de a rula pe c001n03 - versiunea extinsă" + +#: Ch-Rules.xml:333(para) +msgid "The advantage of using the expanded form is that one can then add extra clauses to the rule, such as limiting the rule such that it only applies during certain times of the day or days of the week (this is discussed in subsequent sections)." +msgstr "Avantajul folosirii formei extinse este că se pot adăuga clauze suplimentare la regulă, cum ar fi limitarea regulii astfel încât să se aplice doar în momente specifice ale zilei sau zilelor săptămânii (acest lucru este discutat în secţiunile următoare)." + +#: Ch-Rules.xml:334(para) +msgid "It also allows us to match on node properties other than its name. If we rated each machine's CPU power such that the cluster had the following nodes section:" +msgstr "Este folosit de asemenea pentru a realiza potriviri pe proprietăţi ale nodului altele decât numele acestuia. Dacă am apreciat puterea procesorului fiecărei maşini astfel încât clusterul să aibe următoarea secţiune de noduri: " + +#: Ch-Rules.xml:339(title) +msgid "A sample nodes section for use with score-attribute" +msgstr "Un exemplu de secţiune de noduri pentru utilizarea cu score-attribute" + +#: Ch-Rules.xml:357(para) +msgid "then we could prevent resources from running on underpowered machines with the rule" +msgstr "atunci am putea împiedica resursele de a rula pe maşini fără nivelul de procesare cerut cu această regulă" + +#: Ch-Rules.xml:366(title) +msgid "Using score-attribute Instead of score" +msgstr "Folosind score-attribute în loc de score" + +#: Ch-Rules.xml:367(para) +msgid "When using score-attribute instead of score, each node matched by the rule has its score adjusted differently, according to its value for the named node attribute. Thus in the previous example, if a rule used score-attribute=\"cpu_mips\", c001n01 would have its preference to run the resource increased by 1234 whereas c001n02 would have its preference increased by 5678." +msgstr "Când folosim score-attribute în loc de score, fiecare nod care se potriveşte regulii va avea scorul acestuia ajustat în mod diferit, în funcţie de valoarea sa pentru atributul numit de nod. Prin urmare în exemplul anterior, dacă o regulă folosea score-attribute=\"cpu_mips\", c001n001 ar avea preferinţa proprie de a rula resursa crescută cu 1234 în timp ce c001n02 ar avea preferinţa crescută cu 5678." + +#: Ch-Rules.xml:374(title) +msgid "Using Rules to Control Resource Options" +msgstr "Folosind Reguli pentru a Controla Opţiunile Resurselor" + +#: Ch-Rules.xml:375(para) +msgid "Often some cluster nodes will be different from their peers, sometimes these differences (the location of a binary or the names of network interfaces) require resources be configured differently depending on the machine they're hosted on." +msgstr "Adeseori unele noduri din cluster vor fi diferite de altele, câteodată aceste diferenţe (locaţia unui binar sau numele interfeţelor de reţea) necesită ca şi resursele să fie configurate diferit în funcţie de maşina pe care sunt găzduite." + +#: Ch-Rules.xml:376(para) +msgid "By defining multiple instance_attributes objects for the resource and adding a rule to each, we can easily handle these special cases." +msgstr "Prin definirea de obiecte multiple instance_attributes pentru resursă şi prin adăugarea unei reguli pentru fiecare, putem gestiona facil aceste cazuri speciale." + +#: Ch-Rules.xml:377(para) +msgid "In the example below, mySpecialRsc will use eth1 and port 9999 when run on node1, eth2 and port 8888 on node2 and default to eth0 and port 9999 for all other nodes." +msgstr "În exemplul de mai jos, mySpecialRsc va folosi eth1 şi portul 9999 când va rula pe node1, eth2 şi portul 8888 pe node2 şi va avea valorea implicită eth0 şi portul 9999 pentru toate celelalte noduri. " + +#: Ch-Rules.xml:379(title) +msgid "Defining different resource options based on the node name" +msgstr "Definirea de opţiuni de resursă diferite pe baza numelui nodului" + +#: Ch-Rules.xml:404(para) +msgid "The order in which instance_attributes objects are evaluated is determined by their score (highest to lowest). If not supplied, score defaults to zero and objects with an equal score are processed in listed order. If the instance_attributes object does not have a rule or has a rule that evaluates to true, then for any parameter the resource does not yet have a value for, the resource will use the parameter values defined by the instance_attributes object." +msgstr "Ordinea în care obiectele instance_attributes sunt evaluate este determinată de către scorul acestora (cel mai mare la cel mai mic). Dacă nu este furnizat, scorul va avea valoarea implicită zero şi obiectele cu un scor egal sunt procesate în ordinea listată. Dacă obiectul instance_attributes nu are o rule sau are o rule care este evaluată la true, atunci pentru orice parametru pentru care resursa nu are înca o valoare, resursa va folosi valorile parametrilor definite de obiectul instance_attributes." + +#: Ch-Rules.xml:411(title) +msgid "Using Rules to Control Cluster Options" +msgstr "Folosind Reguli pentru a Controla Opţiunile Clusterului" + +#: Ch-Rules.xml:412(para) +msgid "Controlling cluster options is achieved in much the same manner as specifying different resource options on different nodes." +msgstr "Controlarea opţiunilor clusterului este reuşită în mare parte prin aceeaşi manieră ca şi specificarea diverselor opţiuni pentru resurse pe noduri diferite." + +#: Ch-Rules.xml:413(para) +msgid "The difference is that because they are cluster options, one cannot (or should not because they won't work) use attribute based expressions. The following example illustrates how to set a different resource-stickiness value during and outside of work hours. This allows resources to automatically move back to their most preferred hosts, but at a time that (in theory) does not interfere with business activities." +msgstr "Diferenţa este că din cauza că sunt opţiuni de cluster, nu ar trebui să puteţi (sau nu ar trebui să pentru că acestea nu funcţionează) să folosiţi expresii bazate pe atribute. Următorul exemplu ilustrează cum să setaţi o valoare instance_attributes diferită în timpul şi în afara orelor de lucru. Acest lucru permite resurselor să se mute înapoi în mod automat la gazdele cele mai preferate, dar la un moment în care (teoretic) nu interferează cu activităţile de business." + +#: Ch-Rules.xml:419(title) +msgid "Set resource-stickiness=INFINITY Mon-Fri between 9am and 6pm, and resource-stickiness=0 all other times" +msgstr "Setaţi resource-stickiness=INFINITY Lun-Vin între 9am şi 6pm, iar resource-stickiness=0 în restul timpului" + +#: Ch-Rules.xml:440(title) +msgid "Ensuring Time Based Rules Take Effect" +msgstr "Asigurarea că Regulile Bazate pe Timp Iau Efect" + +#: Ch-Rules.xml:441(para) +msgid "A Pacemaker cluster is an event driven system. As such, it won't recalculate the best place for resources to run in unless something (like a resource failure or configuration change) happens. This can mean that a location constraint that only allows resource X to run between 9am and 5pm is not enforced." +msgstr "Un cluster Pacemaker este un sistem condus de evenimente. Prin urmare, nu va recalcula cel mai bun loc pentru a rula resursele decât dacă ceva (cum ar fi eşecul unei resurse sau modificarea configuraţiei) se întâmplă. Asta poate însemna că o restricţie a locaţiei care permite resursei X să ruleze numai între 9am şi 5pm nu este aplicată în mod obligatoriu." + +#: Ch-Rules.xml:446(para) +msgid "If you rely on time based rules, it is essential that you set the cluster-recheck-interval option. This tells the cluster to periodically recalculate the ideal state of the cluster. For example, if you set cluster-recheck-interval=5m, then sometime between 9:00 and 9:05 the cluster would notice that it needs to start resource X, and between 17:00 and 17:05 it would realize it needed to be stopped." +msgstr "Dacă vă bazaţi pe reguli bazate pe timp, este esenţial să setaţi opţiunea cluster-recheck-interval. Aceasta spune clusterului să recalculeze periodic starea ideală a clusterului. De exemplu, dacă setaţi cluster-recheck-interval=5m, atunci cândva între 9:00 şi 9:05 clusterul va detecta că trebuie să pornească resursa X, iar între 17:00 şi 17:05 va realiza că trebuie să o oprească." + +#: Ch-Rules.xml:451(para) +msgid "Note that the timing of the actual start and stop actions depends on what else needs to be performed first." +msgstr "Ţineţi cont că momentul efectiv de pornire şi oprire al acţiunilor depinde de ce alte lucruri trebuie efectuate mai întâi." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ch-Rules.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ch-Status.po b/doc/Pacemaker_Explained/ro-RO/Ch-Status.po new file mode 100644 index 0000000000..472451d5fb --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ch-Status.po @@ -0,0 +1,398 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-11-03 01:06+0100\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Ch-Status.xml:2(title) +msgid "Status - Here be dragons" +msgstr "Status - Aici sunt dragoni" + +#: Ch-Status.xml:3(para) +msgid "Most users never need understand the contents of the status section and can be content with the output from crm_mon. However for those with a curious inclination, the following attempts to provide an overview of its contents." +msgstr "Majoritatea utilizatorilor nu trebuie niciodată să înţeleagă conţinutul secţiunii de status şi se pot mulţumi cu rezultatul de ieşire de la crm_mon. Totuşi pentru aceia dintre voi cu o înclinaţie către curiozitate, următoarele încearcă să furnizeze o vedere de ansamblu asupra conţinutului acestuia." + +#: Ch-Status.xml:8(title) +msgid "Node Status" +msgstr "Status-ul Nodului" + +#: Ch-Status.xml:9(para) +msgid "In addition to the cluster's configuration, the CIB holds an up-to-date representation of each cluster node in the status section." +msgstr "În plus faţă de configuraţia clusterului, CIB-ul menţine o reprezentare cât mai actualizată a fiecărui nod din cluster în secţiunea de status." + +#: Ch-Status.xml:11(title) +msgid "A bare-bones status entry for a healthy node called cl-virt-1" +msgstr "O intrare iniţială de status pentru un nod sănătos numit cl-virt-1" + +#: Ch-Status.xml:21(para) +msgid "Users are highly recommended not to modify any part of a node's state directly. The cluster will periodically regenerate the entire section from authoritative sources. So any changes should be with the tools for those subsystems." +msgstr "Utilizatorilor li se recomandă stringent să nu modifice nici o parte din starea nodului în mod direct. Clusterul va regenera periodic întreaga secţiune din surse autoritative. Aşa că orice modificare ar trebui executată cu utilitarele pentru acele subsisteme." + +#: Ch-Status.xml:27(title) +msgid "Authoritative Sources for State Information" +msgstr "Surse Autoritative pentru Informaţia de Stare" + +#: Ch-Status.xml:31(entry) +msgid "Dataset" +msgstr "Dataset" + +#: Ch-Status.xml:32(entry) +msgid "Authoritative Source" +msgstr "Sursă Autoritativă" + +#: Ch-Status.xml:35(entry) +msgid "node_state fields" +msgstr "câmpurile node_state" + +#: Ch-Status.xml:36(entry) +#: Ch-Status.xml:76(entry) +msgid "crmd" +msgstr "crmd" + +#: Ch-Status.xml:39(entry) +msgid "transient_attributes tag" +msgstr "tag-ul transient_attributes" + +#: Ch-Status.xml:40(entry) +msgid "attrd" +msgstr "attrd" + +#: Ch-Status.xml:43(entry) +msgid "lrm tag" +msgstr "tag-ul lrm" + +#: Ch-Status.xml:44(entry) +msgid "lrmd" +msgstr "lrmd" + +#: Ch-Status.xml:47(para) +msgid "The fields used in the node_state objects are named as they are largely for historical reasons and are rooted in Pacemaker's origins as the Heartbeat resource manager. They have remained unchanged to preserve compatibility with older versions." +msgstr "Câmpurile folosite în obiectele node_state sunt denumite aşa cum sunt în mare parte din motive istorice şi sunt înrădăcinate în originile Pacemaker-ului ca manager de resurse pentru Heartbeat. Acestea au rămas neschimbate pentru a păstra compatibilitatea cu versiuni mai vechi." + +#: Ch-Status.xml:52(title) +msgid "Node Status Fields" +msgstr "Câmpuri de Status ale Nodului" + +#: Ch-Status.xml:56(entry) +#: Ch-Status.xml:147(entry) +msgid "Field" +msgstr "Câmp" + +#: Ch-Status.xml:57(entry) +#: Ch-Status.xml:148(entry) +msgid "Description" +msgstr "Descriere" + +#: Ch-Status.xml:60(entry) +#: Ch-Status.xml:151(entry) +msgid "id" +msgstr "id" + +#: Ch-Status.xml:61(entry) +msgid "Unique identifier for the node. Corosync based clusters use the same value as uname, Heartbeat cluster use a human-readable (but annoying) UUID." +msgstr "Identificator unic pentru nod. Clusterele bazate pe Corosync folosesc aceeaşi valoare ca uname, clusterele Heartbeat folosesc un UUID în format uşor de citit de oameni (dar enervant)." + +#: Ch-Status.xml:64(entry) +msgid "uname" +msgstr "uname" + +#: Ch-Status.xml:65(entry) +msgid "The node's machine name (output from uname -n)" +msgstr "Numele nodului (rezultat din uname -n)" + +#: Ch-Status.xml:68(entry) +msgid "ha" +msgstr "ha" + +#: Ch-Status.xml:69(entry) +msgid "Is the cluster software active on the node. Allowed values: active, dead" +msgstr "Este soft-ul de cluster activ pe nod? Valori permise: active, dead" + +#: Ch-Status.xml:72(entry) +msgid "in_ccm" +msgstr "in_ccm" + +#: Ch-Status.xml:73(entry) +msgid "Is the node part of the cluster's membership. Allowed values: true, false" +msgstr "Este nodul parte din apartenenţa clusterului. Valori permise: true, false" + +#: Ch-Status.xml:77(entry) +msgid "Is the crmd process active on the node. Allowed values: online, offline" +msgstr "Este procesul crmd activ pe nod. Valori permise: online, offline" + +#: Ch-Status.xml:80(entry) +msgid "join" +msgstr "join" + +#: Ch-Status.xml:81(entry) +msgid "Is the node participating in hosting resources. Allowed values: down, pending, member, banned" +msgstr "Participă nodul în găzduirea de resurse. Valori permise: down, pending, member, banned" + +#: Ch-Status.xml:84(entry) +msgid "expected" +msgstr "expected" + +#: Ch-Status.xml:85(entry) +msgid "Expected value for join" +msgstr "Valoarea aşteptată pentru join" + +#: Ch-Status.xml:88(entry) +#: Ch-Status.xml:207(entry) +msgid "crm-debug-origin" +msgstr "crm-debug-origin" + +#: Ch-Status.xml:89(entry) +msgid "Diagnostic indicator. The origin of the most recent change(s)." +msgstr "Indicator de diagnostic. Originea celei mai recente schimbări." + +#: Ch-Status.xml:92(para) +msgid "The cluster uses these fields to determine if, at the node level, the node is healthy or is in a failed state and needs to be fenced." +msgstr "Clusterul foloseşte aceste câmpuri ca să determine dacă, la nivel de nod, nodul este sănătos sau este într-o stare defectuoasă şi trebuie evacuat." + +#: Ch-Status.xml:95(title) +msgid "Transient Node Attributes" +msgstr "Atribute Tranziente ale Nodului" + +#: Ch-Status.xml:96(para) +msgid "Like regular node attributes, the name/value pairs listed here also help describe the node. However they are forgotten by the cluster when the node goes offline. This can be useful, for instance, when you only want a node to be in standby mode (not able to run resources) until the next reboot." +msgstr "Precum atributele nodului obişnuite, perechile nume/valoare listate aici ajută de asemenea la descrierea nodului. Totuşi acestea sunt uitate de către cluster atunci când nodul trece în mod offline. Acest lucru poate fi util, de exemplu, când vreţi un nod să se afle în mod standby (să nu poată rula resurse) până la următorul reboot." + +#: Ch-Status.xml:101(para) +msgid "In addition to any values the administrator sets, the cluster will also store information about failed resources here." +msgstr "În plus faţă de orice valori setează administratorul, clusterul va stoca de asemenea informaţii despre resursele eşuate aici." + +#: Ch-Status.xml:103(title) +msgid "Example set of transient node attributes for node \"cl-virt-1\"" +msgstr "Exemplu de atribute tranziente de nod pentru nodul \"cl-virt-1\"" + +#: Ch-Status.xml:119(para) +msgid "You can use the following Perl one-liner to print a human readable of any seconds-since-epoch value:" +msgstr "Puteţi folosi umătorul one-liner Perl pentru a printa o valoare a secundelor-de-la-epoch în format uşor de citit pentru oameni." + +#: Ch-Status.xml:120(literal) +msgid "$seconds" +msgstr "$seconds" + +#: Ch-Status.xml:120(command) +msgid "" +"perl -e 'print scalar(localtime()).\"\\n" +"\"'" +msgstr "" +"perl -e 'print scalar(localtime()).\"\\n" +"\"'" + +#: Ch-Status.xml:117(para) +msgid "In the above example, we can see that the pingd:0 resource has failed once, at Mon Apr 6 11:22:22 2009. We also see that the node is connected to three \"pingd\" peers and that all known resources have been checked for on this machine (probe_complete)." +msgstr "În exemplul de mai sus, putem vedea că resursa pingd:0 a eşuat o dată, pe Mon Apr 6 11:22:22 2009. Observăm de asemenea că nodul este conectat la trei vecini \"pingd\" şi că toate resursele cunoscute au fost verificate pe această maşină (probe_complete)." + +#: Ch-Status.xml:126(title) +msgid "Operation History" +msgstr "Istoricul Operaţiilor" + +#: Ch-Status.xml:127(para) +msgid "A node's resource history is held in the lrm_resources tag (a child of the lrm tag). The information stored here includes enough information for the cluster to stop the resource safely if it is removed from the configuration section. Specifically we store the resource's id, class, type and provider." +msgstr "Istoricul resurselor unui nod este ţinut în tag-ul lrm_resources (un copil al tag-ului lrm). Informaţia stocată aici include destulă informaţie pentru ca şi clusterul să oprească resursa în siguranţă dacă este îndepărtată din secţiunea de configurare. În mod specific stocăm id, class, type şi provider-ul resursei." + +#: Ch-Status.xml:133(title) +msgid "A record of the apcstonith resource" +msgstr "O înregistrare a resursei apcstonith" + +#: Ch-Status.xml:134(screen) +#, no-wrap +msgid "" +"\n" +" <lrm_resource id=\"apcstonith\" type=\"apcmastersnmp\" class=\"stonith\">\n" +"\t" +msgstr "" +"\n" +" <lrm_resource id=\"apcstonith\" type=\"apcmastersnmp\" class=\"stonith\">\n" +"\t" + +#: Ch-Status.xml:138(para) +msgid "Additionally, we store the last job for every combination of resource, action and interval. The concatenation of the values in this tuple are used to create the id of the lrm_rsc_op object." +msgstr "Suplimentar, stocăm ultimul job pentru fiecare combinaţie de resource, action şi interval. Concatenarea valorilor din această tuplă este folosită pentru a crea id-ul obiectului lrm_rsc_op." + +#: Ch-Status.xml:143(title) +msgid "Contents of an lrm_rsc_op job." +msgstr "Conţinutul unui job lrm_rsc_op." + +#: Ch-Status.xml:152(entry) +msgid "Identifier for the job constructed from the resource id, operation and interval." +msgstr "Identificatorul pentru job construit din id-ul resursei, operaţiunii şi intervalului." + +#: Ch-Status.xml:155(entry) +msgid "call-id" +msgstr "call-id" + +#: Ch-Status.xml:156(entry) +msgid "The job's ticket number. Used as a sort key to determine the order in which the jobs were executed." +msgstr "Numărul tichetului job-ului. Folosit ca şi cheie de sortare pentru a determina ordinea în care job-urile au fost executate." + +#: Ch-Status.xml:159(entry) +msgid "operation" +msgstr "operaţiune" + +#: Ch-Status.xml:160(entry) +msgid "The action the resource agent was invoked with." +msgstr "Acţiunea cu care a fost invocat agentul de resursă." + +#: Ch-Status.xml:163(entry) +msgid "interval" +msgstr "interval" + +#: Ch-Status.xml:164(entry) +msgid "The frequency, in milliseconds, at which the operation will be repeated. 0 indicates a one-off job." +msgstr "Frecvenţa, în milisecunde, la care va fi repetată operaţiunea. 0 indică un job unicat." + +#: Ch-Status.xml:167(entry) +msgid "op-status" +msgstr "op-status" + +#: Ch-Status.xml:168(entry) +msgid "The job's status. Generally this will be either 0 (done) or -1 (pending). Rarely used in favor of rc-code." +msgstr "Status-ul job-ului. În general acesta va fi ori 0 (completat) ori -1 (în aşteptare). Rareori folosit în favoarea a rc-code." + +#: Ch-Status.xml:171(entry) +msgid "rc-code" +msgstr "rc-code" + +#: Ch-Status.xml:172(entry) +msgid "The job's result. Refer to for details on what the values here mean and how they are interpreted." +msgstr "Rezultatul job-ului. Faceţi referire la pentru detalii despre ce înseamnă valorile de aici şi cum sunt interpretate." + +#: Ch-Status.xml:175(entry) +msgid "last-run" +msgstr "last-run" + +#: Ch-Status.xml:176(entry) +msgid "Diagnostic indicator. Machine local date/time, in seconds since epoch, at which the job was executed." +msgstr "Indicator de diagnostic. Ora/data locală a maşinii, în secunde de la epocă, la care job-ul a fost executat." + +#: Ch-Status.xml:179(entry) +msgid "last-rc-change" +msgstr "last-rc-change" + +#: Ch-Status.xml:180(entry) +msgid "Diagnostic indicator. Machine local date/time, in seconds since epoch, at which the job first returned the current value of rc-code" +msgstr "Indicator de diagnostic. Ora/data locală a maşinii, în secunde de la epocă, la care job-ul a returnat prima oară valoarea rc-code" + +#: Ch-Status.xml:183(entry) +msgid "exec-time" +msgstr "exec-time" + +#: Ch-Status.xml:184(entry) +msgid "Diagnostic indicator. Time, in milliseconds, that the job was running for" +msgstr "Indicator de diagnostic. Timpul, în milisecunde, pentru care a rulat job-ul" + +#: Ch-Status.xml:187(entry) +msgid "queue-time" +msgstr "queue-time" + +#: Ch-Status.xml:188(entry) +msgid "Diagnostic indicator. Time, in seconds, that the job was queued for in the LRMd" +msgstr "Indicator de diagnostic. Timpul, în secunde, pentru care a fost pus job-ul în coada de aşteptare în LRMd" + +#: Ch-Status.xml:191(entry) +msgid "crm_feature_set" +msgstr "crm_feature_set" + +#: Ch-Status.xml:192(entry) +msgid "The version which this job description conforms to. Used when processing op-digest" +msgstr "Versiunea la care se conformează această descriere a job-ului. Folosită când se procesează op-digest" + +#: Ch-Status.xml:195(entry) +msgid "transition-key" +msgstr "transition-key" + +#: Ch-Status.xml:196(entry) +msgid "A concatenation of the job's graph action number, the graph number, the expected result and the UUID of the crmd instance that scheduled it. This is used to construct transition-magic (below)." +msgstr "O concatenare a numărului de acţiune al grafului job-ului, numărul grafului, rezultatul aşteptat şi UUID-ul instanţei de crmd care l-a programat. Acesta este folosit pentru a construi magica-tranziţiei (mai jos)." + +#: Ch-Status.xml:199(entry) +msgid "transition-magic" +msgstr "transition-magic" + +#: Ch-Status.xml:200(entry) +msgid "A concatenation of the job's op-status, rc-code and transition-key. Guaranteed to be unique for the life of the cluster (which ensures it is part of CIB update notifications) and contains all the information needed for the crmd to correctly analyze and process the completed job. Most importantly, the decomposed elements tell the crmd if the job entry was expected and whether it failed." +msgstr "O concatenare a op-status-ului job-ului, rc-code-ului şi a transition-key. Garantat să fie unic pe perioada vieţii clusterului (fapt care asigură ca este parte din notificările de actualizări ale CIB-ului) şi conţine toată informaţia necesară ca şi crmd-ul să analizeze şi să proceseze corect job-ul terminat. Cel mai important, elementele descompuse îi spun crmd-ului dacă intrarea pentru job era aşteptată şi dacă aceasta a eşuat." + +#: Ch-Status.xml:203(entry) +msgid "op-digest" +msgstr "op-digest" + +#: Ch-Status.xml:204(entry) +msgid "An MD5 sum representing the parameters passed to the job. Used to detect changes to the configuration and restart resources if necessary." +msgstr "Un hash MD5 reprezentând parametrii trimişi job-ului. Folosit pentru a detecta schimbările în configuraţie şi a reporni resursele dacă este necesar." + +#: Ch-Status.xml:208(entry) +msgid "Diagnostic indicator. The origin of the current values." +msgstr "Indicator de diagnostic. Originea valorilor curente." + +#: Ch-Status.xml:214(title) +msgid "Simple Example" +msgstr "Exemplu Simplu" + +#: Ch-Status.xml:216(title) +msgid "A monitor operation performed by the cluster to determine the current state of the apcstonith resource" +msgstr "O operaţiune de monitorizare efectuată de către cluster pentru a determina starea curentă a resursei apcstonith." + +#: Ch-Status.xml:230(para) +msgid "In the above example, the job is a non-recurring monitor often referred to as a \"probe\" for the apcstonith resource. The cluster schedules probes for every configured resource on when a new node starts, in order to determine the resource's current state before it takes further any further action." +msgstr "În exemplul de mai sus, job-ul este un monitor non-recurent adeseori făcută referire la acesta sub numele de \"probă\" pentru resursa apcstonith. Clusterul programează probe pentru fiecare resursă configurată când un nou nod porneşte, în vederea determinării stării curente a resursei înainte de a urma orice acţiune ulterioară." + +#: Ch-Status.xml:234(para) +msgid "From the transition-key, we can see that this was the 22nd action of the 2nd graph produced by this instance of the crmd (2668bbeb-06d5-40f9-936d-24cb7f87006a). The third field of the transition-key contains a 7, this indicates that the job expects to find the resource inactive. By now looking at the rc-code property, we see that this was the case." +msgstr "Din transition-key, putem să vedem că aceasta a fost a 22-a acţiune a celui de-al 2-lea graf produs de această instanţă a crmd-ului (2668bbeb-06d5-40f9-936d-24cb7f87006a). Al treilea câmp al transition-key conţine un 7, acest lucru indică faptul că job-ul se aşteaptă să găsească resursa inactivă. Uitându-ne acum la proprietatea rc-code, putem vedea că aşa a şi fost." + +#: Ch-Status.xml:239(para) +msgid "Evidently, the cluster started the resource elsewhere as that is the only job recorded for this node." +msgstr "În mod evident, clusterul a pornit resursa în altă parte din moment ce acesta este singurul job înregistrat pentru acest nod." + +#: Ch-Status.xml:242(title) +msgid "Complex Resource History Example" +msgstr "Exemplu Complex de Istoric al Resurselor" + +#: Ch-Status.xml:244(title) +msgid "Resource history of a pingd clone with multiple jobs" +msgstr "Istoricul resurselor unei clone pingd cu job-uri multiple" + +#: Ch-Status.xml:276(para) +msgid "When more than one job record exists, it is important to first sort them by call-id before interpret them. Once sorted, the above example can be summarized as:" +msgstr "Când există mai mult de o singură înregistrare a unui job, este important mai întâi să le sortăm după call-id înainte de a le interpreta. Odată sortate, exemplul de mai sus poate fi sumarizat ca:" + +#: Ch-Status.xml:281(para) +msgid "A non-recurring monitor operation returning 7 (not running), with a call-id of 3" +msgstr "O operaţiune non-recurentă de monitorizare returnează 7 (nu rulează), cu un call-id de 3" + +#: Ch-Status.xml:282(para) +msgid "A stop operation returning 0 (success), with a call-id of 32" +msgstr "O operaţiune de oprire returnează 0 (succes), cu un call-id de 32" + +#: Ch-Status.xml:283(para) +msgid "A start operation returning 0 (success), with a call-id of 33" +msgstr "O operaţiune de pornire returnează 0 (succes), cu un call-id de 33" + +#: Ch-Status.xml:284(para) +msgid "A recurring monitor returning 0 (success), with a call-id of 34" +msgstr "Un monitor recurent returnează 0 (succes), cu un call-id de 34" + +#: Ch-Status.xml:286(para) +msgid "The cluster processes each job record to build up a picture of the resource's state. After the first and second entries, it is considered stopped and after the third it considered active. Based on the last operation, we can tell that the resource is currently active." +msgstr "Clusterul procesează fiecare înregistrare a unui job pentru a construi o imagine asupra stării resursei. După prima şi a doua intrare, este considerată oprită şi după a treia este considerată activă. Pe baza ultimelor operaţiuni, putem spune că resursa este activă în mod curent." + +#: Ch-Status.xml:291(para) +msgid "Additionally, from the presence of a stop operation with a lower call-id than that of the start operation, we can conclude that the resource has been restarted. Specifically this occurred as part of actions 11 and 31 of transition 11 from the crmd instance with the key 2668bbeb-06d5-40f9-936d-24cb7f87006a. This information can be helpful for locating the relevant section of the logs when looking for the source of a failure." +msgstr "Suplimentar, din prezenţa unei operaţiuni de oprire cu un call-id mai mic decât cel al operaţiunii start, putem concluziona că resursa a fost repornită. În mod specific acest lucru s-a întâmplat ca parte a acţiunilor 11 şi 31 ale tranziţiei 11 de la instanţa crmd cu cheia 2668bbeb-06d5-40f9-936d-24cb7f87006a. Această informaţie poate fi utilă pentru localizarea secţiunii relevante din loguri când căutaţi sursa unei defecţiuni." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ch-Status.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Ch-Stonith.po b/doc/Pacemaker_Explained/ro-RO/Ch-Stonith.po new file mode 100644 index 0000000000..2be2bc1787 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Ch-Stonith.po @@ -0,0 +1,301 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-11-03 01:16+0100\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Ch-Stonith.xml:2(title) +msgid "Protecting Your Data - STONITH" +msgstr "Protejarea Datelor Voastre - STONITH" + +#: Ch-Stonith.xml:4(title) +msgid "Why You Need STONITH" +msgstr "De Ce Aveţi Nevoie De STONITH" + +#: Ch-Stonith.xml:5(para) +msgid "STONITH is an acronym for Shoot-The-Other-Node-In-The-Head and it protects your data from being corrupted by rogue nodes or concurrent access." +msgstr "STONITH este un acronim pentru Shoot-The-Other-Node-In-The-Head şi protejează datele voastre de la a fi corupte de către noduri pribege sau de la acces simultan." + +#: Ch-Stonith.xml:6(para) +msgid "Just because a node is unresponsive, this doesn't mean it isn't accessing your data. The only way to be 100% sure that your data is safe, is to use STONITH so we can be certain that the node is truly offline, before allowing the data to be accessed from another node." +msgstr "Doar pentru că un nod nu mai răspunde, acest lucru nu înseamnă că acesta nu mai accesează datele voastre. Singura metodă de a fi 100% siguri că datele voastre sunt în siguranţă, este să folosiţi STONITH pentru a putea fi siguri că nodul este cu adevărat offline, înainte de a permite datelor să fie accesate de pe alt nod." + +#: Ch-Stonith.xml:10(para) +msgid "STONITH also has a role to play in the event that a clustered service cannot be stopped. In this case, the cluster uses STONITH to force the whole node offline, thereby making it safe to start the service elsewhere." +msgstr "STONITH mai are un rol pe care îl joacă în cazul în care un serviciu de pe cluster nu poate fi oprit. În acest caz, clusterul foloseşte STONITH pentru a forţa întregul nod offline, astfel făcând să fie sigurâ pornirea serviciului în altă parte." + +#: Ch-Stonith.xml:16(title) +msgid "What STONITH Device Should You Use" +msgstr "Ce Dispozitiv STONITH Ar Trebui Să Folosiţi" + +#: Ch-Stonith.xml:17(para) +msgid "It is crucial that the STONITH device can allow the cluster to differentiate between a node failure and a network one." +msgstr "Este imperativ ca dispozitivul STONITH să permită clusterului să facă diferenţa între o defecţiune a nodului şi una a reţelei." + +#: Ch-Stonith.xml:18(para) +msgid "The biggest mistake people make in choosing a STONITH device is to use remote power switch (such as many on-board IMPI controllers) that shares power with the node it controls. In such cases, the cluster cannot be sure if the node is really offline, or active and suffering from a network fault." +msgstr "Cea mai mare greşeală pe care o fac oamenii în alegerea unui dispozitiv STONITH este să folosească un switch de curent cu acces la distanţă (cum ar fi multe controlere IPMI integrate) care partajează curentul cu nodul pe care îl controlează. În astfel de cazuri, clusterul nu poate fi sigur dacă nodul este cu adevărat offline sau inactiv şi suferă din cauza unei probleme de reţea." + +#: Ch-Stonith.xml:22(para) +msgid "Likewise, any device that relies on the machine being active (such as SSH-based \"devices\" used during testing) are inappropriate." +msgstr "În mod similar, orice dispozitiv care se bazează pe maşină să fie activă (cum ar fi \"dispozitivele\" bazate pe SSH folosite în timpul testării) sunt nepotrivite." + +#: Ch-Stonith.xml:25(title) +msgid "Configuring STONITH" +msgstr "Configurarea STONITH" + +#: Ch-Stonith.xml:28(para) +msgid "Find the correct driver: stonith_admin --list-installed" +msgstr "Găsiţi driverul corect: stonith_admin --list-installed" + +#: Ch-Stonith.xml:31(para) +msgid "Since every device is different, the parameters needed to configure it will vary. To find out the parameters associated with the device, run:" +msgstr "Din moment ce fiecare dispozitiv este diferit, parametrii necesari să îl configureze vor varia. Pentru a afla parametrii asociaţi dispozitivului, rulaţi:" + +#: Ch-Stonith.xml:33(replaceable) +msgid "type" +msgstr "type" + +#: Ch-Stonith.xml:33(command) +msgid "stonith_admin --metadata --agent " +msgstr "stonith_admin --metadata --agent " + +#: Ch-Stonith.xml:35(para) +msgid "The output should be XML formatted text containing additional parameter descriptions. We will endeavour to make the output more friendly in a later version." +msgstr "Rezultatul de ieşire ar trebui să fie un text formatat XML conţinând descrierile parametrilor adiţionali. Ne vom aventura să facem rezultatul de ieşire mai prietenos într-o versiune ulterioară." + +#: Ch-Stonith.xml:39(para) +msgid "Create a file called stonith.xml containing a primitive resource with a class of stonith, a type of type and a parameter for each of the values returned in step 2" +msgstr "Creaţi un fişier numit stonith.xml conţinând o resursă primitivă cu o clasă de stonith, un tip de type şi un parametru pentru fiecare dintre valorile returnate la pasul 2" + +#: Ch-Stonith.xml:44(para) +msgid "If the device does not know how to fence nodes based on their uname, you may also need to set the special pcmk_host_map parameter. See man stonithd for details." +msgstr "Dacă dispozitivul nu ştie să evacueze noduri pe baza uname-ului acestora, ar putea fi nevoie să setaţi parametrul special pcmk_host_map. Vedeţi man stonithd pentru detalii." + +#: Ch-Stonith.xml:49(para) +msgid "If the device does not support the list command, you may also need to set the special pcmk_host_list and/or pcmk_host_check parameters. See man stonithd for details." +msgstr "Dacă dispozitivul nu suportă comanda list, ar putea fi nevoie să setaţi parametrii speciali pcmk_host_list şi/sau pcmk_host_check. Vedeţi man stonithd pentru detalii." + +#: Ch-Stonith.xml:55(para) +msgid "If the device does not expect the victim to be specified with the port parameter, you may also need to set the special pcmk_host_argument parameter. See man stonithd for details." +msgstr "Dacă dispozitivul nu se aşteaptă ca victima să fie specificată cu parametrul port, ar putea fi nevoie să setaţi parametrul special pcmk_host_argument. Vedeţi man stonithd pentru detalii." + +#: Ch-Stonith.xml:61(para) +msgid "Upload it into the CIB using cibadmin: cibadmin -C -o resources --xml-file stonith.xml" +msgstr "Încărcaţi-l în CIB folosind cibadmin: cibadmin -C -o resources --xml-file stonith.xml" + +#: Ch-Stonith.xml:65(para) +msgid "Once the stonith resource is running, you can test it by executing: stonith_admin --reboot nodename. Although you might want to stop the cluster on that machine first." +msgstr "Odată ce resursa stonith rulează, o puteţi testa executând: stonith_admin --reboot nodename. Deşi aţi putea dori să opriţi clusterul pe acea maşină mai întâi." + +#: Ch-Stonith.xml:71(title) +msgid "Example" +msgstr "Exemplu" + +#: Ch-Stonith.xml:72(para) +msgid "Assuming we have an chassis containing four nodes and an IPMI device active on 10.0.0.1, then we would chose the fence_ipmilan driver in step 2 and obtain the following list of parameters" +msgstr "Presupunând că avem un şasiu conţinând patru noduri şi un dispozitiv IPMI activ pe 10.0.0.1, atunci am alege driverul fence_ipmilan la pasul 2 şi am obţine următoarea listă de parametri" + +#: Ch-Stonith.xml:76(title) +msgid "Obtaining a list of STONITH Parameters" +msgstr "Obţinerea unei liste de Parametri STONITH" + +#: Ch-Stonith.xml:77(programlisting) +#, no-wrap +msgid "" +"\n" +"# stonith_admin --metadata -a fence_ipmilan\n" +"\n" +"<?xml version=\"1.0\" ?>\n" +"<resource-agent name=\"fence_ipmilan\" shortdesc=\"Fence agent for IPMI over LAN\">\n" +"<longdesc>\n" +"fence_ipmilan is an I/O Fencing agent which can be used with machines controlled by IPMI. This agent calls support software using ipmitool (http://ipmitool.sf.net/).\n" +"\n" +"To use fence_ipmilan with HP iLO 3 you have to enable lanplus option (lanplus / -P) and increase wait after operation to 4 seconds (power_wait=4 / -T 4)</longdesc>\n" +"<parameters>\n" +"\t<parameter name=\"auth\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-A\" />\n" +"\t\t<content type=\"string\" />\n" +"\t\t<shortdesc lang=\"en\">IPMI Lan Auth type (md5, password, or none)</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"ipaddr\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-a\" />\n" +"\t\t<content type=\"string\" />\n" +"\t\t<shortdesc lang=\"en\">IPMI Lan IP to talk to</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"passwd\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-p\" />\n" +"\t\t<content type=\"string\" />\n" +"\t\t<shortdesc lang=\"en\">Password (if required) to control power on IPMI device</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"passwd_script\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-S\" />\n" +"\t\t<content type=\"string\" />\n" +"\t\t<shortdesc lang=\"en\">Script to retrieve password (if required)</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"lanplus\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-P\" />\n" +"\t\t<content type=\"boolean\" />\n" +"\t\t<shortdesc lang=\"en\">Use Lanplus</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"login\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-l\" />\n" +"\t\t<content type=\"string\" />\n" +"\t\t<shortdesc lang=\"en\">Username/Login (if required) to control power on IPMI device</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"action\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-o\" />\n" +"\t\t<content type=\"string\" default=\"reboot\"/>\n" +"\t\t<shortdesc lang=\"en\">Operation to perform. Valid operations: on, off, reboot, status, list, diag, monitor or metadata</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"timeout\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-t\" />\n" +"\t\t<content type=\"string\" />\n" +"\t\t<shortdesc lang=\"en\">Timeout (sec) for IPMI operation</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"cipher\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-C\" />\n" +"\t\t<content type=\"string\" />\n" +"\t\t<shortdesc lang=\"en\">Ciphersuite to use (same as ipmitool -C parameter)</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"method\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-M\" />\n" +"\t\t<content type=\"string\" default=\"onoff\"/>\n" +"\t\t<shortdesc lang=\"en\">Method to fence (onoff or cycle)</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"power_wait\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-T\" />\n" +"\t\t<content type=\"string\" default=\"2\"/>\n" +"\t\t<shortdesc lang=\"en\">Wait X seconds after on/off operation</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"delay\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-f\" />\n" +"\t\t<content type=\"string\" />\n" +"\t\t<shortdesc lang=\"en\">Wait X seconds before fencing is started</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"verbose\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-v\" />\n" +"\t\t<content type=\"boolean\" />\n" +"\t\t<shortdesc lang=\"en\">Verbose mode</shortdesc>\n" +"\t</parameter>\n" +"</parameters>\n" +"<actions>\n" +"\t<action name=\"on\" />\n" +"\t<action name=\"off\" />\n" +"\t<action name=\"reboot\" />\n" +"\t<action name=\"status\" />\n" +"\t<action name=\"diag\" />\n" +"\t<action name=\"list\" />\n" +"\t<action name=\"monitor\" />\n" +"\t<action name=\"metadata\" />\n" +"</actions>\n" +"</resource-agent>\n" +msgstr "" +"\n" +"# stonith_admin --metadata -a fence_ipmilan\n" +"\n" +"<?xml version=\"1.0\" ?>\n" +"<resource-agent name=\"fence_ipmilan\" shortdesc=\"Fence agent for IPMI over LAN\">\n" +"<longdesc>\n" +"fence_ipmilan is an I/O Fencing agent which can be used with machines controlled by IPMI. This agent calls support software using ipmitool (http://ipmitool.sf.net/).\n" +"\n" +"To use fence_ipmilan with HP iLO 3 you have to enable lanplus option (lanplus / -P) and increase wait after operation to 4 seconds (power_wait=4 / -T 4)</longdesc>\n" +"<parameters>\n" +"\t<parameter name=\"auth\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-A\" />\n" +"\t\t<content type=\"string\" />\n" +"\t\t<shortdesc lang=\"en\">IPMI Lan Auth type (md5, password, or none)</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"ipaddr\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-a\" />\n" +"\t\t<content type=\"string\" />\n" +"\t\t<shortdesc lang=\"en\">IPMI Lan IP to talk to</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"passwd\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-p\" />\n" +"\t\t<content type=\"string\" />\n" +"\t\t<shortdesc lang=\"en\">Password (if required) to control power on IPMI device</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"passwd_script\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-S\" />\n" +"\t\t<content type=\"string\" />\n" +"\t\t<shortdesc lang=\"en\">Script to retrieve password (if required)</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"lanplus\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-P\" />\n" +"\t\t<content type=\"boolean\" />\n" +"\t\t<shortdesc lang=\"en\">Use Lanplus</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"login\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-l\" />\n" +"\t\t<content type=\"string\" />\n" +"\t\t<shortdesc lang=\"en\">Username/Login (if required) to control power on IPMI device</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"action\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-o\" />\n" +"\t\t<content type=\"string\" default=\"reboot\"/>\n" +"\t\t<shortdesc lang=\"en\">Operation to perform. Valid operations: on, off, reboot, status, list, diag, monitor or metadata</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"timeout\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-t\" />\n" +"\t\t<content type=\"string\" />\n" +"\t\t<shortdesc lang=\"en\">Timeout (sec) for IPMI operation</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"cipher\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-C\" />\n" +"\t\t<content type=\"string\" />\n" +"\t\t<shortdesc lang=\"en\">Ciphersuite to use (same as ipmitool -C parameter)</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"method\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-M\" />\n" +"\t\t<content type=\"string\" default=\"onoff\"/>\n" +"\t\t<shortdesc lang=\"en\">Method to fence (onoff or cycle)</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"power_wait\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-T\" />\n" +"\t\t<content type=\"string\" default=\"2\"/>\n" +"\t\t<shortdesc lang=\"en\">Wait X seconds after on/off operation</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"delay\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-f\" />\n" +"\t\t<content type=\"string\" />\n" +"\t\t<shortdesc lang=\"en\">Wait X seconds before fencing is started</shortdesc>\n" +"\t</parameter>\n" +"\t<parameter name=\"verbose\" unique=\"1\">\n" +"\t\t<getopt mixed=\"-v\" />\n" +"\t\t<content type=\"boolean\" />\n" +"\t\t<shortdesc lang=\"en\">Verbose mode</shortdesc>\n" +"\t</parameter>\n" +"</parameters>\n" +"<actions>\n" +"\t<action name=\"on\" />\n" +"\t<action name=\"off\" />\n" +"\t<action name=\"reboot\" />\n" +"\t<action name=\"status\" />\n" +"\t<action name=\"diag\" />\n" +"\t<action name=\"list\" />\n" +"\t<action name=\"monitor\" />\n" +"\t<action name=\"metadata\" />\n" +"</actions>\n" +"</resource-agent>\n" + +#: Ch-Stonith.xml:166(para) +msgid "from which we would create a STONITH resource fragment that might look like this" +msgstr "din care am crea un fragment de resursă STONITH care ar putea arăta aşa" + +#: Ch-Stonith.xml:168(title) +msgid "Sample STONITH Resource" +msgstr "Exemplu de Resursă STONITH" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Ch-Stonith.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Pacemaker_Explained.po b/doc/Pacemaker_Explained/ro-RO/Pacemaker_Explained.po new file mode 100644 index 0000000000..6f1b056cb9 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Pacemaker_Explained.po @@ -0,0 +1,54 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-11-03 01:17+0100\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Pacemaker_Explained.xml:15(title) +msgid "Receiving Notification of Cluster Events" +msgstr "Primirea de Notificări ale Evenimentelor Clusterului" + +#: Pacemaker_Explained.xml:16(title) +msgid "Configuring Email Notifications" +msgstr "Configurarea de Notificări pe Email" + +#: Pacemaker_Explained.xml:17(title) +msgid "Configuring SNMP Notifications" +msgstr "Configurarea de Notificări pe SNMP" + +#: Pacemaker_Explained.xml:34(title) +msgid "Further Reading" +msgstr "Documentaţie Adiţională" + +#: Pacemaker_Explained.xml:36(para) +msgid "Project Website: and Documentation " +msgstr "Site-ul Proiectului: şi Documentaţia " + +#: Pacemaker_Explained.xml:38(para) +msgid "Cluster Commands" +msgstr "Comenzile Clusterului" + +#: Pacemaker_Explained.xml:39(para) +msgid "A comprehensive guide to cluster commands has been written by Novell and can be found at: " +msgstr "Un ghid comprehensiv al comenzilor clusterului a fost scris de Novell şi poate fi găsit la: " + +#: Pacemaker_Explained.xml:41(para) +msgid "Heartbeat configuration: " +msgstr "Configuraţia Heartbeat: " + +#: Pacemaker_Explained.xml:42(para) +msgid "Corosync Configuration: " +msgstr "Configuraţia Corosync: " + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Pacemaker_Explained.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Preface.po b/doc/Pacemaker_Explained/ro-RO/Preface.po new file mode 100644 index 0000000000..8e3cdcf496 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Preface.po @@ -0,0 +1,22 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-16 07:12+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Preface.xml:4(title) +msgid "Preface" +msgstr "Prefaţă" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Preface.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/Revision_History.po b/doc/Pacemaker_Explained/ro-RO/Revision_History.po new file mode 100644 index 0000000000..0f65c5ba1b --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/Revision_History.po @@ -0,0 +1,84 @@ +msgid "" +msgstr "" +"Project-Id-Version: Pacemaker 1.1\n" +"POT-Creation-Date: 2011-09-24 23:25+0300\n" +"PO-Revision-Date: 2011-10-16 07:25+0200\n" +"Last-Translator: Dan Frîncu \n" +"Language-Team: Dan Frîncu \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Romanian\n" +"X-Poedit-Country: ROMANIA\n" + +#: Revision_History.xml:5(title) +msgid "Revision History" +msgstr "Istoricul Reviziilor" + +#: Revision_History.xml:9(revnumber) +msgid "1" +msgstr "1" + +#: Revision_History.xml:10(date) +msgid "19 Oct 2009" +msgstr "19 Oct 2009" + +#: Revision_History.xml:11(firstname) +#: Revision_History.xml:17(firstname) +#: Revision_History.xml:23(firstname) +msgid "Andrew" +msgstr "Andrew" + +#: Revision_History.xml:11(surname) +#: Revision_History.xml:17(surname) +#: Revision_History.xml:23(surname) +msgid "Beekhof" +msgstr "Beekhof" + +#: Revision_History.xml:11(email) +#: Revision_History.xml:17(email) +#: Revision_History.xml:23(email) +msgid "andrew@beekhof.net" +msgstr "andrew@beekhof.net" + +#: Revision_History.xml:12(member) +msgid "Import from Pages.app" +msgstr "Import din Pages.app" + +#: Revision_History.xml:15(revnumber) +msgid "2" +msgstr "2" + +#: Revision_History.xml:16(date) +msgid "26 Oct 2009" +msgstr "26 Oct 2009" + +#: Revision_History.xml:18(member) +msgid "Cleanup and reformatting of docbook xml complete" +msgstr "Curăţarea şi reformatarea xml-ului pentru docbook terminată" + +#: Revision_History.xml:21(revnumber) +msgid "3" +msgstr "3" + +#: Revision_History.xml:22(date) +msgid "Tue Nov 12 2009" +msgstr "Tue Nov 12 2009" + +#: Revision_History.xml:26(member) +msgid "Split book into chapters and pass validation" +msgstr "Împărţirea cărţii în capitole şi trecerea validării" + +#: Revision_History.xml:27(ulink) +msgid "Publican" +msgstr "Publican" + +#: Revision_History.xml:27(member) +msgid "Re-organize book for use with " +msgstr "Reorganizarea cărţii pentru folosirea cu " + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2 +#: Revision_History.xml:0(None) +msgid "translator-credits" +msgstr "genericul-traducătorului" + diff --git a/doc/Pacemaker_Explained/ro-RO/images/Policy-Engine-big.dot b/doc/Pacemaker_Explained/ro-RO/images/Policy-Engine-big.dot new file mode 100644 index 0000000000..40ced22ccc --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/images/Policy-Engine-big.dot @@ -0,0 +1,83 @@ +digraph "g" { +"Cancel drbd0:0_monitor_10000 frigg" -> "drbd0:0_demote_0 frigg" [ style = bold] +"Cancel drbd0:0_monitor_10000 frigg" [ style=bold color="green" fontcolor="black" ] +"Cancel drbd0:1_monitor_12000 odin" -> "drbd0:1_promote_0 odin" [ style = bold] +"Cancel drbd0:1_monitor_12000 odin" [ style=bold color="green" fontcolor="black" ] +"IPaddr0_monitor_5000 odin" [ style=bold color="green" fontcolor="black" ] +"IPaddr0_start_0 odin" -> "IPaddr0_monitor_5000 odin" [ style = bold] +"IPaddr0_start_0 odin" -> "MailTo_start_0 odin" [ style = bold] +"IPaddr0_start_0 odin" -> "group_running_0" [ style = bold] +"IPaddr0_start_0 odin" [ style=bold color="green" fontcolor="black" ] +"MailTo_start_0 odin" -> "group_running_0" [ style = bold] +"MailTo_start_0 odin" [ style=bold color="green" fontcolor="black" ] +"drbd0:0_demote_0 frigg" -> "drbd0:0_monitor_12000 frigg" [ style = bold] +"drbd0:0_demote_0 frigg" -> "ms_drbd_demoted_0" [ style = bold] +"drbd0:0_demote_0 frigg" [ style=bold color="green" fontcolor="black" ] +"drbd0:0_monitor_12000 frigg" [ style=bold color="green" fontcolor="black" ] +"drbd0:0_post_notify_demote_0 frigg" -> "ms_drbd_confirmed-post_notify_demoted_0" [ style = bold] +"drbd0:0_post_notify_demote_0 frigg" [ style=bold color="green" fontcolor="black" ] +"drbd0:0_post_notify_promote_0 frigg" -> "ms_drbd_confirmed-post_notify_promoted_0" [ style = bold] +"drbd0:0_post_notify_promote_0 frigg" [ style=bold color="green" fontcolor="black" ] +"drbd0:0_pre_notify_demote_0 frigg" -> "ms_drbd_confirmed-pre_notify_demote_0" [ style = bold] +"drbd0:0_pre_notify_demote_0 frigg" [ style=bold color="green" fontcolor="black" ] +"drbd0:0_pre_notify_promote_0 frigg" -> "ms_drbd_confirmed-pre_notify_promote_0" [ style = bold] +"drbd0:0_pre_notify_promote_0 frigg" [ style=bold color="green" fontcolor="black" ] +"drbd0:1_monitor_10000 odin" [ style=bold color="green" fontcolor="black" ] +"drbd0:1_post_notify_demote_0 odin" -> "ms_drbd_confirmed-post_notify_demoted_0" [ style = bold] +"drbd0:1_post_notify_demote_0 odin" [ style=bold color="green" fontcolor="black" ] +"drbd0:1_post_notify_promote_0 odin" -> "ms_drbd_confirmed-post_notify_promoted_0" [ style = bold] +"drbd0:1_post_notify_promote_0 odin" [ style=bold color="green" fontcolor="black" ] +"drbd0:1_pre_notify_demote_0 odin" -> "ms_drbd_confirmed-pre_notify_demote_0" [ style = bold] +"drbd0:1_pre_notify_demote_0 odin" [ style=bold color="green" fontcolor="black" ] +"drbd0:1_pre_notify_promote_0 odin" -> "ms_drbd_confirmed-pre_notify_promote_0" [ style = bold] +"drbd0:1_pre_notify_promote_0 odin" [ style=bold color="green" fontcolor="black" ] +"drbd0:1_promote_0 odin" -> "drbd0:1_monitor_10000 odin" [ style = bold] +"drbd0:1_promote_0 odin" -> "ms_drbd_promoted_0" [ style = bold] +"drbd0:1_promote_0 odin" [ style=bold color="green" fontcolor="black" ] +"group_running_0" [ style=bold color="green" fontcolor="orange" ] +"group_start_0" -> "IPaddr0_start_0 odin" [ style = bold] +"group_start_0" -> "MailTo_start_0 odin" [ style = bold] +"group_start_0" -> "group_running_0" [ style = bold] +"group_start_0" [ style=bold color="green" fontcolor="orange" ] +"ms_drbd_confirmed-post_notify_demoted_0" -> "drbd0:0_monitor_12000 frigg" [ style = bold] +"ms_drbd_confirmed-post_notify_demoted_0" -> "drbd0:1_monitor_10000 odin" [ style = bold] +"ms_drbd_confirmed-post_notify_demoted_0" -> "ms_drbd_pre_notify_promote_0" [ style = bold] +"ms_drbd_confirmed-post_notify_demoted_0" [ style=bold color="green" fontcolor="orange" ] +"ms_drbd_confirmed-post_notify_promoted_0" -> "drbd0:0_monitor_12000 frigg" [ style = bold] +"ms_drbd_confirmed-post_notify_promoted_0" -> "drbd0:1_monitor_10000 odin" [ style = bold] +"ms_drbd_confirmed-post_notify_promoted_0" -> "group_start_0" [ style = bold] +"ms_drbd_confirmed-post_notify_promoted_0" [ style=bold color="green" fontcolor="orange" ] +"ms_drbd_confirmed-pre_notify_demote_0" -> "ms_drbd_demote_0" [ style = bold] +"ms_drbd_confirmed-pre_notify_demote_0" -> "ms_drbd_post_notify_demoted_0" [ style = bold] +"ms_drbd_confirmed-pre_notify_demote_0" [ style=bold color="green" fontcolor="orange" ] +"ms_drbd_confirmed-pre_notify_promote_0" -> "ms_drbd_post_notify_promoted_0" [ style = bold] +"ms_drbd_confirmed-pre_notify_promote_0" -> "ms_drbd_promote_0" [ style = bold] +"ms_drbd_confirmed-pre_notify_promote_0" [ style=bold color="green" fontcolor="orange" ] +"ms_drbd_demote_0" -> "drbd0:0_demote_0 frigg" [ style = bold] +"ms_drbd_demote_0" -> "ms_drbd_demoted_0" [ style = bold] +"ms_drbd_demote_0" [ style=bold color="green" fontcolor="orange" ] +"ms_drbd_demoted_0" -> "ms_drbd_post_notify_demoted_0" [ style = bold] +"ms_drbd_demoted_0" -> "ms_drbd_promote_0" [ style = bold] +"ms_drbd_demoted_0" [ style=bold color="green" fontcolor="orange" ] +"ms_drbd_post_notify_demoted_0" -> "drbd0:0_post_notify_demote_0 frigg" [ style = bold] +"ms_drbd_post_notify_demoted_0" -> "drbd0:1_post_notify_demote_0 odin" [ style = bold] +"ms_drbd_post_notify_demoted_0" -> "ms_drbd_confirmed-post_notify_demoted_0" [ style = bold] +"ms_drbd_post_notify_demoted_0" [ style=bold color="green" fontcolor="orange" ] +"ms_drbd_post_notify_promoted_0" -> "drbd0:0_post_notify_promote_0 frigg" [ style = bold] +"ms_drbd_post_notify_promoted_0" -> "drbd0:1_post_notify_promote_0 odin" [ style = bold] +"ms_drbd_post_notify_promoted_0" -> "ms_drbd_confirmed-post_notify_promoted_0" [ style = bold] +"ms_drbd_post_notify_promoted_0" [ style=bold color="green" fontcolor="orange" ] +"ms_drbd_pre_notify_demote_0" -> "drbd0:0_pre_notify_demote_0 frigg" [ style = bold] +"ms_drbd_pre_notify_demote_0" -> "drbd0:1_pre_notify_demote_0 odin" [ style = bold] +"ms_drbd_pre_notify_demote_0" -> "ms_drbd_confirmed-pre_notify_demote_0" [ style = bold] +"ms_drbd_pre_notify_demote_0" [ style=bold color="green" fontcolor="orange" ] +"ms_drbd_pre_notify_promote_0" -> "drbd0:0_pre_notify_promote_0 frigg" [ style = bold] +"ms_drbd_pre_notify_promote_0" -> "drbd0:1_pre_notify_promote_0 odin" [ style = bold] +"ms_drbd_pre_notify_promote_0" -> "ms_drbd_confirmed-pre_notify_promote_0" [ style = bold] +"ms_drbd_pre_notify_promote_0" [ style=bold color="green" fontcolor="orange" ] +"ms_drbd_promote_0" -> "drbd0:1_promote_0 odin" [ style = bold] +"ms_drbd_promote_0" [ style=bold color="green" fontcolor="orange" ] +"ms_drbd_promoted_0" -> "group_start_0" [ style = bold] +"ms_drbd_promoted_0" -> "ms_drbd_post_notify_promoted_0" [ style = bold] +"ms_drbd_promoted_0" [ style=bold color="green" fontcolor="orange" ] +} diff --git a/doc/Pacemaker_Explained/ro-RO/images/Policy-Engine-big.svg b/doc/Pacemaker_Explained/ro-RO/images/Policy-Engine-big.svg new file mode 100644 index 0000000000..7964fcfd30 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/images/Policy-Engine-big.svg @@ -0,0 +1,418 @@ + + + + + + +g + + +Cancel drbd0:0_monitor_10000 frigg + +Cancel drbd0:0_monitor_10000 frigg + + +drbd0:0_demote_0 frigg + +drbd0:0_demote_0 frigg + + +Cancel drbd0:0_monitor_10000 frigg->drbd0:0_demote_0 frigg + + + + +drbd0:0_monitor_12000 frigg + +drbd0:0_monitor_12000 frigg + + +drbd0:0_demote_0 frigg->drbd0:0_monitor_12000 frigg + + + + +ms_drbd_demoted_0 + +ms_drbd_demoted_0 + + +drbd0:0_demote_0 frigg->ms_drbd_demoted_0 + + + + +Cancel drbd0:1_monitor_12000 odin + +Cancel drbd0:1_monitor_12000 odin + + +drbd0:1_promote_0 odin + +drbd0:1_promote_0 odin + + +Cancel drbd0:1_monitor_12000 odin->drbd0:1_promote_0 odin + + + + +drbd0:1_monitor_10000 odin + +drbd0:1_monitor_10000 odin + + +drbd0:1_promote_0 odin->drbd0:1_monitor_10000 odin + + + + +ms_drbd_promoted_0 + +ms_drbd_promoted_0 + + +drbd0:1_promote_0 odin->ms_drbd_promoted_0 + + + + +IPaddr0_monitor_5000 odin + +IPaddr0_monitor_5000 odin + + +IPaddr0_start_0 odin + +IPaddr0_start_0 odin + + +IPaddr0_start_0 odin->IPaddr0_monitor_5000 odin + + + + +MailTo_start_0 odin + +MailTo_start_0 odin + + +IPaddr0_start_0 odin->MailTo_start_0 odin + + + + +group_running_0 + +group_running_0 + + +IPaddr0_start_0 odin->group_running_0 + + + + +MailTo_start_0 odin->group_running_0 + + + + +ms_drbd_post_notify_demoted_0 + +ms_drbd_post_notify_demoted_0 + + +ms_drbd_demoted_0->ms_drbd_post_notify_demoted_0 + + + + +ms_drbd_promote_0 + +ms_drbd_promote_0 + + +ms_drbd_demoted_0->ms_drbd_promote_0 + + + + +drbd0:0_post_notify_demote_0 frigg + +drbd0:0_post_notify_demote_0 frigg + + +ms_drbd_confirmed-post_notify_demoted_0 + +ms_drbd_confirmed-post_notify_demoted_0 + + +drbd0:0_post_notify_demote_0 frigg->ms_drbd_confirmed-post_notify_demoted_0 + + + + +ms_drbd_confirmed-post_notify_demoted_0->drbd0:0_monitor_12000 frigg + + + + +ms_drbd_confirmed-post_notify_demoted_0->drbd0:1_monitor_10000 odin + + + + +ms_drbd_pre_notify_promote_0 + +ms_drbd_pre_notify_promote_0 + + +ms_drbd_confirmed-post_notify_demoted_0->ms_drbd_pre_notify_promote_0 + + + + +drbd0:0_post_notify_promote_0 frigg + +drbd0:0_post_notify_promote_0 frigg + + +ms_drbd_confirmed-post_notify_promoted_0 + +ms_drbd_confirmed-post_notify_promoted_0 + + +drbd0:0_post_notify_promote_0 frigg->ms_drbd_confirmed-post_notify_promoted_0 + + + + +ms_drbd_confirmed-post_notify_promoted_0->drbd0:0_monitor_12000 frigg + + + + +ms_drbd_confirmed-post_notify_promoted_0->drbd0:1_monitor_10000 odin + + + + +group_start_0 + +group_start_0 + + +ms_drbd_confirmed-post_notify_promoted_0->group_start_0 + + + + +drbd0:0_pre_notify_demote_0 frigg + +drbd0:0_pre_notify_demote_0 frigg + + +ms_drbd_confirmed-pre_notify_demote_0 + +ms_drbd_confirmed-pre_notify_demote_0 + + +drbd0:0_pre_notify_demote_0 frigg->ms_drbd_confirmed-pre_notify_demote_0 + + + + +ms_drbd_demote_0 + +ms_drbd_demote_0 + + +ms_drbd_confirmed-pre_notify_demote_0->ms_drbd_demote_0 + + + + +ms_drbd_confirmed-pre_notify_demote_0->ms_drbd_post_notify_demoted_0 + + + + +drbd0:0_pre_notify_promote_0 frigg + +drbd0:0_pre_notify_promote_0 frigg + + +ms_drbd_confirmed-pre_notify_promote_0 + +ms_drbd_confirmed-pre_notify_promote_0 + + +drbd0:0_pre_notify_promote_0 frigg->ms_drbd_confirmed-pre_notify_promote_0 + + + + +ms_drbd_post_notify_promoted_0 + +ms_drbd_post_notify_promoted_0 + + +ms_drbd_confirmed-pre_notify_promote_0->ms_drbd_post_notify_promoted_0 + + + + +ms_drbd_confirmed-pre_notify_promote_0->ms_drbd_promote_0 + + + + +drbd0:1_post_notify_demote_0 odin + +drbd0:1_post_notify_demote_0 odin + + +drbd0:1_post_notify_demote_0 odin->ms_drbd_confirmed-post_notify_demoted_0 + + + + +drbd0:1_post_notify_promote_0 odin + +drbd0:1_post_notify_promote_0 odin + + +drbd0:1_post_notify_promote_0 odin->ms_drbd_confirmed-post_notify_promoted_0 + + + + +drbd0:1_pre_notify_demote_0 odin + +drbd0:1_pre_notify_demote_0 odin + + +drbd0:1_pre_notify_demote_0 odin->ms_drbd_confirmed-pre_notify_demote_0 + + + + +drbd0:1_pre_notify_promote_0 odin + +drbd0:1_pre_notify_promote_0 odin + + +drbd0:1_pre_notify_promote_0 odin->ms_drbd_confirmed-pre_notify_promote_0 + + + + +ms_drbd_promoted_0->group_start_0 + + + + +ms_drbd_promoted_0->ms_drbd_post_notify_promoted_0 + + + + +group_start_0->IPaddr0_start_0 odin + + + + +group_start_0->MailTo_start_0 odin + + + + +group_start_0->group_running_0 + + + + +ms_drbd_pre_notify_promote_0->drbd0:0_pre_notify_promote_0 frigg + + + + +ms_drbd_pre_notify_promote_0->ms_drbd_confirmed-pre_notify_promote_0 + + + + +ms_drbd_pre_notify_promote_0->drbd0:1_pre_notify_promote_0 odin + + + + +ms_drbd_demote_0->drbd0:0_demote_0 frigg + + + + +ms_drbd_demote_0->ms_drbd_demoted_0 + + + + +ms_drbd_post_notify_demoted_0->drbd0:0_post_notify_demote_0 frigg + + + + +ms_drbd_post_notify_demoted_0->ms_drbd_confirmed-post_notify_demoted_0 + + + + +ms_drbd_post_notify_demoted_0->drbd0:1_post_notify_demote_0 odin + + + + +ms_drbd_post_notify_promoted_0->drbd0:0_post_notify_promote_0 frigg + + + + +ms_drbd_post_notify_promoted_0->ms_drbd_confirmed-post_notify_promoted_0 + + + + +ms_drbd_post_notify_promoted_0->drbd0:1_post_notify_promote_0 odin + + + + +ms_drbd_promote_0->drbd0:1_promote_0 odin + + + + +ms_drbd_pre_notify_demote_0 + +ms_drbd_pre_notify_demote_0 + + +ms_drbd_pre_notify_demote_0->drbd0:0_pre_notify_demote_0 frigg + + + + +ms_drbd_pre_notify_demote_0->ms_drbd_confirmed-pre_notify_demote_0 + + + + +ms_drbd_pre_notify_demote_0->drbd0:1_pre_notify_demote_0 odin + + + + + diff --git a/doc/Pacemaker_Explained/ro-RO/images/Policy-Engine-small.dot b/doc/Pacemaker_Explained/ro-RO/images/Policy-Engine-small.dot new file mode 100644 index 0000000000..3fef81e789 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/images/Policy-Engine-small.dot @@ -0,0 +1,31 @@ + digraph "g" { +"rsc1_monitor_0 pcmk-2" -> "probe_complete pcmk-2" [ style = bold] +"rsc1_monitor_0 pcmk-2" [ style=bold color="green" fontcolor="black" ] +"rsc1_stop_0 pcmk-1" [ style=dashed color="red" fontcolor="black" ] +"rsc1_start_0 pcmk-2" [ style=dashed color="red" fontcolor="black" ] +"rsc1_stop_0 pcmk-1" -> "rsc1_start_0 pcmk-2" [ style = dashed ] +"rsc1_stop_0 pcmk-1" -> "all_stopped" [ style = dashed ] +"probe_complete" -> "rsc1_start_0 pcmk-2" [ style = dashed ] + +"rsc2_monitor_0 pcmk-2" -> "probe_complete pcmk-2" [ style = bold] +"rsc2_monitor_0 pcmk-2" [ style=bold color="green" fontcolor="black" ] +"rsc2_stop_0 pcmk-1" [ style=dashed color="red" fontcolor="black" ] +"rsc2_start_0 pcmk-2" [ style=dashed color="red" fontcolor="black" ] +"rsc2_stop_0 pcmk-1" -> "rsc2_start_0 pcmk-2" [ style = dashed ] +"rsc2_stop_0 pcmk-1" -> "all_stopped" [ style = dashed ] +"probe_complete" -> "rsc2_start_0 pcmk-2" [ style = dashed ] + +"rsc3_monitor_0 pcmk-2" -> "probe_complete pcmk-2" [ style = bold] +"rsc3_monitor_0 pcmk-2" [ style=bold color="green" fontcolor="black" ] +"rsc3_stop_0 pcmk-1" [ style=dashed color="blue" fontcolor="orange" ] +"rsc3_start_0 pcmk-2" [ style=dashed color="blue" fontcolor="black" ] +"rsc3_stop_0 pcmk-1" -> "all_stopped" [ style = dashed ] +"probe_complete" -> "rsc3_start_0 pcmk-2" [ style = dashed ] + +"probe_complete pcmk-2" -> "probe_complete" [ style = bold] +"probe_complete pcmk-2" [ style=bold color="green" fontcolor="black" ] +"probe_complete" [ style=bold color="green" fontcolor="orange" ] + +"all_stopped" [ style=dashed color="red" fontcolor="orange" ] + +} diff --git a/doc/Pacemaker_Explained/ro-RO/images/Policy-Engine-small.svg b/doc/Pacemaker_Explained/ro-RO/images/Policy-Engine-small.svg new file mode 100644 index 0000000000..a020d564f8 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/images/Policy-Engine-small.svg @@ -0,0 +1,133 @@ + + + + + + +g + + +rsc1_monitor_0 pcmk-2 + +rsc1_monitor_0 pcmk-2 + + +probe_complete pcmk-2 + +probe_complete pcmk-2 + + +rsc1_monitor_0 pcmk-2->probe_complete pcmk-2 + + + + +probe_complete + +probe_complete + + +probe_complete pcmk-2->probe_complete + + + + +rsc1_stop_0 pcmk-1 + +rsc1_stop_0 pcmk-1 + + +rsc1_start_0 pcmk-2 + +rsc1_start_0 pcmk-2 + + +rsc1_stop_0 pcmk-1->rsc1_start_0 pcmk-2 + + + + +all_stopped + +all_stopped + + +rsc1_stop_0 pcmk-1->all_stopped + + + + +probe_complete->rsc1_start_0 pcmk-2 + + + + +rsc2_start_0 pcmk-2 + +rsc2_start_0 pcmk-2 + + +probe_complete->rsc2_start_0 pcmk-2 + + + + +rsc3_start_0 pcmk-2 + +rsc3_start_0 pcmk-2 + + +probe_complete->rsc3_start_0 pcmk-2 + + + + +rsc2_monitor_0 pcmk-2 + +rsc2_monitor_0 pcmk-2 + + +rsc2_monitor_0 pcmk-2->probe_complete pcmk-2 + + + + +rsc2_stop_0 pcmk-1 + +rsc2_stop_0 pcmk-1 + + +rsc2_stop_0 pcmk-1->all_stopped + + + + +rsc2_stop_0 pcmk-1->rsc2_start_0 pcmk-2 + + + + +rsc3_monitor_0 pcmk-2 + +rsc3_monitor_0 pcmk-2 + + +rsc3_monitor_0 pcmk-2->probe_complete pcmk-2 + + + + +rsc3_stop_0 pcmk-1 + +rsc3_stop_0 pcmk-1 + + +rsc3_stop_0 pcmk-1->all_stopped + + + + + diff --git a/doc/Pacemaker_Explained/ro-RO/images/pcmk-active-active.svg b/doc/Pacemaker_Explained/ro-RO/images/pcmk-active-active.svg new file mode 100644 index 0000000000..c377cce410 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/images/pcmk-active-active.svg @@ -0,0 +1,1398 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + D'base + + + + + Web Site + + Web Site + + Web Site + + Web Site + + GFS2 + + + + + + + + Host + Host + Host + Host + + Shared Storage + CoroSync + Pacemaker + Active / Active + Hardware + ClusterSoftware + Services + GFS2 + GFS2 + GFS2 + URL + Mail + D'base + URL + Mail + D'base + URL + Mail + D'base + URL + Mail + + + + diff --git a/doc/Pacemaker_Explained/ro-RO/images/pcmk-active-passive.svg b/doc/Pacemaker_Explained/ro-RO/images/pcmk-active-passive.svg new file mode 100644 index 0000000000..2c33fd0db2 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/images/pcmk-active-passive.svg @@ -0,0 +1,1027 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + + + + + + URL + + + Web Site + + + + Files + + Storage + + + + + + Host + Host + Host + Host + CoroSync + Pacemaker + Active / Passive + Hardware + ClusterSoftware + Services + URL + D/base + Storage + D/base + + + + Synch + Synch + + + diff --git a/doc/Pacemaker_Explained/ro-RO/images/pcmk-internals.svg b/doc/Pacemaker_Explained/ro-RO/images/pcmk-internals.svg new file mode 100644 index 0000000000..c2f50044f8 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/images/pcmk-internals.svg @@ -0,0 +1,1158 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + + + Pacemaker Internals + + + + + + crmd + + + stonithd + + cib + + pengine + + lrmd + + cluster abstraction layer + + corosync + + ccm + or + + heartbeat + + + + + + + + + + + + + + linux-ha project + + pacemaker project + + + + diff --git a/doc/Pacemaker_Explained/ro-RO/images/pcmk-overview.svg b/doc/Pacemaker_Explained/ro-RO/images/pcmk-overview.svg new file mode 100644 index 0000000000..9fb022db44 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/images/pcmk-overview.svg @@ -0,0 +1,855 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + + + Pacemaker 10,000ft + + + + + + + + Cluster Resource Manager + + + + + + Local Resource Manager + + + + + Resource Agents + + Messaging & Membership + + + + + + diff --git a/doc/Pacemaker_Explained/ro-RO/images/pcmk-shared-failover.svg b/doc/Pacemaker_Explained/ro-RO/images/pcmk-shared-failover.svg new file mode 100644 index 0000000000..b28d09cea3 --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/images/pcmk-shared-failover.svg @@ -0,0 +1,1306 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + + + + + + URL + + + + Mail + + + + + Files + + + + + Storage + + + + + + Host + Host + Host + Host + CoroSync + Pacemaker + Shared Failover + Hardware + ClusterSoftware + Services + Storage + D'base + Storage + Storage + D'base + URL + URL + Web Site + Files + + + + Synch + Synch + Synch + + + + diff --git a/doc/Pacemaker_Explained/ro-RO/images/pcmk-stack.svg b/doc/Pacemaker_Explained/ro-RO/images/pcmk-stack.svg new file mode 100644 index 0000000000..ac5455799e --- /dev/null +++ b/doc/Pacemaker_Explained/ro-RO/images/pcmk-stack.svg @@ -0,0 +1,909 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + + + + + + + + cLVM2 + + GFS2 + + + OCFS2 + + + + Distributed Lock Manager + + + CoroSync + + + Pacemaker + + Pacemaker Stack + Build Dependancy + + + + + + + + + + + Resource Agents + + + + + + Cluster Glue + + + + + + + + + + +