Implementing Consistent Storage Service Levels ... - NetApp · Implementing Consistent Storage...

Implementing Consistent StorageService Levels with OnCommandWorkflow Automation

October 2016 | SL10296 Version 1.0.1

Implementing Consistent Storage Service Levels with OnCommand Workflow Automation2 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

1 IntroductionOnCommand Workflow Automation brings automated Service Level Objective (SLO) storage management toyour NetApp ONTAP infrastructure.

This is an advanced level OnCommand Workflow Automation (WFA) lab exercise. To get the most out of this labyou should have the following level of experience:

• You have executed a workflow on OnCommand Workflow Automation.• You have some hands-on experience with NetApp ONTAP.

In this lab you will perform the following activities:

• Learn the Service Level Objective (SLO) storage concept.• Configure WFA with the downloadable SLO workflows.• Provision and protect storage according to defined Storage Service Level Classes (SSLC) and

Protection Service Level Classes (PSLC).• Migrate existing storage to a different SSLC.• Learn about a new way to classify storage resources with Adaptive Qos Policy Manager.


2 Lab EnvironmentThe following diagram illustrates the components and connectivity of this lab. You can access these componentsusing the credentials listed in the table that follows the diagram.

Figure 2-1:

2 Table of Systems

Host Name Operating System Role/Function IP Address

jumphost Windows 2012 R2 Primary desktop entrypoint for lab

192.168.0.5

dc1 Windows 2012 R2 Domain Controller, DNS 192.168.0.253

ocum Windows 2012 R2 OnCommand UnifiedManager

192.168.0.71

opm OPM 7.0 VM Appliance OnCommandPerformance Manager

192.168.0.72

wfa Windows 2012 R2 OnCommand WorkflowAutomation

192.168.0.73

rhel1 Redhat Linux Linux client 192.168.0.61

cluster1-01 ONTAP 8.3.2 Cluster1 node1 192.168.0.111




cluster1 ONTAP 8.3.2 cluster admin shell 192.168.0.101

cluster2 ONTAP 8.3.2 cluster admin shell 192.168.0.102

2 User IDs and Passwords

Host Name User ID Password Comments

jumphost DEMO\administrator Netapp1! The portal automaticallylogs you into this systemfor lab access

dc1 DEMO\administrator Netapp1!

ocum DEMO\administrator Netapp1!

opm admin Netapp1!

wfa DEMO\administrator Netapp1!

rhel1 root Netapp1!

cluster1 admin Netapp1! Node shell logins availableas root with the samepassword


Host Name User ID Password Comments

cluster2 admin Netapp1! Node shell logins availableas root with the samepassword


3 Introduction to Service Level ObjectiveService Level Objectives (SLOs) provide a quantitative means of describing and comparing the capabilities ofsystems and services. SLOs provide the physical basis for metering and translating storage services into othertangible metrics, such as Watts, area, and dollars. This enables application of a business model to the deliveryof storage services, such as a Service Level Agreement (SLA). The SLO framework also provides a means forproviders of storage service to drive optimization of utilization, performance modelling, and trending analysis, andasset planning.

SLOs can be applied to many different types of storage objects like LUNs, files, objects, and file systems. Foreach of these storage objects the WFA SLO pack includes objectives for:

• Performance• Capacity• Data Protection• ...and many others not covered in this guide!

Note: Other attributes of interest include security, durability, and availability.


4 Storage Service Level ClassA Storage Service Level Class (SSLC), is a set of attribute-value pairs (called SSLC descriptors) for a definedcollection of storage SLO attributes. A SSLC may include attributes for IOPs, capacity, etc. While the possiblespace of all SLCs is the infinite cross product of all realizable combinations of SLO attributes, in practice only asmall number of SCLs need to be defined.

As a storage architect, you will use WFA to select an existing SSLC (or define new ones) that matches eachapplication's storage needs. If these needs change over time, you can migrate that dataset to a differenct SSLClevel using WFA.


5 Protection Service Level ClassA Protection Service Level Class (PSLC) is a set of attribute-value pairs (called PSLC descriptors) for definingdata protection capabilities such as backup, disaster recovery, etc. Normally only a small number of PSLCs needto be defined.

As a storage architect, you will use WFA to associate a PSLC to a SSLC. By doing this, you can add the correctlevel of data protection to your SSLC datasets.


6 Introduction to Adaptive Qos Policy ManagerTwo major trends in storage have emerged simultaneously. At one extreme, modern flash-accelerated storagesystems have become faster and are capable of delivering thousands of I/O operations per second per terabyteof stored data. On the other hand, the falling prices of spinning disks allow delivery of capacity with a low cost pergigabyte per month.

