WEBVTT

1
00:00:00.120 --> 00:00:03.120
<v Speaker 1>Welcome to the deep dive. Looks like someone is ready

2
00:00:03.160 --> 00:00:05.879
<v Speaker 1>to tackle network programmability head on.

3
00:00:06.440 --> 00:00:07.000
<v Speaker 2>You could see that.

4
00:00:07.759 --> 00:00:10.720
<v Speaker 1>We've got excerpts from a book on yang, a few

5
00:00:10.800 --> 00:00:14.720
<v Speaker 1>white papers, even some RFCs. Someone's been doing their homework.

6
00:00:15.119 --> 00:00:17.160
<v Speaker 2>It seems like managing the network is becoming a bit

7
00:00:17.160 --> 00:00:20.480
<v Speaker 2>of a struggle, like hurting cats. Maybe more like.

8
00:00:20.480 --> 00:00:23.359
<v Speaker 1>Hurting cats with a spoon from the sound of it. Okay,

9
00:00:23.559 --> 00:00:26.559
<v Speaker 1>but hey, maybe we can help with that, expert speaker,

10
00:00:26.600 --> 00:00:27.079
<v Speaker 1>what do you think?

11
00:00:27.320 --> 00:00:30.719
<v Speaker 2>Absolutely, I think it's safe to say the old ways

12
00:00:30.760 --> 00:00:34.240
<v Speaker 2>of managing networks, well, they just aren't cutting it anymore.

13
00:00:34.280 --> 00:00:35.600
<v Speaker 1>You're definitely not alone there.

14
00:00:35.719 --> 00:00:37.280
<v Speaker 2>I think a lot of folks are feeling that pain.

15
00:00:37.359 --> 00:00:40.679
<v Speaker 1>Yeah, that makes sense. I've heard whispers that the command

16
00:00:40.719 --> 00:00:43.960
<v Speaker 1>line interface, the CLI, is kind of reaching its limits.

17
00:00:44.280 --> 00:00:45.840
<v Speaker 2>You know. It's like it's like trying to write a

18
00:00:45.840 --> 00:00:46.719
<v Speaker 2>novel on a typewriter.

19
00:00:46.880 --> 00:00:49.640
<v Speaker 1>It got the job done back then, it did, Yeah.

20
00:00:49.399 --> 00:00:52.039
<v Speaker 2>But these days you need something, I don't know, a

21
00:00:52.079 --> 00:00:53.039
<v Speaker 2>little more powerful.

22
00:00:53.200 --> 00:00:55.719
<v Speaker 1>Yeah, you need a word processor or something like that.

23
00:00:56.159 --> 00:00:59.159
<v Speaker 1>But what's so limiting about the CLI these days, especially

24
00:00:59.159 --> 00:01:00.920
<v Speaker 1>with networks becoming so complex.

25
00:01:01.439 --> 00:01:06.599
<v Speaker 2>Well, for one, modern networks are just massive it's gotten

26
00:01:06.680 --> 00:01:09.959
<v Speaker 2>way beyond what humans can reasonably manage, right I think

27
00:01:09.959 --> 00:01:12.400
<v Speaker 2>about it. Businesses need to be able to like deploy

28
00:01:12.519 --> 00:01:17.879
<v Speaker 2>new services instantly in seconds, not months, and that kind

29
00:01:17.920 --> 00:01:22.879
<v Speaker 2>of agility is just impossible with like manual CLI commands.

30
00:01:22.959 --> 00:01:26.519
<v Speaker 1>It's yeah, like you're stuck typing in commands one by one.

31
00:01:26.599 --> 00:01:29.280
<v Speaker 2>By one, hoping you don't, you know, make a typo

32
00:01:29.400 --> 00:01:30.519
<v Speaker 2>and crash the whole system.

33
00:01:30.599 --> 00:01:33.680
<v Speaker 1>Yeah, it's it's slow, it's prone to errors. It's not

34
00:01:33.719 --> 00:01:35.000
<v Speaker 1>built for automation.

35
00:01:34.920 --> 00:01:35.439
<v Speaker 2>Definitely not.

36
00:01:35.680 --> 00:01:38.959
<v Speaker 1>And then imagine being afraid to even upgrade your devices

37
00:01:39.000 --> 00:01:41.760
<v Speaker 1>because you think, oh, my custom scripts are going to break, right,

38
00:01:42.079 --> 00:01:44.799
<v Speaker 1>you know that's the reality for a lot of people.

39
00:01:45.079 --> 00:01:46.280
<v Speaker 2>Yeah, that's a scary thought.

40
00:01:46.599 --> 00:01:50.439
<v Speaker 1>They're clinging to CLI based management. Clies just weren't built

41
00:01:50.439 --> 00:01:53.159
<v Speaker 1>to talk to machines. And if we want automation, we

42
00:01:53.239 --> 00:01:55.879
<v Speaker 1>need standards, we need programmable interfaces.

43
00:01:55.920 --> 00:01:57.519
<v Speaker 2>Okay, I'm sensing a butt coming.

44
00:01:58.239 --> 00:02:02.879
<v Speaker 1>Oh that's where Yang comes in. Yang Young. I knew it. Okay.

