1
00:00:00,000 --> 00:00:02,860
Well, so you're saying you live around Toulouse, right?

2
00:00:03,160 --> 00:00:03,340
Yeah.

3
00:00:03,580 --> 00:00:09,140
And so, like, if you were work aside, like, if someone was going there, like, say, like

4
00:00:09,140 --> 00:00:14,480
me, importantly, like, what would you recommend would be a, just something relaxing to do?

5
00:00:14,640 --> 00:00:16,560
Like, what's your ideal day in Toulouse?

6
00:00:17,160 --> 00:00:17,560
Toulouse?

7
00:00:18,420 --> 00:00:22,920
Ah, make a small visit of the capital, I think, a nice place in Toulouse.

8
00:00:23,120 --> 00:00:23,340
Yeah.

9
00:00:23,780 --> 00:00:28,280
And if we have time, we have the mountain, the scenery of Toulouse, one hour by car.

10
00:00:28,600 --> 00:00:28,860
Ah.

11
00:00:28,860 --> 00:00:31,080
So, I think you call...

12
00:00:31,080 --> 00:00:32,880
So, sort of outdoor activities.

13
00:00:33,200 --> 00:00:34,160
Yeah, outdoor activities.

14
00:00:34,480 --> 00:00:37,620
And you can visit a big town called Carcassonne.

15
00:00:37,860 --> 00:00:41,360
I think you already saw in some medieval films.

16
00:00:41,580 --> 00:00:42,120
Ah, right, right.

17
00:00:42,200 --> 00:00:43,940
Very nice, nice medieval.

18
00:00:44,140 --> 00:00:45,660
Are there some castles and things there?

19
00:00:45,680 --> 00:00:45,860
Yeah.

20
00:00:46,180 --> 00:00:46,300
Oh.

21
00:00:46,660 --> 00:00:49,580
Big, I don't remember, a lot of films.

22
00:00:50,140 --> 00:00:53,060
Well, you just, you just, well, first, why don't you introduce yourself?

23
00:00:53,380 --> 00:00:53,660
Okay.

24
00:00:54,440 --> 00:00:57,580
I'm working in France, Kallem, since 19 years ago.

25
00:00:57,720 --> 00:01:05,720
And so, I have started as a developer, and now I am in the support team to help the developer.

26
00:01:05,960 --> 00:01:07,100
I am the global architect.

27
00:01:07,440 --> 00:01:07,780
All right.

28
00:01:07,780 --> 00:01:12,960
Because in the team, we provide tooling, framework, CICD for the developers, so a lot of things.

29
00:01:13,480 --> 00:01:18,700
And I check all the consistency between all the people provide.

30
00:01:19,200 --> 00:01:20,580
For example, a new language arrived.

31
00:01:21,080 --> 00:01:22,400
We don't know Node.js, for example.

32
00:01:22,860 --> 00:01:24,600
So, we need to align the tooling.

33
00:01:24,820 --> 00:01:26,220
We need to align the framework.

34
00:01:26,480 --> 00:01:29,520
So, you're sort of like a product manager for the developers.

35
00:01:30,160 --> 00:01:36,040
I mean, if you think of it, well, I mean, tell me if I'm wrong, but if you think of them as customers, right?

36
00:01:36,040 --> 00:01:39,580
Like, you think about what it is they do and what they need and try to help deliver.

37
00:01:39,580 --> 00:01:48,120
So, clearly, one pillar of TechSE is to still be customer-centric and be sure what we provide and fit for the end users.

38
00:01:48,380 --> 00:01:48,560
Right.

39
00:01:48,660 --> 00:01:50,560
And then a background as a developer is nice for that.

40
00:01:51,340 --> 00:01:53,260
It's always good to have.

41
00:01:53,300 --> 00:01:54,480
What did you develop in?

42
00:01:54,700 --> 00:01:55,740
Like, what languages did you use?

43
00:01:55,740 --> 00:01:56,160
Languages?

44
00:01:56,420 --> 00:02:00,320
It was Java, mostly, because Java started a long time ago in France.

45
00:02:00,320 --> 00:02:03,620
You know, I think it was like two days and you need to beat all yourself.

46
00:02:04,060 --> 00:02:04,160
Right.

47
00:02:04,260 --> 00:02:13,780
And when we are starting, for example, when I have started, if we want just to have a table and sort the table, you need to implement all in our table.

48
00:02:14,220 --> 00:02:14,360
Yeah.

49
00:02:14,360 --> 00:02:23,920
In fact, in the team, we have started to develop a set of subcomponents, like what's later called the GSF.

50
00:02:24,180 --> 00:02:24,600
Oh, right, right.