In response to these trends, multiple service levels can be differentiated by IOPS/TB ratios. This allows ITorganizations to match application storage needs with the correct price and performance characteristics. Theseprice and performance characteristics can differ from one service level to another by an order of magnitude.

Adaptive QoS Policy Manager enables a range of service levels aligned to application I/O requirements.

The following chart summarizes the conceptual basis for QoS enabled service levels. These storage servicelevels are designed to meet the cost and performance requirements using a storage service.

Figure 6-1:


7 SLO Setup and Configuration on OnCommand Workflow AutomationThis activity shows how to complete the SLO setup and configuration on WFA. The steps demonstrate how toimport SLO 1.4 Pack from the NetApp Automation Store into WFA, initialize the SLO pack, update an existingStorage Service Level, and update an existing Protection Service Level.

Follow the steps below to import and configure the SLO pack:

1. On jumphost, click the Windows button and then select Remote Desktop Connection.

1

Figure 7-1:

The “Remote Desktop Connection” window opens.

2. In the “Computer” dropdown, select wfa.3. Click Connect.


2

3

Figure 7-2:

The “Remote Desktop Connection” window closes, and the “Windows Security” window opens.

4. Enter the password Netapp1!.5. Click OK.

4

5

Figure 7-3:

The “Windows Security” window closes and a RDP session opens to the Windows server named wfa.


6. On the taskbar of wfa, launch Chrome.

6

Figure 7-4:

The Chrome browser opens and displays the OnCommand Workflow Automation (WFA) login page,which is configured as Chrome's home page.

7. Enter the user name admin and the password Netapp1!.8. Click Sign in.

7

8

Figure 7-5:

The OnCommand Workflow Automation tool logs you in and displays the Portal tab.

Note: The WFA browser interface requires a lot of screen space. If the WFA tab names appearall jumbled up in your browser, try expand the size of your browser window.

9. In the menu bar that appears above the row of tabs, navigate to Administration > Import.


9

Figure 7-6:

The “Open” window opens.

10. In the left pane, select Downloads.11. In the right pane, select the file wfa-slo-1.4.0-3876949.dar. For your convenience this file has

already been downloaded from the NetApp Automation Store and saved in the Downloads folder.12. Click Open.


1011

12

Figure 7-7:

The “Open” window close, and after a few moments the “Import DAR file” window opens.

13. Click Import.


13

Figure 7-8:

The “Import DAR File” window closes, and the import operation proceeds. Once the import finishes the“Import Success” window opens.

14. Click OK.

14

Figure 7-9:

The “Import success” window closes, and focus to the WFA web interface window.

15. Three new categories appear in the left pane; Adaptive QoS, Service Level based Provisioning, andService Level Management.

16. In the left pane, click Adaptive QoS.17. In the right pane, click Service Catalog Initialization.


15

16

17

Figure 7-10:

The Execute Workflow Service Catalog Initialization” window opens.

18. Set the “Action?” dropdown to Create.19. Click Execute.


18

19

Figure 7-11:

The “Execute Workflow Service Catalog Initialization” window closes, and the “Service CatalogInitialization” window opens and the workflow begins executing.

20. This workflow initializes all the Service Level classes and their respective parameters. Wait for theworkflow to complete. You will know it's done when you see a green checkmark in the upper lefthandcorner of the window.

Note: Don't rely on the progress bar showing 100% as a general indication of completion. Otherworkflows in this lab will be complete with a progress bar percentage as low as 0%, so alwaysuse the green checkmark as the completion indicator.

21. Click OK.


20

21

Figure 7-12:

The “Service Catalog Initialization” window closes, and focus returns to the main WFA browser page.

22. In the left pane, Adaptive QoS should still be selected.23. In the right pane, click Manage Storage and Adaptive QoS Service Configuration.


22

23

Figure 7-13:

The “Execute Workflow Manage Storage and Adaptive QoS Service Configuration” window opens.

24. Set the “Select Task:” dropdown to Manage Storage & AQoS Service Levels.25. Set the “Service Level Action:” dropdown to Update.26. Set the “Storage Level Service Class:” dropdown to Capacity.27. Set the ”Aggregate Include (REGEX):” field to aggrSSD.28. Set the “Volume Include (REGEX):” field to Vol.29. Click Execute.


24

2526

2728

29

Figure 7-14:

