Dell DX6000 Overview
Dx object storage scsp proxy overview version 1.2
Hide thumbs
Also See for DX6000:
- Hardware owner's manual (198 pages) ,
- Getting started with your system (124 pages) ,
- Application manual (81 pages)
Table of Contents
Related Manuals for Dell DX6000
Summary of Contents for Dell DX6000
- Page 1 SCSP Proxy Overview Version 1.2...
- Page 2 SCSP Proxy Overview: Version 1.2 Copyright © 2010 Caringo, Inc. All Rights Reserved. No part of this document may be reproduced, transmitted, or transcribed without the written consent of Caringo, Inc.
-
Page 3: Table Of Contents
Table of Contents 1. Introduction ......................... 1 1.1. Basic SCSP Proxy ....................1 1.1.1. Getting a List of DX Storage Cluster IPs ............1 1.1.2. About Expect: 100-continue Behavior .............. 3 1.1.3. About Location Headers ................. 3 1.2. Remote Cluster Communication and Coordination ............3 1.2.1. -
Page 4: Introduction
Chapter 1. Introduction The SCSP Proxy accepts HTTP requests from a host network, forwards them to a DX Storage cluster, handles redirects transparently, and then supplies the response back to the requestor. In many deployments, a DX Storage cluster might be isolated on an internal network, protecting it from undesired interaction with the host network, and also protecting the host network from services like PXE boot and multicast traffic that can interfere with other network resources. - Page 5 configured cluster name. If the names do not match, no node IP addresses are returned in the response. If Scsp-Proxy-Cluster is not present, the request uses the configured cluster name and the list of node IP addresses reflects the currently known node IPs for that cluster. In either case, the response metadata includes a response header with the same name containing the cluster name used by the Proxy.
-
Page 6: About Expect: 100-Continue Behavior
Reason for empty node list Meaning Indicates the Proxy's reportHosts configuration parameter is disabled set to False. 1.1.1.3. Response Body The body of the response to a GET / is Content-Type text/plain list of IP addresses of DX Storage nodes local to that proxy, one address per CRLF-terminated line. The Content-Length header calculation is based on the number of bytes in this list of CRLF terminated IPs. -
Page 7: Examples Of Using /_Proxy Syntax
Syntax Description If the object exists in the local cluster the information is returned. Otherwise, the request is sent to each remote cluster in random order. If no cluster is able to locate the data, the error response from the local server is returned. -
Page 8: Remote Synchronous Writes And Updates
Note Because you are working with the default cluster domain, the domain name does not need to be sent as the Host in the request. For unnamed objects, POST authentication is supported only in the default cluster domain. • Remote synchronous write POST of an unnamed object to the default cluster domain, which has POST authentication enabled POST /_proxy/cluster-name/?replicate=immediate For more information about remote synchronous write, see the next section. - Page 9 response body. Similar to the individual Info method, the response for a successful AggregateInfo method execution is a 200 code. The following is a sample checkpoint manifest stream. All object names must be URL-encoded so you must use percent encoding to escape special characters in named objects, including space. All line terminators must be CRLF: 1C1AF51688DA4F752CD26E6CD115A6A5 mybucket/photos/marketing/photo.jpg...
- Page 10 Response for stream uuid = f6a0c60d53dd1047ce670c747b1aba91 HTTP/1.1 200 OK Castor-System-Cluster: DR Cluster Castor-System-Created: Tue, 03 Aug 2010 18:49:27 GMT Content-Length: 11 Content-Type: application/x-www-form-urlencoded Last-Modified: Tue, 03 Aug 2010 18:49:27 GMT Etag: "f6a0c60d53dd1047ce670c747b1aba91" Date: Tue, 03 Aug 2010 18:49:28 GMT Server: CAStor Cluster/4.0.2 If the first line does not have a valid UUID, the proxy responds with a single error message in the response body stating that the checkpoint stream is incorrectly formatted and stops processing.
-
Page 11: Installing, Configuring And Running Scsp Proxy
Chapter 2. Installing, Configuring and Running SCSP Proxy The SCSP Proxy installs as an RPM and is managed very similarly to other RPM packages. If the SCSP Proxy is being utilized on a Cluster Services Node (CSN), the installation and base configuration are performed automatically as part of CSN setup. -
Page 12: Configuring The Scsp Proxy
• If you use a CSN, to upgrade the SCSP Proxy, copy and unzip the release distribution, and run the following commands in the order shown: $ sudo su - # /etc/init.d/scspproxy stop # cd scspproxy-copy-dir # ./caringo-scspproxy-install.sh • If you do not use a CSN and instead run the proxy from a RHEL 5.5 server, extract the SDK on the server and install the enclosed RPM. -
Page 13: Validation Mode
• To use startup options. • Using the startup/shutdown scripts: /etc/init.d/scspproxy start /etc/init.d/scspproxy stop Use the startup/shutdown scripts if the Proxy is installed on a CSN, or if it is installed on RHEL and you do not want to use optional startup options. •... - Page 14 • The SDK returns a 50x for general request errors such as bad host name, unknown method, HTTP syntax errors, and so on. Your client might return other response codes for these types of errors. Outside of validation mode, headers or query arguments that are invalid are either silently ignored or trigger an error at the DX Storage server layer and return as SCSP errors to the client.
- Page 15 Validation GET HEAD POST DELETE COPY APPEND Query Argument: newhashtype Query Argument: countreps Query Argument: indirect Copyright © 2010 Caringo, Inc. Version 1.2 All rights reserved December 2010...
-
Page 16: Configuration Parameters
Chapter 3. Configuration Parameters You can configure the SCSP Proxy using either the Cluster Services Node (CSN) console or by editing the scspproxy.cfg file. If you use CSN, see the CSN Installation and Configuration Guide. 3.1. Configuring the Proxy by Editing scspproxy.cfg To configure the SCSP proxy when you are not using CSN, edit /etc/caringo/scspproxy/ scspproxy.cfg. - Page 17 [connectionPool] 200 (minimum) to 4000 The number of connections maxStoredConnections (maximum) the proxy saves for reuse. Dell recommends you set this parameter to five times the number of DX Storage cluster nodes. [connectionPool] The amount of time in seconds connectTimeOut...
-
Page 18: Hosts.cfg
# PARAMETERS [proxy] port = 80 interface = 192.168.1.1 validationMode = False [log] #<10 = CHATTER, which includes twisted.internet logs #10 = DEBUG - Turns on detail message handling logs #20 = INFO - Turns on request and response echo and connection pool logging #40 = ERROR - Turns on error logging level = 40 #default = localhost... - Page 19 Option Name Description character hex string. May be the DNS name for the cluster but that is not required. RemoteAddress The IP address for the remote proxy the local proxy will communicate with. May not contain whitespaces. Port The port from which the remote proxy will listen incoming requests.