WEBVTT

1
00:00:00.040 --> 00:00:03.200
<v Speaker 1>Hey everyone, and welcome back. Ready to dive into something

2
00:00:03.279 --> 00:00:04.839
<v Speaker 1>pretty huge in the tech world.

3
00:00:05.000 --> 00:00:07.679
<v Speaker 2>Absolutely, we're talking all about network programmability today.

4
00:00:07.839 --> 00:00:10.080
<v Speaker 1>Yeah, and to really get into it, we're going deep

5
00:00:10.080 --> 00:00:14.599
<v Speaker 1>on this awesome book Programming and Automating Cisco Networks. This

6
00:00:14.640 --> 00:00:17.760
<v Speaker 1>stuff is changing how networks are built, like from the

7
00:00:17.839 --> 00:00:18.399
<v Speaker 1>ground up.

8
00:00:18.480 --> 00:00:21.320
<v Speaker 2>It's a total game changer, not just a tech buzzword.

9
00:00:21.640 --> 00:00:24.559
<v Speaker 2>This is like a fundamental shift, you know, how we

10
00:00:24.600 --> 00:00:27.719
<v Speaker 2>think about network, designing them, managing them, the whole nine

11
00:00:27.760 --> 00:00:28.879
<v Speaker 2>yards exactly.

12
00:00:29.120 --> 00:00:31.440
<v Speaker 1>And no matter where you're at, whether you're a coding

13
00:00:31.480 --> 00:00:34.159
<v Speaker 1>guru or well, let's just say you've been typing commands

14
00:00:34.159 --> 00:00:35.119
<v Speaker 1>since before I was born.

15
00:00:35.200 --> 00:00:36.280
<v Speaker 2>Hopefully not that long ago.

16
00:00:36.439 --> 00:00:40.159
<v Speaker 1>Hum, but you get the idea. This deep dive is

17
00:00:40.200 --> 00:00:42.840
<v Speaker 1>for you. We're giving you the tools the knowledge to

18
00:00:42.920 --> 00:00:45.560
<v Speaker 1>navigate this whole network programmability thing.

19
00:00:45.840 --> 00:00:48.799
<v Speaker 2>And what's really cool is that it is accessible whether

20
00:00:48.840 --> 00:00:51.000
<v Speaker 2>you're just starting out or you've been in the field

21
00:00:51.000 --> 00:00:51.600
<v Speaker 2>for years.

22
00:00:51.759 --> 00:00:54.280
<v Speaker 1>Okay, so let's get into it. Why is now the

23
00:00:54.359 --> 00:00:57.000
<v Speaker 1>time for this change? What's the big push behind all

24
00:00:57.039 --> 00:00:58.840
<v Speaker 1>this network programmability stuff.

25
00:00:59.000 --> 00:01:02.600
<v Speaker 2>It's a perfect storm. Really. You've got cloud computing blowing

26
00:01:02.679 --> 00:01:07.079
<v Speaker 2>up data everywhere and businesses. They need to move faster

27
00:01:07.159 --> 00:01:11.079
<v Speaker 2>than ever. The old way like manually configuring every little thing, yeah,

28
00:01:11.319 --> 00:01:12.120
<v Speaker 2>just doesn't cut it.

29
00:01:12.439 --> 00:01:14.799
<v Speaker 1>Yeah. The book makes that super clear with that story

30
00:01:14.799 --> 00:01:16.920
<v Speaker 1>about the company, right, the one that missed out on

31
00:01:16.920 --> 00:01:19.519
<v Speaker 1>a huge EE opportunity because their network just couldn't adapt

32
00:01:19.599 --> 00:01:20.159
<v Speaker 1>fast enough.

33
00:01:20.200 --> 00:01:24.000
<v Speaker 2>Exactly. It's a wake up call in today's world. Your network,

34
00:01:24.280 --> 00:01:26.719
<v Speaker 2>it can either hold you back or launch you forward.

35
00:01:27.159 --> 00:01:30.680
<v Speaker 2>Network programmability, it's about making sure it's the second.

36
00:01:30.400 --> 00:01:33.000
<v Speaker 1>One makes sense. So how does it actually do that

37
00:01:33.079 --> 00:01:37.159
<v Speaker 1>make networks faster, more adaptable? What's the secret? Sauce?

38
00:01:37.760 --> 00:01:41.480
<v Speaker 2>Software. We're using software to automate all those tedious tasks,

39
00:01:41.599 --> 00:01:46.359
<v Speaker 2>to organize resources, even create systems that can fix themselves.

