+ Petter Reinholdtsen + +

12 years of outages - summarised by Stuart Kendrick

@@ -2145,7 +2246,7 @@ dag.

@@ -2169,7 +2270,7 @@ dag.

@@ -2199,7 +2300,7 @@ dag.

diff --git a/blog/index.html b/blog/index.html index d7585cd63f..be574db4a8 100644 --- a/blog/index.html +++ b/blog/index.html @@ -19,6 +19,101 @@ +

26th October 2012

I work at the University of Oslo +looking after the computers, mostly on the unix side, but in general +all over the place. I am also a member (and currently leader) of +the NUUG association, which in turn +make me a member of USENIX. NUUG +is an member organisation for us in Norway interested in free +software, open standards and unix like operating systems, and USENIX +is a US based member organisation with similar targets. And thanks to +these memberships, I get all issues of the great USENIX magazine +;login: in the +mail several times a year. The magazine is great, and I read most of +it every time.

+ +

In the last issue of the USENIX magazine ;login:, there is an +article by Stuart Kendrick from +Fred Hutchinson Cancer Research Center titled +"What +Takes Us Down" (also +available +from his own site), where he report what he found when he +processed the outage reports (both planned and unplanned) from the +last twelve years and classified them according to cause, time of day, +etc etc. The article is a good read to get some empirical data on +what kind of problems affect a data centre, but what really inspired +me was the kind of reporting they had put in place since 2000.

+ +

The centre set up a mailing list, and started to send fairly +standardised messages to this list when a outage was planned or when +it already occurred, to announce the plan and get feedback on the +assumtions on scope and user impact. Here is the two example from the +article: First the unplanned outage: + +

+Subject:     Exchange 2003 Cluster Issues
+Severity:    Critical (Unplanned)
+Start: 	     Monday, May 7, 2012, 11:58
+End: 	     Monday, May 7, 2012, 12:38
+Duration:    40 minutes
+Scope:	     Exchange 2003
+Description: The HTTPS service on the Exchange cluster crashed, triggering
+             a cluster failover.
+
+User Impact: During this period, all Exchange users were unable to
+             access e-mail. Zimbra users were unaffected.
+Technician:  [xxx]
+

+ +Next the planned outage: + +

+Subject:     H Building Switch Upgrades
+Severity:    Major (Planned)
+Start:	     Saturday, June 16, 2012, 06:00
+End:	     Saturday, June 16, 2012, 16:00
+Duration:    10 hours
+Scope:	     H2 Transport
+Description: Currently, Catalyst 4006s provide 10/100 Ethernet to end-
+	     stations. We will replace these with newer Catalyst
+	     4510s.
+User Impact: All users on H2 will be isolated from the network during
+     	     this work. Afterward, they will have gigabit
+     	     connectivity.
+Technician:  [xxx]
+

+ +

He notes in his article that the date formats and other fields have +been a bit too free form to make it easy to automatically process them +into a database for further analysis, and I would have used ISO 8601 +dates myself to make it easier to process (in other words I would ask +people to write '2012-06-16 06:00 +0000' instead of the start time +format listed above). There are also other issues with the format +that could be improved, read the article for the details.

+ +

I find the idea of standardising outage messages seem to be such a +good idea that I would like to get it implemented here at the +university too. We do register +planned +changes and outages in a calendar, and report the to a mailing +list, but we do not do so in a structured format and there is not a +report to the same location for unplanned outages. Perhaps something +for other sites to consider too?

+ + + Tags: english, nuug, standard. + + +

Amazon steal books from customer and throw out her out without any explanation

22nd October 2012

@@ -607,50 +702,6 @@ krav!

ColonHelp produser sue WordPress to silence critic

12th October 2012

Thanks to a blog post by -Eddy -PetriÈor, I became aware of yet another "alternative medicine" -company using legal intimidation tactics to scare off critics. -According to the originating blog post about the detox "cure" -ColonHelp -and its producers Zenyth Pharmaceuticals actions, the producer -sues Wordpress to get rid of the critical information. To check if -the story was for real, I contacted Automattic, the company behind -wordpress.com, and they reply was "We can confirm that Zenyth is -seeking a court order against WordPress / Automattic. However, we -don't believe the Terms of Service have been violated in this -matter".

- -

The story seem to be simply that a blogger checked the scientific -foundation for a popular health product in Rumania, ColonHelp, and -reported that there was no reason at all to believe it improved the -health of its users. This caused the company behind the product, -Zenyth Pharmaceuticals, to use legal intimidation to try to silence -the critic, instead of presenting its views and scientific foundation -to argue its side.

- -

This is the usual story, and the Zenyth Pharmaceuticals company -deserve everyone to know how it failed to act properly. Lets hope the -Streisand -effect can make it rethink its strategy.

- -

What is the harm, you might think. I suggest you take a look at -a list of -victims of detoxification.

- - - Tags: english, skepsis. - - -

@@ -680,7 +731,7 @@ victims of detoxification.

@@ -809,7 +860,7 @@ victims of detoxification.

@@ -833,7 +884,7 @@ victims of detoxification.

@@ -863,7 +914,7 @@ victims of detoxification.

