Dell DX6004S DX Object Storage SCSP Proxy Overview - Page 13

Validation Mode

Get Dell DX6004S PDF manuals and user guides View all Dell DX6004S manuals
Add to My Manuals
Save this manual to your list of manuals

Page 13 highlights

• 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. • You can start the Proxy using proxyservice.py under any of the following circumstances: Run the following command from the directory where the install file was unzipped (or from any location if you have configured your Python path to point to the installed location): python2.5 proxyservice.py options where options are discussed in the following table. proxyservice.py startup option --staticlocator --cfgfile path-to-scspproxy.cfg --pidfile path-to-scspproxy.pid Meaning Start the Proxy and use the static locator. Access the Proxy configuration file from the specified location. Specify the location of the Proxy service Process Identifier (PID) file. The default location is /var/run/ scspproxy.pid. To validate if the proxy is running in front of a DX Storage cluster, enter the Proxy's IP address and port in a web browser's location or address field. If you see a DX Storage status page the proxy is working correctly. 2.3.1. Validation Mode In addition to the basic validation included in the DX Storage SDK, the SCSP Proxy includes a validation mode that provides validation for incoming SCSP requests. This validation checks the syntax for common operations like adding query arguments and creating lifepoint headers. The SCSP Proxy does not discern between clients created using the DX Storage SDK and those that were created without it. Validation mode and execution mode are mutually exclusive. Requests are not sent to DX Storage while in validation mode but are instead analyzed by the Proxy for a response. If a query fails validation, it returns an error describing the reason for the failed validation. Successful status codes in validation mode follow: • 200 for GET, HEAD, and DELETE • 201 for POST, PUT, COPY, and APPEND Errors are returned as one of the following codes: • 400 for any validation error for a known method Copyright © 2010 Caringo, Inc. All rights reserved 10 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
10
Version 1.2
December 2010
•
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.
•
You can start the Proxy using
proxyservice.py
under any of the following circumstances:
Run the following command from the directory where the install file was unzipped (or from any
location if you have configured your Python path to point to the installed location):
python2.5 proxyservice.py
options
where
options
are discussed in the following table.
proxyservice.py startup option
Meaning
--staticlocator
Start the Proxy and use the static locator.
--cfgfile
path-to-scspproxy.cfg
Access the Proxy configuration file from the
specified location.
--pidfile
path-to-scspproxy.pid
Specify the location of the Proxy service
Process Identifier (PID) file.
The default location is
/var/run/
scspproxy.pid
.
To validate if the proxy is running in front of a DX Storage cluster, enter the Proxy's IP address and
port in a web browser's location or address field. If you see a DX Storage status page the proxy is
working correctly.
2.3.1. Validation Mode
In addition to the basic validation included in the DX Storage SDK, the SCSP Proxy includes a
validation mode
that provides validation for incoming SCSP requests. This validation checks the
syntax for common operations like adding query arguments and creating lifepoint headers. The
SCSP Proxy does not discern between clients created using the DX Storage SDK and those that
were created without it.
Validation mode and execution mode are mutually exclusive. Requests are not sent to DX Storage
while in validation mode but are instead analyzed by the Proxy for a response. If a query fails
validation, it returns an error describing the reason for the failed validation.
Successful status codes in validation mode follow:
•
200 for GET, HEAD, and DELETE
•
201 for POST, PUT, COPY, and APPEND
Errors are returned as one of the following codes:
•
400 for any validation error for a known method