Dell DX6004S DX Object Storage SCSP Proxy Overview - Page 4

Introduction

Page 4 highlights

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. This reverse proxy can serve several other purposes as well, both in production deployments and in test environments. Specifically, the SCSP Proxy supports the following types of interactions: • Basic SCSP Proxy for a local cluster • Remote cluster coordination and communication • Validation of incoming client requests for proper syntax and formatting 1.1. Basic SCSP Proxy In a local cluster deployment, the SCSP Proxy handles all local SCSP traffic and manages the associated communication with the local DX Storage cluster. The SCSP Proxy listens for any inbound SCSP communications on the configured port and determines which DX Storage node to send the initial request to. For optimal performance, the SCSP Proxy caches open connections to DX Storage for reuse. For more information, see one of the following sections: • Section 1.1.1, "Getting a List of DX Storage Cluster IPs" • Section 1.1.2, "About Expect: 100-continue Behavior" • Section 1.1.3, "About Location Headers" 1.1.1. Getting a List of DX Storage Cluster IPs The SCSP Proxy intercepts GET / and HEAD / requests and responds with information it stores internally about itself and about the cluster for which it serves as a forward proxy. Only GET / and HEAD / requests result in this type of special handling by the SCSP Proxy. Query arguments are not processed, even when the resource is empty. A request with a query argument is forwarded as-is to the cluster and receives no special processing by the Proxy. The Proxy responds to a GET / request from a client running in a private network with the Proxy's list of DX Storage IP addresses and data and metadata describing the Proxy's DX Storage cluster. You can prevent the Proxy from returning cluster IP addresses using the configuration parameter reportHosts. For more information about configuration parameters, see Chapter 3, Configuration Parameters 1.1.1.1. Scsp-Proxy-Cluster Request Header The optional Scsp-Proxy-Cluster: cluster-name request header, if included with a request, causes the Proxy to first compare the case-sensitive cluster-name against the Proxy's own Copyright © 2010 Caringo, Inc. All rights reserved 1 Version 1.2 December 2010

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19

Copyright © 2010 Caringo, Inc.
All rights reserved
1
Version 1.2
December 2010
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.
This reverse proxy can serve several other purposes as well, both in production deployments and in
test environments.
Specifically, the SCSP Proxy supports the following types of interactions:
Basic SCSP Proxy for a local cluster
Remote cluster coordination and communication
Validation of incoming client requests for proper syntax and formatting
1.1. Basic SCSP Proxy
In a local cluster deployment, the SCSP Proxy handles all local SCSP traffic and manages the
associated communication with the local DX Storage cluster. The SCSP Proxy listens for any
inbound SCSP communications on the configured port and determines which DX Storage node to
send the initial request to.
For optimal performance, the SCSP Proxy caches open connections to DX Storage for reuse.
For more information, see one of the following sections:
Section 1.1.1, “Getting a List of DX Storage Cluster IPs”
Section 1.1.2, “About Expect: 100-continue Behavior”
Section 1.1.3, “About Location Headers”
1.1.1. Getting a List of DX Storage Cluster IPs
The SCSP Proxy intercepts GET / and HEAD / requests and responds with information it stores
internally about itself and about the cluster for which it serves as a forward proxy. Only GET / and
HEAD / requests result in this type of special handling by the SCSP Proxy.
Query arguments are not processed, even when the resource is empty. A request with a query
argument is forwarded as-is to the cluster and receives no special processing by the Proxy.
The Proxy responds to a GET / request from a client running in a private network with the Proxy's
list of DX Storage IP addresses and data and metadata describing the Proxy's DX Storage cluster.
You can prevent the Proxy from returning cluster IP addresses using the configuration parameter
reportHosts
. For more information about configuration parameters, see
Chapter 3,
Configuration
Parameters
1.1.1.1. Scsp-Proxy-Cluster Request Header
The optional Scsp-Proxy-Cluster:
cluster-name
request header, if included with a request,
causes the Proxy to first compare the case-sensitive
cluster-name
against the Proxy's own