{"id":55735,"date":"2020-01-27T00:00:00","date_gmt":"2020-01-26T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/eshhe-raz-o-devops-i-sre"},"modified":"2020-02-18T14:03:52","modified_gmt":"2020-02-18T11:03:52","slug":"eshhe-raz-o-devops-i-sre","status":"publish","type":"post","link":"https:\/\/prohoster.info\/da\/blog\/administrirovanie\/eshhe-raz-o-devops-i-sre","title":{"rendered":"Endnu engang om DevOps og SRE","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Inspiration from the chat discussion AWS Minsk Community<\/a><\/noindex><\/p>\n

Recently, there have been real battles over defining the concepts of DevOps and SRE.
\nAlthough discussions on this topic have become quite repetitive, including for me, I decided to present my perspective to the Habr community. Those who are interested, welcome under the cut. Let it all begin anew!
\n<\/a><\/noindex><\/p>\n

Background<\/h4>\n

\nSo, in ancient times, there lived a separate team of software developers and server administrators. The former happily wrote code, while the latter, using various warm and affectionate words towards the former, configured servers, occasionally visiting the developers and receiving the all-encompassing response of \"it works on my machine.\" The business awaited software, everything was idle, occasionally breaking down, and everyone was on edge. Especially the one who was paying for all this mess. A glorious, nostalgic era. But you're already aware of where DevOps originated. <\/p>\n

The Birth of DevOps Practices<\/h4>\n

\nThen came serious gentlemen who declared \u2014 this is not an industry, this way of working is unacceptable. They brought in life cycle models. For example, the V-model.<\/p>\n

\"Endnu
\nSo, what do we see? The business comes with a concept, architects design solutions, developers write code, then \u2014 failure. Someone tests the product in some way, someone delivers it to the end user, and somewhere at the end of this miracle model sits a solitary business client waiting for promised results. It was concluded that methods were needed to streamline this process. They decided to create practices that would implement them.<\/p>\n

A Lyric Digression on What Practice Is<\/b>
\nBy practice, I mean a combination of technology and discipline. An example \u2014 the practice of describing infrastructure as code using Terraform. Discipline refers to how to describe infrastructure as code, which is in the developer's mind, while the technology itself is Terraform.<\/p>\n

Og de besluttede at kalde dem DevOps-praksisser - jeg tror, de mente fra Development til Operations. De opfandt forskellige komplicerede ting - CI\/CD-praksisser, praksisser baseret p\u00e5 IaC-princippet, tusinder af dem. Og s\u00e5 gik det, udviklere skriver kode, DevOps-ingeni\u00f8rer transformerer systembeskrivelsen i form af kode til fungerende systemer (ja, kode er desv\u00e6rre kun en beskrivelse, men ikke selve systemet), leveringen k\u00f8rer, og s\u00e5 videre. Tidligere administratorer, der har mestret de nye praksisser, har stolt omd\u00f8bt sig til DevOps-ingeni\u00f8rer, og s\u00e5 gik det hele i gang. Og der blev aften, og der blev morgen... undskyld, ikke derfra.<\/p>\n

Det hele er igen ikke til at tro.<\/h4>\n

\nBare n\u00e5r alt faldt p\u00e5 plads, begyndte forskellige snedige \"metodologer\" at skrive tykke b\u00f8ger om DevOps-praksisser, der stille og roligt opstod debatter om, hvem den berygtede DevOps-ingeni\u00f8r egentlig er, og hvad DevOps er - en produktionskultur, igen voksede utilfredsheden. Det viste sig pludselig, at levering af software er en absolut ikke-triviel opgave. Hver udviklingsinfrastruktur har sin egen stak, et sted skal det opsamles, et andet sted skal milj\u00f8et implementeres, her er tomcat n\u00f8dvendigt, h\u00e9r er der behov for en endnu mere kompliceret m\u00e5de at starte - generelt er det komplekst. Og s\u00e5 var problemet, underligt nok, is\u00e6r i organiseringen af processerne - denne leveringsfunktion blev som en flaskehals hindret processerne. Desuden blev driften (Operations) ikke annulleret. Den er ikke synlig i V-modellen, og der er stadig hele livscyklussen til h\u00f8jre. I sidste ende skal infrastrukturen ogs\u00e5 vedligeholdes, der skal kigges p\u00e5 overv\u00e5gningen, og h\u00e6ndelser skal h\u00e5ndteres, og s\u00e5 skal der ogs\u00e5 tages sig af leveringen. Det vil sige, at man skal st\u00e5 med det ene ben i udviklingen og det andet i driften - og pludselig blev det til s\u00e5dan en Development & Operations. Og s\u00e5 kom der ogs\u00e5 et vildt hype om mikroservices. Og med dem begyndte udviklingen fra lokale maskiner at flytte til skyen - pr\u00f8v at fejlfinde lokalt, hvis der er titusinder og hundredtusinder af mikroservices, s\u00e5 bliver kontinuerlig levering et middel til overlevelse. For en \"lille beskeden virksomhed\" kan det v\u00e6re fint, men alligevel? Hvad med Google?<\/p>\n

SRE fra Google<\/h4>\n

\nGoogle kom, spiste de st\u00f8rste kaktuser, og besluttede, at vi ikke har brug for det, vi har brug for p\u00e5lidelighed. Og p\u00e5lidelighed skal styres. S\u00e5 han sagde, at vi har brug for specialister, der kan styre p\u00e5lideligheden. Han kaldte dem SR-ingeni\u00f8rer og sagde: 'Her er alt, g\u00f8r det som s\u00e6dvanligt, godt. Her er SLI, her er SLO, her er monitorering. Og han pegede hen imod driftsafdelingen. Og han kaldte sin 'p\u00e5lidelige DevOps' SRE. Det ser rigtigt ud, men der er en beskidt hack, som Google kunne tillade sig \u2014 at ans\u00e6tte folk til SR-ingeni\u00f8rstillinger, som havde kvalifikationer som udviklere og som ogs\u00e5 havde lidt erfaring med at forst\u00e5 fungererende systemer. Problemet er, at Google selv har udfordringer med at ans\u00e6tte s\u00e5danne mennesker \u2014 hovedsageligt fordi han konkurrerer med sig selv \u2014 man skal jo beskrive forretningslogikken et eller andet sted. Leveringen blev overladt til release-ingeni\u00f8rer, SR-ingeni\u00f8rer styrer p\u00e5lideligheden (naturligvis ikke direkte, men ved at p\u00e5virke infrastrukturen, \u00e6ndre arkitekturen, overv\u00e5ge \u00e6ndringer og indikatorer, h\u00e5ndtere h\u00e6ndelser). Smukt sagt, kan man skrive b\u00f8ger<\/a><\/noindex>. Hvad skal man g\u00f8re, hvis man ikke er Google, men p\u00e5lidelighed stadig bekymrer en?<\/p>\n

Udvikling af DevOps id\u00e9er<\/h4>\n

\nHer kom Docker, som voksede ud af lxc, og derefter forskellige orkestreringssystemer som Docker Swarm og Kubernetes, hvor DevOps ingeni\u00f8rer kunne \u00e5nde lettet op \u2014 en enhed af praksis har forenklet levering. Den forenklede det s\u00e5 meget, at det blev muligt endda at overgive levering til udviklerne \u2014 hvad er der i deployment.yaml. Containerisering l\u00f8ser problemet. Og modenheden af CI\/CD systemer er allerede p\u00e5 niveauet, hvor man skriver \u00e9n fil, og s\u00e5 k\u00f8rer det \u2014 udviklerne klarer det selv. Og her begynder vi at tale om, hvordan vi laver vores SRE, med ... ja, hvem som helst. <\/p>\n

SRE ikke hos Google<\/h4>\n

\nN\u00e5 ja, vi har givet levering videre, og det ser ud til, at vi kan \u00e5nde lettet op og vende tilbage til de gamle gode tider, hvor administratorer overv\u00e5gede CPU-belastningen, fintune systemerne og stille og roligt n\u00f8d noget ukendt fra krus i stilhed og ro... Stop. Vi gjorde ikke alt dette for det (hvilket er en skam!). Det viser sig pludselig, at i Googles tilgang kan vi sagtens tage nogle gode praksisser \u2014 det er ikke CPU-belastningen, der er vigtig, og ikke hvor ofte vi skifter diske, eller hvordan vi optimerer omkostninger i skyen, men forretningsmetrikker \u2014 de samme velkendte SLx. Og ingen har fjernet ansvar for infrastrukturforvaltning, vi skal h\u00e5ndtere h\u00e6ndelser, holde vagt i ny og n\u00e6, og vi skal generelt v\u00e6re opdateret p\u00e5 forretningsprocesser. Og drenge, begyd at programmere p\u00e5 et ordentligt niveau, Google har allerede ventet p\u00e5 jer.<\/p>\n

For at opsummere. Pludselig er du allerede tr\u00e6t af at l\u00e6se, og du kan ikke vente med at klage til forfatteren i kommentarfeltet. DevOps som praksis for levering har v\u00e6ret, er stadig og vil altid v\u00e6re der. Og det forsvinder ikke nogen steder. SRE som et s\u00e6t driftpraksisser g\u00f8r denne levering succesfuld.
\n
Kilde: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041f\u043e \u043c\u043e\u0442\u0438\u0432\u0430\u043c \u0434\u0438\u0441\u043a\u0443\u0441\u0441\u0438\u0438 \u0432 \u0447\u0430\u0442\u0435 AWS Minsk Community \u0412 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0435\u0435 \u0432\u0440\u0435\u043c\u044f \u0440\u0430\u0437\u0433\u043e\u0440\u0430\u044e\u0442\u0441\u044f \u043d\u0430\u0441\u0442\u043e\u044f\u0449\u0438\u0435 \u0431\u0438\u0442\u0432\u044b \u043d\u0430 \u043f\u0440\u0435\u0434\u043c\u0435\u0442 \u043e\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u0438\u044f \u043f\u043e\u043d\u044f\u0442\u0438\u044f DevOps \u0438 SRE. \u041d\u0435\u0441\u043c\u043e\u0442\u0440\u044f \u043d\u0430 \u0442\u043e, \u0447\u0442\u043e \u0443\u0436\u0435 \u0432\u043e \u043c\u043d\u043e\u0433\u043e\u043c \u0434\u0438\u0441\u043a\u0443\u0441\u0441\u0438\u0438 \u043d\u0430 \u044d\u0442\u0443 \u0442\u0435\u043c\u0443 \u0443\u0436\u0435 \u043d\u0430\u0431\u0438\u043b\u0438 \u043e\u0441\u043a\u043e\u043c\u0438\u043d\u0443, \u0432 \u0442\u043e\u043c \u0447\u0438\u0441\u043b\u0435 \u0438 \u043c\u043d\u0435, \u0440\u0435\u0448\u0438\u043b \u0432\u044b\u043d\u0435\u0441\u0442\u0438 \u043d\u0430 \u0441\u0443\u0434 \u0445\u0430\u0431\u0440\u0430-\u0441\u043e\u043e\u0431\u0449\u0435\u0441\u0442\u0432\u0430 \u0438 \u0441\u0432\u043e\u0439 \u0432\u0437\u0433\u043b\u044f\u0434 \u043d\u0430 \u044d\u0442\u0443 \u0442\u0435\u043c\u0443. \u0422\u0435\u043c, \u043a\u043e\u043c\u0443 \u0438\u043d\u0442\u0435\u0440\u0435\u0441\u043d\u043e, \u0434\u043e\u0431\u0440\u043e […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":55736,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-55735","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Endnu engang om DevOps og SRE | ProHoster","description":"Inspireret af diskussionen i chatten i AWS Minsk Community I den seneste tid er der opst\u00e5et \u00e6gte kampe om at definere begrebet.","canonical_url":"https:\/\/prohoster.info\/da\/blog\/administrirovanie\/eshhe-raz-o-devops-i-sre","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"da_DK","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0415\u0449\u0435 \u0440\u0430\u0437 \u043e DevOps \u0438 SRE | ProHoster","og:description":"\u041f\u043e \u043c\u043e\u0442\u0438\u0432\u0430\u043c \u0434\u0438\u0441\u043a\u0443\u0441\u0441\u0438\u0438 \u0432 \u0447\u0430\u0442\u0435 AWS Minsk Community \u0412 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0435\u0435 \u0432\u0440\u0435\u043c\u044f \u0440\u0430\u0437\u0433\u043e\u0440\u0430\u044e\u0442\u0441\u044f \u043d\u0430\u0441\u0442\u043e\u044f\u0449\u0438\u0435 \u0431\u0438\u0442\u0432\u044b \u043d\u0430 \u043f\u0440\u0435\u0434\u043c\u0435\u0442 \u043e\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u0438\u044f \u043f\u043e\u043d\u044f\u0442\u0438\u044f.","og:url":"https:\/\/prohoster.info\/da\/blog\/administrirovanie\/eshhe-raz-o-devops-i-sre","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-01-26T21:00:00+00:00","article:modified_time":"2020-02-18T11:03:52+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"55735","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 19:37:39","updated":"2022-10-05 06:23:35","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/posts\/55735","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/comments?post=55735"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/posts\/55735\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/media\/55736"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/media?parent=55735"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/categories?post=55735"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/tags?post=55735"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}