45
00:02:02.920 --> 00:02:05.719
<v Speaker 1>So everyone's saying Yang is like the magic solution to

46
00:02:05.799 --> 00:02:09.479
<v Speaker 1>all our CLI woes, but like, what is it really

47
00:02:09.879 --> 00:02:12.199
<v Speaker 1>and how does it actually solve these problems?

48
00:02:12.479 --> 00:02:16.840
<v Speaker 2>So Yang stands for yet another next generation. It's kind

49
00:02:16.840 --> 00:02:19.400
<v Speaker 2>of a funny name, yeah, but basically it's a language

50
00:02:19.400 --> 00:02:23.120
<v Speaker 2>for describing network devices and services like a blueprint.

51
00:02:23.240 --> 00:02:25.840
<v Speaker 1>You know, so instead of having a jumble of different

52
00:02:25.840 --> 00:02:28.879
<v Speaker 1>commands for every vendor, yeah, exactly, Like we're giving all

53
00:02:28.919 --> 00:02:31.599
<v Speaker 1>our devices one language they can understand exactly.

54
00:02:31.879 --> 00:02:35.800
<v Speaker 2>Yang models are like contracts between your devices and applications.

55
00:02:35.840 --> 00:02:37.319
<v Speaker 2>Make sure everyone's on the same page.

56
00:02:37.400 --> 00:02:39.680
<v Speaker 1>Okay, that's pretty neat. But if YANG is so great,

57
00:02:40.039 --> 00:02:43.400
<v Speaker 1>how come everyone isn't already using it? Any downsides? Or

58
00:02:43.439 --> 00:02:44.960
<v Speaker 1>is it just you know, too good to be true.

59
00:02:45.319 --> 00:02:47.960
<v Speaker 2>Well, like anything new, there is a learning curve. Yang

60
00:02:48.080 --> 00:02:50.199
<v Speaker 2>is a pretty you know, ro best language.

61
00:02:50.240 --> 00:02:52.400
<v Speaker 1>So it's like learning a new programming language. You need

62
00:02:52.439 --> 00:02:54.120
<v Speaker 1>to put in the time, but then you can do

63
00:02:54.280 --> 00:02:57.560
<v Speaker 1>all sorts of amazing things exactly. Okay, So let's say

64
00:02:57.560 --> 00:03:00.759
<v Speaker 1>I'm sold on this YANG thing. Where do I even begin?

65
00:03:00.919 --> 00:03:02.680
<v Speaker 1>How does this work in practice?

66
00:03:02.879 --> 00:03:05.439
<v Speaker 2>Okay? So let's use this book soon an example from

67
00:03:05.479 --> 00:03:09.120
<v Speaker 2>the book you sent. Imagine like a network connecting bookstores

68
00:03:09.120 --> 00:03:12.599
<v Speaker 2>and publishers and customers. Okay, you can use Yang to

69
00:03:12.639 --> 00:03:17.080
<v Speaker 2>model everything, inventory, orders, delivery routes, all of it.

70
00:03:17.479 --> 00:03:19.840
<v Speaker 1>So I can actually define like this is a bookstore,

71
00:03:19.919 --> 00:03:23.039
<v Speaker 1>it has these capabilities, and like it needs to connect

72
00:03:23.039 --> 00:03:24.639
<v Speaker 1>to the publisher's network this way.

73
00:03:24.759 --> 00:03:28.520
<v Speaker 2>Yeah, exactly, you're not just defining data, you're defining relationships

74
00:03:28.560 --> 00:03:30.159
<v Speaker 2>between all the parts of your network.

75
00:03:30.199 --> 00:03:33.280
<v Speaker 1>Okay, that's pretty cool. But Yang itself is just a language, right,

76
00:03:33.439 --> 00:03:37.520
<v Speaker 1>It's not actually like sending commands to my routers and switches.

77
00:03:37.680 --> 00:03:38.719
<v Speaker 1>How does that part work?

78
00:03:38.879 --> 00:03:42.159
<v Speaker 2>Right? Yang sets the rules, but we need something to

79
00:03:42.199 --> 00:03:44.280
<v Speaker 2>make it happen. That's where these protocols come in, like

80
00:03:44.360 --> 00:03:45.439
<v Speaker 2>net cof and rest com.

81
00:03:45.719 --> 00:03:48.960
<v Speaker 1>Okay, so Yang is like the blueprint, and then netcof

82
00:03:49.000 --> 00:03:52.199
<v Speaker 1>and restcom are like the construction workers who actually build

83
00:03:52.280 --> 00:03:55.199
<v Speaker 1>the thing. They handle the communication with the devices.

84
00:03:55.479 --> 00:03:57.479
<v Speaker 2>That's a great way to put it, and each one

85
00:03:57.560 --> 00:04:00.479
<v Speaker 2>has its own strengths and weaknesses. You know. Net con

86
00:04:00.560 --> 00:04:04.599
<v Speaker 2>it's very robust, great for big changes where you absolutely

87
00:04:04.639 --> 00:04:05.879
<v Speaker 2>cannot afford an error.

