1
00:00:04,240 --> 00:00:07,240
Speaker 1: Welcome to tech Stuff, a production of I Heart Radios,

2
00:00:07,320 --> 00:00:14,280
Speaker 1: How Stuff Works. Hey there, and welcome to this special

3
00:00:14,520 --> 00:00:18,680
Speaker 1: Bonus sponsored episode of tech Stuff. I'm Jonathan Strickland. I'm

4
00:00:18,680 --> 00:00:20,760
Speaker 1: an executive producer with How Stuff Works and I Heart

5
00:00:20,840 --> 00:00:23,479
Speaker 1: Radio and I love all things tech and back in

6
00:00:23,640 --> 00:00:28,240
Speaker 1: July two thousand nineteen, IBM completed it's acquisition of the

7
00:00:28,280 --> 00:00:32,560
Speaker 1: company red Hat, famed for its work in open source software.

8
00:00:32,840 --> 00:00:36,200
Speaker 1: The company's invited me out to red Hat headquarters, which

9
00:00:36,880 --> 00:00:40,120
Speaker 1: does in fact have a big red hat on it,

10
00:00:40,520 --> 00:00:43,160
Speaker 1: to talk about why the company has made this move,

11
00:00:43,479 --> 00:00:46,600
Speaker 1: how they plan to work together, and ultimately what does

12
00:00:46,640 --> 00:00:50,560
Speaker 1: this mean for all of us? And so in this episode,

13
00:00:50,560 --> 00:00:52,960
Speaker 1: you're going to hear sections of an interview I did

14
00:00:53,000 --> 00:00:56,640
Speaker 1: with IBMS Steve Robinson and red hats a Chesh Badani,

15
00:00:57,000 --> 00:00:59,160
Speaker 1: and I'll be popping in and out to give a

16
00:00:59,200 --> 00:01:02,360
Speaker 1: bit more content text and explanation. But first I want

17
00:01:02,400 --> 00:01:05,440
Speaker 1: to set the stage a bit. Now. We're mainly going

18
00:01:05,480 --> 00:01:09,520
Speaker 1: to talk about cloud computing and open source software in

19
00:01:09,560 --> 00:01:12,479
Speaker 1: this conversation, and the reason that this is a big

20
00:01:12,520 --> 00:01:15,560
Speaker 1: deal is that more companies are putting more of their

21
00:01:15,600 --> 00:01:18,240
Speaker 1: operations on the cloud, and there are a lot of

22
00:01:18,280 --> 00:01:21,000
Speaker 1: different reasons to do this. One is to make sure

23
00:01:21,160 --> 00:01:25,800
Speaker 1: that the services they provide are available whenever and wherever

24
00:01:25,959 --> 00:01:28,520
Speaker 1: the end user needs them, whether the end user is

25
00:01:28,520 --> 00:01:31,360
Speaker 1: someone else in the company, a different company, or a

26
00:01:31,360 --> 00:01:36,319
Speaker 1: consumer like you or me. Another reason is to maximize resources,

27
00:01:36,360 --> 00:01:40,280
Speaker 1: and there are tons of other reasons besides those that

28
00:01:40,400 --> 00:01:44,440
Speaker 1: companies do this. What about the average user? You know,

29
00:01:44,480 --> 00:01:48,080
Speaker 1: I don't run a global company with worldwide service, so

30
00:01:48,280 --> 00:01:51,320
Speaker 1: why do I care about all this? Well, for me,

31
00:01:51,680 --> 00:01:55,440
Speaker 1: it's about the utility and availability of the apps I

32
00:01:55,600 --> 00:01:58,360
Speaker 1: run on all these different devices, whether it's a computer

33
00:01:58,640 --> 00:02:01,720
Speaker 1: or a mobile phone, a tablet, whatever it might be.

34
00:02:02,240 --> 00:02:05,520
Speaker 1: More of those apps are tapping into lots of different

35
00:02:05,560 --> 00:02:09,480
Speaker 1: aspects that a company is involved with. So a bank,

36
00:02:09,600 --> 00:02:11,920
Speaker 1: for example, could have an app that allows you to

37
00:02:11,960 --> 00:02:14,960
Speaker 1: access your bank account. You can make transfers, you can

38
00:02:15,000 --> 00:02:17,639
Speaker 1: pay bills, you can check your reward status on any

39
00:02:17,680 --> 00:02:19,360
Speaker 1: credit cards you might have, You might be able to

40
00:02:19,400 --> 00:02:22,760
Speaker 1: apply for loans, and more. To the end user, it

41
00:02:22,840 --> 00:02:25,239
Speaker 1: might seem like all that stuff just sort of lives

42
00:02:25,560 --> 00:02:29,120
Speaker 1: in the brick and mortar building that the bank we

43
00:02:29,280 --> 00:02:32,320
Speaker 1: use happens to be located in, But in reality, those

44
00:02:32,320 --> 00:02:36,240
Speaker 1: services might be spread across numerous computer systems all over

45
00:02:36,280 --> 00:02:39,040
Speaker 1: the place. Some of them might be on premises at

46
00:02:39,040 --> 00:02:41,880
Speaker 1: the bank itself, some might be in a privately managed

47
00:02:41,960 --> 00:02:45,080
Speaker 1: data center off site. Some might depend upon large cloud

48
00:02:45,160 --> 00:02:49,000
Speaker 1: computing services run by big companies. So there's a whole

49
00:02:49,080 --> 00:02:52,600
Speaker 1: variety out there now. As an end user, I just

50
00:02:52,680 --> 00:02:56,560
Speaker 1: expect that stuff to work. I expect all those services

51
00:02:56,600 --> 00:03:00,680
Speaker 1: to be integrated into the app seamlessly, and it's frustrating

52
00:03:00,680 --> 00:03:03,080
Speaker 1: when that's not the case, right like when you try

53
00:03:03,120 --> 00:03:06,040
Speaker 1: to do something and either there's a long wait time

54
00:03:06,240 --> 00:03:08,680
Speaker 1: or it doesn't work the way you expected. But the

55
00:03:08,720 --> 00:03:11,720
Speaker 1: cloud computer landscape it's a complicated one for reasons that

56
00:03:11,760 --> 00:03:13,960
Speaker 1: we're going to get into in the discussions I had

57
00:03:13,960 --> 00:03:18,359
Speaker 1: with Steve in a chef. So making this happen all

58
00:03:18,400 --> 00:03:22,320
Speaker 1: the stuff working together isn't as easy as just inserting

59
00:03:22,360 --> 00:03:26,840
Speaker 1: a few links between services. So let's get started. I

60
00:03:26,919 --> 00:03:30,400
Speaker 1: began with what seems like a simple question but is

61
00:03:30,680 --> 00:03:36,360
Speaker 1: actually fairly complicated. So I'm very pleased that I get

62
00:03:36,400 --> 00:03:40,400
Speaker 1: to speak to two experts on this subject because about

63
00:03:40,440 --> 00:03:44,080
Speaker 1: a decade ago I wrote more than a dozen articles

64
00:03:44,160 --> 00:03:49,400
Speaker 1: all about the concept of cloud computing. Back then, cloud computing,

65
00:03:49,440 --> 00:03:52,720
Speaker 1: at least for the mainstream, was just creeping into the

66
00:03:52,760 --> 00:03:55,960
Speaker 1: public consciousness and there was a lot of confusion about it.

67
00:03:56,520 --> 00:03:59,800
Speaker 1: And I think over the years everyone has a better

68
00:03:59,800 --> 00:04:02,080
Speaker 1: and standing of what cloud computing is. But the problem

69
00:04:02,120 --> 00:04:05,360
Speaker 1: is everyone has a different understanding of what cloud computing is.

70
00:04:05,680 --> 00:04:09,240
Speaker 1: So can we talk about the definition of cloud computing

71
00:04:09,240 --> 00:04:13,120
Speaker 1: and how that has actually evolved over time? Be happy

72
00:04:13,160 --> 00:04:15,400
Speaker 1: to and I think you you again, you hit the

73
00:04:15,440 --> 00:04:18,360
Speaker 1: nail on the head with regards to I think it's

74
00:04:18,360 --> 00:04:22,000
Speaker 1: one of the most amorphous definitions out there. You ask anybody,

75
00:04:22,080 --> 00:04:24,480
Speaker 1: I think they've got a different view. And I think

76
00:04:24,480 --> 00:04:27,240
Speaker 1: around a period of time, at least in an IBM's view,

77
00:04:27,440 --> 00:04:31,160
Speaker 1: is is that it's one that's continually redefining, and it's

78
00:04:31,200 --> 00:04:34,600
Speaker 1: probably in a phase right now where it's being redefined

79
00:04:34,760 --> 00:04:38,000
Speaker 1: as well. I think in most cases people originally assumed

80
00:04:38,120 --> 00:04:42,160
Speaker 1: an associated cloud with the large public clouds, you know,

81
00:04:42,279 --> 00:04:47,159
Speaker 1: the multi tenant hyper scalers and UH And it reminds

82
00:04:47,160 --> 00:04:49,800
Speaker 1: me a little bit like the early days of the Internet.

83
00:04:49,880 --> 00:04:52,120
Speaker 1: You know, if you if you go back to UH

84
00:04:52,400 --> 00:04:55,680
Speaker 1: the Internet, you had extra net, you had internet, you

85
00:04:55,720 --> 00:05:00,240
Speaker 1: had public Internet, you had private Internet, and before long

86
00:05:00,320 --> 00:05:02,120
Speaker 1: you started to see most of the vendors start to

87
00:05:02,240 --> 00:05:05,080
Speaker 1: rally around a small set of standards T C P

88
00:05:05,200 --> 00:05:07,880
Speaker 1: I P H, T M L, and before long it

89
00:05:08,000 --> 00:05:10,800
Speaker 1: just became the Internet. You know, you would serve up

90
00:05:10,800 --> 00:05:12,800
Speaker 1: a U R L and you really didn't care where

91
00:05:12,800 --> 00:05:16,120
Speaker 1: the server was that was serving up the content behind it.

92
00:05:16,240 --> 00:05:17,919
Speaker 1: It could be in your data center, could be on

93
00:05:18,000 --> 00:05:21,160
Speaker 1: go Daddy, could be wherever that uh, it could be

94
00:05:21,200 --> 00:05:24,159
Speaker 1: in one country versus another. It just became the Internet.

95
00:05:24,400 --> 00:05:26,120
Speaker 1: And I think that the cloud we're kind of ad

96
00:05:26,160 --> 00:05:28,240
Speaker 1: that position to. I think the cloud is going to

97
00:05:28,960 --> 00:05:31,719
Speaker 1: start to expand to be almost anywhere that I've got

98
00:05:31,760 --> 00:05:35,359
Speaker 1: compute and data capabilities. And we've seen this this whole

99
00:05:35,440 --> 00:05:39,800
Speaker 1: rally around a certain set of standards really driving that

100
00:05:39,920 --> 00:05:42,760
Speaker 1: and driving that at a speed that's just unbelievable. Right now,

101
00:05:43,160 --> 00:05:45,440
Speaker 1: I think, you know, the adoption of lenox, I think

102
00:05:45,480 --> 00:05:49,960
Speaker 1: the whole history of containers and the maturity of containers,

