WEBVTT

1
00:00.000 --> 00:02.360
Okay friends, so let's get to the fun stuff.

2
00:02.360 --> 00:04.960
Let's get to the actual automation portion.

3
00:04.960 --> 00:09.080
So, very first thing that we're going to be looking at right here is some of

4
00:09.080 --> 00:09.720
the utilities

5
00:09.720 --> 00:11.160
that we are going to be using.

6
00:11.160 --> 00:16.160
So just as a starter, the very first command that we want to be using is one

7
00:16.160 --> 00:17.040
called MDADM.

8
00:17.040 --> 00:20.560
Okay, now this is going to allow us to manage MD devices.

9
00:20.560 --> 00:23.280
This is basically Linux software reads.

10
00:23.280 --> 00:26.360
So we have the dash capital C or dash dash create.

11
00:26.360 --> 00:30.580
This is going to allow us to create a new array, an array simply means an array
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:26.360 --> 00:30.580
This is going to allow us to create a new array, an array simply means an array

12
00:30.580 --> 00:31.240
of devices

13
00:31.240 --> 00:33.200
that we're going to be using for RAID.

14
00:33.200 --> 00:36.890
So say for example, we have these two different drives, we could combine them

15
00:36.890 --> 00:37.600
into a single

16
00:37.600 --> 00:38.600
RAID array.

17
00:38.600 --> 00:39.960
This is what we're talking about here.

18
00:39.960 --> 00:41.680
So this is command we want to be using.

19
00:41.680 --> 00:46.440
And if we scroll on down, we also have this particular option here, dash in or

20
00:46.440 --> 00:47.640
alternatively,

21
00:47.640 --> 00:50.560
dash, dash, RAID, dash devices.

22
00:50.560 --> 00:54.750
This is going to allow us to specify the number of devices that we want within

23
00:54.750 --> 00:55.520
an array.

24
00:55.520 --> 00:59.500
So say for example, we want to create a red one array, which only requires two

25
00:59.500 --> 01:00.200
devices,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
00:59.500 --> 01:00.200
devices,

26
01:00.200 --> 01:02.640
we can specify we want two devices here.

27
01:02.640 --> 01:06.730
Whereas if you want to be implementing RAID 5, we just learned that we're going

28
01:06.730 --> 01:07.160
to have

29
01:07.160 --> 01:09.960
to have at least three devices in that array.

30
01:09.960 --> 01:12.760
We specify that with this particular option here.

31
01:12.760 --> 01:15.480
Now this here is obviously a very important option.

32
01:15.480 --> 01:18.280
You have the dash L or dash dash level.

33
01:18.280 --> 01:21.480
This is going to allow us to set the RAID level pretty much.

34
01:21.480 --> 01:25.300
Maybe we want a RAID 1 array, a RAID 5 array, a RAID 10 array, that type of

35
01:25.300 --> 01:25.880
thing.

36
01:25.880 --> 01:27.760
This is how we're going to specify this.

37
01:27.760 --> 01:30.720
Now let me just show you one more that is going to present perhaps a little bit
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

37
01:27.760 --> 01:30.720
Now let me just show you one more that is going to present perhaps a little bit

38
01:30.720 --> 01:30.920
of an

39
01:30.920 --> 01:31.920
issue.

40
01:31.920 --> 01:36.480
Notice we have this option here, dash E or dash dash metadata.

41
01:36.480 --> 01:40.150
This is going to allow us to specify the style of RAID metadata that's going to

42
01:40.150 --> 01:40.840
be used.

43
01:40.840 --> 01:45.240
Now by default, the value is going to be 1.2, but notice we also have other

44
01:45.240 --> 01:46.120
options available

45
01:46.120 --> 01:47.120
to us.

46
01:47.120 --> 01:49.640
The original is 0.90.

47
01:49.640 --> 01:52.260
This might seem pretty arbitrary, but as you're going to see this might

48
01:52.260 --> 01:53.360
actually become a little

49
01:53.360 --> 01:54.760
bit useful to know.

50
01:54.760 --> 01:58.120
So let's go and begin creating this particular array.

