‫Yeah and all these questions you're getting answered but I want to answer them anyway so.
‫Thanks so much for the help in the chat.
‫Andy asked Do you have any advice on mounting the same persistent volume using Rex Ray across multiple
‫containers in a swarm stack.
‫When the when the PD can only be attached to one note at a time.
‫Yeah.
‫So you can not see here's the thing about container orchestration.
‫Andy is that containers don't change any of the fundamental underlying storage infrastructure features
‫or limitations.
‫So what I mean by that is if you're using elastic block storage and eight of us which can only talk
‫to one container at one server at a time right you can only connect CBS to a single easy to node at
‫a time it's a feature or a limitation of that storage device.
‫That storage system containers don't change that and I don't know that they ever would right.
‫Certainly they don't today and they know all the tools out there will just assist you in getting that
‫UBS object onto the right node for the right container at the right time.
‫Now on 8 of us if you use something like Alexander mentions in a.
‫That's essentially what is backing the ESFS tool with eight of us is ESFs storage and that is slower
‫but a type of storage that is designed for multi node multi read and write.
‫It's essentially like a Windows file share if you're from a Windows background SMB sifts file share
‫in Windows world has that same functionality where multiple in nodes or clients can connect to the storage
‫shared over the network I scuzzy for example does allow it but it tends to not allow multiple rights
‫at the same time only reads in certain technologies depending on whether using advance storage like
‫NetApp.
‫Stuff like that so when you think about storage you basically realize that to realize that remember
‫that containers don't change any of the limitations of storage really so you have to go find the right
‫storage and in fact when people asked me about storage in general we'd a lot people still tend to gravitate
‫to storage like I need the container storage tool first.
‫To me that's the last thing you should do.
‫First you took you look at the application you look at its requirements.
‫You know I'm earning my sequel.
‫I had to have certain response rate a certain level of IO.
‫Hopefully you can find out some of these things and then you have to go then looking for the storage
‫itself that will fulfill that need.
‫And then last thing is how do I get that storage working in a orchestrator or Docker itself if you're
‫not using orchestration like just a docker run.
‫And then.
‫So that's how you know because most storage vendors now are all providing Docker drivers Cuba Daddy's
‫drivers stuff like that.
‫So I don't tend to go looking for that first.
‫I tend to answer the questions.
‫What's the app need.
‫Let me go find the right storage solution once I find that storage solution.
‫How do I get it connected to my cluster.
‫Maybe you did it that way and maybe you're just already at the point of saying hey how do I do multiple
‫read rights to it.
‫And unfortunately you're gonna have to find specific storage that supports that.
‫Now we can get into that whole you know storage replication right.
‫We are replicating files across different servers called shared nothing storage or where you have storage
‫that's sitting on one no that's shared across the network maybe using infests to others or you're using
‫cloud storage or your own private storage in a data center.
‫Those are all different types of storage solutions that you would work out before you decide what needs
‫to be an orchestration.
‫Right.
‫Because again those all those things aren't necessarily container specific.
‫They're just standard storage solutions and they've most of them have existed before containers and
‫then you just need to get the right driver or plug in for your container orchestrator or Docker run.
‫So hopefully that process will help you work out what you need to to find to solve your problem.