fernando ribeiro oracle re.47 chainlink startupsOpenstack Is Doomed And It Is Your Fault

How To Buy Ethereum With a Credit Card and No ID - Market ,Buy Ethereum on crypto exchanges that don’t require ID Crypto exchanges have different requirements and limitations. On most exchanges, users are required to undergo some sort of ID What is the Average Household Income in Canada in ? According to the Retail Council of Canada RCC, the current lowest minimum wage is in Saskatchewan, where it is $13 per hour. However, this will increase to $14 per hour in October and $15 per hour the following year. The highest minimum wage is currently in Nunavut, where it is $16 per hour. fernando ribeiro oracle re.47 chainlink startups Openstack Is Doomed And It Is Your Fault
fernando ribeiro oracle re.47 chainlink startups Spiral Out — Using the Golden Ratio and... Openstack Is Doomed And It Is Your Fault
yeah hi everybody welcome to opens welcome to OpenStack is doomed thats all Im while youre all here at this conference right there were some alternate titles for the talk somebody might have seen it flash by OpenStack is doom or how I learned to stop worrying and accept complete corporate control my job here is to sort of poke the bear rile you guys up you may not agree with everything I say but if you do I accept a variety of forms of payment if theres have something funny to contribute and shout it out I probably wont to be angry with you I know I would for those of you who dont know me it might be my fault too because I hope to write a bunch of these things a long time ago thanks for showing up for my wonderful clickbait title if you dont know who I am some may consider you lucky hopefully none of them are in the room but Im one of the original little group who wrote Nova before this OpenStack stuff all started with a couple people in here and Ive worked at NASA and so Rackspace nebula and piston and nowadays Im the CTO of a great little startups focused on developer experience and nothing at all OpenStack related so to help you out with with the talk to figure out you know what Im talking about in different things I made a little guide here Ill try to use different colors to do you know different types of statements Im making that way you can figure out you know where Im going with things I dont want anybody to be confused so heres a few examples to help out incendiary everything that touches Launchpad is poisoned I really hated launch pad or mmm darn hated launch pad I thought pretty much day and night against it as we when we started it clearly the bunch of people quite liked it but I actually had to spend I spent a lot of time writing a bi-directional bridge so I wouldnt have to use bzr its actually still gets like github things just because people hate pzr that much but it actually has its own bi-directional bridge now so you dont need to use mine this is a doom thing the Rackspace API was the worst thing to ever happen to Nova its really not we wanted it was extremely delayed it really sort of set the stage for kind of what was next things that eager fault Keystone should not have its own user database somehow I like left for a week and we got a user database they might have a session going on right now I dont know whats whats going on there but yeah the original Keystone light stuff was really the goal was to just back-end on your existing user databases you as big companies have your own yeah theres no real reason to write our own and then unrelated this presentation Amazon Web Services names their stuff way better than we do we have a lot of really weird names in here and none of them really make any sense unless you know some really weird inside joke so itd be nice to fix that at some point so just to figure out whos gonna beat me up later can everybody who is a developer or an ops person raise their hand all right keep your hands up now if youve contributed to other open-source projects besides OpenStack keep your hand up alright cool so we have a lot of people you people with hands up dont tell the people who dont have their hands up whatever Im blatantly lying you put your hands down now so in order to talk about something being doomed you have to kind of decide where it was trying to go in the first place so this is a thing copied off of that that website that I didnt like and this is whats been on there I dont know was last updated but there is something important them stands out on that for me its definitely one of the things I cared about most when I when we started this project one of the reasons why we were trying to make nova and not use eucalyptus for example was WS star so tons of saml soap WSDL things like this or what we were trying to get away from and then the very first thing was a API that was very heavily wisdom compliant so yeah this used to be the thing I cared about most before OpenStack broke my heart but yeah sad times but you know people are excited about the implementation now people who have Stockholm Syndrome and people who are consultants so its a good its good for some people so theres 143 projects listed on launchpad some of those are corpses of projects some of those are reanimated corpses and projects plenty of them do more or less the same thing but in ways that are incompatible anybody can those who they all are is probably on the Technical Committee and even then I would be surprised if they they actually did if there was an Olympic event for feature creep OpenStack would definitely take the gold theres 85 things called plugins in Nova so I havent looked at Nova a lot lately I just was scanning through the codebase when I was making this talk theres a directory under the nova api v3 called plugins theres 85 things in there besides the fact that you know the Nova API is pretty much undefinable because of this I think somebody forgot an important rule about open source software and that is saying we have a plug-in API is basically your way your nice way of saying we dont want your code plugins dont belong in the repo they belong somewhere else where you dont have to look at them or care about them the if if we wanted it it would be a feature likewise theres also a 91 can trim modules that seem to be more or less overlap with the API modules I dont know I dont like directories with 90 things in them Im not really sure what any of those things are anymore I dont again you know whether anybody else is ideally theres probably some test somewhere thats tech checking where they work and if you turn on one of the options somewhere you might have it installed or something yeah it makes me it makes me pretty sad the other big one this is a great joke right its its like on the dreamhost shirts but basically barring cloud foundries Bosch I dont think anybodys worked with the more complicated setup system for a tool right so its a its probably the most complicated shell script anybody mystery was ever seen it does basically defined what OpenStack is at this point as far as I can tell but it is not its not simple so how did we get to this right we are no longer simple to implement making something simple after the fact is just about impossible you usually way it works is somebody does a rewrite too that replaces the old thing this is how we got say Firefox out of Mozilla Moore for example Keystone light out of Keystone its its very its a very active job to keep anything simple you really have to be very very attentive the whole time every option you add will be there forever we have a lot of them throughout a lot of projects knowing how to keep something simple requires having a definable problem something that you you actually know you can solve as soon as you start trying to solve other additional problems outside of your original scope you start getting a future Creek the water has become less clear the original plan needs modification it may not really fit and thats where most of your technical debt will come from every API call you add will be there forever theres thats thats one of the saddest things for me about the Rackspace API was its really been how many years now that we were we were stuck with a sort of non-conforming API it took months and months and months to sort of implement and it really didnt match the project at all its why very few projects that dont evolve into spaces they were they didnt start in they started with an epiphany you had an idea for an elegant solution to a problem and then you ended up with feature creep you it as you grow into new things the solution no longer if its a problem then you usually go refactor and write again but usually though at that point it is nice at least that the new problems weve run into are only now addressable because youve solved the original problem so you got that going for you the next rewrite is usually better but thats how technical debt is formed its the v authentication system you write is usually better than the first second third and fourth and by the time you finish it you already know what you want to do for the sixth so you have to usually yeah you have to take a strong stand on things is Jim Baker in the room there we are Ive met this guy at the at the HP party at the ranger station or whatever Mountain Air Station and I told him I put it in the side in the slide were trying to decide on whether we want the avocado or bacon grilled cheese sandwiches and so its a hard decision and so yeah of course you say hey why not both which more or less works for grilled cheese sandwiches besides the obvious heart attack area but it doesnt work that way for software with you if you take both sides on software you end up with a very indecisive a very indecisive code base one of the big challenges for getting sort of external corporate approval for for OpenStack early on was the fact that Rackspace was seen as being like to in control everybody thought that since they paid from the conferences and things like this that other big companies you know the HPs IBMs of the world werent going to join the join the project so very early on we got a committee we got like a board I forget what it was called - beginning Oversight Committee or something project policy board yeah thats right yeah so basically you suddenly had to get things sort of approved via a like a political committee there were ways it was supposed to sort of be a way to solve arguments but in the end it basically didnt things have improved slightly since then changed theres Chapman changes and what sort of the roles are of the board but the amount of time we spent dealing with the project policy board rather than making development release down do we need the board now hell yes this thing is a gigantic machine now right theres six thousand people at this conference its ridiculous its a its a political political beast that a lot of people have you know their their horse in the race song but back then it was it was a really bad thing for the project multiple groups of opposing views cannot all own a codebase it got really bad like warring patches implementing the same things two different ways people trying to hide their code in places where other people with opposing opinions wouldnt wouldnt see them wouldnt notice them until they were already in the codebase and its much harder to get something pulled out than it is to get something in it got to the point where people were literally sneaking in code that they knew I wouldnt approve when I was asleep and which again is why some people are proud like dont like me because I was very adamant about I dont want these things in and people just would go around it entire projects came into existence simply because individuals refused to work together they wanted to do something their own way and the way back then to do something your own way was to sort of work off a project that way you could build your little section of it your own way which resulted in many types of apis things like that we cant all on the same code base somebody has to run it a committee was not the right choice its basic committee the software designed by design by committee is doesnt really it doesnt go anywhere its it you start you have features that you just add features and features of features nothing really gets better those team you need good software is designed by team those teams can be across companies but they have to be working together towards the same goal a committee is working towards multiple goals and compromises that leads things to having a yeah a very non decisive non decisive codebase I didnt want my project to be open source so that people could tell me what to do or so that they could you know help me write my code like I already know whatever right open source is not about contributions so OpenStack all we use is talking about how many contributors there are open source is not there so that you get people to write other people to write your code its its there so that people can find out what went wrong its so its so that you can share the code of people and sometimes somebody will come in who starts working closer to project and has opinions about it but open-source is about providing a better product so people sometimes challenge like say Google or someone for like throwing things over the wall you once you want insight into the development process as a developer because like maybe there is a feature that Im really hoping is coming and I ask a question about it you say oh thats coming soon you can actually see when its when is showing up but really open source about providing a better product as a if youre an ops person if youre a dev person when youre using this thing it will break guaranteed you will never use a piece of software your life that does not break except maybe something written in like Ada and the goal is to find out what the person who wrote the software was thinking so you can figure out how to fix your own problem its not so that you can go and having input on the direction of the project itd be nice to but really thats not thats not their role theyre giving you something and its better than what it would be if this closed source mark talked a little bit in his presentation about experiments so you know OpenStack was kind of an experiment and we have a lot of new experiments some of the smaller projects I think are doing actually pretty well looking through looking over stuff theyre pretty well they have a pretty well-defined scope they they have a small enough team that they can actually still get some stuff done but without having an opinion as to what we wanted to do this is this is an experiment without controls its sort of just wandering we like we let the we let the rat loose in the office and were hoping to catch it later on or something its not it cant be proven or disproven whether it actually has solved a problem or not it simply just keeps on growing and so right now thats all were doing were like a cura at the end were just growing and growing and growing with an opinion you have variables you have controls in your experiment and variables you can try again next time and to a different thing and have idea that you might actually do it make it better you know solution but the more I thought about I realized focus tack did sort of pick a side and they actually really knocked out of the park they did they did an extremely good job its by far the most successful project Ive ever started or worked on early on and Ive you know had successful startups and things like this OpenStack is definitely a bigger bigger business than any of those unfortunately for me the side OpenStack picked is money they we wouldnt have six thousand people here without it it was a sighted very early on that we needed enterprise buy-in and like literal buy-in to make this thing to make this thing real were competing against people like Amazon who have a very large cloud and the only way to for everybody to feel like they can get the the attention that they need is through very large companies helping and that kind of fight is not cheap its big it has it has to have a big marketing apartment everything like this at which OpenStack does so sort of my statement here is that OpenStack isnt people can we do like a hand raising thing again who here has worked for a Rackspace I know I have all right anybody from HP how about a Dell Cisco IBM who else is here uh Morant Asst yeah theres theres some rare individuals who just like are really into it themselves and theres a lot of smaller companies have joined but a huge percentage of the people here are from from large companies OpenStack is actually companies and thats okay they come in two varieties theres those with heavy open-source backgrounds oh I should also say Red Hat yeah there we go Ubuntu thanks sorry the those are those are companies with large open-source backgrounds so that a lot of the stuff they they contributed were contributed in a sort of as normal open-source way and a lot of other companies work on open source software or theyve hired people who had good open source backgrounds but theres also a lot of companies here that are named on a box companies that they sell a product OpenStack is a way for them to get more theyre spotted sold more and again it it works its good its been for that and theyve theyve been getting theyve been getting what they want out of it which is their name in front of more people and things like this unfortunately for me thats astroturf thing thats not a community thats so I didnt put the word OpenStack on here because if people are taking a picture I dont its its such a dirty word to me that I dont want I dont want to soil this thing with OpenStack by putting those two words and together but really thats what is happening theres a lot of community decisions that are led by large companies and thats not really a community decision it means the community is the companys not the people and I think that its a its definitely a misnomer to claim that this was sort of the peoples the peoples cloud its not grassroots and everybody know like what astroturf means its like fake grassroots movement and thats fine again its working it works for tons of people its obviously being used by tons of people we see great keynotes every year by gigantic companies using it in large ways making plenty of people plenty of money thats great ecosystem getting incrementally better at a bunch of the things it does its just not what I wanted right when I was writing the software I wanted to have the you know product a user experience like a developer experience I wanted to I wanted to change this cloud thing because theres so many interesting fun moving parts and cool algorithms and other neat things to try I wanted my opinion validated by usage I wanted a platform for like redefining how I use a computer every day I want no more user names I want hypocrite is computing where my local machine and my and machines in like my office and everywhere else theyre just running whatever jobs one of the things I love most when I was working at Google is every time I compiled something I compile them like eating machines somewhere it was great thats what I wanted I wanted to build that system for for everybody I wanted organic I wanted to be like the substrate that Skynet is gonna be built on you know I wanted the machines to win but you know because theres been such strong push for you know from vendors and feature creep the developer experience has been just really shoddy theres I dont work on software because Im paid to work on software I work on software because I love writing software and its just not an experience thats pleasant at all in OpenStack is heavily political heavily bloated and theres so very very very very many moving parts its yeah its unfortunately not not a nice place to be so if you were to do this again what would you change anybody whos worked has answers to this theres plenty of things that youd like to have had done differently the first time so here are some out of context quotes from the community thats fish sorry I was wrong Ive made this up so its not really a quote from fish but the I told them I was gonna put on there anyway weve made mistakes lets uh you know say thats okay we can do it again thats theres a lot of code there most of it doesnt need to be a lot of its implementing things we we never needed in the first place and working around stuff we implemented that we wouldnt do again this way we are a resident our resident spook had a lot to say on the matter and you know thats I think I think actually they were they were one of my like most pleasant experiences early on very quietly in the back of room suggesting nice improvements every so often without necessarily having any without seeming to try to make a power play theyre not selling a product theyre just trying to make their product better I think that is thats the minds that we wanted right we wanted to how do we make this product better not how do we make this product to support my so speaking of supporting things the I was very proud of I was very proud of Mike in the last release of cutting out a whole bunch of drivers at a cinder and I think he gave this little quote in a session somewhere so hopefully some reporters get to it too and they said well you know hey arent your arent you worried that green valleys drivers is going to is gonna make your project fail and so theres a lot of drivers already in cinder it supports a lot of things he doesnt need he doesnt need the corporate buy-in they need to buy into his stuff right and thats the way we should have been thats the thats the dream of open stat for me right was that I was defining something with a great abstraction that companies would then come to you and want to use I didnt want the companies to define the project spark Sparky has been a wonderful a wonderful contribution to this whole thing and hes hes done a great job at making sure everybody you know hears about us and does things now hes like running the foundation with Jonathan and and all those people theres not really a thing to say about this code its just a funny slide I guess but yeah so I guess what Im trying to say is I think the five five year experiment is done weve gone as far down this path as anybody should ever want to were never gonna fix the technical debt of Nova inside Nova for example its too big it has to be changed weve been the experiment went off the rails years ago weve been being held hostage in like a room full of a thousand cooks and its a very busy kitchen its not yeah its we have to escape so I think we should rewrite go rewrite Nova I dont think it needs to do all the things that it does right now I think we could probably make a lot of better decisions than the decisions that you know 100 ish people have made over five years or made five years ago as to what it should support I think its a probably a fun job to say these are the things that we actually care about and get to be opinionated right funds software and yeah I think thats where we should go with this I never invite plants its its just a list of URLs guys like I dont know it yeah it was one of those projects that exists existed because two people can work together so and then you know we tried to salvage it but yeah it doesnt really do anything Id love to stop at the terrible apis just find an actual web developer anywhere and ask them how to do it like its its its ridiculous having a bunch of systems guys right apis because its yeah you really just dont know what youre doing man and so yeah I think we should you know stop it with those go look at actual web things Im sure some of you some of the projects probably have nice apis some of the major projects but but yeah we have a lot of a lot of weird calls I think this is a device that sort of goes beyond OpenStack its but people people have been toeing the party line very heavily for a very long time and yeah I think for yourself you know its its not its not your bosses youre not trying to implement what HP wants or IBM wants you should you should buy into the project buy into the vision to buy into a dream and you should work on that and then tell your bosses thats what were doing so I think we should start the new experiment do start the next one make a new Innova make something make something better something clean something lovely that wed all like to work on take some sides maybe even your own side have an opinion you can produce a lot of code very quickly theres a lot of tools nowadays you can make proof of concepts again Nova was written over a weekend and it replaced very rapidly stuff that was much much more mature than it was Nova 2.0 or whatever can happen the same way so OpenStack is doomed long live OpenStack so thats about all I can handle talking about it Im willing to take some questions I dont know whether theyre thats like the kind of tougher question all right this guy so I think I think theres a the question is could you give a concrete example of what you would sort of rewrite in Nova I think the so the API first off theres really no reason to have a API as epically large as that a lot of the things were started based on having the Rackspace API and these sort of concepts listed there those are sort of old ideas nowadays we know a lot more about cloud stuff weve seen all the different things that people have our regular cloud containers containers are a really lovely way to like bundle your apps write the code the processes you would like to write I think probably a probably a focus on bare metal with a stronger container system I think is probably what most people out there who are building cloud software nowadays want to do thats like thats what is currently happening you having an easy way to wrap container dries things and vms for security purposes I think those things are stuff that people care about now I dont think its as exciting anymore to just spawn a VM its no longer no longer interesting so yeah thats thats something I would do I would I would basically focus on focus on bare metal containers and not necessarily just docker so any other comments or anything like this cool well my job here is done I hope I hope some of you have taken least some of the things a little bit seriously Oh somebody there yeah I just Ive been giving talks on contains a lot my company does container stuff any taught any other ideas on containers since its a hot topic right now yeah Ive Ive talked a lot about containers I think the well if since were all just like opinion talk I think I think doctor doesnt have anybodys best interests in mind besides Dockers and thats sort of sad to me I think that they are very much trying to centralize control over the ecosystem and its not somewhere I want to be I dont want to be in something where I have to talk to them to get my things so obviously so rocket is a sort of up-and-coming alternative LXE and lxd are other different nice ways to start containers and things like this but the what docker got right was the ux right they had a product and they got it they got a UX that worked it rapidly went off the rails it has a lot of bad UX now too but but yeah i think i think separating I think docker is not going to be the answer I guess on containers but rocket isnt yet to cancer either so well see where it goes I think maybe OpenStack could have an opinion governess 2.0 is big tent I think thats a good start so I think so what does governess 2.0 look like its a question I think I think big tent is a good start but the idea that we are again like I said earlier on plugins dont belong in your repository OpenStack stuff doesnt have to be under an openstack umbrella it doesnt have to be a incubated project or any of these things these are all terrible terrible terrible ideas when really if youre trying to build a community you want that one guy over there is random project to be able to interact with your stuff without them having to sign papers and be beholden to some committee so I think I think weekends a good start I think having less governance is better for most that stuff I do think theres still various governance related to say branding and things like this I I know they talk about a lot I dont know what the current state of the art as far as whos allowed to use the OpenStack logo or for what reasons Im an open-source guy all my stuffs always like MIT licensed I say use whatever you want you know use the logo whenever you want it say like we support this and if you dont support it and you said you did your customers will find out pretty quick and not use you so I dont think thats too too bad but but yeah Im a definitely a less governance kind of person I think fighting with technical committees has wasted a lot of my life do I think mandating Python makes sense going forward I would say no except that the apis are pretty bad and so in order to in order to have multilingual support for stuff like a poly a polyglot language you really need to have a very strong sort of API system things things like protocol buffers stuff like that helps a lot for doing multilingual stuff they have a common a common API is from multiple languages it can be done I like go I write everything and go now I like Python too but but for the most part I write stuff and go I think I think were big enough now that it doesnt really matter what language things are written in but if you soon as you write it is something else you dont have access to what Oslo is is OpenStack common now or right yeah you dont have access to stuff thats in there but I think thats probably okay I think wasnt did Dean was did you could go with glow go for the open set client No yeah okay well okay so he said no he didnt go with go for the OpenStack line but I think that would be a good test of the community if you tried to write a unified client in another language you would rapidly see how difficult it is to define your apis and so I Ive tried a couple times and sort of failed yeah thats why its little toys what Dean said so I would like to see other languages just cuz I whats up Oh so Swift has a branch and go right now so thats cool I think thats probably cuz those guys are like really bored of working on the same code base so if Swift has been like a very stable project for a very long time and so yeah I think I think those guys are antsy to mess with new stuff yeah any other random opinions on things all right I am gonna cut out really then thank you An inspiring walk through the decisions and mistakes that turned Openstack from the peoples revolution into yet another piece of enterprise software laden with technical debt. From early heavy-handed architectural decisions to latter-day corporate power jockeying, this talk aims to steer the audience out of the dark depths beneath the mountains of legacy and into the clear green fields and river valleys of modern day, because…Full session details here: