StorageGRID Webscale 10.0

Transcription

1 StorageGRID Webscale 10.0 Grid Designer User Guide NetApp, Inc. 495 East Java Drive Sunnyvale, CA U.S. Telephone: +1 (408) Fax: +1 (408) Support telephone: +1 (888) Web: Feedback: Part number: _A0 September 2014

2

3 Contents 1 Introduction About this Guide Who Should Read this Guide About Grid Designer What You Can Do with Grid Designer Workflow for Using Grid Designer About Grid Specification Files Installing and updating Grid Designer Planning Your Deployment Compatibility Requirements Prerequisites Downloading Grid Designer Installing and Starting Grid Designer Viewing Grid Designer Version Information Updating Grid Designer Uninstalling Grid Designer Grid Topologies and Rules Grid Topologies Data Center Sites Grid Node Rules Admin Node Rules API Gateway Node Rules Storage Node Rules Archive Node Rules Naming Conventions for Grid Nodes Creating a New Deployment Creating a New StorageGRID Webscale System Saving a Partially Completed System Entering the Grid ID License Text Block Entering Password Information Entering Grid Node Information Entering Grid Network Information Entering Supplementary Network Information Entering Time Synchronization Information Finishing the Grid Specification File _A0 StorageGRID Webscale 10.0

4 Grid Designer User Guide 4 Using the Grid Specification File Modifying a StorageGRID Webscale Configuration Obtaining the Provisioned Grid Specification File Expanding a StorageGRID Webscale System Supported Expansions Expanding a StorageGRID Webscale System Maintenance Procedures Changing IP Addresses Decommissioning Grid Nodes Glossary Copyright Information Trademark Information How to Send Comments Index StorageGRID Webscale _A0

5 Introduction 1 About this Guide The Grid Designer User Guide describes how to use Grid Designer and create the configuration materials required to install, expand, and maintain a StorageGRID Webscale system. This guide does not include design information needed to plan out a grid topology. Who Should Read this Guide This guide is intended for technical personnel trained to install, expand, maintain, and support the StorageGRID Webscale system. About Grid Designer Grid Designer is a Microsoft Windows application used to create the configuration materials needed to install, expand, and maintain a grid. It produces a grid specification file containing the grid s configuration details (in an XML format) required for the successful deployment of a StorageGRID Webscale system _A0 StorageGRID Webscale 10.0

6 6 Grid Designer User Guide Figure 1: A New StorageGRID Webscale System is Created What You Can Do with Grid Designer Use Grid Designer to accomplish the following tasks: Create a new grid. See Chapter 4: Creating a New Deployment. Expand a grid, for example, by adding more grid nodes. See Chapter 5: Expanding a StorageGRID Webscale System. Maintain a grid, for example, by changing an IP address or decommissioning a grid node. See Chapter 6: Maintenance Procedures. StorageGRID Webscale _A0

7 Introduction 7 Workflow for Using Grid Designer Using Grid Designer helps you create, install, expand, and maintain grids. Figure 2 shows how Grid Designer fits into the overall process of creating, installing, expanding, and maintaining grids. New StorageGRID System Create new grid with Grid Designer Expansion Create expansion with Grid Designer Grid spec file <filename>.xml Grid spec file contains the basic design Expansion grid spec file EXP_GID<Grid_ID>_REV2_GSPEC.xml Contains new servers Grid ID signed-grid-id.txt Deploy grid with Grid Designer Deploy grid with Grid Designer Maintenance Perform maintenance procedures with Grid Designer Grid spec file GID<Grid_ID>_REV1_GSPEC.xml Customer-specific information such as IP addresses has been added Grid spec file GID<Grid_ID>_REV2_GSPEC.xml Contains customer-specific information Grid spec file GID<Grid_ID>_REV2_GSPEC.xml Contains new information Install StorageGRID system Provisioned grid spec file GID<Grid_ID>_REV1_GSPEC.xml File has been modified by provisioning Install expansion Provisioned grid spec file GID<Grid_ID>_REV2_GSPEC.xml File has been modified by provisioning Perform maintenance procedure Provisioned grid spec file GID<Grid_ID>_REV2_GSPEC.xml File has been modified by provisioning Figure 2: Grid Designer Workflow About Grid Specification Files After entering topology, server, and networking details into Grid Designer, Grid Designer generates a grid specification file. The grid specification file is an XML file that encapsulates the configuration information needed to install, expand, and maintain a StorageGRID Webscale system. The file includes topology, servers, options, and networking details for the StorageGRID Webscale system _A0 StorageGRID Webscale 10.0

8 8 Grid Designer User Guide Grid Specification File Status The grid specification file has the following statuses: Grid specification file: After you enter details in Grid Designer, you generate the grid specification file from Grid Designer. Provisioned grid specification file: You use the grid specification file during the StorageGRID Webscale system installation and provisioning. After you provision the StorageGRID Webscale system, you can export a grid specification file, but it is now a provisioned grid specification file. Grid Specification File Naming Convention Grid specification files use the naming convention GID<grid_ID>_REV<revision_number>_GSPEC.xml, where <grid_id> refers to the StorageGRID Webscale system s unique identifier and <revision_number> refers to the revision number of the grid specification file, for example, GID1234_REV1_GSPEC.xml. The revision number is increased by one each time the grid specification file is modified, for example to add grid nodes or change IP addresses. For the initial installation of the StorageGRID Webscale system, the revision number is 1 (REV1) that is, the grid specification file has been modified once for the installation of the StorageGRID Webscale system. Any other revision number causes provisioning to fail. StorageGRID Webscale _A0