51
00:02:24,600 --> 00:02:27,580
And if you have already set up in France, we have called that Welcome.

52
00:02:28,360 --> 00:02:31,000
And I am with another guy, two guys, we have developed that.

53
00:02:31,180 --> 00:02:40,980
And we have spread this framework in all Air France, and I think in 2010, most of 50% of the application use it in Air France.

54
00:02:42,100 --> 00:02:45,640
And now is, of course, legacy one.

55
00:02:45,760 --> 00:02:48,260
And then, so, is that a collection of services?

56
00:02:48,620 --> 00:02:50,700
Or what was that again that you just said?

57
00:02:50,700 --> 00:02:51,760
It was a tag link, in fact.

58
00:02:52,180 --> 00:02:53,260
Ah, okay, okay.

59
00:02:53,260 --> 00:02:58,660
In principle, so we have just write RF dot dot table.

60
00:02:59,200 --> 00:02:59,860
Oh, right, right.

61
00:02:59,860 --> 00:03:01,280
And that generates a table for you.

62
00:03:01,380 --> 00:03:03,240
You have just to say, okay, I want to sort this colon.

63
00:03:03,680 --> 00:03:05,700
And all the code was generated behind.

64
00:03:05,720 --> 00:03:06,520
Wow, so it auto-generated.

65
00:03:06,540 --> 00:03:10,600
It was very nice for the date.

66
00:03:10,860 --> 00:03:11,400
Yeah, yeah.

67
00:03:11,680 --> 00:03:13,500
But today is...

68
00:03:13,500 --> 00:03:14,120
Yeah, yeah.

69
00:03:14,120 --> 00:03:23,980
Yeah, I was just talking with someone who had been working on another application, and they were describing that the application was basically a database, right?

70
00:03:24,020 --> 00:03:25,740
Like a UI on top of a database.

71
00:03:25,940 --> 00:03:36,300
And I was thinking, I don't know if it was fondly, but I was remembering all the, you know, your joins and outer joins and all your crazy SQL stuff to, like, pull that together.

72
00:03:36,300 --> 00:03:38,940
And yeah, automating that is certainly nice.

73
00:03:39,600 --> 00:03:47,480
Yeah, so in the end, when we presented that to the developer, they reduced their code by two or three at this time.

74
00:03:48,020 --> 00:03:50,100
And they quick, very fast, their development.

75
00:03:50,380 --> 00:03:55,900
And one thing very interesting, and today, very hard, is all the skin of each application was the same.

76
00:03:56,260 --> 00:04:00,140
Because inside the tag link, they say, okay, I am a button, I am here in the screen.

77
00:04:00,320 --> 00:04:00,460
Right.

78
00:04:00,460 --> 00:04:03,400
So I need to be at this render, this rendering.

79
00:04:03,960 --> 00:04:11,320
So by this way, it was very powerful for the developer, because they have not to learn a brand image or things like that, because all was behind.

80
00:04:11,660 --> 00:04:12,140
Right, right.

81
00:04:12,240 --> 00:04:13,200
Yeah, that's a good project.

82
00:04:13,400 --> 00:04:17,640
And how, like, how widely did you say the result of it is used now?

83
00:04:17,780 --> 00:04:18,300
Like, how is it used?

84
00:04:18,400 --> 00:04:19,740
Today, it's decreased, I think.

85
00:04:20,000 --> 00:04:20,200
Right.

86
00:04:20,200 --> 00:04:22,720
Because the application was rewriting, and today we are in Angular.

87
00:04:23,480 --> 00:04:23,700
Right.

88
00:04:23,700 --> 00:04:30,060
And, but, yes, I think in 2010, it was used by 50%.

89
00:04:30,060 --> 00:04:30,640
Right, right, right.

90
00:04:30,660 --> 00:04:31,320
So it was much.

91
00:04:31,680 --> 00:04:39,200
So to that end, so the team that you're on, I mean, you think it would be fair to say you support developers, right?

92
00:04:39,200 --> 00:04:50,320
Like you kind of, I don't know what you call it internally, but you support the developer services and tools, and I'll advocate for them, as it were, about what the platform needs to look like.

93
00:04:50,320 --> 00:04:50,720
Yeah.

94
00:04:51,200 --> 00:04:55,040
And so how, how did that team come about?

95
00:04:55,420 --> 00:05:04,200
In fact, at the beginning, when Techassist started, I said, okay, it was an entity, but no problem, I am project, I'm doing what I want.

96
00:05:04,400 --> 00:05:05,040
Right, exactly.

97
00:05:05,180 --> 00:05:05,780
You had to centralize it.

98
00:05:05,780 --> 00:05:06,780
And it was the beginning like this.