51
01:58.120 --> 02:00.920
Now what I'm going to do here is I'm going to go to my blue box device here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
01:58.120 --> 02:00.920
Now what I'm going to do here is I'm going to go to my blue box device here.

52
02:00.920 --> 02:06.440
Now if I do an LSBLK dash F, what I've done is I've added two new disks.

53
02:06.440 --> 02:08.320
Disk number two and disk number three right here.

54
02:08.320 --> 02:12.440
These are two new hard drives and they both happen to be of the same size.

55
02:12.440 --> 02:15.840
In my case here, they both happen to be one gig in size.

56
02:15.840 --> 02:19.520
So what I want to do here is I want to use these two drives and combine them

57
02:19.520 --> 02:20.120
into a RAID

58
02:20.120 --> 02:21.120
array.

59
02:21.120 --> 02:23.920
So let's maybe say I want to invoke some type of mirroring.

60
02:23.920 --> 02:27.830
So basically all the data is going to be duplicated across both of these drives

61
02:27.830 --> 02:28.160
when

62
02:28.160 --> 02:29.360
I happen to write to it.

63
02:29.360 --> 02:30.360
So check this out.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
02:29.360 --> 02:30.360
So check this out.

64
02:30.360 --> 02:31.480
Let's do this then.

65
02:31.480 --> 02:35.580
Let's go back to our control nodes and let me create a playbook called play one

66
02:35.580 --> 02:36.200
dot yml.

67
02:36.200 --> 02:39.110
So I'm going to insert mode to have my three hyphens, give this one a name, let

68
02:39.110 --> 02:39.480
's just

69
02:39.480 --> 02:41.960
call this creating a RAID array.

70
02:41.960 --> 02:45.320
Now whom I'm going to target, again I can target the all group if I so wish,

71
02:45.320 --> 02:45.680
but all

72
02:45.680 --> 02:49.100
I've done is added two disks to one device and right now that is going to be

73
02:49.100 --> 02:49.600
the blue

74
02:49.600 --> 02:50.600
box.

75
02:50.600 --> 02:51.960
So let's just target that for the moment.

76
02:51.960 --> 02:55.000
I'm going to set gather facts to false because it's not actually necessary to

77
02:55.000 --> 02:56.440
gather facts.

78
02:56.440 --> 03:00.200
And the very first thing I want to do right now here is to define my tasks.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

78
02:56.440 --> 03:00.200
And the very first thing I want to do right now here is to define my tasks.

79
03:00.200 --> 03:05.440
So as it stands right now, we do not actually have a dedicated Ansible RAID

80
03:05.440 --> 03:06.280
module.

81
03:06.280 --> 03:09.850
So what we're going to do here is we want to effectively send out the commands

82
03:09.850 --> 03:10.160
that

83
03:10.160 --> 03:12.960
we would ordinarily send over the shell.

84
03:12.960 --> 03:17.560
This time just directly via Ansible using the Ansible command module.

85
03:17.560 --> 03:19.080
So let's give this task a name.

86
03:19.080 --> 03:23.460
We'll just say this is called task number one, and we just create a mirror rate

87
03:23.460 --> 03:24.080
array.

88
03:24.080 --> 03:28.950
So what I'm going to do is use the Ansible built in command module right here

89
03:28.950 --> 03:29.280
and the

90
03:29.280 --> 03:32.280
parameter I'm going to specify as the CMD parameter.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
03:29.280 --> 03:32.280
parameter I'm going to specify as the CMD parameter.

91
03:32.280 --> 03:35.340
Now here is where I'm going to specify the actual commands that I would

92
03:35.340 --> 03:36.240
ordinarily type

93
03:36.240 --> 03:37.560
on the command line.

94
03:37.560 --> 03:40.760
So I'm going to say MDADM, which is the utility we're going to use.

95
03:40.760 --> 03:43.440
So I'll say dash dash create to create a new array.

96
03:43.440 --> 03:46.320
And now what I want to do is I want to specify the device I'm going to be

97
03:46.320 --> 03:46.960
creating.

