Today, storage and memory hierarchies are manually tuned and sized at design time. But tomorrow’s workloads are increasingly dynamic, multi-tenant and variable. It just simply is not possible to build truly autonomous storage systems that can adapt to changing application workloads with today’s methods. In this session, we demonstrate recent breakthroughs in autonomous storage systems research including how traditional real-time approaches have not been able to succeed up to now.

Zero Trust is a collection of security methodologies that work together to enforce access, with the view that your network has already been compromised, and using contextual information from identity, security, and IT infrastructure, along with risk and analytics tools, to enable dynamic enforcement of security policies uniformly across the corporate network. This session will highlight the main attributes of Zero Trust, and why it is important for storage developers.

On the domain controller side we got a lot of updates recently: - Updated Heimdal - Working with the latest MIT Kerberos On the member server side we fixed some critical bugs and have plans for future improvements how a file server can avoid as much domain controller interaction as possible.

The exponential growth in data volume and traffic across the global internet infrastructure is motivating the exploration of new architectures for data centers to achieve the demand for better performance, efficiency and total cost of ownership (TCO). One promising trend is to segregate the functional components of compute, memory, storage, and networking into pools and organize them as needed according to the specific needs of different workloads. This disaggregation and composability will take us beyond the classic architecture of servers as the unit of computing.

The UNIX Filesystem API is profoundly broken, and user-settable symbolic links are to blame. In this talk I will explain how CVE-2021-20316 made me realize how symbolic links, introduced in 4.2BSD Unix from U.C. Berkeley, broke the previously elegant UNIX file system API and file system design. The design and implementation of symbolic links has caused years worth of security flaws and API patches to fix a conceptually broken idea. I also propose a modest suggestion in order to help Linux step away from this mess to a more secure by-design future.

A new class of cloud and datacenter infrastructure is emerging into the marketplace. This new infrastructure element, often referred as Data Processing Unit (DPU) or Infrastructure Processing Unit (IPU), takes the form of a server hosted PCIe add-in card or on-board chip(s), containing one or more ASIC’s or FPGA's, usually anchored around a single powerful SoC device. The DPU/IPU-like devices have their roots in the evolution of SmartNIC devices but separate themselves from that legacy in several important ways.

Hear from the experts on the latest from NVMe including implementation experiences.

The SNIA Technical Council believes that it is important for storage developers to learn about the emerging technology of Data Processing Units (DPUs). We have created a task force to provide an overview and answer the following questions. What is a DPU? Why might storage developers want to adopt DPUs in their products or services? What tools and libraries do you provide for developers? Which parts are open source? What development languages are supported? Following the panel presentations, we will open the floor to questions from the participants.

We will have some experts regarding the EDSFF specifications to discuss related topics. We may also have a few experts regarding connectors and cables.

We will guide the group to discuss the 1.0 specification, what it means for the industry, and where we go from here.