9 2 Installing and updating Grid Designer Planning Your Deployment Before you install Grid Designer, you should be aware of the following: Compatibility requirements Prerequisite software, storage, and hardware Compatibility Requirements Grid Designer is closely linked to a specific version of both the StorageGRID Webscale software and grid specification file. If you work on different releases of StorageGRID Webscale software, install the correct versions of Grid Designer to support the StorageGRID Webscale software and grid specification files on which you are working. StorageGRID Webscale Software Each major version of Grid Designer supports a specific major release of the StorageGRID Webscale software. For example, Grid Designer 10.0 is compatible only with StorageGRID Webscale 10.0.x software. Updates to a major release of Grid Designer do not affect compatibility with the same major StorageGRID Webscale software release. Grid Specification Files Grid Designer supports and opens only grid specification files created by the same version of Grid Designer _A0 StorageGRID Webscale 10.0

10 10 Grid Designer User Guide Prerequisites Grid Designer requires the following items: Computer running Windows MB free disk space for Grid Designer and the.net Framework Microsoft.NET Framework 3.5 or Downloading Grid Designer You can download the Grid Designer software from the NetApp Support Site. Procedure 1. Access the NetApp Support Site at mysupport.netapp.com. 2. On the top of the page, click Downloads. 3. Click Software. 4. On the StorageGRID row, select All Platforms in the drop-down list and click Go. 5. Continue to the Download page and download the software. Installing and Starting Grid Designer The Grid Designer software is provided as a self-extracting zipped file. 1. Double-click the self extraction Grid Designer installer and follow its prompts. By default, Grid Designer installs at C:\Program Files (x86)\netapp\ StorageGRID Webscale Grid Designer 10.0, and shortcuts appear in the Windows Start menu and on the desktop. Install each version of Grid Designer in its own directory. For Windows 7, Grid Designer installs at Program Files (x86). StorageGRID Webscale _A0

11 Installing and updating Grid Designer Start Grid Designer: Double-click the Grid Designer desktop shortcut. or From the Windows Start menu, select Programs NetApp StorageGRID Webscale Grid Designer Viewing Grid Designer Version Information You can identify the version of Grid Designer. 1. Select Help About Grid Designer. Updating Grid Designer Updates of Grid Designer software might be issued after its initial release. Install the latest update of Grid Designer to access its latest features. Updates might include support for new hardware and new functionality. When you install the latest update of Grid Designer, it replaces any previous updates of that release. Compatible grid specification files are left unchanged and remain available for use with the latest update of Grid Designer. Procedure 1. Double-click the self-extracting installer for the update of Grid Designer software. 2. Follow the prompts _A0 StorageGRID Webscale 10.0

12 12 Grid Designer User Guide Uninstalling Grid Designer If you no longer want to use Grid Designer, you can uninstall it. 1. From the Windows Start menu, select Programs NetApp StorageGRID Webscale Grid Designer <version number> Uninstall NetApp Grid Designer <version number>. 2. Follow the prompts in the Uninstall wizard. StorageGRID Webscale _A0

13 Grid Topologies and Rules 3 Supported topologies, rules on how grid nodes can be used, and naming conventions Grid Topologies Grid Designer supports the following: One to 16 Data Center sites Up to 300 grid nodes for one StorageGRID Webscale deployment Data Center Sites You can create a StorageGRID Webscale deployment with a single data center or multiple data centers. Single Data Center Site A Data Center site (DC) topology is configured to centralize all StorageGRID Webscale infrastructure and operations in a single site. Storage can include both disk storage and nearline archival storage. Multiple Data Center Sites A multiple Data Center site topology is configured to spread Storage- GRID Webscale infrastructure and operations across two or more data centers. Data sharing and disaster recovery is achieved in a peer-topeer manner by automatically distributing data to other sites. Each DC site acts as a disaster recovery site for another site. Storage at any site can include disk storage and nearline archival storage. For more information about topologies, see the Grid Primer _A0 StorageGRID Webscale 10.0

14 14 Grid Designer User Guide Grid Node Rules Each site in a StorageGRID Webscale deployment should include an Admin Node and Storage Nodes. There is however only one primary Admin Node per deployment. A deployment can also include one or more API Gateway Nodes and Archive Nodes. For more information about grid nodes, see the Administrator Guide. Admin Node Rules Each StorageGRID Webscale deployment includes a primary Admin Node that monitors system operations and performs configuration tasks. Only the primary Admin Node includes the Configuration Management Node (CMN) service. The following rules apply to Admin Nodes: All deployments include one primary Admin Node. Each site should include an Admin Node. Only one Admin Node is permitted per site. API Gateway Node Rules Any site can include optional API Gateway Nodes, which provide load balancing functionality to the StorageGRID Webscale system. The API Gateway Node helps distribute workloads when multiple client applications are performing ingest and retrieval operations. Storage Node Rules Storage Nodes host disk storage. All deployments must include Storage Nodes. The number of Storage Nodes depends on object storage requirements. The following rules apply to Storage Nodes: Each data center site must include at least three Storage Nodes. The first three Storage Nodes per site include the Administrative Domain Controller (ADC) service. StorageGRID Webscale _A0