40
00:01:46.560 --> 00:01:49.400
<v Speaker 2>Remember all those times you spent troubleshooting until two am?

41
00:01:49.439 --> 00:01:50.760
<v Speaker 1>Don't remind me, right?

42
00:01:51.040 --> 00:01:54.319
<v Speaker 2>Network programmability can automate a lot of that, free you

43
00:01:54.439 --> 00:01:56.840
<v Speaker 2>up for more, shall we say, strategic thinking?

44
00:01:57.040 --> 00:01:59.319
<v Speaker 1>Okay, now you're talking my language. Less time fighting with

45
00:01:59.439 --> 00:02:03.159
<v Speaker 1>command line, more time for you know, actual thinking. So

46
00:02:03.359 --> 00:02:06.319
<v Speaker 1>automation versus programmability. The book kind of touches on this,

47
00:02:06.480 --> 00:02:08.719
<v Speaker 1>but I think it would help to dig a little deeper.

48
00:02:08.840 --> 00:02:12.520
<v Speaker 2>Totally think of it like this automation is like those microwaves,

49
00:02:12.520 --> 00:02:17.400
<v Speaker 2>you know, the popcorn button. Preset instructions works for specific things,

50
00:02:17.719 --> 00:02:21.879
<v Speaker 2>but not very flexible programmability. That's like having a full

51
00:02:21.919 --> 00:02:26.039
<v Speaker 2>on chef's kitchen. Yeah right, you call the shots, customize everything.

52
00:02:25.879 --> 00:02:30.759
<v Speaker 1>So basic microwave versus like five star restaurant level control exactly.

53
00:02:31.039 --> 00:02:34.840
<v Speaker 2>With programmability, you're not stuck with preset options. You've got

54
00:02:34.840 --> 00:02:36.439
<v Speaker 2>the power to fine tune everything.

55
00:02:36.560 --> 00:02:38.680
<v Speaker 1>That's amazing. So how does coding actually fit into all

56
00:02:38.719 --> 00:02:41.039
<v Speaker 1>of this? I'll admit it can seem kind of intimidating,

57
00:02:41.159 --> 00:02:42.080
<v Speaker 1>especially in networking.

58
00:02:42.319 --> 00:02:44.639
<v Speaker 2>I get it, but it's not as scary as it sounds.

59
00:02:44.759 --> 00:02:46.800
<v Speaker 2>A lot of the ideas are similar to what you

60
00:02:46.840 --> 00:02:49.520
<v Speaker 2>already do as a network engineer. Think about changing an

61
00:02:49.639 --> 00:02:52.759
<v Speaker 2>NTP server. Do it once, no big deal, but now

62
00:02:52.840 --> 00:02:55.680
<v Speaker 2>imagine doing that across say hundreds of devices.

63
00:02:56.000 --> 00:02:58.039
<v Speaker 1>Ugh. I think my fingers are starting to cramp up

64
00:02:58.120 --> 00:03:00.360
<v Speaker 1>just thinking about all that typing exactly.

65
00:03:00.400 --> 00:03:02.800
<v Speaker 2>That's where coding comes in. Write a script, automate that

66
00:03:02.840 --> 00:03:05.319
<v Speaker 2>whole process faster, fewer errors.

67
00:03:05.439 --> 00:03:07.439
<v Speaker 1>And the book really seems to like Python for this

68
00:03:07.560 --> 00:03:11.080
<v Speaker 1>right programming and automating Cisco networks. They're big fans for.

69
00:03:11.000 --> 00:03:14.639
<v Speaker 2>A good reason. Python is super versatile, relatively easy to learn,

70
00:03:14.719 --> 00:03:19.159
<v Speaker 2>and it's used everywhere in network programmability. What's really cool

71
00:03:19.199 --> 00:03:21.439
<v Speaker 2>is it's even used in stuff like open stack for

72
00:03:21.560 --> 00:03:25.599
<v Speaker 2>managing those cloud environments. So the skills you learn they translate.

73
00:03:25.719 --> 00:03:28.039
<v Speaker 1>Okay, so Python it is. And this isn't just some

74
00:03:28.240 --> 00:03:31.439
<v Speaker 1>like niche skill, right. It sounds like this is valuable

75
00:03:31.439 --> 00:03:34.120
<v Speaker 1>across it absolutely so for our listeners who are like

76
00:03:34.520 --> 00:03:36.840
<v Speaker 1>ready to jump into the coding pool. What are some

77
00:03:36.879 --> 00:03:41.039
<v Speaker 1>tools that can make it less you know, intimidating? Oh?

78
00:03:41.080 --> 00:03:44.400
<v Speaker 2>For sure. The book highlights a few. One that stands

79
00:03:44.400 --> 00:03:47.000
<v Speaker 2>out is pipe charm. It's like having a coding buddy

80
00:03:47.240 --> 00:03:51.240
<v Speaker 2>helps you write your code, test it, fix any bugs, autocomplete,

81
00:03:51.280 --> 00:03:54.479
<v Speaker 2>syntax highlighting. Think of it like spell check but for code.

82
00:03:54.599 --> 00:03:56.879
<v Speaker 1>Okay, so less chance of messing everything up. I can

83
00:03:56.919 --> 00:03:59.280
<v Speaker 1>get behind that. What about get and get hub? The

84
00:03:59.280 --> 00:04:00.520
<v Speaker 1>book mentions though too.

85
00:04:00.520 --> 00:04:03.400
<v Speaker 2>Those are essential, especially if you're working with a team.

86
00:04:03.560 --> 00:04:06.639
<v Speaker 2>Imagine working on a script, you make some changes, then bam,

87
00:04:06.800 --> 00:04:08.879
<v Speaker 2>you realize you need to go back to an earlier version.

88
00:04:08.960 --> 00:04:12.719
<v Speaker 1>Oh I've been there. Stringtel plus z is my best friend.

89
00:04:12.479 --> 00:04:15.879
<v Speaker 2>Right, But with get you can track every single change

90
00:04:15.919 --> 00:04:19.000
<v Speaker 2>you've made, go back to any previous version, life saver

91
00:04:19.839 --> 00:04:22.480
<v Speaker 2>and GitHub. That's where we saw your code, work with

92
00:04:22.519 --> 00:04:24.319
<v Speaker 2>other people on projects, that kind of thing.

93
00:04:24.399 --> 00:04:26.600
<v Speaker 1>So it's like a time machine and a collaboration hub

94
00:04:26.720 --> 00:04:27.240
<v Speaker 1>all in one.

95
00:04:27.399 --> 00:04:27.879
<v Speaker 2>You got it.

96
00:04:28.120 --> 00:04:32.360
<v Speaker 1>Okay, So we've got the why behind network programmability. We've

97
00:04:32.360 --> 00:04:36.560
<v Speaker 1>talked about automation versus programmability. We've even dipped our toes

98
00:04:36.600 --> 00:04:40.360
<v Speaker 1>into the coding world with Python, pie Charm, the whole shebang.

99
00:04:40.839 --> 00:04:43.399
<v Speaker 1>What I'm really curious about is Cisco. They're, you know,

100
00:04:43.439 --> 00:04:46.560
<v Speaker 1>the hardware giant. How are they embracing this whole software

101
00:04:46.600 --> 00:04:48.600
<v Speaker 1>driven thing? What are they doing to keep up?

102
00:04:48.759 --> 00:04:51.360
<v Speaker 2>That's the question, right And the book dives into this

103
00:04:51.439 --> 00:04:54.800
<v Speaker 2>with the Nexus nine thousand series, prime example of Cisco

104
00:04:55.000 --> 00:04:57.480
<v Speaker 2>bridging that gap between hardware and software.

105
00:04:57.560 --> 00:05:00.000
<v Speaker 1>Okay, so spill the tea on the Nexus nine thousand.

106
00:05:00.319 --> 00:05:02.959
<v Speaker 1>What makes them so special for network programmability.

107
00:05:03.000 --> 00:05:06.439
<v Speaker 2>It's all in the architecture really. See, in the past,

108
00:05:06.439 --> 00:05:10.240
<v Speaker 2>network devices were like those black boxes, right, tough to

109
00:05:10.279 --> 00:05:13.160
<v Speaker 2>work with, hard to automate. The next is nine thousand.

110
00:05:13.279 --> 00:05:15.079
<v Speaker 2>It changes all that. It runs on Linux.

111
00:05:15.199 --> 00:05:18.920
<v Speaker 1>Wait, hold up, Linux on a network switch that's like,

112
00:05:19.720 --> 00:05:21.920
<v Speaker 1>I don't know, teaching my dog to do my taxes

113
00:05:22.000 --> 00:05:24.000
<v Speaker 1>or something. It just sounds wrong, huh.

114
00:05:24.079 --> 00:05:27.319
<v Speaker 2>I know, right. It seems weird at first, but it's

115
00:05:27.439 --> 00:05:31.079
<v Speaker 2>huge because now you can use all those familiar Linux