diff --git a/blog/index.rss b/blog/index.rss index bfbcec07ca..4604ec2edb 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -6,6 +6,95 @@ http://people.skolelinux.org/pere/blog/ + + 12 years of outages - summarised by Stuart Kendrick + http://people.skolelinux.org/pere/blog/12_years_of_outages___summarised_by_Stuart_Kendrick.html + http://people.skolelinux.org/pere/blog/12_years_of_outages___summarised_by_Stuart_Kendrick.html + Fri, 26 Oct 2012 14:20:00 +0200 + I work at the <a href="http://www.uio.no/">University of Oslo</a> +looking after the computers, mostly on the unix side, but in general +all over the place. I am also a member (and currently leader) of +<a href="http://www.nuug.no/">the NUUG association</a>, which in turn +make me a member of <a href="http://www.usenix.org/">USENIX</a>. NUUG +is an member organisation for us in Norway interested in free +software, open standards and unix like operating systems, and USENIX +is a US based member organisation with similar targets. And thanks to +these memberships, I get all issues of the great USENIX magazine +<a href="https://www.usenix.org/publications/login">;login:</a> in the +mail several times a year. The magazine is great, and I read most of +it every time. + +In the last issue of the USENIX magazine ;login:, there is an +article by <a href="http://www.skendric.com/">Stuart Kendrick</a> from +Fred Hutchinson Cancer Research Center titled +"<a href="https://www.usenix.org/publications/login/october-2012-volume-37-number-5/what-takes-us-down">What +Takes Us Down</a>" (also +<a href="http://www.skendric.com/problem/incident-analysis/2012-06-30/What-Takes-Us-Down.pdf">available +from his own site</a>), where he report what he found when he +processed the outage reports (both planned and unplanned) from the +last twelve years and classified them according to cause, time of day, +etc etc. The article is a good read to get some empirical data on +what kind of problems affect a data centre, but what really inspired +me was the kind of reporting they had put in place since 2000. + +The centre set up a mailing list, and started to send fairly +standardised messages to this list when a outage was planned or when +it already occurred, to announce the plan and get feedback on the +assumtions on scope and user impact. Here is the two example from the +article: First the unplanned outage: + +<blockquote><pre> +Subject: Exchange 2003 Cluster Issues +Severity: Critical (Unplanned) +Start: Monday, May 7, 2012, 11:58 +End: Monday, May 7, 2012, 12:38 +Duration: 40 minutes +Scope: Exchange 2003 +Description: The HTTPS service on the Exchange cluster crashed, triggering + a cluster failover. + +User Impact: During this period, all Exchange users were unable to + access e-mail. Zimbra users were unaffected. +Technician: [xxx] +</pre></blockquote> + +Next the planned outage: + +<blockquote><pre> +Subject: H Building Switch Upgrades +Severity: Major (Planned) +Start: Saturday, June 16, 2012, 06:00 +End: Saturday, June 16, 2012, 16:00 +Duration: 10 hours +Scope: H2 Transport +Description: Currently, Catalyst 4006s provide 10/100 Ethernet to end- + stations. We will replace these with newer Catalyst + 4510s. +User Impact: All users on H2 will be isolated from the network during + this work. Afterward, they will have gigabit + connectivity. +Technician: [xxx] +</pre></blockquote> + +He notes in his article that the date formats and other fields have +been a bit too free form to make it easy to automatically process them +into a database for further analysis, and I would have used ISO 8601 +dates myself to make it easier to process (in other words I would ask +people to write '2012-06-16 06:00 +0000' instead of the start time +format listed above). There are also other issues with the format +that could be improved, read the article for the details. + +I find the idea of standardising outage messages seem to be such a +good idea that I would like to get it implemented here at the +university too. We do register +<a href="http://www.uio.no/tjenester/it/aktuelt/planlagte-tjenesteavbrudd/">planned +changes and outages in a calendar</a>, and report the to a mailing +list, but we do not do so in a structured format and there is not a +report to the same location for unplanned outages. Perhaps something +for other sites to consider too? + + + Amazon steal books from customer and throw out her out without any explanation http://people.skolelinux.org/pere/blog/Amazon_steal_books_from_customer_and_throw_out_her_out_without_any_explanation.html @@ -540,43 +629,5 @@ krav! - - ColonHelp produser sue WordPress to silence critic - http://people.skolelinux.org/pere/blog/ColonHelp_produser_sue_WordPress_to_silence_critic.html - http://people.skolelinux.org/pere/blog/ColonHelp_produser_sue_WordPress_to_silence_critic.html - Fri, 12 Oct 2012 23:50:00 +0200 - Thanks to a blog post by -<a href="http://ramblingfoo.blogspot.no/2012/10/a-shitstorm-is-comming.html">Eddy -PetriÈor</a>, I became aware of yet another "alternative medicine" -company using legal intimidation tactics to scare off critics. -According to the originating blog post about the detox "cure" -<a href="http://insulaindoielii.wordpress.com/2012/10/11/colon-help-sues-wordpress/">ColonHelp -and its producers Zenyth Pharmaceuticals actions</a>, the producer -sues Wordpress to get rid of the critical information. To check if -the story was for real, I contacted Automattic, the company behind -wordpress.com, and they reply was "We can confirm that Zenyth is -seeking a court order against WordPress / Automattic. However, we -don't believe the Terms of Service have been violated in this -matter". - -The story seem to be simply that a blogger checked the scientific -foundation for a popular health product in Rumania, ColonHelp, and -reported that there was no reason at all to believe it improved the -health of its users. This caused the company behind the product, -Zenyth Pharmaceuticals, to use legal intimidation to try to silence -the critic, instead of presenting its views and scientific foundation -to argue its side. - -This is the usual story, and the Zenyth Pharmaceuticals company -deserve everyone to know how it failed to act properly. Lets hope the -<a href="http://en.wikipedia.org/wiki/Streisand_effect">Streisand -effect</a> can make it rethink its strategy. - -What is the harm, you might think. I suggest you take a look at -<a href="http://www.whatstheharm.net/detoxification.html">a list of -victims of detoxification</a>. - - - diff --git a/blog/jXplorer__a_very_nice_LDAP_GUI.html b/blog/jXplorer__a_very_nice_LDAP_GUI.html index 966ec68ffc..0c6cc9a404 100644 --- a/blog/jXplorer__a_very_nice_LDAP_GUI.html +++ b/blog/jXplorer__a_very_nice_LDAP_GUI.html @@ -72,7 +72,7 @@ and remove the failing query. Nothing big, but very annoying.

@@ -201,7 +201,7 @@ and remove the failing query. Nothing big, but very annoying.

@@ -225,7 +225,7 @@ and remove the failing query. Nothing big, but very annoying.

@@ -255,7 +255,7 @@ and remove the failing query. Nothing big, but very annoying.

diff --git a/blog/sitemap.xml b/blog/sitemap.xml index ce0e3c7950..9753cc4d1d 100644 --- a/blog/sitemap.xml +++ b/blog/sitemap.xml @@ -15,6 +15,11 @@ 0.50 weekly + + http://people.skolelinux.org/pere/blog/12_years_of_outages___summarised_by_Stuart_Kendrick.html + 0.50 + weekly + http://people.skolelinux.org/pere/blog/165_norske_overv_kningskamera_registert_s__langt_i_OpenStreetmap_org.html 0.50 diff --git a/blog/systemd__an_interesting_alternative_to_upstart.html b/blog/systemd__an_interesting_alternative_to_upstart.html index f8b7f45ed7..e7a0dfdde0 100644 --- a/blog/systemd__an_interesting_alternative_to_upstart.html +++ b/blog/systemd__an_interesting_alternative_to_upstart.html @@ -90,7 +90,7 @@ with parallel booting enabled by default.

@@ -219,7 +219,7 @@ with parallel booting enabled by default.

@@ -243,7 +243,7 @@ with parallel booting enabled by default.

@@ -273,7 +273,7 @@ with parallel booting enabled by default.

diff --git a/blog/tags/3d-printer/index.html b/blog/tags/3d-printer/index.html index 151c50ce66..25d7862238 100644 --- a/blog/tags/3d-printer/index.html +++ b/blog/tags/3d-printer/index.html @@ -624,7 +624,7 @@ hÃ¥per det ikke gÃ¥r tapt pÃ¥ samme vis.

@@ -753,7 +753,7 @@ hÃ¥per det ikke gÃ¥r tapt pÃ¥ samme vis.

@@ -777,7 +777,7 @@ hÃ¥per det ikke gÃ¥r tapt pÃ¥ samme vis.

@@ -807,7 +807,7 @@ hÃ¥per det ikke gÃ¥r tapt pÃ¥ samme vis.

diff --git a/blog/tags/amiga/index.html b/blog/tags/amiga/index.html index bc641092d3..62e25e76d9 100644 --- a/blog/tags/amiga/index.html +++ b/blog/tags/amiga/index.html @@ -78,7 +78,7 @@ pakke. Kanskje Aros kunne vÃ¦rt interessant for et NUUG-foredrag?

@@ -207,7 +207,7 @@ pakke. Kanskje Aros kunne vÃ¦rt interessant for et NUUG-foredrag?