15 Grid Topologies and Rules 15 Archive Node Rules Archive Nodes interface with middleware, such as Tivoli Storage Manager (TSM), that controls archival storage device (tape). Naming Conventions for Grid Nodes Grid Designer assigns each grid node a name that uniquely identifies its location and purpose. The elements that make up a grid node name help to identify the type and function of the grid node. Grid node names can include all or part of the elements in the following format: <Site> <GridNode>n <Type>n Table 1: Naming convention for grid nodes Element <Site> Description Identifies the site name abbreviation. By default, the abbreviated site names are: DC Data Center n Each DC site is numbered sequentially. <GridNode>n Identifies the name of the grid node (with the exception of Gateway Nodes): ADM Admin Node ARC Archive Node G API Gateway Node S Storage Node n Each grid node type at a site is numbered sequentially. The following are examples of grid node names: DC2-ADM1 Admin Node at DC2. DC1-S4 Storage Node at DC _A0 StorageGRID Webscale 10.0

16 16 Grid Designer User Guide StorageGRID Webscale _A0

17 Creating a New Deployment 4 How to create a new StorageGRID Webscale deployment Creating a New StorageGRID Webscale System When you create a new StorageGRID Webscale system, you complete the following tasks: Add one or more data center sites. Add grid nodes to those data center sites. Enter password information. Enter grid network information. Enter any supplementary network information. Synchronize the time between grid nodes. Procedure 1. From Grid Designer, select File New. A yellow field or tab indicates that required information is missing _A0 StorageGRID Webscale 10.0

18 18 Grid Designer User Guide Figure 3: New StorageGRID Webscale System 2. In the General tab, change the grid name and description. The name can be up to 20 characters long. In the Grid Topology tree, the name of the grid site changes. NOTE This name also appears at the top level of the Grid Topology tree in the NMS Management Interface (MI). 3. In the Grid Topology tree, add a data center site by right-clicking on the grid name, selecting Add Site, and entering a site name. Add additional data center sites as needed. 4. (Optional) To change a data center name, in the Grid Topology tree, right-click on the data center site and enter the new name. 5. Add grid nodes to the data center by completing the following: a. In the Grid Topology tree, right-click on the data center and select Add Nodes to <data center name>. b. Select the grid node type (Admin, Storage, API Gateway, or Archive) and enter how many grid nodes of that type. NOTE You can enter only one Admin Node. You must enter a minimum of three storage nodes. StorageGRID Webscale _A0

19 Creating a New Deployment 19 c. Click OK. d. Repeat for each grid node you add. 6. Continue with Entering the Grid ID License Text Block on page 19. Saving a Partially Completed System As you create your StorageGRID Webscale system, you can save the grid specification file you are creating at any time. Procedure 1. At any time during creation, select File Save As. 2. Locate a directory for your StorageGRID Webscale system. 3. In the File Name box, type a name for the partial grid, and click Save. 4. To continue working on the partial grid, select File Open. 5. Locate the grid specification file and click Open. 6. Click Action Modify New Grid to continue working. Entering the Grid ID License Text Block Each StorageGRID Webscale system has a unique numeric identifier. The Grid ID field is extracted from the grid license. You must enter the Grid ID signed text block, which provides the StorageGRID Webscale system with a unique grid identifier. The Grid ID signed text block comes from the signed-grid-id.txt file issued to you. A new Grid ID signed text block is not required for expansions. Procedure 1. Open the text file (signed-grid-id.txt) that contains the Grid ID serial number. 2. Select the text including the opening and closing delimiters and all blank lines that are a part of the file _A0 StorageGRID Webscale 10.0

20 20 Grid Designer User Guide For example: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 gid=xxxxxxx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) id8dbqfirtvfuycc0gvf84oraoxpaj0crfml35+ejswt6f5/ Le+H36YQzgCfUSyO FSJiBm+KxqXNudn+89uvcPA= =FQi END PGP SIGNATURE Press <Ctrl>+C to copy the selected text to the clipboard. 4. In the General tab, place the cursor in the Enter Grid ID text block field, and press <Ctrl>+V to paste the content into the Grid Designer field. 5. Continue with Entering Password Information on page 20. Entering Password Information When you create a new StorageGRID Webscale system, you also specify the password information needed to access grid nodes once the system is deployed. You enter information for the following types of passwords: Root password Identifies the root password for the grid nodes. Server Manager password Prevents unauthorized access to actions performed from the Server Manager console of each grid node. NMS MI vendor password Accesses the NMS Management Interface with the Vendor account. Procedure 1. In the General tab, for each password, select how it will be generated: Auto-Generated Create a unique random password for each server. Choose this option for optimal security. The root password for each grid node is randomly generated and unique. User-Specified Let me specify a single password for all servers. The StorageGRID Webscale system uses the same root password for all grid nodes and permits you to specify its StorageGRID Webscale _A0

