On Sat, Aug 17, 2013 at 8:40 PM, Ken Snider <ksnider(a)wikimedia.org> wrote:
On Aug 17, 2013, at 1:33 PM, rupert THURNER <rupert.thurner(a)gmail.com> wrote:
hi faidon, i do not think you personally and WMF
are particularly
helpful in accepting contributions. because you:
* do not communicate openly the problems
* do not report upstream publically
* do not ask for help, and even if it gets offered you just ignore it
with quite some arrogance
Rupert, please don't call out or attack specific people. We're all on the same
team, and I can
...
let me change the title, as this is not site hardening any more.
Further, Ops in general, and Faidon in particular,
routinely report issues upstream. Our recent bug reports or patches to Varnish and Ceph
are two examples that easily come to mind. Faidon was (rightly) attempting to restore
service first ...
yes ken, you are right, lets stick to the issues at hand:
(1) by when you will finally decide to invest the 10 minutes and
properly trace the gitblit application? you have the commands in the
ticket:
https://bugzilla.wikimedia.org/show_bug.cgi?id=51769
(2) by when you will adjust your operating guideline, so it is clear
to faidon, ariel and others that 10 minutes tracing of an application
and getting a holistic view is mandatory _before_ restoring the
service, if it goes down for so often, and for days every time. the 10
minutes more can not be noticed if it is gone for more than a day.
(3) how you will handle offers to help out of the community in future.
like in the gitblit case, i offered to help tracing the problem while
the service was down. max semenik now reported that gitblit should set
rel="nofollow".
best regards, rupert.