Bestand wählen
Merken

Build Cookbooks and The Service Delivery Canvas

Zitierlink des Filmsegments
Embed Code

Automatisierte Medienanalyse

Beta
Erkannte Entitäten
Sprachtranskript
alright so eraser to wake up from like the launch from our readers and kind of like taking up his I do try and have enough energy like he was going but I told you understand if you just like and over because like yet which is wonderful right so we will start with a little bit of work we go that article was used button or maybe rural area right so
cial about who I am and your remarks I mean the person that was behind people were at of last year so if you watch the video on stage they deliver delivery using delivery and on stage check on that I was the person in the back and super heavily stressed because they were doing that line in on stage and I was responsible for writing the build a book that made all that happened and to the point of there was actually a little sonata act had written off to the side that give us the ability to like cut over vastly to a prepress thing just in case because were all people right like you don't have a backup plan of books that was would yet we actually did deliver delivery on stage of using delivery I now automate workflow and the author of about 1 year so Bill cookbooks I and that number just keeps increasing because my team keeps shipping software and the important part to really take in is I am not sending appear as a developer of me and in fact I'm customer really patient 0 and I'm going to be the person that goes ring teams like our guys so can can we fix this thing because it kind of hurts and and the delivery team I'm going to use that word uh the workload team has been super responsive in here that the number of opportunities we've had to adopt our own stuff and actually fix things before they got customs in fantastic and with that said I'm the engineering manager for the CIA 18 of that has nothing to do with intelligence it has everything to do with our corporate infrastructure and applications which when we get into some of the stuff later you understand why so it doesn't have to do the Taligent am so a really hammered today we're going to cover the prerequisites and assumptions and some concepts vocabulary prerequisites and these are kind of the things I think are prerequisites the mechanics of how all this works the actual service delivery canvas yes is actually a thing some examples using that canvas
and then on a show you some actual code that runs actual things at shot
so starting with prerequisites and assumptions because we always have to make assumptions I'm going to assume you're doing the dow marks and really all of my code assumes you doing Ops now as we all know that's kind of a loaded term what is it actually mean to do DevOps under you some very specific things that I expect of you I and I think that the workflow that I'm going to presenting is really does require the app that teens and the options are able to use get the the it's workflow were opinionated and 1 of the things repudiated is that you can use any 1 of the version control systems as long as they're get the 18 hour in order and very specifically deliveries get how absorber buckets actors as the ones we support today out but you're the team hostilities get you can't use get this just isn't going to work because the system kind disorder depends on it the each group is willing to see the work the other is doing this is super super important because I'm gonna ask you to take your infrastructure code that relates to the application is being deployed and the application code and put them in the same repo you've got to work with the rest of your organization you gotta work with your teams you gotta work with your ops teams it is all about being as a single team is how many people have had that thing words like OK 0 my god we have to coordinate this change across the cookbook and the act at the same time because otherwise everything's going to go wrong and how often is that work well but instead I can be a code change and a couple change and they get to this point as the same change that because they really are the same change that both the chapter about production but they just here I I usually start I'm during up some people room identify as admins operations engineers that sort of thing my people's and they people identifies developers that the right poly an egg don't you a folks house the deviations by idea of my duties dissolve that's our job and you have to be in a place where everybody's talking and you all have to care about the end result but because I'm USA some super blasphemous things in a few minutes and it will really make sense why we all have to care about the service and production of about and going to go so far as to say that the only thing that matters is the service in production the source code for the application I touched on this a 2nd ago but but the application the could put that deploys the application and the cook to the cookbook for building the application only deliver the same repo in harmony and because the it's just the only thing we operate in my not so humble opinion I should probably also mindset mention of these are my views of how light my team functions that doesn't necessarily mean that they are the views of how shall I think you should function because like the yeah there's a completely different thing between like what my team does and what we say is the right thing to do but I'm taller gonna tell users told the right thing to do we all have to start from a place of an API I want you to deliver the entire service How many people think the service is some application code I should go and as with a male so as not links there's like when you talk about it His right it like a load balancer there is there's probably some like storage involved Haywood probably got out compute instances active sources that I run the don't computes chemical and there might be some city involved I you have to be in a place where the majority of your stuff is BPI accessible a dozen all have to be but for everything that's not in the pipeline the more opportunity you have for things to go horribly wrong so the more you do it in the pipeline as part of the pipeline makes a huge difference the so for me what the minimum think has to be is that we can provision you compute whether that's the EMS instances no pick your flavor write OpenStack VMware the AWS measure but ruled you can provision and I think I most of us don't is like stand up an instance and . stuff and it there's usually some sort of load balancer stuff you really should be about to spend or make the load balancer change necessary to spin up that cluster of servers and also however people have API access to change their DNS that makes me sad so for coming coming bar in the cloud right now How about people on and that is there's there's OK I've got suggestions at i should holy the I will talk about that later as a dot concepts vocabulary the words that I'm going to use we
are delivering a service anything that you hits what we're not delivering is a package binary that someone else downloads and of something with and that's another topic for another day I it is not something frankly I care much about my team delivers services right we deliver at the corpora website we deliver the thing that makes the jobs actually show up on the website as those of the the things my team is responsible for when I say the word or artifact what is that mean to people is made that like does having people heard the use word artifact that is there anybody that thinks I'm crazy by saying the simplest artifact we can ship in the world is a parable they may have a problem that so a tarball a cookbook is a package artifact we care about the version the promotable thing which means we really do wanna do continues variation delivery I'm just going to say it now if you were not merging to master it's not continuous integration you could run all your tests all day long on Jenkins if that code is on master it is a continuously integrated and and delivery actually means it's in production somewhere crazy thought I even if it's in production QA because and about you but that my acceptance environment Tolley production environment just production for someone else but now it goes back to that point we're talking about services not code your code is no longer holy developers I don't care that there's something broken on master why do but if it gets the master that's not the end of the world because the thing I care about is the artifact is that artifact something I can deploy in if it's not we need to probe a big flag that says that artifact it be broke don't do anything with that and and we need to get to a point where every pull request or change request is shippable we need to shift the thing the goal is to get to his many small changes they go all the way out to production is we can because as we all know the smaller the change the easier it is to be bad right if I go in deploy 6 months worth of changes I just deployed 6 months worth of changes and you but that scares me the crap out like war come unusual tools were entitled the delivery truck I automate delivery users to have the right now like you already have it installed somewhere get you've probably seen delivery truck right is at the heart of our put put workflow essentially you can take this this this a good book usage recipes and it will handle moving cookbooks through the pipeline for you but little do people know it also has some facilities through for moving your versions of the application that you're using after the powerpoint in it that's probably also the point when I talk about moving a version that doesn't mean like we deployed a thing that just means like the version just so that were super clarinet from concept then there's the liberation a which is a neat could put that has a whole bunch of helper methods better sugar on top of delivery right so have there there is for example 1 where you use it to a go talk to the deliveries are Chef server to pull versions and do some stuff at those living deliberation so let's talk about mechanics the displays weird that story and talk about these in stages so I know what usual fashion so everybody has it and we have stages with inside of them stages are verified build acceptance universal delivered In lent we run things to lend code and is only clear everything before acceptance is free of artifact so we're talking in terms of this is about the code so relating the code were syntax checking the code we're unit testing that code that doesn't mean we're standing up a service running test against that's bad we want this to be as fast as possible and functional test come later the we do it again and build so when that approved bit hits we just merge to master let me say that again the when we hit the approved but we have merged master there also there are true places where the human gates that is for a reason writing it into now but anytime you sit and think to yourself 0 my god we need to prove that 1 more time don't it's their the reasons why and I'd love the talks more about it but a why there are only 2 candidates so when we get back to build we've now merged master in as anybody that's ever used any sort of urging intro system you know that on occasion you merge things and the thing you got out at the other end is not what you thought you were going to get so we re-run Flint syntax unit because it's entirely possible that the code that came out the other end wasn't what you thought it was an security and this is colour security it is not syst it's instance security or service security it is code security I will give examples of a little bit later at quality and that's kind of a loaded term and I think we understand that it needs to be there but a we have super great examples in many cases of what the right thing
to do is they're depending on your language of choice published this is more you actually do the build like you build the thing you build artifact in my case Thomas because I like turtles and or in the case of Michael books I like do and I could put upload because we upload the parks we'll talk a little about this stage is made up of of phases think did that right I'm told screw up at some point today because like the the words and you can skip phases but not stages right so if you're running a I legitimately have h have projects that are just HTML files like but there's not even you just make some changes and we seriously skip unit went and syntax because others nothing to unit went or syntax hit is just like go put some files on history and stand up some an each phase is a collection of true independent Chephren's so you run your D faltered Derby your built book as resting so your deforesting that is going to be your set recipe you're going to handle I'll show examples of this you know AWS spreads you might wanna laid out maybe insults Ruby has like 11 is Ruby Europe's shop for job shop you're gonna do that not resting and then the 2nd run is done is that people do you build user the and it executes the basic recipe so for a bill answer for an unit it's going to run the unit respite from it's going around people interested we don't she problem it's a right so reasons version promotion so what we do essentially is we created a Adam with the version an artifact information so if I have version 1 . 5 where they had to I get version 1 . 5 if it's a good book which holy noted together Chester right like that's easy application get a artifact uses nexus S 3 toll industry is 1 you gotta know where to go find artifact that you actually want deployed so we're going to do is we're going to go take that information so I restore like a check so as we want verify that the thing worse was going is the thing that we're applying at the location of said artifact so usually it's an S 3 you out and in any other metadata that's associated with that that's important because you may need I tend like drop the entire delivery environment just so that I know like how like the state of the world was built I'm skeptical pointed out here and because we're all we all can hit this secrets management is kind of an interesting use case for er interesting situation in delivery right now and so can work flooring out and it's getting better but it's not perfect um but for me the way I handle this is my builders have at the ability of the inca to date about secret on the and I use that to encrypt my secrets and put them up in the clouds and answer into the CEP server and then on my actual nodes have the encrypted data vectors wall and user of my hope is that that over the next year that a little bit worded you breaking apart of the AP and I'm and I'm just glossing over this because it's it's it's there you can have an entire section on just breaking apart applications in understanding like what it looks like but the couple questions you ask yourself what are all the pieces is related to the application so an yeah you occasionally see applications words really 3 applications in 1 will break them apart an maybe the shared pieces of the application so we talk about being in a in actual on from data center you probably don't spin up a new load balancer for every single application if you do I wanna work for your company because you probably have lots and lots of money to have a F I took a fiber um Net skill over everything would applications and we call them and that it's probably not API accessible theatregoer crack something every time like that really crazy 1 you know is the data shared I've worked in environments for the database is a shared thing and the applications that go talk to the database like that the database is itself an application in other cases like we spend my single instance are bus presents sensor post this poster for every single application it really depends on what you're doing when we talk about dependencies you need to understand if there are things that you can do something about their will will call operational concern and so you can't do anything that the operational concerns so like it it's the VM were cluster as wholly dependency but you're not going to test whether or not the the were cluster is up and running because like the BMR clusters are not up and running would probably have a different problem and like which should be having this conversation now and is the time runtime dependency we're gonna talk explicitly about runtime dependencies as we move forward in what I mean by that is does the service use it while it's running so like that's bad example the sciences depends very when we talk about things it's the does a API talk to this other API well the does it's probably a sort of run time dependency should we actually actively test code paths that verify that dependency that you declare and if you can't test it like there's no reason to declare so important word emerging after verify were gonna build for master and remove artifacts not code through acceptance union rehearsal and delivered and alright so 1st time and the service
delivery chemists where the start the artifacts in this all makes sense in a 2nd when I show you this thing I call service delivery chemist 1 is a canvas which means it is a non linear like we all like this that I think about starting at the beginning and getting to the end the reality is that in its pipeline right like you start at the beginning the pipeline you go through new eventually and well but the canvas is not meant to work that way the can this is really it's a document is an opportunity to think nonlinear only about your problems identify the operational concerns you go I touched on this a little bit a little bit ago but is your building out your applications stand where operational concerns verses water dependencies so an operational concern might be the FI device because yeah that's operational concern I am only concerned about the for this thing maybe the operational concern is that that frankly we don't actually ever launched features is part of the pipeline launching features as operational concerned because we take on feature flags that's an Austin would rely way I identify the defense is you once again we're looking for runtime dependencies we really want to have been a place where we can actually test the thing that I depending on because were responsible for doing that in there was a talk given by just earlier in our yesterday the effect and that gives a little bit more detail around the dependency graph model that I inside a delivery but think about this magic for just a 2nd you have 6 services you tell the services what they depend on it every time I deploy my application at the things that told that I told you workflow that i depended on it had it they run their test to so all of a sudden we now have the ability to actually do things like micro-services safely the so this is a the canvas really simple and this is the PowerPoint version because it looks pretty but this is is the actual you thing like I wasn't long strings last week working through my talk and I pull this for my backpack and Saturn wrote down with a pen and work through piece by piece what an actual application would look like and this is actually available at sea level but now delivery in this work aims not yet at Q. shout out to Mark Harrison who actually made this look nice in OmniGraffle has like I am a manager in 10 years PowerPoint for things that shouldn't use point for of so
the original 1 was the power point he made it really really pretty enough i in I need even be allowed to post the OmniGraffle ball so son about Ruby at let's let's get into this so really simple right revenue that's a load balancer in some instances the stupid simple application we got snatcher there's no database and I am just because we all like to have that mental model that it's running unicorn next goal so far we're going to start by
figuring out what we're gonna published is once again I told you at the end of the day what we care about is the art actually care about the service I don't care about unit testing code at this point because frankly I care about the service so what's going to get the service the points so let's start by legal let's build with standard let's take it created tarball create a pop up we want at that point where we are able to actually go see this even come up right and sometimes it's a proof of concept we use the beginning of the pipeline and get it right and the they right is the future wanting to early years spend all your time trying to figure out why revoke blowing up instead of like shipping code and sometimes
it's good and sometimes it's that it really depends on what you do so once again were
promising provisioning easy to instances Gnostic load bouncer well can know how that works right I've got I you shuffle visually you may use terraform as all cool just picked the thing that makes more sense to you the deploy phase In 110 were were walking through this as we go alright so we're gonna go run the shaft on the nodes to install and or a pretty act right so in this place we're going to do things like here there was a couple change so now we're going to change the engine ex-convict or like are application actually change so we will do a shot from which will cause and uniformed announced that sort of thing and smoke like this is the simplest like we have to remember smoke should be super braindead simple you just want to check did it work so did I get a 200 at a particular path and in my my case like I use a lot of symbol based applications of the 1st thing I ask is doing the 302 like does it redirect because I need off and that's a huge like awesome smoke test right is if I 200 on a page that should be sending me to go get authenticated I wanna know that blow up like that and functional like Szelényi you mean if it's an API maybe you're playing guns and J. Sonner making making sense of the on like it's always about what makes sense to you From there I dive in and it journey rights on reds many test it's a cookbook right in chest back or uncertainty so through a cop food critic Rubalcaba works for both are a decode-and-forward could occur after critic kind of more familiar with real and food that is awesome I love to see that the so here's the thing right line it could that you think you should always do that and my team actually just rolls straight recall because we write a ton of remote recode outside of like shut land and Ruby dachsie have some great stories about this in a few minutes here but we're going to check to see he is the syntax right like we want has this as soon as possible and then finally found in this period Bayes retches can make sure that is really were animation that there are no open CVDs against the germs the inner bundle of if you are running restart and like in production you should holy reusing but or other because it will tell you hang by the way that Sam ordinary using this holy and open cv against it you should fix that so use a more is more complex example this looks a little bit more like a normal applications right there there's been as there's 3 layers of caching because of course you have to is catching and you know we've got the load balancer we've got the CDN and without red post breast so what might that look like tha is even tell you now what change but we can look across and go wow Corporation a lot more things we should think about that the canvas gives you the opportunity 2 at-a-glance get a feel for what you should be doing in your face before you even writer of because we wanted to a place where before we sit down and go right build codebooks we have an idea of what should go where I and I talked a little bit
about this a few minutes ago you work in a real dataset you may not have the ability to do the thing in a cloud so maybe at applying a PHP applications hello my suggestion of I this is wholly not like paid for but in the and you can actually get it with an API I'd like to think they now have a REST API Beckham idea was all Pearl so you wrote some Perl to do the things I but you walks to spin appeared in Aston and handle IP address like assignment that sort of thing but load bounces and you're probably gonna talk about it instead of the actual announces discuss your standards in PHP instances some icicle instances in cement cash and then it has been where instances and no reason and fast so 1 and do of I on right and that's BPI accessible it the the key for me is we all have to understand I don't have to have a WS I don't have to have rule to get this today to get to this point the ultimate goal is that when you hit approve and you hit acceptance the entire thing comes up on its own when you hit liver the application comes into being you shouldn't have to spend your time going well it's it's it's a production employ so you do we run through the checklist review the thing that we do the thing as were deploying it like
really what we want to do is actually no because we ran through the checklist in the code the verify that the code is compliant and does the right things instead of about whether or not we had the checklist and as you as standardized bases you get to a point where you start caring about that because it's encapsulated in the code this is what that looks like right same general ideas we all were operational concerns because like the other side approaches should but it US that because yet but we have here our bicluster and all that stuff so I'm sure you all like season code as arena look at some code I this is just so that we have a certain point this is chef purchase an application in the Sierra wonderful in and is a simple Sinatra at that handles the purchases for 1 of services so if you'd like 1 of our our solutions are text to spend a day with you remotely had to talk about all the shaft of whether it's to you by some huddled cookbooks and no cultural questions that you can buy up to 3 non-contiguous days online and on the internet in fact like if you go to that website right now I you can't push the buttons in and like hit the credit card button and into your credit card and all the e-mail that says you bought something and so this is a service like we all have things were we accept money and what not so this as we started this off campus right this is how the application gets built we were gonna do unit testing that some when some syntax and fill all in it the 1st go around right I when I 1st deployed this through which holy didn't have went enabled the in fact I is actually a commit a on and on the repo that says make see Weber not a liar because I turned on a bunch of these things and to make sure that I wasn't line I give this talk so it's actually a look at some code in Iceland point out like I'm skipping functional right now I don't know the the the amount of work it takes to do functional testing with things like sales force and Caballero and striped like this is not worth it for something that I don't know how to make any money at all yet so this point words instead functional testing if it breaks my dad it's fully experiment right now we'd like to see it successful like if you all want go spend 2 thousand dollars to have a day of rest solutions team I would love you all right now I can that be awesome so this is my entire deeper lobby recipe that used to be super longer because of back in the day we didn't have things like flock integration wouldn't been of integration high those were things but it's not really simple you do a default for toolbar track i which is basically sets up the environment we have AWS correct so for those of you that know about interacting with it unless you know that you have to have friends on the box you know that you have to have an the actual in steel that's how your clean that there are a lot of little things you need to be useful so we have arrested does that we also install Ruby are the same way that we install Ruby on the actual node because crazy that if I can install Ruby the same way in 2 places which seems like a miracle sometimes and it's probably going to be more effective right so my university and I've got to hustle and we're going to do the delivery truck you test so that's just run unit testing against our cookbook right we want actually care about what the capitalist we're going to install are dependencies from other but it's an application uses that then sign going to happen my dad and file in place because that's kind useful and then we got a little helper method here to run rate test same idea right willing to the Cookbook we install a bundle dependencies we run recount dashed the i which is to say I don't like to have to go figure out what in God's name and recover was complaining about an tax and I mentioned earlier the whole idea of a Ruby Dessie I initially developed find only to find out that find always returns 0 because it found things uh instead of the that the thing that was inside broke yeah when the is all bundle a installment tendencies at the landlord check the bundle we standardized and I'm happy to showing where code inside of us but we're not a point that I don't think about how cluster gets it's what 4 lines that stands that X is the size number of E C 2 instances and he'll be terminates SSL and um sets the run list as appropriate and this goes out to those nodes and tells them to run a check due total I'm just checking the status code that pack such architect is is what matters to me that return to 100 couple useful things about and there's a cookbooks directory if you stick a cookbook in their delivery truck will just work it's beautiful and they can think got his eyes were your actual configuration code goes you wanna read up on the line that it gives you the ability to do things like ask skip bases and specify the search for the bill nodes and then I'm gonna say this to kind tongue-in-cheek i . delivery source-filter quick is kind of the standard utterly isn't because there isn't actually a standard but were might seem only puts are build properties and that delivery such book reports so we're not polluting the main part of the name space and finally our are coupled to slow brief that's taken as a custom resources they will make your life better I'm helper methods are awesome so you can drop as things that you used throughout the cookbook all over the place in the library structure he in it makes life better and finally output things in shared report so you saw that CIA and from CIA delivery but that's where those come from so I with 3 minutes left that's my talk what can I answer Fourier OK so the question is
and if I'm only going to do something in a certain phase should I switch on it right so far yeah I'm in unit went syntactic probably don't need terraform but the the answer really becomes it depends on what your coding standards allow for it also depends on what you want to do so at this point build nodes are shared and the 1st time it runs it basically our warms the cash and just make it's makes sure it is there and With terror is a great example if I don't have to install as root I'm not going to and so I'm just gonna put it in his the build user and that's really what I uses the differentiator I don't tend to add a this switches because it adds complexity to my default recipes that me person but the question is work I go to find out more about delivery truck Andalucía so there are is info in the docks so if you can search in the docks delivery truck in Galicia additionally had their or to put the cookbooks are up on get have I don't remember are they in the chef the the chef cookbooks 3 upward and a lot of preparatory just parts of some of the links here and so the idea get have like but not a I I'm of the belief that the best thing you can do when you run into problems go read the source code so I told you lots of source code and so and that said in my at 0 minutes the awesome I think you very much I will be down at the shaft with if you have any questions on after this talk please and
Energiedichte
Bit
Rechter Winkel
Computersicherheit
Dienst <Informatik>
Kraftfahrzeugmechatroniker
Punkt
Stichprobe
Automatische Handlungsplanung
Zahlenbereich
Kartesische Koordinaten
Dienst <Informatik>
Überlagerung <Mathematik>
Kraftfahrzeugmechatroniker
Datensicherung
Code
IT infrastructure library
Videokonferenz
Beanspruchung
Unterring
Datenmanagement
Software
Code
Mereologie
Computersicherheit
Demoszene <Programmierung>
Wort <Informatik>
Softwareentwickler
Schnitt <Graphentheorie>
Gerade
Resultante
TVD-Verfahren
Bit
Komponententest
Punkt
Datensichtgerät
Gruppenkeim
Versionsverwaltung
Schreiben <Datenverarbeitung>
Kartesische Koordinaten
Computerunterstütztes Verfahren
Extrempunkt
Binärcode
Kontinuierliche Integration
Eins
PROM
Einheit <Mathematik>
Prozess <Informatik>
Code
Fahne <Mathematik>
Einflussgröße
Softwaretest
Kraftfahrzeugmechatroniker
App <Programm>
Nichtlinearer Operator
Lineares Funktional
Sichtenkonzept
Oval
Computersicherheit
Güte der Anpassung
Quellcode
Biprodukt
Konfiguration <Informatik>
Teilmenge
Arithmetisches Mittel
Dienst <Informatik>
Verknüpfungsglied
Gruppenkeim
Rechter Winkel
Grundsätze ordnungsmäßiger Datenverarbeitung
Phasenumwandlung
Server
Identifizierbarkeit
Ordnung <Mathematik>
Programmierumgebung
Repository <Informatik>
Standardabweichung
Instantiierung
Web Site
Subtraktion
Selbst organisierendes System
Mathematisierung
Gebäude <Mathematik>
Dienst <Informatik>
Term
Polygon
Code
Lastteilung
Quellcode
Repository <Informatik>
Datennetz
Direkte numerische Simulation
Vererbungshierarchie
Speicher <Informatik>
Softwareentwickler
Ideal <Mathematik>
Demo <Programm>
Open Source
Kontinuierliche Integration
Systemverwaltung
Physikalisches System
Binder <Informatik>
Quick-Sort
Mereologie
Wort <Informatik>
Entropie
Streuungsdiagramm
Bit
Umsetzung <Informatik>
Punkt
Formale Sprache
Versionsverwaltung
Datenmanagement
Kartesische Koordinaten
Kraftfahrzeugmechatroniker
Information
Rechenzentrum
Metadaten
Datenmanagement
Einheit <Mathematik>
Prozess <Informatik>
Code
Urbild <Mathematik>
Tropfen
Phasenumwandlung
Auswahlaxiom
Softwaretest
Datenhaltung
Rohdaten
Gebäude <Mathematik>
Programmierumgebung
Teilmenge
Dienst <Informatik>
Rechter Winkel
Wurzel <Mathematik>
Server
Phasenumwandlung
Garbentheorie
Projektive Ebene
Information
URL
Versionsverwaltung
Programmierumgebung
Aggregatzustand
Instantiierung
Gewicht <Mathematik>
App <Programm>
Mathematisierung
Dienst <Informatik>
Kombinatorische Gruppentheorie
Code
Lastteilung
Knotenmenge
Cluster <Rechnernetz>
Ganze Funktion
Stochastische Abhängigkeit
Stochastische Abhängigkeit
Rechenzeit
Vektorraum
Elektronische Publikation
Quick-Sort
Bus <Informatik>
Wort <Informatik>
Systemidentifikation
Lineare Abbildung
Bit
Punkt
App <Programm>
Wasserdampftafel
Versionsverwaltung
Kartesische Koordinaten
IT infrastructure library
Datenhaltung
Lastteilung
Last
Informationsmodellierung
Datenmanagement
Softwaretest
Fahne <Mathematik>
Leistung <Physik>
Softwaretest
Nichtlinearer Operator
Graph
Datenhaltung
Gebäude <Mathematik>
Stichprobe
Rechenzeit
Linearisierung
Dienst <Informatik>
Rechter Winkel
Mereologie
Reelle Zahl
Zeichenkette
Instantiierung
Elastische Deformation
Last
Dienst <Informatik>
Punkt
Komponententest
Einheit <Mathematik>
Beweistheorie
Güte der Anpassung
Code
Faserbündel
Codebuch
Bit
Punkt
Mathematisierung
Summengleichung
Kartesische Koordinaten
Netzadresse
Datenhaltung
Homepage
Lastteilung
Last
Knotenmenge
RPC
Computersicherheit
Vererbungshierarchie
Gleitendes Mittel
Gerade
Phasenumwandlung
Hardware
Softwaretest
Elastische Deformation
REST <Informatik>
Speicher <Informatik>
Schlussregel
Symboltabelle
Instantiierung
Lineares Funktional
Biprodukt
Frequenz
Quick-Sort
Checkliste
CDN-Netzwerk
Teilmenge
Einheit <Mathematik>
Rechter Winkel
Last
Transcodierung
Modem
Schlüsselverwaltung
Streuungsdiagramm
Instantiierung
Standardabweichung
Stellenring
Komponententest
Punkt
Summengleichung
Kartesische Koordinaten
Komplex <Algebra>
Internetworking
Last
Einheit <Mathematik>
Standardabweichung
Vorzeichen <Mathematik>
Code
Computersicherheit
Radikal <Mathematik>
Stützpunkt <Mathematik>
Wurzel <Mathematik>
Figurierte Zahl
Default
E-Mail
Phasenumwandlung
Gerade
Funktion <Mathematik>
Softwaretest
Elastische Deformation
Lineares Funktional
Namensraum
Prozess <Informatik>
Kategorie <Mathematik>
Gebäude <Mathematik>
Stichprobe
Spieltheorie
Speicher <Informatik>
Programmierumgebung
Quellcode
Bitrate
Knotenmenge
Checkliste
Dienst <Informatik>
Magnetkarte
Forcing
Verschlingung
Einheit <Mathematik>
Rechter Winkel
Grundsätze ordnungsmäßiger Datenverarbeitung
Phasenumwandlung
Information
Repository <Informatik>
Verzeichnisdienst
Programmierumgebung
Faserbündel
Standardabweichung
Instantiierung
Faserbündel
Total <Mathematik>
EINKAUF <Programm>
Quader
Zahlenbereich
Schar <Mathematik>
Code
Differential
Knotenmenge
Weg <Topologie>
Verzeichnisdienst
Programmbibliothek
Installation <Informatik>
Datenstruktur
Konfigurationsraum
Grundraum
Hardware
Binärdaten
Videospiel
Elektronische Publikation
Konfigurationsraum
Default
Mailing-Liste
Lineares Funktional
Binder <Informatik>
Elektronische Publikation
EINKAUF <Programm>
Chipkarte
Integral
Chatten <Kommunikation>
Mereologie
Codierung
Wort <Informatik>
Zeitzone
Verkehrsinformation

