Dell DX6004S DX Object Storage Application Guide

Dell DX6004S Manual

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

Dell DX6004S manual content summary:

  • Dell DX6004S | DX Object Storage Application Guide - Page 1
    DX Object Storage Application Guide Version 5.0
  • Dell DX6004S | DX Object Storage Application Guide - Page 2
    DX Object Storage Application Guide: Version 5.0 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.
  • Dell DX6004S | DX Object Storage Application Guide - Page 3
    Table of Contents 1. Introduction to DX Storage Objects 1 1.1. Introducing Named Objects 1 1.2. Summary of Named Objects and Unnamed Objects 2 1.3. Common Named Object Terminology 2 1.4. About DX Storage Object Types 3 1.5. Bucket and Object Naming Rules 3 1.6. Simple Examples of Creating
  • Dell DX6004S | DX Object Storage Application Guide - Page 4
    5.3.3. Other Normal READ Responses 25 5.4. Error Responses to READ 25 6. SCSP WRITE ...27 6.1. Introduction to WRITE 27 6.1.1. About the Expect: 100-continue Header and WRITE 28 6.1.2. About Replicate On Write 28 6.2. Named Object WRITE Details 28 6.3. Unnamed Object WRITE Details 28 6.4.
  • Dell DX6004S | DX Object Storage Application Guide - Page 5
    13.3. Example: Creating Bucket Owners 51 13.4. Examples of Creating Buckets and Named Objects 51 14. Managing Security for Domain Managers 54 14.1. What Domain Managers Need to Know 54 14.2. About Domain Manager Tasks and Responsibilities 54 14.3. Examples of Updating Domain and Administrator
  • Dell DX6004S | DX Object Storage Application Guide - Page 6
    Resource Identifiers (URIs)" • Section 1.9, "Concepts for Unnamed Objects" • Section 1.10, "Document Typographical Conventions" 1.1. Introducing Named Objects DX Storage version 5.0 supports the option of storing and accessing objects in a DX Storage public or private cloud by name or by UUID as
  • Dell DX6004S | DX Object Storage Application Guide - Page 7
    • Both named and unnamed objects in any proportion 1.2. Summary of Named Objects and Unnamed Objects You might find it useful to keep the following in mind when planning to implement named and unnamed objects in your cluster: • Unnamed objects: • Are named by DX Storage • Are created, updated,
  • Dell DX6004S | DX Object Storage Application Guide - Page 8
    the same as an object named /folder2/object.txt. These legitimate names specify two different objects. 1.4. About DX Storage Object Types DX Storage supports the following general types of objects: • Immutable unnamed objects, which can be deleted but not changed. If you delete an unnamed object,
  • Dell DX6004S | DX Object Storage Application Guide - Page 9
    If you are not sure how to create a domain, see the DX Object Storage Administration Guide or contact your cluster administrator. The following examples assume that the domain is named test.example.com and that you are sending commands to a node
  • Dell DX6004S | DX Object Storage Application Guide - Page 10
    servers and browsers. While it is possible that additional access protocols will be added to DX Storage in the future, HTTP is the only protocol supported for the URI at this time. A DX Storage cluster is addressed using either the DNS name or the IP address of one of the nodes
  • Dell DX6004S | DX Object Storage Application Guide - Page 11
    1.8.2. Commonly Used Security Terminology Following is a list of commonly used terms: • Security realm: (Also referred to as a realm or a user list.) A list of user names and hashed passwords. Associating a realm with a bucket enables users in the realm privileges to execute specific SCSP operations
  • Dell DX6004S | DX Object Storage Application Guide - Page 12
    doesn't help to describe it or name it, because these can be ambiguous. No one else can retrieve your coat, unless they have the coat check. A DX Storage UUID is a 128-bit, 16-octet, case-insensitive, opaque sequence of bits. In text-based languages and protocols, notably the Simple Content Storage
  • Dell DX6004S | DX Object Storage Application Guide - Page 13
    Note An anchor stream can be updated at a maximum frequency of once per second. Attempting more frequent updates can produce unpredictable results with the stored object version. 1.10. Document Typographical Conventions Unless otherwise noted, the following typographical conventions are used in
  • Dell DX6004S | DX Object Storage Application Guide - Page 14
    for a particular request is the first node in the cluster that receives the request from the application. After a PAN receives a request, it decides whether to service the request itself or to request the application to redirect it to one of the other nodes in the cluster. Because the PAN takes
  • Dell DX6004S | DX Object Storage Application Guide - Page 15
    to use mDNS. mDNS is often referred to by the name Zeroconf, the collective name form DNS and DNS Service Discovery to enable zero-configuration networking. mDNS is supported for all deployments and provides the most flexibility because it provides applications with a list of storage nodes to choose
  • Dell DX6004S | DX Object Storage Application Guide - Page 16
    2.2.5. Using a Single Static IP Address The simplest but least recommended (and least supported) way for an application to address a DX Storage cluster is to assign disadvantage that, if the sole PAN is taken out of service or fails completely, the application cannot send requests to the
  • Dell DX6004S | DX Object Storage Application Guide - Page 17
    simplifies integration with DX Storage by providing client library support that includes handling for specific SCSP behaviors to programmers on the high availability code path of your client application. Instead, Dell recommends you perform POST and DELETE on buckets using a separate initialization
  • Dell DX6004S | DX Object Storage Application Guide - Page 18
    Most of these client libraries will take care of the low-level protocol issues for you. Formatting the requests and interpreting the responses are usually much easier with an existing framework. In fact, much of the SCSP discussion above can be skipped, allowing the framework to do the work for you.
  • Dell DX6004S | DX Object Storage Application Guide - Page 19
    DX Storage automatically load balances requests by causing them to be redirected to a less busy node in the cluster that is capable of servicing the request, this multi-threaded client strategy can be very effective in improving overall performance when necessary, because each client thread (or
  • Dell DX6004S | DX Object Storage Application Guide - Page 20
    . Moreover, DX Storage assumes communication with an HTTP/1.1 compliant client application. In DX Storage version 5.0 for the first time, SCSP supports authentication and authorization on all SCSP operations. For details, see Chapter 12, Introduction to Object Security . This chapter provides an
  • Dell DX6004S | DX Object Storage Application Guide - Page 21
    4.2. HTTP Overview The following is paraphrased from the HTTP/1.1 specification. The HTTP protocol is a request/response protocol. A client sends a request to the DX Storage server in the form of a request method, URI, and protocol version, followed by a MIME-like message containing request
  • Dell DX6004S | DX Object Storage Application Guide - Page 22
    ", 417: "Expectation Failed", 500: "Internal Server Error", 501: "Not Implemented", 502: "Bad Gateway", 503: "Service Unavailable", 504: "Gateway Time-out", 505: "HTTP Version not supported", 507: "Insufficient Storage Space" 4.3.2. Redirect Responses Client applications must be able to accept and
  • Dell DX6004S | DX Object Storage Application Guide - Page 23
    in DX Storage. Check your logs for more information, and contact your support representative if necessary. HTTP/1.1 501 Not Implemented Date: Wed, 1 Sept . For more information, see Appendix A, Content Header Metadata HTTP/1.1 503 Service Unavailable Date: Wed, 1 Sept 2010 15:59:02 GMT Server:
  • Dell DX6004S | DX Object Storage Application Guide - Page 24
    -Length: 0 Content-Type: text/html The preceding response indicates a request was received with an HTTP version other than 1.1. DX Storage supports HTTP/1.1 only. 4.6. Normal Response Headers The following table shows normal response headers that can be returned with SCSP operations. Information
  • Dell DX6004S | DX Object Storage Application Guide - Page 25
    Header Castor-System-CID SCSP operations INFO, READ, DELETE Meaning operations on an unnamed anchor stream object or to delete an unnamed immutable object. The UUID of the domain, bucket, or named object's parent. This UUID cannot be used for any SCSP operation. Castor-SystemCreated INFO, READ,
  • Dell DX6004S | DX Object Storage Application Guide - Page 26
    Header Last-Modified lifepoint Replica-Count Server SCSP operations All READ, INFO INFO All Meaning on WRITE. For more information, see Section 18.2.4, "Expires". Standard HTTP header. Returned for an object that was created with a lifepoint header. See Chapter 16, Using Lifepoint Metadata Headers
  • Dell DX6004S | DX Object Storage Application Guide - Page 27
    the stream content as it is being read, you must add the query argument ? validate=yes to the URI. The content digest is then be computed and compared at the end. A hash mismatch will cause the socket connection to be dropped before the final bytes are sent. GET /name-or-uuid
  • Dell DX6004S | DX Object Storage Application Guide - Page 28
    User-Agent: DX Storage Client/0.1 5.2. Unnamed Object READ Details If the UUID refers to an unnamed anchor stream object, you must add alias=yes to the URI, as shown in the following example. Failure to include alias=yes for an unnamed object anchor stream read results in a 403 Forbidden response
  • Dell DX6004S | DX Object Storage Application Guide - Page 29
    Castor-System-Version: 1287187180.959 Content-Length: 0 Last-Modified: Fri, 15 Oct 2010 18:35:56 GMT lifepoint: [] reps=16 Etag: "da8bfbb04d089b9c22ae77747f327233" Date: Sat, 16 Oct 2010 00:41:23 GMT Server: CAStor Cluster/5.0.0 The initial 401 (Unauthorized) is a normal part of HTTP authentication
  • Dell DX6004S | DX Object Storage Application Guide - Page 30
    further notice. 5.4. Error Responses to READ The DX Storage cluster can return the following responses when the specified content cannot be found or there is a problem with the READ request itself. Copyright © 2010 Caringo, Inc. All rights reserved 25 Version 5.0 December 2010
  • Dell DX6004S | DX Object Storage Application Guide - Page 31
    GMT Server: CAStor Cluster/5.0.0 Connection: close Content-Length: 24 Content-Type: text/html CRLF Host header is required. The preceding response indicates a problem with the READ request, such as missing mandatory headers, invalid message body, or any other violation of HTTP/1.1 by the GET request
  • Dell DX6004S | DX Object Storage Application Guide - Page 32
    Chapter 6. SCSP WRITE The following topics in this chapter discuss details about SCSP WRITE: • Section 6.1, "Introduction to WRITE" • Section 6.3, "Unnamed Object WRITE Details" • Section 6.4, "Normal Responses to WRITE" • Section 6.5, "Error Responses to WRITE" 6.1. Introduction to WRITE This
  • Dell DX6004S | DX Object Storage Application Guide - Page 33
    DX Storage makes no assumptions about User-Agent (except that it is an HTTP/1.1 client). The Host header is mandatory and must conform to the requirements of Section 14.23 of the HTTP/1.1 spec. 6.1.1. About the Expect: 100-continue Header and WRITE The Expect: 100-continue header tells the server
  • Dell DX6004S | DX Object Storage Application Guide - Page 34
    when the content length header does not match the actual content length, the specified content cannot be written to the cluster, or if there is a problem with the WRITE request itself. HTTP/1.1 400 Bad Request Date: Wed, 1 Sept 2010 15:59:02 GMT Server: CAStor Cluster/5.0.0 Content-Type: text/html
  • Dell DX6004S | DX Object Storage Application Guide - Page 35
    HTTP/1.1 411 Length Required Date: Wed, 1 Sept 2010 15:59:02 GMT Server: CAStor Cluster/5.0.0 Content-Type: text/html Content-Length: 93 CRLF WRITE requests must include a Content-Length header specifying the exact byte-length of the content stream to be stored. The preceding response indicates the
  • Dell DX6004S | DX Object Storage Application Guide - Page 36
    Chapter 7. SCSP DELETE The following topics in this chapter discuss details about SCSP DELETE: • Section 7.1, "Introduction to DELETE" • Section 7.2, "Unnamed Object DELETE Details" • Section 7.3, "Named Object DELETE Details" • Section 7.4, "Normal Responses to DELETE" • Section 7.5, "Error
  • Dell DX6004S | DX Object Storage Application Guide - Page 37
    7.2. Unnamed Object DELETE Details The UUID of a deleted object is never reused, whether the object is immutable or mutable. The query argument ?alias=yes must be added to the URI portion of the HTTP request line for unnamed anchor stream object, as shown in the following example. Failure to include
  • Dell DX6004S | DX Object Storage Application Guide - Page 38
    DELETE The DX Storage cluster might return the following responses when the specified content cannot be deleted from the cluster or there is a problem with the DELETE request itself. HTTP/1.1 400 Bad Request Date: Wed, 1 Sept 2010 15:59:02 GMT Server: CAStor Cluster/5.0.0 Connection: close Content
  • Dell DX6004S | DX Object Storage Application Guide - Page 39
    Chapter 8. SCSP UPDATE The following topics in this chapter discuss details about SCSP UPDATE: • Section 8.1, "Introduction to UPDATE" • Section 8.2, "Unnamed Object UPDATE Details" 8.1. Introduction to UPDATE This section discusses general information about SCSP UPDATE that applies to both named
  • Dell DX6004S | DX Object Storage Application Guide - Page 40
    illustrated below. Note that the query argument alias=yes is optional on an UPDATE because this operation applies to anchor streams only. The normal response to a PUT request, similar to a POST, is a 201 (Created) response. 8.3. Normal Responses to UPDATE For a list of response headers, see Section
  • Dell DX6004S | DX Object Storage Application Guide - Page 41
    Chapter 9. SCSP COPY The following topics in this chapter discuss details about SCSP COPY: • Section 9.1, "Introduction to COPY" • Section 9.2, "Unnamed Object COPY Details" 9.1. Introduction to COPY This section discusses general information about SCSP COPY that applies to both named and unnamed
  • Dell DX6004S | DX Object Storage Application Guide - Page 42
    acme-meta-* and lifepoint headers in the preceding example are ignored. If the client provides a Content-MD5 header with the APPEND request, DX Storage computes the digest of the content data plus the appended data and compares it with the provided MD5 hash. This assumes the client either has access
  • Dell DX6004S | DX Object Storage Application Guide - Page 43
    10.2. Unnamed Object APPEND Details The query argument alias=yes is required, and the object specified by the included UUID must be an anchor stream in DX Storage. DX Storage returns a 404 (Not Found) error in any of the following circumstances: • The object is not an anchor stream; that is, you try
  • Dell DX6004S | DX Object Storage Application Guide - Page 44
    Chapter 11. SCSP INFO The following topics in this chapter discuss details about SCSP INFO: • Section 11.1, "Introduction to INFO" • Section 11.2, "Unnamed Object INFO Details" • Section 11.4, "Error Responses to INFO" 11.1. Introduction to INFO This section discusses general information about SCSP
  • Dell DX6004S | DX Object Storage Application Guide - Page 45
    2096EFA659295BBB819D1FECCE77D2EF Content-Length: 0 The preceding response means the requested stream has been located, but that another node in the cluster will service the request for meta-information. Furthermore, all future requests of this DX Storage cluster should be made through the new access
  • Dell DX6004S | DX Object Storage Application Guide - Page 46
    11.3.2. Normal INFO Responses for Named Objects INFO on a domain: HTTP/1.1 401 Unauthorized WWW-Authenticate: Digest realm="cluster.example.com/_administrators", / nonce="05d0a60ee1f44361f449496505e05116", opaque="fd9c8e14e20fb7c13408c049b7d222af", stale=false, qop="auth", algorithm=MD5 WWW-
  • Dell DX6004S | DX Object Storage Application Guide - Page 47
    Responses to INFO The following responses may be returned by the DX Storage cluster when the specified content cannot be found or there is a problem with the INFO request itself. HTTP/1.1 400 Bad Request Date: Wed, 1 Sept 2010 15:59:02 GMT Server: CAStor Cluster 5.0.0 Content-Length: 24 Content
  • Dell DX6004S | DX Object Storage Application Guide - Page 48
    Chapter 12. Introduction to Object Security Starting with DX Storage version 5.0, you can optionally provide security for domains, buckets, named objects, and unnamed objects. Because the UUIDs of unnamed objects are difficult to remember or to guess, this chapter focuses on providing security for
  • Dell DX6004S | DX Object Storage Application Guide - Page 49
    • Cluster administrators: The chapter on managing tenants in the DX Object Storage Administration Guide. • Application developers: Chapter 13, Managing Security for Application Developers • Domain managers: Chapter 14, Managing Security for Domain Managers 12.2. Security Realm Overview By default,
  • Dell DX6004S | DX Object Storage Application Guide - Page 50
    the user list yet for a bucket, DX Storage returns a 401 (Unauthorized). These errors stop after the realm cache interval has passed. 12.3. About Authorization Header Syntax You set an authorization specification using the Castor-Authorization header, which has the following syntax: Castor-
  • Dell DX6004S | DX Object Storage Application Guide - Page 51
    Make sure you use consistent URIs when you are accessing unnamed objects with the Castor-Authorization header. 12.3.1. About Realm Names The following topics discuss the syntax you must use for realm-name in the authorization specification: • Section 12.3.1.1, "About Realms and Buckets" • Section
  • Dell DX6004S | DX Object Storage Application Guide - Page 52
    • Castor-Authorization: cluster.example.com/mybucket enables only users in the cluster.example.com/mybucket realm to perform operations on an object. All other users are prevented from performing any operation on the object. • Castor-Authorization: view=cluster.example.com, change=cluster.example.
  • Dell DX6004S | DX Object Storage Application Guide - Page 53
    "Security Realm Overview". A realm is a collection of user credentials, each of which includes an MD5 hash. It is computed from the string username:realm:password. You can compute the realm using a programming language, or a utility like Apache htdigest or md5sum. htdigest is provided as part of the
  • Dell DX6004S | DX Object Storage Application Guide - Page 54
    wiki or bug report page for up-to-date information about it. Dell testing and experience recommends you observe the following guidelines when using htdigest More examples are shown in subsequent chapters in this guide. 12.8. Administrative Override and Security Administrative override means
  • Dell DX6004S | DX Object Storage Application Guide - Page 55
    Chapter 13. Managing Security for Application Developers This chapter discusses specific security-related tasks that must be performed by application developers. Before you continue, make sure you review the information discussed in Chapter 12, Introduction to Object Security. For more information
  • Dell DX6004S | DX Object Storage Application Guide - Page 56
    An example of creating a bucket and uploading a realm follows: curl -H "Castor-Authorization: authorization-specification/bucket-name" -H "Castor-Stream-Type: admin" --data-binary @realm --anyauth -u "authorizeduser-name:password" --post301 --location-trusted http://node-ip/bucketname [-D log-file-
  • Dell DX6004S | DX Object Storage Application Guide - Page 57
    1. Use the following commands to create the /mybucket realm: htdigest -c cluster_example_com_mybucket cluster.example.com/mybucket john.rogers htdigest cluster_example_com_mybucket cluster.example.com/mybucket jane.lalane 2. Create mybucket with its own authorization list. Restrict the ability to
  • Dell DX6004S | DX Object Storage Application Guide - Page 58
    u "john.rogers:john" --location-trusted http://172.16.0.35/mybucket/ file2.html --post301 -D write2.log This object requires credentials in the cluster.example.com/mybucket realm to change but can be viewed by any domain user. 7. Verify the object in a web browser. Start a web browser and enter the
  • Dell DX6004S | DX Object Storage Application Guide - Page 59
    Chapter 14. Managing Security for Domain Managers This chapter discusses specific security-related tasks that must be performed by domain managers. Before you continue, make sure you review the information discussed in Chapter 12, Introduction to Object Security. See one of the following topics
  • Dell DX6004S | DX Object Storage Application Guide - Page 60
    • You send your commands to a node whose IP address is 172.16.0.35. Note The examples show how to update user lists using APPEND, which is recommended because APPEND does not change the Castor-Authorization header for the object. If you use PUT instead of APPEND, make sure you first HEAD the domain
  • Dell DX6004S | DX Object Storage Application Guide - Page 61
    curl --anyauth -u "fred.bell:fred" --location-trusted "http://172.16.0.35?domain=cluster.example.com" -D get-domain-realm2.log The domain realm displays: james.north:cluster.example.com:fef73c5a743a14bf0468a2a5c7177d22 sarah.jones:cluster.example.com:8ac9676459e241875098cd5e207c6a17 5. Use the
  • Dell DX6004S | DX Object Storage Application Guide - Page 62
    to create a new domain realm: htdigest -c cluster_example_com cluster.example.com john.rogers htdigest cluster_example_com cluster.example.com jane.lalane 2. Dell strongly recommends you HEAD the domain to get the Castor-Authorization header for the domain as follows: curl -I --anyauth -u "larry
  • Dell DX6004S | DX Object Storage Application Guide - Page 63
    The Castor-Authorization header in this example is: Castor-Authorization: cluster.example.com/_administrators, POST=cluster.example.com 3. PUT the updated realm on the domain: curl -X PUT --data-binary @cluster_example_com -H "Castor-Authorization: cluster.example.com/_administrators, POST=cluster.
  • Dell DX6004S | DX Object Storage Application Guide - Page 64
    entity-body in transit. Also, a client can provide this header to indicate that DX Storage should compute and check it as it is storing or returning the object data. For a list of all metadata headers supported by DX Storage, see the Content Metadata appendix. During a POST or PUT, the client can
  • Dell DX6004S | DX Object Storage Application Guide - Page 65
    chapter discusses the optional lifepoint header, which defines a DX Storage storage policy for the associated object. For a list of all metadata headers supported by DX Storage, see the Content Metadata appendix. 16.1. About Storage Policies Each node in a DX Storage cluster has a component called
  • Dell DX6004S | DX Object Storage Application Guide - Page 66
    If the current date is between the first and second lifepoints, the Health Processor allows the number of replicas to decrease, perhaps leaving only a single replica. However, the fact that this lifepoint specifies the deletable constraint enables a client to delete the content by sending a DELETE
  • Dell DX6004S | DX Object Storage Application Guide - Page 67
    16.4.1. Replication The ReplicationConstraintSpecialist maintains the desired level of redundancy of content objects, as well as making sure they are being stored in the most efficient manner possible. ReplicationConstraintSpecialist understands one constraint name: reps, which can be set to any
  • Dell DX6004S | DX Object Storage Application Guide - Page 68
    Note Do not use deletable=no and delete in the same lifepoint. Incorrect: Lifepoint: [Wed, 08 Jun 2008 15:59:02 GMT] reps=3, deletable=no, delete Correct: Lifepoint: [Fri, 12 Dec 2007 15:59:02 GMT] reps=3, deletable=no Lifepoint: [] delete Copyright © 2010 Caringo, Inc. All rights reserved 63
  • Dell DX6004S | DX Object Storage Application Guide - Page 69
    with a PUT request when the user is ready for the object to become immutable: Allow: GET, HEAD This removes PUT, COPY, and APPEND from the supported methods, effectively making the object immutable. When it is asked to perform some request on an anchor stream, the SCSP server will first examine its
  • Dell DX6004S | DX Object Storage Application Guide - Page 70
    and authorized administrator credentials, it proceeds and the Allow header is ignored. Administrative overrides cannot be used for methods that are never supported for an object, specifically application of update methods like PUT, COPY or APPEND to immutable objects. If an administrator anticipates
  • Dell DX6004S | DX Object Storage Application Guide - Page 71
    , this approach also requires the client and/or proxy clocks to be reasonably well synchronized with the server clocks. Although DX Storage will support this coherency method for compatibility reasons, it is not the preferred mechanism because of these objections. Note that the value of each header
  • Dell DX6004S | DX Object Storage Application Guide - Page 72
    HTTP/1.1 Caching Headers The newer HTTP/1.1 cache coherency mechanism does not use dates or time stamps and thus avoids the granularity and synchronization problems of the HTTP/1.0 headers. Instead, it uses "entity tags" or ETags which can only be compared for exact equality. In DX Storage, ETag
  • Dell DX6004S | DX Object Storage Application Guide - Page 73
    Examples of If-Match request headers: If-Match: "508941dc9b52243f64d964b058354b76" If-Match: "508941dc9b52243f64d964b058354b76", "fe3233d3c6881d5e8b654117b829d26c" If-Match: W/"508941dc9b52243f64d964b058354b76" If-Match: * If any of the entity tags match the primary UUID of the object that would
  • Dell DX6004S | DX Object Storage Application Guide - Page 74
    The value of the header can be either a single quoted string (possibly with some ignored flags outside the quotation marks) or an HTTP-date string (unquoted). Examples of If-Range request headers: If-Range: "508941dc9b52243f64d964b058354b76" If-Range: W/"508941dc9b52243f64d964b058354b76" If-Range:
  • Dell DX6004S | DX Object Storage Application Guide - Page 75
    This chapter discusses custom metadata headers, which you can use to pass any data your application requires. For a list of all metadata headers supported by DX Storage, see the Content Metadata appendix. Starting with DX Storage version 5.0, you can use custom headers in the following formats
  • Dell DX6004S | DX Object Storage Application Guide - Page 76
    has not been modified or corrupted in any way, the hashes match and, in that case, DX Storage returns the object as usual with the computed digest as a trailing Location header. Because the hash algorithms are published and well-known, it is also possible for users and third parties to independently
  • Dell DX6004S | DX Object Storage Application Guide - Page 77
    that the stored content has always been as it is now, and that it has always been associated with the same UUID. Note Range headers are not compatible with integrity seals. If the seal is incorrect, the connection might be closed prematurely. For more information about integrity seals, see Section
  • Dell DX6004S | DX Object Storage Application Guide - Page 78
    Appendix A. Content Header Metadata This appendix lists all supported HTTP headers that can be persisted and returned on a subsequent READ or INFO requests. All content metadata headers are case- insensitive but DX Storage preserves
  • Dell DX6004S | DX Object Storage Application Guide - Page 79
    For a non-CSN-managed cluster, the cluster name is specified by the value of the cluster parameter in your cluster or node configuration file. Dell recommends you set your cluster name to a fully qualified domain name. For more information, see the chapter on advanced configuration in the DX Object
  • Dell DX6004S | DX Object Storage Application Guide - Page 80
    Appendix B. Sample Code and Client Library Behaviors with 100Continue The best practice for integrators is to use the DX Storage Software Development Kit, which includes fully implementations of the SCSP protocol in multiple languages. Integrators not using the Software Development Kit should be
  • Dell DX6004S | DX Object Storage Application Guide - Page 81
    Appendix C. Open Source Software Regarding certain third party open source components also shipped with the product, please see the detailed information that appears in the document DX Storage OSS License Notices for 3rd Party Software.pdf. Your vendor will ship open/free/libre (for example, GPL-
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
DX Object Storage Application Guide
Version 5.0