116
00:05:31.120 --> 00:05:34.560
<v Speaker 2>tools languages like Python to work directly with the switch.

117
00:05:34.920 --> 00:05:36.319
<v Speaker 2>No more clunky workarounds.

118
00:05:36.600 --> 00:05:39.759
<v Speaker 1>So we're talking about really merging networking and software development,

119
00:05:39.839 --> 00:05:42.199
<v Speaker 1>like they're actually on speaking terms now exactly.

120
00:05:42.439 --> 00:05:45.519
<v Speaker 2>And it gets even cooler. The Nexus nine thousand supports

121
00:05:45.519 --> 00:05:47.160
<v Speaker 2>containers too, call it guest shell.

122
00:05:47.279 --> 00:05:50.680
<v Speaker 1>Guest shell sounds kind of friendly for something so technical.

123
00:05:50.439 --> 00:05:53.720
<v Speaker 2>Right, but it's powerful stuff. Imagine running apps directly on

124
00:05:53.759 --> 00:05:56.240
<v Speaker 2>the switch itself, no need for a separate server. It's

125
00:05:56.279 --> 00:05:56.839
<v Speaker 2>all right there.

126
00:05:56.920 --> 00:05:59.120
<v Speaker 1>Okay, that's got to be a game changer for performance.

127
00:05:59.160 --> 00:06:01.160
<v Speaker 1>But what kind of apps are we talking about here?

128
00:06:01.279 --> 00:06:05.040
<v Speaker 2>I think network monitoring, security analysis, even custom stuff you

129
00:06:05.120 --> 00:06:08.439
<v Speaker 2>name it. Running these directly on the switch, it means

130
00:06:08.439 --> 00:06:10.639
<v Speaker 2>things happen faster, smoother, more efficiently.

131
00:06:10.879 --> 00:06:13.160
<v Speaker 1>So it's like having a mini data center built right

132
00:06:13.199 --> 00:06:14.240
<v Speaker 1>into the switch itself.

133
00:06:14.279 --> 00:06:16.519
<v Speaker 2>You've got it and the cherry on top. Cisco's got

134
00:06:16.560 --> 00:06:19.680
<v Speaker 2>this thing called the devnet sandbox. It's a virtual environment

135
00:06:19.680 --> 00:06:21.079
<v Speaker 2>where you can actually test all this out.

136
00:06:21.240 --> 00:06:23.800
<v Speaker 1>Oh nice, so our listeners they can actually get hands

137
00:06:23.800 --> 00:06:27.439
<v Speaker 1>on without the risk of blowing up their entire companies network.

138
00:06:27.560 --> 00:06:31.079
<v Speaker 2>Exactly, safe space to experiment, learn the ropes, really get

139
00:06:31.120 --> 00:06:33.439
<v Speaker 2>a feel for what network programmability can do.

140
00:06:33.680 --> 00:06:36.199
<v Speaker 1>Love it. But we've been talking a lot about like

141
00:06:36.800 --> 00:06:40.639
<v Speaker 1>data centers, these high end switches. What about everyone else?

142
00:06:40.720 --> 00:06:45.000
<v Speaker 1>Does this apply to, say, campus networks ones?

143
00:06:45.160 --> 00:06:47.720
<v Speaker 2>Absolutely? In fact, you could argue that it's even more

144
00:06:47.720 --> 00:06:51.360
<v Speaker 2>impactful in those environments. Yeah, campus networks they can be massive, right,

145
00:06:51.600 --> 00:06:55.399
<v Speaker 2>hundreds even thousands of devices. That's where Cisco's apic EM

146
00:06:55.439 --> 00:06:55.759
<v Speaker 2>comes in.

147
00:06:55.879 --> 00:07:00.920
<v Speaker 1>Apic EM as in Application Policy, Infrastructure, Controller and Prize Module.

148
00:07:01.199 --> 00:07:01.680
<v Speaker 2>You got it.

149
00:07:01.759 --> 00:07:03.399
<v Speaker 1>Okay, that's a mouthful.

150
00:07:03.160 --> 00:07:06.560
<v Speaker 2>I hear you. But the name's a mouthful, The functionality's

151
00:07:06.600 --> 00:07:09.399
<v Speaker 2>even better, trust me. Remember that example in the book

152
00:07:09.879 --> 00:07:15.519
<v Speaker 2>about configuring QoS quality of service on a really large network, Yeah.

153
00:07:15.279 --> 00:07:17.879
<v Speaker 1>The one where doing it manually would take like a

154
00:07:17.879 --> 00:07:19.360
<v Speaker 1>whole team of engineers a week.

