On Sat, 10 Aug 2013 02:48:43 +0200 janI <[email protected]> wrote: > Hi. > > > We have now reconfigured mysql, and arist has optimized all myisam tables, > so now it actually runs pretty good. > > BUT I would still loke to do updates, so the vm enters a maintainable > status, with good stable versions. In order to that I need to schedule > downtime. > > We had a long discussion in infra, and it is not possible to do a parallel > vm, due to the size of this vm, so we have to do inline (of course with > backups etc). > > Jira https://issues.apache.org/jira/browse/INFRA-6652 tracks this issue. > > The downtime will be in 3 blocks: > > 1) Patch mysql 5.1 to highest 5.1 patch level > This is needed to convert tables to innodb. > Approx. downtime: 2-3 hours > when: a.s.a.p. > > 2) update ubuntu 10.04 to 12.04 and add puppet with security measured > (standard infra) > Approx. downtime 1 day > When: next weekend > > 3) Update mysql to 5.6 and upgrade db. > Approx. downtime 1 day > When: next weekend. > > Any thought about this ? > > > If anybody is strict against it, with a good reason, please give it a -1. >
+1 - the sooner the better! Can, without great work - a "Downtime" message display in place of a 404 or similar ambiguous message? -- Rory O'Farrell <[email protected]> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