99
00:05:07,180 --> 00:05:17,160
But what happened after two or three years, in fact, when there is a, this project need a migration, if I use the technology, I don't know, for example, Ruby.

100
00:05:17,700 --> 00:05:18,300
Right, right.

101
00:05:18,400 --> 00:05:20,140
And now we say, okay, I want to move.

102
00:05:20,640 --> 00:05:26,580
Ah, because now the stack of operations has changed, and the developer is not there right now.

103
00:05:27,060 --> 00:05:31,440
So the project manager called to Techassist and said, okay, could you please me?

104
00:05:31,780 --> 00:05:35,620
And we said, I'm sorry, we don't use what we provide, so we can help you.

105
00:05:36,060 --> 00:05:41,520
And so by this way, now the project manager said, okay, is it validated by Techassist and can support us after?

106
00:05:41,640 --> 00:05:42,040
Right, right.

107
00:05:42,180 --> 00:05:43,280
And by this way, in fact.

108
00:05:43,380 --> 00:05:45,180
That's always a good thing to check, right?

109
00:05:45,180 --> 00:05:45,480
Yeah.

110
00:05:45,480 --> 00:05:55,400
And by this way, now, for example, when the project starts, we are invited to what is called the launch meeting, just to be sure of what the project want to do.

111
00:05:55,820 --> 00:05:58,160
Now it's not an architect thinks, et cetera, we are more technical.

112
00:05:58,520 --> 00:05:58,720
Right.

113
00:05:58,740 --> 00:06:03,700
And we can say, okay, this framework is good, yeah, no problem, for us it's perfect.

114
00:06:04,160 --> 00:06:05,240
For example, Julian does that.

115
00:06:06,960 --> 00:06:15,840
And by this way, we can keep our expertise level and spread expertise level.

116
00:06:16,080 --> 00:06:25,800
So when they have a problem, they can call us, and mostly we try to find the solution for them, and sometimes we do code review, and we can help to say, okay, it's not this way, or this way.

117
00:06:25,820 --> 00:06:27,180
And we should adapt to this.

118
00:06:27,420 --> 00:06:27,900
Right, right.

119
00:06:27,960 --> 00:06:32,960
So this is sort of like the front end of, I don't think people say governance too much anymore.

120
00:06:33,100 --> 00:06:33,300
Yeah.

121
00:06:33,500 --> 00:06:44,660
But it's the front end of governance in what your team is trying to do is help the developers, make sure you can support the tools and the service, the things that they use.

122
00:06:45,160 --> 00:06:55,300
So if there's a new thing they want to use, it's a good idea to make sure you can support it and work with them early enough on, I guess, over lunch.

123
00:06:55,300 --> 00:07:00,680
Actually, when we start new things, for example, Kafka or things like that, we try to be close with the teams to help them to start.

124
00:07:00,860 --> 00:07:01,100
Right.

125
00:07:01,440 --> 00:07:12,200
But we aren't alone because sometimes there is a part of operation, so that we can help and we have a time to be sure what we provide is in the right way.

126
00:07:12,300 --> 00:07:19,200
So we go to the confederate, we try to keep the good feeling and to say, okay, we need to move in this direction, this direction.

127
00:07:19,620 --> 00:07:26,900
For example, for Cloud Foundry, at the beginning, it was in Tech SE, but in Amsterdam, and it was the first setup with the open source version.

128
00:07:27,320 --> 00:07:29,300
And we said, okay, we have implemented Cloud Foundry.

129
00:07:29,740 --> 00:07:32,420
These developers are very okay and very powerful.

130
00:07:32,960 --> 00:07:36,560
And after, we have tried to say, okay, now please, operation, implement it.

131
00:07:37,540 --> 00:07:39,440
I'm curious, and this is a good instance.

132
00:07:39,560 --> 00:07:43,800
It might be too big, but how do you walk through that?

133
00:07:44,180 --> 00:07:47,460
Do you have a system, a process that you go through that?

134
00:07:47,600 --> 00:07:48,480
At the beginning, it was not a process.

135
00:07:48,480 --> 00:07:49,760
Is it more just talking with people?

136
00:07:49,900 --> 00:07:56,520
No, at the beginning, we have started in Tech SE to implement the CICD, more on the CI part at the beginning, as it was 10 years ago.

137
00:07:56,720 --> 00:08:00,120
And so it was good because, in fact, we are autonomous.

138
00:08:00,700 --> 00:08:06,060
Okay, I have my JI, I have my bucket, I have my bamboo, and all it was perfect.

139
00:08:06,500 --> 00:08:08,700
And to deploy, please, call operation.

140
00:08:09,280 --> 00:08:09,640
Yeah, yeah.

141
00:08:09,660 --> 00:08:10,060
In the test.