155
00:07:19.480 --> 00:07:22.759
<v Speaker 2>Exactly, with a bic EM, you can automate that entire thing,

156
00:07:23.120 --> 00:07:26.120
<v Speaker 2>set your QoS policies across the whole network just a

157
00:07:26.120 --> 00:07:27.439
<v Speaker 2>few clicks, Boom done.

158
00:07:27.519 --> 00:07:29.519
<v Speaker 1>I bet that saves a ton of headaches too. So

159
00:07:29.560 --> 00:07:31.920
<v Speaker 1>how does it work? What's the magic behind epic em.

160
00:07:32.040 --> 00:07:35.680
<v Speaker 2>It's all about centralized control. Epic EM. It's like the

161
00:07:35.680 --> 00:07:38.560
<v Speaker 2>brain of your network. It sees everything, all your device is,

162
00:07:38.639 --> 00:07:40.680
<v Speaker 2>all your settings all in one place.

163
00:07:40.879 --> 00:07:43.279
<v Speaker 1>So no more logging into each device one by one

164
00:07:43.360 --> 00:07:45.360
<v Speaker 1>like it's the Stone Age or something exactly.

165
00:07:45.680 --> 00:07:48.680
<v Speaker 2>And get this. Apic em is built on open APIs

166
00:07:49.480 --> 00:07:51.959
<v Speaker 2>just like the NEXTUS nine thousand. It plays well with others,

167
00:07:52.399 --> 00:07:54.519
<v Speaker 2>third party tools, systems, you name it.

168
00:07:54.639 --> 00:07:56.839
<v Speaker 1>Okay, so we're talking about a flexible system here, not

169
00:07:57.000 --> 00:08:00.160
<v Speaker 1>just locked into Cisco Land. But what about the wham.

170
00:08:00.360 --> 00:08:03.680
<v Speaker 1>We've covered data centers, campus networks, but the land seems

171
00:08:03.720 --> 00:08:05.959
<v Speaker 1>like could be even trickier with the old school ways.

172
00:08:06.319 --> 00:08:10.240
<v Speaker 2>You're not wrong. Wands can be a real pain, especially

173
00:08:10.279 --> 00:08:13.639
<v Speaker 2>now with cloud apps everywhere. Everyone needs their connection to

174
00:08:13.680 --> 00:08:17.160
<v Speaker 2>be rock solid. That's where Cisco's intelligent one comes in.

175
00:08:17.600 --> 00:08:21.600
<v Speaker 1>I won for sure, I wan another acronym. Is starting

176
00:08:21.639 --> 00:08:23.839
<v Speaker 1>to think these Cisco folks just love them. But what

177
00:08:23.920 --> 00:08:26.000
<v Speaker 1>makes it so intelligent? Fill me in?

178
00:08:26.079 --> 00:08:30.519
<v Speaker 2>Okay, imagine this. You're driving right and you've got different

179
00:08:30.560 --> 00:08:33.240
<v Speaker 2>routes to your destination. Do you always take the exact

180
00:08:33.279 --> 00:08:34.000
<v Speaker 2>same one.

181
00:08:34.200 --> 00:08:38.080
<v Speaker 1>Not if I can help it. Traffic accidents got to

182
00:08:38.120 --> 00:08:39.440
<v Speaker 1>mix it up sometimes exactly.

183
00:08:39.480 --> 00:08:41.919
<v Speaker 2>Sometimes you want the fastest routes, sometimes the most scenic.

184
00:08:42.000 --> 00:08:44.799
<v Speaker 2>Sometimes you just want to avoid the tolls. Right, depends

185
00:08:44.799 --> 00:08:45.519
<v Speaker 2>on your priorities.

186
00:08:45.519 --> 00:08:48.440
<v Speaker 1>Okay, so is I like the GPS for your network

187
00:08:48.440 --> 00:08:49.200
<v Speaker 1>traffic or what.

188
00:08:49.279 --> 00:08:51.519
<v Speaker 2>You got it? It's always checking out all the available

189
00:08:51.559 --> 00:08:54.720
<v Speaker 2>WAN links in PLS, Internet, you name it, and it

190
00:08:54.799 --> 00:08:57.919
<v Speaker 2>routes traffic based on what's needed. Maybe an app needs

191
00:08:57.960 --> 00:09:01.120
<v Speaker 2>top speed, maybe you need to keep cast down. I

192
00:09:01.240 --> 00:09:02.080
<v Speaker 2>one figures it out.