88
00:04:06.000 --> 00:04:08.479
<v Speaker 1>That sounds like a lifesaver when you're dealing with a

89
00:04:08.479 --> 00:04:11.879
<v Speaker 1>complex network. One small mistake could cause chaos.

90
00:04:12.159 --> 00:04:15.360
<v Speaker 2>Exactly. And then you've got rest con. Okay, rest coon

91
00:04:15.439 --> 00:04:18.839
<v Speaker 2>if is more web friendly, good for integrating with modern

92
00:04:18.879 --> 00:04:20.199
<v Speaker 2>web services, so I.

93
00:04:20.160 --> 00:04:23.279
<v Speaker 1>Could manage network devices from a web browser, or even

94
00:04:23.399 --> 00:04:26.439
<v Speaker 1>tie them into my company's existing web application.

95
00:04:26.120 --> 00:04:28.120
<v Speaker 2>Exactly opens up a lot of possibilities.

96
00:04:28.360 --> 00:04:30.800
<v Speaker 1>The sources also mentioned something called GNMI.

97
00:04:31.000 --> 00:04:34.720
<v Speaker 2>What's that about, Oh, GNMI that stands for GRPFE Network

98
00:04:34.759 --> 00:04:39.560
<v Speaker 2>Management Interface. It's newer known for its speed and efficiency. Okay,

99
00:04:39.639 --> 00:04:41.600
<v Speaker 2>particularly good for things like telemetry.

100
00:04:41.680 --> 00:04:45.120
<v Speaker 1>Telemetry. Right, Yeah, that's about getting real time insights from

101
00:04:45.120 --> 00:04:48.759
<v Speaker 1>the network, isn't it. Instead of constantly asking devices for updates,

102
00:04:48.800 --> 00:04:50.120
<v Speaker 1>it's like a live stream of.

103
00:04:50.120 --> 00:04:52.920
<v Speaker 2>Data precisely, no more waiting around. You just get those

104
00:04:52.959 --> 00:04:53.839
<v Speaker 2>insights instantly.

105
00:04:53.959 --> 00:04:55.920
<v Speaker 1>This makes a lot of sense. But how does all

106
00:04:55.959 --> 00:04:59.480
<v Speaker 1>of this tie back into YANG? How do these protocols

107
00:04:59.480 --> 00:05:00.560
<v Speaker 1>actually work work together?

108
00:05:01.000 --> 00:05:03.519
<v Speaker 2>That is a fantastic question and one that we will

109
00:05:03.560 --> 00:05:06.000
<v Speaker 2>definitely be unpacking in the next part of our deep dive.

110
00:05:06.120 --> 00:05:07.240
<v Speaker 1>Sounds good, but.

111
00:05:07.240 --> 00:05:08.759
<v Speaker 2>For now, I want to leave you with this thought.

112
00:05:09.079 --> 00:05:12.879
<v Speaker 1>Okay, YANG isn't just about automating network management. It's about

113
00:05:13.040 --> 00:05:17.959
<v Speaker 1>laying the foundation for intelligent networks, networks that can adapt

114
00:05:18.000 --> 00:05:19.600
<v Speaker 1>and give you real time insights.

115
00:05:20.000 --> 00:05:22.560
<v Speaker 2>That's pretty mind blowing. We've gone from the limitations of

116
00:05:22.600 --> 00:05:25.439
<v Speaker 2>the CLI to this whole new world of what is

117
00:05:25.480 --> 00:05:29.360
<v Speaker 2>it network programmability, all powered by Yang in these different

118
00:05:29.360 --> 00:05:32.040
<v Speaker 2>protocols exactly. But before we get lost in all the

119
00:05:32.040 --> 00:05:33.920
<v Speaker 2>technical details, I want to take a step back. Why

120
00:05:33.959 --> 00:05:36.439
<v Speaker 2>should all of this matter to our listeners? What's the

121
00:05:36.439 --> 00:05:39.680
<v Speaker 2>big takeaway here? Welcome back? So are you ready to

122
00:05:39.720 --> 00:05:42.519
<v Speaker 2>see how all this Yang stuff actually works in practice?

123
00:05:42.560 --> 00:05:42.879
<v Speaker 2>I am.

124
00:05:43.240 --> 00:05:45.920
<v Speaker 1>Let's get down to the nitty gritty. How does Yang

125
00:05:46.199 --> 00:05:49.759
<v Speaker 1>actually help me, you know, manage my network? And particularly

126
00:05:49.800 --> 00:05:54.160
<v Speaker 1>thinking about things like setting up a secure VPN connection

127
00:05:54.319 --> 00:05:57.600
<v Speaker 1>between like multiple sites. That always feels like a major headache.

128
00:05:57.639 --> 00:05:59.480
<v Speaker 2>Oh, I can definitely see that being a pain point.

129
00:05:59.560 --> 00:06:02.319
<v Speaker 2>In the old CLI centric world. That would mean logging

130
00:06:02.399 --> 00:06:05.759
<v Speaker 2>into every single device, typing in commands, hoping you don't

131
00:06:05.759 --> 00:06:10.439
<v Speaker 2>make a typo. It's a recipe for late night's troubleshooting.