103
00:05:50,000 --> 00:05:52,760
Speaker 1: which are you know, kind of you know, finer grained

104
00:05:52,839 --> 00:05:56,040
Speaker 1: virtualization that allows me to to have code and move

105
00:05:56,080 --> 00:05:58,880
Speaker 1: it around and pack the middlewhere into it, etcetera. And

106
00:05:58,920 --> 00:06:01,360
Speaker 1: then finally kubernet ease that gives me the ability to

107
00:06:01,480 --> 00:06:04,880
Speaker 1: orchestrate and manage those containers. Are kind of that becoming

108
00:06:04,880 --> 00:06:07,640
Speaker 1: that Lingua franco. You know, I think we all of

109
00:06:07,680 --> 00:06:11,760
Speaker 1: the major vendors are now kind of embracing those three standards.

110
00:06:12,040 --> 00:06:15,159
Speaker 1: I think there's probably over forty to fifty different distros

111
00:06:15,200 --> 00:06:18,279
Speaker 1: of coube today and that's now I think kind of

112
00:06:18,279 --> 00:06:20,480
Speaker 1: turning it into cloud. I Can I do cloud in

113
00:06:20,480 --> 00:06:22,640
Speaker 1: my data center? Sure, there's a lot of things I

114
00:06:22,680 --> 00:06:25,080
Speaker 1: can do. I can run containers, I can run Kubernetes,

115
00:06:25,120 --> 00:06:27,279
Speaker 1: I can build a p I S, I can have

116
00:06:27,360 --> 00:06:29,360
Speaker 1: always on, I can do a lot of cloud native

117
00:06:29,360 --> 00:06:32,320
Speaker 1: concepts right in the data center. Can I do a

118
00:06:32,400 --> 00:06:35,440
Speaker 1: dedicated cloud that may be set up and assigned to

119
00:06:35,680 --> 00:06:38,640
Speaker 1: a single client or a single customer. Yep. You now

120
00:06:38,680 --> 00:06:40,640
Speaker 1: have been able to to do cloud concepts and put

121
00:06:40,640 --> 00:06:43,320
Speaker 1: a single customer boundary around it as well. And then

122
00:06:43,360 --> 00:06:45,120
Speaker 1: you've got the hyper scale ers that can do that

123
00:06:45,200 --> 00:06:48,039
Speaker 1: for a wide range and never know where. You know,

124
00:06:48,080 --> 00:06:51,560
Speaker 1: my my my machine, maybe in one data center one day,

125
00:06:51,560 --> 00:06:53,640
Speaker 1: in one data center the next day. So I think

126
00:06:53,760 --> 00:06:57,479
Speaker 1: all of this is becoming the cloud, and uh, I

127
00:06:57,480 --> 00:07:00,080
Speaker 1: think within the next couple of years, cloud will be

128
00:07:00,160 --> 00:07:04,520
Speaker 1: anywhere that I'm doing kind of cloud native properties independent

129
00:07:04,560 --> 00:07:07,280
Speaker 1: of its its final locality here. And this has kind

130
00:07:07,279 --> 00:07:09,800
Speaker 1: of been the real basis of some of the work

131
00:07:09,840 --> 00:07:12,800
Speaker 1: you guys have been doing the red house strategy the right. Yeah, yeah,

132
00:07:12,840 --> 00:07:17,120
Speaker 1: And you're write about the definition of cloud search changing, right,

133
00:07:17,160 --> 00:07:21,120
Speaker 1: So from this notion of cloud computing is when it

134
00:07:21,320 --> 00:07:26,280
Speaker 1: just happened on somebody else's computer, right or somewhere else.

135
00:07:26,480 --> 00:07:28,440
Speaker 1: And you know, if we go back, right, if you

136
00:07:28,480 --> 00:07:32,760
Speaker 1: can ask yourself, look, where were people's expectations of this frame, right?

137
00:07:33,360 --> 00:07:36,280
Speaker 1: Were they in the P two P sharing? You know,

138
00:07:36,320 --> 00:07:38,720
Speaker 1: if anyone remembers that, right, So there's notion of kind

139
00:07:38,760 --> 00:07:43,520
Speaker 1: of you know, music sharing or streaming um or or

140
00:07:43,520 --> 00:07:45,800
Speaker 1: even this notion that you had with regard to well

141
00:07:45,840 --> 00:07:48,080
Speaker 1: I can get my email and that's being served over

142
00:07:48,080 --> 00:07:50,480
Speaker 1: the internet. And then you know, people to equate the

143
00:07:50,480 --> 00:07:54,040
Speaker 1: Internet to the cloud. And so I'll sort of taking

144
00:07:54,080 --> 00:07:55,960
Speaker 1: people the different sort of you know, aspect of that

145
00:07:57,080 --> 00:08:00,960
Speaker 1: from you, Steve, because I think people expectations for cloud

146
00:08:00,960 --> 00:08:04,200
Speaker 1: competing we're also computing. We're also sort of shaped around

147
00:08:04,760 --> 00:08:07,880
Speaker 1: being able to access software from anywhere they were, right,

148
00:08:07,920 --> 00:08:09,600
Speaker 1: So in the past, WHEA was Hey, I'm locked down

149
00:08:09,600 --> 00:08:12,960
Speaker 1: to particular desktop or particular laptop or machine write a

150
00:08:12,960 --> 00:08:15,000
Speaker 1: physical location. And now you can say, well, I'm free

151
00:08:15,040 --> 00:08:17,200
Speaker 1: now right now, I can you know, get my information

152
00:08:17,200 --> 00:08:19,160
Speaker 1: wherever and you know, the same data I could get

153
00:08:19,200 --> 00:08:20,960
Speaker 1: from a laptop. You know, I can be on the go,

154
00:08:21,600 --> 00:08:24,080
Speaker 1: you know, hiking in Peru, and I can access at

155
00:08:24,080 --> 00:08:27,080
Speaker 1: the same time too. Having said all that, I think

156
00:08:27,160 --> 00:08:30,920
Speaker 1: also the definition of cloud or the sort of expectation

157
00:08:30,960 --> 00:08:33,440
Speaker 1: cloud or sort of shifting to new areas right and

158
00:08:33,480 --> 00:08:37,960
Speaker 1: to all call out around security and privacy. Increasingly we're finding,

159
00:08:38,360 --> 00:08:40,520
Speaker 1: especially red hat, we're seeing customers sort of you know,

160
00:08:40,600 --> 00:08:43,880
Speaker 1: talking about you know, inasmuch as a fine value from

161
00:08:43,880 --> 00:08:47,240
Speaker 1: being able to take advantage of you know, deploying applications,

162
00:08:47,320 --> 00:08:50,319
Speaker 1: running them, thinking avoute, all the new technologies you talked about.

163
00:08:50,720 --> 00:08:53,920
Speaker 1: It's also about, you know, is this secure? You know,

164
00:08:54,080 --> 00:08:56,079
Speaker 1: is this something you know, if I'm audited that I

165
00:08:56,120 --> 00:08:58,800
Speaker 1: can kind of stand behind u, you know, is this

166
00:08:58,920 --> 00:09:01,400
Speaker 1: complying with the regular lation and the governance of the

167
00:09:01,400 --> 00:09:04,640
Speaker 1: particular region that I'm working with? And then ultimately, right

168
00:09:04,679 --> 00:09:06,400
Speaker 1: are we making sure I think maybe you know you've

169
00:09:06,400 --> 00:09:09,080
Speaker 1: talked about this before. Stay around gdp R or privacy

170
00:09:09,160 --> 00:09:11,840
Speaker 1: or regulations that are put in place to ensure that

171
00:09:11,960 --> 00:09:14,880
Speaker 1: when customers and you know, be the individual consumers, are

172
00:09:15,000 --> 00:09:18,200
Speaker 1: actual enterprises, we're meeting the requirements that they've put in

173
00:09:18,280 --> 00:09:22,280
Speaker 1: place to us as providers. This is a good spot

174
00:09:22,480 --> 00:09:24,880
Speaker 1: for me to jump back in here and explain some

175
00:09:24,960 --> 00:09:29,880
Speaker 1: basic concepts like containers and kuberneties. You may remember I

176
00:09:29,920 --> 00:09:33,400
Speaker 1: did an episode not long ago about virtualization, and the

177
00:09:33,400 --> 00:09:36,920
Speaker 1: concept of virtualization is to use software to create a

178
00:09:37,000 --> 00:09:41,960
Speaker 1: virtual machine on top of an actual, real physical machine.

179
00:09:42,040 --> 00:09:44,400
Speaker 1: And when I say machine, I'm really talking about computers.

180
00:09:44,840 --> 00:09:46,640
Speaker 1: And there are lots of different reasons that you would

181
00:09:46,679 --> 00:09:48,960
Speaker 1: want to build a virtual computer on top of a

182
00:09:49,000 --> 00:09:52,280
Speaker 1: physical computer. You might want to have a virtual machine

183
00:09:52,280 --> 00:09:56,120
Speaker 1: dedicated to running a specific application, for example, and you

184
00:09:56,160 --> 00:10:00,480
Speaker 1: want it completely separated from any other process running on

185
00:10:00,520 --> 00:10:04,440
Speaker 1: the physical hardware itself, and the application might not be

186
00:10:04,520 --> 00:10:07,000
Speaker 1: so demanding that would take up all, or maybe even

187
00:10:07,000 --> 00:10:11,480
Speaker 1: a significant amount of a physical machine's resources. So if

188
00:10:11,520 --> 00:10:14,400
Speaker 1: you did decide I'm just going to buy a server

189
00:10:14,800 --> 00:10:17,440
Speaker 1: and that server is just going to run this one app,

190
00:10:17,760 --> 00:10:21,160
Speaker 1: even though the app only relies on maybe five percent

191
00:10:21,280 --> 00:10:24,640
Speaker 1: of the server's processing power and storage, you would have

192
00:10:24,679 --> 00:10:28,640
Speaker 1: a ton of computing power just sitting idle, essentially going

193
00:10:28,720 --> 00:10:32,040
Speaker 1: to waste. Virtual machines give you the chance to run

194
00:10:32,160 --> 00:10:35,600
Speaker 1: data centers more efficiently with less idle time. On computers,

195
00:10:35,640 --> 00:10:39,280
Speaker 1: you could have multiple virtual machines on the same physical device,

196
00:10:39,920 --> 00:10:43,080
Speaker 1: and that way you're maximizing the use of that physical

197
00:10:43,160 --> 00:10:48,360
Speaker 1: hardware and you're minimizing downtime. This is increased efficiency, better savings.

198
00:10:48,400 --> 00:10:52,960
Speaker 1: It just makes more sense. Containers are similar to virtualization

199
00:10:53,040 --> 00:10:56,319
Speaker 1: in many ways. A container sits on top of an

200
00:10:56,360 --> 00:11:00,320
Speaker 1: operating system on a computer, and containers hold all the

201
00:11:00,360 --> 00:11:05,760
Speaker 1: components necessary to run some bit of code in isolation

202
00:11:05,880 --> 00:11:09,040
Speaker 1: of everything else. And you can have multiple containers on

203
00:11:09,080 --> 00:11:12,360
Speaker 1: the same machine, each in its own protected environment, on