@@ -231,7 +231,7 @@ pakke. Kanskje Aros kunne vÃ¦rt interessant for et NUUG-foredrag?

@@ -261,7 +261,7 @@ pakke. Kanskje Aros kunne vÃ¦rt interessant for et NUUG-foredrag?

diff --git a/blog/tags/aros/index.html b/blog/tags/aros/index.html index a622159e3e..296e26f469 100644 --- a/blog/tags/aros/index.html +++ b/blog/tags/aros/index.html @@ -78,7 +78,7 @@ pakke. Kanskje Aros kunne vÃ¦rt interessant for et NUUG-foredrag?

@@ -207,7 +207,7 @@ pakke. Kanskje Aros kunne vÃ¦rt interessant for et NUUG-foredrag?

@@ -231,7 +231,7 @@ pakke. Kanskje Aros kunne vÃ¦rt interessant for et NUUG-foredrag?

@@ -261,7 +261,7 @@ pakke. Kanskje Aros kunne vÃ¦rt interessant for et NUUG-foredrag?

diff --git a/blog/tags/bitcoin/index.html b/blog/tags/bitcoin/index.html index ff6c226dfc..c3adef9b13 100644 --- a/blog/tags/bitcoin/index.html +++ b/blog/tags/bitcoin/index.html @@ -207,7 +207,7 @@ donations to the address

@@ -336,7 +336,7 @@ donations to the address

@@ -360,7 +360,7 @@ donations to the address

@@ -390,7 +390,7 @@ donations to the address

diff --git a/blog/tags/bootsystem/index.html b/blog/tags/bootsystem/index.html index 348d2c1c17..2509247951 100644 --- a/blog/tags/bootsystem/index.html +++ b/blog/tags/bootsystem/index.html @@ -785,7 +785,7 @@ insserv'. Will need to test if that work. :)

@@ -914,7 +914,7 @@ insserv'. Will need to test if that work. :)

@@ -938,7 +938,7 @@ insserv'. Will need to test if that work. :)

@@ -968,7 +968,7 @@ insserv'. Will need to test if that work. :)

diff --git a/blog/tags/bsa/index.html b/blog/tags/bsa/index.html index 53a072d82c..aa53afd9de 100644 --- a/blog/tags/bsa/index.html +++ b/blog/tags/bsa/index.html @@ -166,7 +166,7 @@ pÃ¥ Slashdot.

@@ -295,7 +295,7 @@ pÃ¥ Slashdot.

@@ -319,7 +319,7 @@ pÃ¥ Slashdot.

@@ -349,7 +349,7 @@ pÃ¥ Slashdot.

diff --git a/blog/tags/debian edu/index.html b/blog/tags/debian edu/index.html index a3f8c7f782..bd62ae86d8 100644 --- a/blog/tags/debian edu/index.html +++ b/blog/tags/debian edu/index.html @@ -10334,7 +10334,7 @@ be the only one fitting our needs. :/

@@ -10463,7 +10463,7 @@ be the only one fitting our needs. :/

@@ -10487,7 +10487,7 @@ be the only one fitting our needs. :/

@@ -10517,7 +10517,7 @@ be the only one fitting our needs. :/

diff --git a/blog/tags/debian/index.html b/blog/tags/debian/index.html index 90ca4b77f5..32f75a7770 100644 --- a/blog/tags/debian/index.html +++ b/blog/tags/debian/index.html @@ -4425,7 +4425,7 @@ be the only one fitting our needs. :/

@@ -4554,7 +4554,7 @@ be the only one fitting our needs. :/

@@ -4578,7 +4578,7 @@ be the only one fitting our needs. :/

@@ -4608,7 +4608,7 @@ be the only one fitting our needs. :/

diff --git a/blog/tags/digistan/index.html b/blog/tags/digistan/index.html index ef975cc863..0c34a73a4f 100644 --- a/blog/tags/digistan/index.html +++ b/blog/tags/digistan/index.html @@ -1186,7 +1186,7 @@ produkter basert pÃ¥ standarden.

@@ -1315,7 +1315,7 @@ produkter basert pÃ¥ standarden.

@@ -1339,7 +1339,7 @@ produkter basert pÃ¥ standarden.

@@ -1369,7 +1369,7 @@ produkter basert pÃ¥ standarden.

diff --git a/blog/tags/docbook/index.html b/blog/tags/docbook/index.html index 58db9bc896..21e5818248 100644 --- a/blog/tags/docbook/index.html +++ b/blog/tags/docbook/index.html @@ -477,7 +477,7 @@ slik at du kan oppdatere direkte.

@@ -606,7 +606,7 @@ slik at du kan oppdatere direkte.

@@ -630,7 +630,7 @@ slik at du kan oppdatere direkte.

@@ -660,7 +660,7 @@ slik at du kan oppdatere direkte.

diff --git a/blog/tags/drivstoffpriser/index.html b/blog/tags/drivstoffpriser/index.html index 3ff0d18add..9668f0a887 100644 --- a/blog/tags/drivstoffpriser/index.html +++ b/blog/tags/drivstoffpriser/index.html @@ -507,7 +507,7 @@ en liste med stasjoner pÃ¥ samme format som PriserVedStasjoner.

@@ -636,7 +636,7 @@ en liste med stasjoner pÃ¥ samme format som PriserVedStasjoner.

@@ -660,7 +660,7 @@ en liste med stasjoner pÃ¥ samme format som PriserVedStasjoner.

@@ -690,7 +690,7 @@ en liste med stasjoner pÃ¥ samme format som PriserVedStasjoner.

diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss index 234d4f613c..3e0650877e 100644 --- a/blog/tags/english/english.rss +++ b/blog/tags/english/english.rss @@ -6,6 +6,95 @@ http://people.skolelinux.org/pere/blog/ + + 12 years of outages - summarised by Stuart Kendrick + http://people.skolelinux.org/pere/blog/12_years_of_outages___summarised_by_Stuart_Kendrick.html + http://people.skolelinux.org/pere/blog/12_years_of_outages___summarised_by_Stuart_Kendrick.html + Fri, 26 Oct 2012 14:20:00 +0200 + I work at the <a href="http://www.uio.no/">University of Oslo</a> +looking after the computers, mostly on the unix side, but in general +all over the place. I am also a member (and currently leader) of +<a href="http://www.nuug.no/">the NUUG association</a>, which in turn +make me a member of <a href="http://www.usenix.org/">USENIX</a>. NUUG +is an member organisation for us in Norway interested in free +software, open standards and unix like operating systems, and USENIX +is a US based member organisation with similar targets. And thanks to +these memberships, I get all issues of the great USENIX magazine +<a href="https://www.usenix.org/publications/login">;login:</a> in the +mail several times a year. The magazine is great, and I read most of +it every time. + +In the last issue of the USENIX magazine ;login:, there is an +article by <a href="http://www.skendric.com/">Stuart Kendrick</a> from +Fred Hutchinson Cancer Research Center titled +"<a href="https://www.usenix.org/publications/login/october-2012-volume-37-number-5/what-takes-us-down">What +Takes Us Down</a>" (also +<a href="http://www.skendric.com/problem/incident-analysis/2012-06-30/What-Takes-Us-Down.pdf">available +from his own site</a>), where he report what he found when he +processed the outage reports (both planned and unplanned) from the +last twelve years and classified them according to cause, time of day, +etc etc. The article is a good read to get some empirical data on +what kind of problems affect a data centre, but what really inspired +me was the kind of reporting they had put in place since 2000. + +The centre set up a mailing list, and started to send fairly +standardised messages to this list when a outage was planned or when +it already occurred, to announce the plan and get feedback on the +assumtions on scope and user impact. Here is the two example from the +article: First the unplanned outage: + +<blockquote><pre> +Subject: Exchange 2003 Cluster Issues +Severity: Critical (Unplanned) +Start: Monday, May 7, 2012, 11:58 +End: Monday, May 7, 2012, 12:38 +Duration: 40 minutes +Scope: Exchange 2003 +Description: The HTTPS service on the Exchange cluster crashed, triggering + a cluster failover. + +User Impact: During this period, all Exchange users were unable to + access e-mail. Zimbra users were unaffected. +Technician: [xxx] +</pre></blockquote> + +Next the planned outage: + +<blockquote><pre> +Subject: H Building Switch Upgrades +Severity: Major (Planned) +Start: Saturday, June 16, 2012, 06:00 +End: Saturday, June 16, 2012, 16:00 +Duration: 10 hours +Scope: H2 Transport +Description: Currently, Catalyst 4006s provide 10/100 Ethernet to end- + stations. We will replace these with newer Catalyst + 4510s. +User Impact: All users on H2 will be isolated from the network during + this work. Afterward, they will have gigabit + connectivity. +Technician: [xxx] +</pre></blockquote> + +He notes in his article that the date formats and other fields have +been a bit too free form to make it easy to automatically process them +into a database for further analysis, and I would have used ISO 8601 +dates myself to make it easier to process (in other words I would ask +people to write '2012-06-16 06:00 +0000' instead of the start time +format listed above). There are also other issues with the format +that could be improved, read the article for the details. + +I find the idea of standardising outage messages seem to be such a +good idea that I would like to get it implemented here at the +university too. We do register +<a href="http://www.uio.no/tjenester/it/aktuelt/planlagte-tjenesteavbrudd/">planned +changes and outages in a calendar</a>, and report the to a mailing +list, but we do not do so in a structured format and there is not a +report to the same location for unplanned outages. Perhaps something +for other sites to consider too? + + + Amazon steal books from customer and throw out her out without any explanation http://people.skolelinux.org/pere/blog/Amazon_steal_books_from_customer_and_throw_out_her_out_without_any_explanation.html diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html index 3638f02853..d4a8292e94 100644 --- a/blog/tags/english/index.html +++ b/blog/tags/english/index.html @@ -20,6 +20,107 @@

Entries tagged "english".

+ 12 years of outages - summarised by Stuart Kendrick +

+ 26th October 2012 +

+ +

+Subject:     Exchange 2003 Cluster Issues
+Severity:    Critical (Unplanned)
+Start: 	     Monday, May 7, 2012, 11:58
+End: 	     Monday, May 7, 2012, 12:38
+Duration:    40 minutes
+Scope:	     Exchange 2003
+Description: The HTTPS service on the Exchange cluster crashed, triggering
+             a cluster failover.
+
+User Impact: During this period, all Exchange users were unable to
+             access e-mail. Zimbra users were unaffected.
+Technician:  [xxx]
+

+ +Next the planned outage: + +

+Subject:     H Building Switch Upgrades
+Severity:    Major (Planned)
+Start:	     Saturday, June 16, 2012, 06:00
+End:	     Saturday, June 16, 2012, 16:00
+Duration:    10 hours
+Scope:	     H2 Transport
+Description: Currently, Catalyst 4006s provide 10/100 Ethernet to end-
+	     stations. We will replace these with newer Catalyst
+	     4510s.
+User Impact: All users on H2 will be isolated from the network during
+     	     this work. Afterward, they will have gigabit
+     	     connectivity.
+Technician:  [xxx]
+

+ +

+ + + Tags: english, nuug, standard. + + +

Amazon steal books from customer and throw out her out without any explanation @@ -11859,7 +11960,7 @@ be the only one fitting our needs. :/

@@ -11988,7 +12089,7 @@ be the only one fitting our needs. :/

@@ -12012,7 +12113,7 @@ be the only one fitting our needs. :/

@@ -12042,7 +12143,7 @@ be the only one fitting our needs. :/

diff --git a/blog/tags/fiksgatami/index.html b/blog/tags/fiksgatami/index.html index 3361d0a9b9..a747592343 100644 --- a/blog/tags/fiksgatami/index.html +++ b/blog/tags/fiksgatami/index.html @@ -1191,7 +1191,7 @@ med dem. Dette blir bra.

@@ -1320,7 +1320,7 @@ med dem. Dette blir bra.

@@ -1344,7 +1344,7 @@ med dem. Dette blir bra.

@@ -1374,7 +1374,7 @@ med dem. Dette blir bra.

diff --git a/blog/tags/fildeling/index.html b/blog/tags/fildeling/index.html index 9edfa93252..0407873059 100644 --- a/blog/tags/fildeling/index.html +++ b/blog/tags/fildeling/index.html @@ -651,7 +651,7 @@ og fildeling av slike filer er fullt ut lovlig.

@@ -780,7 +780,7 @@ og fildeling av slike filer er fullt ut lovlig.

@@ -804,7 +804,7 @@ og fildeling av slike filer er fullt ut lovlig.

@@ -834,7 +834,7 @@ og fildeling av slike filer er fullt ut lovlig.

diff --git a/blog/tags/freeculture/index.html b/blog/tags/freeculture/index.html index 0016336a4d..ae94ae20c5 100644 --- a/blog/tags/freeculture/index.html +++ b/blog/tags/freeculture/index.html @@ -520,7 +520,7 @@ slik at du kan oppdatere direkte.

@@ -649,7 +649,7 @@ slik at du kan oppdatere direkte.

@@ -673,7 +673,7 @@ slik at du kan oppdatere direkte.

@@ -703,7 +703,7 @@ slik at du kan oppdatere direkte.

diff --git a/blog/tags/frikanalen/index.html b/blog/tags/frikanalen/index.html index d9be69bf94..79e350ff7d 100644 --- a/blog/tags/frikanalen/index.html +++ b/blog/tags/frikanalen/index.html @@ -636,7 +636,7 @@ NUUG lykkes med Ã¥ fÃ¥ ut sine opptak med like stor suksess.

@@ -765,7 +765,7 @@ NUUG lykkes med Ã¥ fÃ¥ ut sine opptak med like stor suksess.

@@ -789,7 +789,7 @@ NUUG lykkes med Ã¥ fÃ¥ ut sine opptak med like stor suksess.

@@ -819,7 +819,7 @@ NUUG lykkes med Ã¥ fÃ¥ ut sine opptak med like stor suksess.

diff --git a/blog/tags/intervju/index.html b/blog/tags/intervju/index.html index 463bb22bed..3041a813de 100644 --- a/blog/tags/intervju/index.html +++ b/blog/tags/intervju/index.html @@ -3560,7 +3560,7 @@ veldig bra utvalg av gratis spill som er av hÃ¸y kvalitet. Veldig lett

@@ -3689,7 +3689,7 @@ veldig bra utvalg av gratis spill som er av hÃ¸y kvalitet. Veldig lett

@@ -3713,7 +3713,7 @@ veldig bra utvalg av gratis spill som er av hÃ¸y kvalitet. Veldig lett

@@ -3743,7 +3743,7 @@ veldig bra utvalg av gratis spill som er av hÃ¸y kvalitet. Veldig lett

diff --git a/blog/tags/kart/index.html b/blog/tags/kart/index.html index daeb0db9db..47c9436a40 100644 --- a/blog/tags/kart/index.html +++ b/blog/tags/kart/index.html @@ -1116,7 +1116,7 @@ det viser at behovet for fribruks-sjÃ¸kart er til stedet.

@@ -1245,7 +1245,7 @@ det viser at behovet for fribruks-sjÃ¸kart er til stedet.

@@ -1269,7 +1269,7 @@ det viser at behovet for fribruks-sjÃ¸kart er til stedet.

@@ -1299,7 +1299,7 @@ det viser at behovet for fribruks-sjÃ¸kart er til stedet.

diff --git a/blog/tags/ldap/index.html b/blog/tags/ldap/index.html index af3e169373..09e66f5e24 100644 --- a/blog/tags/ldap/index.html +++ b/blog/tags/ldap/index.html @@ -967,7 +967,7 @@ new IETF work group?

@@ -1096,7 +1096,7 @@ new IETF work group?

@@ -1120,7 +1120,7 @@ new IETF work group?

@@ -1150,7 +1150,7 @@ new IETF work group?

diff --git a/blog/tags/lenker/index.html b/blog/tags/lenker/index.html index c2c4de2ef9..2db6caf0e4 100644 --- a/blog/tags/lenker/index.html +++ b/blog/tags/lenker/index.html @@ -202,7 +202,7 @@ Word 2007 hÃ¥ndterer ODF dÃ¥rlig

@@ -331,7 +331,7 @@ Word 2007 hÃ¥ndterer ODF dÃ¥rlig

@@ -355,7 +355,7 @@ Word 2007 hÃ¥ndterer ODF dÃ¥rlig

@@ -385,7 +385,7 @@ Word 2007 hÃ¥ndterer ODF dÃ¥rlig

diff --git a/blog/tags/ltsp/index.html b/blog/tags/ltsp/index.html index 4475b0dfe4..8a47d3ff9e 100644 --- a/blog/tags/ltsp/index.html +++ b/blog/tags/ltsp/index.html @@ -83,7 +83,7 @@ of these cards.

@@ -212,7 +212,7 @@ of these cards.

@@ -236,7 +236,7 @@ of these cards.

@@ -266,7 +266,7 @@ of these cards.

diff --git a/blog/tags/multimedia/index.html b/blog/tags/multimedia/index.html index e566f3e254..e667db6662 100644 --- a/blog/tags/multimedia/index.html +++ b/blog/tags/multimedia/index.html @@ -1900,7 +1900,7 @@ be the only one fitting our needs. :/

@@ -2029,7 +2029,7 @@ be the only one fitting our needs. :/

@@ -2053,7 +2053,7 @@ be the only one fitting our needs. :/

@@ -2083,7 +2083,7 @@ be the only one fitting our needs. :/

diff --git a/blog/tags/norsk/index.html b/blog/tags/norsk/index.html index 3fa92925c2..15d34d29e7 100644 --- a/blog/tags/norsk/index.html +++ b/blog/tags/norsk/index.html @@ -15288,7 +15288,7 @@ forsÃ¸k.

@@ -15417,7 +15417,7 @@ forsÃ¸k.

@@ -15441,7 +15441,7 @@ forsÃ¸k.

@@ -15471,7 +15471,7 @@ forsÃ¸k.

diff --git a/blog/tags/nuug/index.html b/blog/tags/nuug/index.html index 77239b3ef7..6e3c5e526b 100644 --- a/blog/tags/nuug/index.html +++ b/blog/tags/nuug/index.html @@ -20,6 +20,107 @@

Entries tagged "nuug".

+ 12 years of outages - summarised by Stuart Kendrick +

+ 26th October 2012 +

+ +

+Subject:     Exchange 2003 Cluster Issues
+Severity:    Critical (Unplanned)
+Start: 	     Monday, May 7, 2012, 11:58
+End: 	     Monday, May 7, 2012, 12:38
+Duration:    40 minutes
+Scope:	     Exchange 2003
+Description: The HTTPS service on the Exchange cluster crashed, triggering
+             a cluster failover.
+
+User Impact: During this period, all Exchange users were unable to
+             access e-mail. Zimbra users were unaffected.
+Technician:  [xxx]
+

+ +Next the planned outage: + +

+Subject:     H Building Switch Upgrades
+Severity:    Major (Planned)
+Start:	     Saturday, June 16, 2012, 06:00
+End:	     Saturday, June 16, 2012, 16:00
+Duration:    10 hours
+Scope:	     H2 Transport
+Description: Currently, Catalyst 4006s provide 10/100 Ethernet to end-
+	     stations. We will replace these with newer Catalyst
+	     4510s.
+User Impact: All users on H2 will be isolated from the network during
+     	     this work. Afterward, they will have gigabit
+     	     connectivity.
+Technician:  [xxx]
+

+ +

+ + + Tags: english, nuug, standard. + + +

NUUGs spÃ¸rreundersÃ¸kelse for 2012 endelig Ã¥pnet @@ -9259,7 +9360,7 @@ hÃ¥per det ikke gÃ¥r tapt pÃ¥ samme vis.

@@ -9388,7 +9489,7 @@ hÃ¥per det ikke gÃ¥r tapt pÃ¥ samme vis.

@@ -9412,7 +9513,7 @@ hÃ¥per det ikke gÃ¥r tapt pÃ¥ samme vis.

@@ -9442,7 +9543,7 @@ hÃ¥per det ikke gÃ¥r tapt pÃ¥ samme vis.

diff --git a/blog/tags/nuug/nuug.rss b/blog/tags/nuug/nuug.rss index 6d8392febd..ed8ca6d605 100644 --- a/blog/tags/nuug/nuug.rss +++ b/blog/tags/nuug/nuug.rss @@ -6,6 +6,95 @@ http://people.skolelinux.org/pere/blog/ + + 12 years of outages - summarised by Stuart Kendrick + http://people.skolelinux.org/pere/blog/12_years_of_outages___summarised_by_Stuart_Kendrick.html + http://people.skolelinux.org/pere/blog/12_years_of_outages___summarised_by_Stuart_Kendrick.html + Fri, 26 Oct 2012 14:20:00 +0200 + I work at the <a href="http://www.uio.no/">University of Oslo</a> +looking after the computers, mostly on the unix side, but in general +all over the place. I am also a member (and currently leader) of +<a href="http://www.nuug.no/">the NUUG association</a>, which in turn +make me a member of <a href="http://www.usenix.org/">USENIX</a>. NUUG +is an member organisation for us in Norway interested in free +software, open standards and unix like operating systems, and USENIX +is a US based member organisation with similar targets. And thanks to +these memberships, I get all issues of the great USENIX magazine +<a href="https://www.usenix.org/publications/login">;login:</a> in the +mail several times a year. The magazine is great, and I read most of +it every time. + +In the last issue of the USENIX magazine ;login:, there is an +article by <a href="http://www.skendric.com/">Stuart Kendrick</a> from +Fred Hutchinson Cancer Research Center titled +"<a href="https://www.usenix.org/publications/login/october-2012-volume-37-number-5/what-takes-us-down">What +Takes Us Down</a>" (also +<a href="http://www.skendric.com/problem/incident-analysis/2012-06-30/What-Takes-Us-Down.pdf">available +from his own site</a>), where he report what he found when he +processed the outage reports (both planned and unplanned) from the +last twelve years and classified them according to cause, time of day, +etc etc. The article is a good read to get some empirical data on +what kind of problems affect a data centre, but what really inspired +me was the kind of reporting they had put in place since 2000. + +The centre set up a mailing list, and started to send fairly +standardised messages to this list when a outage was planned or when +it already occurred, to announce the plan and get feedback on the +assumtions on scope and user impact. Here is the two example from the +article: First the unplanned outage: + +<blockquote><pre> +Subject: Exchange 2003 Cluster Issues +Severity: Critical (Unplanned) +Start: Monday, May 7, 2012, 11:58 +End: Monday, May 7, 2012, 12:38 +Duration: 40 minutes +Scope: Exchange 2003 +Description: The HTTPS service on the Exchange cluster crashed, triggering + a cluster failover. + +User Impact: During this period, all Exchange users were unable to + access e-mail. Zimbra users were unaffected. +Technician: [xxx] +</pre></blockquote> + +Next the planned outage: + +<blockquote><pre> +Subject: H Building Switch Upgrades +Severity: Major (Planned) +Start: Saturday, June 16, 2012, 06:00 +End: Saturday, June 16, 2012, 16:00 +Duration: 10 hours +Scope: H2 Transport +Description: Currently, Catalyst 4006s provide 10/100 Ethernet to end- + stations. We will replace these with newer Catalyst + 4510s. +User Impact: All users on H2 will be isolated from the network during + this work. Afterward, they will have gigabit + connectivity. +Technician: [xxx] +</pre></blockquote> + +He notes in his article that the date formats and other fields have +been a bit too free form to make it easy to automatically process them +into a database for further analysis, and I would have used ISO 8601 +dates myself to make it easier to process (in other words I would ask +people to write '2012-06-16 06:00 +0000' instead of the start time +format listed above). There are also other issues with the format +that could be improved, read the article for the details. + +I find the idea of standardising outage messages seem to be such a +good idea that I would like to get it implemented here at the +university too. We do register +<a href="http://www.uio.no/tjenester/it/aktuelt/planlagte-tjenesteavbrudd/">planned +changes and outages in a calendar</a>, and report the to a mailing +list, but we do not do so in a structured format and there is not a +report to the same location for unplanned outages. Perhaps something +for other sites to consider too? + + + NUUGs spÃ¸rreundersÃ¸kelse for 2012 endelig Ã¥pnet http://people.skolelinux.org/pere/blog/NUUGs_sp_rreunders_kelse_for_2012_endelig__pnet.html diff --git a/blog/tags/offentlig innsyn/index.html b/blog/tags/offentlig innsyn/index.html index d745585d19..3599e21d28 100644 --- a/blog/tags/offentlig innsyn/index.html +++ b/blog/tags/offentlig innsyn/index.html @@ -590,7 +590,7 @@ til Ã¥ levere hver uke. Har ikke undersÃ¸kt noen av de andre.

@@ -719,7 +719,7 @@ til Ã¥ levere hver uke. Har ikke undersÃ¸kt noen av de andre.

@@ -743,7 +743,7 @@ til Ã¥ levere hver uke. Har ikke undersÃ¸kt noen av de andre.

@@ -773,7 +773,7 @@ til Ã¥ levere hver uke. Har ikke undersÃ¸kt noen av de andre.

diff --git a/blog/tags/open311/index.html b/blog/tags/open311/index.html index 25f71d070b..ebb7b62d30 100644 --- a/blog/tags/open311/index.html +++ b/blog/tags/open311/index.html @@ -178,7 +178,7 @@ work like the free software project communities I am used to.

@@ -307,7 +307,7 @@ work like the free software project communities I am used to.

@@ -331,7 +331,7 @@ work like the free software project communities I am used to.

@@ -361,7 +361,7 @@ work like the free software project communities I am used to.

diff --git a/blog/tags/opphavsrett/index.html b/blog/tags/opphavsrett/index.html index 265c68e9ce..aa15335299 100644 --- a/blog/tags/opphavsrett/index.html +++ b/blog/tags/opphavsrett/index.html @@ -2711,7 +2711,7 @@ og endrer pÃ¥ betingelsene.

@@ -2840,7 +2840,7 @@ og endrer pÃ¥ betingelsene.

@@ -2864,7 +2864,7 @@ og endrer pÃ¥ betingelsene.

@@ -2894,7 +2894,7 @@ og endrer pÃ¥ betingelsene.

diff --git a/blog/tags/personvern/index.html b/blog/tags/personvern/index.html index e035e4b706..98fd83e009 100644 --- a/blog/tags/personvern/index.html +++ b/blog/tags/personvern/index.html @@ -4461,7 +4461,7 @@ kontanter for noen dager siden.

@@ -4590,7 +4590,7 @@ kontanter for noen dager siden.

@@ -4614,7 +4614,7 @@ kontanter for noen dager siden.

@@ -4644,7 +4644,7 @@ kontanter for noen dager siden.

diff --git a/blog/tags/raid/index.html b/blog/tags/raid/index.html index 7aa44fb6cc..de7790fdcc 100644 --- a/blog/tags/raid/index.html +++ b/blog/tags/raid/index.html @@ -119,7 +119,7 @@ disk(s) is failing when the RAID is running short on disks.

@@ -248,7 +248,7 @@ disk(s) is failing when the RAID is running short on disks.

@@ -272,7 +272,7 @@ disk(s) is failing when the RAID is running short on disks.

@@ -302,7 +302,7 @@ disk(s) is failing when the RAID is running short on disks.

diff --git a/blog/tags/reprap/index.html b/blog/tags/reprap/index.html index 5a96423921..061cf137e1 100644 --- a/blog/tags/reprap/index.html +++ b/blog/tags/reprap/index.html @@ -545,7 +545,7 @@ hÃ¥per det ikke gÃ¥r tapt pÃ¥ samme vis.

@@ -674,7 +674,7 @@ hÃ¥per det ikke gÃ¥r tapt pÃ¥ samme vis.

@@ -698,7 +698,7 @@ hÃ¥per det ikke gÃ¥r tapt pÃ¥ samme vis.

@@ -728,7 +728,7 @@ hÃ¥per det ikke gÃ¥r tapt pÃ¥ samme vis.

diff --git a/blog/tags/rfid/index.html b/blog/tags/rfid/index.html index b471bfcda4..7b72505433 100644 --- a/blog/tags/rfid/index.html +++ b/blog/tags/rfid/index.html @@ -168,7 +168,7 @@ mer om de nye biometriske passene.

@@ -297,7 +297,7 @@ mer om de nye biometriske passene.

@@ -321,7 +321,7 @@ mer om de nye biometriske passene.

@@ -351,7 +351,7 @@ mer om de nye biometriske passene.

diff --git a/blog/tags/robot/index.html b/blog/tags/robot/index.html index e955679a32..8adb71486d 100644 --- a/blog/tags/robot/index.html +++ b/blog/tags/robot/index.html @@ -266,7 +266,7 @@ firmwaren. :)

@@ -395,7 +395,7 @@ firmwaren. :)

@@ -419,7 +419,7 @@ firmwaren. :)

@@ -449,7 +449,7 @@ firmwaren. :)

diff --git a/blog/tags/rss/index.html b/blog/tags/rss/index.html index 052a094962..56fbf410bc 100644 --- a/blog/tags/rss/index.html +++ b/blog/tags/rss/index.html @@ -72,7 +72,7 @@ forsÃ¸k.

@@ -201,7 +201,7 @@ forsÃ¸k.

@@ -225,7 +225,7 @@ forsÃ¸k.

@@ -255,7 +255,7 @@ forsÃ¸k.

diff --git a/blog/tags/ruter/index.html b/blog/tags/ruter/index.html index 5cc5e4b442..e675a1755d 100644 --- a/blog/tags/ruter/index.html +++ b/blog/tags/ruter/index.html @@ -226,7 +226,7 @@ OsloomrÃ¥det.

@@ -355,7 +355,7 @@ OsloomrÃ¥det.

@@ -379,7 +379,7 @@ OsloomrÃ¥det.

@@ -409,7 +409,7 @@ OsloomrÃ¥det.

diff --git a/blog/tags/scraperwiki/index.html b/blog/tags/scraperwiki/index.html index 7b66e219d6..6ed47f30a2 100644 --- a/blog/tags/scraperwiki/index.html +++ b/blog/tags/scraperwiki/index.html @@ -161,7 +161,7 @@ av Ã¥ dele informasjon med andre uten bruksbegresninger.

@@ -290,7 +290,7 @@ av Ã¥ dele informasjon med andre uten bruksbegresninger.

@@ -314,7 +314,7 @@ av Ã¥ dele informasjon med andre uten bruksbegresninger.

@@ -344,7 +344,7 @@ av Ã¥ dele informasjon med andre uten bruksbegresninger.

diff --git a/blog/tags/sikkerhet/index.html b/blog/tags/sikkerhet/index.html index 5963fbc277..ba3a11d8a2 100644 --- a/blog/tags/sikkerhet/index.html +++ b/blog/tags/sikkerhet/index.html @@ -1550,7 +1550,7 @@ betydelige.

@@ -1679,7 +1679,7 @@ betydelige.

@@ -1703,7 +1703,7 @@ betydelige.

@@ -1733,7 +1733,7 @@ betydelige.

diff --git a/blog/tags/sitesummary/index.html b/blog/tags/sitesummary/index.html index 32bc260d93..27ddd45941 100644 --- a/blog/tags/sitesummary/index.html +++ b/blog/tags/sitesummary/index.html @@ -277,7 +277,7 @@ everything is taken care of.

@@ -406,7 +406,7 @@ everything is taken care of.

@@ -430,7 +430,7 @@ everything is taken care of.

@@ -460,7 +460,7 @@ everything is taken care of.

diff --git a/blog/tags/skepsis/index.html b/blog/tags/skepsis/index.html index 28d87058f1..cb8a860ce1 100644 --- a/blog/tags/skepsis/index.html +++ b/blog/tags/skepsis/index.html @@ -400,7 +400,7 @@ skyskrapere. Takke meg til en tur til mÃ¥nen.

@@ -529,7 +529,7 @@ skyskrapere. Takke meg til en tur til mÃ¥nen.

@@ -553,7 +553,7 @@ skyskrapere. Takke meg til en tur til mÃ¥nen.

@@ -583,7 +583,7 @@ skyskrapere. Takke meg til en tur til mÃ¥nen.

diff --git a/blog/tags/standard/index.html b/blog/tags/standard/index.html index 8e990990ee..35f1d18b0a 100644 --- a/blog/tags/standard/index.html +++ b/blog/tags/standard/index.html @@ -20,6 +20,107 @@

Entries tagged "standard".

+ 12 years of outages - summarised by Stuart Kendrick +

+ 26th October 2012 +

+ +

+Subject:     Exchange 2003 Cluster Issues
+Severity:    Critical (Unplanned)
+Start: 	     Monday, May 7, 2012, 11:58
+End: 	     Monday, May 7, 2012, 12:38
+Duration:    40 minutes
+Scope:	     Exchange 2003
+Description: The HTTPS service on the Exchange cluster crashed, triggering
+             a cluster failover.
+
+User Impact: During this period, all Exchange users were unable to
+             access e-mail. Zimbra users were unaffected.
+Technician:  [xxx]
+

+ +Next the planned outage: + +

+Subject:     H Building Switch Upgrades
+Severity:    Major (Planned)
+Start:	     Saturday, June 16, 2012, 06:00
+End:	     Saturday, June 16, 2012, 16:00
+Duration:    10 hours
+Scope:	     H2 Transport
+Description: Currently, Catalyst 4006s provide 10/100 Ethernet to end-
+	     stations. We will replace these with newer Catalyst
+	     4510s.
+User Impact: All users on H2 will be isolated from the network during
+     	     this work. Afterward, they will have gigabit
+     	     connectivity.
+Technician:  [xxx]
+

+ +

+ + + Tags: english, nuug, standard. + + +

NUUGs hÃ¸ringsuttalelse til DIFIs forslag om Ã¥ kaste ut ODF fra statens standardkatalog @@ -3146,7 +3247,7 @@ Kjenner kun til ufullstendige lÃ¸sninger for slikt.

@@ -3275,7 +3376,7 @@ Kjenner kun til ufullstendige lÃ¸sninger for slikt.

@@ -3299,7 +3400,7 @@ Kjenner kun til ufullstendige lÃ¸sninger for slikt.

@@ -3329,7 +3430,7 @@ Kjenner kun til ufullstendige lÃ¸sninger for slikt.

diff --git a/blog/tags/standard/standard.rss b/blog/tags/standard/standard.rss index e94c2a9240..35154dff98 100644 --- a/blog/tags/standard/standard.rss +++ b/blog/tags/standard/standard.rss @@ -6,6 +6,95 @@ http://people.skolelinux.org/pere/blog/ + + 12 years of outages - summarised by Stuart Kendrick + http://people.skolelinux.org/pere/blog/12_years_of_outages___summarised_by_Stuart_Kendrick.html + http://people.skolelinux.org/pere/blog/12_years_of_outages___summarised_by_Stuart_Kendrick.html + Fri, 26 Oct 2012 14:20:00 +0200 + I work at the <a href="http://www.uio.no/">University of Oslo</a> +looking after the computers, mostly on the unix side, but in general +all over the place. I am also a member (and currently leader) of +<a href="http://www.nuug.no/">the NUUG association</a>, which in turn +make me a member of <a href="http://www.usenix.org/">USENIX</a>. NUUG +is an member organisation for us in Norway interested in free +software, open standards and unix like operating systems, and USENIX +is a US based member organisation with similar targets. And thanks to +these memberships, I get all issues of the great USENIX magazine +<a href="https://www.usenix.org/publications/login">;login:</a> in the +mail several times a year. The magazine is great, and I read most of +it every time. + +In the last issue of the USENIX magazine ;login:, there is an +article by <a href="http://www.skendric.com/">Stuart Kendrick</a> from +Fred Hutchinson Cancer Research Center titled +"<a href="https://www.usenix.org/publications/login/october-2012-volume-37-number-5/what-takes-us-down">What +Takes Us Down</a>" (also +<a href="http://www.skendric.com/problem/incident-analysis/2012-06-30/What-Takes-Us-Down.pdf">available +from his own site</a>), where he report what he found when he +processed the outage reports (both planned and unplanned) from the +last twelve years and classified them according to cause, time of day, +etc etc. The article is a good read to get some empirical data on +what kind of problems affect a data centre, but what really inspired +me was the kind of reporting they had put in place since 2000. + +The centre set up a mailing list, and started to send fairly +standardised messages to this list when a outage was planned or when +it already occurred, to announce the plan and get feedback on the +assumtions on scope and user impact. Here is the two example from the +article: First the unplanned outage: + +<blockquote><pre> +Subject: Exchange 2003 Cluster Issues +Severity: Critical (Unplanned) +Start: Monday, May 7, 2012, 11:58 +End: Monday, May 7, 2012, 12:38 +Duration: 40 minutes +Scope: Exchange 2003 +Description: The HTTPS service on the Exchange cluster crashed, triggering + a cluster failover. + +User Impact: During this period, all Exchange users were unable to + access e-mail. Zimbra users were unaffected. +Technician: [xxx] +</pre></blockquote> + +Next the planned outage: + +<blockquote><pre> +Subject: H Building Switch Upgrades +Severity: Major (Planned) +Start: Saturday, June 16, 2012, 06:00 +End: Saturday, June 16, 2012, 16:00 +Duration: 10 hours +Scope: H2 Transport +Description: Currently, Catalyst 4006s provide 10/100 Ethernet to end- + stations. We will replace these with newer Catalyst + 4510s. +User Impact: All users on H2 will be isolated from the network during + this work. Afterward, they will have gigabit + connectivity. +Technician: [xxx] +</pre></blockquote> + +He notes in his article that the date formats and other fields have +been a bit too free form to make it easy to automatically process them +into a database for further analysis, and I would have used ISO 8601 +dates myself to make it easier to process (in other words I would ask +people to write '2012-06-16 06:00 +0000' instead of the start time +format listed above). There are also other issues with the format +that could be improved, read the article for the details. + +I find the idea of standardising outage messages seem to be such a +good idea that I would like to get it implemented here at the +university too. We do register +<a href="http://www.uio.no/tjenester/it/aktuelt/planlagte-tjenesteavbrudd/">planned +changes and outages in a calendar</a>, and report the to a mailing +list, but we do not do so in a structured format and there is not a +report to the same location for unplanned outages. Perhaps something +for other sites to consider too? + + + NUUGs hÃ¸ringsuttalelse til DIFIs forslag om Ã¥ kaste ut ODF fra statens standardkatalog http://people.skolelinux.org/pere/blog/NUUGs_h_ringsuttalelse_til_DIFIs_forslag_om___kaste_ut_ODF_fra_statens_standardkatalog.html diff --git a/blog/tags/stavekontroll/index.html b/blog/tags/stavekontroll/index.html index d8c401f3a1..ff811b2e90 100644 --- a/blog/tags/stavekontroll/index.html +++ b/blog/tags/stavekontroll/index.html @@ -256,7 +256,7 @@ stavekontrollen.

@@ -385,7 +385,7 @@ stavekontrollen.

@@ -409,7 +409,7 @@ stavekontrollen.

@@ -439,7 +439,7 @@ stavekontrollen.

diff --git a/blog/tags/stortinget/index.html b/blog/tags/stortinget/index.html index e6bd48f3ea..b7acfc4022 100644 --- a/blog/tags/stortinget/index.html +++ b/blog/tags/stortinget/index.html @@ -392,7 +392,7 @@ at vi i NUUG har fÃ¥tt operativ en norsk utgave av

@@ -521,7 +521,7 @@ at vi i NUUG har fÃ¥tt operativ en norsk utgave av

@@ -545,7 +545,7 @@ at vi i NUUG har fÃ¥tt operativ en norsk utgave av

@@ -575,7 +575,7 @@ at vi i NUUG har fÃ¥tt operativ en norsk utgave av

diff --git a/blog/tags/surveillance/index.html b/blog/tags/surveillance/index.html index 8aa14f7d31..14f3183de9 100644 --- a/blog/tags/surveillance/index.html +++ b/blog/tags/surveillance/index.html @@ -609,7 +609,7 @@ automatisk over i spesialkartet.

@@ -738,7 +738,7 @@ automatisk over i spesialkartet.

@@ -762,7 +762,7 @@ automatisk over i spesialkartet.

@@ -792,7 +792,7 @@ automatisk over i spesialkartet.

diff --git a/blog/tags/valg/index.html b/blog/tags/valg/index.html index 4cb1a57105..a591f140d8 100644 --- a/blog/tags/valg/index.html +++ b/blog/tags/valg/index.html @@ -666,7 +666,7 @@ inneholdt i Iran hvis de ikke hadde hemmelige valg?

@@ -795,7 +795,7 @@ inneholdt i Iran hvis de ikke hadde hemmelige valg?

@@ -819,7 +819,7 @@ inneholdt i Iran hvis de ikke hadde hemmelige valg?

@@ -849,7 +849,7 @@ inneholdt i Iran hvis de ikke hadde hemmelige valg?

diff --git a/blog/tags/video/index.html b/blog/tags/video/index.html index e1a999c770..7a58477207 100644 --- a/blog/tags/video/index.html +++ b/blog/tags/video/index.html @@ -2766,7 +2766,7 @@ larger stick as well.

@@ -2895,7 +2895,7 @@ larger stick as well.

@@ -2919,7 +2919,7 @@ larger stick as well.

@@ -2949,7 +2949,7 @@ larger stick as well.

diff --git a/blog/tags/vitenskap/index.html b/blog/tags/vitenskap/index.html index 6a2cabae72..a190534910 100644 --- a/blog/tags/vitenskap/index.html +++ b/blog/tags/vitenskap/index.html @@ -403,7 +403,7 @@ skyskrapere. Takke meg til en tur til mÃ¥nen.

@@ -532,7 +532,7 @@ skyskrapere. Takke meg til en tur til mÃ¥nen.

@@ -556,7 +556,7 @@ skyskrapere. Takke meg til en tur til mÃ¥nen.

@@ -586,7 +586,7 @@ skyskrapere. Takke meg til en tur til mÃ¥nen.

diff --git a/blog/tags/web/index.html b/blog/tags/web/index.html index 129c8c0a12..157e678f9a 100644 --- a/blog/tags/web/index.html +++ b/blog/tags/web/index.html @@ -1990,7 +1990,7 @@ be the only one fitting our needs. :/