21 Creating a New Deployment 21 value. This setting is not recommended for StorageGRID Webscale system where grid node and data security is a concern. Default Use the default server password. NOT RECOMMENDED. The StorageGRID Webscale system uses the default grid node password. WARNING For security reasons, use of the default password is not recommended. 2. If you selected the user-specified password, enter the password information in the Enter Password and Confirm Password fields. 3. Click Next to go to the Grid Node tab. 4. Continue with Entering Grid Node Information on page 21. Entering Grid Node Information You can change the name of the grid nodes and view the type of hardware for that grid node. You can modify which grid node host certain services. Grid Designer places all required services on the StorageGRID Webscale system. If required, you can: Choose which Admin Node is the primary Admin Node. The primary Admin Node hosts the CMN service. By default, the primary Admin Node is placed at DC1. To change the location of the primary Admin Node, remove the CMN service from the DC1 Admin Node and add it to another Admin Node. A StorageGRID Webscale system includes only one CMN service. Change which Storage Nodes host the ADC service. By default, the ADC service is placed on each of the first three Storage Nodes per site. To change this, remove the ADC service from one Storage Node and add it to another Storage Node in the same site. You must have three ADC services per site _A0 StorageGRID Webscale 10.0

22 22 Grid Designer User Guide Procedure 1. (Optional) In the Grid Nodes tab, to change the grid node name, click on the name and enter a new name. Figure 4: Grid Nodes and their Services 2. (Optional) For each grid node, to change the services on that node click on the Services cell, select the service from the view that appears, and click Finish. 3. Click Next. 4. Continue with Entering Grid Network Information on page 23. StorageGRID Webscale _A0

23 Creating a New Deployment 23 Entering Grid Network Information You can specify IP addresses and network routing for the grid nodes. You configure the network to place all grid nodes on the grid network, with all traffic between grid nodes and all interaction with outside servers occurring on this single network. When you deploy a StorageGRID Webscale system, Grid Designer automatically assigns the grid node s network interfaces (NICs) as you make deployment decisions. The first NIC (eth0) is assigned to the grid network. If you choose to bond this network interface, eth0 and eth1 are both assigned to the grid network. Not Bonded eth0 All servers Bonded eth0, eth1 All servers Steps 1. In the Grid Network tab, select the grid node that you want to edit. Figure 5: Grid Network Tab _A0 StorageGRID Webscale 10.0

24 24 Grid Designer User Guide 2. Complete the following for the selected grid node: a. Bonded. Select Yes or No to assign the server s NICs as required. By default, network interfaces are not bonded. b. IP address. Enter the IP address for the grid node. Each grid node must have a unique IP address. c. Mask. Enter the network mask for the subnet to which the grid node as direct access. d. Gateway. Enter the IP address of the default gateway. 3. Click Next. 4. Continue with Entering Supplementary Network Information on page 24. Entering Supplementary Network Information Using the Supplementary Network tab, you should specify routing for servers that must be integrated on networks other than the grid networks. This is optional; ignore this tab if the StorageGRID Webscale system is not accessed from other networks. Procedure 1. In the Supplementary Network tab, select the Supplementary Routing Profile row that you want to edit and enter the following information: StorageGRID Webscale _A0

25 Creating a New Deployment 25 Figure 6: Supplementary Network Tab a. Profile Name. Enter a routing profile name for each route required to configure the networking for the grid nodes. The name for the routing profile is arbitrary. On expansion, existing profiles are read-only. When you change the IP address of an existing network, you can edit the current profile or add a new one. b. Network ID and Mask. Enter the Network ID and subnet Mask to specify the range of IP addresses that are routable through the network Gateway specified for the profile. c. Gateway. Enter the IP address of the gateway that routes the addresses described by the Network ID and Mask. 2. Select the Supplementary Grid Networking row that you want to edit and enter the following information: a. Grid Node. The list contains all servers in the grid that have enough NICS for the specified networking configuration. b. Bonded. Select Yes or No to assign bonding. By default, network interfaces are not bonded. c. IP Address. The IP address of the grid node on the supplementary network. Each grid node must have a unique IP address. d. Mask. The network mask for the local subnet _A0 StorageGRID Webscale 10.0

26 26 Grid Designer User Guide e. Supplementary Routing Profile Name. Click to display the Routing Profile Selection dialog, which contains the list of routing profiles that you created at the top of this tab. Select one or more routing profiles for the grid node, and then click Finish. All of the routing profiles that you selected are now assigned to the grid node. If you later expand a StorageGRID Webscale system, you can add new routing profiles to an existing grid node, but you cannot remove existing profiles. 3. Click Next. 4. Continue with Entering Time Synchronization Information on page 26. Entering Time Synchronization Information You should specify the NTP configuration for the StorageGRID Webscale system. Specify at least four external NTP sources. The maximum is eight. External time sources must use the NTP protocol, not the SNTP protocol. In particular, the Windows Time Service does not provide enough synchronization accuracy because it uses SNTP. If you later expand a StorageGRID Webscale system, the NTP sources and roles of existing grid nodes are read-only. Procedure 1. In the Time Synchronization tab, select the External NTP Sources row that you want to edit and enter the following information: a. Name. This field is included for your reference only. Grid Designer does not perform a DNS lookup or save this information. Enter the name of an NTP time reference that is external to the StorageGRID Webscale system. b. IP Address. The IP address of the NTP reference time source external to the StorageGRID Webscale system. Specify four external NTP time references of Stratum 3 or better to prevent issues with time drift. The IP address identifies and contacts the NTP time server, so it must be specified correctly. StorageGRID Webscale _A0