Metadaten

Formale Metadaten

Titel Build Cookbooks and The Service Delivery Canvas
Serientitel ChefConf 2016
Autor Webber, Christopher
Lizenz CC-Namensnennung - Weitergabe unter gleichen Bedingungen 3.0 Unported:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen und nicht-kommerziellen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen und das Werk bzw. diesen Inhalt auch in veränderter Form nur unter den Bedingungen dieser Lizenz weitergeben.
DOI 10.5446/34618
Herausgeber Confreaks, LLC
Erscheinungsjahr 2016
Sprache Englisch

Inhaltliche Metadaten

Fachgebiet Informatik
Abstract So you have Chef Delivery, now what? This talk is a practical introduction to build cookbooks and how to figure out what should run in each stage. Have you ever found yourself wondering: "What is a build cookbook?" "Where should I put performance tests?" "How does this work with Docker?" If you have, this talk is for you. Come join us as we plan out a few projects in Delivery. We will start by using the Service Delivery Canvas, a tool for thinking about where things go in the pipeline, to layout our project. From there, we will take what we learned from the canvas and walk through building out a few applications, including examples from Chef's own infrastructure. We will also demonstrate multiple language runtimes and methodologies. Come be part of delivering all the things!

Ähnliche Filme

Loading...
Feedback