WEBVTT

1
00:00.000 --> 00:04.280
So friends, how to be do now there was some particular clues within this

2
00:04.280 --> 00:06.240
scenario that should help guide your answer

3
00:06.240 --> 00:09.720
So let's see if you came to the same type of conclusion that I did

4
00:09.720 --> 00:13.080
Okay, so first thing I noticed in this particular scenario

5
00:13.080 --> 00:17.000
We've got a lot of new equipment. This is very important

6
00:17.000 --> 00:21.720
So what this suggests to me is we're not going to be limited by all equipment

7
00:21.720 --> 00:23.360
that only allows us to automate

8
00:23.360 --> 00:27.040
via ssh and using regular old CLI syntax

9
00:27.320 --> 00:31.120
Modern equipment is now capable of these modern interfaces
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:27.320 --> 00:31.120
Modern equipment is now capable of these modern interfaces

10
00:31.120 --> 00:34.520
So we will have access to things such as neck-on and

11
00:34.520 --> 00:38.510
Restconnth more specifically though what I'm talking about here is that we're

12
00:38.510 --> 00:41.560
going to be able to introduce data modeling into our automation

13
00:41.560 --> 00:47.110
Now next point we actually have a multi-vendor environment both Cisco and Jun

14
00:47.110 --> 00:47.480
iper

15
00:47.480 --> 00:51.600
But what do we know about automation? We want things to be as repeatable as

16
00:51.600 --> 00:52.240
possible

17
00:52.240 --> 00:56.080
So when the team leader asks how can we best implement automation?

18
00:56.080 --> 01:00.340
What I would suggest is that we look at utilizing some type of yang model data
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
00:56.080 --> 01:00.340
What I would suggest is that we look at utilizing some type of yang model data

19
01:00.340 --> 01:01.840
and where possible

20
01:01.840 --> 01:06.520
We should be making use of the open config and IATF Yang models a reason being

21
01:06.520 --> 01:09.200
is because we have a multi-vendor environment

22
01:09.200 --> 01:14.320
By using these vendor neutral models we can effectively stream in our process

23
01:14.320 --> 01:16.840
and use the same type of data

24
01:16.840 --> 01:21.120
Independent of the target device whether it's Cisco or whether it's Juniper we

25
01:21.120 --> 01:23.880
can structure our configurations in the exact same way

26
01:23.880 --> 01:27.280
So that would be the best implementation, but obviously if we happen to have

27
01:27.280 --> 01:29.760
some type of corner case whereby

28
01:29.760 --> 01:34.330
Some Cisco feature was not available on Juniper. Maybe we could use some type
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:29.760 --> 01:34.330
Some Cisco feature was not available on Juniper. Maybe we could use some type

29
01:34.330 --> 01:35.560
of native Yang model

30
01:35.560 --> 01:39.120
But in a best-case scenario using open config models where possible would

31
01:39.120 --> 01:41.160
certainly give us the easiest transition

32
01:41.160 --> 01:44.040
Now how would this solution improve our processes?

33
01:44.040 --> 01:47.840
Well by utilizing data modeling we're going to get things such as client-side

34
01:47.840 --> 01:48.600
validation

35
01:48.600 --> 01:52.580
Which is going to help us push out the correct configurations that are not full

36
01:52.580 --> 01:54.520
of errors and validate those changes

37
01:54.520 --> 01:57.160
Now also because we have this Yang model data

38
01:57.160 --> 02:01.100
What this effectively means is that we have the ability to get structured data
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:57.160 --> 02:01.100
What this effectively means is that we have the ability to get structured data

39
02:01.100 --> 02:01.400
back

40
02:01.400 --> 02:05.150
Which once again is going to be good for things such as validation because we

41
02:05.150 --> 02:07.760
're going to be able to get information from our devices

42
02:07.760 --> 02:12.460
In this programmatic manner and we can then use tools such as Python to conduct

43
02:12.460 --> 02:15.560
tests and ensure that our network is indeed stable

44
02:16.040 --> 02:19.690
Now lastly, are there any considerations that we could introduce to help the

45
02:19.690 --> 02:21.800
junior engineers in their daily duties?

46
02:21.800 --> 02:26.040
Well, what we could suggest is that this Yang model data for our configuration

47
02:26.040 --> 02:26.640
files

48
02:26.640 --> 02:31.000
We should use the Yamal file format. This is going to be very human readable
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

48
02:26.640 --> 02:31.000
We should use the Yamal file format. This is going to be very human readable

49
02:31.000 --> 02:35.000
So it is easier on the I and easier for a junior engineer to digest these

50
02:35.000 --> 02:39.080
perhaps complex configurations and we can also annotate these particular

51
02:39.080 --> 02:42.520
Files with their own comments to give context and direction

52
02:42.520 --> 02:45.860
This should help our junior engineers adapt and feel a little bit more

53
02:45.860 --> 02:49.080
confident as they adapt to these new automated processes

54
02:49.080 --> 02:52.600
And we still get all the benefits of having your data in this structured way

55
02:52.600 --> 02:55.080
that is fully capable of being automated

56
02:55.080 --> 02:59.550
So friends, that is us for our challenge on data serialization and data

57
02:59.550 --> 03:00.120
modeling
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:59.550 --> 03:00.120
modeling

58
03:00.120 --> 03:03.560
I hope it's been informative for you and I'd like to thank you for viewing