98
03:46.960 --> 03:49.440
This is going to be the logical RAID array.

99
03:49.440 --> 03:53.600
So I will just say forward slash dev and it's going to be called MD0.

100
03:53.600 --> 03:58.540
This will represent the two disks when they are combined together as a mirrored

101
03:58.540 --> 03:59.240
array.

102
03:59.240 --> 04:03.640
Next I'll say dash dash level is equal to one specifying that we want a RAID
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

102
03:59.240 --> 04:03.640
Next I'll say dash dash level is equal to one specifying that we want a RAID

103
04:03.640 --> 04:04.560
one array.

104
04:04.560 --> 04:05.560
This is the mirror.

105
04:05.560 --> 04:10.520
And then I'll say dash dash rate dash devices is equal to two.

106
04:10.520 --> 04:13.640
And now I'm going to specify the two devices that I want to add in.

107
04:13.640 --> 04:19.880
Now recall over on my particular device, the name of my first disk is NVMe0.

108
04:19.880 --> 04:21.920
And the second one is NVMe0.

109
04:21.920 --> 04:26.220
And three if you happen to have a different style of naming convention, then

110
04:26.220 --> 04:26.800
you use the

111
04:26.800 --> 04:28.040
names that you see.

112
04:28.040 --> 04:29.840
Okay, so I'll just say forward slash dev.

113
04:29.840 --> 04:32.560
I'll just say N V M E zero enter.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

113
04:29.840 --> 04:32.560
I'll just say N V M E zero enter.

114
04:32.560 --> 04:37.800
And the second one will be dev N V M E zero and three.

115
04:37.800 --> 04:40.840
Now for the moment, this is all I'm going to type right here.

116
04:40.840 --> 04:43.720
Okay, so let me just save this and I'm going to try to run this playbook.

117
04:43.720 --> 04:47.080
We're actually going to have a little bit of a problem as you're going to see.

118
04:47.080 --> 04:48.520
Let's hit enter and find out.

119
04:48.520 --> 04:54.100
So the playbook executes and it just hangs and it just hangs and it hangs and

120
04:54.100 --> 04:55.080
hangs and

121
04:55.080 --> 04:57.800
hangs and if you happen to be running this at home, you're going to find out

122
04:57.800 --> 04:57.840
that this

123
04:57.840 --> 04:59.800
is going to hang for a very long time.

124
04:59.800 --> 05:03.630
So all I'm going to do right now is I'm going to press c to interrupt the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

124
04:59.800 --> 05:03.630
So all I'm going to do right now is I'm going to press c to interrupt the

125
05:03.630 --> 05:04.480
playbook.

126
05:04.480 --> 05:06.160
Pretty much this is what is happening.

127
05:06.160 --> 05:10.960
Let me go into the playbook here and if I just copy this command directly, copy

128
05:10.960 --> 05:11.800
you if I

129
05:11.800 --> 05:15.350
just type this in manually and because I'm the user here, I'm going to have to

130
05:15.350 --> 05:15.760
add in

131
05:15.760 --> 05:17.320
the pseudo command.

132
05:17.320 --> 05:19.960
Ansible is already configured to run as super user.

133
05:19.960 --> 05:24.370
If I say pseudo and I type in the password for super user and to enter, look at

134
05:24.370 --> 05:24.760
what we

135
05:24.760 --> 05:26.280
actually have here.

136
05:26.280 --> 05:29.040
This is effectively what is causing answerable on issue.

137
05:29.040 --> 05:32.770
Pretty much answerable is typing in this command and then the system is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

137
05:29.040 --> 05:32.770
Pretty much answerable is typing in this command and then the system is

138
05:32.770 --> 05:33.960
effectively asking

139
05:33.960 --> 05:35.360
answerable question.

140
05:35.360 --> 05:39.840
It's saying that this array metadata at the start may not be suitable as a boot

141
05:39.840 --> 05:40.440
device.

142
05:40.440 --> 05:45.970
So pretty much we can change the metadata to that value 0.9, which we just

143
05:45.970 --> 05:47.400
talked about.

144
05:47.400 --> 05:52.200
And what it's saying here is asking us a question, continue creating array.