27 Creating a New Deployment 27 Figure 7: Time Synchronization Tab 2. Under Internal NTP Hierarchy, select a grid node and enter the following information: a. Grid Node. This field is prepopulated with the hostname of a grid node. With the recommended NTP hierarchy, Admin Nodes and API Gateway nodes receive time and act as primary NTP time servers for the StorageGRID Webscale system, while all other grid nodes are NTP clients. b. NTP Role. Specify whether the grid node acts as a primary NTP time server for the StorageGRID Webscale system or as an NTP client. The primary NTP time servers synchronize to external time sources and with each other. You must specify at least two primary NTP servers for redundancy and for loss of inter-site communication. In a StorageGRID Webscale system with multiple data center sites, at least one grid node at each site must be a primary NTP time server. The primary Admin Node must be a primary NTP time server. 3. Continue with Finishing the Grid Specification File on page _A0 StorageGRID Webscale 10.0

28 28 Grid Designer User Guide Finishing the Grid Specification File After you click Finish, Grid Designer verifies data and generates a grid specification file. 1. Review each tab carefully. 2. Click Finish. A new grid specification file is created that can be used to provision the StorageGRID Webscale system. NOTE The Finish button becomes available only when enough information is specified to create an operational StorageGRID Webscale system. A warning appears if Grid Designer detects duplicate IP addresses. The tabs highlighted in yellow contain these duplicate IP addresses. NOTE Do not rename the grid specification file. The grid specification file must follow the GID<Grid_ID>_REV1_GSPEC.xml naming format. When the grid specification file does not follow the naming formation, provisioning fails during installation of the StorageGRID Webscale software. Using the Grid Specification File The grid specification file created by Grid Designer is used to provision the StorageGRID Webscale system. For more information about provisioning the StorageGRID Webscale system, see the Installation Guide. Modifying a StorageGRID Webscale Configuration You can modify a grid specification file at any time before you use that grid specification file to provision a StorageGRID Webscale system by opening it in Grid Designer making changes and then clicking Finish. However, once a grid specification file is used to provision a Storage- GRID Webscale system, you must use the provisioned grid StorageGRID Webscale _A0

29 Creating a New Deployment 29 specification file to make changes. You cannot use any other version of the grid specification file. The provisioned grid specification file is used expand the system the StorageGRID Webscale system or perform maintenance procedures. For more information, see Obtaining the Provisioned Grid Specification File on page 29, Expanding a StorageGRID Webscale System on page 31 or Maintenance Procedures on page 33. Procedure 1. Select File Open. Locate the grid specification file (not provisioned), and click Open. 2. Select Actions Modify New Grid. 3. Modify the StorageGRID Webscale design as required. 4. Click Finish, and save the grid specification file. The grid specification file is saved under the same name, if the Grid ID serial number has not been modified (the revision number is not updated), and under a different name, if the Grid ID serial number has been modified, following the file naming convention GID<Grid_ID>_REV1_GSPEC.xml. Obtaining the Provisioned Grid Specification File Before you edit the grid specification file, obtain a copy of the provisioned grid specification file from the grid. Then, you can open the latest grid specification file in Grid Designer to edit it. To expand a StorageGRID Webscale deployment or perform certain maintenance procedures, you must use the latest version of the provision grid specification file. Obtain this file by copying it from the StorageGRID Webscale deployment. Prerequisites Passwords.txt file for the grid Service laptop An SCP tool, such as WinSCP (available at download.php), to transfer files to and from the primary Admin Node _A0 StorageGRID Webscale 10.0

30 30 Grid Designer User Guide Procedure 1. At the primary Admin Node server, access a command shell and log in as root using the password listed in the Passwords.txt file. 2. Create a directory to which you will copy the latest provisioned grid specification file by entering: mkdir <directory> 3. Copy the latest grid specification file to the directory that you created by entering: copy-grid-spec <directory> 4. Use WinSCP or a similar tool to copy the GID<Grid_ID>_REV<revision_number>_GSPEC.xml file from the directory newly created directory to your service laptop. 5. Log out of the command shell by entering: exit StorageGRID Webscale _A0