204
00:11:12,440 --> 00:11:15,240
Speaker 1: the same operating system, so you don't need a bunch

205
00:11:15,320 --> 00:11:18,400
Speaker 1: of virtual machines on the same physical hardware. You could

206
00:11:18,520 --> 00:11:21,280
Speaker 1: run containers on virtual machines, but you could also run

207
00:11:21,280 --> 00:11:25,719
Speaker 1: containers just on a computer without the virtual machine and

208
00:11:25,800 --> 00:11:29,240
Speaker 1: hypervisor layers, so there's no need to allocate resources to

209
00:11:29,320 --> 00:11:33,199
Speaker 1: apps dynamically because the containers quote unquote contain everything needed

210
00:11:33,240 --> 00:11:37,120
Speaker 1: to run that code. Moreover, it's easy to move those

211
00:11:37,160 --> 00:11:42,360
Speaker 1: containers from environment to environment, so a developer builds the

212
00:11:42,679 --> 00:11:46,480
Speaker 1: some app and puts it into a few containers. The

213
00:11:46,800 --> 00:11:50,959
Speaker 1: different containers are specific parts of what that app does,

214
00:11:51,440 --> 00:11:53,640
Speaker 1: and then it's very easy for the developer to move

215
00:11:53,720 --> 00:11:57,280
Speaker 1: those containers over to a test environment and from there

216
00:11:57,280 --> 00:12:00,280
Speaker 1: to a production environment or deployment to the cloud. You

217
00:12:00,320 --> 00:12:03,360
Speaker 1: can think of containers as keeping things efficient and tidy,

218
00:12:03,480 --> 00:12:06,000
Speaker 1: and they're called that because it's very much like the

219
00:12:06,040 --> 00:12:08,680
Speaker 1: containers you would have in shipping. The whole idea is

220
00:12:08,679 --> 00:12:12,320
Speaker 1: that you've standardized this and it's really easy to move

221
00:12:12,320 --> 00:12:15,120
Speaker 1: it around to wherever it needs to go. Okay, but

222
00:12:15,200 --> 00:12:18,560
Speaker 1: what is Kubernetes. Well, that's a system that's designed to

223
00:12:18,720 --> 00:12:24,200
Speaker 1: manage the deployment, scaling, and management of containerized applications. It's

224
00:12:24,240 --> 00:12:27,720
Speaker 1: not the only one out there. There are other strategies

225
00:12:27,720 --> 00:12:30,720
Speaker 1: for doing this, but it's one that has become incredibly

226
00:12:30,760 --> 00:12:33,920
Speaker 1: popular over the last few years. So an application might

227
00:12:33,960 --> 00:12:38,600
Speaker 1: require the use of several containers. Kubernetes organizes containers for

228
00:12:38,640 --> 00:12:43,600
Speaker 1: applications into groups called pods, nodes, and name spaces. That's

229
00:12:43,640 --> 00:12:47,120
Speaker 1: going from the smallest to largest. So containers your basic unit.

230
00:12:47,240 --> 00:12:50,280
Speaker 1: Then you have pods, the nodes, the name spaces. I'm

231
00:12:50,280 --> 00:12:52,040
Speaker 1: not going to get too much into the weeds here,

232
00:12:52,200 --> 00:12:55,240
Speaker 1: because we get really kind of bogged down. But think

233
00:12:55,240 --> 00:12:57,760
Speaker 1: of this as a way to coordinate all of these

234
00:12:57,920 --> 00:13:01,240
Speaker 1: different containers so that the apps work the way they

235
00:13:01,280 --> 00:13:03,800
Speaker 1: need to and you can easily poured it over to

236
00:13:03,880 --> 00:13:07,599
Speaker 1: whatever environment you need to use. And the use of

237
00:13:07,640 --> 00:13:11,199
Speaker 1: containers and orchestration strategies like Kubernetes is making it easier

238
00:13:11,240 --> 00:13:13,720
Speaker 1: for developers to build and deploy apps that will work

239
00:13:13,760 --> 00:13:16,920
Speaker 1: on any computing environment. All right, now, let's get back

240
00:13:16,960 --> 00:13:20,880
Speaker 1: to my discussion with Stephen a chef. So for the

241
00:13:20,920 --> 00:13:24,440
Speaker 1: average person, I think most people, if they hear about

242
00:13:24,480 --> 00:13:27,280
Speaker 1: cloud computing, they're mostly thinking of public cloud applications. You

243
00:13:27,440 --> 00:13:31,319
Speaker 1: think about cloud storage is probably the number one application

244
00:13:31,360 --> 00:13:35,199
Speaker 1: that they think of us exactly. And then and then

245
00:13:35,320 --> 00:13:37,640
Speaker 1: if they're thinking about the apps that they're running, they

246
00:13:37,720 --> 00:13:40,840
Speaker 1: might have a little bit of appreciation about that as well.

247
00:13:41,840 --> 00:13:45,840
Speaker 1: But I think a lot of people who aren't in

248
00:13:46,200 --> 00:13:51,120
Speaker 1: that world, they hear terms like public cloud and private cloud,

249
00:13:51,440 --> 00:13:54,560
Speaker 1: and that already starts to get a little confusing to them.

250
00:13:54,559 --> 00:13:57,160
Speaker 1: So could you just for a moment kind of talk

251
00:13:57,240 --> 00:14:00,679
Speaker 1: about the difference is what what are those entities and

252
00:14:00,760 --> 00:14:03,319
Speaker 1: what would you use public cloud for versus private cloud.

253
00:14:03,360 --> 00:14:07,520
Speaker 1: If you're let's say, I don't know a global corporation

254
00:14:07,559 --> 00:14:13,440
Speaker 1: that has locations in the EU, for example, Yeah, let

255
00:14:13,480 --> 00:14:15,840
Speaker 1: me do that. So and we'll try to break it

256
00:14:15,880 --> 00:14:19,840
Speaker 1: down whereby we don't get so caught up in definitions

257
00:14:19,880 --> 00:14:22,320
Speaker 1: that we miss the point of where we're trying to

258
00:14:22,360 --> 00:14:27,760
Speaker 1: get to, right, which is um Historically, you know, we

259
00:14:27,840 --> 00:14:30,000
Speaker 1: always dealt with this right. So we we've talked about,

260
00:14:30,040 --> 00:14:33,560
Speaker 1: for example, data centers, and it could be your own

261
00:14:33,640 --> 00:14:35,800
Speaker 1: data center that you managed, could be a third party

262
00:14:35,800 --> 00:14:37,880
Speaker 1: that sort of managed it on your behalf. You might

263
00:14:37,920 --> 00:14:40,320
Speaker 1: deploy some applications on your own, you might have someone

264
00:14:40,360 --> 00:14:42,720
Speaker 1: else deploying on your behalf, and then you should go

265
00:14:42,760 --> 00:14:46,440
Speaker 1: back and forth across them. Now, if you extend that

266
00:14:46,480 --> 00:14:48,720
Speaker 1: out and then you say, well, you know what if

267
00:14:48,760 --> 00:14:50,560
Speaker 1: we started having and I'm going to sort of take

268
00:14:50,600 --> 00:14:54,240
Speaker 1: this if this sort of analogy to its logical conclusion.

269
00:14:54,760 --> 00:14:58,440
Speaker 1: What if we now had a vast pool of compute,

270
00:14:58,480 --> 00:15:01,760
Speaker 1: network and storage, right, and then we dev that up

271
00:15:01,760 --> 00:15:04,440
Speaker 1: to say, some of it lives physically in a certain area,

272
00:15:04,800 --> 00:15:08,160
Speaker 1: managed by a certain party, some live somewhere else managed

273
00:15:08,200 --> 00:15:11,360
Speaker 1: by someone else. You can take advantage of economics. Because

274
00:15:11,400 --> 00:15:14,720
Speaker 1: it shared, multiple parties can use it and then be

275
00:15:14,800 --> 00:15:17,600
Speaker 1: able to say, well, I'll deploy now those applications that

276
00:15:17,640 --> 00:15:20,480
Speaker 1: I have based on policies right now, those policies might

277
00:15:20,480 --> 00:15:23,440
Speaker 1: be cost they might be based on latency, they could

278
00:15:23,440 --> 00:15:26,680
Speaker 1: be based on performance, they might be based on you know,

279
00:15:26,960 --> 00:15:29,760
Speaker 1: we talked about regulation, privacy and governance and so on,

280
00:15:30,240 --> 00:15:33,320
Speaker 1: right and then in that sense, it doesn't really matter

281
00:15:33,720 --> 00:15:36,240
Speaker 1: what we've called it. And this is why I think

282
00:15:36,320 --> 00:15:38,840
Speaker 1: between a red hat and IBM and I think we

283
00:15:38,920 --> 00:15:41,040
Speaker 1: share this vision. And I'm sure Steve you'd agree with

284
00:15:41,080 --> 00:15:44,040
Speaker 1: this right that, you know, the hybrid cloud notion is,

285
00:15:44,080 --> 00:15:46,760
Speaker 1: you know, really the abstraction that we can put in

286
00:15:46,880 --> 00:15:50,400
Speaker 1: front of resources that can be made widely available to

287
00:15:50,520 --> 00:15:52,960
Speaker 1: customers around the world, and then for us to now

288
00:15:53,000 --> 00:15:55,840
Speaker 1: think about what productive things can they do on top

289
00:15:55,880 --> 00:15:58,760
Speaker 1: of that, What new applications can they build? How can

290
00:15:58,800 --> 00:16:01,520
Speaker 1: they integrate both exists stinging around as they have the

291
00:16:01,760 --> 00:16:03,800
Speaker 1: new ones they wanted to build out, How can they

292
00:16:03,800 --> 00:16:07,600
Speaker 1: create great agility and great innovation in vols? Jumping back

293
00:16:07,600 --> 00:16:10,440
Speaker 1: in here again just to clear up a couple more things. So,

294
00:16:10,520 --> 00:16:13,280
Speaker 1: why would a company want to keep some stuff on premises?

295
00:16:13,640 --> 00:16:17,600
Speaker 1: Some in a private cloud and some on a public cloud. Well,

296
00:16:17,600 --> 00:16:19,280
Speaker 1: it has to do with a lot of different stuff,

297
00:16:19,360 --> 00:16:23,880
Speaker 1: including security, governance, and cost. All this data has to

298
00:16:23,960 --> 00:16:28,920
Speaker 1: ultimately live on physical machines somewhere, and it costs money

299
00:16:28,960 --> 00:16:32,160
Speaker 1: to buy and maintain those machines, and they take up

300
00:16:32,160 --> 00:16:37,600
Speaker 1: physical space. So there are limiting factors, mostly money in space.

301
00:16:37,680 --> 00:16:39,760
Speaker 1: The restrict how many computers are going to have in

302
00:16:39,800 --> 00:16:43,360
Speaker 1: your physical location. Now, some stuff you're gonna want to

303
00:16:43,400 --> 00:16:46,960
Speaker 1: keep close to you. Maybe you have some trade secrets

304
00:16:47,040 --> 00:16:51,119
Speaker 1: that you're protecting. Maybe you have private data on customers

305
00:16:51,160 --> 00:16:54,600
Speaker 1: that you don't want leaked out to anybody else. Maybe