145
05:52.200 --> 05:54.200
So this is a bit of a problem with Ansible.

146
05:54.200 --> 05:56.120
We've got to effectively answer this prompt.

147
05:56.120 --> 05:59.200
Now there are multiple ways in which we can do this.

148
05:59.200 --> 06:00.440
Let me show you one way.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

148
05:59.200 --> 06:00.440
Let me show you one way.

149
06:00.440 --> 06:04.200
If you happen to search for Ansible, expect and collect this link here.

150
06:04.200 --> 06:09.310
As we can see here, this particular module is designed to execute a command and

151
06:09.310 --> 06:09.960
respond

152
06:09.960 --> 06:11.160
to a prompt.

153
06:11.160 --> 06:14.420
So basically what we just saw there, we sent a command and then the system gave

154
06:14.420 --> 06:14.960
us a prompt

155
06:14.960 --> 06:16.840
back and we have to answer the question.

156
06:16.840 --> 06:20.250
So really what we can do here is if we scroll on down to the very bottom, we

157
06:20.250 --> 06:20.920
can see all

158
06:20.920 --> 06:22.600
of the ways in which we can use this.

159
06:22.600 --> 06:26.160
So what we can do here is specify a regular expression to specify what we think

160
06:26.160 --> 06:26.760
the prompt

161
06:26.760 --> 06:27.760
should be.

162
06:27.760 --> 06:29.720
In this case here, we're going to be asked for the password.

163
06:29.720 --> 06:34.320
And then as a response, we supply what we would like the password to be.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

163
06:29.720 --> 06:34.320
And then as a response, we supply what we would like the password to be.

164
06:34.320 --> 06:38.480
Similarly, if we happen to have a generic question and the example here with

165
06:38.480 --> 06:39.080
multiple

166
06:39.080 --> 06:42.790
different responses, you can specify a list of different responses that you

167
06:42.790 --> 06:43.600
want to give.

168
06:43.600 --> 06:47.500
So this is one way that you can solve the problem, but recall, we can also just

169
06:47.500 --> 06:47.840
pass

170
06:47.840 --> 06:51.120
in the metadata and modify that.

171
06:51.120 --> 06:52.200
Let's see how that operates.

172
06:52.200 --> 06:57.430
So let's go into play one dot YML and all I'm going to do here is at the very

173
06:57.430 --> 06:58.120
end, I'm

174
06:58.120 --> 07:02.600
going to say dash dash metadata and forgive the ugly line wrapping right here
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

174
06:58.120 --> 07:02.600
going to say dash dash metadata and forgive the ugly line wrapping right here

175
07:02.600 --> 07:03.160
because

176
07:03.160 --> 07:07.480
the line is so long and I'm going to set the metadata to 0.90.

177
07:07.480 --> 07:08.480
So check this out.

178
07:08.480 --> 07:12.000
If I do this, when I run this command, we're no longer going to be prompted by

179
07:12.000 --> 07:12.720
the system.

180
07:12.720 --> 07:15.720
So effectively we are skipping that particular prompt.

181
07:15.720 --> 07:17.560
So let's hit enter, check this out.

182
07:17.560 --> 07:19.560
Look at this, we get a change straight away.

183
07:19.560 --> 07:23.530
So that is one way we can do this and all I'll do is I'll go back to my device,

184
07:23.530 --> 07:24.000
the blue

185
07:24.000 --> 07:25.000
box.

186
07:25.000 --> 07:26.800
Let me just go and stop the rate array.

187
07:26.800 --> 07:32.420
I will say sudo mda m dash dash stop and the device I created was dev mda 0,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

187
07:26.800 --> 07:32.420
I will say sudo mda m dash dash stop and the device I created was dev mda 0,

188
07:32.420 --> 07:32.920
type in my

189
07:32.920 --> 07:34.320
password right here.

190
07:34.320 --> 07:42.120
And then I'll also say sudo mda m dash dash 0 dash super block dev nvm 0 enter

191
07:42.120 --> 07:43.560
and 0n3.

