1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. From the left navigation bar, select Wizards.

3. Expand the individual categories by clicking the arrow down icon next to them and select the desired wizard.

4. Follow the instructions on the screen. After the last configuration step, Verify the values you have entered.

   Hawk2 shows which actions it is going to perform and what the configuration looks like. Depending on the configuration, you might be prompted for the root password before you can Apply the configuration.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. From the left navigation bar, select Add Resource › Primitive.

3. Enter a unique Resource ID.

4. In case a resource template exists on which you want to base the resource configuration, select the respective Template. For details about configuring templates, see Procedure 7.6, “Adding a Resource Template”.

5. Select the resource agent Class you want to use: lsb, ocf, service, stonith, or systemd. For more information, see Section 6.3.2, “Supported Resource Agent Classes”.

6. If you selected ocf as class, specify the Provider of your OCF resource agent. The OCF specification allows multiple vendors to supply the same resource agent.

7. From the Type list, select the resource agent you want to use (for example, IPaddr or Filesystem). A short description for this resource agent is displayed.

   With that, you have specified the resource basics.

   

   Note

   The selection you get in the Type list depends on the Class (and for OCF resources also on the Provider) you have chosen.

   

   Figure 7.3: Hawk2—Primitive Resource #

8. To keep the Parameters, Operations, and Meta Attributes as suggested by Hawk2, click Create to finish the configuration. A message at the top of the screen shows if the action has been successful.

   To adjust the parameters, operations, or meta attributes, refer to Section 7.5.5, “Modifying Resources”. To configure Utilization attributes for the resource, see Procedure 7.21, “Configuring the Capacity a Resource Requires”.

Resource templates are configured like primitive resources.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. From the left navigation bar, select Add Resource › Template.

3. Enter a unique Resource ID.

4. Follow the instructions in Procedure 7.5, “Adding a Primitive Resource”, starting from Step 5.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. On the Hawk2 Status screen, go to the Resources list.

3. In the Operations column, click the arrow down icon next to the resource or group you want to modify and select Edit.

   The resource configuration screen opens.

   

   Figure 7.4: Hawk2—Editing A Primitive Resource #

4. To add a new parameter, operation, or meta attribute, select an entry from the empty drop-down box.

5. To edit any values in the Operations category, click the Edit icon of the respective entry, enter a different value for the operation, and click Apply.

6. When you are finished, click the Apply button in the resource configuration screen to confirm your changes to the parameters, operations, or meta attributes.

   A message at the top of the screen shows if the action has been successful.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. From the left navigation bar, select Add Resource › Primitive.

3. Enter a unique Resource ID.

4. From the Class list, select the resource agent class stonith.

5. From the Type list, select the STONITH plug-in to control your STONITH device. A short description for this plug-in is displayed.

6. Hawk2 automatically shows the required Parameters for the resource. Enter values for each parameter.

7. Hawk2 displays the most important resource Operations and proposes default values. If you do not modify any settings here, Hawk2 adds the proposed operations and their default values when you confirm.

8. If there is no reason to change them, keep the default Meta Attributes settings.

   

   Figure 7.5: Hawk2—STONITH Resource #

9. Confirm your changes to create the STONITH resource.

   A message at the top of the screen shows if the action has been successful.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. From the left navigation bar, select Add Resource › Group.

3. Enter a unique Group ID.

4. To define the group members, select one or multiple entries in the list of Children. Re-sort group members by dragging and dropping them into the order you want by using the “handle” icon on the right.

5. If needed, modify or add Meta Attributes.

6. Click Create to finish the configuration. A message at the top of the screen shows if the action has been successful.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. From the left navigation bar, select Add Resource › Clone.

3. Enter a unique Clone ID.

4. From the Child Resource list, select the primitive or group to use as a sub-resource for the clone.

5. If needed, modify or add Meta Attributes.

6. Click Create to finish the configuration. A message at the top of the screen shows if the action has been successful.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. From the left navigation bar, select Add Resource › Multi-state.

3. Enter a unique Multi-state ID.

4. From the Child Resource list, select the primitive or group to use as a sub-resource for the multi-state resource.

5. If needed, modify or add Meta Attributes.

6. Click Create to finish the configuration. A message at the top of the screen shows if the action has been successful.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. From the left navigation bar, select Add Resource › Tag.

3. Enter a unique Tag ID.

4. From the Objects list, select the resources you want to refer to with the tag.

5. Click Create to finish the configuration. A message at the top of the screen shows if the action has been successful.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. Add a resource as described in Procedure 7.5, “Adding a Primitive Resource” or select an existing primitive to edit.

   Hawk2 automatically shows the most important Operations (start, stop, monitor) and proposes default values.

   To see the attributes belonging to each proposed value, hover the mouse pointer over the respective value.

   