306
00:16:54,680 --> 00:16:57,400
Speaker 1: there are specific laws in place that state you have

307
00:16:57,600 --> 00:17:02,240
Speaker 1: to keep certain information under your control and you alone

308
00:17:02,360 --> 00:17:04,920
Speaker 1: are allowed to have access to it. Whatever the motivation.

309
00:17:05,400 --> 00:17:07,760
Speaker 1: You may want some of your data and services running

310
00:17:07,760 --> 00:17:11,080
Speaker 1: on equipment that your team directly manages, so you keep

311
00:17:11,080 --> 00:17:14,840
Speaker 1: all that stuff on premises or on prem We talk

312
00:17:14,920 --> 00:17:17,399
Speaker 1: a lot about the EU and this discussion, because the

313
00:17:17,440 --> 00:17:20,720
Speaker 1: EU has strict rules about what data can and can't

314
00:17:20,800 --> 00:17:24,040
Speaker 1: leave the continent, and in those cases, you have to

315
00:17:24,080 --> 00:17:27,240
Speaker 1: make sure your system respects those restrictions. If you're doing

316
00:17:27,280 --> 00:17:30,560
Speaker 1: business inside the EU, now, you might hire a third

317
00:17:30,600 --> 00:17:35,200
Speaker 1: party to oversee servers running your apps, and that's all

318
00:17:35,240 --> 00:17:38,480
Speaker 1: those particular servers are doing, right you. They aren't running

319
00:17:38,520 --> 00:17:43,120
Speaker 1: any applications for any other client on those particular servers.

320
00:17:43,400 --> 00:17:46,520
Speaker 1: They might all exist in a similar data center, but

321
00:17:46,640 --> 00:17:50,200
Speaker 1: the machines you're using are quote unquote yours alone. You're

322
00:17:50,280 --> 00:17:54,439
Speaker 1: essentially renting them. Your stuff is completely separated from anyone else's.

323
00:17:55,240 --> 00:17:57,320
Speaker 1: Or maybe you've got some services you want to move

324
00:17:57,359 --> 00:18:01,160
Speaker 1: to big public cloud providers, and those solutions might cost

325
00:18:01,440 --> 00:18:05,760
Speaker 1: much less than running the machinery yourself, and the services

326
00:18:05,800 --> 00:18:09,680
Speaker 1: guarantee redundancy. They have multiple machines holding onto your data,

327
00:18:10,080 --> 00:18:13,000
Speaker 1: so if one set of servers go down, other servers

328
00:18:13,080 --> 00:18:17,200
Speaker 1: with the same information can take their place, and this

329
00:18:17,400 --> 00:18:21,400
Speaker 1: takes a lot of the management of that information off

330
00:18:21,480 --> 00:18:23,920
Speaker 1: of your plate. So there are a lot of big

331
00:18:23,960 --> 00:18:27,720
Speaker 1: companies that are using multiple cloud and on premises solutions

332
00:18:28,000 --> 00:18:31,280
Speaker 1: to host their services and their data, and as you

333
00:18:31,320 --> 00:18:35,320
Speaker 1: can imagine, that gets really complicated. Just knowing where stuff

334
00:18:35,520 --> 00:18:39,320
Speaker 1: is is complicated, getting stuff to work together with each

335
00:18:39,359 --> 00:18:43,200
Speaker 1: other on these different platforms is even more so, And

336
00:18:43,320 --> 00:18:45,760
Speaker 1: so you have to figure out how to make all

337
00:18:45,800 --> 00:18:49,080
Speaker 1: this data living in these different environments to play nice together,

338
00:18:49,480 --> 00:18:52,560
Speaker 1: and that's where the concept of the hybrid cloud comes

339
00:18:52,560 --> 00:18:56,199
Speaker 1: into play. Let's get back to Stephen Asches. So this

340
00:18:56,280 --> 00:18:59,280
Speaker 1: kind of gets us into this concept of the hybrid

341
00:18:59,440 --> 00:19:03,160
Speaker 1: cloud strategy. Can you talk a bit more about what

342
00:19:03,240 --> 00:19:06,800
Speaker 1: that is and how that's going to benefit companies? That's

343
00:19:06,800 --> 00:19:11,119
Speaker 1: sactly right. So the part that we sometimes skip over,

344
00:19:11,160 --> 00:19:12,680
Speaker 1: and I think this is kind of you know, where

345
00:19:12,840 --> 00:19:17,280
Speaker 1: hybrid really really shines is far that you know, Steve

346
00:19:17,320 --> 00:19:19,199
Speaker 1: started talking about, right, And I think Steve, you're describing

347
00:19:19,280 --> 00:19:21,119
Speaker 1: this as sort of the two phases, right, you know

348
00:19:21,200 --> 00:19:24,280
Speaker 1: about you know, we're about of our way into the journey.

349
00:19:24,320 --> 00:19:27,560
Speaker 1: We've got any percent to go? Why is that really important?

350
00:19:27,560 --> 00:19:30,440
Speaker 1: It's almost like an iceberg, right, We've got so much

351
00:19:30,520 --> 00:19:32,600
Speaker 1: more to do, and yet we only see the tip

352
00:19:32,920 --> 00:19:35,720
Speaker 1: of what we've done now. If you don't think of

353
00:19:35,760 --> 00:19:37,720
Speaker 1: the world, you know, in a hybrid fashion, when as

354
00:19:37,720 --> 00:19:39,360
Speaker 1: a hybrid you know, I'm sort of gonna call out

355
00:19:39,359 --> 00:19:41,919
Speaker 1: your right at uses a terminology call four footprints, right,

356
00:19:42,760 --> 00:19:44,840
Speaker 1: running something in a physical environment, running something in the

357
00:19:44,920 --> 00:19:47,960
Speaker 1: virtual environment virch your life environment, running it in a

358
00:19:47,960 --> 00:19:50,680
Speaker 1: private cloud, running in a public cloud. If you don't

359
00:19:50,720 --> 00:19:53,679
Speaker 1: have something that stands the four footprints? What are you

360
00:19:53,720 --> 00:19:59,320
Speaker 1: doing right? You are potentially choosing to disregard that any

361
00:19:59,359 --> 00:20:02,000
Speaker 1: percent that you haven't moved over where you can make

362
00:20:02,000 --> 00:20:06,359
Speaker 1: it most productive. Why is it important? Most enterprises of

363
00:20:06,480 --> 00:20:15,040
Speaker 1: any size have large investments in applications, services, processes, people's

364
00:20:15,040 --> 00:20:18,560
Speaker 1: skills that they've made over decades. What happens to all

365
00:20:18,600 --> 00:20:22,280
Speaker 1: of those? Right? And if we aren't able to unlock

366
00:20:22,320 --> 00:20:25,600
Speaker 1: all of that, right, how can we truly deliver innovation

367
00:20:26,080 --> 00:20:28,760
Speaker 1: and the scale that we want while leaving all that

368
00:20:28,840 --> 00:20:31,600
Speaker 1: moroon on the side. Right, So the opportunity to able

369
00:20:31,640 --> 00:20:33,679
Speaker 1: to say, look, I am going to be able to

370
00:20:33,760 --> 00:20:36,080
Speaker 1: bridge you know, existing investments that I've made and I

371
00:20:36,400 --> 00:20:39,840
Speaker 1: obviously worked with the clients you know for decades around this,

372
00:20:40,400 --> 00:20:42,600
Speaker 1: but at the same time expose them to what we

373
00:20:42,800 --> 00:20:45,800
Speaker 1: call you know, cloud native, you know ways of working. Right.

374
00:20:45,840 --> 00:20:48,840
Speaker 1: There's notion of micro services. Right. Let me not build

375
00:20:48,840 --> 00:20:51,520
Speaker 1: out massive applications. Let me build them in smaller and

376
00:20:51,560 --> 00:20:53,600
Speaker 1: more actual fashion. Steeve talked about you and having a

377
00:20:53,720 --> 00:20:56,439
Speaker 1: PI is available right to make it just easier for

378
00:20:56,440 --> 00:20:59,000
Speaker 1: different applications to to interact each other and be able

379
00:20:59,040 --> 00:21:01,800
Speaker 1: to share information data across them, but to be able

380
00:21:01,840 --> 00:21:04,199
Speaker 1: to realize all that promise, and we've got to be

381
00:21:04,280 --> 00:21:07,760
Speaker 1: able to provide a hybrid cloud platform that spans both

382
00:21:08,080 --> 00:21:10,359
Speaker 1: the new environments that we're all trying to go towards

383
00:21:10,760 --> 00:21:13,960
Speaker 1: as well as the existing applications and environment that we

384
00:21:13,960 --> 00:21:17,120
Speaker 1: have running today. And I think it's an interesting case

385
00:21:17,119 --> 00:21:20,280
Speaker 1: in point. Right when we announced the acquisition intent of

386
00:21:20,600 --> 00:21:23,720
Speaker 1: red Hat, I had a ce IO executive VP of

387
00:21:23,720 --> 00:21:27,560
Speaker 1: a large fast food restaurant chain called me up and

388
00:21:27,560 --> 00:21:29,760
Speaker 1: he says, okay, Steve, give me the scoop. Why did

389
00:21:29,800 --> 00:21:32,239
Speaker 1: you do it? And I had to tell him. I said, well,

390
00:21:32,320 --> 00:21:34,679
Speaker 1: let's just take a look at what we're doing with you.

391
00:21:34,840 --> 00:21:37,720
Speaker 1: And at that point in time, um, we were putting

392
00:21:37,720 --> 00:21:40,719
Speaker 1: a server in every single one of those restaurants, were

393
00:21:40,720 --> 00:21:44,040
Speaker 1: putting a private cloud in every single one of his restaurants,

394
00:21:44,280 --> 00:21:46,159
Speaker 1: and what we were attaching that we were attaching our

395
00:21:46,160 --> 00:21:48,760
Speaker 1: Watson services to do the ordering so that you just

396
00:21:48,800 --> 00:21:51,840
Speaker 1: speak in but automatically handle it, etcetera, saving the labor

397
00:21:51,920 --> 00:21:54,439
Speaker 1: on that, etcetera. We had also outfitted every one of

398
00:21:54,480 --> 00:21:56,920
Speaker 1: his stores with IoT cameras, so all of a sudden,

399
00:21:56,920 --> 00:21:59,480
Speaker 1: you see the bustload of high school students start to

400
00:21:59,520 --> 00:22:01,760
Speaker 1: come in. He felt that if he had just a

401
00:22:02,040 --> 00:22:05,560
Speaker 1: minute lead time, he could reposition his employees and be

402
00:22:05,640 --> 00:22:08,320
Speaker 1: ready to take that that that on and manage the

403
00:22:08,359 --> 00:22:12,640
Speaker 1: traffic of that. You know, those two applications resided, and

404
00:22:13,040 --> 00:22:16,399
Speaker 1: we're critical just to that store. They didn't benefit from

405
00:22:16,440 --> 00:22:19,240
Speaker 1: bouncing or sending any data back up to their data

406
00:22:19,280 --> 00:22:21,879
Speaker 1: center or to the public cloud. They all the processing

407
00:22:21,880 --> 00:22:24,200
Speaker 1: etcetera needed to happen right there in the store. I said,