132
00:06:10.600 --> 00:06:12.560
<v Speaker 1>Tell me about it, and then if you need to

133
00:06:12.560 --> 00:06:14.839
<v Speaker 1>make a change, you got to go through that whole

134
00:06:14.879 --> 00:06:17.680
<v Speaker 1>process again on every single device exactly.

135
00:06:18.120 --> 00:06:20.319
<v Speaker 2>And that's where YANG can make a world of difference.

136
00:06:20.439 --> 00:06:24.000
<v Speaker 2>Instead of manually configuring everything, you define a YANG model

137
00:06:24.079 --> 00:06:30.439
<v Speaker 2>that captures your VPN service, IP addresses, encryption, authentication methods,

138
00:06:30.480 --> 00:06:31.519
<v Speaker 2>all the important stuff.

139
00:06:31.560 --> 00:06:34.160
<v Speaker 1>So it's like a blueprint for my VPN, but in

140
00:06:34.279 --> 00:06:35.920
<v Speaker 1>code exactly.

141
00:06:36.000 --> 00:06:38.759
<v Speaker 2>And then remember those protocols we talked about metconf and

142
00:06:38.800 --> 00:06:41.800
<v Speaker 2>rest CONC. They take that YANG model and translate it

143
00:06:41.839 --> 00:06:43.959
<v Speaker 2>into device specific configurations.

144
00:06:44.240 --> 00:06:46.639
<v Speaker 1>So instead of me typing in commands on each device,

145
00:06:46.800 --> 00:06:48.879
<v Speaker 1>net con anofhores CONC does it for me.

146
00:06:49.120 --> 00:06:51.759
<v Speaker 2>Exactly, And you can use that same YANG model for

147
00:06:51.879 --> 00:06:54.480
<v Speaker 2>all sorts of different devices, regardless of the vendor.

148
00:06:54.560 --> 00:06:56.759
<v Speaker 1>So I don't need to learn a different set of

149
00:06:56.800 --> 00:06:59.319
<v Speaker 1>commands for each brand of router or sweat.

150
00:06:59.480 --> 00:07:03.160
<v Speaker 2>Nope. That's the beauty of YANG. It eliminates the need

151
00:07:03.279 --> 00:07:05.079
<v Speaker 2>for vendor specific expertise.

152
00:07:05.240 --> 00:07:07.959
<v Speaker 1>That's a huge time saver for sure. Okay, but what

153
00:07:08.000 --> 00:07:10.160
<v Speaker 1>about monitoring. Once my VPN is set up, how do

154
00:07:10.199 --> 00:07:11.199
<v Speaker 1>I know it's actually working?

155
00:07:11.480 --> 00:07:14.879
<v Speaker 2>Well, remember telemetry. You can define YANG models for that too.

156
00:07:15.360 --> 00:07:17.879
<v Speaker 2>You can get real time insights into the performance of

157
00:07:17.879 --> 00:07:19.120
<v Speaker 2>your VPN.

158
00:07:18.800 --> 00:07:20.920
<v Speaker 1>So instead of waiting for things to break, I can

159
00:07:20.959 --> 00:07:23.800
<v Speaker 1>actually see how things are performing and fix problems before

160
00:07:23.800 --> 00:07:25.439
<v Speaker 1>they even happen exactly.

161
00:07:25.839 --> 00:07:28.959
<v Speaker 2>You can see bottlenecks, security issues, anything that might be

162
00:07:28.959 --> 00:07:31.560
<v Speaker 2>affecting your VPN. It's all about being proactive.

163
00:07:31.879 --> 00:07:35.480
<v Speaker 1>Okay. So that's for managing individual services like my VPN,

164
00:07:35.839 --> 00:07:38.639
<v Speaker 1>But what about more complex things like, I don't know,

165
00:07:38.839 --> 00:07:42.480
<v Speaker 1>managing a bunch of different network services across multiple clouds.

166
00:07:42.720 --> 00:07:44.519
<v Speaker 1>Can Yang handle that?

167
00:07:44.519 --> 00:07:47.240
<v Speaker 2>That's where Yang really shines. It allows you to go

168
00:07:47.279 --> 00:07:51.839
<v Speaker 2>beyond managing individual devices and actually orchestrate entire network services.

169
00:07:52.279 --> 00:07:54.480
<v Speaker 1>So it's like, I don't know, like a conductor leading

170
00:07:54.480 --> 00:07:57.199
<v Speaker 1>an orchestra, but instead of instruments, it's all these different

171
00:07:57.199 --> 00:07:58.720
<v Speaker 1>network services exactly.

172
00:07:59.160 --> 00:08:03.040
<v Speaker 2>You define the relationships between those services, their dependencies, and

173
00:08:03.360 --> 00:08:06.000
<v Speaker 2>Yang takes care of the rest. It's really about creating

174
00:08:06.000 --> 00:08:07.759
<v Speaker 2>a symphony of network services.

175
00:08:07.800 --> 00:08:10.800
<v Speaker 1>But you mentioned earlier that Yang is a pretty complex language.

176
00:08:10.959 --> 00:08:12.519
<v Speaker 1>How do I even get started with this? Is this