3. To change the suggested timeout values for the start or stop operation:

   1. Click the pen icon next to the operation.

   2. In the dialog that opens, enter a different value for the timeout parameter, for example 10, and confirm your change.

4. To change the suggested interval value for the monitor operation:

   1. Click the pen icon next to the operation.

   2. In the dialog that opens, enter a different value for the monitoring interval.

   3. To configure resource monitoring in the case that the resource is stopped:

      1. Select the role entry from the empty drop-down box below.

      2. From the role drop-down box, select Stopped.

      3. Click Apply to confirm your changes and to close the dialog for the operation.

5. Confirm your changes in the resource configuration screen. A message at the top of the screen shows if the action has been successful.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. From the left navigation bar, select Add Constraint › Location.

3. Enter a unique Constraint ID.

4. From the list of Resources select the resource or resources for which to define the constraint.

5. Enter a Score. The score indicates the value you are assigning to this resource constraint. Positive values indicate the resource can run on the Node you specify in the next step. Negative values mean it should not run on that node. Constraints with higher scores are applied before those with lower scores.

   Some often-used values can also be set via the drop-down box:

   • To force the resources to run on the node, click the arrow icon and select Always. This sets the score to INFINITY.

   • If you never want the resources to run on the node, click the arrow icon and select Never. This sets the score to -INFINITY, meaning that the resources must not run on the node.

   • To set the score to 0, click the arrow icon and select Advisory. This disables the constraint. This is useful when you want to set resource discovery but do not want to constrain the resources.

6. Select a Node.

7. Click Create to finish the configuration. A message at the top of the screen shows if the action has been successful.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. From the left navigation bar, select Add Constraint › Colocation.

3. Enter a unique Constraint ID.

4. Enter a Score. The score determines the location relationship between the resources. Positive values indicate that the resources should run on the same node. Negative values indicate that the resources should not run on the same node. The score will be combined with other factors to decide where to put the resource.

   Some often-used values can also be set via the drop-down box:

   • If you want to force the resources to run on the same node, click the arrow icon and select Always. This sets the score to INFINITY.

   • If you never want the resources to run on the same node, click the arrow icon and select Never. This sets the score to -INFINITY, meaning that the resources must not run on the same node.

5. To define the resources for the constraint:

   1. From the drop-down box in the Resources category, select a resource (or a template).

      The resource is added and a new empty drop-down box appears beneath.

   2. Repeat this step to add more resources.

      As the topmost resource depends on the next resource and so on, the cluster will first decide where to put the last resource, then place the depending ones based on that decision. If the constraint cannot be satisfied, the cluster may not allow the dependent resource to run.

   3. To swap the order of resources within the colocation constraint, click the arrow up icon next to a resource to swap it with the entry above.

6. If needed, specify further parameters for each resource (such as Started, Stopped, Master, Slave, Promote, Demote): Click the empty drop-down box next to the resource and select the desired entry.

7. Click Create to finish the configuration. A message at the top of the screen shows if the action has been successful.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. From the left navigation bar, select Add Constraint › Order.

3. Enter a unique Constraint ID.

4. Enter a Score. If the score is greater than zero, the order constraint is mandatory, otherwise it is optional.

   Some often-used values can also be set via the drop-down box:

   • To make the order constraint mandatory, click the arrow icon and select Mandatory.

   • If you want the order constraint to be a suggestion only, click the arrow icon and select Optional.

   • Serialize: To ensure that no two stop/start actions occur concurrently for the resources, click the arrow icon and select Serialize. This makes sure that one resource must complete starting before the other can be started. A typical use case are resources that put a high load on the host during start-up.

5. For order constraints, you can usually keep the option Symmetrical enabled. This specifies that resources are stopped in reverse order.

6. To define the resources for the constraint:

   1. From the drop-down box in the Resources category, select a resource (or a template).

      The resource is added and a new empty drop-down box appears beneath.

   2. Repeat this step to add more resources.

      The topmost resource will start first, then the second, etc. Usually the resources will be stopped in reverse order.

   3. To swap the order of resources within the order constraint, click the arrow up icon next to a resource to swap it with the entry above.

7. If needed, specify further parameters for each resource (like Started, Stopped, Master, Slave, Promote, Demote): Click the empty drop-down box next to the resource and select the desired entry.

8. Confirm your changes to finish the configuration. A message at the top of the screen shows if the action has been successful.