408
00:22:24,240 --> 00:22:26,840
Speaker 1: that's your private cloud. I said, Now that same store

409
00:22:26,880 --> 00:22:30,440
Speaker 1: also has to order from you, do your supply chain,

410
00:22:30,520 --> 00:22:33,320
Speaker 1: do your analytics, do your HR, get your paychecks, etcetera.

411
00:22:33,600 --> 00:22:36,000
Speaker 1: All that and you know, so that's coming back into

412
00:22:36,119 --> 00:22:39,719
Speaker 1: your worldwide headquarters, and that's probably running in conjunction with

413
00:22:39,800 --> 00:22:43,160
Speaker 1: historical applications that you have, and probably some dedicated cloud

414
00:22:43,160 --> 00:22:45,840
Speaker 1: capabilities is there. And I said, and we're also working

415
00:22:45,840 --> 00:22:48,639
Speaker 1: with your marketing department on kind of running your annual

416
00:22:48,640 --> 00:22:51,720
Speaker 1: sweep stakes game and doing your customer loyalty etcetera. You

417
00:22:51,720 --> 00:22:53,440
Speaker 1: want to reach as many as people across as many

418
00:22:53,480 --> 00:22:56,320
Speaker 1: channels as possible. That's your public cloud, and that's what

419
00:22:56,359 --> 00:22:59,480
Speaker 1: you're doing as well. I said. I said, now imagine

420
00:23:00,000 --> 00:23:03,959
Speaker 1: in architecture, so your programmers could build that once and

421
00:23:04,040 --> 00:23:06,840
Speaker 1: they could then deploy that in all three of those

422
00:23:06,960 --> 00:23:11,000
Speaker 1: environments seamlessly, so you didn't have to know ahead of

423
00:23:11,040 --> 00:23:13,240
Speaker 1: time where that application was going to run. You know,

424
00:23:13,280 --> 00:23:15,560
Speaker 1: let's just imagine that all of a sudden, speeds came up.

425
00:23:15,560 --> 00:23:16,960
Speaker 1: You know, all of a sudden, we're doing five G

426
00:23:17,400 --> 00:23:19,800
Speaker 1: I can I can move those private cloud applications back

427
00:23:19,800 --> 00:23:22,639
Speaker 1: to a center location do that more efficiently. A single

428
00:23:22,760 --> 00:23:25,560
Speaker 1: architecture gives the ability to write at once, run it

429
00:23:25,640 --> 00:23:28,240
Speaker 1: anywhere that I want to. We're starting to future proof

430
00:23:28,600 --> 00:23:33,520
Speaker 1: those applications as well. So a hybrid cloud strategy is

431
00:23:33,560 --> 00:23:37,240
Speaker 1: one that has a layer that facilitates operations across different

432
00:23:37,280 --> 00:23:42,080
Speaker 1: computer environments. In an ideal version of the hybrid cloud strategy,

433
00:23:42,280 --> 00:23:45,920
Speaker 1: it wouldn't matter where your data and services lived. The

434
00:23:46,040 --> 00:23:50,160
Speaker 1: hybrid cloud infrastructure would create the connections necessary for services

435
00:23:50,200 --> 00:23:53,560
Speaker 1: to run without any hiccups and give developers opportunities to

436
00:23:53,560 --> 00:23:57,240
Speaker 1: build new applications without having to worry about some services

437
00:23:57,320 --> 00:24:00,760
Speaker 1: or information being off limits. It's just sort of meant

438
00:24:00,800 --> 00:24:05,479
Speaker 1: to smooth everything out and pave the way for more interoperability.

439
00:24:06,080 --> 00:24:08,800
Speaker 1: Let's get back to Stephen the chef, So can you

440
00:24:08,840 --> 00:24:11,960
Speaker 1: talk to me a little bit about IBM S multi

441
00:24:11,960 --> 00:24:17,400
Speaker 1: cloud platform and what that means to businesses. I think

442
00:24:17,440 --> 00:24:21,359
Speaker 1: we early on decided that, you know, no firm or

443
00:24:21,440 --> 00:24:24,760
Speaker 1: no enterprise is going to be wed to a single cloud,

444
00:24:24,840 --> 00:24:27,520
Speaker 1: much much to the chagrine of the public cloud vendors.

445
00:24:27,560 --> 00:24:30,199
Speaker 1: I think, uh, you know, we're starting to hear from

446
00:24:30,240 --> 00:24:32,439
Speaker 1: some of the analysts calling it a mono cloud, you know,

447
00:24:32,480 --> 00:24:35,600
Speaker 1: where they're trying to you know, build either outposts or

448
00:24:35,760 --> 00:24:38,959
Speaker 1: build you know some some some code that replicates their

449
00:24:39,000 --> 00:24:42,400
Speaker 1: public cloud down into the data center. Uh so it's

450
00:24:42,440 --> 00:24:44,679
Speaker 1: more easy to go up to their public cloud. But

451
00:24:44,760 --> 00:24:46,040
Speaker 1: we did a lot of work. We've done a lot

452
00:24:46,080 --> 00:24:49,920
Speaker 1: of interviews with enterprise customers, and you know, they are

453
00:24:50,000 --> 00:24:52,560
Speaker 1: not going to be wed to a single vendor. You know,

454
00:24:52,600 --> 00:24:55,520
Speaker 1: we we learned back from the our our prior days

455
00:24:55,720 --> 00:24:58,040
Speaker 1: of working with them over the past decades. Nobody likes

456
00:24:58,119 --> 00:25:01,240
Speaker 1: lock in. Everybody wants choice, and I think many of

457
00:25:01,280 --> 00:25:05,160
Speaker 1: them are attracted to certain clouds based off unique capability

458
00:25:05,240 --> 00:25:08,479
Speaker 1: and unique functions associated with those. Some of those may

459
00:25:08,640 --> 00:25:11,840
Speaker 1: maybe cost oriented, management oriented, but you're starting to see

460
00:25:11,840 --> 00:25:14,119
Speaker 1: some very unique services that are pretty much went to

461
00:25:14,200 --> 00:25:17,520
Speaker 1: a single cloud as well. So we made the determination

462
00:25:17,640 --> 00:25:19,760
Speaker 1: that we wanted to be one of the few vendors

463
00:25:19,760 --> 00:25:24,639
Speaker 1: that could really tackle a multi cloud problem. And we

464
00:25:24,640 --> 00:25:26,639
Speaker 1: could have done two things. We've taken our stack and

465
00:25:26,680 --> 00:25:30,000
Speaker 1: custom fit it to every single cloud that's out there,

466
00:25:30,280 --> 00:25:35,040
Speaker 1: plus build our own tremendous private cloud infrastructure. Or could

467
00:25:35,119 --> 00:25:39,120
Speaker 1: we look at at a fabric that could be consistent

468
00:25:39,640 --> 00:25:43,720
Speaker 1: across these multiple environments. And this what attracted us to

469
00:25:43,840 --> 00:25:46,520
Speaker 1: our early work that we had done with Kubernetes, and

470
00:25:46,560 --> 00:25:48,320
Speaker 1: then again we were we were you know, it was

471
00:25:48,440 --> 00:25:50,600
Speaker 1: a tremendous ory. Maybe a chef tell the whole story

472
00:25:50,600 --> 00:25:53,600
Speaker 1: on open Shift as well, but but that was unlike

473
00:25:53,640 --> 00:25:55,960
Speaker 1: anything we had seen. And red Hat both brought that

474
00:25:56,040 --> 00:25:58,720
Speaker 1: fabric to the table for us. And then they already

475
00:25:58,760 --> 00:26:01,680
Speaker 1: had you know, deep relationships with all the public cloud

476
00:26:01,760 --> 00:26:03,720
Speaker 1: vendors itself that you know, we would have taken us

477
00:26:03,800 --> 00:26:06,280
Speaker 1: years to develop that. So we felt that this would

478
00:26:06,280 --> 00:26:09,800
Speaker 1: give us tremendous acceleration. Use that beautiful foundation, that fabric

479
00:26:09,840 --> 00:26:12,480
Speaker 1: and their multi cloud relationships, and then all we had

480
00:26:12,520 --> 00:26:14,600
Speaker 1: to do was right on top of that and we

481
00:26:14,680 --> 00:26:16,560
Speaker 1: start to fulfill out our We start to fill out

482
00:26:16,600 --> 00:26:20,240
Speaker 1: our overall multiploud story very rapidly here yes to to

483
00:26:20,320 --> 00:26:22,760
Speaker 1: add towards perceived cetera, which is which is great And

484
00:26:22,760 --> 00:26:24,920
Speaker 1: I think this is a truly a great partnership that

485
00:26:24,960 --> 00:26:29,320
Speaker 1: we put together between Red and IBM. That the platform

486
00:26:29,359 --> 00:26:31,919
Speaker 1: that you know, we've built that that IBM has taken

487
00:26:34,520 --> 00:26:36,840
Speaker 1: into account here and then it's going to build out

488
00:26:37,760 --> 00:26:41,960
Speaker 1: further an ad additional services on top. UM. The foundation

489
00:26:41,960 --> 00:26:44,200
Speaker 1: of that is Linux. And then for the folks who

490
00:26:44,200 --> 00:26:46,800
Speaker 1: for all the technology they know, Linus is the foundation

491
00:26:47,240 --> 00:26:51,160
Speaker 1: of you know, pretty much every significant platform that's running

492
00:26:51,200 --> 00:26:54,320
Speaker 1: out there today, but has been building that for twenty

493
00:26:54,400 --> 00:26:57,280
Speaker 1: years UM. And what we decided was to say, well,

494
00:26:57,320 --> 00:27:00,639
Speaker 1: how can we now think about while Linux was the

495
00:27:00,640 --> 00:27:04,119
Speaker 1: best platform for running applications in traditional data centers, what

496
00:27:04,200 --> 00:27:07,119
Speaker 1: would be the right platform for running these applications in

497
00:27:07,119 --> 00:27:10,240
Speaker 1: a hybrid line environment. And the lesson that we learned

498
00:27:10,280 --> 00:27:15,119
Speaker 1: in building this operating system that's running mission critical applications

499
00:27:15,119 --> 00:27:17,680
Speaker 1: really all around the world, UM, and then build the

500
00:27:17,720 --> 00:27:20,320
Speaker 1: next platform on it, and that's open Shift UM. And

501
00:27:20,320 --> 00:27:22,600
Speaker 1: the journey we've taken, you know, for that is to

502
00:27:22,640 --> 00:27:26,080
Speaker 1: really evolve that from initially being you know, a platform

503
00:27:26,200 --> 00:27:29,120
Speaker 1: we say, well, it's an a pinated platform for specific

504
00:27:29,119 --> 00:27:32,040
Speaker 1: sense of developers to really being one that we can

505
00:27:32,119 --> 00:27:36,120
Speaker 1: say is now serving a multitude applications. So whether you're

506
00:27:36,119 --> 00:27:41,359
Speaker 1: trying to run reservation systems, whether you're thinking about building

507
00:27:41,440 --> 00:27:44,399
Speaker 1: your next gent you know, web application, whether you're thinking about,

508
00:27:44,520 --> 00:27:47,760
Speaker 1: you know, building software that you can stand up and

509
00:27:47,880 --> 00:27:50,119
Speaker 1: run and serve to other customers in the cloud, you

