 Hello everyone and first a big thanks to For for sasia to accept my talk, and I I'm really happy to be here. It's my first time in Singapore and Except the jet lag. I really enjoy it But it's okay, and yeah, I'm working for captain we've cut him in a four four months now I would just just introduce myself Rapidly and I'm French you could have my accent, okay? I like eating bread and work in the street with my dog and drinking wine as usual I am a big fan of martial arts. I practice martial arts for 25 years now And big fan of Bruce Lee is because of him. I started to practice martial heart, and I'm continuing the rent now I'm in a free and open source world free software exactly for 15 years now I contributing I've been contributing and in a lot of open source project. They are also in open stack For example, I create in the open stack French user association in France, but also in Montreal I be a part of the first free software association in France named April. I was VP for years I I I was lucky. I have I talk for example. I have some talk in the Libre planet the free software event in Boston and For I spent my last four years in in Canada working for manual life I think you know manual life in Singapore. You also have a manual life. It's it's it's a financial company particularly on retirement and Mostly on retirement and for four years now. I'm working with Kajimini. I'm in charge of I'm working in Toulouse in the south of France. I'm back to my homeland and I'm in charge particularly of Airbus Help Airbus, but also Thales and some over company you have here there to to work on open Global technical strategy, but particularly open source in cap in just to let you know in in manual life I was director of DevOps for the Canadian division and after I run the Global Kubernetes platform worldwide for all the company and and what's that's it about me What I yesterday I heard a lot open source one personally I Never Work in open source because I would like to one is like martial heart. You know, I never start much I I purchase martial heart for 25 years not because I would like to to win someone It's because I would like to be a better myself and that's why I'm doing open source today And that's why I'm doing open source for four years and and that's really important because okay, we won that's it but We have a huge challenge in front of us because we we're talking about particularly in a big company We have different legacy to manage first. We have the technical legacy. You won you win today But anyway, you have to deal with 30 years A proprietary solution deploy in company. You have to deal with stuff In production today, you have to manage them You have maybe you have to work with them for at least the next 10 years And this is really important when you're talking about a big company thinking not like I'm a startup I just thought today. I'm gonna grab some Kubernetes. No, you have to manage a real fact. You have web sphere You have eyes for eyes for thousand hundreds You have a lot of technology and you're gonna have those technology for years. Also, you have a human legacy, you know, I Have been used to work with with Linux guy, I'm a Linux guy and Today my team is not the Linux guy today my team its windows guys is VMware guys And that's people used to work in a properties world used to work with projects Already built used to work on in a way very different Also, you have a lot of people from hardware and you know when you're talking about microservices to someone I used to work on the hardware side. It's it's a big challenge And this is really important when you you would like to deal with particularly big company You have to think okay about everything you said It's good. And if you know it's good But now how you apply that with people they are not maybe sometime ready to do and to practice in the real life First it's about management You have a lot of waterfall mindsets in a big company particular waterfall is not only the way you manage software production or Software life cycle. It's also a way you managing problem. And for example in a big company project manager there are there are the master of the class, you know, they decide everything And this is really important to understand You have the hierarchy between technical people and non-technical people is really On the advantage of non-technical people in big company and because for many reasons Historical reason also you have you very they are really sharp or cost-saving strategy For example, when you work with Airbus Airbus, it's a bigger big big company They manage planes all around the world and they manage their provider as they manage any Over-provider, you know and when they're talking about software when they're talking about how she they would like to save cost They would like to save money Also, it's a procurement process the way you acquire software your cry services. They are on the they are really They build it on the on the old-fashioned made they build it about subscription. They build it about How I'm gonna pay for Microsoft and so on. That's why I like this about Sentence it's really about okay. You have to convince yourself. It's like you mantra I would like to do open source on taxes good for me. I have to do that But how and how I'm gonna be ready People are I scare today really in big company? I think I scare for their job I scare for their futures and this is really important to To help them and to figure it out and to find a way to to resolve First We have the good news Force are mature today when we're talking about a voice technology both different stacks. They are not Rocket science at least all of them are here for five years even Kubernetes is one of the of the last and Spinnaker maybe is the last one but for example when I'm talk to my this is my My stack I'm talk with my clients, you know, I manage when I was in manual life people talk about fun tree in production Today, I'm running a Kubernetes and docker previously with people tall Kubernetes now with open shift We even have a vanilla version on each scenario. We use to today a g-club Artifactory Jenkins, you know, it's really important to understand the stock are here Maybe sometimes they are the big message and standing about what is continuous delivery and what is continuous integration? There are a lot of people is understand about that and and today we managing my team is managing the Infrastructure part just look at this picture if you look at only one or two years ago an infrastructure team manage only private and public Infrastructure as a service you could say private or public infrastructure today. We have to manage all of them You know last Yesterday you have to manage a VM today You have to manage a continuous delivery platform a containers platform And you have to manage and to offer to your client all Solution to deploy the CI that's a wall change of the world It's everything. It's changing and you have to manage right and to to build your skill set on it and and But we have another good news in this world communities are strong and Really really strong just look at today what we have we have an event like for sahaja on so we could sell a grand event after that you have Cloud native foundation you have OpenStack foundation. I think OpenStack really I've been working for long with OpenStack OpenStack really open after the Linux foundation really open the new way of managing foundation today You have cloud native foundation OpenStack foundation is soon open infrastructure foundation You have the Linux foundation just look at the Linux from the exchange the size of the foundation today, you know You you're going everywhere. You have Linux foundation somewhere Apache it's the same thing Apache sometimes you you say just stop to accept project You are too big you are more project that people you know It's it's a problem that but but she is strong or so and more than that Apache It's the way you managing your you lessons and it's the way you managing the collaboration It's that's really what's Apache bring on the table You also have eclipse for everything. It's about Java But you know for I don't know if you know but for the first time you have a Jakarta Just replace the Java to Java he and for the first time eclipse really manage the new version of the Java runtime and This is really interesting. I have friends of mine everywhere now and I really Didn't expect that only a few years ago. We are we we do have a foundation We have a foundation so strong and first First, sorry We have the business is mature too. Just look at the market today. Okay readout IBM Okay, don't care about the acquisition, but let's look at readout look at our she-corp The we really good project really a good way to attack the market They are mature on not only on the technical side They are mature on the way they go on the market on the way they manage the partnership with Over vendors with with a company like us G frog and github they erased I think all of them around the 15 million dollars no 60 million each of them dollars last year to grow the company Github was a cry by Microsoft. Red Hat was a cry by by by IBM and Ashicorp, I think a lot of a lot of you know terraform for example or never took like that It's it's a huge and both company are well And that's why big over the the legacy people like VMware like IBM and some try to attract them and Just to be sure. Okay but now If you would like to think about big company if you would like to manage a big company is not about excel Documentation is not about process. You have to think 24 7 Everything you're doing today. It's to you have one objective. I'm gonna run that platform 24 7 I don't want no one wake up on Saturday morning at 4 a.m To fix my platform in production never never never no one touch the platform During the weekend at night and so on this is really we not Netflix We're not Twitter. We're not a company like that when we're talking about big company They are company they have another job like her bus and they have to manage platform is really Is really is really important when you're thinking DevOps, you know, it's this loop is really cool. You could put any many technology on it But for me DevOps is production It's security to go in production each time I have the same question how you manage the difference with non-prod and prod how you use and you Authentify yourself when you're going in prod Which is the master we we which is Which is the team which team has the key of the DevOps tooling? This is really really really important I have a coat of oh Okay, I just stop I think I see something strange. Okay. No, it's okay I would like to to share with you a coat of the day. You say, okay, it's weird We're not we're not gonna we're gonna talk about love today With Guillaume Musso. It's a French whiter. Okay, you could take just one minute to to read this one It's about love and it's it's really beautiful, you know, and I like this one love is like fire on a rainy day You've got to spend all your all your time protecting it feeding it tending it because if you don't it if you if you don't it goes out, okay, you say, okay, but What is the link with today just replace? Love by pock proof of concept It's exactly what is it? Pluck pock is like love is wonderful Okay, everything. It's about pock. You have everything but in the real life No, what last in the pain that come after pock? Just look at you have to feed your pock You have to to take to take care of it and you you know after you pock Is gonna be a nightmare, you know, everything. It's okay. The client is happy. You have a pock Everything. It's okay. The best people just say, okay, we deliver the pock. We could go in another project No, no, you you don't get it. You have to stay And we're gonna run it together if you're not ready to run with me at 4 a.m. On Saturday morning This is not a project this you just playing a game with your computer and it's cool, but if you would like to go Further you really need to need to to to thinking about that With in 15 years. I saw many projects fail particularly in open source. I think open stack is the good example Because I saw many many open stack project failed that why first Let's do it myself from scratch Everything is the same You have a guy's he's clever. It's smart. It's the best guy you have he would like to do from scratch You know, he would like to do it to take the code to go upstream and that city deploy it He is he is or she by the way as the only guys in the world could do or rebuild what is done You know no reverse engineering here only one engineer do that does that you know or did that? Secondly, oh, it's open source. Let's do cheap Okay, we're gonna save money. We're gonna go directly We're gonna go build a pork and we're gonna do that really lean lean management meaning Okay, I'm gonna give you less money than I gave to Microsoft before that's my plan and After that, okay guys, we have a pork. We don't have any more any skill set about how managing the pork Let's move this pork in production Okay, you have a pork with no money only one guys did it and you're gonna go in production After that when you you it's it's real life example. I Have it's in any big company. It's always when you talk about people. Yeah, but about oh How are you gonna manage it in run or how you're gonna move even on the build to move to the product to the pork to prod People say oh people will learn by themselves if you're gonna go Kubernetes you go Kubernetes.io. It's okay. If you have all the documentation Let's take the guys you say you have three weeks to to train them and you go online And that's it and you're gonna have expert after three weeks of learning online, you know and or you say okay Let's go certify them Online it's gonna is gonna be okay Another things I saw and I saw really it's no documentation and I don't know how many of you really document what with what they do every day, you know Really it's it's about and particularly when you are in the park you're running on time You have a constraint Sometimes they are consultant come only for the park and they are they stay only one week and you have to deal that And most of them they really forgot The N1 support the guys is gonna is gonna talk the call at the first line That's exactly what is 24 seven. It's you have a guy he like fishing during the weekend he likes doing any many things in his in his or her life and His job is only his job. Okay, but he is the one Every weekend Ramp up if they have any issue and you have to manage your documentation You have to manage your process for him or her not for the high-level guys Not for the claimers or smarter could go anywhere can do anything That's a big difference you have in open source community Compared to a big company in open source community. You have all of all the people are smart You know how we are smart or look at my demo look at myself Okay, but in the big company we can't pay only smart people You know and all many of you like documentation and all many of you are okay to do 24 seven front of his support Okay, after you finish your book, how many of you are ready to say, okay, this my job I'm gonna get this in production. I'm sure because I'm good guys. I do I Did my job well is now most of them they just finish That was exciting and they're gonna go in a new technology in a new area. Let's do let's do Yeah, yeah, yeah, let's do another thing. That's why to finish on this First you build a pack not a stack. We really don't care about Technology because this is not open source is not about technology It's about the capabilities to change and to improve your technology you build a pack a really big pack and And why because what you would like to do it's to have a team ready Ready to attack ready to manage a project first. I never go in in a company in big company without an editor Red arts it could be pivotal. It could be any Jeff frog. It could be first Builds work with an editor a ball a be sure you have the good subscription And you're gonna be supported by the editor is not your job to upgrade Linux It's not your job to upgrade Artifact to read to be sure you don't have backdoor. I just have a question before about how we manage docker Security no is gonna be managed by itself. No, no docker No thing docker is not managing security at all. It's your process. It's the tooling you had today If this is this is one of the big weakness of Docker, it's you have trouble to manage it in production But if you're working with for example open-shift with red art or with build park or source to image You could have a support from red art to to hardening you you docker images You never go, please on docker hub and put it in production never, okay? Docker hub it's only to to to play with your laptop you have contribution back I have five million contribution back isn't is really hard for big company Not only about the legal and the process. It's all also because most of the time you just integrates You just have a configuration in your work on the technology. You're not gonna contribute You have people for example, they could contribute because they're Their activity or Twitter or Facebook, but when you are Airbus, it's really hard because your main goal is to build plane It's not to build software if you go and defense in space one of the area of Airbus They are an editor and they manage software. They could contribute But most of the big part of Airbus for example, then they're not gonna contribute You understand about my pocket to production Really important train you people Don't think they're gonna learn by themselves. It's for its force The reality is you have to put them in a real training session Like a long Institute for example, you could go if you go with an editor is that's really help you You're gonna have to official training from an editor also put expert on the table Expert they're gonna help if they're gonna accelerate the process documentation obviously and thinking only about 24-7 if you have 24-7 support in your mind, you're gonna see it's gonna be really easy I'm I'm finished with this slide and You have also to help yourself and your team one of the big part I'm talking particularly about infrastructure the big part of DevOps when I was director of DevOps 7 today We now when I help my client it's to onboard people and to onboard project, but you know I remember first my own co-activity was in in a cleaner infrastructure side now I have to onboard people on the DevOps pipeline. I created I think after that we're gonna have a talk about DevOps pipeline You create you devote private is great now. You have to onboard them You have to have someone give some advice is technical Assessment just to say okay. You have to do that. I'm gonna create you get lab You're gonna create a Jenkins and after everything is gonna run and I'm gonna document that and and after I'm gonna support Your company is really important because you understand about with a pack human Advices come first you have technology behind technology It's 100% automated, but you need advices you need a frontline of people not rocket science people Just take care about your clients and take care about the project. I Would like to share this picture because as I said I'm a big mostly fan and I was looking because the last Last year I was in Seattle in on his grave and I take this picture. I just realized this day He died before I was born and He died younger than me now But anyway, he's influence. It's a big particularly in martial heart. Thank you Okay, we have plenty of time for questions. I'm a bit of luck the bouncy Michael turn itself on the filmers of time No, Bancy Mike. Hang on Gonna work this time. All right set deliberate Okay, so I I work in a similar field. I also try to help companies see see the light with DevOps But the way I I've been in two types of projects, right? One is where DevOps is comes in as as as a mega project, right? with their team of consultants and everything gets to get transform training everything full package and leave and Another type of project where DevOps is is is done gradually in a in a step-by-step What dealing with specific problems that they face immediately and showing them a tool that solves their major problem let them see that That this works and builds up confidence And then go on to the next phase But they the problem with the second with this way of doing it is that it becomes very very organic, right? They're not using for most part best practices. It works, but it may but it's not big best practices the first one Best practices, but then is often not sustainable So I'm wondering where if you approach it in these two ways and how you found the balance It's it's really a What I think my feeling is and how we do that just to explain in when I was in my life I have I had two team one team was a platform team. They're working really on the engineering stuff They were internal team and I only had seven people there There must they were my smart guys, you know and and on this side I build by platform Kubernetes, but also pipeline and The big part of my company my team after that 30 people were only delivery people and their focus is really Apply and try to apply the best practice And welcome the project to see onboarding them and try to apply and to work with them, but he's really Is really easy when you're talking about containers when you're talking about micro services for example in my previous company We work it on on on Pivotal code foundry for everything net new and on Kubernetes to move the legacy On some on container is a legacy, but I say one is when is net new is more a culture I change a new way of working particularly for the developers when it's legacy It's sometimes it's about technical issue or so. That's why it's the only solution I had it's build DevOps pipeline first standardized the way you are implementing and you connect the tools together and after well just on board the project and you don't have one in fact one recipe you have recipes and and and you try to to help them to converge on the same on the same way to to to work with DevOps, but I had an example about IIx technology created in the 90s and we we deploy it with with DevOps tooling githlab Jenkins and Archifactory, but we deploy deployed it. It's really on the simplest way you could Is not we the idea is we don't we don't want to challenge the people We don't want to automate But when you go on the net new like micro services No, you have to as you say you have to go fast and you have to move and to give them quickly A good solution by the way guys from legacy they used to wait You know When you work with startup they would like to go fast But people from legacy they used to wait and they know what's If you're talking about a six-month project, they're not gonna be scared If you say that to a Small company, they're gonna be scared, but Many thanks round of applause, please