Implementing Consistent Storage Service Levels with OnCommand Workflow Automation. October 2016 SL10296 Version 1.0.1

Transcription

1 Implementing Consistent Storage Service Levels with OnCommand Workflow Automation October 2016 SL10296 Version 1.0.1

2 1 Introduction OnCommand Workflow Automation brings automated Service Level Objective (SLO) storage management to your NetApp ONTAP infrastructure. This is an advanced level OnCommand Workflow Automation (WFA) lab exercise. To get the most out of this lab you 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: 2 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.

3 2 Lab Environment The following diagram illustrates the components and connectivity of this lab. You can access these components using 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 entry point for lab dc1 Windows 2012 R2 Domain Controller, DNS ocum Windows 2012 R2 OnCommand Unified Manager opm OPM 7.0 VM Appliance OnCommand Performance Manager wfa Windows 2012 R2 OnCommand Workflow Automation rhel1 Redhat Linux Linux client cluster1-01 ONTAP Cluster1 node cluster1-02 ONTAP Cluster1 node cluster2-01 ONTAP Cluster2 node cluster2-02 ONTAP Cluster2 node cluster1 ONTAP cluster admin shell cluster2 ONTAP cluster admin shell User IDs and Passwords 3 Host Name User ID Password Comments jumphost DEMO\administrator Netapp1! The portal automatically logs you into this system for 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 available as root with the same password

4 4 Host Name User ID Password Comments cluster2 admin Netapp1! Node shell logins available as root with the same password

5 3 Introduction to Service Level Objective Service Level Objectives (SLOs) provide a quantitative means of describing and comparing the capabilities of systems and services. SLOs provide the physical basis for metering and translating storage services into other tangible metrics, such as Watts, area, and dollars. This enables application of a business model to the delivery of storage services, such as a Service Level Agreement (SLA). The SLO framework also provides a means for providers of storage service to drive optimization of utilization, performance modelling, and trending analysis, and asset planning. SLOs can be applied to many different types of storage objects like LUNs, files, objects, and file systems. For each 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. 5

6 4 Storage Service Level Class A Storage Service Level Class (SSLC), is a set of attribute-value pairs (called SSLC descriptors) for a defined collection of storage SLO attributes. A SSLC may include attributes for IOPs, capacity, etc. While the possible space of all SLCs is the infinite cross product of all realizable combinations of SLO attributes, in practice only a small 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 each application's storage needs. If these needs change over time, you can migrate that dataset to a differenct SSLC level using WFA. 6

7 5 Protection Service Level Class A Protection Service Level Class (PSLC) is a set of attribute-value pairs (called PSLC descriptors) for defining data protection capabilities such as backup, disaster recovery, etc. Normally only a small number of PSLCs need to be defined. As a storage architect, you will use WFA to associate a PSLC to a SSLC. By doing this, you can add the correct level of data protection to your SSLC datasets. 7

8 6 Introduction to Adaptive Qos Policy Manager Two major trends in storage have emerged simultaneously. At one extreme, modern flash-accelerated storage systems have become faster and are capable of delivering thousands of I/O operations per second per terabyte of stored data. On the other hand, the falling prices of spinning disks allow delivery of capacity with a low cost per gigabyte per month. In response to these trends, multiple service levels can be differentiated by IOPS/TB ratios. This allows IT organizations to match application storage needs with the correct price and performance characteristics. These price 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 service levels are designed to meet the cost and performance requirements using a storage service. Figure 6-1: 8

9 7 SLO Setup and Configuration on OnCommand Workflow Automation This activity shows how to complete the SLO setup and configuration on WFA. The steps demonstrate how to import SLO 1.4 Pack from the NetApp Automation Store into WFA, initialize the SLO pack, update an existing Storage 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. 9

10 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. 10

11 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 appear all 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. 11

12 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 dar. For your convenience this file has already been downloaded from the NetApp Automation Store and saved in the Downloads folder. 12. Click Open. 12

13 Figure 7-7: The Open window close, and after a few moments the Import DAR file window opens. 13. Click Import. 13

14 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, and Service Level Management. 16. In the left pane, click Adaptive QoS. 17. In the right pane, click Service Catalog Initialization. 14

15 Figure 7-10: The Execute Workflow Service Catalog Initialization window opens. 18. Set the Action? dropdown to Create. 19. Click Execute. 15

16 18 19 Figure 7-11: The Execute Workflow Service Catalog Initialization window closes, and the Service Catalog Initialization window opens and the workflow begins executing. 20. This workflow initializes all the Service Level classes and their respective parameters. Wait for the workflow to complete. You will know it's done when you see a green checkmark in the upper lefthand corner of the window. Note: Don't rely on the progress bar showing 100% as a general indication of completion. Other workflows in this lab will be complete with a progress bar percentage as low as 0%, so always use the green checkmark as the completion indicator. 21. Click OK. 16

17 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. 17

18 22 23 Figure 7-13: The Execute Workflow Manage Storage and Adaptive QoS Service Configuration window opens Set the Select Task: dropdown to Manage Storage & AQoS Service Levels. Set the Service Level Action: dropdown to Update. Set the Storage Level Service Class: dropdown to Capacity. Set the Aggregate Include (REGEX): field to aggrssd. Set the Volume Include (REGEX): field to Vol. Click Execute.

19 Figure 7-14: The Execute Workflow Manage Storage and Adaptive QoS Service Configuration window closes, and the Manage Storage and Adaptive QoS Service Configuration window opens and the workflow begins executing. 30. Wait for the workflow to complete based on the appearance of the green checkmark in the upper left corner of the window. 31. Click OK. 19