510
00:27:50,160 --> 00:27:53,679
Speaker 1: can now build with this same technology and sticking advantages

511
00:27:53,720 --> 00:27:56,560
Speaker 1: some of the concepts that Steve Leader earlier, and there's

512
00:27:56,600 --> 00:27:59,840
Speaker 1: notions of you know, containers or Kuberneties, which has contained orchestration,

513
00:28:00,760 --> 00:28:04,000
Speaker 1: which has now become industry standards, and so being able

514
00:28:04,040 --> 00:28:07,000
Speaker 1: to now have this well called really is the industry

515
00:28:07,040 --> 00:28:10,359
Speaker 1: standard platform right now, we're serving over a thousand applications

516
00:28:10,560 --> 00:28:15,680
Speaker 1: customers today running these applications that scale along with IBM S.

517
00:28:15,720 --> 00:28:18,480
Speaker 1: Ability to be able to now deploy this hybrid multi

518
00:28:18,480 --> 00:28:22,000
Speaker 1: cloud platform in front of it's thousands of customers, you know,

519
00:28:22,080 --> 00:28:26,359
Speaker 1: I think it's an extremely powerful value proposition that related

520
00:28:26,359 --> 00:28:29,720
Speaker 1: in front of customers. Steve and A Chees have mentioned

521
00:28:29,840 --> 00:28:33,359
Speaker 1: Linux a few times. Lenox is an operating system, meaning

522
00:28:33,480 --> 00:28:36,800
Speaker 1: it's the software that acts as a liaison between programs

523
00:28:37,000 --> 00:28:39,920
Speaker 1: and the computer hardware that makes stuff you know actually

524
00:28:40,000 --> 00:28:43,800
Speaker 1: happen on computers. And Linux is an open source operating

525
00:28:43,840 --> 00:28:48,440
Speaker 1: system with an enormous community of developers. There are numerous

526
00:28:48,560 --> 00:28:51,440
Speaker 1: versions of Linux out there, and they're referred to as

527
00:28:51,600 --> 00:28:55,880
Speaker 1: distros or distributions. They all share the same basic DNA,

528
00:28:56,280 --> 00:28:58,880
Speaker 1: but they have different user interfaces and a few other

529
00:28:59,000 --> 00:29:03,560
Speaker 1: unique aspects to each distribution. Computers running Linux make up

530
00:29:03,560 --> 00:29:07,520
Speaker 1: about nine of the workload in the public cloud, and

531
00:29:07,560 --> 00:29:10,240
Speaker 1: a big reason for that is the open source nature

532
00:29:10,280 --> 00:29:13,320
Speaker 1: of Linux. Because the code is open, anyone can look

533
00:29:13,360 --> 00:29:15,640
Speaker 1: at it. Anyone can take that code and make their

534
00:29:15,680 --> 00:29:19,040
Speaker 1: own version or distribution of Linux. Anyone can look for

535
00:29:19,120 --> 00:29:22,960
Speaker 1: ways to improve how it works, or search out vulnerabilities

536
00:29:22,960 --> 00:29:26,280
Speaker 1: and patch them. Now that's true with open source software

537
00:29:26,320 --> 00:29:29,560
Speaker 1: in general, and it's why open source projects can evolve

538
00:29:29,640 --> 00:29:33,240
Speaker 1: rapidly with a strong enough community contributing to those projects.

539
00:29:33,480 --> 00:29:36,840
Speaker 1: All right, back to the conversation. The next thing I

540
00:29:36,840 --> 00:29:38,680
Speaker 1: want to talk about is something that I think is

541
00:29:38,720 --> 00:29:42,360
Speaker 1: almost synonymous with red hat. It's another two word phrase,

542
00:29:42,920 --> 00:29:47,240
Speaker 1: that being open source. And you know red hat and

543
00:29:47,240 --> 00:29:51,320
Speaker 1: IBM both have done incredible work around open source. I

544
00:29:51,360 --> 00:29:55,320
Speaker 1: know that for my listeners. That sometimes comes as a

545
00:29:55,360 --> 00:29:58,320
Speaker 1: surprise to hear about ibm s involvement in it. That's

546
00:29:58,360 --> 00:30:00,959
Speaker 1: not frequently a name that they would associated with it.

547
00:30:01,000 --> 00:30:03,520
Speaker 1: But I've been to IBM think a couple of times.

548
00:30:04,520 --> 00:30:09,920
Speaker 1: My eyes have been Yeah, it was definitely But yeah,

549
00:30:09,960 --> 00:30:12,440
Speaker 1: let's talk about open source for a bit. Why why

550
00:30:12,560 --> 00:30:16,240
Speaker 1: is that so important? Specifically? Why is it going to

551
00:30:16,280 --> 00:30:21,160
Speaker 1: be critical in this world where we're looking at this

552
00:30:21,160 --> 00:30:26,040
Speaker 1: this cloud infrastructure for various services in different industries. Yes,

553
00:30:26,160 --> 00:30:29,520
Speaker 1: so open sources at the beating hard. It's in the

554
00:30:29,640 --> 00:30:31,400
Speaker 1: d n A, you know, use whatever way you want

555
00:30:31,400 --> 00:30:34,360
Speaker 1: to describe it, you know, for red hat, but has

556
00:30:34,400 --> 00:30:36,800
Speaker 1: been since its earliest days, right, it's has been in

557
00:30:36,840 --> 00:30:40,600
Speaker 1: two decades. Everything that we do with red hat is open, right,

558
00:30:40,640 --> 00:30:43,479
Speaker 1: there's no code that we keep behind. Everything shed out

559
00:30:43,520 --> 00:30:46,080
Speaker 1: of the community. Why do we do that. We've believed

560
00:30:46,240 --> 00:30:48,440
Speaker 1: in that from the earliest days, right, that the greatest

561
00:30:48,440 --> 00:30:50,560
Speaker 1: amount of innovation that will happen will happen out in

562
00:30:50,600 --> 00:30:53,280
Speaker 1: the open um. And and that, by the way, it's

563
00:30:53,280 --> 00:30:55,920
Speaker 1: proven true. Right. So if you look at the basis

564
00:30:56,240 --> 00:30:59,880
Speaker 1: of you know, critical infrastructure, you look at the base

565
00:31:00,120 --> 00:31:03,280
Speaker 1: is of you know, what you see on security, emerging

566
00:31:03,320 --> 00:31:07,920
Speaker 1: technologies like blog chain. You see, uh, innovation that's been

567
00:31:07,920 --> 00:31:10,880
Speaker 1: happening in big data everything is founded on the base

568
00:31:10,920 --> 00:31:15,680
Speaker 1: of open source. That's because also large corporations, you know,

569
00:31:15,680 --> 00:31:20,120
Speaker 1: whether they be providers technology or consumers technology, have started understanding,

570
00:31:20,200 --> 00:31:24,040
Speaker 1: you know, you cannot innovate as well within your own

571
00:31:24,080 --> 00:31:27,080
Speaker 1: sort of for virtual walls of an organization versus being

572
00:31:27,080 --> 00:31:30,320
Speaker 1: able to unlock a global community of innovation. Right, So

573
00:31:30,600 --> 00:31:33,840
Speaker 1: this notion of crowdsource, saying, this notion of collaboration, you

574
00:31:33,880 --> 00:31:35,120
Speaker 1: know how it is that you sort of want to

575
00:31:35,120 --> 00:31:37,920
Speaker 1: think about it. You know, we've always believed that there's

576
00:31:38,040 --> 00:31:41,080
Speaker 1: much more value that you can generate, right when you've

577
00:31:41,080 --> 00:31:44,680
Speaker 1: got hundreds of thousands of eyes looking at something, right

578
00:31:44,880 --> 00:31:49,360
Speaker 1: versus you know, something that's just a small fraction of that.

579
00:31:50,600 --> 00:31:52,600
Speaker 1: So so that's one aspect, right, which is if you

580
00:31:52,600 --> 00:31:54,560
Speaker 1: you can call the philosophical belief, you can call it

581
00:31:54,600 --> 00:31:56,840
Speaker 1: that you know, are sort of you know, a commitment

582
00:31:56,880 --> 00:31:59,240
Speaker 1: that that's that's the way innovation must happen. Went forward,

583
00:31:59,800 --> 00:32:02,920
Speaker 1: um another side of that, right, he said, it's a

584
00:32:02,960 --> 00:32:07,680
Speaker 1: smart decision for customers, right if you're concerned about lock

585
00:32:07,720 --> 00:32:10,880
Speaker 1: in and by the way, which customer isn't What better

586
00:32:10,960 --> 00:32:13,160
Speaker 1: way you know, to be able to avoid that or

587
00:32:13,200 --> 00:32:16,719
Speaker 1: minimize that then to rely on open source technologies. Right

588
00:32:16,880 --> 00:32:21,160
Speaker 1: If your provider, your your vendor isn't delivering the technology

589
00:32:21,160 --> 00:32:23,640
Speaker 1: and the way you wanted to the quality or the

590
00:32:23,640 --> 00:32:25,720
Speaker 1: price that you wanted, now you have the ability to

591
00:32:25,720 --> 00:32:29,000
Speaker 1: go switch out to someone else who's building on that basis.

592
00:32:29,280 --> 00:32:32,120
Speaker 1: And so you know, in that way also you know,

593
00:32:32,320 --> 00:32:34,600
Speaker 1: we think there's great value that's created for customers. It

594
00:32:34,720 --> 00:32:38,240
Speaker 1: also keeps us on its right. It keeps us as

595
00:32:38,240 --> 00:32:40,680
Speaker 1: a company always sort of looking to say, how can

596
00:32:40,720 --> 00:32:43,680
Speaker 1: we contially deliver value for for the for the price

597
00:32:43,760 --> 00:32:47,520
Speaker 1: that that we're charging U customers. And then finally, what

598
00:32:47,640 --> 00:32:50,520
Speaker 1: this also does, right is creates you know, what will

599
00:32:50,520 --> 00:32:54,240
Speaker 1: call a sort of open standards, right ways for different

600
00:32:54,320 --> 00:32:58,960
Speaker 1: organizations to come together to collaborate and start you know, deciding, hey,

601
00:32:59,000 --> 00:33:01,520
Speaker 1: this is the best way for to essentially get a commonality.

602
00:33:01,840 --> 00:33:04,400
Speaker 1: What often happened in technology, and Steve probably knows this

603
00:33:04,440 --> 00:33:07,560
Speaker 1: as well as I do, is that moment different choices

604
00:33:07,600 --> 00:33:10,480
Speaker 1: get made right now, enterprises are forced to pick one path,

605
00:33:10,560 --> 00:33:13,680
Speaker 1: they pick the wrong path. They're now going down, you know,

606
00:33:14,600 --> 00:33:17,160
Speaker 1: a road which will become a dead end. So right,

607
00:33:17,560 --> 00:33:21,080
Speaker 1: if you've got you know, a coalescing of companies around,

608
00:33:21,120 --> 00:33:23,360
Speaker 1: you know, open source and open standards, then they have

609
00:33:23,400 --> 00:33:25,680
Speaker 1: a lot more confidence. Hey, I can build applications, I

610
00:33:25,680 --> 00:33:27,880
Speaker 1: can build services on top of that, and of course