31 Expanding a StorageGRID Webscale System 5 Procedures used to expand a deployed StorageGRID Webscale system Supported Expansions Grid Designer supports the following expansion procedures: Add Storage Capacity Adding storage capacity by adding Storage Nodes or Archive Node. Add Other Grid Nodes Add API Gateways. The grid node rules apply to grid expansions. For more information, see Chapter 3, Grid Topologies and Rules. Expanding a StorageGRID Webscale System You can add grid nodes to a data center site at any time. Prerequisites A copy of the latest provisioned grid specification file. To expand a StorageGRID Webscale deployment or perform maintenance procedures that require you to provision the StorageGRID Webscale system, you must use the latest version of the provision grid specification file. Obtain this file by exporting it from the StorageGRID Webscale system. For more information, see Obtaining the Provisioned Grid Specification File on page _A0 StorageGRID Webscale 10.0

32 32 Grid Designer User Guide A version of Grid Designer compatible with the provisioned grid specification file The IP address of each new grid node Expansion Guide Steps 1. From Grid Designer., select File Open. 2. Open the latest provisioned grid specification file. 3. Select Actions Expand Grid. The Current Topology table on the Topology tab summarizes the sites that are already included in the grid. 4. Add grid nodes using the same steps as for a new StorageGRID Webscale system. 5. Update information in all applicable tabs. A yellow field or tab indicates that required information is missing. 6. When you complete the expansion, click Finish. Grid Designer creates files in same directory as the provisioned grid specification file that was used to begin the expansion process. StorageGRID Webscale _A0

33 6 Maintenance Procedures Maintenance procedures that updating the provisioned grid specification file Changing IP Addresses The following IP addresses can be changed at any time: External NTP sources IP address Grid network IP address Supplementary IP address This procedure is part of a larger procedure described in the Administrator Guide. Prerequisites A copy of the latest provisioned grid specification file. To perform certain maintenance procedures, you must use the latest version of the provisioned grid specification file. Obtain this file from the StorageGRID Webscale system. For more information, see Obtaining the Provisioned Grid Specification File on page 29. A version of Grid Designer compatible with the currently installed version of StorageGRID Webscale software The new IP addresses Administrator Guide Procedure 1. From Grid Designer, select File Open. 2. Open the latest provisioned grid specification file _A0 StorageGRID Webscale 10.0

34 34 Grid Designer User Guide 3. Select Maintenance Change IP Addresses. 4. Click the Grid Network tab, the Supplementary Network tab, or the NTP tab. NOTE Both networks and NTP can be changed at the same time. 5. Make the required changes. You can change fields that have a white background. For a description of the fields, see Creating a New StorageGRID Webscale System on page Change values on other tabs as needed. 7. Click Finish. The grid specification file is saved, with the revision number increased by 1. This grid specification file can now be used to provision the Storage- GRID Webscale system. Post-requirements To complete the IP address changes, follow the instructions in the Administrator Guide. Decommissioning Grid Nodes You can update the grid specification file to indicate grid nodes to decommission. You can decommission Storage Nodes and API Gateway Nodes. Storage Node decommissioning is the process of permanently moving content from an existing Storage Node to other Storage Nodes in such a way that system operations are not affected, and the ILM policy is satisfied. After all content has been moved to other Storage Nodes, the old Storage Node is removed from the StorageGRID Webscale system. This procedure is part of a larger procedure described in the Maintenance Guide. StorageGRID Webscale _A0

35 Maintenance Procedures 35 Prerequisites A copy of the latest provisioned grid specification file. To perform certain maintenance procedures, you must use the latest version of the provisioned grid specification file. Obtain this file from the StorageGRID Webscale system. For more information, see Obtaining the Provisioned Grid Specification File on page 29. A version of Grid Designer compatible with the currently installed version of StorageGRID Webscale software. The name or names of the Storage Nodes to decommission Maintenance Guide Procedure 1. From Grid Designer, select File Open. 2. Open the latest grid specification file. 3. Select Maintenance Decommission a Storage or Gateway Node. 4. Select one or more Storage Nodes or API Gateway Nodes to decommission, and click OK. Figure 8: Selecting Storage Nodes for Decommissioning The grid specification file is saved, with the revision number increased by one _A0 StorageGRID Webscale 10.0

36 36 Grid Designer User Guide Post-requirements To complete the decommissioning procedure, follow the instructions in the Maintenance Guide. StorageGRID Webscale _A0

37 Glossary ACL ADC service ADE Admin Node Amazon S3 AMS service API API Gateway Node ARC service Archive Node atom Access control list Specifies what users or groups of users are allowed to access an object and what operations are permitted, for example, read, write, and execute. Administrative Domain Controller The ADC service maintains topology information, provides authentication services, and responds to queries from the LDR, CMN, and CLB services. The ADC service is present on the first three Storage Nodes installed at a site. Asynchronous Distributed Environment Proprietary development environment used as a framework for services within the StorageGRID Webscale system. The Admin Node provides services for the web interface, system configuration, and audit logs. See the primary Admin Node definition. Proprietary web service from Amazon for the storage and retrieval of data. Audit Management System The AMS service monitors and logs all audited system events and transactions to a text log file. The AMS service is present on the Admin Node. Application Programming Interface A set of commands and functions, and their related syntax, that enable software to use the functions provided by another piece of software. An API Gateway Node provides load balancing functionality to the StorageGRID Webscale system and is used to distribute the workload when multiple client applications are performing ingest and retrieval operations. API Gateway Nodes include a CLB service service. Archive The ARC service manages interactions with archiving middleware that controls nearline archival media devices such as tape libraries. The ARC service is present on the Archive Node. The Archive Node manages storage of data to nearline data storage devices such as such as tape libraries. Atoms are the lowest-level component of the container data structure, and generally encode a single piece of information. (Containers are sometimes used when interacting with the StorageGRID Webscalesystem through the StorageGRID API) _A0 StorageGRID Webscale 10.0