142
00:08:10,820 --> 00:08:19,920
And by this way, that's why we say, maybe if we want to have a sandbox, something like that, in kind of sight, people say, okay, Cloud Foundry is powerful.

143
00:08:20,160 --> 00:08:21,460
So they have tried to implement it.

144
00:08:21,580 --> 00:08:22,480
They have implemented.

145
00:08:22,980 --> 00:08:23,660
Project moved.

146
00:08:24,020 --> 00:08:28,520
And when we said, okay, operation, maybe you need to check, it can be powerful too.

147
00:08:29,060 --> 00:08:33,600
It was a little bit, at the beginning, difficult because I say, okay, but we provide tools.

148
00:08:33,600 --> 00:08:36,580
What do you have in Cloud Foundry, which should create in our tooling?

149
00:08:37,120 --> 00:08:38,560
Right, right, right, right.

150
00:08:38,620 --> 00:08:47,360
So beginning, I started with this, and at the end, I say, okay, we are going to build a joint Cloud Foundry team, and we want to deliver the Cloud Foundry solution.

151
00:08:47,740 --> 00:08:55,420
And so, I mean, it strikes me that you're right in the middle of developers and operators, right?

152
00:08:55,580 --> 00:08:58,040
Yeah, it's a subset, in fact, of TechCase.

153
00:08:58,240 --> 00:09:01,200
It was the team with managers, CICD has done that.

154
00:09:01,380 --> 00:09:02,160
Oh, right, right, right, right.

155
00:09:02,160 --> 00:09:04,300
It's not the team with managers framework or anything like that.

156
00:09:04,380 --> 00:09:04,960
They have used it.

157
00:09:05,040 --> 00:09:06,800
I say, why, yes, it's powerful.

158
00:09:07,300 --> 00:09:09,740
Just I have to click, and I can't deploy my application.

159
00:09:09,920 --> 00:09:10,360
It's incredible.

160
00:09:10,740 --> 00:09:11,000
Right.

161
00:09:11,240 --> 00:09:12,920
So starting like this.

162
00:09:13,560 --> 00:09:26,700
So like in the instance of a PCF or something else, like how do you, what are the differences between sort of working with the developers and working with the operations people?

163
00:09:26,980 --> 00:09:27,760
Like you're saying.

164
00:09:28,040 --> 00:09:31,660
It was difficult because what we see, we have started with Cloud Foundry open source.

165
00:09:31,940 --> 00:09:39,600
So when we, operations wanted to start, they say, okay, we are, today you are using Tomcat as an open source.

166
00:09:40,080 --> 00:09:41,380
So platform is an open source.

167
00:09:41,500 --> 00:09:43,240
We are going to implement it in an open source.

168
00:09:43,540 --> 00:09:43,860
Right, right.

169
00:09:44,020 --> 00:09:46,720
And this is what the developers were saying?

170
00:09:47,200 --> 00:09:48,380
The developers, no problem.

171
00:09:48,540 --> 00:09:49,360
They want the platform.

172
00:09:49,580 --> 00:09:49,920
Right, right, right.

173
00:09:49,920 --> 00:09:52,480
No source or Pivotal, no problem for them.

174
00:09:52,920 --> 00:10:00,780
But what we saw is fact is the transformation in Ops was more difficult with the open source version because what we see, they have a lot of silos.

175
00:10:01,340 --> 00:10:02,920
And so you need to convince one department.

176
00:10:03,060 --> 00:10:05,200
They say, okay, it's interesting, but I want to add the databases.

177
00:10:05,680 --> 00:10:06,980
So the other person, do you have a budget?

178
00:10:07,200 --> 00:10:07,380
No?

179
00:10:07,620 --> 00:10:07,780
Okay.

180
00:10:08,660 --> 00:10:13,840
And when things, when Pivotal guys arrive, they say, okay, we can help you to set up.

181
00:10:13,960 --> 00:10:15,860
We can help you to enable all the team.

182
00:10:15,960 --> 00:10:16,560
What is a container?

183
00:10:16,720 --> 00:10:17,420
What is a concept?

184
00:10:17,420 --> 00:10:23,820
What we need to work together and break the silo.

185
00:10:24,640 --> 00:10:31,240
And have some person outside the company help a lot.

186
00:10:31,340 --> 00:10:33,360
Because they are most earned, in fact.

187
00:10:33,520 --> 00:10:44,040
You know, that's an interesting point that having, working with developers can be faster because I guess there's less of them.

188
00:10:44,480 --> 00:10:44,760
Right?

189
00:10:44,860 --> 00:10:46,440
Like there's, it's sort of.

190
00:10:46,680 --> 00:10:47,220
That depends.