611
00:33:27,920 --> 00:33:30,240
Speaker 1: that will make sure that you know, I have something

612
00:33:30,240 --> 00:33:32,400
Speaker 1: that's vibrant and that's something that has a long life.

613
00:33:32,400 --> 00:33:36,320
Speaker 1: I think Steve we called the future. I love those answers.

614
00:33:36,360 --> 00:33:40,000
Speaker 1: I mean h I I have often referred to open

615
00:33:40,080 --> 00:33:44,160
Speaker 1: source versus having the more closed off approach. If you

616
00:33:44,200 --> 00:33:47,120
Speaker 1: have the closed off approach, you can hire the smartest

617
00:33:47,120 --> 00:33:49,840
Speaker 1: people you can run into, but you can only fit

618
00:33:49,960 --> 00:33:53,600
Speaker 1: so many of the room, right, But an open source

619
00:33:53,600 --> 00:33:56,080
Speaker 1: you have access to all the smartest people in all

620
00:33:56,160 --> 00:34:01,640
Speaker 1: the rooms. So that's a I fully on board on

621
00:34:01,680 --> 00:34:04,720
Speaker 1: the open source train. That's I think that that's where

622
00:34:04,720 --> 00:34:08,840
Speaker 1: we see not just rapid innovation, but we see that

623
00:34:09,040 --> 00:34:13,520
Speaker 1: rapid response when something hasn't gone right because we all

624
00:34:13,560 --> 00:34:17,840
Speaker 1: know that sometimes in software, something there's a vulnerability that

625
00:34:17,880 --> 00:34:20,360
Speaker 1: someone didn't know, or maybe someone builds something new that

626
00:34:20,400 --> 00:34:23,960
Speaker 1: breaks something old. When you have that community there, they

627
00:34:24,040 --> 00:34:27,000
Speaker 1: recognize that so quickly and are able to respond so

628
00:34:27,080 --> 00:34:31,560
Speaker 1: much more nimbly than an in house team typically could that.

629
00:34:32,360 --> 00:34:34,640
Speaker 1: I've been a big proponent of it, so it's it's

630
00:34:34,640 --> 00:34:36,400
Speaker 1: good to see this. I think you're exactly right, and

631
00:34:36,440 --> 00:34:38,160
Speaker 1: I think just case in point, I think somebody was

632
00:34:38,200 --> 00:34:41,520
Speaker 1: doing some pin testing against the Kubernetes code out there

633
00:34:41,600 --> 00:34:45,320
Speaker 1: and a few vulnerabilities were found. They were patched almost

634
00:34:45,640 --> 00:34:49,120
Speaker 1: within days. Look at a commercial software vendor. I was

635
00:34:49,160 --> 00:34:51,799
Speaker 1: involved in starting up the security division at IBM, and

636
00:34:51,840 --> 00:34:54,040
Speaker 1: we used to track with our our X force work

637
00:34:54,080 --> 00:34:56,279
Speaker 1: as to how long it took a commercial vendor to

638
00:34:56,440 --> 00:34:58,799
Speaker 1: patch some of their code. You're talking years if ever

639
00:34:59,080 --> 00:35:01,799
Speaker 1: in some of these cases the speeds unbelievable. Here, well,

640
00:35:01,840 --> 00:35:05,040
Speaker 1: this lets me transition the chef to a question for you.

641
00:35:05,840 --> 00:35:10,120
Speaker 1: Red hat is known for its platform neutrality, for its independence.

642
00:35:10,200 --> 00:35:13,960
Speaker 1: It's been called the Switzerland of i T Switzerland and

643
00:35:14,000 --> 00:35:16,799
Speaker 1: our our board discussions all this. It was there from

644
00:35:16,880 --> 00:35:21,440
Speaker 1: day one. So with that in mind, what steps are

645
00:35:21,480 --> 00:35:23,640
Speaker 1: are you taking over a red hat to to kind

646
00:35:23,640 --> 00:35:26,040
Speaker 1: of ensure that in this new era, how do you

647
00:35:26,520 --> 00:35:29,279
Speaker 1: make certain that this thing that red hat has been

648
00:35:29,320 --> 00:35:34,000
Speaker 1: known for is protected and preserved and grown. Yeah, I'll

649
00:35:34,000 --> 00:35:36,040
Speaker 1: answer from my perspective, and then it'd be great to

650
00:35:36,080 --> 00:35:37,880
Speaker 1: hear from from Steve because then he can tell you

651
00:35:37,920 --> 00:35:44,279
Speaker 1: what steps IBM take, because that's not like, look what

652
00:35:44,400 --> 00:35:45,880
Speaker 1: we've got a saying I think a red hat and

653
00:35:45,880 --> 00:35:48,680
Speaker 1: it's probably true at IBM as well. Um, you know

654
00:35:48,760 --> 00:35:50,919
Speaker 1: red hat is still red hat? What does that mean?

655
00:35:51,560 --> 00:35:54,400
Speaker 1: That means that a big part of our value and

656
00:35:54,400 --> 00:35:56,799
Speaker 1: I being fully recognizes this right as as it should

657
00:35:56,840 --> 00:35:58,440
Speaker 1: have been, you know, going to the process to get

658
00:35:58,440 --> 00:36:02,439
Speaker 1: approvals due to make this accosition happened. A big part

659
00:36:02,440 --> 00:36:04,719
Speaker 1: of our value is to be you know, as you

660
00:36:04,760 --> 00:36:08,680
Speaker 1: describe you in Switzerland or neutral or the commonality. You know,

661
00:36:08,719 --> 00:36:11,480
Speaker 1: you use the word of choice that you want. Um,

662
00:36:11,520 --> 00:36:14,239
Speaker 1: we firmly believe in that. Right. So whether it's for

663
00:36:14,360 --> 00:36:17,960
Speaker 1: us to work with let's say Amazon or Microsoft or

664
00:36:18,040 --> 00:36:21,000
Speaker 1: Google or any of the other you know, large providers

665
00:36:21,160 --> 00:36:25,720
Speaker 1: or other partners right like HP or Dell, emerging companies.

666
00:36:25,719 --> 00:36:28,080
Speaker 1: You know, a big part of what we do right

667
00:36:28,239 --> 00:36:30,680
Speaker 1: is to be able to work with these companies, have

668
00:36:30,800 --> 00:36:34,640
Speaker 1: commercial relationships with them also collaborative community with them. Right.

669
00:36:34,680 --> 00:36:37,080
Speaker 1: And then sometimes you know those two work together really well,

670
00:36:37,160 --> 00:36:39,040
Speaker 1: and other times, you know, we have to sort of

671
00:36:39,040 --> 00:36:41,239
Speaker 1: make sure that we balance across them right to sort

672
00:36:41,239 --> 00:36:44,480
Speaker 1: of keep keep terms consistent and fair. Um, so our

673
00:36:44,520 --> 00:36:47,160
Speaker 1: focus really is that we're going down that path and

674
00:36:47,200 --> 00:36:49,680
Speaker 1: we're want to continue going on that path. We haven't

675
00:36:49,680 --> 00:36:52,400
Speaker 1: really changed any of that. Of course, you know that

676
00:36:52,480 --> 00:36:54,560
Speaker 1: with the opportunity with the IBM is to be able

677
00:36:54,600 --> 00:36:59,440
Speaker 1: to go and avail our customers with with with you know,

678
00:37:00,000 --> 00:37:02,319
Speaker 1: a lot greater reach than than we've had before. But

679
00:37:02,400 --> 00:37:05,719
Speaker 1: that independs that we had the broad ecosystem that we've

680
00:37:05,719 --> 00:37:10,680
Speaker 1: cultivated of providers of partners around the world. We continue

681
00:37:10,719 --> 00:37:14,799
Speaker 1: to work with it and so you know, oftentimes when

682
00:37:14,800 --> 00:37:17,480
Speaker 1: the questions that comes back, you know, my response, I

683
00:37:17,520 --> 00:37:19,880
Speaker 1: don't want it to sound glibe, is to say business

684
00:37:19,880 --> 00:37:23,040
Speaker 1: as usual. Right, We've worked in a certain way. It's

685
00:37:23,080 --> 00:37:26,279
Speaker 1: been reasonably successful, we'd like to believe, and we want

686
00:37:26,320 --> 00:37:28,879
Speaker 1: to keep continue going on that. All Right, It's been

687
00:37:28,920 --> 00:37:32,000
Speaker 1: several weeks since red Hat and IBM came together, and

688
00:37:32,000 --> 00:37:35,759
Speaker 1: the question is is the honeymoon over? How have things been,

689
00:37:36,040 --> 00:37:38,839
Speaker 1: how's the transition going? What have you learned so far?

690
00:37:39,480 --> 00:37:45,600
Speaker 1: I just really started this last year even started well,

691
00:37:45,640 --> 00:37:49,160
Speaker 1: it's been a whirlwind. Right, So, so the the good

692
00:37:49,160 --> 00:37:54,920
Speaker 1: news that wasn't surprised exactly working looking through it for

693
00:37:54,960 --> 00:38:00,160
Speaker 1: a while. UM, I think maybe what the surprice sing

694
00:38:00,239 --> 00:38:05,080
Speaker 1: part has been is that there is so much more

695
00:38:05,120 --> 00:38:08,200
Speaker 1: in common than we thought there was. What do you

696
00:38:08,239 --> 00:38:11,360
Speaker 1: mean by that? It's you know, IBM has invested in

697
00:38:11,480 --> 00:38:14,520
Speaker 1: so you've talked about this, you know, the commitment to Linux,

698
00:38:15,400 --> 00:38:17,680
Speaker 1: the long relationship that I've been read at has had.

699
00:38:18,640 --> 00:38:21,520
Speaker 1: There's a lot of work that's happened from an engineering perspective,

700
00:38:22,280 --> 00:38:26,200
Speaker 1: collaboration over the years that we had in place. UM. So,

701
00:38:27,560 --> 00:38:29,839
Speaker 1: you know, just this sort of notion of hey, we're

702
00:38:29,840 --> 00:38:32,759
Speaker 1: actually working with you know, people that many parts of

703
00:38:32,760 --> 00:38:34,319
Speaker 1: the company have worked with in the past, you know,

704
00:38:34,360 --> 00:38:39,640
Speaker 1: has been good. UM. I think also the realization on

705
00:38:39,760 --> 00:38:43,239
Speaker 1: both sides to respect you know, both parties, if you will,

706
00:38:43,320 --> 00:38:45,759
Speaker 1: culture and heritage right. You know, I've been honestly as

707
00:38:45,800 --> 00:38:48,759
Speaker 1: a long storied one, but all the work that we've

708
00:38:48,760 --> 00:38:51,560
Speaker 1: done with Steve and his team and you know the

709
00:38:52,080 --> 00:38:55,800
Speaker 1: large Organs organization general, you know, has been extremely positive.

710
00:38:56,480 --> 00:39:00,399
Speaker 1: I think you know, both parties have now done work

711
00:39:00,440 --> 00:39:03,080
Speaker 1: them essentially established. You know, we're all called, for lack

712
00:39:03,120 --> 00:39:06,200
Speaker 1: of better describe them, you know, offices within sales organization,

713
00:39:06,280 --> 00:39:10,240
Speaker 1: the products team to interface with IBM um and so