38 38 Grid Designer User Guide audit message AutoYaST BASE64 binding bundle Cassandra CBID CDMI CIDR CLB service Cloud Data Management Interface Information about an event occurring in the StorageGRID Webscale system that is captured and logged to a file. An automated version of the Linux installation and configuration tool YaST (Yet another Setup Tool), which is included as part of the SUSE Linux distribution. A standardized data encoding algorithm that enables 8-bit data to be converted into a format that uses a smaller character set, enabling it to safely pass through legacy systems that can only process basic (low order) ASCII text excluding control characters. See RFC 2045 for more details. The persistent assignment of a service (for example, an AMS service or SSM service) to the NMS service. This assignment is based on Storage- GRID Webscale topology. See also the Admin Node definition. A structured collection of configuration information used internally by various components of the StorageGRID Webscale system. Bundles are structured in container format. An open-source database that is scalable and distributed, provides high availability, and handles large amounts of data across multiple servers. Content Block Identifier A unique internal identifier of a piece of content within the StorageGRID Webscale system. Cloud Data Management Interface An industry standard defined by SNIA that includes a RESTful interface for object storage. For more information, see Classless Inter-Domain Routing A notation used to compactly describe a subnet mask used to define a range of IP addresses. In CIDR notation, the subnet mask is expressed as an IP address in dotted decimal notation, followed by a slash and the number of bits in the subnet. For example, /24. Connection Load Balancer The CLB service provides a gateway into the StorageGRID Webscale system for client applications connecting through HTTP. The CLB service is part of the API Gateway Node. See CDMI on page 38. StorageGRID Webscale _A0

39 Glossary 39 CMN service CMS service command container content block ID content handle CSTR DC DDS service distributed key value store Enablement Layer Configuration Management Node The CMN service manages system-wide configuration and grid tasks. The CMN service is present on the primary Admin Node. Content Management System The CMS service manages content replication according to the ILM rules specified by the ILM policy. The CMS service is present on the Storage Node. In HTTP, an instruction in the request header such as GET, HEAD, DELETE, OPTIONS, POST, or PUT. Also known as an HTTP method. Within the StorageGRID Webscale system, there are several different uses (and technologies) for the term container: SGAPI A container is a data structure used by the internals of StorageGRID Webscale software. In the StorageGRID API, an XML representation of a container is used to define queries or audit messages submitted using the POST command. Containers are used for information that has hierarchical relationships between components. The lowest-level component of a container is an atom. Containers can contain 0 to N atoms, and 0 to N other containers. CDMI Analogous to a file system directory, a container object allows access to child data objects. segmented objects When an object is split into segments, a container is created that lists the header information for all segments of the split object. This is then used by the LDR service to assemble the segmented object when it is retrieved by a client application. See the CBID definition. See the UUID definition. Null-terminated, variable length string. Data Center site. Distributed Data Store The DDS service interfaces with the distributed key-value store and manages object metadata. It distributes metadata copies to multiple instances of the distributed key-value store so that metadata is always protected against loss. Data storage and retrieval that unlike a traditional relational database manages data across grid nodes. The Enablement Layer is used during installation to customize the Linux operating system installed on each grid node. Only the _A0 StorageGRID Webscale 10.0

40 40 Grid Designer User Guide packages needed to support the services hosted on the grid node are retained, which minimizes the overall footprint occupied by the operating system and maximize the security of each grid node. fibre channel GDU GPT Grid ID signed text block grid node grid specification file grid task HTTP HTTPS A networking technology primarily used for storage. Grid Deployment Utility A StorageGRID Webscale software utility used to facilitate the installation of software on all grid nodes. GDU is installed and available on the primary Admin Node. Grid Provisioning Tool A software tool included with StorageGRID Webscale software that permits you to provision a StorageGRID Webscale system for installation, maintenance, or expansion. GPT creates and maintains an encrypted repository of information about the system that is required to maintain the StorageGRID Webscale system and recover failed grid nodes. A BASE64 encoded block of cryptographically signed data that contains the grid ID which must match the grid ID (gid) element in the grid specification file. See also provisioning. The basic software building block for the StorageGRID Webscale system, for example, Admin Node or Storage Node. Each grid node type consists of a set of services that perform a specialized set of tasks. An XML file that provides a complete technical description of a specific StorageGRID Webscale deployment. It describes the system s topology and specifies the hardware, options, grid nodes, network settings and time synchronization for the deployment. System-wide scripts used to trigger various actions that implement specific changes to the StorageGRID Webscale system. For example, most maintenance and expansion procedures involve running grid tasks. Grid tasks are typically long-term operations that span many entities within the StorageGRID Webscale system. See also the Task Signed Text Block definition. Hyper-Text Transfer Protocol A simple, text based client/ protocol for requesting hypertext documents from a server. Hyper-Text Transfer Protocol, Secure URIs that include HTTPS indicate that the transaction must use HTTP with an additional encryption/authentication layer and often, a different default port number. The encryption layer is usually provided by SSL or TLS. HTTPS is widely used on the internet for secure communications. StorageGRID Webscale _A0