192
07:43.560 --> 07:47.630
So what we can also do to solve this particular problem is if I go in to the

193
07:47.630 --> 07:48.640
playbook, let's

194
07:48.640 --> 07:53.150
delete the metadata and what I will do is I'll change the module to the shell

195
07:53.150 --> 07:54.160
module and

196
07:54.160 --> 07:56.760
let me just use the pipe here to use a second line.

197
07:56.760 --> 07:59.200
And I'm going to say echo why.

198
07:59.200 --> 08:03.650
So I'm going to echo why is the answer and I'll pipe it into the output of this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

198
07:59.200 --> 08:03.650
So I'm going to echo why is the answer and I'll pipe it into the output of this

199
08:03.650 --> 08:04.480
particular

200
08:04.480 --> 08:05.480
command.

201
08:05.480 --> 08:10.320
So think about it, we're going to run this particular command here and we'll

202
08:10.320 --> 08:10.600
echo in

203
08:10.600 --> 08:11.600
the letter Y.

204
08:11.600 --> 08:12.880
Let's see if that works.

205
08:12.880 --> 08:13.880
So let's write and quit.

206
08:13.880 --> 08:18.420
If I say Ansible Playbook, play one dot Y mail and to enter and as we can see

207
08:18.420 --> 08:19.000
here, it

208
08:19.000 --> 08:21.880
seems we have created our rate array once again.

209
08:21.880 --> 08:24.480
So one last time, let's just go back to the blue box right here.

210
08:24.480 --> 08:26.000
I'm just going to repeat these commands.

211
08:26.000 --> 08:29.880
I will stop the device and I'll zero the super blocks for both devices.

212
08:29.880 --> 08:32.640
And all I want to do is I want to build out my playbook up it.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

212
08:29.880 --> 08:32.640
And all I want to do is I want to build out my playbook up it.

213
08:32.640 --> 08:35.000
So let's go into the play one dot Y mail.

214
08:35.000 --> 08:38.670
Now in order for the radar to be functional, there's a few things we also have

215
08:38.670 --> 08:39.240
to do.

216
08:39.240 --> 08:40.560
So that's creating new task.

217
08:40.560 --> 08:43.400
And what I want to do is I want to do something that we talked about and that

218
08:43.400 --> 08:44.000
is create a

219
08:44.000 --> 08:46.280
file system on the array.

220
08:46.280 --> 08:49.720
So I will use the Ansible Community File System module.

221
08:49.720 --> 08:53.850
To specify the file system type, let's maybe go with, oh, I don't know, let's

222
08:53.850 --> 08:54.600
say XFS.

223
08:54.600 --> 08:57.080
And the required parameter here is going to be the death.

224
08:57.080 --> 08:59.120
This is the device that we want to target.

225
08:59.120 --> 09:03.440
So in my case here, we're going to be targeting forward slash dev MD zero.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

225
08:59.120 --> 09:03.440
So in my case here, we're going to be targeting forward slash dev MD zero.

226
09:03.440 --> 09:05.480
This is the logical radar array.

227
09:05.480 --> 09:08.320
Now once we have the file system, what do we also have to do?

228
09:08.320 --> 09:10.520
We want to ensure that we have a mount point.

229
09:10.520 --> 09:12.440
So we'll say create a mount point.

230
09:12.440 --> 09:15.840
So I'll use the Ansible built in file module this time.

231
09:15.840 --> 09:18.320
And let's just create a path and we'll put this.

232
09:18.320 --> 09:21.780
Let's maybe say in the Mount directory and let's just create a directory called

233
09:21.780 --> 09:22.160
, oh, I don't

234
09:22.160 --> 09:24.440
know, let's just say red, hyphen dev.

235
09:24.440 --> 09:25.440
Okay.

236
09:25.440 --> 09:28.440
And I'll specify that this is going to be a directory with the state parameter.

237
09:28.440 --> 09:32.140
And now with this mountain point created, what I actually want to do is to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

237
09:28.440 --> 09:32.140
And now with this mountain point created, what I actually want to do is to

238
09:32.140 --> 09:32.720
mount the