177
00:08:12.680 --> 00:08:14.439
<v Speaker 1>like years of training.

178
00:08:14.439 --> 00:08:17.759
<v Speaker 2>You don't need to become a Yang expert overnight. Start

179
00:08:17.759 --> 00:08:21.879
<v Speaker 2>with the basics. Containers, lists, leafs. Those are the building

180
00:08:21.959 --> 00:08:22.720
<v Speaker 2>blocks of Yang.

181
00:08:22.759 --> 00:08:24.839
<v Speaker 1>Okay, so those are the basics. But I'm guessing there's

182
00:08:24.879 --> 00:08:26.360
<v Speaker 1>a lot more to it than just that, right.

183
00:08:26.399 --> 00:08:29.759
<v Speaker 2>Oh yeah, there's a lot more things like augmentations and deviations.

184
00:08:29.800 --> 00:08:32.120
<v Speaker 1>Augmentations and deviations, what are those?

185
00:08:32.240 --> 00:08:34.919
<v Speaker 2>Think of augmentations Like adding an extension to your house,

186
00:08:35.639 --> 00:08:39.960
<v Speaker 2>You're expanding its capabilities without changing the core structure. With Yang,

187
00:08:40.320 --> 00:08:43.679
<v Speaker 2>augmentations let you add new stuff to existing models without

188
00:08:43.759 --> 00:08:47.159
<v Speaker 2>changing the original and deviations let you tweak a YANG

189
00:08:47.399 --> 00:08:49.759
<v Speaker 2>model for like specific.

190
00:08:49.320 --> 00:08:52.120
<v Speaker 1>Devices, So it's like I can customize YANG to fit

191
00:08:52.159 --> 00:08:53.000
<v Speaker 1>my needs.

192
00:08:52.799 --> 00:08:56.240
<v Speaker 2>Exactly, and that's really important for building you know, flexible

193
00:08:56.279 --> 00:08:58.840
<v Speaker 2>and scalable solutions, and you don't have to figure all

194
00:08:58.879 --> 00:09:00.679
<v Speaker 2>of this out on your own. There are tools out

195
00:09:00.720 --> 00:09:03.639
<v Speaker 2>there to help you, like paying libbyaning wide DK.

196
00:09:03.919 --> 00:09:06.679
<v Speaker 1>So these tools they're like my power tools for building

197
00:09:06.679 --> 00:09:08.480
<v Speaker 1>and managing my network precisely.

198
00:09:08.600 --> 00:09:10.519
<v Speaker 2>They take all the complexity of YANG and make it

199
00:09:10.799 --> 00:09:11.639
<v Speaker 2>actually usable.

200
00:09:12.080 --> 00:09:14.639
<v Speaker 1>Okay, but with so many tools out there, it's easy

201
00:09:14.679 --> 00:09:16.919
<v Speaker 1>to get overwhelmed. Where do I even begin?

202
00:09:17.360 --> 00:09:19.960
<v Speaker 2>Start with what you need and build your toolkit as

203
00:09:20.000 --> 00:09:22.759
<v Speaker 2>you go. The good news is that the YANG community

204
00:09:22.840 --> 00:09:26.360
<v Speaker 2>is super helpful. Tons of resources online. People are always

205
00:09:26.399 --> 00:09:27.440
<v Speaker 2>willing to lend a hand.

206
00:09:27.759 --> 00:09:30.320
<v Speaker 1>That's reassuring. It's less scary when you know there's a

207
00:09:30.320 --> 00:09:33.360
<v Speaker 1>community to support you. But before we go too deep

208
00:09:33.360 --> 00:09:34.799
<v Speaker 1>into the weeds, I want to bring it back to

209
00:09:34.840 --> 00:09:38.159
<v Speaker 1>the big picture. All this talk about YANG is great,

210
00:09:38.240 --> 00:09:42.080
<v Speaker 1>but why should businesses care? What's the real world impact?

211
00:09:42.399 --> 00:09:46.480
<v Speaker 2>Well, at its core, network programmability is all about making

212
00:09:46.519 --> 00:09:50.679
<v Speaker 2>businesses more agile, more efficient, more innovative.

213
00:09:50.240 --> 00:09:53.279
<v Speaker 1>So it's not just about automating tasks, it's about changing

214
00:09:53.320 --> 00:09:55.120
<v Speaker 1>how businesses operate exactly.

215
00:09:55.480 --> 00:09:58.679
<v Speaker 2>Businesses can save money, they can deploy news services faster,

216
00:09:58.799 --> 00:10:02.000
<v Speaker 2>they can improve network really ability. It's really a game changer.

217
00:10:02.159 --> 00:10:05.159
<v Speaker 1>Those are some pretty compelling benefits. So network programmability is

218
00:10:05.200 --> 00:10:07.600
<v Speaker 1>kind of like essential for digital transformation.

219
00:10:07.799 --> 00:10:10.360
<v Speaker 2>It is businesses that don't adapt are going to fall behind.

220
00:10:10.559 --> 00:10:13.600
<v Speaker 1>Okay, I'm convinced YANG sounds like a must have for