193
00:09:02.120 --> 00:09:04.840
<v Speaker 1>So let me get this straight. I WAN can prioritize

194
00:09:04.840 --> 00:09:07.639
<v Speaker 1>traffic for say, like a big video conference, make sure

195
00:09:07.679 --> 00:09:10.080
<v Speaker 1>that goes smoothly, even if someone's downloading a massive file

196
00:09:10.120 --> 00:09:10.840
<v Speaker 1>at the same time.

197
00:09:11.120 --> 00:09:13.960
<v Speaker 2>Precisely, it's about making the most of what you got,

198
00:09:14.159 --> 00:09:18.039
<v Speaker 2>making sure everyone have the best possible experience, even when

199
00:09:18.080 --> 00:09:18.919
<v Speaker 2>things get crazy.

200
00:09:19.000 --> 00:09:23.200
<v Speaker 1>Okay, that's pretty slick. So we've got apic M automating

201
00:09:23.200 --> 00:09:25.840
<v Speaker 1>the campus, i WAN acting like a traffic cop for

202
00:09:25.879 --> 00:09:28.320
<v Speaker 1>the one. What I'm seeing is this isn't just about

203
00:09:28.360 --> 00:09:31.840
<v Speaker 1>making our lives easier as network engineers. It's about letting

204
00:09:31.960 --> 00:09:37.000
<v Speaker 1>businesses actually do more be more responsive in this whole digital.

205
00:09:36.639 --> 00:09:39.240
<v Speaker 2>World one hundred percent. And it's bigger than just Cisco too.

206
00:09:39.600 --> 00:09:43.480
<v Speaker 2>There's this whole world of open source tools, technologies, all

207
00:09:43.519 --> 00:09:44.679
<v Speaker 2>built on these same principles.

208
00:09:44.799 --> 00:09:47.279
<v Speaker 1>Oh yeah, that's right. We've been Cisco heavy so far,

209
00:09:47.440 --> 00:09:50.240
<v Speaker 1>but we can't ignore the open source world for sure.

210
00:09:50.440 --> 00:09:53.360
<v Speaker 2>And this is where things get really interesting. Open standards,

211
00:09:53.440 --> 00:09:57.720
<v Speaker 2>open source tools. They're making network programmability accessible to everyone,

212
00:09:57.799 --> 00:09:58.799
<v Speaker 2>not just the big players.

213
00:09:58.879 --> 00:10:01.519
<v Speaker 1>So you're telling me, and if you're not a Cisco shop,

214
00:10:01.679 --> 00:10:03.080
<v Speaker 1>you can still get in on this.

215
00:10:03.320 --> 00:10:05.879
<v Speaker 2>Absolutely. We've talked a lot about what Cisco's doing, which

216
00:10:05.919 --> 00:10:09.360
<v Speaker 2>is huge, but network programmability it's bigger than any one company.

217
00:10:09.799 --> 00:10:10.480
<v Speaker 2>It's a movement.

218
00:10:10.879 --> 00:10:14.279
<v Speaker 1>I love it. So let's talk open source. Then. What

219
00:10:14.399 --> 00:10:17.360
<v Speaker 1>are some of the big names the tools our listeners

220
00:10:17.399 --> 00:10:18.360
<v Speaker 1>should know about.

221
00:10:18.559 --> 00:10:21.080
<v Speaker 2>Okay, so we're ditching the big brand names from a minute,

222
00:10:21.120 --> 00:10:24.559
<v Speaker 2>heading into the open source world. What's out there? Give

223
00:10:24.639 --> 00:10:25.279
<v Speaker 2>us the highlights.

224
00:10:25.360 --> 00:10:28.519
<v Speaker 1>One name you'll hear everywhere is Yang And no it's

225
00:10:28.519 --> 00:10:29.679
<v Speaker 1>not some hip new band.

226
00:10:29.960 --> 00:10:31.679
<v Speaker 2>Oh that would be pretty cool, right.

227
00:10:32.000 --> 00:10:35.759
<v Speaker 1>But Yang it stands for yet another next generation and

228
00:10:35.840 --> 00:10:39.639
<v Speaker 1>it's all about creating one language for network devices to speak.

229
00:10:40.120 --> 00:10:44.360
<v Speaker 2>Yet another next generation. Someone was having fun with that one. Yeah,

230
00:10:44.360 --> 00:10:46.799
<v Speaker 2>but okay, why is a common language so important. We're

231
00:10:46.840 --> 00:10:49.399
<v Speaker 2>talking about networks here, not the un Think about it.

