39 UI Verification #

Log into the horizon dashboard.

Choose Project › Compute › Volumes.

On the Volumes tabs, click the Create Volume button to create a volume.

In the Create Volume options, enter the required details into the fields and then click the Create Volume button:

1. Volume Name - This is the name you specify for your volume.

2. Description (optional) - This is an optional description for the volume.

3. Type - Select the volume type you have created for your volumes from the drop down.

4. Size (GB) - Enter the size, in GB, you would like the volume to be.

5. Availability Zone - You can either leave this at the default option of Any Availability Zone or select a specific zone from the drop-down box.

Log into the horizon dashboard.

Choose Project › Compute › Instances.

In the Action column, choose the Edit Attachments in the drop-down box next to the instance you want to attach the volume to.

In the Attach To Instance drop-down, select the volume that you want to attach.

Edit the Device Name if necessary.

Click Attach Volume to complete the action.

On the Volumes screen, verify that the volume you attached is displayed in the Attached To columns.

Log into the horizon dashboard.

Choose Project › Compute › Instances.

Click the check box next to the name of the volume you want to detach.

In the Action column, choose the Edit Attachments in the drop-down box next to the instance you want to attach the volume to.

Click Detach Attachment. A confirmation dialog box appears.

Click Detach Attachment to confirm the detachment of the volume from the associated instance.

Log into the horizon dashboard.

Choose Project › Compute › Volumes.

In the Actions column, click Delete Volume next to the volume you would like to delete.

To confirm and delete the volume, click Delete Volume again.

Verify that the volume was removed from the Volumes screen.

Run the swift-compare-model-rings.yml playbook as follows:

cd ~/scratch/ansible/next/ardana/ansible
ansible-playbook -i hosts/verb_hosts swift-compare-model-rings.yml

Search for output similar to the following. Specifically, look at the number of drives that are proposed to be added.

TASK: [swiftlm-ring-supervisor | validate-input-model | Print report] *********
ok: [ardana-cp1-c1-m1-mgmt] => {
    "var": {
        "report.stdout_lines": [
            "Rings:",
            "  ACCOUNT:",
            "    ring exists",
            "    no device changes",
            "    ring will be rebalanced",
            "  CONTAINER:",
            "    ring exists",
            "    no device changes",
            "    ring will be rebalanced",
            "  OBJECT-0:",
            "    ring exists",
            "    no device changes",
            "    ring will be rebalanced"
        ]
    }
}

If the text contains "no device changes" then the deploy was successful and no further action is needed.

If more drives need to be added, it indicates that the deploy failed on some nodes and that you restarted the deploy to include those nodes. However, the nodes are not in the swift rings because enough time has not elapsed to allow the rings to be rebuilt. You have two options to continue:

1. Repeat the deploy. There are two steps:

   1. Delete the ring builder files as described in Section 18.6.2.8, “Restarting the Object Storage Deployment”.

   2. Repeat the installation process starting by running the site.yml playbook as described in Section 24.7, “Deploying the Cloud”.

2. Rebalance the rings several times until all drives are incorporated in the rings. This process may take several hours to complete (because you need to wait one hour between each rebalance). The steps are as follows:

   1. Change the min-part-hours to 1 hour. See Section 9.5.7, “Changing min-part-hours in Swift”.

   2. Use the "First phase of ring rebalance" and "Final rebalance phase" as described in Section 9.5.5, “Applying Input Model Changes to Existing Rings”. The “Weight change phase of ring rebalance” does not apply because you have not set the weight-step attribute at this stage.

   3. Set the min-part-hours to the recommended 16 hours as described in Section 9.5.7, “Changing min-part-hours in Swift”.