1

00:00:00,660 --> 00:00:09,890

This is the solution video for the minority dueling lap so for the first question and engine next door



2

00:00:09,920 --> 00:00:11,000

the ammo file is given.



3

00:00:11,030 --> 00:00:13,260

We have to create a port using this file.



4

00:00:13,730 --> 00:00:16,320

So let's go to the terminal and type.



5

00:00:16,340 --> 00:00:20,460

Alice and use the engine Xstrata and we'll fall.



6

00:00:20,470 --> 00:00:27,170

We can create it using cube C deal apply dash f engine Xstrata Amel to port has been created.



7

00:00:27,230 --> 00:00:34,010

So let's move on to the next question so for the second question we have to inspect the status of the



8

00:00:34,010 --> 00:00:41,100

pod so let's run cube C diesel get ports and you can see that the state is spending



9

00:00:47,020 --> 00:00:53,260

next year to figure out why the port is now pending state who will inspect the environmental of various



10

00:00:53,280 --> 00:00:55,060

gov does control plane components



11

00:00:58,560 --> 00:01:03,420

so let's run cube steel dash and cube system get pods



12

00:01:08,000 --> 00:01:11,300

as you can see we have different control plane components listed here.



13

00:01:11,300 --> 00:01:17,900

The cube EPA over at City master cube controller manager but there is one pod which is missing which



14

00:01:17,900 --> 00:01:24,920

is the cube scheduler and there is a reason why the port that we created earlier is now pending state



15

00:01:26,810 --> 00:01:28,990

so the correct answer is no scheduler.



16

00:01:29,000 --> 00:01:29,540

Present



17

00:01:34,040 --> 00:01:41,180

now for the next question we have to manually should use the port on Node 0 1 so we'll delete and recreate



18

00:01:41,180 --> 00:01:50,070

the port as necessary so let's go back and the first thing we'll do is delete the existing pod and next



19

00:01:50,070 --> 00:02:00,400

let's update the pod ammo file and under the spec section will add a field for node name as equal to



20

00:02:00,460 --> 00:02:02,860

node 0 1.



21

00:02:02,990 --> 00:02:09,170

This will ensure that the board is manually scheduled on Node 0 1 and in this case it will not make



22

00:02:09,170 --> 00:02:12,260

use of the scheduler and it is not present in the system anyway



23

00:02:16,700 --> 00:02:18,560

so let's recreate the pod



24

00:02:21,780 --> 00:02:30,270

and now let's say the status is in CubeSat you'll get ports you can see it's an all running script now



25

00:02:34,850 --> 00:02:40,880

now for the last question we are to schedule the same port on the master node so let's do the same steps



26

00:02:40,880 --> 00:02:47,690

again full delete the port make sure it's completely deleted and wait for the prompt to reappear again



27

00:02:49,410 --> 00:02:54,220

and now let's update the ammo file and change it from N0 one to master



28

00:02:58,260 --> 00:03:01,710

now save the file and recreate it using cube to apply



29

00:03:08,260 --> 00:03:10,420

wait for the port to be in a running state



30

00:03:13,430 --> 00:03:18,060

now it's not running yet so let's check it again and that was the last question.



31

00:03:18,300 --> 00:03:20,330

Well thank you for joining me in this video.



32

00:03:20,340 --> 00:03:21,710

Well see you in the next one.