221
00:10:13.679 --> 00:10:16.600
<v Speaker 1>any business that relies on its network. But let's be real,

222
00:10:16.759 --> 00:10:19.440
<v Speaker 1>it can't all be smooth sailing, right, Yeah. What are

223
00:10:19.480 --> 00:10:22.000
<v Speaker 1>some of the challenges businesses might face along the way.

224
00:10:22.200 --> 00:10:26.480
<v Speaker 2>Of course, implementing any new technology has its challenges.

225
00:10:26.519 --> 00:10:29.080
<v Speaker 1>Like what what should businesses be prepared for?

226
00:10:29.519 --> 00:10:33.360
<v Speaker 2>One common challenge is finding skilled people. Yang experts are

227
00:10:33.360 --> 00:10:36.799
<v Speaker 2>in high demand, so finding and keeping them can be tough.

228
00:10:37.200 --> 00:10:39.759
<v Speaker 1>Yeah, I can see that it's such a specialized field.

229
00:10:39.879 --> 00:10:42.559
<v Speaker 1>Investing in training is probably crucial, right, absolutely.

230
00:10:42.960 --> 00:10:45.519
<v Speaker 2>And then there's the human element, getting people to change

231
00:10:45.519 --> 00:10:48.720
<v Speaker 2>their ways to embrace this new way of doing things.

232
00:10:48.960 --> 00:10:49.720
<v Speaker 2>That can be tough.

233
00:10:50.039 --> 00:10:52.559
<v Speaker 1>People are creatures of habit. It's understandable that some might

234
00:10:52.600 --> 00:10:54.039
<v Speaker 1>be resistant to change of.

235
00:10:54.000 --> 00:10:58.720
<v Speaker 2>Course, but it's all about communication, explaining the benefits, addressing

236
00:10:58.720 --> 00:10:59.519
<v Speaker 2>those concerns.

237
00:11:00.159 --> 00:11:03.519
<v Speaker 1>So those are the people challenges. What about technical challenges.

238
00:11:03.080 --> 00:11:06.480
<v Speaker 2>Well, one thing is ensuring that everything works together different vendors,

239
00:11:06.480 --> 00:11:10.879
<v Speaker 2>different platforms. Even though YANG is a standard, there can

240
00:11:10.960 --> 00:11:13.279
<v Speaker 2>be variations in how it's implemented.

241
00:11:12.840 --> 00:11:14.559
<v Speaker 1>So it's not always just plug and play.

242
00:11:14.639 --> 00:11:16.639
<v Speaker 2>You got to do your testing, make sure your YANG

243
00:11:16.679 --> 00:11:18.639
<v Speaker 2>models work across your entire network.

244
00:11:18.720 --> 00:11:19.200
<v Speaker 1>Makes sense.

245
00:11:19.519 --> 00:11:22.799
<v Speaker 2>Anything else security, As we automate more things, we need

246
00:11:22.840 --> 00:11:24.559
<v Speaker 2>to be extra careful about security.

247
00:11:24.840 --> 00:11:27.440
<v Speaker 1>Yeah, that makes sense, especially when we're talking about automating

248
00:11:27.519 --> 00:11:29.200
<v Speaker 1>critical network functions.

249
00:11:29.279 --> 00:11:34.440
<v Speaker 2>Absolutely, authentication, authorization, encryption, those are all crucial.

250
00:11:34.600 --> 00:11:37.440
<v Speaker 1>This has been really insightful. I'm starting to grasp the

251
00:11:37.600 --> 00:11:40.279
<v Speaker 1>potential of YANG, but also the complexity.

252
00:11:40.480 --> 00:11:43.840
<v Speaker 2>You've got it. It's powerful, but it's not magic. You

253
00:11:43.879 --> 00:11:45.759
<v Speaker 2>need planning, you need the right expertise.

254
00:11:45.879 --> 00:11:47.919
<v Speaker 1>Okay, before we wrap up this part of our deep dive,

255
00:11:48.000 --> 00:11:51.039
<v Speaker 1>one more question. We've talked about the theory, the challenges,

256
00:11:51.120 --> 00:11:54.080
<v Speaker 1>but I'm really curious about real world examples how our

257
00:11:54.120 --> 00:11:57.559
<v Speaker 1>businesses actually using YANG to solve real problems.

258
00:11:57.600 --> 00:11:59.879
<v Speaker 2>That's a great question, Yeah, and one that we will

259
00:12:00.240 --> 00:12:01.879
<v Speaker 2>into in the final part of our deep dive.

260
00:12:02.000 --> 00:12:04.240
<v Speaker 1>This is getting exciting. I can't wait to see how

261
00:12:04.320 --> 00:12:07.120
<v Speaker 1>YANG is being used out in the wild. But for now,

262
00:12:07.200 --> 00:12:09.720
<v Speaker 1>let's take a short break and come back refreshed and

263
00:12:09.840 --> 00:12:12.159
<v Speaker 1>ready to finish our deep dive into the world of

264
00:12:12.240 --> 00:12:16.639
<v Speaker 1>network programmability. Welcome back for the final part of our

265
00:12:16.679 --> 00:12:19.879
<v Speaker 1>deep dive. It's been quite the journey exploring this whole

