Storage Developer Conference

Hyperscaler companies as well as large enterprises who build their own datacenters have specific requirements for new features in storage drives. The SNIA Technical Council has created a white paper on these requirements and how current and future standards and open source projects can address them.

This talk will present the results of the the TC research in this area and discuss how SNIA and other standards bodies are making changes to accommodate them.

Learning Objectives: 1) Learn about Datacenter customer drive requirements, 2) Learn about existing and new standards for drive interfaces,

3)Learn about open source projects that address these requirement.

Swift on File enables the swift object store hosted over clustered file system to have file as well as object access for the same data. Such multi protocol access enables various use-cases where data can be ingested via object and processed for analytics over file protocols (SMB/NFS/POSIX). In another manifestation, data can be accessed or shared by the user interchangeable via different protocols enabling user data sync n share across protocols.

For some of these use-cases, there is a strong need to have common User Identity management across object and file protocols so that one can leverage the underlying common file system features like quota management per user or group, per user/group placement policies on data or even have common authorisation across file and object . In order to achieve this, the approaches need to ensure that objects created by an user via Swift is associated with the user's user ID (UID) and group ID (GID) which is same when the object is accessed by that user via file protocols like NFS/SMB/POSIX (where typically the ID's are stored in a centrally ID mapping server like Microsoft AD or LDAP).

This presentation discusses in detail the various issues and nuances associated with having common ID management across Swift object access and file access and presents an approach to solve them without changes in core Swift code by leveraging powerful SWIFT middleware framework.

Learning Objectives: 1) Understanding Openstack SWIFT Object Store and File access challanges, 2) Learning about OpenStack middleware which will help developers on its usage, 3) Learning ID management concepts for File and Object, 4) Learning the different approaches to solve SWIFT on File ID management problem, 5) Learning the algorithm that developers can deploy to have common ID management between object (SWIFT) and FILE.

The implementation of advanced SMB3 features is a broad and important set of topics on the Samba roadmap. One of these SMB3 features that is currently being actively worked on is Multi-Channel, a kind of channel bonding at the SMB level intended to increase both performance and fault-tolerance of SMB sessions. It is not only one of the most generally useful features of SMB3 but also a prerequisite for enabling RDMA as a transport for SMB with SMB Direct.

This talk will provide details about the current project to finish the implementation of SMB3 Multi-Channel in Samba, explaining the challenges for development and how they are solved. The presentation will include demos. The talk will conclude with a brief outlook how SMB Direct support can be added to Samba.

Learning Objectives: 1) Refresher on Multi-Channel, 2) State of implementation of Multi-Channel in Samba, 3) Challenges for Samba to implement Multi-Channel, 4) Design of Multi-Channel in Samba, 5) Outlook to SMB Direct support.

Practical experience from implementing the OASIS Key Management Interoperability Protocol (KMIP) and from deploying and interoperability testing multiple vendor implementations of KMIP form the bulk of the material covered. Guidance will be provided that covers the key issues to require that your vendors address and how to distinguish between simple vendor tick-box approaches to standard conformance and actual interoperable solutions.

Learning Objectives:

1) In-depth knowledge of the core of the OASIS KMIP

2) Awareness of requirements for practical interoperability

3) Guidance on important of conformance testing

In this presentation we extend previous work to include p2p transfers between NVMe devices and RDMA capable NICs running protocols like Infiniband, RoCE and iWARP. We present experimental results using both 10Gbe iWARP and 56G Infiniband NICs that show how the latency associated with remote transfer of data can be reduced whilst also offloading the CPU allowing it to focus on other tasks. We show how this work can act as a precursor for the NVMe over Fabrics work currently being standardized. We also show how the Controller Memory Buffer (CMB) feature introduced in NVMe 1.2 be utilized in a novel fashion to aid this work.

Learning Objectives:

1) What are the benefits of NVM Express

2) How can NVM Express and RDMA be utilized prior to NVMe over Fabrics

3) How Donard code builds on open-source code

4) How latency, bandwidth and CPU offload can all be improved using peer-2-peer

