 Okay, I think we're about a minute after so They'll be respectful of your time and get started here so thank you everybody for sticking around not to quite the bitter end, but for a lifetime at any rate Tell you a little bit about me Gordon half on cloud evangelist at red hat which is sort of a fancy way of saying that I do all kinds of different stuff related to Cloud and pretty much everything that touches cloud at red hat which is pretty much everything Some various contact information for me there I have a blog and I Google plus and Twitter and so forth a bit red have about three years and Before that I was an industry analyst for a long time covering server clustering Virtualization cloud all that kind of stuff and then before that I was at data general for many years I did some of the early numa unit servers there and so forth Um, I do have a new book out. So people ask good questions I've got some copies up here and for those I don't have enough to go around But if anybody else wants to give me your business card, I'll be happy to send you a free Blackcrow copy. I do believe these slides are going to be made available by a Linux foundation But in any case I can I can mail them to you I'm not going to spend as much time on the first part of this talk as I as I probably would with a different Audience, but I think just to make sure we're all in the same page and really kind of as a segue into the rest of this talk Um, I do want to spend a few minutes talking about and having us think about Kind of how we got to where we are with open source and and really sort of the What we're really doing with open source because Because that's essential to talking about some of the other things I'm going to be talking about in the rest of this talk and by the way This I want would like this be very interactive. So if I've said something that Disagree with or that you really feel an urge to comment on or ask a quest about feel free to interrupt me. I Retain the right to I suggest taking it offline and more detail later, but very happy to make this erect So you're kind of storing back with BSD You know that is people know I probably everyone in this room knows Rose it Berkeley Wasn't many ways something that was somewhat Pragmatically done by Bill Joy and others but nevertheless it certainly had a connection to free speech movement at Berkeley and this is a quote from John Gay to Layer go on to have career at Sun Microsystems and Basically, he says the open source movement is a free speech movement So it was really very much tied up from the beginning with something that went beyond just looking at source code Chris probably better known today is What went on later at the free software foundation where Richard Stallman? I think in a sense may be codified and went beyond Some of the early initial open source efforts would sort of happened With this connection to free speech, but without not necessarily a whole lot of Kind of philosophical thinking about kind of a framework for what that connection would look like and as good as Everybody in this room. I'm sure knows this idea of Free of this being a matter of freedom not free beer No charge that kind of thing However, I think we well we have in many cases. I think probably somewhat to the annoyance of some Probably beyond annoyance in the case of free software foundation have tended to equate this idea of software freedom with open source and Kind of kind of set those two are kind of sort of the same thing and I Think it's understandable because if you kind of look at the history of and this is primarily the history From kind of the originally the unit side of things There the open source was a very useful vehicle for providing many of those freedoms Early unit source code was widely shared picture in the right there is is Kind of a later in a later sort of the official version of this sharing in terms of lion's commentary and you Nick Many of you are probably familiar with The other thing was that sharing source code was something that was practical I mean, you know, maybe the wide world as whole didn't really know much about FTP or email or any of those kind of things, but they existed in the academic environments at which this sharing was happening then finally You had all this incompatible Hardware and units was written as a portable operating system and see originally rather an innovation in that regard But you had all these different hardware Architectures, so this portable operating system nonetheless had to be tweet and recompile Relate whatever for each of these different hardware platform so having the source code be open was Useful practical thing in order to have this freedom to run software across all these different platforms but now we have the cloud and At some level this doesn't all necessarily carry over to the cloud I am going to talk a little bit about licenses in the context of cloud Frankly, there have been sessions here that you've gone into a little more detail on that particular topic and I'm not a lawyer and Just a little time there But I'm really going to focus on what some of the other aspects of openness that are very relevant in a cloud computing context Couple of caveats here and covering a fair amount of ground not going to a huge amount of depth in a single topic My idea here is really more to give you perhaps some things to think about also, I'm Deliberately sort of focusing Here on things that touch cloud computing in a relatively Narrow sense and there are other aspects of openness such as open access to Scientific journals and so forth think are also important things to think about as society as we move forward But I don't really address those particular points here Well, first of all, I guess very briefly about kind of distribution the licensing sort of thing. There was actually a very good panel here Earlier this morning about talking about the AGPL v3. How many here are familiar with the APL AGPL? Okay, you of you So basically this is a variant on the GPL v3 licensed GPL The two of course being you being used for Linux and many other things in GPL v3 being used for Number of newer projects AGPL v3 was released at the same time as the GPL and essentially you know the way to copy left provisions of the GPL work is They kick in when you actually distribute the code and that that distribution is defined in essentially a fairly traditional UNIX kind of way having to do with With linking essentially That doesn't apply if you're delivering software over the network and number of people kind of saw this as a Bug essentially or certainly a limitation in that license. So the AGPL V3 came out It hasn't been widely accepted. And in fact, you know, there was a fairly Lively discussion at panel earlier that to a degree it's been used. It's been used predominantly and What might be called nefarious ways essentially as a way to really force an upsell To a proprietary license in a dual licensing kind of a model In any case it really has not taken off And in fact, if we look at kind of web services community, if you would Way modern applications are written up the way things a lot of service providers are working in There's really been a general trend towards permissive licensing This is from a blog post that Donnie Burke holds with red monk did Did recently they kind of shows it in a language by language basis which is sort of interesting its own right I think Donnie's floating around the conference somewhere. You want to talk about this in more detail? And again, I'm not going to spend a lot of time in this but I just I think I just kind of observed that this has probably come about in large my theory is or one of my theories is that open source has been a very successful development model and having permissive licensing Makes it easier for different entities, particularly commercial entities to collaborate with each other Whereas I copy left at some level represents that this are belief that that That the essentially the opens open source needs to be protected in that you kind of need to force people to contribute And I'm sure many folks in this conference would probably object to that exact characterization But nonetheless, I would argue permissive licensing has come about in part because it essentially emphasizes collaboration over Protecting open source from nefarious use Well, I think is one of the more important aspects of openness that we really need to think about in a cloud computing context So not just cloud but it's in cloud among other things is really around the idea of community and you know, I mean There's at one level open source project an open source project That doesn't have a community doesn't have that you know type isn't widely used and contributed to Isn't really that useful yet today, and you really do need to Develop those communities and of course Linux has been hugely successful in this This is some of the Linux foundation numbers from last year I'm not I don't think I've seen their numbers this year yet, but get lots of different people contributing Over time and I think that's very clearly been one of great successes of Linux It's you know, really everyone here knows That there has it really has been this wonderful development model for an operating system Now, you know, let's go forward to the cloud world Open stack of Grizzly as the current version Big open stack design summit Go it's been going on up in Portland, Oregon this week I'd actually be up there if I worked out here and again a Lot of contributions and in fact For those of you may not know open stack is essentially an infrastructure as a service So the idea is that you can stand up essentially a service provider on your own premise Stable service provider like rack space on your own premise and it's really been interesting if you look dynamic of how this cloud computing space has been developing because the I think a lot of folks are really looking open stack right now as sort of The presumptive winner in this space that I use the air quotes because I really try to avoid Getting into kind of this race horse mentality of the trade press. I don't think it's that simple But in any case certainly open stack has gone from being nothing to being widely hailed as a very successful cloud computing project and One of there's one reason for that and that is the strength of the open stack community but again my point here is that I Think increasingly we need to think less about licensing and more about the community associated with the project and I think what makes a community successful and again, I think there have been Community talks at least one community talk here by people who are far more involved in details here than I am But a lot of interacting things matter and in fact I talked to a number of our community people I've done a couple of Podcasts with some of our open shift community folks over the last month or two and you know one of the things that you know One of the things that strikes me is that you figure company like red hat has been doing this for you know forever Would you know have this process that we follow you You probably do step A step B step C so forth poof you have a community You have a mod a governance model and so forth, but in reality it's a lot more complicated than that and You have a lot of different things that essentially interact with each other and creating community Go through a few of these a little more detail We have a group at red hat called OSAS open source and standards and I cribbed this from from one of our webpages here that they got a look in their veins serve three different fundamental community models and You know lots of variants within this but kind of from a high level and the top level is Nothing dies here The top level is the first one to serve a wall guard, you know, this is the idea that a company has an open-source project But it's under an open-source license, but only their employees get to be committers It's you know, this is very much driven, you know almost as a traditional software project What do we need to do for our customers? And certainly one of the concerns here is what happens if the ownership changes Not to mention, you know any companies by name, but one might begin with ass the other might go We just caused some issues, but you know in general, you know, you can argue. Yeah This is sort of open source and ladder, but maybe not in spirit The second which I think one could imagine I think probably everybody here can imagine a particular Project that very much lines with sort of the benevolent dictator model And you know, I suppose that might be a little bit of a loaded term But it's certainly not meant to be a negative in fact, you know I've had arguments with people to say that really you kind of look historically at the Successful open-source projects they tended to be sort of a benevolent dictator model where I think it's important note the dictator is essentially being given given power by the by the community and The you know, I think the concerns there over time is you know Well, what happens if the dictator comes less benevolent or you know It sort of gets out of it and there hasn't really been a succession plan Which often there isn't in kind of community type of environment And then the third is and you know, I think meritocracy is a term sometimes get the bad rap because I think it's sometimes Deliberately misused but the idea here is that you do have kind of a broader community of some sort of governance model You know a patching software foundation is there are probably what the classic examples of this What why the issues you run in here? And you know, certainly there's been some criticism around open stack in this regard is You've got all these different entities and it's messy and they have to coordinate and so forth Although, okay, I guess if you buy into open source, I'm not sure that's a terrible thing So that's kind of some thinking around community So, you know gang kind of More into the bigger cloud picture So, you know, if open source code isn't the be all to end all You know, what are some of the other aspects of openness that matter and I would argue that one of us fundamental points is around The portability of workflows from one place to another so if you're running in one public cloud or if you're running in one private private cloud or virtualization platform implementation Can you move that to other places because you know the fundamental idea with with cloud and I've very Deliberately not gone into a bunch of definitional stuff here But the bottom line there is that you're running your workflow in one place You won't be able to move it elsewhere This is probably particularly evident on in terms of public cloud providers But it also applies across different virtualization technologies and so forth and You and you know if there's just sort of an idea of Hybrid IT you know red hat we kind of call what we're doing in cloud open hybrid cloud But you'll pretty much all big analyst firms and so forth all pretty much agree that we are moving to this environment where you're going to be sourcing services of various kinds and computing resources from a bunch of different places and Some of those be more reliable than others some of them will go away some of them will change business practices for example So the basic idea is you really want to be able to move those workloads and that data Across those different environments You know this is sort of one particular example You know that we're doing with with management called cloud forms and the idea here is that you can have sensually define an application But then deploy it in a number of different environments so you kind of having having served as application and offering system environment defined by template and Having that be essentially a way to to specify a portable application That can run on the different virtualization platforms public clouds and so forth But I think we also arguably Maybe I think the application portability aspect of things is certainly important I think it's also important to Think about data and in fact, I would probably argue that yet as Things become have more data centric and we're dealing with these very large Data bases are actually more more typically very large sets of unstructured data Thinking about how the data relates to portability Is also important and then you know that kind of technical aspect and we talk about that a little bit But then the other aspect which sort of gets out of the technology to at least a certain degree is Have who owns this data and how can the you know, what are kind of permissible uses of intersecting the data? Dave McGorrie who's at Warner now call I think he's generally credited with pointing this term data gravity and this is a graphic of his kind of Flying to sort of a quantify what data gravity means and I'm actually not so concerned with the You know kind with with the pictorial equation that's up here, but rather Really with the basic concept that you know this idea that if you have a very large amount of data In an application associated with it well, maybe you can move the application but there are a lot of Matters of physics of nothing else to actually moving that data around and you know There's certainly no you kind of change the laws of physics and all that so There's not always going to be an answer to this but really though my point here is that when We are thinking about portability of applications I think it's going to be increasingly important to think about the portability of the associated data with those applications and in fact Talking to Adrian co-cropped of Netflix a couple nights ago And he actually prefers the term Services applications and one of the reasons he likes to use the term Services there is because it really he really thinks of a service as the And it's associated data, so you really almost need to think of those as an atomic entity at some level But one of the things as many of you may have heard a John Mark Walker Up in key knowing in the first day You know again can't change the laws of physics, but one of the things to think about is at least the technical point of view How do you how do you create a Hybrid storage infrastructure that lets you move data across different places and you know I think the main point here is the contrast with say having a storage array that only runs You know in one particular data center You can't bring your custom storage array into a public cloud environment for example So I think that's what a reason starting to think about these open source software only storage infrastructures is that although we still definitely need to worry about latency and bandwidth and all that kind of stuff That at least gives you a an infrastructure that is portable Subject to whatever constraints you may have in terms of moving large amounts of data So I mean I certainly don't claim that having a very large-scale software only Storage is the only thing you need to think about in terms of data portability Absolutely isn't but I think I would probably argue that storing a thinkable storage in these terms is sort of preconditioned towards having portable data You know, that's kind of the The kind of the technical aspect of things. I think there I think there's also We're we're needing to start to think more about kind of some of the kind of something more philosophical or some of the more human use terminology here Jurthor by these NYU. I think he was it was like a residency Intel when he was saying this but you know, I'm starting to really think about What are some of the Kind of questions that we're going need to be answering around data and I think a lot of these are not really well understood at this point But you know, what do what do kind of do we mean by data ownership a lot? This is not as well established necessarily some of this is in copyright law But a lot of things are not terribly well established. Yeah, I meant to be issue around journals earlier on You know and You know, and so but even if you kind of establish ownership of a particular block of data I think one of the things that we're increasingly have to deal with is what do the Intersections of these data meet being you know, what really is is privacy and I'll show you an example in that slide That I think is going to be very problematic and I'm frequently reminded of Way back in the Dark Ages in the early days of CDs Lotus had a had a program But well an offering that they called up Marketplace, which was essentially this Bunch of data on you know sense a demographic type data By nine digits zip code, which they were going to be selling on CDs and There was a massive out, you know up war about this because You know, it's nine digits seeded nine digit zip codes in some context can get very close to being personally identifiable data and You know, it seems certain so quaint by today's standards but this caused massive outrage that anybody could buy this in the early 90s and You know, of course today, there's many more complicated things, you know, like What is anonymized that data for example? And it turns out that a lot of things that are apparently anonymized turn out in fact Anonymization can be broken. So that that's kind of going to be That's going to be a big question going forward This is this is just sort of one example not really a personally identifiable way but just an example of some of the kind of almost surprising things that you can do When you start Mashable to stay here. This is this is Flickr. This is San Francisco Uh, basically using some algorithms Eric Fischer The pain point whether a person had recently taken photos nearby Um, just sort of classified them as either tourists the likely tourists are likely residents and the red are Likely tourists and the blue are likely residents and for any of you who know San Francisco This actually looks pretty on target And basically of course people this is with geo tagging Primarily in people's cell phones who are taking these pictures and uploading the flicker So this is this is just one I think particularly colorful example of the kind Things that can be determined by piecing the essentially bringing together different types of information and in this case I think this is pretty much a very harmless example But there are other things that could be done that are you'll perhaps less harmful You know as we start talking about tagging people in facebook and that kind of thing apis um This in a way, I think this is probably going to be one of the biggest questions that From an openness standpoint, we really need to deal with going forward because increasingly apis are Going to be central to app development. Um, now I think the folks say, oh, you'll be develop applications just by Putting a bunch of apis and pointing and clicking and tying them together Any of you were app developers out there? I think your jobs are still very safe There is uh, there is lots of other things that will need to be done Uh to develop application, but I think it is also fair to say, um You know, I did sort of show the graph going up and to the right that there's more and more apis are going to be out there and increasingly for web type development You're not going to just Uh develop an application, you know, write a whole bunch of python code and in a vacuum and be done with it In many cases, you're going to consume maps apis or other types of apis that are out there So, you know, what does Open mean in the context of apis? I think there's a lot of different kind of taxonomies and things you can do about This is from uh, luis gray who had a very popular blog in silicon valley And he sort of breaks the middle three category. You know, the first one is open access and this basically means that you know That you you can use an api API that you can't use is probably not very useful but this is api that The company in question can Sort of decide tomorrow that you're a competitor and don't get to use it any longer Or that they're going to change the pricing for the terms of accessing that api um Not surprisingly, you know, I would argue that you know, that's kind of Dangerous to face a business around those APIs. Of course, you know, there are companies that that you know, basically were Building their business and using twitter apis and where I said, no, I don't think we're going to let you do that any longer and Goodbye business um, there were apis that leveraged open standards of various sorts and you know, um You know everybody you you know using standards is great, you know, that's sort of like saying yeah, you know I'm going to program an api and I'm going to follow best practices by following some of the open standards out there But that doesn't really say much about the api itself And then open standard apis there's a clear definition To be utilized by multiple providers in an interoperable way Now when I say standard, do I mean that some holy standard's body has sprinkled Holy water on it and said this is good I'm not necessarily because I think that's a recipe for moving very slowly But uh, I do think uh, I do think it means that it's not you know one company Saying oh, this api is open, but the implementation is really complicated and nobody else actually offers it um, you know, this is um, this is another listing drug looser, um I think this is more about I would argue it's more about what makes it a good api in general than what makes a good open api necessarily Um, you know, and so none of this comes back to come some of the community discussing around open source You know, it's great to be open, but it also needs to be useful You know, there needs to be some sort of plan and business model perhaps around this that you know It's actually going to exist in six months has to be easy to use. This is why rest has become so popular um Great support for developers. So, yeah, I think this is really in addition to having something that you're in control of It needs to be something you would actually want to use because just being open doesn't buy you a lot You know, obviously, uh, there has been some There's been some legal Legal cases around apis in recent years. This is the the google android, uh, we Fortunately seems to for now have come down largely in google's favor. Namely, you know, you can't you can't copyright an api Um, but this is certainly going to be you know, I'm going legal area that is I think a lot concerned a lot of folks going forward Yeah, these are some other aspects of apis you'll stability I kind of talked about some of these But you know what basically how can you use this and how confident are you that you'll continue to be able to use it On the terms that you started using it Final area, you know, this gives me a little further field is the mobile web and you know, I suppose the provocative quest is or our app stores evil So, you know, certainly they've been successful, but are they evil? And are they a passing fad html 5? Um, you know, not quite standardized yet, but you know, essentially it is intended to address a lot of the limitations that exist in html and you know the the idea here that Um, you know someone promote is that once we get to this You know html 5 nirvana We don't need app stores a longer because html 5 has some offline capability and You know besides we're you know, we're reaching You know, I think eric spick just said everybody on the planet is going to be connected the air net in a few years decade or so And so, you know, do we really need this and You know my personal belief is we're going to shift to more of a of a kind of a web centered world There there's certainly some advantage to doing there's certainly openness advantage to doing it But I think there's a lot of reason to believe that we're going to continue to have app stores Certainly a lot from a monetization point of view app stories make it a lot easier um, there's There's the distribution infrastructure of the app stores of the Arguably someone could build an html 5 distribution nexus that looked like an app store um And you know kind of a lot you know kind of a lot number a number of things that sort of relate to if you won't sell an application um App stores probably going to remain a fair way of doing it And I also suspect that they're still going to remain something with functionality They obviously remain something with functionality gap, although That could that will arguably narrow I mean the conundrum here is they're generally walled gardens of some sort, uh, the greater or lesser degrees um There are currently incompatibilities between free software licenses and some of the app stores um Simon Fitz who many of you may know actually gave a good talk and gaps app stores in general It buzzed them. I think Simon's feeling is the The the licensing compatibility thing is going to be straightened out and in fact Microsoft of all people Uh may actually be furthest along with that with their keys and seeds They basically have a term to the effect of to a degree free software, you know our teas and seas Don't jive with free software license teas and fees the free software The free software license sort of prevailed um You know currently You know, there's there's as far as I know no way to kind of make a donation to an app in app store as opposed to having a fixed payment um, but I but you know, I I think the expect if the general expectation here and this was kind of Simon's Inclusion as well. It's that You're probably kind of sticking your head in the sand if you just you know sort of don't want to deal with this because It does seem likely to be the predominant way that these consumer apps are going to be continued to be deployed for you know, interesting time horizons so, you know questions, uh, this is to get my info and uh, you know, feel free to email me and We have a few minutes for questions. So questions anyone I have some books here to give away so, okay I I mean, I think that's very fine. I'm not sure how how new it necessarily is I could you know name at least one very successful open source company But I won't that was I mean not really in a nefarious way But was very much, you know, all the developers Were there I also say in all fairness that I think many open source projects kind of get started by You know in no nefarious way, you know, it's just natural There's a group of people that get started and maybe you know, maybe they form some sort of commercial entity around it but then they they just never Expand that community not because again, they had anything nefarious in mind, but You know, there was sort of the loss of control. There was the Um, you know, they just didn't invest in it. I mean you have to invest to make community I mean, I know an open shift at red hat to our past, you know, we've been We just hired a a cloud ecosystem evangelist for it We've been hiring developer evangelists. We put a lot effort into, you know blog posts Like, I mean it is I mean we're spending real money in order to do that and and you know, obviously we think it's the right thing to do But I think it's very easy for companies again with no nefarious intent Oh, you know Do we hire an evangelist or do we hire another developer, you know, another coder? Oh, well, we don't have enough coders We need to hire an arcoder And your questions Okay. Well, I do have a few books up here that don't stampede to get up here and even if I don't have enough I Do I will can send electronic copies to people. So something else comes up feel free to tweet email Comment on my blog what have you so thank you all