266
00:12:19.879 --> 00:12:21.519
<v Speaker 1>world of network programmability.

267
00:12:21.840 --> 00:12:24.080
<v Speaker 2>It really has. We've covered a lot of ground we have.

268
00:12:24.200 --> 00:12:27.080
<v Speaker 1>From the good old CLI all the way to YANG

269
00:12:27.320 --> 00:12:30.000
<v Speaker 1>and these new protocol. I'm excited to hear about those

270
00:12:30.000 --> 00:12:32.960
<v Speaker 1>real world examples. You promised you know how our business

271
00:12:33.000 --> 00:12:36.799
<v Speaker 1>is actually using YANG to solve real problems and you know,

272
00:12:36.840 --> 00:12:38.120
<v Speaker 1>make their networks run better.

273
00:12:38.360 --> 00:12:41.879
<v Speaker 2>Let's start with a big one service providers, telecom companies.

274
00:12:42.120 --> 00:12:44.919
<v Speaker 2>They're using YANG to automate all those services we use

275
00:12:44.960 --> 00:12:49.080
<v Speaker 2>every day, broadband, mobile, data, voi, IP, you name it.

276
00:12:49.360 --> 00:12:53.480
<v Speaker 1>So they're not like manually configuring routers and switches for

277
00:12:53.600 --> 00:12:54.960
<v Speaker 1>every new customer anymore.

278
00:12:55.080 --> 00:12:58.960
<v Speaker 2>Exactly. Yang models define what each service needs and then

279
00:12:59.080 --> 00:13:02.679
<v Speaker 2>orchestration system take care of the configuration automatically.

280
00:13:02.840 --> 00:13:05.080
<v Speaker 1>I bet that not only saves time, but also cuts

281
00:13:05.080 --> 00:13:07.480
<v Speaker 1>down on those human errors.

282
00:13:07.559 --> 00:13:10.639
<v Speaker 2>You got it. And it's not just about the initial setup.

283
00:13:10.919 --> 00:13:15.480
<v Speaker 2>YANG also helps with monitoring performance, finding problems, and even

284
00:13:15.519 --> 00:13:17.120
<v Speaker 2>optimizing traffic in real time.

285
00:13:17.240 --> 00:13:19.960
<v Speaker 1>So it's like having a self driving network. That's pretty amazing.

286
00:13:20.000 --> 00:13:22.440
<v Speaker 2>It is pretty amazing. And service providers need this kind

287
00:13:22.440 --> 00:13:24.799
<v Speaker 2>of automation to keep up with the demand for bandwidth

288
00:13:24.799 --> 00:13:27.240
<v Speaker 2>and need to scale quickly, and YANG helps them do that.

289
00:13:27.600 --> 00:13:30.320
<v Speaker 1>Okay, so Yang's great for service providers, but what about

290
00:13:30.360 --> 00:13:33.279
<v Speaker 1>other industries? Are regular companies using this too? Oh?

291
00:13:33.399 --> 00:13:36.879
<v Speaker 2>Yeah, absolutely, enterprises are using YANG for all sorts of things,

292
00:13:36.960 --> 00:13:40.240
<v Speaker 2>data centers, office networks, even the Internet of Things.

293
00:13:40.399 --> 00:13:43.600
<v Speaker 1>Wow, so YANG isn't just for telecoms. It's going mainstream.

294
00:13:43.679 --> 00:13:46.159
<v Speaker 1>Can you give me an example, like, how are companies

295
00:13:46.240 --> 00:13:47.600
<v Speaker 1>using it in their data centers?

296
00:13:47.919 --> 00:13:50.559
<v Speaker 2>Well, for example, they're using to automate the setup of

297
00:13:51.159 --> 00:13:55.720
<v Speaker 2>virtual machines, storage networks, load balancers, all those crucial data

298
00:13:55.720 --> 00:13:57.159
<v Speaker 2>center components so they.

299
00:13:57.000 --> 00:14:00.919
<v Speaker 1>Can like scale their IT infrastructure on demand, right, responding

300
00:14:00.960 --> 00:14:03.360
<v Speaker 1>quickly to changes in their business exactly.

301
00:14:03.519 --> 00:14:06.399
<v Speaker 2>That's essential these days. And YANG also plays a big

302
00:14:06.480 --> 00:14:10.519
<v Speaker 2>role in technologies like SDN and NFB, software defined networking

303
00:14:10.799 --> 00:14:12.440
<v Speaker 2>and network functions virtualization.

304
00:14:12.559 --> 00:14:15.000
<v Speaker 1>So it sounds like YANG is a key part of

305
00:14:15.039 --> 00:14:17.600
<v Speaker 1>this whole software defined future of networking.

306
00:14:17.720 --> 00:14:20.840
<v Speaker 2>It is, and as networks get more complex, more spread out,

307
00:14:21.320 --> 00:14:23.000
<v Speaker 2>yang's importance is only going to grow.

308
00:14:23.240 --> 00:14:26.320
<v Speaker 1>That makes a lot of sense. But like any new technology,

