In our recent (July) team retrospective, we didn't have a chance to review
the action items that came out of our June retrospective. However, I have
posted those previous items, with status updates (as best I know them)[1].
Of the 18 items, 5 are "done", and several others are improved or in
progress.
[1]
https://www.mediawiki.org/wiki/Wikimedia_Search_Team/Retrospective_2015-07-…
That page will also contain our July retrospective notes, after they have
been processed.
Kevin Smith
Agile Coach
Wikimedia Foundation
*Imagine a world in which every single human being can freely share in the
sum of all knowledge. That's our commitment. Help us make it a reality.*
I'm having trouble enabling the analytics role on vagrant. Does this mean
anything to anyone?
==> default: Error: Puppet::Parser::AST::Resource failed with error
> ArgumentError: Could not find declared class ::cdh::hadoop at
> /vagrant/puppet/modules/role/manifests/hadoop.pp:45
> on node mediawiki-vagrant.dev
>
I even tried vagrant destroying, and starting from scratch. It seems like
maybe I need to apt-get install something Hadoop related, but my Google-fu
isn't helping.
We had a meeting today with Giuseppe and Andrew from Ops, and clarified our
path toward getting WDQS deployed in production (as a test service). Here
are the takeaways/action items I'm aware of:
1. We need to specify our hardware needs ASAP
---> I think this means we should unstall
https://phabricator.wikimedia.org/T86561 and assign it to Stas.
2. Most likely the service will run on existing hardware (and ops will want
to deploy it in both data centers)
3. Debian packaging is not required--we'll use maven+archiva+git deploy (?)
4. Andrew can help Stas with archiva (which Stas and Nik have already used)
5. Giuseppe can help Stas with puppet, which should be pretty easy
6. The puppet work should include basic health and performance monitoring
7. Stas will consider using jmx for additional logging
Full notes of the meeting are here:
http://etherpad.wikimedia.org/p/DiscoveryOpsWDQS
Kevin Smith
Agile Coach
Wikimedia Foundation
*Imagine a world in which every single human being can freely share in the
sum of all knowledge. That's our commitment. Help us make it a reality.*
If the query returned 0 results and didn't have any syntax (no intitle:foo)
in it, should we try _harder_ to get suggestions? I don't know exactly what
that changes that means but we can totally implement the retry if we think
it'll help.
The idea is that it might not be performant enough to run super duper
strong suggester settings all the time and when there are no results it
important to have suggestions.
For reference, only 20% of 0 results queries that I counted this morning
returned a suggestion. I don't know how many asked for it though.
Hi all,
As a reminder, all[1] of your Discovery-related research and coding work
should be tracked in phabricator. During our Tuesday/Thursday standups,
most of what you talk about should be tasks on one of the "sprint"
workboards. If you are working on a task that isn't in the sprint board,
please a) re-check to be sure that is the highest priority thing you should
be working on, and b) if it is, add it to phabricator and/or to the sprint
board as needed.
When you pick what to work on, try to grab something from near the top of
the sprint's Backlog column, and move it to In Progress. Please use the
Needs Review column as needed, and when the task is really done, move it to
Done.
Each sub-team should be focused on its quarterly goal. Please be sure that
Dan is aware of any work you do outside that. If you have any questions,
check with him, me, or a team lead.
[1] If you do a 15-minutes task here or there, it doesn't need to be
tracked in phab. But any substantive work should be. Personally I would set
the threshold at about an hour, but your mileage may vary.
Thanks much!
Kevin Smith
Agile Coach
Wikimedia Foundation
*Imagine a world in which every single human being can freely share in the
sum of all knowledge. That's our commitment. Help us make it a reality.*