191
00:10:47,300 --> 00:10:50,580
In fact, you have some key developers.

192
00:10:51,000 --> 00:10:51,140
Right.

193
00:10:51,140 --> 00:10:51,720
Like you know it.

194
00:10:52,000 --> 00:10:54,560
And so when you say, hey, please, you ring the coffee.

195
00:10:55,000 --> 00:10:56,580
You say, you want this?

196
00:10:56,680 --> 00:10:58,560
I can do it very quickly like this, like this.

197
00:10:58,560 --> 00:10:58,980
Right, right.

198
00:10:58,980 --> 00:11:01,180
And by this way, you can propagate.

199
00:11:01,600 --> 00:11:01,800
Yeah.

200
00:11:02,140 --> 00:11:04,520
So that's a good point.

201
00:11:04,740 --> 00:11:12,040
For example, when we have started the Pepe transformation, of course, we are going to see some developers we are knowing because we say you have no budget.

202
00:11:12,040 --> 00:11:20,340
You need to take a new budget, this transformation, but you have some people from Tech.se and Pivotal came and helped you to set up the transformation.

203
00:11:21,060 --> 00:11:24,760
And of course, it was more easiest when you're knowing the developer.

204
00:11:25,300 --> 00:11:25,420
Right.

205
00:11:25,420 --> 00:11:31,400
What we see is for the early adopter, it's easy, but after you want to scale, it's not enough.

206
00:11:31,880 --> 00:11:37,560
And now, for example, we are going to buy it by the hierarchical way.

207
00:11:38,080 --> 00:11:38,240
Right.

208
00:11:38,240 --> 00:11:42,700
Like, okay, we wanted to re-platform, to modernize application.

209
00:11:43,040 --> 00:11:44,780
So you need budget, you need to evaluate.

210
00:11:45,300 --> 00:11:47,040
And you see, it's much larger in scope.

211
00:11:47,060 --> 00:11:49,280
Yes, it's more larger than what we are today, in fact.

212
00:11:49,420 --> 00:11:49,840
Right, right.

213
00:11:49,840 --> 00:11:58,400
And so it sounds like with developers, before you get to the larger in scope, you know, application transformation stuff.

214
00:11:58,480 --> 00:12:02,120
But initially, it's a lot more casual to talk with them.

215
00:12:02,120 --> 00:12:06,520
I mean, you know, as you said, you can talk with them over coffee and you know the key people.

216
00:12:06,640 --> 00:12:10,140
But then, as you were saying, in operations, there are many different silos.

217
00:12:10,540 --> 00:12:10,680
Yeah.

218
00:12:10,680 --> 00:12:15,600
And so you almost have to go visit and learn all those different people.

219
00:12:15,780 --> 00:12:24,640
The good point is when we see Cloud Foundry open source as really difficult to implement in apps, there is a high decision in France-KLM to say,

220
00:12:24,800 --> 00:12:29,140
okay, we are creating a new program dedicated on the containerized platform.

221
00:12:29,680 --> 00:12:34,120
And there is already a lot of initiative around Kubernetes, Docker, things like that.

222
00:12:34,420 --> 00:12:36,760
And they say, okay, we put all the people in the same place.

223
00:12:36,820 --> 00:12:38,020
We create a virtual team.

224
00:12:38,280 --> 00:12:38,840
Right, right, right.

225
00:12:38,840 --> 00:12:44,840
And in this virtual team, me and Julien are the dev representative.

226
00:12:45,320 --> 00:12:47,160
So we have created what we call the MVP.

227
00:12:47,640 --> 00:12:56,120
And we say, okay, we have done a survey with the developer that the features I want, we have created a subset because at the beginning, it was more than 100 of requirements.

228
00:12:56,160 --> 00:12:56,780
As always, right.

229
00:12:56,800 --> 00:13:00,060
If we say that to the, please develop that we have 100, it's very hard.

230
00:13:00,480 --> 00:13:03,620
So at the end, we reduce it to 40, I think.

231
00:13:03,720 --> 00:13:04,860
Okay, that's a big reduction.

232
00:13:04,860 --> 00:13:07,960
And most of them are more about the platform concept.

233
00:13:08,360 --> 00:13:08,640
Yeah, yeah.

234
00:13:08,720 --> 00:13:11,500
And some of them are about the services.

235
00:13:11,840 --> 00:13:11,980
Okay.

236
00:13:11,980 --> 00:13:16,200
For example, in the services, we said just, please put in self-service a post-gray and release.

237
00:13:16,960 --> 00:13:20,560
And the rest was more, okay, I want to be able to manage myself, my environment.

238
00:13:20,820 --> 00:13:24,920
I want to be able to declare automatically the DNS.