309
00:14:26.399 --> 00:14:28.679
<v Speaker 1>I'm sure there are challenges and new things popping up

310
00:14:28.720 --> 00:14:30.720
<v Speaker 1>all the time. What are some of those things shaping

311
00:14:30.759 --> 00:14:31.720
<v Speaker 1>the future of Yang?

312
00:14:31.960 --> 00:14:36.519
<v Speaker 2>One big trend is open source YANG models. Organizations like

313
00:14:36.559 --> 00:14:40.440
<v Speaker 2>open config are creating standardized models that anyone can use.

314
00:14:40.799 --> 00:14:42.559
<v Speaker 1>That sounds like a good way to make sure everything

315
00:14:42.600 --> 00:14:44.159
<v Speaker 1>works together, right it is.

316
00:14:44.600 --> 00:14:47.679
<v Speaker 2>And another cool trend is using AI and machine learning

317
00:14:48.080 --> 00:14:48.679
<v Speaker 2>with YANG.

318
00:14:48.879 --> 00:14:50.639
<v Speaker 1>Oh that's interesting. How does that work?

319
00:14:50.759 --> 00:14:55.080
<v Speaker 2>Well? Yang gives those AI and mL algorithms the structured

320
00:14:55.159 --> 00:14:57.799
<v Speaker 2>data they need to analyze what's happening in the network.

321
00:14:57.840 --> 00:15:00.320
<v Speaker 2>They can find patterns, make predictions, all sorts of things.

322
00:15:00.559 --> 00:15:03.799
<v Speaker 1>So we're not just automating tasks, but actually moving towards

323
00:15:03.840 --> 00:15:06.200
<v Speaker 1>networks that can learn and adapt on their own.

324
00:15:06.200 --> 00:15:09.039
<v Speaker 2>Exactly, self optimizing, self healing networks.

325
00:15:09.279 --> 00:15:11.679
<v Speaker 1>That's a pretty incredible vision of the future. But what

326
00:15:11.720 --> 00:15:14.000
<v Speaker 1>about the challenges? You know, there's always something.

327
00:15:13.759 --> 00:15:17.320
<v Speaker 2>Right, of course, one thing is the need for better tools.

328
00:15:17.799 --> 00:15:20.639
<v Speaker 2>We have some good ones, but there's always room for improvement,

329
00:15:20.840 --> 00:15:23.200
<v Speaker 2>making them easier to use, more powerful, that kind of thing.

330
00:15:23.240 --> 00:15:26.200
<v Speaker 1>It's making YANG more user friendly is important absolutely.

331
00:15:26.600 --> 00:15:30.600
<v Speaker 2>And then there's security. As we automate more, security becomes

332
00:15:30.600 --> 00:15:32.679
<v Speaker 2>even more critical. We need to make sure everything is

333
00:15:32.720 --> 00:15:34.039
<v Speaker 2>locked down tight well.

334
00:15:34.080 --> 00:15:37.080
<v Speaker 1>Security is always a top priority, especially when we're talking

335
00:15:37.080 --> 00:15:39.320
<v Speaker 1>about automating important network functions.

336
00:15:39.519 --> 00:15:40.000
<v Speaker 2>You got it.

337
00:15:40.759 --> 00:15:44.440
<v Speaker 1>This has been a truly eye opening deep dive. We've

338
00:15:44.480 --> 00:15:48.840
<v Speaker 1>gone from CLIs to YANG, explored the details, looked at

339
00:15:48.840 --> 00:15:52.080
<v Speaker 1>real world uses, and even talked about the future. It's

340
00:15:52.080 --> 00:15:54.679
<v Speaker 1>clear that YANG is changing networking in a big way.

341
00:15:54.879 --> 00:15:58.879
<v Speaker 2>I completely agree. It's giving businesses what they need to

342
00:15:58.960 --> 00:16:02.919
<v Speaker 2>build those modern and agile, intelligent networks that are ready

343
00:16:02.960 --> 00:16:03.559
<v Speaker 2>for the future.

344
00:16:03.919 --> 00:16:05.919
<v Speaker 1>And to our listener, I hope this deep dive has

345
00:16:05.919 --> 00:16:08.519
<v Speaker 1>given you a solid understanding of this whole YANG thing.

346
00:16:08.559 --> 00:16:11.039
<v Speaker 1>You came to us with a ton of questions and materials,

347
00:16:11.399 --> 00:16:13.159
<v Speaker 1>and hopefully we've been able to break.

348
00:16:13.000 --> 00:16:15.480
<v Speaker 2>It all down. We've only scratched the surface, but hopefully

349
00:16:15.559 --> 00:16:18.799
<v Speaker 2>we spark your interest and you'll want to keep exploring.

350
00:16:18.440 --> 00:16:21.519
<v Speaker 1>The world of network Programmability is a vast and ever

351
00:16:21.639 --> 00:16:26.360
<v Speaker 1>changing landscape. It is, so keep learning, keep experimenting, and

352
00:16:26.519 --> 00:16:29.080
<v Speaker 1>who knows, maybe you'll be the one building the next

353
00:16:29.200 --> 00:16:32.279
<v Speaker 1>amazing Yang powered network solution, Happy networking