1. To use a resource set within a location constraint:

   1. Proceed as outlined in Procedure 7.14, “Adding a Location Constraint”, apart from Step 4: Instead of selecting a single resource, select multiple resources by pressing Ctrl or Shift and mouse click. This creates a resource set within the location constraint.

   2. To remove a resource from the location constraint, press Ctrl and click the resource again to deselect it.

2. To use a resource set within a colocation or order constraint:

   1. Proceed as described in Procedure 7.15, “Adding a Colocation Constraint” or Procedure 7.16, “Adding an Order Constraint”, apart from the step where you define the resources for the constraint (Step 5.a or Step 6.a):

   2. Add multiple resources.

   3. To create a resource set, click the chain icon next to a resource to link it to the resource above. A resource set is visualized by a frame around the resources belonging to a set.

   4. You can combine multiple resources in a resource set or create multiple resource sets.

      

      Figure 7.14: Hawk2—Two Resource Sets in a Colocation Constraint #

   5. To unlink a resource from the resource above, click the scissors icon next to the resource.

3. Confirm your changes to finish the constraint configuration.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. Configure a location constraint for the resource as described in Procedure 7.14, “Adding a Location Constraint”.

3. Add the migration-threshold meta attribute to the resource as described in Procedure 7.7: Modifying Parameters, Operations, or Meta Attributes for a Resource, Step 4 and enter a value for the migration-threshold. The value should be positive and less than INFINITY.

4. If you want to automatically expire the failcount for a resource, add the failure-timeout meta attribute to the resource as described in Procedure 7.5: Adding a Primitive Resource, Step 4 and enter a Value for the failure-timeout.

   

5. If you want to specify additional failover nodes with preferences for a resource, create additional location constraints.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. Add the resource-stickiness meta attribute to the resource as described in Procedure 7.7: Modifying Parameters, Operations, or Meta Attributes for a Resource, Step 4.

3. Specify a value between -INFINITY and INFINITY for resource-stickiness.

   

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. In the left navigation bar, select Status.

3. On the Nodes tab, select the node whose capacity you want to configure.

4. In the Operations column, click the arrow down icon and select Edit.

   The Edit Node screen opens.

5. Below Utilization, enter a name for a utilization attribute into the empty drop-down box.

   The name can be arbitrary (for example, RAM_in_GB).

6. Click the Add icon to add the attribute.

7. In the empty text box next to the attribute, enter an attribute value. The value must be an integer.

8. Add as many utilization attributes as you need and add values for all of them.

9. Confirm your changes. A message at the top of the screen shows if the action has been successful.

Configure the capacity a certain resource requires from a node either when creating a primitive resource or when editing an existing primitive resource.

Before you can add utilization attributes to a resource, you need to have set utilization attributes for your cluster nodes as described in Procedure 7.20.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. To add a utilization attribute to an existing resource: Go to Manage › Status and open the resource configuration dialog as described in Section 7.7.1, “Editing Resources and Groups”.

   If you create a new resource: Go to Configuration › Add Resource and proceed as described in Section 7.5.3, “Adding Simple Resources”.

3. In the resource configuration dialog, go to the Utilization category.

4. From the empty drop-down box, select one of the utilization attributes that you have configured for the nodes in Procedure 7.20.

5. In the empty text box next to the attribute, enter an attribute value. The value must be an integer.

6. Add as many utilization attributes as you need and add values for all of them.

7. Confirm your changes. A message at the top of the screen shows if the action has been successful.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. In the left navigation bar, select Cluster Configuration to open the respective screen. It shows global cluster options and resource and operation defaults.

3. From the empty drop-down box in the upper part of the screen, select placement-strategy.

   By default, its value is set to Default, which means that utilization attributes and values are not considered.

4. Depending on your requirements, set Placement Strategy to the appropriate value.

5. Confirm your changes.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. In the left navigation bar, select Status. The list of Resources also shows the Status.

3. Select the resource to start. In its Operations column click the Start icon. To continue, confirm the message that appears.

   When the resource has started, Hawk2 changes the resource's Status to green and shows on which node it is running.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. In the left navigation bar, select Status. The list of Resources also shows the Status.

3. Go to the resource to clean up. In the Operations column click the arrow down button and select Cleanup. To continue, confirm the message that appears.

   This executes the command crm resource cleanup and cleans up the resource on all nodes.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. Clean up the resource on all nodes as described in Procedure 7.24, “Cleaning Up A Resource”.

3. Stop the resource:

   1. In the left navigation bar, select Status. The list of Resources also shows the Status.

   2. In the Operations column click the Stop button next to the resource.

   3. To continue, confirm the message that appears.

      The Status column will reflect the change when the resource is stopped.