239
09:32.720 --> 09:33.720
radar array.

240
09:33.720 --> 09:36.920
So I'm going to use the Ansible POSIX mount module and now I'm going to specify

241
09:36.920 --> 09:37.440
the path

242
09:37.440 --> 09:39.680
where I want to mount what is the path going to be?

243
09:39.680 --> 09:43.210
Well, it's going to be in the Mount directory and then red hyphen dev, the

244
09:43.210 --> 09:44.280
directory we just

245
09:44.280 --> 09:45.280
created.

246
09:45.280 --> 09:49.080
And I'll say the source is going to be forward slash dev MD zero.

247
09:49.080 --> 09:52.880
This is the red device we want to mount and now I specify the file system type.

248
09:52.880 --> 09:56.640
But it's going to be formatted with an XFS file system as we've seen here.

249
09:56.640 --> 10:01.270
Therefore, we want to specify XFS right here and now we specify the states is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

249
09:56.640 --> 10:01.270
Therefore, we want to specify XFS right here and now we specify the states is

250
10:01.270 --> 10:01.840
going to

251
10:01.840 --> 10:03.240
be mounted.

252
10:03.240 --> 10:04.840
So let's check this out right here.

253
10:04.840 --> 10:08.240
What we'll do here is say Ansible play book play one dot YML answer.

254
10:08.240 --> 10:11.640
Oh, that appears we happen to have an error it says we can't resolve this

255
10:11.640 --> 10:12.720
particular module

256
10:12.720 --> 10:13.720
here.

257
10:13.720 --> 10:17.630
And that's because I've specified the wrong module that should actually be

258
10:17.630 --> 10:18.760
community dot

259
10:18.760 --> 10:21.560
general dot fail system apologies about that.

260
10:21.560 --> 10:24.640
Let's try that entirely again and let's run the play book.

261
10:24.640 --> 10:27.630
So we create the array we build the fail system we create the mount point and

262
10:27.630 --> 10:28.440
then we mount

263
10:28.440 --> 10:29.440
the radar array.

264
10:29.440 --> 10:31.480
So let's go and see the net effect of this thing.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

264
10:29.440 --> 10:31.480
So let's go and see the net effect of this thing.

265
10:31.480 --> 10:35.080
So if I do an LSB OK dash if check this out right here.

266
10:35.080 --> 10:40.320
Let's look at this device here NVMe zero into and NVMe zero in three.

267
10:40.320 --> 10:42.720
Notice they are both part of MD zero.

268
10:42.720 --> 10:46.740
You see this they're both sharing this array and they both are formatted with

269
10:46.740 --> 10:47.240
the fail

270
10:47.240 --> 10:50.920
system XFS XFS and where exactly are they accessible?

271
10:50.920 --> 10:53.730
They're both accessible in the same mount point because logically they are

272
10:53.730 --> 10:54.160
combined

273
10:54.160 --> 10:55.160
together.

274
10:55.160 --> 10:57.720
They're both in mount rate hyphen dev.

275
10:57.720 --> 11:01.740
So to confirm what I can do is I can cat proc MD stat and to enter we can
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

275
10:57.720 --> 11:01.740
So to confirm what I can do is I can cat proc MD stat and to enter we can

276
11:01.740 --> 11:02.400
actually see

277
11:02.400 --> 11:03.920
the status of a radar array.

278
11:03.920 --> 11:07.360
We can see it is configured for red one it is active and we can see the

279
11:07.360 --> 11:08.240
participating

280
11:08.240 --> 11:12.870
discs NVM E0 into an NVMe zero in three and if I want to see more detailed

281
11:12.870 --> 11:13.880
information

282
11:13.880 --> 11:19.240
I can say pseudo MD ADM dash dash detail and then say forward slash dev MD zero

283
11:19.240 --> 11:19.600
which is

284
11:19.600 --> 11:23.040
our radar array device if I hit enter check this out right here.

285
11:23.040 --> 11:27.160
As we can see here we have fully configured a particular device to run as red

286
11:27.160 --> 11:28.040
one utilizing

287
11:28.040 --> 11:28.640
answerable.