20 30 31 Figure 7-15: The Manage Storage and Adaptive QoS Service Configuration window closes and focus returns to the browser's WFA page. 32. In the right pane, again click Manage Storage and Adaptive QoS Service Configuration. 20

21 32 Figure 7-16: The Execute Workflow Manage Storage and Adaptive QoS Service Configuration window opens Set the Select Task: dropdown to Manage Storage & AQoS Service Levels. Set the Service Level Action: dropdown to Update. Set the Storage Level Service Class: dropdown to Extreme. Set the Aggregate Include (REGEX): field to aggrssd. Click Execute.

22 Figure 7-17: The Execute Workflow Manage Storage and Adaptive QoS Service Configuration window closes, and the Manage Storage and Adaptive QoS Service Configuration window opens and the workflow begins executing. 38. Wait for the workflow to complete, as indicated by the green checkmark in the upper left corner of the window. 39. Click OK. 22

23 38 39 Figure 7-18: The Manage Storage and Adaptive QoS Service Configuration window closes and focus returns the the browser's WFA page. 40. In the left pane, click Service Level Management. 41. In the right pane, click Manage Protection Service Level Class. 23

24 41 40 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. 24

25 43 Figure 7-20: the Execute Workflow Manage Protection Service Level Class window closes, and focus returns to the browser's WFA page. Now add the clusters to the setup. 44. In the right pane, click Manage Storage and Adaptive QoS Service Configuration. 25

26 44 Figure 7-21: The Execute Workflow Manage Storage and Adaptive QoS Service Configuration window opens Set the Select Task dropdown to Manage Clusters Set the Cluster Action? dropdown to add. Check all the checkboxes in the Cluster Details list. Click Execute.

27 Figure 7-22: The Execute Workflow Manage Storage and Adaptive QoS Service Configuration window closes and the Manage Storage and Adaptive QoS Service Configuration window opens. 49. Wait for the workflow to complete, as indicated by the green checkmark in the upper left corner of the window. 50. Click OK. 27

28 49 50 Figure 7-23: The Manage Storage and Adaptive QoS Service Configuration window closes and focus returns to the browser's WFA page. 51. In the right pane, again click Manage Storage and Adaptive QoS Service Configuration. 28

29 51 Figure 7-24: The Execute Workflow Manage Storage and Adaptive QoS Service Configuration window opens Set the Select Task dropdown to Manage AQoS Service. Set the AQoS Service Action dropdown to Start Service. Set the WFA Admin User Name field to admin. Set the Password field to Netapp1!. Set the Re-enter Password field to NetApp1!. Click Execute.

30 Figure 7-25: The Execute Workflow Manage Storage and Adaptive QoS Service Configuration window closes and the Manage Storage and Adaptive QoS Service Configuration window opens. 58. Wait for the workflow to complete, as indicated by the green checkmark in the upper left corner of the window. 59. Click OK. 30

31 58 59 Figure 7-26: The Manage Storage and Adaptive QoS Service Configuration window closes and focus returns to the browser's WFA page. These steps complete the SLO setup and configuration on OnCommand WFA. 31

32 8 Run SLO Workflows This activity is to provision and manage NetApp Storage based on Storage Level Objectives with the help of OnCommand 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. 2 1 Figure 8-1: The Execute Workflow Provision Volume based on service level window opens In the Storage Virtual Machine list, select svm2_cluster1. Set the Storage Service Level Class dropdown to Extreme. Set the Protection Service Level Class dropdown to bkp_copy. Set Volume Name to extremevol. Set Volume Size (GB) to 1. Click Execute.

33 Figure 8-2: The Execute Workflow Provision Volume based on service level window closes, and the Provision Volume based on service level window opens. 9. Wait for the workload to complete, which should take a couple of minutes. Once it finishes (as indicated by the green checkmark in the upper left corner of the window), click OK. 33

34 9 Figure 8-3: The Provision Volume based on service level window closes, and focus returns to the main WFA browser window. Verify that the volume was created in the primary cluster, and that the backup copy was created in the destination cluster. 10. Open a new browser tab in Chrome. 11. Enter the URL 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 the page. 13. Click the Proceed to cluster1.demo.netapp.com (unsafe) link at the bottom of the page. 34

35 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. 35

36 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. 36

37 Figure 8-6: Check for the presence of the backup copy of the volume on cluster2. Open a new browser tab in Chrome. Enter the URL 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 to cluster1.demo.netapp.com (unsafe) at the bottom of the page. In the System Manager login page, set the fields as follows: User Name : admin Password : Netapp1! 24. Click Sign In. 37

38 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 named extremevol_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_vol from svm2_cluster1. 38

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

40 9 References NetApp Workflow Automation Store can be found on the NetApp community site. There you will also find the following 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 for download. All of the above workflows are officially supported as of September Check the site for more details: 40

41 10 Version History 41 Version Date Document Version History September 2016 Initial Release September 2016 Fixed title page

42 Refer to the Interoperability Matrix Tool (IMT) on the NetApp Support site to validate that the exact product 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 construct configurations that are supported by NetApp. Specific results depend on each customer's installation in accordance with published specifications. NetApp provides no representations or warranties regarding the accuracy, reliability, or serviceability of any information or recommendations provided in this publication, or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS, and the use of this information or the implementation of any recommendations or techniques herein is a customer s responsibility and depends on the customer s ability to evaluate and integrate them into the customer s operational environment. This document and the information contained herein may be used 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 consent of 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 registered trademarks of NetApp, Inc. in the United States and/or other countries. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such.