The “Execute Workflow Manage Storage and Adaptive QoS Service Configuration” window closes, andthe “Manage Storage and Adaptive QoS Service Configuration” window opens and the workflow beginsexecuting.

30. Wait for the workflow to complete based on the appearance of the green checkmark in the upper leftcorner of the window.

31. Click OK.


30

31

Figure 7-15:

The “Manage Storage and Adaptive QoS Service Configuration” window closes and focus returns to thebrowser's WFA page.

32. In the right pane, again click Manage Storage and Adaptive QoS Service Configuration.


32

Figure 7-16:


33. Set the “Select Task:” dropdown to Manage Storage & AQoS Service Levels.34. Set the “Service Level Action:” dropdown to Update.35. Set the “Storage Level Service Class:” dropdown to Extreme.36. Set the ”Aggregate Include (REGEX):” field to aggrSSD.37. Click Execute.


33

3435

36

37

Figure 7-17:

The “Execute Workflow Manage Storage and Adaptive QoS Service Configuration” window closes, andthe “Manage Storage and Adaptive QoS Service Configuration” window opens and the workflow beginsexecuting.

38. Wait for the workflow to complete, as indicated by the green checkmark in the upper left corner of thewindow.

39. Click OK.


38

39

Figure 7-18:

The “Manage Storage and Adaptive QoS Service Configuration” window closes and focus returns thethe browser's WFA page.

40. In the left pane, click Service Level Management.41. In the right pane, click Manage Protection Service Level Class.


40

41

Figure 7-19:

the “Execute Workflow Manage Protection Service Level Class” window opens.

42. Verify that the following fields are set correctly.

Caution: You will not be executing this workflow, just examining the defaults!

• “Action”: Update PSL• “Protection Service Level Class”: bkp_copy• “Relationship Action?”: Update Relation• “Relationship Name”: bkp• Relationship Destination's Storage Service Level Class”: Capacity

43. Click Cancel.


43

Figure 7-20:

the “Execute Workflow Manage Protection Service Level Class” window closes, and focus returns to thebrowser's WFA page.

Now add the clusters to the setup.44. In the right pane, click Manage Storage and Adaptive QoS Service Configuration.


44

Figure 7-21:


45. Set the “Select Task” dropdown to Manage Clusters46. Set the “Cluster Action?” dropdown to add.47. Check all the checkboxes in the “Cluster Details” list.48. Click Execute.


45

4647

Figure 7-22:

The “Execute Workflow Manage Storage and Adaptive QoS Service Configuration” window closes andthe “Manage Storage and Adaptive QoS Service Configuration” window opens.


50. Click OK.


49

50

Figure 7-23:


51. In the right pane, again click Manage Storage and Adaptive QoS Service Configuration.


51

Figure 7-24:


52. Set the “Select Task” dropdown to Manage AQoS Service.53. Set the “AQoS Service Action” dropdown to Start Service.54. Set the “WFA Admin User Name” field to admin.55. Set the “Password” field to Netapp1!.56. Set the “Re-enter Password” field to NetApp1!.57. Click Execute.


52

53

545556

57

Figure 7-25:

The “Execute Workflow Manage Storage and Adaptive QoS Service Configuration” window closes andthe “Manage Storage and Adaptive QoS Service Configuration” window opens.


59. Click OK.


58

59

Figure 7-26:


These steps complete the SLO setup and configuration on OnCommand WFA.


8 Run SLO WorkflowsThis activity is to provision and manage NetApp Storage based on Storage Level Objectives with the help ofOnCommand Workflow Automation.

The WFA browser window should still be open to the Portal tab from the last exercise.

Begin by provisoning a volume based on service level.

1. In the left pane, click Service Level based Provisioning.2. In the right pane, click Provision Volume based on Service Level.

1

2

Figure 8-1:

The “Execute Workflow Provision Volume based on service level” window opens.

3. In the “Storage Virtual Machine” list, select svm2_cluster1.4. Set the “Storage Service Level Class” dropdown to Extreme.5. Set the “Protection Service Level Class” dropdown to bkp_copy.6. Set “Volume Name” to extremeVol.7. Set “Volume Size (GB)” to 1.8. Click Execute.


3

45

67

8

Figure 8-2:

The “Execute Workflow Provision Volume based on service level” window closes, and the “ProvisionVolume based on service level” window opens.

9. Wait for the workload to complete, which should take a couple of minutes. Once it finishes (as indicatedby the green checkmark in the upper left corner of the window), click OK.


9

Figure 8-3:

