1
00:00:00,180 --> 00:00:07,500
This is the solution video for the explorer Cianni Veev Lab. So for the first question and spectacular

2
00:00:07,500 --> 00:00:14,520
service and identify the network plug in configured for carbon and so will run the command, which is

3
00:00:14,520 --> 00:00:17,520
listed below, which is spacecraft Giblett.

4
00:00:22,350 --> 00:00:25,590
And our goal is to identify the network plug in used.

5
00:00:28,140 --> 00:00:36,420
So here we have in our result the network plugin used as CNN, but let us also great for and I specifically.

6
00:00:41,530 --> 00:00:47,680
So loose pipe grips, he and I, and in the last line, you'll notice that the dash dash to plug in

7
00:00:47,680 --> 00:00:48,880
is Cianni.

8
00:00:49,960 --> 00:00:51,190
So that's our answer.

9
00:00:52,380 --> 00:00:57,240
What is the path configured with all the boundaries of CNI supported plugins?

10
00:01:02,860 --> 00:01:08,680
All right, so here again, and the same output, you'll see that he NIBIN directory, which contains

11
00:01:08,680 --> 00:01:13,200
all the binaries, is under slash or pretty slash nice like.

12
00:01:13,240 --> 00:01:15,130
And so that's our answer.

13
00:01:17,950 --> 00:01:24,520
Identify which of the Blue Plugins is not available in the list of available Cianni plugins, so let's

14
00:01:24,580 --> 00:01:28,900
CD into the directory, which is or PTC, NIBIN.

15
00:01:31,720 --> 00:01:35,890
So I'm just going to copy this and CD into that directory.

16
00:01:37,080 --> 00:01:41,580
Or it can just run less and less everything inside the directory.

17
00:01:42,030 --> 00:01:50,370
And here we have different options, such as we've McQuillen, Reline Loop, DCP Bridge, etc, but

18
00:01:50,640 --> 00:01:55,050
one of the options which is missing here, and that is Sasko.

19
00:01:56,670 --> 00:01:59,360
Cisco is not available as a cianni.

20
00:02:01,060 --> 00:02:05,470
What is this in a plugin configured to be used on this when it is cluster?

21
00:02:06,710 --> 00:02:14,300
So let's check the CNN configuration, which is under ETECSA and I need Dhody, and here you'll find

22
00:02:14,300 --> 00:02:19,360
the configuration file for V, which gives us a good indication that it's running veve.

23
00:02:20,090 --> 00:02:22,620
There is another way to find this out as well.

24
00:02:22,640 --> 00:02:29,570
We can check still get pots and decubitus in this space and actually show you the veev pots, which

25
00:02:29,570 --> 00:02:30,830
is created on discloser.

26
00:02:31,670 --> 00:02:39,080
And the next question, what bindery executable file will be run by Kubelik after a container and its

27
00:02:39,080 --> 00:02:41,240
associated namespace are created?

28
00:02:41,720 --> 00:02:45,560
So for this we'll have to check the configuration file for Veev.

29
00:02:46,040 --> 00:02:50,410
And here on the plug ins you'll see that the type as we've met.

30
00:02:50,450 --> 00:02:52,890
So that's our option here.

31
00:02:53,690 --> 00:02:56,480
So that's the binary that will be called Venette.

32
00:02:56,960 --> 00:02:58,350
So that was the last question.

33
00:02:58,370 --> 00:03:01,040
This was a very straightforward and simple app.

34
00:03:01,310 --> 00:03:02,740
So I'll see you and the next one.

35
00:03:02,750 --> 00:03:03,140
Thank you.