232
00:10:49.440 --> 00:10:52.600
<v Speaker 1>You've got all these different companies, right, Cisco, Juniper, whoever.

233
00:10:52.799 --> 00:10:55.480
<v Speaker 1>Each one's got their own way of doing things, configuring devices,

234
00:10:55.639 --> 00:10:58.240
<v Speaker 1>managing them. It's like a tower of Babbel Yang. It's

235
00:10:58.240 --> 00:10:59.440
<v Speaker 1>like the universal translator.

236
00:10:59.559 --> 00:11:01.720
<v Speaker 2>So I could use the same tools, same scripts to

237
00:11:01.799 --> 00:11:05.919
<v Speaker 2>manage like a Cisco switch and a Juniper Rider. No problem,

238
00:11:05.960 --> 00:11:06.559
<v Speaker 2>you got it.

239
00:11:06.559 --> 00:11:09.039
<v Speaker 1>It's about breaking down those walls, making it easier to

240
00:11:09.080 --> 00:11:12.000
<v Speaker 1>manage a network that's got a little bit of everything. Okay,

241
00:11:12.039 --> 00:11:15.120
<v Speaker 1>that makes sense. Let's headache for everyone. But Yang's just

242
00:11:15.159 --> 00:11:16.440
<v Speaker 1>part of the picture, right Right.

243
00:11:16.840 --> 00:11:19.039
<v Speaker 2>You've also got net conf, which is how we actually

244
00:11:19.080 --> 00:11:21.519
<v Speaker 2>talk to those devices using the Yang model.

245
00:11:21.639 --> 00:11:24.519
<v Speaker 1>So Yang's like the blueprint net con and f's the

246
00:11:24.679 --> 00:11:26.600
<v Speaker 1>construction crew making it happen.

247
00:11:26.840 --> 00:11:28.360
<v Speaker 2>Perfect analogy, nailed it.

248
00:11:28.639 --> 00:11:32.519
<v Speaker 1>Okay, what about actual tools? Anything open source that uses

249
00:11:32.559 --> 00:11:33.080
<v Speaker 1>this stuff?

250
00:11:33.159 --> 00:11:37.399
<v Speaker 2>Oh yeah, tons. One example is CONFD, developed by this

251
00:11:37.480 --> 00:11:41.000
<v Speaker 2>company tailhaf Systems before Cisco scooped them up.

252
00:11:41.080 --> 00:11:44.440
<v Speaker 1>Wait, Cisco bought a company making open source stuff interesting?

253
00:11:44.559 --> 00:11:47.360
<v Speaker 2>It is shows you how important this whole movement is becoming.

254
00:11:47.399 --> 00:11:49.440
<v Speaker 2>Even the big guys are paying attention for sure.

255
00:11:50.000 --> 00:11:53.440
<v Speaker 1>So back to CONFD. What is it? What's the deal?

256
00:11:53.679 --> 00:11:57.120
<v Speaker 2>It's a platform let you build your own network management apps,

257
00:11:57.399 --> 00:12:00.039
<v Speaker 2>custom made for what you need. Provides all the p

258
00:12:00.360 --> 00:12:01.559
<v Speaker 2>you just put them together like.

259
00:12:01.519 --> 00:12:03.600
<v Speaker 1>A Lego set for a network engineers.

260
00:12:03.639 --> 00:12:05.440
<v Speaker 2>Basically, you get to be creative.

261
00:12:05.559 --> 00:12:06.039
<v Speaker 1>I like it.

262
00:12:06.320 --> 00:12:06.519
<v Speaker 2>Now.

263
00:12:06.600 --> 00:12:09.960
<v Speaker 1>You mentioned another one earlier, Open Daylight. What's that all about?

264
00:12:10.039 --> 00:12:12.320
<v Speaker 2>Oh, that's a big one. Open Daylight. It's a whole

265
00:12:12.320 --> 00:12:16.000
<v Speaker 2>operating system for your network, open source, totally modular.

266
00:12:16.279 --> 00:12:18.279
<v Speaker 1>So if con off D's like the Lego set, open

267
00:12:18.320 --> 00:12:20.840
<v Speaker 1>Daylight is more like, I don't know, building a whole house.

268
00:12:20.679 --> 00:12:24.200
<v Speaker 2>From scratch exactly. It's a huge community effort, lots of

269
00:12:24.200 --> 00:12:26.799
<v Speaker 2>people working on it, adding new features, making it better

270
00:12:26.840 --> 00:12:27.360
<v Speaker 2>all the time.

271
00:12:27.559 --> 00:12:29.759
<v Speaker 1>That's awesome, real community spirit right there.

