2/13/2023 0 Comments Convoy plugin vs docker for volumeTraditional Server SAN refers to individual servers connected to a dedicated, separate SAN storage solution (e.g. How is” Enterprise Server SAN” different from “Traditional” Server SAN?Ī. You can also download a PDF of the webcast slides.Īs promised, we are providing answers to the questions we received during the live event. If you missed the live event, it’s now available on-demand. The SNIA Cloud Storage Initiative recently hosted a live webcast “ Containers and Persistent Memory.†Where my colleagues and I discussed persistent storage for containers, persistent memory for containers, infrastructure software changes for persistent memory-based containers, and what SNIA is doing to advance persistent memory. It will be live, so bring your questions! How to get involved in the container community.The Container Storage Interface spec and Kubernetes 1.13.How to identify the most important projects to follow in the container world.An overview of the various storage APIs for the container landscape.Container storage types and Container Frameworks.What’s new, what to pay attention to, and how to make sense of the ever-shifting container landscape.I encourage you to register today for the February 26 th session where you’ll learn: If you missed it, it’s available on demand and will provide you with some great background information before our February 26 h webcast. In this webcast, Keith Hudgins of Docker joins us as a follow up to his earlier container webcast “ Intro to Containers, Container Storage and Docker.†It’s our most popular webcast to date with thousands of views. That’s why the SNIA Cloud Storage Technologies Initiative is hosting a live webcast on February 26, 2019, “ What’s New in Container Storage.†If you wondering what’s new in container storage, you are not alone. The landscape of containers is moving fast and constantly changing, with new standards emerging every few months. Therefore, the biggest challenge is to deploy the storage resources that are necessary for the workload, but at the same time, making sure your footprint is appropriate for the deployment infrastructure. Added components, like container-native storage, are required for many edge applications, but they take up resources. One big challenge for Kubernetes at the edge in general is to provide a lightweight deployment. It can also mean device edge, like MicroShift running on a small form factor computer or within an ARM or FPGA card for example. It could mean Kubernetes deployed on a single node at a site with little or no IT support, or even disconnected from the internet, on ships, oil rigs, or even in space for example. It could mean enterprise or provider edge locations, which are typically characterized by smaller, compact deployments of Kubernetes. Edge means different things depending on context. What are the additional/different challenges for Kubernetes storage at the edge – in contrast to the data center?Ī. In this Q&A blog, our panelists Nick Connolly, Michael St-Jean, Pete Brey and I elaborate on some of the most intriguing questions during the session. It was a lively and enlightening discussion on key considerations for container storage. Last month, the SNIA Cloud Storage Technologies Initiative hosted a fascinating panel discussion “ Kubernetes is Everywhere: What About Cloud Native Storage?” where storage experts from SNIA and Kubernetes experts from the Cloud Native Computing Foundation (CNCF) discussed storage implications for Kubernetes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |