{"id":49434,"date":"2014-12-18T15:41:07","date_gmt":"2014-12-18T20:41:07","guid":{"rendered":"http:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/human-error-root-cause-of-november-microsoft-azure-outage\/"},"modified":"2014-12-18T15:41:07","modified_gmt":"2014-12-18T20:41:07","slug":"human-error-root-cause-of-november-microsoft-azure-outage","status":"publish","type":"post","link":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/transhuman-news-blog\/post-human\/human-error-root-cause-of-november-microsoft-azure-outage\/","title":{"rendered":"Human error root cause of November Microsoft Azure outage"},"content":{"rendered":"<p><p>    Human error was the culprit for a     November outage of the Microsoft Azure cloud storage    service. The company is hoping that recent updates that    automate formerly manual processes will help prevent similar    outages in the future.  <\/p>\n<p>    \"Microsoft Azure had clear operating guidelines but there was a    gap in the deployment tooling that relied on human decisions    and protocol,\" wrote Jason Zander, Microsoft vice president for    Azure, in a blog post Wednesday detailing the    outage. \"With the tooling updates the policy is now    enforced by the deployment platform itself.\"  <\/p>\n<p>    This is not the first time Azure has been bedeviled by human    failure.  <\/p>\n<p>    In February 2013, a lapsed security certificate led to a major Azure outage.  <\/p>\n<p>    Both cases show how even small errors can have a huge impact in    a service as large as Azure, and seem to have reinforced for    Microsoft the importance of automating manual processes as    thoroughly as possible.  <\/p>\n<p>    This latest Azure outage happened late in the evening of Nov.    18, Pacific Standard Time (Nov. 19 Coordinated Universal Time),    due to intermittent failure from some of the company's storage    services.  <\/p>\n<p>    Other Azure services that relied on the storage service also    went offline, most notably the Azure Virtual Machines.  <\/p>\n<p>    The outage stemmed from a change in the configuration of the    storage service, one that was made to improve the performance    of the service.  <\/p>\n<p>    Typically, Microsoft, like most other cloud providers, will    test a proposed change to its cloud services on a handful of    servers. This way, if there is a problem with the configuration    change, engineers can spot it early before a large number of    customers are impacted. If the change works as expected, the    company will then roll the change out to larger numbers of    servers in successive waves, until the entire system is    updated.  <\/p>\n<p>    In the case of this particular change, however, an engineer    assumed that the update had already been tested in a number of    waves (or \"flights\" in Microsoft parlance), and so went ahead    and applied the change across the rest of the system.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Read the original here:<br \/>\n<a target=\"_blank\" href=\"http:\/\/news.techworld.com\/virtualisation\/3591466\/human-error-root-cause-of-november-microsoft-azure-outage\/?olo=rss\/RK=0\/RS=4C12kpjdU923dLW0BOSPi19OFTw-\" title=\"Human error root cause of November Microsoft Azure outage\">Human error root cause of November Microsoft Azure outage<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Human error was the culprit for a November outage of the Microsoft Azure cloud storage service. The company is hoping that recent updates that automate formerly manual processes will help prevent similar outages in the future.  <a href=\"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/transhuman-news-blog\/post-human\/human-error-root-cause-of-november-microsoft-azure-outage\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"class_list":["post-49434","post","type-post","status-publish","format-standard","hentry","category-post-human"],"_links":{"self":[{"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/posts\/49434"}],"collection":[{"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/comments?post=49434"}],"version-history":[{"count":0,"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/posts\/49434\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/media?parent=49434"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/categories?post=49434"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/tags?post=49434"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}