239
00:13:25,160 --> 00:13:27,300
But I think we were natively, in fact, in the platform.

240
00:13:27,860 --> 00:13:33,500
On that point, I'm curious, like, so what were, like, some of the 60 things that were cut?

241
00:13:33,500 --> 00:13:38,140
Like, it's interesting to think about, like, what actually are the high-priority things versus now?

242
00:13:38,140 --> 00:13:46,640
Mostly it was services at the beginning because, for example, we wanted Oracle, we wanted MySQL, RabbitMQ, a lot of services.

243
00:13:46,940 --> 00:13:47,160
Right.

244
00:13:47,380 --> 00:13:59,420
And some of them are most about the autonomy of the developer for existing things inside the platform because today we can reach them by a cup, for example, in platformery.

245
00:13:59,980 --> 00:14:09,380
I guess what you're saying is, so you might have, I'm just making up some numbers, you might have 50 existing services, whether they're data services or process things.

246
00:14:09,620 --> 00:14:12,760
And, of course, you've got to do all 50 of them, right?

247
00:14:12,800 --> 00:14:13,820
That's all priority one.

248
00:14:14,340 --> 00:14:19,820
But you can kind of systematically go through and say, well, they already exist, right?

249
00:14:19,860 --> 00:14:23,600
So we could do a minimal amount of work to make it so you can use them.

250
00:14:23,840 --> 00:14:26,880
And at some point, we could integrate them more fully into the platform.

251
00:14:27,080 --> 00:14:31,740
But you can, they're not so high-priority versus other ones that we need to make more native.

252
00:14:32,520 --> 00:14:42,840
Yeah, for example, when we have kept Redis and Postgre at the beginning, it was just because all new projects in R-France KNM should be used as a rational database of Postgre.

253
00:14:42,960 --> 00:14:44,720
So as we said, we are going to put this one.

254
00:14:44,980 --> 00:14:45,200
Yeah.

255
00:14:45,480 --> 00:14:49,560
Because mostly of applications have other databases at the minimum.

256
00:14:49,960 --> 00:14:50,360
Right, right.

257
00:14:50,580 --> 00:14:53,000
And for Redis, it was simple.

258
00:14:53,120 --> 00:15:00,500
If we started to implement a Node.js application, and if you want to distribute caching, it's Redis, it's not Postgre.

259
00:15:00,500 --> 00:15:03,020
So that's why we put these two in the I-priority.

260
00:15:03,140 --> 00:15:05,140
So you have that prioritization of services.

261
00:15:05,480 --> 00:15:05,580
Yeah.

262
00:15:05,580 --> 00:15:07,420
And I guess, where does that go?

263
00:15:08,020 --> 00:15:12,100
Is that what goes back to operations to work on, or does your team work on that?

264
00:15:12,280 --> 00:15:12,600
No.

265
00:15:12,900 --> 00:15:14,960
In CAD, we are just providing the requirements.

266
00:15:15,100 --> 00:15:15,960
We explain what we want.

267
00:15:16,560 --> 00:15:19,360
And after it's in this operation, they should provide us.

268
00:15:20,180 --> 00:15:28,440
But it was very difficult at the beginning because to push the requirement of the size broker, we have four teams in operation can handle it.

269
00:15:29,180 --> 00:15:30,400
And that's a good thing.

270
00:15:30,480 --> 00:15:34,300
The last month, they say, okay, we're creating only one entry point.

271
00:15:34,860 --> 00:15:36,180
So for me, it's not simple now.

272
00:15:36,440 --> 00:15:39,980
I speak with them, and these people are going to dispatch in operation.

273
00:15:40,660 --> 00:15:42,680
Because, for example, I have the database team.

274
00:15:43,220 --> 00:15:45,520
I have the storage team, et cetera, et cetera.

275
00:15:45,620 --> 00:15:50,840
So each time I want something, I need to discuss with the architect of ours or the responsible of the platform.

276
00:15:51,160 --> 00:15:53,860
So now, in operations, they have rationalized.

277
00:15:54,380 --> 00:15:54,560
Right, right.

278
00:15:54,560 --> 00:15:56,220
So for us, it's not easy.

279
00:15:57,220 --> 00:16:02,400
In fact, if we check with the operation, I already have the services for the current stacks.

280
00:16:02,960 --> 00:16:03,160
Right, right.

281
00:16:03,160 --> 00:16:09,120
And so what we ask them is just we wanted to be able to consume as a self-service.

282
00:16:09,540 --> 00:16:11,940
And so, by the way, we ask us to create a service broker.

283
00:16:12,440 --> 00:16:15,440
There is a service broker today inside the platform.

