Bestand wählen
Merken

Operationalizing Unknown Cloud Deployments (In a Repeatable Fashion)

Zitierlink des Filmsegments
Embed Code

Automatisierte Medienanalyse

Beta
Erkannte Entitäten
Sprachtranskript
no 1 really Latin amazed by the turn out that standing-room-only so I think you guys all over for coming to this session this is my 1st time presenting action can't although Michael CEO's here lecture the topic today is operationalizing other people's poorly deployed complements and or as I like put it migrate haste repent at leisure but this is born out of a lot of experience we've had doing enterprise club migrations and systems architecture projects of the years but
why why should you believe me or us about when you say the 1st thing is we don't sell things so when I'm here to seller convincing a byproduct of any sort but we actually only do professional services that still in the money but we're vendor-neutral so we have companies like check that we like and we work with and we support that but we're not beholden to them and when we think that they're doing something wrong we are quick to point out that in our clients of the around for 11 years we started out doing and virtualizes center migrations the December louts and early can appreciate report that batch scripting and automation backup or there was thing on in most of us came out of the high speed backbone enterprise software world 1 of the things that I think is a kind of about us we're not the huge company but but but were big enough that we've made premier status with 2 of the 3 major cloud providers Google and Amazon Web Services I believe we are the only duty of consulting a professional services firm that is in the Premier consulting category with them all the others are major companies like Accenture and capture roles
of OK so may I suggest video about 11 years ago after I got lots of time in the eyes P and hosting it in backbone community but still 1 of the 1st dialog bias peas DSL eyes these in Seattle did that a bunch of ice mergers and acquisitions and learned a lot about other people's deployments through the process of consolidating these beta 9 different ice piece that we acquired with older legacy systems that had been built by and and a lot of people and both of course I also worked on Silicon Valley sneakers probably in that shows up and show that the member and season to the result that we have a data center in the garage indicate Bitcoin mining rigs for server that was my idea contribution project but also was heavily involved with the Seattle exchange which is a public I Utrecht switch in Seattle that is the world's largest free exchange point we move almost the terabit per 2nd of backbone traffic now across the 6 and I was when the founding were members of that and that involve about quite some time but also built a be distributed phonatory system for the cloud platforms behind the scenes we were conscious for clients but also for some writers of the and of course in Chap based so that only appropriate but also what he done for underground graduates used acquire claims that I had kids decided that was not a good idea anymore but I selected from scheme so the point is redundant but still travesties mistake against the picture by the way the top of my youngest over and the bottom is meeting a gigantic magnet in the Amazon it many years ago I lost track
so I've got off all of his revolting the head was crunchy to the body was squishy and then when you get it but I was because it was 1 of the worst things are evidence but it those right the OK so like I said you know we we've been recognized by a bunch these companies as not known as and we also because well shocks might system is popular up and time that's inside that's me you probably will find about some that but by no means do we only do these things these are just companies that we end up working with a lot because they tend to be big players in industry and ultimately were demanded right we're gonna Paul where customers wants to go because we're consultants and they pay us to use so OK and that marketing stop market Babylon about Cassio about what we do know until you you a demo of our product which has never been publicly Singapore at the end of this but what I wanna talk about today instead is the hell that is other people's stuff right so you know when you inherit somebody else's environment either at your job a new job because your hosting provider in this speedy but how do you rationalize that and take control of it and have some sense of predictability around it when happen time that wasn't even documented that was built by hand years ago and the people who built along the right so it was really
easy when we started out doing this and also has about 10 years ago we use always have this conversation with clients you know what you're trying to do and what your parameters right because we can do a really with prolog bodies it and if we take the bodies we can do pass that right but that gets expensive and if you wanna go hire a bunch of just sort of random bodies to fill seats that might be cheaper on a per unit basis but may take longer in the practice might so they to right which of those 2 you on that that you still work people used to be willing to accept that as a reasonable compromise that because everybody else still the same guy that was just the reality of the market I
it today I think it's gotten better but in part because of good tackling chat and in part just because expectations from consumers change I think durability is got really good by ability and mean Moroccans people's data that almost never happens unless you really really bad around and or you have some horrible you know inside sabotage there I guess but early high-visibility so I think you know we've got to the point where even legacy vertical the apps can be built and operated in a way that keeps them fairly stable and reliable although as was mentioned in the keynote this morning but you know there's this culture of sort of fear and paralysis around change management and around operations because the consequences of screen these big modeling systems that are so that right if you not the 1 mainframe the United Airlines outlined you just rented a bazillion people in the process of an animal dollars right don't know what to that or the person names on it and industry and so I started in the garden but I bet I'm having history that I've done some dumb dumb things of which you'll see soon actually but mn scalability so we got pretty good at building scalable systems but usually you get you know kind of 2 of the 3 you don't really get all 3 the problem is
that customers and I'm not talking about the people that pay me I'm talking about the people that pay are customers their expectations have changed format right and I use Facebook is a good example but it's by no means the only 1 of customers view this as person for most bears it's no longer your data it's no longer companies data in their minds those cute pictures of their kids on a tricycle belong to them even though licensing wise maybe they belong to they always have a always the little pictures no matter where they are they wanna show that the monogram lot whenever wherever they don't want the system to be slowly going to go down they want to work all the time they don't want you to leak their personal quota library fileshar lose they expect all this stuff to just work automatically when it doesn't work they get really really upset but if you're trying to share some cute could pick grammar and it doesn't work you to base time with grandma doesn't work it's a it's an incredibly upsetting and frustrating experience especially non-technical users right in the reality is that the majority of the consumers in the world are not very technical and if you explain to them well there was this that the other and I lost a data they don't hear this that the other they hear what you mean you lost right so I think and really really challenging spot where the implicit assumption that the customers carry into a transaction with any kind of a vendor these days is that they're going to get all the stuff right all
the time so what companies do in practice as is my older sisters Isaac Isaac getting into the pool for the 1st time just decided to jump right in and see I liked it and I would say this pretty much sums up lifting shipped in my mind so that the ship for those unfamiliar means taking some VM or server that has been running and somehow moving it over into some other persons environment companies environment and letting go and playing with the knobs levers to get to work in the networks and that's considered done and I posit that this leads to but that serial even though it's not quite as instantaneous you realize instantly that jumping in the pools but probably not gonna work out the way that would most people lived in shift and get to work run in that state for some period of time book or the real misery media why is this a bad idea OK so you guys are all sort of shepherds so I think you probably know a lot of this already but them quickly take through it just to make sure that you covered it up 1st and foremost if you have machines that humans built and maintained by hand over time they get cracking stuff piles up versions get where an upper versions in your ability to accurately describe this data that system recreated in a given time is massively impaired couple that with all of the recent revelations courtesy of snow than others about the extent to which not just that quote and quote bad guys but the good guys are masked employing malware Ricketts even at the hardware level I think when you have the atoms that have an unknown operational history and have been running for months or years the odds of them becoming compromised in a way that you never find barring network traffic analysis I think that goes way so I think short-lived VM's trump long ones of only because there's less properties is last time elapsed from when a compromise occurs to when it so we got that up the bigger than that I think is that a lack of repeatability that means that when you need it most you may not be able to recover right I think we all have been through another operational experience to know that in the real world Dr RBC plans exist on paper they get exercised infrequently imperfectly if at all sometimes those exercises are not a full pale over and bill that just sort of a dry run a dress rehearsal and and a lot of companies will say things like well it's OK because we have a snapshot of things break we can just roll back to the snapshot which is great right up until that doesn't fix the problem right so many times people say well we'll just roll back the but services and like what was in here before as as a matter of matter was there before just having a snapshot is not enough to recreate the system state to a dwindled quantifiable jet right the and the last 1 I Band-Aids become fossils right if you have humans in their applying bandages under the gun to a morning on new Year's no one's going to go back and fix those things in up and sooner or later someone's gonna forget and then something that break in unit of level cycle in the 2nd incident of a human trying to figure out fundamentally why it's broken rather than making it yourself so it's even worse than this because and I again were friends with a lot of other writers but we do not represent them or their interest that they want you to do lifting shift by large because it accelerates revenue from right so if you move BMC into the cloud environments and go to the meter starts spinning revenue numbers go up Wall Street smiles everybody wins except I would argue the customer there are corner cases where lifting ship is not evil but but those are carefully considered and uh I think Bible decisions as opposed to using Lipton ship by default which is what we see in the field a lot of companies doing a lot of them in their mind is less skip this step in the cloud and we'll come back and way I would argue having been through a lot of these now that kind of all stages of the public cloud error in and the steps managed hosting that came before it and it turns out that even though it sounds like it would be easier to run a and through converter and maybe make some tweaks to its you often end up spending more time energy dealing with driver issues the volume replication issues or whatever it may be but it would it ends up being the case that even if you had to manually redeploy that probably would have been more efficient they're just trying to suck the thing into pick your cloud and it up and the last thing I think we all know this there's no such thing as doing it once cloud you're going get the something wrong even if the addressing scheme wrong you going to get the new Amazon account you're gonna get something that's going to necessitate redeploying even if you think it's done it's never done it couldn't do it twice the price of an entity with ways of writing as well just take the time to write some automation around do and yet as a managed hosting provider of which we are 1 but we're stuck with that right because customers come to us and say help us help us is a common scenario help us help us the guy who move as an Amazon is gone there is no documentation the system is running in production in airplanes at 30 thousand think it's on a pilot it's working but we don't know how much gas it's gotten with a low whereas with maintenance and and so you know we collectively and my little company are stuck with us right but the clever about is what they're spending buckets of money driving it because he and the view is a land grab they viewed as the customers in will also lot later because whichever plow they land on the instead and most of these companies have already adopted right a lot of companies the interface with are no longer in the thinking about cloud stages there in the we've already got stopped running in production even though we don't really have that correctly what we do have this was the case the last point when I was a bias and web hosting person and it's certainly the case today are trying to be the OPS staff for a thousand deployments than a thousand different ways by a thousand different humans is almost impossible right these are all 1 with their own little tweaks to remove over collapsed a little scripts in crime jobs and whatever else and and trying to operationalize that is really really hard I
other painful reality of 100 per cent of everything including the humans like myself in uh in practice right if you have anything that runs for a long period of time something horrible happened that we acquire above the earthquake there be a nuclear incident on this case that any given the Philippines and wrinkled and why the question Lovász tantalize they call it run but I assure you it's not it's something far far far more dangerous the other thing I think
about here is a scale so I like to pick on Airbus a little bit of the 380 obviously a miracle of engineering it's so big in fact that they had to make special airplanes just move the parts to make the EI 380 nm in maybe a 382 had a wide the taxiways had put new jetways again and they had to have a whole new slew of facilities to accommodate something that had scaled beyond what the rest of the industry and the side of the natural vertical scaling limit for aircraft what it's cool but boy that's a that's a really extreme corner there's not that many treaties there's not that many airports that can even accommodate 1 and it takes a heck of a lot to build 1 of these things up with the past right that you look at tassels approach to the factory and contrast that to be a 380 I think it's kind of an interesting thing right the 3 D is this giant massive vertically scaled system that it blows up you killed 700 people and cost a billion dollars and see the bigger right every single time right you cannot afford to have these things the back the bus and the and other built by handedness customizations in the different airlines 1 configurations and although the perspective of Tesla if you guys have been watching this fascinating stuff on the batteries are and how they're doing that but I think the key thing here is that many you collectively get a factory as the product of the product is going to be made more than once so we're not just going take 1 of these things really make lots of money and automate the crap out of all of them and iterate on them and we're make lots and lots of batteries in put batteries in cars and powerpacks some of them are gonna fail is the dancing was is the cheap ones but at the end of the day it's a automation scale project but instead of 8 let's build a perfect thing that never balls out the sky and can scale to impossible limits because we can have a pressure right all the cool but I would argue that the latter is probably more forward-looking from they overall engineering interest so how we pick some that's right there's all these deployments out their customers bodies that money they're not going to turn down my whole company runs on his legacy vertical line of business European up and moved it into the con Google today so it's running on Google Cloud even though I don't really know how it runs and I don't really know what's going on and things just got worse right I think a lot of this has to do with the same fundamental design flaw that led to this is a condition about away but but any kind of nuclear incident like this where the systems are built with a fundamentally flawed assumptions and that is that humans will be able to maintain positive control over the system at all times so Fukushima had triply redundant cooling systems all active that grid power they had diesel generators in any of their own power the nuclear reactor that turns out that the triple redundancy doesn't mean anything given tsunami comes in like so out right so that the big problem was they thought that they could maintain operational control and the date that assumption and the engineering class this is what companies in the non cloud world do with their IT they make the assumption implicitly that they can maintain these things and fix them and it they all that they can come run fast enough to press the button before the thing melts down and that sooner or later you on a personal ratings asking along the front so you guys probably already know
some or all this but I'll quickly recap because I think these are important if you're building apps for the cloud or your refactoring for the cloud but there's always compromise is to be had in no small part because you don't have good visibility or control over the underlying network and systems the structure but I think the on the 1st point Google has taught us among others is good enough really is easier than you think so think about Gmail Gmail sometimes will say what sorry I can't load your male right now I'm sorry you access to their customers don't feel like they're getting a 500 air but maybe your mailboxes offline promote I think availability is over estimated most people's minds I think people assume that they need five-nines when in reality getting to that is astronomically difficult expensive and in reality if you can preserve the endpoint and the illusion of of time availability even at the back and failures but people are much more forgiving intolerant that the bigger than people often don't fully comp contemplate and understand but is they lost so they'll say things like well it it breaks we have OK so how often you run your backups well we run them every 12 hours so you test them every 12 no so what happens at the back of is that all it will be well OK let's hope so so I think if you are willing to write down in 7 so what is your tolerance for data loss and how quickly you have will recover you can make a lot of good engineering decisions and trade-offs that other non-technical people can understand about what that means in practice and I'll give you an example that the boss says 0 data loss absolutely unequivocally not 1 transaction loss this is the Sun Master you cannot lose 1 credit card transaction that's fine but that means synchronously replication which is very very expensive to do at scale right but if you say look I'm willing to lose no more than in minutes of data and I understand the cost of that and I can prove at all times that that is the worst-case outcome that's going to occur no matter what that's a different scenario and oftentimes it's much much less expensive than that trying to build a system and repels right I think scalability you know obviously running big but monolithic but a quiz collapses not on running lots of parallel production deployments is better with some kind of a traffic management load balancing during part of it not all but legacy apps can be retrofitted easily this the ones that can't can block the use have to live with it against gone but many of them you can actually sort of wrapped orchestration frameworks around and run multiple copies in shot of the workload across them and we got a lot of this work for extending the life of vertical axis that need to keep running at increasing scale but without trying to divert was killed her and then uh security I'm very much a pessimist and we take the assumption breach philosophy which is to say everything is compromised that soup-to-nuts including the hardware that using right now but we don't know how many different parties have compromised it we just know there's at least 1 of them and probably more than 1 and so are poker ships instead to blast radius so when it occurs so how do we limit the destruction that's inevitable we don't want but your personal i message chat history link to the Internet because that would be absolutely devastating to Apple so they're going to great lengths to limit the blast radius if and when I messages compromise to make sure that there's hopefully please never a you know that in a moment with a bazillion people's II message accounts getting them to be the real solution all this at the end of the day is microservices we define that internally as having 3 components interaction where stop this part the world could be API and points could be points can be mobile apps are coordination so some system that deals with asynchronous event handling of the that pulling the that pub sub b that just guy events coming in and then a bunch of back and services this is usually where we try to relegate legacy applications so all pick on alaska airlines bundle industrial America at this point is employment but Alaska Airlines did a national thing where they took all their legacy airplane you know Europe's stuff that probably runs on mainframes back here and they really done a great job wrapping their web interface in mobile user experience the check and experience with really did interaction presentation-layer start any ability over here to deal with transient there's of various forms so even though I'm guessing on the back and it's an ancient system it doesn't feel like you're using Saber on American it feels like using a modern know properly designed when the
thing we see companies get wrong all the time almost down the line almost every single 1 of them get this wrong I don't know why I think that there is an implicit assumption that if you move step to the cloud that now the network is somebody else's problem a lot of these companies also made really bad design assumptions and the and the system's architecture like here's the app server and here's a database server and there's a wire connecting them or there's a switch between and all of a sudden they take things like an observer moving to the cloud that leave the database server behind now that traffic is going across a wide area network with higher latency and they can't quite figure out why the apple slot it's like well you know we so here's the thing right but network is more important before and there's no way to make that somebody else's problem entirely but things like Rocky if you guys have seen this year is the company Cisco acquired fascinating technology I'm absolutely convinced that the future of network engineering and I used to be the the GP guided there an appeal important special case I knew it nobody else did a is absolutely the right way to go but not because of them as a company that because of the approach and the general approach here is that they take all of the control plane and can be management and analytics make that sarsa they sell you the box the box is basically the bottom eyes and just contacts the mother ship to get configuration this lets you do all sorts of things like API integrations and lets you do things like create templates that uniformly deployed you guys have heard this story before it basically lets you applied good practices in configuration management In the plant automation to you that which most companies absolutely neglected I can't tell you how many times i . that's 5 7 8 years old running on production switches and Michael why is this what it's stable it works in the I guess that's technically accurate it is but what happens when when was the last time anybody exercise any of their operational processes around network failures it's amazing to me how little attention this gets in
practice right so I don't some of the gloom that a lot of stuff isn't it straight and the 1 thing companies and got gazillions of dollars wrapped up in investments that they're not you're right off so a lot of them have spent big money on data center on whatever else and I feel like uh all these problems are just getting
worse over time so how do we solve this are attempts this as I said the 1st time that we're show this in public but is to build a platform for making this less error-prone and less human driven but the idea here is to make this as valuable as it can to everyone we want to deliver these automations 1st and foremost we're not interested in pretty wise and class American than those who are make it so that customers can virus so we can leave value behind we will give you something preparation you can virus and the but really what we're trying to do is take all these painful lessons that we learned over the years doing this and consulting basis and mn service basis and turn into something sort of like excessive so here is the idea super super simple I think that we have a bunch of stuff of which was probably featured but that will colonize customers existing employment there structure planets but this could be on print the cloud and by doing this we automatically set up an entire analytics pipeline learning pipeline visualisation etc. and we do it using open-source software so that the customer can virus and keep running stuff and not have to pay a skip they don't think we're bringing up the table so here's an example of planetary data that's being outputted by the system in command which when you probably use obvious system metrics nothing too exciting here except that all of this can be done now without a human touching anything in an environment that we've never contacted
or and we're working really hard on smart our discovery so how do we sort of did the Chadian and then figure out as much as we can about everything as we possibly can including and a key thing any existing um monitoring or application ones going right we wanna support but more clever right now this is really kind of US centric is that's what the market is going after but we wanna make this agnostic of the real goal here on the medicine
is the analyst so what we really want to do is teach people something that I think 99 per cent of companies have no idea how to actually do in practice and that is due machine learning on the system kilometers right so you can extract and learn this because I did this for want of others and it took years to really understand it but if you can record every single data point about every single thing a and B that a machine learning you can get way way way better operations but in fact you can often see things before they go wrong can you can prevent outages I'm not just talking about the disk is going and talking about differences in the way applications that interact with each other so the real goal here at the end of the day is to bring this down market and make sure that every company competitiveness to the
extent they want to do so with that said I I'm going to attempt to play video here this is a time what because it takes a while to actually deploy these things so on a
walk you through it but ignore the crop clumsy UI here because this is just sort of the prototype burn and stuff so very bad so you know security groups in key there's an instance types and some that's very exciting I know you can see the 1 getting filled unfortunately it's kind of problem on the screen and on the case so you'll see here we got a so that we're gonna go ahead modern art of so we all the given it at this point is an Amazon account and some that were interested in and by doing that we have approved a process that will
go in behind the scenes launch a instance you can see it's called on discovery there but check is used on the instance to play in this case are score which is an open source of monitoring package that we have done a lot of work with over the years I and the idea here is simple we have a basic configuration that tries to do as much as it
can but 2 out of discover everything you can about the environment and then push that back up in assessors so again think about rocky took the control plane for networking and move that into assess service we're trying to take the control playing the monitoring telemetry learning analytics all of that and move that back up into the mother ship so that companies don't have to run it unless they want to know about so you can see here Schepers running the ASR is running trying to find things and now populated on the left here we discovered a bunch of
assets so that you can see that the artist every
instance was automatically terminated were building a big back in API using slanted I know that will give users customers and our own tooling access again think of micro-services we're not trying to lock anybody and using our tooling our scripting our front and whatever we want to expose as much of this is possible to are customers but so that they can repackaging reuse all these components in the ways that make sense for their business that we're not trying to lock people into specific monitoring tool of visualization tool or orchestration framework that we're just trying to give them the option but not the obligation of having these things deploy automatically for them and operated born under contract wish not required expected so
now we moved on to actually deploying the real that so chaperoning once again this time but we are deploying a persistent instance that is going to run these ask application and the data collection alerting thresholds monitoring visualization what have you but and if at the end of the ship right here the client said you guys are stupid you're fired that spiny can still keep all the work that's been done to date because it's in their account their environment they have the credentials and and we have no further interest in it so we expect by the way to include far more than just an austere suite of things that we will gladly know deploy wire-wrap connectance Aceh by for you but we also keep in mind this idea that at any point we should be expandable we should not be mandatory you keep using any of superstructure because after all this is open source
software and is your environment so now we have a bunch of devices here that are actively being monitor the and you can see there already meeting tickets and this and ask this literally takes just minutes to wire up but also large and page duty wires and slacks you get alerts and notifications in this case this is a man services provide customer so you can see that the organization of the is there
the line in the source for what happens see that's already been pre-configured with all your
devices that you are discovered and whatever else so and again these are the events that
generating tickets coming in but relegate so without any human interaction or as in the community strains winner and credentials or whatever else were able to tell you some things
and if you wait 20 minutes which really password here
we also find that all of the telemetry we collect from the OS and other sources I think CloudWatch think your existing monitoring tools think BPM tools that gets steady and to a lesser search logs dash and combined for visualization analysis and you guessed it operative analytics machine learning functions so this
is the general idea behind what we're building a we think this is the right approach Given that there's only so much you can do to forcibly colonizer
models the deployment especially if the the people aren't there to to help you do it
but then with that alright well if anybody's looking for many years and the whole holding and happy to take any feedback around intervals in DSM great does shut up it
Migration <Informatik>
Gruppenoperation
Projektive Ebene
Physikalisches System
Cloud Computing
Unternehmensarchitektur
Resultante
Subtraktion
Prozess <Physik>
Punkt
Freeware
VHDSL
Adressierung
EDV-Beratung
Computer
Dienst <Informatik>
Datensicherung
Data Mining
Rechenzentrum
Demoszene <Programmierung>
Service provider
Client
Weg <Topologie>
Geschlossenes System
Software
Migration <Informatik>
Minimum
Skript <Programm>
Operations Research
Geschlossenes System
Kategorie <Mathematik>
Nummerung
Physikalisches System
Cloud Computing
Quick-Sort
Motion Capturing
Dienst <Informatik>
Server
Projektive Ebene
Cloud Computing
Stapelverarbeitung
Unternehmensarchitektur
Verkehrsinformation
Verschiebungsoperator
Parametersystem
Perspektive
Umsetzung <Informatik>
Demo <Programm>
Kontrolltheorie
Systemplattform
EDV-Beratung
Dienst <Informatik>
Biprodukt
Quick-Sort
Service provider
Arithmetisches Mittel
EDV-Beratung
Client
Einheit <Mathematik>
Prognoseverfahren
Geschlossenes System
Prozess <Informatik>
Rechter Winkel
Datennetz
Basisvektor
Rechenschieber
Randomisierung
Schreib-Lese-Kopf
Facebook
Punkt
Prozess <Physik>
Skalierbarkeit
Mathematisierung
Formale Grammatik
Erwartungswert
Skalierbarkeit
Geschlossenes System
Computersicherheit
Programmbibliothek
Modelltheorie
Touchscreen
Nichtlinearer Operator
App <Programm>
Güte der Anpassung
Physikalisches System
Quick-Sort
Großrechner
Arithmetisches Mittel
Transaktionsverwaltung
Rechter Winkel
Mereologie
Identitätsverwaltung
Dateiformat
Filesharing-System
Umsetzung <Informatik>
Gewichtete Summe
Punkt
Versionsverwaltung
Inzidenzalgebra
Service provider
Übergang
Eins
Einheit <Mathematik>
Geschlossenes System
Prozess <Informatik>
Total <Mathematik>
Datenreplikation
Computersicherheit
Meter
Skript <Programm>
Virtuelle Adresse
Gleitendes Mittel
Default
Schnittstelle
Nichtlinearer Operator
Hardware
Sichtenkonzept
Gruppe <Mathematik>
Datennetz
Kategorie <Mathematik>
Malware
Nummerung
Quantifizierung
Malware
Biprodukt
Frequenz
Entscheidungstheorie
Arithmetisches Mittel
Datenfeld
Wurzel <Mathematik>
Rechter Winkel
Server
Cloud Computing
Fehlermeldung
Aggregatzustand
Ausnahmebehandlung
Stab
Zahlenbereich
Ordinalzahl
Spezifisches Volumen
Systemprogrammierung
Virtuelle Maschine
Benutzerbeteiligung
Zufallszahlen
Iteration
Reelle Zahl
Spezifisches Volumen
Verband <Mathematik>
Maßerweiterung
Analysis
Serialisierbarkeit
Verschiebungsoperator
Sichtenkonzept
Cloud Computing
Quick-Sort
Energiedichte
Druckertreiber
Hypermedia
Dreiecksfreier Graph
Brennen <Datenverarbeitung>
Einfügungsdämpfung
Bit
Punkt
Momentenproblem
Natürliche Zahl
Skalierbarkeit
Kartesische Koordinaten
Inzidenzalgebra
Datensicherung
Internetworking
Eins
Skalierbarkeit
Geschlossenes System
Prozess <Informatik>
Datenreplikation
Computersicherheit
Kontrast <Statistik>
Parallele Schnittstelle
Gerade
Web Services
Prinzip der gleichmäßigen Beschränktheit
App <Programm>
Zentrische Streckung
Dicke
Hardware
Prozess <Informatik>
Datennetz
Kontrolltheorie
Computersicherheit
Gebäude <Mathematik>
Mobiles Internet
Güte der Anpassung
Biprodukt
Bitrate
Ereignishorizont
Großrechner
Entscheidungstheorie
Arithmetisches Mittel
Dienst <Informatik>
Transaktionsverwaltung
Druckverlauf
Generator <Informatik>
Benutzerschnittstellenverwaltungssystem
Rechter Winkel
Chatten <Kommunikation>
Konditionszahl
Nuklearer Raum
Kategorie <Mathematik>
Projektive Ebene
Cloud Computing
Refactoring
Koordinaten
Message-Passing
Subtraktion
Teilmenge
Hecke-Operator
Relationentheorie
Klasse <Mathematik>
Virtuelle Maschine
Interaktives Fernsehen
Dienst <Informatik>
Identitätsverwaltung
Framework <Informatik>
Wiederherstellung <Informatik>
Knotenmenge
Bildschirmmaske
Multiplikation
Perspektive
Inverser Limes
Datenstruktur
Parallele Schnittstelle
Leistung <Physik>
Fundamentalsatz der Algebra
Radius
Videospiel
Benutzeroberfläche
Einfache Genauigkeit
Physikalisches System
Binder <Informatik>
Cloud Computing
Quick-Sort
Inverser Limes
Chipkarte
Beanspruchung
Last
Komponente <Software>
Identitätsverwaltung
Mereologie
Bus <Informatik>
Faktor <Algebra>
Mittelwert
Ebene
Lokales Netz
Server
Multiplikation
Prozess <Physik>
Quader
Computer
Analytische Menge
Unternehmensarchitektur
PROM
Intel
Stabilitätstheorie <Logik>
Rechenzentrum
Geschlossenes System
Datennetz
Weitverkehrsnetz
Luenberger-Beobachter
Konfigurationsraum
Figurierte Zahl
Kontrolltheorie
Gerade
Nichtlinearer Operator
App <Programm>
Datennetz
Kontrolltheorie
Datenhaltung
Template
Güte der Anpassung
Speicher <Informatik>
Biprodukt
Hybridrechner
Cloud Computing
Quick-Sort
Schlussregel
Integral
Konfigurationsverwaltung
Weitverkehrsnetz
Ebene
Rechter Winkel
Identitätsverwaltung
Server
Cloud Computing
Unternehmensarchitektur
Innerer Punkt
Chipkarte
Computervirus
Hochdruck
Kartesische Koordinaten
Dienst <Informatik>
E-Mail
Systemplattform
Eins
Web Services
Geschlossenes System
Benachrichtigungsdienst
Vererbungshierarchie
Visualisierung
Datenstruktur
Lambda-Kalkül
Web Services
Linienelement
Prognostik
Systemplattform
Quick-Sort
Schlussregel
EDV-Beratung
Auswahlaxiom
Rechter Winkel
Basisvektor
Cloud Computing
Tabelle <Informatik>
Web Services
Nichtlinearer Operator
Verschiebungsoperator
Subtraktion
Punkt
Systemplattform
Prognostik
Einfache Genauigkeit
Kartesische Koordinaten
Migration <Informatik>
Videokonferenz
Videokonferenz
Virtuelle Maschine
Programmfehler
Geschlossenes System
Mini-Disc
Cloud Computing
Maßerweiterung
Operations Research
Demoszene <Programmierung>
Punkt
Prozess <Physik>
Open Source
Computersicherheit
Datentyp
Gruppenkeim
Konfigurationsraum
Schlüsselverwaltung
Quick-Sort
Instantiierung
Prototyping
Ebene
Web Services
Datennetz
Kontrolltheorie
Geschlossenes System
Einheit <Mathematik>
Analytische Menge
Einfach zusammenhängender Raum
Suite <Programmpaket>
Schwellwertverfahren
Punkt
Open Source
Kartesische Koordinaten
Framework <Informatik>
Design by Contract
Konfiguration <Informatik>
Client
Geschlossenes System
Komponente <Software>
Visualisierung
Instantiierung
Dienst <Informatik>
Geschlossenes System
Software
Selbst organisierendes System
Quellcode
Gerade
Homepage
Metropolitan area network
Lineares Funktional
Virtuelle Maschine
Nichtlinearer Operator
Endlicher Graph
Visualisierung
Maßerweiterung
Analytische Menge
Quellcode
Programmbibliothek
Sichtenkonzept
Login
Ereignishorizont
Analysis
Offene Menge
Rückkopplung
Modelltheorie

Metadaten

Formale Metadaten

Titel Operationalizing Unknown Cloud Deployments (In a Repeatable Fashion)
Serientitel Chef Conf 2017
Autor Reimer, Jared
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/34598
Herausgeber Confreaks, LLC
Erscheinungsjahr 2017
Sprache Englisch

Inhaltliche Metadaten

Fachgebiet Informatik
Abstract Cascadeo will demonstrate how they use Chef to deploy and manage operational infrastructure in multi-cloud environments for their managed services customers. Chef-driven automation deploys, configures, populates inventory, and validates the telemetry application stack in a distant customer-owned cloud account. Our engineers will demonstrate visualization and reporting based on this data: tickets, device performance graphs, etc. as well as connectivity to services like Slack and PagerDuty for notification and escalation. Companies struggling with operational, monitoring, performance and analytics challenges will find this presentation particularly engaging, as will individuals interested in self-healing distributed systems at scale.

Ähnliche Filme

Loading...
Feedback