272
00:12:30.200 --> 00:12:34.320
<v Speaker 2>Okay, last one I got asked about ansable. It's everywhere

273
00:12:34.399 --> 00:12:37.000
<v Speaker 2>in the automation world. Does it have a place in

274
00:12:37.159 --> 00:12:38.480
<v Speaker 2>network programmability?

275
00:12:38.480 --> 00:12:42.759
<v Speaker 1>To one hundred percent? Ansable is amazing for automating all

276
00:12:42.759 --> 00:12:45.159
<v Speaker 1>sorts of it stuff, including networks, and it's.

277
00:12:45.120 --> 00:12:48.000
<v Speaker 2>Known for being pretty user friendly. Right even if you're

278
00:12:48.000 --> 00:12:49.320
<v Speaker 2>not a coding list totally.

279
00:12:49.480 --> 00:12:52.759
<v Speaker 1>You write your automation tasks in this really simple language,

280
00:12:52.799 --> 00:12:54.360
<v Speaker 1>easy to read, easy to understand.

281
00:12:54.440 --> 00:12:57.039
<v Speaker 2>That's great for people just starting out, definitely less intimidating.

282
00:12:57.200 --> 00:12:59.919
<v Speaker 2>So just to recap, we've got conf d for CUSS,

283
00:13:00.080 --> 00:13:03.639
<v Speaker 2>some tools Open Daylight for building network operating systems from

284
00:13:03.639 --> 00:13:07.600
<v Speaker 2>the ground up, and answable for like everyday automation task

285
00:13:07.679 --> 00:13:08.080
<v Speaker 2>is made.

286
00:13:07.960 --> 00:13:10.639
<v Speaker 1>Easy exactly, And I think that's a really important point.

287
00:13:10.720 --> 00:13:13.399
<v Speaker 1>Network programmability. It's not a one size fits all thing.

288
00:13:13.440 --> 00:13:16.240
<v Speaker 1>You've got choices. The key is figuring out what works

289
00:13:16.240 --> 00:13:19.360
<v Speaker 1>best for you for your network. Couldn't agree more. It's

290
00:13:19.360 --> 00:13:21.679
<v Speaker 1>easy to get overwhelmed by all the options, but like

291
00:13:21.720 --> 00:13:23.919
<v Speaker 1>you said, it's about finding the right tool for the

292
00:13:24.000 --> 00:13:24.919
<v Speaker 1>job it is.

293
00:13:25.039 --> 00:13:27.840
<v Speaker 2>Think of it like I don't know, learning a new language.

294
00:13:27.840 --> 00:13:30.159
<v Speaker 2>You don't need to know every word, every grammar rule. Yeah,

295
00:13:30.200 --> 00:13:32.320
<v Speaker 2>you just got to start talk and start using it.

296
00:13:32.480 --> 00:13:34.919
<v Speaker 1>I love that analogy, And on that note, I think

297
00:13:34.919 --> 00:13:37.679
<v Speaker 1>it's time to wrap up this deep dive. We've covered

298
00:13:37.720 --> 00:13:41.519
<v Speaker 1>a ton the why, the how, the tools, the whole

299
00:13:41.639 --> 00:13:44.679
<v Speaker 1>nine yards. But before we go, any final thoughts for

300
00:13:44.759 --> 00:13:46.240
<v Speaker 1>our listeners, just this.

301
00:13:46.840 --> 00:13:50.639
<v Speaker 2>Network programmability it's not going away. This isn't just a trend.

302
00:13:50.799 --> 00:13:52.559
<v Speaker 2>It's the future, plain and simple.

303
00:13:52.679 --> 00:13:54.600
<v Speaker 1>So whether you're all in on the code or just

304
00:13:54.639 --> 00:13:56.919
<v Speaker 1>dipping your toes in, now's the time to get on board.

305
00:13:56.960 --> 00:14:00.159
<v Speaker 2>Absolutely, the network's changing and we get to be right

306
00:14:00.200 --> 00:14:02.320
<v Speaker 2>there shaping it, making it better.

307
00:14:02.399 --> 00:14:04.600
<v Speaker 1>How cool is that could have said it better myself.

308
00:14:05.080 --> 00:14:08.240
<v Speaker 1>That's a wrap on this deep dive into network programmability.

309
00:14:08.399 --> 00:14:10.840
<v Speaker 1>We've got more exciting stuff coming up, so stay tuned

310
00:14:11.440 --> 00:14:13.679
<v Speaker 1>until then, Happy networking everyone,