Event bus service does not use analytics Kafka though. I would argue that analytics Kafka is tier 1
> On Nov 18, 2016, at 12:12, Gabriel Wicke <gwicke(a)wikimedia.org> wrote:
>
> EventBus is definitely tier-1. It provides a communication backbone that is used for reliable event processing. Delays in update processing cause directly user-visible issues like outdated information, performance regressions in VisualEditor & other use cases, and unavailability of public event streams. Timely processing of events like revision deletions is security-relevant.
>
>> On Fri, Nov 18, 2016 at 9:07 AM, Nuria Ruiz <nuria(a)wikimedia.org> wrote:
>> Team:
>>
>> (services cc-ed)
>>
>> We need to define whether kafka on the analytics cluster is a tier-1 or tier-2 system in order to decide the level of support. At this time an issue with a kafka host pages the whole ops team and I am not sure whether this is needed.
>>
>> From the standpoint of 'anything' analytics kafka is a tier-2 piece on infrastructure (https://wikitech.wikimedia.org/wiki/Analytics/Tier2). I am not sure as to the EventBus use cases ,though. Can the services team detail the use cases for EventBus that would make it tier-1?
>>
>> I want to make sure we are all in the same page when it comes to define something as tier-1: tier-1 means that is as important as the database or varnish or any of the core pieces of infrastructure that allow us to operate. Powering a feature that users use, like, say, a part of the Android application doesn't make a service tier-1, it just makes it user-facing. That does not necessarily imply that it needs 24/7 support.
>>
>> Could services team let us know as to the clients of Event Bus as of now that would make it a tier-1 service?
>>
>> Thanks,
>>
>> Nuria
>>
>>
>>
>>
>>
>
>
>
> --
> Gabriel Wicke
> Principal Engineer, Wikimedia Foundation
> _______________________________________________
> Analytics-internal mailing list
> Analytics-internal(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/analytics-internal
Hello,
Just a short FYI to let you know that tin.eqiad.wmnet has been reimaged and
is now fully working. That means that the transition period of deploying
from mira is over. You should had on to tin for all deployments from now
on. I have updated the relevant Scap configuration files in the deployment
repos, so no particular action is needed on your part.
Cheers,
Marko
--
Marko Obrovac, PhD
Senior Services Engineer
Wikimedia Foundation
Dear Wiki Team,
I am Parthasarathy, Civil Engineer form INDIA, Am Using Wikipedia and
Wikihow for more than 7 years, i sincerely want to thank you for your
service.
Wiki helped me in several occasions in my technical carrier and daily life
style needs.
I sincerely admit that Wiki is ultimate for any thing.
I would like to suggest that Wikimedia need to launch "WIKIWHY" and
"WIKIWHAT"in future to fulfill the needs for Daily lifestyle related quires
with technically. I hope you will start those services soon.
Thanks & Regards,
Parthasarathy.
+91 80983 24254
Hello,
As of today, the SCB cluster consists of 4 machines in each DC, which
spreads the load more evenly and allows for better handling of bad
situations. Kudos to Alex who carried out the work of re-purposing the
ex-SCA nodes (by previously moving Zotero to VMs)~[1]. The deploy
repositories of SCB services have been updated~[2], so you don't have to
adapt to the new situation - just deploy as normal, but see your service
deployed to 8 instead of 4 nodes total :)
Cheers,
Marko
[1] https://phabricator.wikimedia.org/T148380
[2] https://phabricator.wikimedia.org/T147903
--
Marko Obrovac, PhD
Senior Services Engineer
Wikimedia Foundation
Hello,
Node v4.6.0 represents a security release of the current Node.JS LTS line.
The package is already in our APT repo and we plan to upgrade production
clusters soon. Please test your services with the new release.
For the SCB cluster, I have tested all of the services and there is
currently a blocker for proceeding with upgrade~[1]. As soon as that one is
resolved, I will be uploading and merging changes for SCB-bound services,
since the switch must be done for all services at the same time. Even
though I tested all of the services, I invite you to double-check and make
sure that your respective service does not suffer from any problems or
regressions because of the imminent switch.
If you notice any problems or have any questions or concerns, please let me
know ASAP.
Cheers,
Marko
[1] https://phabricator.wikimedia.org/T147849
--
Marko Obrovac, PhD
Senior Services Engineer
Wikimedia Foundation
Hello!
The Wikimedia Developer Summit
<https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit> is the annual
meeting to push the evolution of MediaWiki and other technologies
supporting the Wikimedia movement. The next edition will be held in San
Francisco on January 9-11, 2017.
We welcome all Wikimedia technical contributors, third party developers,
and users of MediaWiki and the Wikimedia APIs. We specifically want to
increase the participation of volunteer developers and other contributors
dealing with extensions, apps, tools, bots, gadgets, and templates.
Important deadlines:
- Monday, October 24: This is the last day to request travel
sponsorship. Applying takes less than five minutes.
- Monday, October 31: This is the last day to propose an activity. Bring
the topics you care about!
Subscribe to weekly updates: https://www.mediawiki.org/
wiki/Topic:Td5wfd70vptn8eu4
Please feel free to forward this email to anyone who might be interested in
attending!
Thanks,
Srishti
--
Srishti Sethi
ssethi(a)wikimedia.org
We are going to finally switch off the deprecated domain rest.wikimedia.org
by September 1st. This should not affect any REST API users, as this domain
has been officially deprecated since January & sunset since April [1].
Since then, requests to that domain have returned an error informing users
about the move.
Access to the REST API is exclusively through the main project domains,
following the following pattern:
https://en.wikipedia.org/api/rest_v1/?doc
Thank you for your cooperation,
--
Gabriel Wicke
Principal Engineer, Wikimedia Foundation
[1]: https://lists.wikimedia.org/pipermail/wikitech-l/2016-April/085309.html
Hello, REST API users.
We are planning to deploy a new REST API endpoint for section editing next
week. This will replace the current /transform/sections/to/wikitext/
<https://en.wikipedia.org/api/rest_v1/#!/Transforms/post_transform_sections_…>
end point, and will provide the same functionality in a more streamlined
and extensible format.
The existing end point is classified as unstable
<https://www.mediawiki.org/wiki/API_versioning#Unstable>, which guarantees
that we are making an effort to avoid breaking existing clients. According
to our data, the end point is basically unused at present, which is why we
are aiming at a fairly speedy deploy around Tuesday next week (Aug 30). If
you are using this end point at present & have concerns about its removal,
then let us know here.
Best regards,
the WMF Services Team <https://www.mediawiki.org/wiki/Wikimedia_Services>.
--
Gabriel Wicke
Principal Engineer, Wikimedia Foundation