Programming with persistent memory is hard, similar to the type of programming a file system developer does because of the need to write changes out in a way that maintains consistency. Applications must be re-architected to change data stored in two tiers (DRAM and storage) into three tiers (DRAM, pmem and storage). This presentation will review key attributes of persistent memory as well as outline architectural and design considerations for making an application persistent memory aware. This discussion will conclude with examples showing how to modify an application to provide consistency when using persistent memory.

Learning Objectives: 1) Introduce how persistent memory differs from DRAM and standard storage for storing application data. 2) Show examples of the architectural considerations for making an application persistent memory aware, 3) Give examples of how to modify an existing application to utilize persistent memory, 4) Discuss the open source Non-Volatile Memory Library (NVML) available on GitHub for use to help with persistent memory programming

Attacks against enterprises and their technology vendors are facilitated by the current rapid adoption of embedded systems, cloud solutions, and web based platforms. These attacks often undermine the very monetization, scalability and user experience goals for which these systems were designed and deployed. As malicious hackers advance their techniques at a staggering pace, often rendering current defense tactics obsolete, so too must security practitioners obsess over deploying progressive techniques. Pre-sented by the elite organization of white hat hackers most widely known for being first to break the iPhone, this session will analyze the anatomies of real world attacks against high profile systems, ranging from the well known Target breach, to Texas In-struments RFID, to Apple products, and more. It will extract lessons from these attack anatomies to provide a framework to account for these modern attackers, articulate industry context, and supply attendees with key takeaways, including immediately actionable guidance.

Learning Objectives: 1) Discipline Division: Security Separated from Functionality. 2) Perspective Matters: White Box vs. Black Box. 3) Defense Priorities: Secure Assets, not Just Perimeters. 4) Timing Security: Build It In, Not Bolt It On. 5) Procedural Duration: Security as an Ongoing Process.

This presentation will describe the changes being made to the Windows OS, its file systems and storage stack in response to new evolving storage technologies. Learn how windows is adaptaing to new storage technologies.

Intel Design environment heavily depends on a large scale NFS infrastructure with 10s of PBs of data. Global Name space helps to navigate this large environment in a uniform way from 60,000 compute servers.

But what if a user doesn't know where the piece of data he is looking for is located?

Our customers used to spend hours waiting for recursive "grep" commands' completion - or preferred not to bother with some less critical queries.

In this talk, we'll cover how Intel IT has identified an opportunity to provide a faster way to look for an information within this large-scale NFS environment. We'll review various open source solutions which were considered, and how we've decided to implement a mix of home-grown scalable NFS crawler with open source ElasticSearch engine to index parts of our NFS environment.

As part of this talk we'll discuss various challenges and our ways to mitigate them, including:

# Crawler scalability required to index large amounts of dynamically changing data within pre-defined indexing SLA

# Index scalability and performance requirements

# Relevancy of the results presented in search queries by customers

# User interface considerations

# Security aspects of the index access control

This might be an interesting conversation for both storage vendors - covering a useful feature which might be implemented as a part of NFS environment, and for storage customers who may benefit from such capability.

Learning Objectives:

1) How to implement scalable indexing and search on top of large scale NFS

2) Scalable crawling with controlled performance impact on shared file servers

3) Security aspects of data index and search representation

Data wants to live in the cloud, and move freely between enterprises, phones, homes and clouds, but one major obstacle remains: How can your data be protected against alteration and disclosure? This session introduces the Cloud Encrypted Object Extension to the CDMI standard, which permits encrypted objects to be stored, retrieved, and transferred between clouds. Originating out of work to make CDMI usable for Electric Medical Records (EMR) application, Cloud Encrypted Objects are a standards-based way to encrypt data, verify integrity, and provide access to secured content, such that objects can freely move between clouds in a cross-protocol manner.

Learning Objectives: 1) Learn how Cloud Encrypted Objects are used by a client, 2) Learn how Cloud Encrypted Objects can move between clouds, 3) Learn about access control and delegation for Cloud Encrypted Objects, 4) Learn how Cloud Encrypted Objects can be stored and accessed from file systems, CDMI, S3, Swift and other repositories.