Minutes 2021 06 17

SNIA Cloud Storage Technical Working Group

Meeting Agenda, 2021-06-17

1. IP Statement:

“You are hereby informed that, under the SNIA IP Policy, your presence at this meeting may obligate you and/or your company/organization with respect to any of the work items of the SNIA Cloud Storage TWG.”

2. Attendance

Attendees: See Causeway listing

Guests:

Guests: Gary M., OEData

3. Agenda review

No changes to agenda

4. Previous meeting minutes review and approval

No objections to approving last meeting minutes as documented: https://github.com/SNIA/CDMI-spec/wiki/Minutes-2021-06-10

5. Continued discussion re. approaches for container/object duality changes

• Confirming valid syntaxes/character sets for S3

Confirmed what we had suspected. Valid characters that can be used for object names for S3 objects are limited to core ASCII plus a few special characters when accessed by path. Will verify this with a test app.

This will mean that CDMI, as currently defined, can act as a superset for all valid S3 objects. However, we need to deal with situations where valid characters in CDMI (or other protocols, such as NFS, etc) will need to be mapped into a valid S3 object name.

Next step is to propose what an S3 export would look like:

"exports" : {
    "1" : {
        "type" : "S3",
        "bucketName" : "myBucket"
    }
}

Bucket name is, by default, the container name. However, since S3 mandates globally unique bucket names (globally unique for the S3 service, but only system-unique when it's a private S3 system), we need to have a provision to allow bucket names to be specified as part of the export. We also need to deal with situations where the container name is not a valid bucket name. In both of those situations, we will return an error, and the user will have to fill in the optional bucketName field as part of the export.

6. Prepare agenda for next meeting

7. Summary of any planned major votes at next meeting

8. Adjournment