41 Glossary 41 ILM LAN latency LDR service LUN metadata namespace nearline NFS NMS service NMS MI node ID Information Lifecycle Management A process of managing content storage location and duration based on content value, cost of storage, performance access, regulatory compliance and other such factors. See also the Admin Node and storage pool definitions. Local Area Network A network of interconnected computers that is restricted to a small area, such as a building or campus. A LAN can be considered a node to the Internet or other wide area network. Contrast with WAN. Time duration for processing a transaction or transmitting a unit of data from end to end. When evaluating system performance, both throughput and latency need to be considered. See the throughput definition. Local Distribution Router The LDR service manages the storage and transfer of content within the StorageGRID Webscale system. The LDR service is present on the Storage Node. See the object store definition. Information related to or describing an object stored in the Storage- GRID Webscale system; for example, ingest time. A set whose elements are unique names. There is no guarantee that a name in one namespace is not repeated in a different namespace. A term describing data storage that is neither online (implying that it is instantly available like spinning disk) nor offline (which could include offsite storage media). An example of a nearline data storage location is a tape that is loaded in a tape library, but is not necessarily mounted. Network File System A protocol (developed by SUN Microsystems) that enables access to network files as if they were on local disks. Network Management System The NMS service provides a webbased interface for managing and monitoring the StorageGRID Webscale system. The NMS service is present on the Admin Node. See also NMS MI and Admin Node definitions. NMS Management Interface The web-based interface for managing and monitoring the StorageGRID Webscale system provided by the NMS software component. See also NMS service definition. An identification number assigned to a service within the Storage- GRID Webscale system. Each service (such as an NMS service or ADC _A0 StorageGRID Webscale 10.0

42 42 Grid Designer User Guide service) must have a unique node ID. The number is set during system configuration and tied to authentication certificates. NTP object object storage object store object segmentation OID primary Admin Node provisioning purge quorum Network Time Protocol A protocol used to synchronize distributed clocks over a variable latency network such as the internet. An artificial construct used to describe a system that divides content into data and metadata. Object Storage is an approach where stored data is accessed by unique identifiers rather than by a user-defined hierarchy of directories and files. Each object has both data (for example, a picture) and metadata (for example, the date the picture was taken). Object storage operations typically act on entire objects as opposed to reading and writing bytes as is commonly done with files, and is typically provided via APIs or HTTP instead of NAS (CIFS/NFS) or block protocols (iscsi/ FC/FCOE). A configured file system on a disk volume. The configuration includes a specific directory structure and resources initialized at system installation. A StorageGRID Webscale process that splits a large object into a collection of small objects (segments) and creates a segment container to track the collection. The segment container contains the UUID for the collection of small objects as well as the header information for each small object in the collection. All of the small objects in the collection are the same size. See also the segment container definition. Object Identifier The unique identifier of an object. Admin Node that hosts the CMN service. There is one per Storage- GRID Webscale system. See also the Admin Node definition. The process of generating a SAID package and GPT repository. This is done on the primary Admin Node using the provision command. The new or updated SAID package is saved to the Provisioning Media. See also the grid specification file and SAID definitions. The act of permanently removing an object from the StorageGRID Webscale system. A simple majority: 50% + 1. Some system functionality requires a quorum of the total number of a particular service type. StorageGRID Webscale _A0

43 Glossary 43 SAID SATA SCSI segment container Server Server Manager service SGAPI SLES SQL ssh Software Activation and Integration Data Generated during provisioning, the SAID package contains site-specific files and software needed to install a StorageGRID Webscale system. Serial Advanced Technology Attachment A connection technology used to connect server and storage devices. Small Computer System Interface A connection technology used to connect servers and peripheral devices such as storage systems. An object created by the StorageGRID Webscale system during the segmentation process. Object segmentation splits a large object into a collection of small objects (segments) and creates a segment container to track the collection. A segment container contains the UUID for the collection of segmented objects as well as the header information for each segment in the collection. When assembled, the collection of segments creates the original object. See also the object segmentation definitions. Used when specifically referring to hardware. May also refer to a virtual machine. Application that runs on all grid nodes, supervises the starting and stopping of services, and monitors all services on the grid node. A unit of the StorageGRID Webscale system such as the ADC service, NMS service, or SSM service. Each service performs unique tasks critical to the normal operations of a StorageGRID Webscale system. StorageGRID Application Programming Interface A set of commands and functions, and their related syntax, that provides client applications with the ability to connect directly to an LDR or CLB service. SUSE Linux Enterprise Server A commercial distribution of the SUSE Linux operating system, used with the StorageGRID Webscale system. Structured Query Language An industry standard interface language for managing relational databases. An SQL database is one that supports the SQL interface. Secure Shell A Unix shell program and supporting protocols used to log in to a remote computer and execute commands over an authenticated and encrypted channel _A0 StorageGRID Webscale 10.0