 Awesome. Well, thank you to to Greg and Molly for having me into the Cloud Foundry Foundation for the opportunity and Nithya as well. Nithya Ruff who if you were at the Keynotes yesterday Was also teed this talk up as well. My name is Chris Power. I've been at Comcast about about four years. I Work on the the cloud team. I'll talk a little bit about that I wanted to spend a little time today to talk about open source In the in the cloud era if you will and give you a bit of perspective from from where I sit on the cloud side of things In terms of how we sort of see open source and how we see teams consuming open source Talk a little bit about some of the challenges that I think we're seeing in in the open source space today And and how that's reflected in the cloud So as I said, my name is Chris power. I'm a cloud protect at Comcast I lead what we call the cloud center of excellence Where we partner with a number of teams across the organization Not just Greg's but but our security organization data center engineering and networking And a number of other SRE and tooling teams as well to try to be an enabling function for the organization as they transform from You know this predominantly data center centric environment into a very cloud-focused environment We'll talk a little bit about some of the cloud stuff that we've done But I think we'll largely stay focused on some of the open open source bits Yeah, so that's a Sort of what I do today historically at Comcast. I built solutions in our open stack environments and our and our AWS environments as well So I guess about eight or nine years ago, there was a somebody made the statement I think it was Mark and Dreyason That software is eating the world and and it had probably had been for some time But I think more recently some folks have come out and said open source is eating software Which I think is largely the case right if you take a look at the Historical software models that were largely built around closed source proprietary solutions and with the advent of open source 2030 even 40 years ago You've seen that cannibalized that market space where Developers groups of developers commercial Software providers as well have gotten on this bandwagon where they've built open source that Essentially at least rival if not rivals in some places displaces in some cases displaces some of their commercial solutions but I think what we're seeing today is The the possibility that is is cloud now eating open source And I think if you're if you're familiar with the space and you use any of the the sort of public cloud vendors that are out There today, you'll see that what what I think is Happening is there's a strong demand to consume deploy and run open source by enterprises middle Sort of middle market companies and even and of course startups as well But a lot of the times that's not necessarily their core business, right? They're focused on building products and features and this is true for us at Comcast and a lot of cases And so what they want is to be able to potentially consume those open source products in some way So those projects make them make their way into into the cloud market space and we see these cloud vendors Running open-source software because there's a demand in the marketplace for us for it And it's it's causing I think some interesting challenges that we'll talk a little bit about Give you a sense of the of the public cloud market space It's growing as as I think is no surprise to anyone AWS obviously dominates the space with somewhere between 31 and 34 percent depending on who you talk to this I think was from canalis and then Azure is growing Incredibly rapidly in GCP as well now as they've brought on some some folks over from Oracle to run the the cloud business there What I think you see there on the right is is actually endemic of the industry, but also true at Comcast as well 84% of enterprises have a multi-cloud strategy. So either some form of multiple public clouds or multiple private clouds We have both And I think it's 58% are actually consuming hybrid cloud in some way meaning they run something on-premise and they're running something in the cloud So a lot of these open-source solutions are really good to do both of those things But in some cases People that are moving to the public cloud are looking to consume these services as I said as as services not as Not as deployments of those things And I think the the market's just gonna gonna continue to grow gardeners looking at almost 18 17% growth in 2019 across the worldwide public cloud services footprint So I think this is gonna continue to just Expand and we see that playing out at Comcast as well But open source is critical to the way these cloud vendors behave and perform if it wasn't for open source I don't think very many of them would exist in the way they do today It started with Linux right the tip of the red hats and the canonicals of the world and other distributions But it includes things like Zen and KVM as the hypervisors for all of the virtual machines that you'll find out there running on these various cloud providers solutions But if you look further you'll find open source strewn throughout the various things Various services that they offer so elastic search Hadoop MySQL Postgres Things like Kafka TensorFlow Kubernetes you name it It's probably being offered as a service in one form or another on one of these clouds and all of these cloud vendors have very different approaches to the way that they're partnering with Or a plot or bringing open source to market So you if you look at Google they've taken what most considered to be a sort of open source first Approach by trying to put Kubernetes out in the market and things like that you look at Microsoft They become one of the biggest open source contributors out there and with the Acquisition of github certainly are firmly entrenched in that space and then you look at Amazon who delivers a majority of these open source products as services and recently in the last couple of years has also become a big open source contributor Arguably maybe forcibly so but certainly have have turned and started to play in that that market as well What this is doing of course is creating some interesting challenges in the space for open source especially for What people traditionally refer to as these commercially? Commercial open source software models where you've got an open source project That's being delivered commercially, and there's some interesting business pieces at play there Clearly though the open source space is attracting a ton of investment Just from 2010 to 2015 eight and a half times growth You see a tremendous amount of investment in the CNCF Ecosystems I think Kubernetes I think Prometheus Istio envoy etc. Blockchain obviously is a huge investment space Front-end no JS is one and and some of the stuff that that you'll find over on the networking side as well So clearly there's a lot of money pouring into open source Both from a venture capital perspective But also from an investment on the on the cloud provider side, and this is further reflected just last year alone this was I think through The middle to end of 20 about the full-time framework of 2018 $65 billion pouring into into their versus in M&A IPOs and acquisitions it started with Red Hat acquiring co-ress in January And moved all the way through the end of the year with elastic having right think was about a five billion dollar IPO In the middle there you've got Pivot obviously IPO'd you've got sales forces acquisition of mule soft one of the bigger ones That we've seen Microsoft's acquisition as we said of GitHub, but I think though you're seeing here is that There's clearly a tremendous amount of value in these open-source products both from a commercial perspective But also from a consumption perspective. I I think at Comcast if I were to survey the footprint We probably would find 95 to 99% of the technologies listed here in use in some way shape or form many of which we're commercially engaged with but at the very least more than likely not you'll find it in some open-source form as well We run our own internal GitHub enterprise for example have had great success with that as well as some of the other things here But what we've also seen are lots of huge acquisitions and consolidations So if you think about the the big data space we saw Claude era and Hortonworks merged this year effectively They had slightly different open-source models Hortonworks was sort of more open open source Whereas Clutter was partially closed, but they were both built on top of the Hadoop ecosystem You saw the same thing with in the Kubernetes space right VM. We're acquiring Heptio for example But the three biggest acquisitions totaling some fifth almost 50 billion dollars this year We're obviously the Salesforce mule soft Microsoft GitHub and more recently Red Hat acquiring IBM and I think That makes 2018 the biggest year in open-source in terms of acquisition In the last 20 years if I were to say so I think three of the top 10 software acquisitions In the for 2018 in the past 10 years were were open-source and occurred in 2018 So clearly a lot of a lot of space here and a lot of integrations And a developer efficiency that have been born out of this. It's interesting to see where some of these will go I think the Microsoft acquiring GitHub one is is certainly cause some Consternation in the in the industry. I personally think it will end up being a good thing But I think time will tell and the same thing probably for Red Hat as well So let's talk a little bit about some of the current business models and what we and some of the newer ones that we see here I this is not an exhaustive list. I sort of in researching some of this stuff for this talk came across lots of different Top five business model lists and things like that, but I think this sums up the majority of them You've got the the subsidy angle so corporate subsidies Personal subsidies meeting you're an open-source developer. You're writing code on your own and contributing that we have corporations that of course Pay people to build open-source. We do that as well. You've got donations based models corporate patronage grants And then the more traditional models right so support and services the red hat model if you will distributions like You know red hat and and you know pivotal and things like that and then they hosted or software as a service models that we've been talking about Where someone will take open-source and and then run that and make that available Or they'll have a closed-source model and make that available as well an example of that might be something like data bricks, for example Which is a spark based vendor and then the licensing models, which is where things I think Get fairly complicated. So you've got open core You've got the enterprise features that get layered in on top of that and confluent is a really good example of one of those What would traditionally be known as a commercial open-source? Software vendor. There's a good list out there if you google around for I think the top 100 open-source commercially commercial open-source vendors by the open-source Software capital or group they keep a public Google doc of that which was really interesting to take a look at but we're seeing is this some new Business models come into this space here And what I think is really interesting is that you see this reflected in other industries as well So tide lift isn't is an example of one of these. It's a subscription based model where you pay a subscription and your Subscription goes to fund the creators of the of the software And and where else have we seen this right? So if you think about the social media space think about YouTube You've got maybe a hundred channels that have a million or more followers out there And those folks have this tremendous amount of inertia behind them and they're doing great for the most part And then you've got this huge long tail of channels with very small following But people are grinding it out there every day to build content some pretty amazing content and the same is true for open source Right, so what have what has the social media space turned to things like patreon subscription based? Hey, you pay you get extra content access to content ahead of time Ability to meet the creators things like that And I think we're seeing solutions like tide lift and other things that are sort of their donation or subscription based mirroring that same thing here, which is this crowd-funded Creator creation based economy really driving the limits of what we think of as business models So I wanted to focus just for a minute on the on the open core model because That's I think really the foundation for a lot of what we're seeing today So just maybe explain what what it is and this was sort of New to me and as a definition, but I think it's it's probably familiar if you've if you've looked at the space at all Right, so pulled this from Wikipedia But it's a business model that that helps support the monetization of commercially produced software so typically there's a core open-source project somewhere and then packaged around that is some number of layers of either Open or source available code or closed source proprietary Third-party code right and or some mix of that with some licensing in the mix and it gets fairly complicated And we'll talk about a couple of examples, but generally speaking This is is the core definition of it and most commercial open-source software companies are using some form of this model today And and I think most have been largely successful, right? We just went through the 65 billion odd dollars of money that's flowed into that space in the last sort of 12 months and many of those are traditional commercial open-source software companies But what but what we're seeing is that as the cloud vendors come into the space and start delivering these solutions as services They're challenging the business models of these commercial open-source companies Directly, so what we're then seeing is we're seeing new licenses come into play licenses that are Shocking some complicating other that the space I think the first foray in this space was Commons Clause Which was intended to take open-source and make it essentially Protective against the cloud vendors from deploying their software as services In a commercial sense to try to create space for these commercial vendors who support the open-source projects mostly directly Right to to be able to make some money because at the end of the day open-source is is not free Somebody is paying for it somehow whether through time or money some notable examples in 2018 where Mongo DB Redis elastic Confluent as we mentioned what we saw was we saw reactions from these companies to the open-source vendors Either Historically running services like elastic search for example or more recently Kafka for example as a service and reactions to that in the form of These vendors going and changing their commercial licenses to expressly prohibit in most cases the The the offering of their of these open-source projects as services via the the cloud And they're doing this in a protective sense whether this is going to to sort of work or not is a good question I think this presents a lot of challenges for the space There's been a tremendous amount of pushback from the open-source community as they've introduced these new licenses Understandably because generally speaking they're not open source open source is not just here's the code open sources Here's the code and here's rules around how you can distribute the code and that's where these licenses really change the game They add complexity they make it complicated for enterprises like Comcast to figure out how to go about Packaging that software and delivering it in most cases these licenses are not targeting You and I in that form But the question then is do they actually solve the problem because common clause has been in effect for a while and other Sort of AGPL and other types of licenses have been in fact for a long time and these vendors are still out there doing this these cloud vendors But they're reacting to to a to market demand right the the vendor see a demand in the market and they run this These open-source projects as a result of that So the question then are is are they enforceable and I think we've yet to we've yet to really see that And then it makes it typically harder. I think to combine these models These open-source hybrid models with other open-source projects because then you get in these overlapping license situations Which I think for especially for large organizations like ourselves complicates things quite quite a bit So Gonna talk about I think a couple of specific examples just to really Look at this in a concrete fashion because this was helpful for me to really understand this So confluent and elastic will just maybe touch on those from a commercial perspective confluent offers a You know is built around is an open-core project, right? It's built around an open-source distribution Apache Kafka license under Apache 2.0 They offer it as a platform you can download in the upper right there as well as via confluent cloud Which is essentially a managed service that they provide which so happens to run on most of the public cloud vendor solutions But what we saw recently, I think towards the end of last year was the release of managed Kafka in Amazon as an example And and confluent reacting to that with the introduction of the confluent community license Which is this tweener license that sits in between traditional open-source Apache 2.0 Kafka and the confluent enterprise license which provides some enterprise-grade features which is a commonly sort of accepted model I'm you know, it's one that that pivotal uses. It's one that read, you know, other distributions use With the injection of this in between that covers some of their I'm gonna call them value-added proprietary features Things like their case equal the schema registry, which is super important in stream data platforms and Essentially all this license does is expressly prohibit the use of the of these features for By cloud vendors when offering a managed streaming platform, right? So they are very much. This is very much targeted at that specific Attack vector if you will But it certainly complicates things some of these vendors actually Provide this middle tier of source code as source available as part of their distributions and others do not So a lot of the times when you pull this down You may get both the piece on the left and the piece in the middle or not and some of that stuff And that makes it I think complicated for us when we're trying to figure out. How do we consume this and how do we legally? Deploy these the software within our organizations and the honestly the same can be largely said of elastic search They finally decided that they would take their x-pack, which was their sort of proprietary feature Around that they delivered on top of the elastic core And actually roll that into their open source distribution as code available features that are free generally speaking outside of their specific Enterprise features and so they have a similar model their code is actually open code available in there So it does make it a bit complicated and then what we saw as a direct result of Sort of some of these things was we saw Amazon then saying okay Well, you know, we're going to release what we call open distro for elastic search Which is essentially a fork of the elastic search code base that they then partnered with I believe Expedia and Netflix to start distributing which essentially offers under Apache 2.0 license all Of the features that are covered by the by that tweener elastic License that that essentially says you can't use these features as a cloud vendor to deploy these things That stuff has been developed majority of it at least and then pushed out through Apache 2.0 via the The open distro for elastic search, so we've clearly got a clashing of business models and licensing here that I think This was just March 11th, so we're talking less than a few weeks ago, right? So this is really early stage not sure where this is going to play out But I think it's really interesting to see these two things and it's unfortunate in some respects because now we've got essentially forked Repositories and this is what I think is is the challenge with some of these hybrid license models So what can we do I think Abby said it yesterday engage more in open source engage in the community, right? code bug fixes documentation feedback issues Community engagement in the form of all of us sitting here today supporting our foundations Meetups going to conferences and financial support right as supporters of foundations or as Organizations that are paying developers to build code There's a myriad ways that we can as a community can can help move this forward. It won't necessarily solve this murky hybrid license problem but the more that we're engaged and understand and our our Intelligent consumers of open source the more we can be involved in the debate and work with the cloud vendors and work with the open Source distributions and work with the commercial open source solutions To really to get to a some sort of tenable situation because ultimately what we're trying to foster here is a sustainable Technology space where people can make money off of software And businesses can run and build amazing products and and today that's a lot a lot of that is based on open source So just to talk a little bit about what we're doing at Comcast for a few minutes I don't think we have the answers or all of the solutions and we certainly could be doing more But I think we are doing a lot as Nithya mentioned yesterday at the keynotes and just wanted to cover that a little bit So for the benefit of the folks in the room Comcast is a bunch of different brands. So Xfinity is one that folks are well-known. That's TV internet home security mobile now and voice traditional landline and We are also own NBC and Universal Studios. So brands like CNBC NBC all of those film and television networks Telemundo Fandango, I believe as well and the Universal Studios Studios as well as the theme parks and as of I guess it was maybe six months ago. We also Sky is also part of our Corporate umbrella if you will so that would be the equivalent of Comcast and the cable pieces in in the UK as well So what you'll find though is you'll find the use of cloud as well as the use of open source throughout All of these brands as as is probably no surprise. So let's talk just a quick minute about our open source journey because I think It is it is sort of emblematic of our commitment to to the space Go all the way back to 2006 we started consuming open source, which is I think where most people start And that's natural at some point a few years later We decided to start contributing and they the contributions came out slowly Little bits here and there where we were using things. We got involved with the Apache Software Foundation in 2011 And we started launching open source projects on the public github comm under the Comcast Organization in 2012 so if you go there today, and we'll talk a little bit about that you'll find quite a few projects We've been supporters of other various foundations that we'll talk about I think really the the the sort of watershed moment for the organization has really come in the last two or three years with the With the advent of our open-source practice office Who I see Nithya is the head of is sitting in the audience here today As well as an amazing team of people a number of which I see also in the room Who really are a center of excellence and a knowledge base that we as a large engineering organization can go and speak to and Understand what are the right open-source licenses and practices that we should be looking at And they work with various parts of the organization and foundations and our legal group to really Enable us as an engineering organization to build products and be really thoughtful about how we do that with respect to open source And then I think You know most recently we've gotten involved in the cloud native commuting foundation We've been involved in the cloud foundry foundation for as well and open stack has also been an area where we've been significant contributors in the past So specifically from a community engagement perspective, we're involved kind of across the board and lots of things This was just some highlights. I've personally been involved in the stuff on the left Specifically open stack and cloud native computing foundation You will find deployments of all of the software here within Comcast in various forms as well as contributions coming from Comcast Comcasters Some of which are done as part of their normal course of business some of which are done through our open-source fellowship program where we're Actually sponsoring people to spend time Contributing back in addition. We're strong supporters financially of these open-source foundations specifically A lot of the ones that you that you see here. I'm most familiar with sort of with the ones on the left there Where we're engaged at kind of a number of different levels So I think there's a there's a really strong commitment from from our organization to try to be involved to be out there Be talking to people hearing challenges and trying to deliver You know our challenges and and some of our needs back into this these organizations If you're interested in seeing some of the projects you can head over to Comcasts.github.io I just highlighted and picked a few of the the most recent contributions that we've made these are projects that we've open-sourced ourselves And and have gotten I think quite a bit of traction the canonical example for us is Apache traffic control Down on the bottom left there, which is a traffic server for our content delivery network And that's been something we've open-sourced and has been open-sourced for some number of years now more recently though in the last 12 months the top three there so Trickster, which is a Open-sourced project that plays in the CNCF space quite a bit It's a front-end cache for Prometheus. So if you've ever used Prometheus, which is a metrics solution It can it's generally a good performer But where it starts to slow down sometimes is from a from a query perspective And so Trickster is sort of a cache that can sit in front of that as well as sit in front of other back-ends also That was something internally developed and open-sourced Cooper healthy is another one which is a health checking system for Kubernetes and vinyl DNS is one of our internal DNS management solutions So these are all projects that we have built and then there's of course contributions that we're making to Kubernetes and other solutions ourselves as well So lastly, you know, where are we going from here, right? What's the future of open-sourced and these business models? I don't have all the answers I sought to sort of hopefully educate everybody today and myself selfishly as well through this process I think the the the flow of money into the open-source space is driving a tremendous amount of change and the demand from the market the demand from organizations like Comcast right to To consume open-source either directly and run it ourselves or via cloud providers Which we do a lot of ourselves as well and that's forcing the models and the licenses that have worked over the last sort of 25 years You know to change in the future. So, you know, how where is it going to go? How do we predict that I don't I don't know that I have all the answers but hopefully you walk away with understanding a bit more about the space and And and as certainly I did as well. Thanks. I saw you first a friendly This was not play it's in question So from a monetization standpoint sure so as we go forward, how much do you see it? the trend or at least the model where it's Microchanges or necessarily paying individual contributors as opposed to company sponsorship in ways Do you almost like a gig economy kind of thing? Do you think that's going to become more prevalent as we go forward that there's more individual contributors who are on a Pay-to-submit kind of basis Yeah, I think we've seen that and and I think solutions like tide lift are probably a way to sort of like scale up that model a little bit We see this a lot with some of these open-source projects that are kind of in the middle of the space I think where you have the potentially the creators form a You know a little a little consulting shop right around that open-source project and are willing to do specific feature development for Paying customers right well that where there can fundamentally alter the roadmap if they believe it It's sort of the right place and I think that's an area where where we can see some expanded expansion in the future Yeah, as you look at these platforms at Comcast You know you're gonna use these for some pretty big scale and you start to put some chips on a platform With the different licensing models of open-source and their support and you know add-on features etc How do you make a decision on your team if you're gonna pay for that support? Or if you think you can support it yourself internally or use a partner How do you figure out that cost side for a podcast? Yeah, that's a really good question I think the financial model here right how to how to support this is is a complex one We I think generally use a fairly distributed decision-making model on the whole Meaning it's up to most of the engineering teams largely to decide what's best for them and how to fun And make the business case to pay for these things I think what we see is that a lot of our teams elect to Contribute in some way to the support models For some of these open-source projects either because they're looking for support in a material way and want to have a backstop for themselves or because they're looking for the Some additional enterprise features and that might drive them down that path as well But I myself have certainly run a number of open-source products Directly myself and supported them I think on the whole that makes sense at some some of the small to medium scales as things become more critical to the enterprise we often look at least initially to To the vendors in the space to help but as we develop centers of excellence around these things cloud founders a great example of that We have a tremendous team and a huge community of engineers that derive a tremendous amount of benefit from that We can sort of bring some of that expertise and develop some of that expertise in house Which enables us to you know be a little bit more flexible with choosing whether or not to consume that But I think we have probably both of those scenarios Yeah Hello, just I saw your timeline. It was pretty extensive History of using open-source. Can you share? What successes or challenges you faced in maintaining executive Support throughout that time period because what we see is that you know, you get a ball rolling maybe a leadership changes and Projects are abandoned and support for them both externally and internally So how did you maintain the support over that period of time? Yeah, that's a good question Probably a longer answer, but I'll give you the sort of my perspective as a consumer and contributor internally We've got sort of this inner-source model that we support and as well. We've Contributed externally as well. I think Generally speaking the leadership from day one has been supportive obviously that that ebbs and flows and we're so we're fortunate in that respect I think and And and to the extent that we put our money where our mouth is mouths are if you will And the creation of this open-source practice office That's really helped to create a sustainable I guess model if you will internally for for the ad not only advocating for open-source, but making it Easy to have a well paved road to both consume open-source, but also contribute I think historically where we saw a lot of challenge was it was it was very unclear how to go about contributing And and many people didn't spend too much time understanding how to consume and as a result though in the last three or four years I think we've seen a much much more sustainable model Built around that because of this knowledge in the space Yeah, it's actually all the time we have for questions. I'm sure you take some afterwards. Yeah grab Chris after thank you Thank you