0 1 00:00:05,740 --> 00:00:09,740 Yeah and all these questions you're getting answered but I want to answer them anyway so. 1 2 00:00:09,790 --> 00:00:11,800 Thanks so much for the help in the chat. 2 3 00:00:12,110 --> 00:00:17,560 Andy asked Do you have any advice on mounting the same persistent volume using Rex Ray across multiple 3 4 00:00:17,560 --> 00:00:18,730 containers in a swarm stack. 4 5 00:00:18,730 --> 00:00:23,270 When the when the PD can only be attached to one note at a time. 5 6 00:00:25,520 --> 00:00:25,860 Yeah. 6 7 00:00:25,890 --> 00:00:30,680 So you can not see here's the thing about container orchestration. 7 8 00:00:30,790 --> 00:00:40,720 Andy is that containers don't change any of the fundamental underlying storage infrastructure features 8 9 00:00:40,720 --> 00:00:41,770 or limitations. 9 10 00:00:41,790 --> 00:00:46,030 So what I mean by that is if you're using elastic block storage and eight of us which can only talk 10 11 00:00:46,030 --> 00:00:52,730 to one container at one server at a time right you can only connect CBS to a single easy to node at 11 12 00:00:52,730 --> 00:00:57,510 a time it's a feature or a limitation of that storage device. 12 13 00:00:57,520 --> 00:01:03,450 That storage system containers don't change that and I don't know that they ever would right. 13 14 00:01:03,480 --> 00:01:09,690 Certainly they don't today and they know all the tools out there will just assist you in getting that 14 15 00:01:10,080 --> 00:01:15,310 UBS object onto the right node for the right container at the right time. 15 16 00:01:15,360 --> 00:01:19,960 Now on 8 of us if you use something like Alexander mentions in a. 16 17 00:01:20,160 --> 00:01:29,250 That's essentially what is backing the ESFS tool with eight of us is ESFs storage and that is slower 17 18 00:01:29,400 --> 00:01:34,110 but a type of storage that is designed for multi node multi read and write. 18 19 00:01:34,170 --> 00:01:39,720 It's essentially like a Windows file share if you're from a Windows background SMB sifts file share 19 20 00:01:39,720 --> 00:01:45,870 in Windows world has that same functionality where multiple in nodes or clients can connect to the storage 20 21 00:01:46,140 --> 00:01:54,480 shared over the network I scuzzy for example does allow it but it tends to not allow multiple rights 21 22 00:01:54,510 --> 00:01:58,860 at the same time only reads in certain technologies depending on whether using advance storage like 22 23 00:01:58,900 --> 00:01:59,470 NetApp. 23 24 00:01:59,610 --> 00:02:04,470 Stuff like that so when you think about storage you basically realize that to realize that remember 24 25 00:02:04,470 --> 00:02:09,540 that containers don't change any of the limitations of storage really so you have to go find the right 25 26 00:02:09,540 --> 00:02:16,170 storage and in fact when people asked me about storage in general we'd a lot people still tend to gravitate 26 27 00:02:16,170 --> 00:02:22,010 to storage like I need the container storage tool first. 27 28 00:02:22,020 --> 00:02:24,540 To me that's the last thing you should do. 28 29 00:02:24,630 --> 00:02:27,720 First you took you look at the application you look at its requirements. 29 30 00:02:27,720 --> 00:02:29,310 You know I'm earning my sequel. 30 31 00:02:29,310 --> 00:02:32,980 I had to have certain response rate a certain level of IO. 31 32 00:02:33,060 --> 00:02:38,400 Hopefully you can find out some of these things and then you have to go then looking for the storage 32 33 00:02:38,520 --> 00:02:40,860 itself that will fulfill that need. 33 34 00:02:40,980 --> 00:02:48,330 And then last thing is how do I get that storage working in a orchestrator or Docker itself if you're 34 35 00:02:48,330 --> 00:02:50,490 not using orchestration like just a docker run. 35 36 00:02:50,730 --> 00:02:51,090 And then. 36 37 00:02:51,120 --> 00:02:55,440 So that's how you know because most storage vendors now are all providing Docker drivers Cuba Daddy's 37 38 00:02:55,440 --> 00:02:56,750 drivers stuff like that. 38 39 00:02:56,760 --> 00:02:59,070 So I don't tend to go looking for that first. 39 40 00:02:59,070 --> 00:03:00,990 I tend to answer the questions. 40 41 00:03:01,020 --> 00:03:02,720 What's the app need. 41 42 00:03:02,730 --> 00:03:06,060 Let me go find the right storage solution once I find that storage solution. 42 43 00:03:06,090 --> 00:03:08,580 How do I get it connected to my cluster. 43 44 00:03:08,610 --> 00:03:13,040 Maybe you did it that way and maybe you're just already at the point of saying hey how do I do multiple 44 45 00:03:13,590 --> 00:03:14,570 read rights to it. 45 46 00:03:14,580 --> 00:03:19,130 And unfortunately you're gonna have to find specific storage that supports that. 46 47 00:03:19,170 --> 00:03:22,900 Now we can get into that whole you know storage replication right. 47 48 00:03:22,920 --> 00:03:29,310 We are replicating files across different servers called shared nothing storage or where you have storage 48 49 00:03:29,310 --> 00:03:34,860 that's sitting on one no that's shared across the network maybe using infests to others or you're using 49 50 00:03:34,860 --> 00:03:37,830 cloud storage or your own private storage in a data center. 50 51 00:03:37,830 --> 00:03:42,930 Those are all different types of storage solutions that you would work out before you decide what needs 51 52 00:03:42,930 --> 00:03:43,840 to be an orchestration. 52 53 00:03:43,840 --> 00:03:44,020 Right. 53 54 00:03:44,040 --> 00:03:47,490 Because again those all those things aren't necessarily container specific. 54 55 00:03:47,490 --> 00:03:53,700 They're just standard storage solutions and they've most of them have existed before containers and 55 56 00:03:53,700 --> 00:03:59,190 then you just need to get the right driver or plug in for your container orchestrator or Docker run. 56 57 00:03:59,220 --> 00:04:04,610 So hopefully that process will help you work out what you need to to find to solve your problem.