284
00:16:15,680 --> 00:16:21,780
But when we ask to the operation, please install it, they say, no, it's difficult because we don't manage this stack.

285
00:16:22,040 --> 00:16:23,000
We don't manage this OS.

286
00:16:25,100 --> 00:16:32,340
And they say, no, we wanted to use our current ready implementation.

287
00:16:33,160 --> 00:16:36,520
And so for that, of course, I need to create their own service brokering to do that.

288
00:16:37,180 --> 00:16:40,100
So now there is one dedicated team to do it.

289
00:16:40,620 --> 00:16:41,280
Oh, right, right, right.

290
00:16:41,340 --> 00:16:43,180
That's sort of like the service broker team.

291
00:16:43,180 --> 00:16:58,100
So having gone through all of this for a long time, if, let's say, someone was starting new doing this, right, outside of Air France KLM, like, what's, like, the playbook you would give them?

292
00:16:58,280 --> 00:17:03,600
Like, what's, like, the recipe you would give them for putting this together, a team like this together?

293
00:17:03,600 --> 00:17:15,400
In fact, today, when we have new people arrive in Air France KLM, we have explained what is working in Air France, what is a CICD, what is all the tooling that you should use, the starter pack, if you want.

294
00:17:15,480 --> 00:17:15,660
Sure.

295
00:17:16,080 --> 00:17:18,160
Your initial sort of on-ramping training.

296
00:17:18,160 --> 00:17:22,380
Yes, just to see, yes, what is the entity, what is legacy, what helps they can provide for us.

297
00:17:23,220 --> 00:17:30,600
And after, they have, in the wiki, all information to set up their own environment for themselves.

298
00:17:30,780 --> 00:17:42,380
And today, when we wanted to improve it, so we have created the TechAC Pro, where it's coaching for the first sprint, if you want, where we work with us.

299
00:17:42,480 --> 00:17:49,860
Because previously, we are just waiting, the developers say, I have need to help, and they come, and we have to solve the problem.

300
00:17:50,620 --> 00:17:53,380
And two days later, they come again, and they say, I have a problem.

301
00:17:53,780 --> 00:18:00,680
So now the idea is, okay, you start, we are going to help you to set up your environment, and we are more close for one week.

302
00:18:00,680 --> 00:18:01,180
Thanks, for example.

303
00:18:01,880 --> 00:18:08,400
And we help us to set up, and to be sure the CICD is implemented, the code is set up.

304
00:18:08,540 --> 00:18:10,040
Oh, like in version control.

305
00:18:10,400 --> 00:18:10,600
Yeah.

306
00:18:10,740 --> 00:18:11,020
Yeah.

307
00:18:11,280 --> 00:18:16,400
So there's almost, I mean, we at Pivotal call that kind of process like a dojo, right?

308
00:18:16,400 --> 00:18:17,500
Yeah, like a dojo.

309
00:18:17,520 --> 00:18:18,400
Which is a fancy word.

310
00:18:18,400 --> 00:18:22,720
I think we are learning today, with Pivot transformation today, we learn about the pairing method.

311
00:18:23,080 --> 00:18:26,540
Maybe it's something we can put inside, in place, we are going to see.

312
00:18:26,880 --> 00:18:28,980
Because what you see was powerful for that.

313
00:18:29,500 --> 00:18:32,360
So maybe it's a good idea to enable the people by this way, too.

314
00:18:32,600 --> 00:18:32,840
Yeah.

315
00:18:33,060 --> 00:18:38,460
So that seems like a part of the cookbook of setting it up is, and to say it out loud seems

316
00:18:38,460 --> 00:18:43,220
obvious, but people probably don't do it, is you should do some training, right?

317
00:18:43,220 --> 00:18:49,640
Like when you come up with the common services for developers, and not only do you want them

318
00:18:49,640 --> 00:18:55,220
to use the existing ones, but understand the process of getting new ones added, you've

319
00:18:55,220 --> 00:18:59,680
got to train them about that, rather than just sending them like, here's a wiki page to read.

320
00:18:59,800 --> 00:19:00,060
Good luck.

321
00:19:00,060 --> 00:19:04,340
Yeah, but no, that's why we wanted to focus more on the coaching.

322
00:19:04,460 --> 00:19:05,280
Exactly, exactly.

323
00:19:05,620 --> 00:19:08,960
Because what we see in the people, even if you have a nice documentation, most of the

324
00:19:08,960 --> 00:19:12,420
developers don't read it, and it's hard to keep it very up to date.

325
00:19:13,080 --> 00:19:13,800
Exactly, exactly.

326
00:19:13,800 --> 00:19:14,940
Because it changes very fast.

327
00:19:15,580 --> 00:19:19,340
So yes, we put effort today on the coaching part.