714
00:39:10,560 --> 00:39:13,360
Speaker 1: you know, every person right that doesn't feel like, you know,

715
00:39:13,400 --> 00:39:15,840
Speaker 1: I've got to engage with it doesn't voc from IBM

716
00:39:16,040 --> 00:39:18,880
Speaker 1: and vice versa. You know, we have some you know,

717
00:39:18,880 --> 00:39:20,920
Speaker 1: sort of processes to be able to do that, and

718
00:39:20,960 --> 00:39:23,000
Speaker 1: I think that's important, right because you know, we talked

719
00:39:23,040 --> 00:39:26,120
Speaker 1: a little bit about red Hat still being red Hat,

720
00:39:26,200 --> 00:39:28,319
Speaker 1: you know, the business that we're pursuing, the work that

721
00:39:28,360 --> 00:39:30,799
Speaker 1: we turned to, the neutrality that you know we wanted

722
00:39:30,840 --> 00:39:33,680
Speaker 1: to keep in place as we go forward and do that,

723
00:39:34,080 --> 00:39:36,279
Speaker 1: and so it's important for all that to happen. So

724
00:39:36,680 --> 00:39:39,040
Speaker 1: we've seen all of that and I think that's been great.

725
00:39:39,440 --> 00:39:41,880
Speaker 1: We've also seen the ability, you know, for us to

726
00:39:41,920 --> 00:39:44,920
Speaker 1: reach out to customers to have different conversations. I don't know,

727
00:39:44,960 --> 00:39:48,400
Speaker 1: I was getting pulled into conversations with some customers you know,

728
00:39:48,440 --> 00:39:51,359
Speaker 1: who we've never previously engaged with, mostly because they said, hey,

729
00:39:51,360 --> 00:39:53,160
Speaker 1: you know, we worked very closely with IBM, and the

730
00:39:53,160 --> 00:39:56,120
Speaker 1: CIO of the large insurance organization said, you know, I'd

731
00:39:56,280 --> 00:39:58,719
Speaker 1: love for you and your teams to come up and

732
00:39:58,840 --> 00:40:00,879
Speaker 1: meet with us and talk about you know, what we've done. Well,

733
00:40:00,920 --> 00:40:03,600
Speaker 1: that's opening up new things and more and more of

734
00:40:03,800 --> 00:40:05,960
Speaker 1: you know, when that happens, right, I think, you know,

735
00:40:06,560 --> 00:40:09,120
Speaker 1: there's a great level of comfort within Red Hat to say, yeah,

736
00:40:09,120 --> 00:40:11,120
Speaker 1: this was really good. So it's one hand to sort

737
00:40:11,160 --> 00:40:12,680
Speaker 1: of think it and the other hand to kind of

738
00:40:13,080 --> 00:40:15,560
Speaker 1: see it and say, you know, our culture is in place,

739
00:40:16,160 --> 00:40:18,600
Speaker 1: the way we're working is in place, and neutrality in place,

740
00:40:18,600 --> 00:40:21,719
Speaker 1: and independence is in place, and and their new and

741
00:40:21,719 --> 00:40:25,359
Speaker 1: bigger opportunities. So I think that's good. You know, we

742
00:40:25,360 --> 00:40:27,919
Speaker 1: we had this concept better together. You know, let's let's

743
00:40:27,960 --> 00:40:30,560
Speaker 1: kind of I think one of the biggest fears is

744
00:40:30,600 --> 00:40:33,320
Speaker 1: we turned four hundred thousand people of IBM loose on

745
00:40:33,320 --> 00:40:36,480
Speaker 1: on Red Hat. And yeah, I've have probably spent over

746
00:40:36,520 --> 00:40:40,640
Speaker 1: half of my career in acquisitions at IBM, from Lotus

747
00:40:40,680 --> 00:40:45,040
Speaker 1: to Rational to multiple security companies, etcetera. And I've seen

748
00:40:45,040 --> 00:40:47,279
Speaker 1: both the good and I've seen the bad and the

749
00:40:47,360 --> 00:40:49,680
Speaker 1: nice thing. I think we worked very closely together during

750
00:40:49,719 --> 00:40:52,400
Speaker 1: the closing period as to putting the right type of

751
00:40:52,440 --> 00:40:55,680
Speaker 1: gates in place so that you know, the right discussions

752
00:40:55,680 --> 00:40:57,640
Speaker 1: could be had at the right time. But there wasn't

753
00:40:57,680 --> 00:41:01,360
Speaker 1: this full inundation of activity from from both sides. I mean,

754
00:41:01,400 --> 00:41:04,560
Speaker 1: it can be a little overwhelming some sometimes, but again

755
00:41:04,600 --> 00:41:07,240
Speaker 1: you know this, uh you know, buying a strong growth

756
00:41:07,280 --> 00:41:10,080
Speaker 1: company that had had sixties plus quarters worth of double

757
00:41:10,120 --> 00:41:13,040
Speaker 1: digit growth, we were very dependent on them just doing

758
00:41:13,120 --> 00:41:16,960
Speaker 1: what they're doing as well. But suggestion, I think, you know,

759
00:41:17,040 --> 00:41:18,759
Speaker 1: we've been doing a lot of account planning right now.

760
00:41:18,800 --> 00:41:21,360
Speaker 1: I think you see a lot of excitement between the

761
00:41:21,400 --> 00:41:23,759
Speaker 1: two teams. A lot of things we could not talk

762
00:41:23,800 --> 00:41:26,440
Speaker 1: about pre clothes that we're now able to talk about,

763
00:41:26,480 --> 00:41:29,239
Speaker 1: so we can now actually you know, share information that

764
00:41:29,280 --> 00:41:32,880
Speaker 1: we have on our customer sets, who has water new opportunities.

765
00:41:33,280 --> 00:41:35,879
Speaker 1: And I think the teams are just overly excited as

766
00:41:35,920 --> 00:41:38,120
Speaker 1: we kind of look at some of the first key

767
00:41:38,160 --> 00:41:40,759
Speaker 1: accounts that we're jointly just looking at to see how

768
00:41:40,800 --> 00:41:43,000
Speaker 1: can we serve them better? And and I think we're

769
00:41:43,000 --> 00:41:45,040
Speaker 1: getting a lot of excitement back from our client basi

770
00:41:45,040 --> 00:41:48,360
Speaker 1: as well. So we're excited. I don't think we're you know,

771
00:41:48,400 --> 00:41:50,719
Speaker 1: we're not. We're keeping our eyes open to look for

772
00:41:50,760 --> 00:41:53,160
Speaker 1: friction points as we move forward. I think we've got

773
00:41:53,160 --> 00:41:56,520
Speaker 1: some good mechanisms in place to address those fairly quick. Uh.

774
00:41:56,600 --> 00:41:58,600
Speaker 1: You know, we're doing this podcast from the Red Hat building.

775
00:41:58,600 --> 00:42:00,799
Speaker 1: You still see red Hat on top associate the logo

776
00:42:00,840 --> 00:42:03,560
Speaker 1: in the front. We're not changing anything as well, so

777
00:42:03,840 --> 00:42:07,920
Speaker 1: this whole independence, this Switzerland red hat is still red hat.

778
00:42:07,920 --> 00:42:10,120
Speaker 1: You know. We're taking that very serious. And there's a

779
00:42:10,120 --> 00:42:12,440
Speaker 1: few x i BMRs on the red Hat side they're like, Wow,

780
00:42:12,840 --> 00:42:16,040
Speaker 1: you guys are really taking this serious, and I think

781
00:42:16,080 --> 00:42:18,360
Speaker 1: that's reflecting in a lot of comments. I want to

782
00:42:18,400 --> 00:42:21,160
Speaker 1: thank IBM and red Hat for having me out to

783
00:42:21,320 --> 00:42:25,560
Speaker 1: Raleigh to talk about this partnership and what it means now. Ultimately,

784
00:42:25,640 --> 00:42:28,160
Speaker 1: their goal is to create a service that lets other

785
00:42:28,200 --> 00:42:32,200
Speaker 1: companies build better apps for end users, whether that's folks

786
00:42:32,239 --> 00:42:35,279
Speaker 1: like me and you, or other companies or even just

787
00:42:35,360 --> 00:42:39,480
Speaker 1: people within that organization itself. So IBM and red hat

788
00:42:39,520 --> 00:42:43,680
Speaker 1: are building out the stuff that makes other people's stuff work,

789
00:42:44,320 --> 00:42:46,640
Speaker 1: in other words, and it can be difficult to get

790
00:42:46,640 --> 00:42:49,480
Speaker 1: an appreciation for that. I know that I've been guilty

791
00:42:49,560 --> 00:42:52,319
Speaker 1: at looking at the surface level of a service or

792
00:42:52,360 --> 00:42:55,320
Speaker 1: an app and not really taking into consideration what's required

793
00:42:55,360 --> 00:43:00,080
Speaker 1: to you know, actually work. So this gave me a

794
00:43:00,120 --> 00:43:04,600
Speaker 1: deeper appreciation of that, and frankly, I'm excited to see

795
00:43:04,640 --> 00:43:08,839
Speaker 1: where this goes, because it could mean that the sort

796
00:43:08,880 --> 00:43:10,680
Speaker 1: of things that you and I interact with on a

797
00:43:10,760 --> 00:43:14,760
Speaker 1: daily basis, whether it's an app program on our desktops

798
00:43:14,800 --> 00:43:18,440
Speaker 1: or laptops. Maybe it's Internet of Things related, could be

799
00:43:19,160 --> 00:43:22,200
Speaker 1: a service that we don't even realize is connected to

800
00:43:22,239 --> 00:43:26,439
Speaker 1: the cloud. All of those can become more robust, more

801
00:43:26,600 --> 00:43:30,799
Speaker 1: feature rich, that can work better. We get a fewer vulnerabilities,

802
00:43:30,800 --> 00:43:36,280
Speaker 1: fewer hiccups. That's the ideal, uh future that we could see,

803
00:43:36,320 --> 00:43:40,000
Speaker 1: and I'm really hoping that that's what we get. And ultimately,

804
00:43:40,040 --> 00:43:42,680
Speaker 1: if it works well, we probably won't even think about it.

805
00:43:42,920 --> 00:43:46,239
Speaker 1: That's kind of the way things work, and we know

806
00:43:46,320 --> 00:43:50,160
Speaker 1: that everything's going well if that happens. So thanks again

807
00:43:50,160 --> 00:43:53,440
Speaker 1: to IBM and red Hat. Thank you guys for listening.

808
00:43:53,640 --> 00:43:56,600
Speaker 1: I hope you enjoyed this bonus episode of tech Stuff

809
00:43:56,920 --> 00:44:04,240
Speaker 1: and I'll talk to you again really soon. Text Stuff

810
00:44:04,239 --> 00:44:06,600
Speaker 1: is a production of I Heart Radio's How Stuff Works.

811
00:44:06,760 --> 00:44:09,560
Speaker 1: For more podcasts from I heart Radio, visit the I

812
00:44:09,680 --> 00:44:12,920
Speaker 1: heart Radio app, Apple Podcasts, or wherever you listen to

813
00:44:12,960 --> 00:44:13,880
Speaker 1: your favorite shows.