4. Delete the resource:

   1. In the left navigation bar, select Edit Configuration.

   2. In the list of Resources, go to the respective resource. From the Operations column click the Delete icon next to the resource.

   3. To continue, confirm the message that appears.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. In the left navigation bar, select Status. The list of Resources also shows the Status.

3. In the list of Resources, select the respective resource.

4. In the Operations column click the arrow down button and select Migrate.

5. In the window that opens you have the following choices:

   • Away from current node: This creates a location constraint with a -INFINITY score for the current node.

   • Alternatively, you can move the resource to another node. This creates a location constraint with an INFINITY score for the destination node.

6. Confirm your choice.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. In the left navigation bar, select Status. The list of Resources also shows the Status.

3. In the list of Resources, go to the respective resource.

4. In the Operations column click the arrow down button and select Unmigrate. To continue, confirm the message that appears.

   Hawk2 uses the crm_resource  -U command. The resource can move back to its original location or it may stay where it is (depending on resource stickiness).

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. In the left navigation bar, select Dashboard.

   Hawk2 shows an overview of the resources and nodes on the current cluster site. In addition, it shows any Tickets that have been configured for use with a Geo cluster. If you need information about the icons used in this view, click Legend. To search for a resource ID, enter the name (ID) into the Search text box. To only show specific nodes, click the filter icon and select a filtering option.

   

   Figure 7.16: Hawk2 Dashboard with One Cluster Site (amsterdam) #

3. To add dashboards for multiple clusters:

   1. Click Add Cluster.

   2. Enter the Cluster name with which to identify the cluster in the Dashboard. For example, berlin.

   3. Enter the fully qualified host name of one of the nodes in the second cluster. For example, charlie.

      

   4. Click Add. Hawk2 will display a second tab for the newly added cluster site with an overview of its nodes and resources.

      

      Note: Connection Error

      If instead you are prompted to log in to this node by entering a password, you probably did not connect to this node yet and have not replaced the self-signed certificate. In that case, even after entering the password, the connection will fail with the following message:

      Error connecting to server. Retrying every 5 seconds...

      To proceed, see Replacing the Self-Signed Certificate.

4. To view more details for a cluster site or to manage it, switch to the site's tab and click the chain icon.

   Hawk2 opens the Status view for this site in a new browser window or tab. From there, you can administer this part of the Geo cluster.

5. To remove a cluster from the dashboard, click the x icon on the right-hand side of the cluster's details.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. In the left navigation bar, select Status. It lists Resources and Nodes.

3. To view recent events of a resource:

   1. Click Resources and select the respective resource.

   2. In the Operations column for the resource, click the arrow down button and select Recent events.

      Hawk2 opens a new window and displays a table view of the latest events.

4. To view recent events of a node:

   1. Click Nodes and select the respective node.

   2. In the Operations column for the node, select Recent events.

      Hawk2 opens a new window and displays a table view of the latest events.

      

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. In the left navigation bar, select History.

   The History Explorer screen opens in the Generate view. By default, the suggested time frame for a report is the last hour.

3. To create a cluster report:

   1. To immediately start a report, click Generate.

   2. To modify the time frame for the report, click anywhere on the suggested time frame and select another option from the drop-down box. You can also enter a Custom start date, end date and hour, respectively. To start the report, click Generate.

      After the report has finished, it is shown below Reports.

4. To upload a cluster report, the crm report archive must be located on a file system that you can access with Hawk2. Proceed as follows:

   1. Switch to the Upload tab.

   2. Browse for the cluster report archive and click Upload.

      After the report is uploaded, it is shown below Reports.

5. To download or delete a report, click the respective icon next to the report in the Operations column.

6. To view Report Details in History Explorer, click the report's name or select Show from the Operations column.

   

7. Return to the list of reports by clicking the Reports button.

1. Log in to Hawk2:

   https://HAWKSERVER:7630/

2. In the left navigation bar, select History.

   If reports have already been generated or uploaded, they are shown in the list of Reports. Otherwise generate or upload a report as described in Procedure 7.31.

3. Click the report's name or select Show from the Operations column to open the Report Details in History Explorer.

4. To access the transition details, you need to select a transition point in the transition time line that is shown below. Use the Previous and Next icons and the Zoom In and Zoom Out icons to find the transition that you are interested in.

5. To display the name of a pe-input* file plus the time and node on which it was created, hover the mouse pointer over a transition point in the time line.

6. To view the Transition Details in the History Explorer, click the transition point for which you want to know more.

7. To show Details, Configuration, Diff, Logs or Graph, click the respective buttons to show the content described in Transition Details in the History Explorer.

8. To return to the list of reports, click the Reports button.