The “Provision Volume based on service level” window closes, and focus returns to the main WFAbrowser window.

Verify that the volume was created in the primary cluster, and that the backup copy was created in thedestination cluster.

10. Open a new browser tab in Chrome.11. Enter the URL https://cluster1.demo.netapp.com.12. You are presented with a page stating the connection is not private. This is because Sysytem Manager

is using a self-signed certificate. To bypass this warning, click the Advanced link in the middle of thepage.

13. Click the Proceed to cluster1.demo.netapp.com (unsafe) link at the bottom of the page.


12

11

13

Figure 8-4:

System Manager displays a login page.

14. Set the “User Name” to admin.15. Set the Password field to Netapp1!.16. Click Sign In.


1415

16

Figure 8-5:

System Manager logs in and displays the cluster dashboard page.

17. In the left pane, navigate to Storage Virtual Machines > cluster1 > svm2_cluster1 > Storage >Volumes.

18. In the Volumes pane, select the entry for the volume named extremeVol.19. Click the Details tab in the lower pane and observe that the ”Policy Group” shows

Extreme_extremeVol, indicating the service level objective for this volume.


17

18

19

Figure 8-6:

Check for the presence of the backup copy of the volume on cluster2.20. Open a new browser tab in Chrome.21. Enter the URL https://cluster2.demo.netapp.com.22. You are presented with a page stating the connection is not private. As before, bypass this

warning by clicking the Advanced link in the middle of the page, and then clicking Proceed tocluster1.demo.netapp.com (unsafe) at the bottom of the page.

23. In the System Manager login page, set the fields as follows:

• “User Name”: admin• “Password”: Netapp1!

24. Click Sign In.


21

2223

24

20

Figure 8-7:

System Manager logs in and displays the cluster dashboard page.

25. In the left pane, navigate to Storage Virtual Machines > cluster1 > svm1_cluster2 > Storage >Volumes.

26. In the Volumes pane, select the entry for the volume namedextremeVol_bkp_copy_bkp_destination_volume.

27. Click the Data Protection tab in the lower pane and observe that this volume is a mirror of extreme_Volfrom svm2_cluster1.


25

26

27

Figure 8-8:

With WFA SLO packs installed, creating consistent storage objects with pre-defined data protectioninvolves just three steps: Select the workflow, fill out the single form with details, and execute theworkflow. As with any automation effort, the automation configuration is well worth the effort due to theoperational efficiencies that are realized in every day work!


9 ReferencesNetApp Workflow Automation Store can be found on the NetApp community site. There you will also find thefollowing resources:

• Tutorials.• Code samples.• Access to experts through discussion groups.

Note that on the following site, there are both NetApp supported and community supported workflow packs fordownload. All of the above workflows are officially supported as of September 2016. Check the site for moredetails:http://automationstore.netapp.com/

http://automationstore.netapp.com/


10 Version History

Version Date Document Version History

1.0.0 September 2016 Initial Release

1.0.1 September 2016 Fixed title page

Refer to the Interoperability Matrix Tool (IMT) on the NetApp Support site to validate that the exactproduct and feature versions described in this document are supported for your specific environment.The NetApp IMT defines the product components and versions that can be used to constructconfigurations that are supported by NetApp. Specific results depend on each customer's installation inaccordance with published specifications.

NetApp provides no representations or warranties regarding the accuracy, reliability, or serviceability of anyinformation or recommendations provided in this publication, or with respect to any results that may be obtainedby the use of the information or observance of any recommendations provided herein. The information in thisdocument is distributed AS IS, and the use of this information or the implementation of any recommendations ortechniques herein is a customer’s responsibility and depends on the customer’s ability to evaluate and integratethem into the customer’s operational environment. This document and the information contained herein may beused solely in connection with the NetApp products discussed in this document.

Go further, faster®

© 2016NetApp, Inc. All rights reserved. No portions of this document may be reproduced without prior written consentof NetApp, Inc. Specifications are subject to change without notice. NetApp, the NetApp logo, Data ONTAP®,ONTAP®, OnCommand®, SANtricity®, FlexPod®, SnapCenter®, and SolidFire® are trademarks or registeredtrademarks of NetApp, Inc. in the United States and/or other countries. All other brands or products are trademarks orregistered trademarks of their respective holders and should be treated as such.

http://support.netapp.com/matrix/mtx/login.do

Implementing Consistent Storage Service Levels ... - NetApp · Implementing Consistent Storage...

Documents

Transcript of Implementing Consistent Storage Service Levels ... - NetApp · Implementing Consistent Storage...