328
00:19:19,520 --> 00:19:23,280
So the coaching part is a huge amount of the process.

329
00:19:23,480 --> 00:19:25,580
Yeah, the process is, yeah.

330
00:19:25,580 --> 00:19:27,660
All right, well, as the final question.

331
00:19:28,140 --> 00:19:34,380
So when you're thinking about like, you know, everyone, including myself, go on vacation

332
00:19:34,380 --> 00:19:36,480
for a while, come back, it'll be a nice fall.

333
00:19:36,740 --> 00:19:40,440
Like, what are you planning on, like, what's a problem you're planning on solving over the

334
00:19:40,440 --> 00:19:41,680
next like six months or so?

335
00:19:41,920 --> 00:19:46,360
Like, is it just down to the services to implement, or is there a part of the process you want to

336
00:19:46,360 --> 00:19:46,620
fix?

337
00:19:46,780 --> 00:19:49,060
Like, how are you going to improve the team?

338
00:19:49,060 --> 00:19:54,840
I think two things on upside, what they should deliver now is the brokering and the PKS

339
00:19:54,840 --> 00:19:58,580
environment, because it's not yet common in France, KLM.

340
00:19:59,500 --> 00:20:03,760
And the last one is to enlarge the service brokering we have today.

341
00:20:03,900 --> 00:20:04,380
Right, right.

342
00:20:04,600 --> 00:20:08,180
That's the main point, and continue the PPP transformation.

343
00:20:08,800 --> 00:20:09,200
Right, right.

344
00:20:09,300 --> 00:20:10,500
Yeah, that'd be interesting.

345
00:20:11,220 --> 00:20:12,120
There's not that many people.

346
00:20:12,240 --> 00:20:13,180
So it was not the last question.

347
00:20:13,440 --> 00:20:16,500
No, I'm always bad at that.

348
00:20:16,660 --> 00:20:18,000
I usually ask like one or two more questions.

349
00:20:18,000 --> 00:20:20,360
Last topic area, let's call it.

350
00:20:21,360 --> 00:20:25,920
But you'll be in an interesting role, because there's not that many organizations like Air

351
00:20:25,920 --> 00:20:31,600
France, KLM, that are figuring out providing Kubernetes as a service, right, like with PKS.

352
00:20:31,840 --> 00:20:35,440
And so that'll be really fun to, like, see what that's like, right?

353
00:20:35,480 --> 00:20:38,380
Like, to see what people actually end up using and how it's supported.

354
00:20:38,780 --> 00:20:42,960
And there'll be a lot of over the next, if we talk in a year, you should have a lot of

355
00:20:42,960 --> 00:20:45,480
good stories about what that actually looks like.

356
00:20:45,480 --> 00:20:48,420
I think in the story, as I said previously, I started a long time ago.

357
00:20:48,700 --> 00:20:48,840
Yeah.

358
00:20:48,840 --> 00:20:51,700
In KLM's side, there are already a lot of applications running on Kubernetes.

359
00:20:52,340 --> 00:20:56,320
So we have a lot of learning about how to integrate in the JCD, how to do patch management.

360
00:20:57,000 --> 00:21:00,300
So I think we have the best of the world.

361
00:21:00,620 --> 00:21:00,880
Yeah.

362
00:21:00,880 --> 00:21:05,160
With PKS and PKS, yes, we can bring a new stage.

363
00:21:05,460 --> 00:21:05,820
Absolutely.

364
00:21:05,820 --> 00:21:06,320
For Skyrim.

365
00:21:06,740 --> 00:21:06,980
Yeah.

366
00:21:07,240 --> 00:21:07,680
Well, thank you.

367
00:21:07,780 --> 00:21:11,760
It's, you know, we, there's always a lot of discussions in the community about, like,

368
00:21:11,760 --> 00:21:17,200
doing platform as a product and developer services and getting a little notion of the actual,

369
00:21:17,540 --> 00:21:23,180
what would you call it, the struggles slash exciting learnings, right?

370
00:21:23,380 --> 00:21:27,940
The way it actually works and the people you need to talk with and the processes you arrange

371
00:21:27,940 --> 00:21:28,860
are not so great.

372
00:21:29,180 --> 00:21:31,240
They're not documented as well as they could.

373
00:21:31,540 --> 00:21:32,900
So I think you can give us a little look at it.

374
00:21:32,940 --> 00:21:33,320
So thanks.

375
00:21:33,680 --> 00:21:34,360
I appreciate it.

376
00:21:34,480 --> 00:21:34,740
Thanks.

377
00:21:34,940 --> 00:21:35,180
Thank you.

378
00:21:35,180 --> 00:21:35,180
Thank you.