Hi Everyone,
We’re happy to announce the January 2020 edition of the Technical Community
Newsletter
<https://www.mediawiki.org/wiki/Technical_Community_Newsletter/2020/January>.
The newsletter is compiled by the Wikimedia Developer Advocacy Team. It
aims to share highlights, news, and information of interest from and about
the Wikimedia technical community.
Check it out, and learn about what technical contributors have been up to
this past quarter, upcoming conferences & calls for papers, and how to get
involved.
The Wikimedia Technical Community is large and diverse, and we know we
can't capture everything perfectly. We welcome your ideas for future
newsletters. Let us know what you would like to see or highlights you would
like us to include.
Subscribe to the Technical Community Newsletter
<https://www.mediawiki.org/wiki/Newsletter:Technical_Community_Newsletter>,
if you'd like to keep up with essential updates and information.
Kindly,
Sarah R. Rodlund
Technical Writer, Developer Advocacy
srodlund(a)wikimedia.org
We'll be upgrading the cloud services OpenStack install next Tuesday,
beginning at 12:00 noon UTC
The entire upgrade process may take an hour or two. Early on in the
process, Horizon (and associated OpenStack APIs) will be disabled
(probably for 20 to 30 minutes.) There may also be brief network
interruptions during the upgrade.
Toolforge and existing VMs should be largely unaffected apart from
possible network hiccups.
- Andrew + the WMCS team
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce
I've got a django-based tool that I was previously running in test mode directly on the bastion hosts using runserver. Now I'm trying to move that over the kubernetes for production. I've got things to the point where I can bring up a pod and see the server start by watching uwsgi.log:
> SIGINT/SIGQUIT received...killing workers...
> worker 1 buried after 1 seconds
> worker 2 buried after 1 seconds
> worker 3 buried after 1 seconds
> worker 4 buried after 1 seconds
> goodbye to uWSGI.
> *** Starting uWSGI 2.0.18-debian (64bit) on [Sun Jan 12 05:28:38 2020] ***
> compiled with version: 8.2.0 on 10 February 2019 02:42:46
> os: Linux-4.9.0-0.bpo.8-amd64 #1 SMP Debian 4.9.144-3.1~deb8u1 (2019-03-14)
> nodename: spi-tools-3688113665-jl049
> machine: x86_64
> clock source: unix
> pcre jit disabled
> detected number of CPU cores: 4
> current working directory: /data/project/spi-tools
> detected binary path: /usr/bin/uwsgi-core
> chdir() to /data/project/spi-tools/www/python/src
> your memory page size is 4096 bytes
> detected max file descriptor number: 65536
> lock engine: pthread robust mutexes
> thunder lock: disabled (you can enable it with --thunder-lock)
> uwsgi socket 0 bound to TCP address :8000 fd 3
> Python version: 3.7.3 (default, Apr 3 2019, 05:39:12) [GCC 8.3.0]
> PEP 405 virtualenv detected: /data/project/spi-tools/www/python/venv
> Set PythonHome to /data/project/spi-tools/www/python/venv
> *** Python threads support is disabled. You can enable it with --enable-threads ***
> Python main interpreter initialized at 0x55ce19eedee0
> your server socket listen backlog is limited to 100 connections
> your mercy for graceful operations on workers is 60 seconds
> mapped 364600 bytes (356 KB) for 4 cores
> *** Operational MODE: preforking ***
> mounting /data/project/spi-tools/www/python/src/app.py on /spi-tools
> WSGI app 0 (mountpoint='/spi-tools') ready in 3 seconds on interpreter 0x55ce19eedee0 pid: 1 (default app)
> *** uWSGI is running in multiple interpreter mode ***
> spawned uWSGI master process (pid: 1)
> spawned uWSGI worker 1 (pid: 7, cores: 1)
> spawned uWSGI worker 2 (pid: 8, cores: 1)
> spawned uWSGI worker 3 (pid: 9, cores: 1)
> spawned uWSGI worker 4 (pid: 10, cores: 1)
which I assume means my server is actually up and running. But, how do I connect to it? What URL is it behind?
As far as I can tell, there's currently no way to search this list other than month-by-month via the pipermail archive page <https://lists.wikimedia.org/pipermail/cloud/>?
Not sure what the process is here, but I gather (from T193572 <https://phabricator.wikimedia.org/T193572>) that each list has to individually approve being indexed by google. If that's the case, then I propose this list be indexed.
Hello Everyone,
I am curious to know that is it possible to access the Wikimedia commons
file in the Toolforge/CloudVPS? Like in the toolforge, we have some mount
points to access the XML dump.
In short, I want to copy the video files in my tool directory instead of
downloading them from Wikimedia commons.
Thanks :) Regards
There seem to be weird things going on.
This is error.log for my tool:
The problem is I didn't shut it down. So what did?
Is this is a bug or someone hacking around or something.
I did notice some problems last year. After 2019-12-12. I assumed that
was a direct consequence of maintenance that happened on that day.
But just to be sure this my log from 2019-12-12:
2019-12-12 11:47:22: (log.c.217) server started
2019-12-12 11:48:38: (log.c.217) server started
Traceback (most recent call last):
File "/usr/bin/webservice-runner", line 30, in <module>
webservice.run(port)
File
"/usr/lib/python2.7/dist-packages/toollabs/webservice/services/lighttpdwebservice.py",
line 656, in run
with open(config_path, 'w') as f:
IOError: [Errno 13] Permission denied: '/var/run/lighttpd/dna'
2019-12-12 11:52:26: (server.c.1751) [note] graceful shutdown started
2019-12-12 11:52:26: (server.c.1828) server stopped by UID = 51936 PID =
16488
2019-12-12 11:52:28: (server.c.1751) [note] graceful shutdown started
2019-12-12 11:52:28: (server.c.1828) server stopped by UID = 51936 PID =
29249
2019-12-12 12:39:37: (log.c.217) server started
Traceback (most recent call last):
File "/usr/bin/webservice-runner", line 30, in <module>
webservice.run(port)
File
"/usr/lib/python2.7/dist-packages/toollabs/webservice/services/lighttpdwebservice.py",
line 656, in run
with open(config_path, 'w') as f:
IOError: [Errno 13] Permission denied: '/var/run/lighttpd/dna'
2019-12-23 20:32:33: (server.c.1464) server started (lighttpd/1.4.53)
2019-12-27 10:51:14: (server.c.1464) server started (lighttpd/1.4.53)
2019-12-30 23:21:10: (server.c.2059) server stopped by UID = 0 PID = 0
2019-12-30 23:21:27: (log.c.217) server started
That on 2019-12-23 was not me either, but that was on request via IRC.
Cheers,
Nux.