Table 3 Command/Request Definitions Request/Operation Container/Bucket Object/File PUT PUT operations performed against PUT operations against an Object Container/Bucket are used to create that are used add object to the container. bucket/container and write, overwrite, an and object’s metadata content. GET GET operations performed against GET operations against an Object Container/Bucket lists information about are used to retrieve objects and the objects within that container/bucket. data from the objects’ container/bucket. HEAD HEAD operations against a storage HEAD operations against an Object Container are used to determine the are used to retrieve object’s number of Objects, and the total bytes of metadata and other HTTP headers. all Objects stored in the Container. DELETE DELETE operations performed against DELETE operations against an Container/Bucket deletes the Object are used to permanently container/bucket. delete the specified object. POST The POST request operation adds an POST operations against an Object POST is an alternate form of object to a container/bucket using HTML name are used to set and overwrite PUT that enables forms. arbitrary key/value metadata. uploads COPY The COPY operation creates a new, The COPY operation creates a uniquely named copy of a container/bucket uniquely name copy of an object/file that is already stored. that is already stored. LIST The LIST operation displays the The LIST operation displays the information of a current Container/Bucket. current objects/files, including metadata. C.6.1.3.4 Support Storage Resource Classes For each Class proposed by the Offeror, a solution of equal or better specifications than identified in Table 4 Proposed Storage Class below will satisfy the requirement. Table 4 Proposed Storage Class Storage Throughput Uptime/ Example Class Availability A 8 Gbps 100% high-speed SAN B 1 Gbps 100% low-speed SAN C 50 Mbps 99.90% Remote On-line Storage D Access within 24 hrs offline Tape Library Independent Task Orders may specify selected storage class and availability requirements and may also specify that Class C and Class D storage be stored in a facility other than the one hosting the related mission system. C.6.1.3.5 Support Data Migration Across Storage Classes
Table 3 Command/Request Definitions Request/Operation Container/Bucket Object/File PUT PUT operations performed against Container/Bucket are used to create that container. PUT operations against an Object are used add object to the bucket/container and write, overwrite, an object’s metadata and content. GET GET operations performed against Container/Bucket lists information about objects within that container/bucket. GET operations against an Object are used to retrieve objects and the objects’ data from the container/bucket. HEAD HEAD operations against a storage Container are used to determine the number of Objects, and the total bytes of all Objects stored in the Container. HEAD operations against an Object are used to retrieve object’s metadata and other HTTP headers. DELETE DELETE operations performed against Container/Bucket deletes the container/bucket. DELETE operations against an Object are used to permanently delete the specified object. POST POST is an alternate form of PUT that enables uploads The POST request operation adds an object to a container/bucket using HTML forms. POST operations against an Object name are used to set and overwrite arbitrary key/value metadata. COPY The COPY operation creates a new, uniquely named copy of a container/bucket that is already stored. The COPY operation creates a uniquely name copy of an object/file that is already stored. LIST The LIST operation displays the information of a current Container/Bucket. The LIST operation displays the current objects/files, including metadata. C.6.1.3.4 Support Storage Resource Classes For each Class proposed by the Offeror, a solution of equal or better specifications than identified in Table 4 Proposed Storage Class below will satisfy the requirement. Table 4 Proposed Storage Class Storage Class Throughput Uptime/ Availability Example A 8 Gbps 100% high-speed SAN B 1 Gbps 100% low-speed SAN C 50 Mbps 99.90% Remote On-line Storage D Access within 24 hrs offline Tape Library Independent Task Orders may specify selected storage class and availability requirements and may also specify that Class C and Class D storage be stored in a facility other than the one hosting the related mission system. C.6.1.3.5 Support Data Migration Across Storage Classes
fchs_section_c_-_description_specification_and_work_statement_1_1.docx