Hi [[ session.user.profile.firstName ]]

SNIA Webcasts

  • Date
  • Rating
  • Views
  • Centralized vs. Distributed Storage
    Centralized vs. Distributed Storage John Kim, Mellanox; Alex McDonald, NetApp; J Metz, Cisco Recorded: Sep 11 2018 63 mins
    In the history of enterprise storage there has been a trend to move from local storage to centralized, networked storage. Customers found that networked storage provided higher utilization, centralized and hence cheaper management, easier failover, and simplified data protection, which has driven the move to FC-SAN, iSCSI, NAS and object storage.

    Recently, distributed storage has become more popular where storage lives in multiple locations but can still be shared. Advantages of distributed storage include the ability to scale-up performance and capacity simultaneously and--in the hyperconverged use case--to use each node (server) for both compute and storage. Attend this webcast to learn about:
    •Pros and cons of centralized vs. distributed storage
    •Typical use cases for centralized and distributed storage
    •How distributed works for SAN, NAS, parallel file systems, and object storage
    •How hyperconverged has introduced a new way of consuming storage
  • RoCE vs. iWARP
    RoCE vs. iWARP Tim Lustig, Mellanox; Fred Zhang, Intel; John Kim, Mellanox Recorded: Aug 22 2018 64 mins
    Network-intensive applications, like networked storage or clustered computing, require a network infrastructure with high bandwidth and low latency. Remote Direct Memory Access (RDMA) supports zero-copy data transfers by enabling movement of data directly to or from application memory. This results in high bandwidth, low latency networking with little involvement from the CPU.

    In the next SNIA ESF “Great Storage Debates” series webcasts, we’ll be examining two commonly known RDMA protocols that run over Ethernet; RDMA over Converged Ethernet (RoCE) and IETF-standard iWARP. Both are Ethernet-based RDMA technologies that reduce the amount of CPU overhead in transferring data among servers and storage systems.

    The goal of this presentation is to provide a solid foundation on both RDMA technologies in a vendor-neutral setting that discusses the capabilities and use cases for each so that attendees can become more informed and make educated decisions.

    Join to hear the following questions addressed:

    •Both RoCE and iWARP support RDMA over Ethernet, but what are the differences?
    •Use cases for RoCE and iWARP and what differentiates them?
    •UDP/IP and TCP/IP: which uses which and what are the advantages and disadvantages?
    •What are the software and hardware requirements for each?
    •What are the performance/latency differences of each?

    Join our SNIA experts as they answer all these questions and more on this next Great Storage Debate

    After you watch the webcast, check out the Q&A blog http://bit.ly/2OH6su8
  • The SNIA Persistent Memory Security Threat Model
    The SNIA Persistent Memory Security Threat Model Doug Voigt, Co-Chair, SNIA NVM Programming TWG and Distinguished Technologist, HPE Recorded: Aug 21 2018 56 mins
    What new security requirements apply to Persistent Memory (PM)? While many existing security practices such as access control, encryption, multi-tenancy and key management apply to persistent memory, new security threats may result from the differences between PM and storage technologies. The SNIA PM security threat model provides a starting place for exposing system behavior, protocol and implementation security gaps that are specific to PM. This in turn motivates industry groups such as TCG and JEDEC to standardize methods of completing the PM security solution space.
  • Cloud Mobility and Data Movement
    Cloud Mobility and Data Movement Eric Lakin, University of Michigan; Michelle Tidwell, IBM; Alex McDonald, NetApp Recorded: Aug 7 2018 60 mins
    We’re increasingly in a multi-cloud environment, with potentially multiple private, public and hybrid cloud implementations in support of a single enterprise. Organizations want to leverage the agility of public cloud resources to run existing workloads without having to re-plumb or re-architect them and their processes. In many cases, applications and data have been moved individually to the public cloud. Over time, some applications and data might need to be moved back on premises, or moved partially or entirely from one cloud to another.

    That means simplifying the movement of data from cloud to cloud. Data movement and data liberation – the seamless transfer of data from one cloud to another – has become a major requirement.

    In this webcast, we’re going to explore some of these data movement and mobility issues with real-world examples from the University of Michigan. Register now for discussions on:

    •How do we secure data both at-rest and in-transit?
    •Why is data so hard to move? What cloud processes and interfaces should we use to make data movement easier?
    •How should we organize our data to simplify its mobility? Should we use block, file or object technologies?
    •Should the application of the data influence how (and even if) we move the data?
    •How can data in the cloud be leveraged for multiple use cases?
  • FCoE vs. iSCSI vs. iSER
    FCoE vs. iSCSI vs. iSER J Metz, Cisco; Saqib Jang, Chelsio; Rob Davis, Mellanox; Tim Lustig, Mellanox Recorded: Jun 21 2018 62 mins
    The “Great Storage Debates” webcast series continues, this time on FCoE vs. iSCSI vs. iSER. Like past “Great Storage Debates,” the goal of this presentation is not to have a winner emerge, but rather provide vendor-neutral education on the capabilities and use cases of these technologies so that attendees can become more informed and make educated decisions.

    One of the features of modern data centers is the ubiquitous use of Ethernet. Although many data centers run multiple separate networks (Ethernet and Fibre Channel (FC)), these parallel infrastructures require separate switches, network adapters, management utilities and staff, which may not be cost effective.

    Multiple options for Ethernet-based SANs enable network convergence, including FCoE (Fibre Channel over Ethernet) which allows FC protocols over Ethernet and Internet Small Computer System Interface (iSCSI) for transport of SCSI commands over TCP/IP-Ethernet networks. There are also new Ethernet technologies that reduce the amount of CPU overhead in transferring data from server to client by using Remote Direct Memory Access (RDMA), which is leveraged by iSER (iSCSI Extensions for RDMA) to avoid unnecessary data copying.

    That leads to several questions about FCoE, iSCSI and iSER:

    •If we can run various network storage protocols over Ethernet, what
    differentiates them?
    •What are the advantages and disadvantages of FCoE, iSCSI and iSER?
    •How are they structured?
    •What software and hardware do they require?
    •How are they implemented, configured and managed?
    •Do they perform differently?
    •What do you need to do to take advantage of them in the data center?
    •What are the best use cases for each?

    Join our SNIA experts as they answer all these questions and more on the next Great Storage Debate.

    After you watch the webcast, check out the Q&A blog from our presenters http://bit.ly/2NyJKUM
  • Everything You Wanted To Know...But Were Too Proud To Ask - Storage Controllers
    Everything You Wanted To Know...But Were Too Proud To Ask - Storage Controllers Peter Onufryk, Microsemi, Craig Carlson, Cavium, Chad Hintz, Cisco, John Kim, Mellanox, J Metz, Cisco Recorded: May 15 2018 48 mins
    Are you a control freak? Have you ever wondered what was the difference between a storage controller, a RAID controller, a PCIe Controller, or a metadata controller? What about an NVMe controller? Aren’t they all the same thing?

    In part Aqua of the “Everything You Wanted To Know About Storage But Were Too Proud To Ask” webcast series, we’re going to be taking an unusual step of focusing on a term that is used constantly, but often has different meanings. When you have a controller that manages hardware, there are very different requirements than a controller that manages an entire system-wide control plane. From the outside looking in, it may be easy to get confused. You can even have controllers managing other controllers!
    Here we’ll be revisiting some of the pieces we talked about in Part Chartreuse [https://www.brighttalk.com/webcast/663/215131], but with a bit more focus on the variety we have to play with:
    •What do we mean when we say “controller?”
    •How are the systems being managed different?
    •How are controllers used in various storage entities: drives, SSDs, storage networks, software-defined
    •How do controller systems work, and what are the trade-offs?
    •How do storage controllers protect against Spectre and Meltdown?
    Join us to learn more about the workhorse behind your favorite storage systems.

    After you watch the webcast, check out the Q&A blog at http://bit.ly/2JgcHlM
  • What’s Next in Storage: Analysts and Experts Share their Predictions
    What’s Next in Storage: Analysts and Experts Share their Predictions Greg McSorley, SNIA Technical Council (non-voting); Rick Kutcipal, President, STA; Don Jeanette of TRENDFOCUS Recorded: May 2 2018 43 mins
    You won’t want to miss the opportunity to hear leading data storage experts provide their insights on prominent technologies that are shaping the market. With the exponential rise in demand for high capacity and secured storage systems, it’s critical to understand the key factors influencing adoption and where the highest growth is expected. From SSDs and HDDs to storage interfaces and NAND devices, get the latest information you need to shape key strategic directions and remain competitive.
  • Introduction to SNIA Swordfish™ ─ Scalable Storage Management
    Introduction to SNIA Swordfish™ ─ Scalable Storage Management Richelle Ahlvers, Broadcom; Don Deel, NetApp Recorded: Apr 19 2018 62 mins
    The SNIA Swordfish™ specification helps to provide a unified approach for the management of storage and servers in hyperscale and cloud infrastructure environments, making it easier for IT administrators to integrate scalable solutions into their data centers. Swordfish builds on the Distributed Management Task Force’s (DMTF’s) Redfish® specification using the same easy-to-use RESTful methods and lightweight JavaScript Object Notation (JSON) formatting. Join this session to receive an overview of Swordfish including the new functionality added in version 1.0.6 released in March, 2018.
  • File vs. Block vs. Object Storage
    File vs. Block vs. Object Storage Mark Carlson, Toshiba, Alex McDonald, NetApp, Saqib Jang, Chelsio, John Kim, Mellanox Recorded: Apr 17 2018 67 mins
    File vs. Block vs. Object Storage

    When it comes to storage, a byte is a byte is a byte, isn’t it? One of the truths about simplicity is that scale makes everything hard, and with that comes complexity. And when we’re not processing the data, how do we store it and access it?

    The only way to manage large quantities of data is to make it addressable in larger pieces, above the byte level. For that, we’ve designed sets of data management protocols that help us do several things: address large lumps of data by some kind of name or handle, organize it for storage on external storage devices with different characteristics, and provide protocols that allow us to programmatically write and read it.

    In this webcast, we'll compare three types of data access: file, block and object storage, and the access methods that support them. Each has its own use cases, and advantages and disadvantages; each provides simple to sophisticated data management; and each makes different demands on storage devices and programming technologies.

    Join us as we discuss and debate:

    Storage devices
    - How different types of storage drive different management & access solutions
    Block
    - Where everything is in fixed-size chunks
    - SCSI and SCSI-based protocols, and how FC and iSCSI fit in
    File
    - When everything is a stream of bytes
    - NFS and SMB
    Object
    - When everything is a blob
    - HTTP, key value and RESTful interfaces
    - When files, blocks and objects collide

    After you watch the webcast, check out the Q&A blog: https://wp.me/p1kTSa-bh
  • Containers and Persistent Memory
    Containers and Persistent Memory Arthur Sainio, Co-Chair, SNIA Persistent Memory and NVDIMM Special Interest Group Recorded: Apr 17 2018 33 mins
    Containers can make it easier for developers to know that their software will run, no matter where it is deployed. What do customers, storage developers, and the industry want to see to fully unlock the potential of persistent memory in a container environment? This presentation will discuss how persistent memory is a revolutionary technology which will boost the performance of next-generation packaging of applications and libraries into containers.

    You’ll learn:
    •What SNIA is doing to advance persistent memory
    •What the ecosystem enablement efforts are around persistent memory solutions
    •How NVDIMMs are paving the way for plug-n-play adoption into container environments

    About the presenter:
    Arthur is Co-Chair of the SNIA Persistent Memory and NVDIMM Special Interest Group, which accelerates the awareness and adoption of Persistent Memories and NVDIMMs for computing architectures.

    As a Director of Product Marketing at SMART Modular Technologies. Arthur has been driving new product launch and business development activities at SMART since 1998. Prior to Smart, Arthur worked as a product manager at Hitachi Semiconductor America. While there, his focus was on DRAM, SRAM and Flash technologies.

    Arthur holds a MBA from San Francisco State University and a MS from Arizona State University

Embed in website or blog