// sorry for cross-posting
Hello everyone,
the Technical Advice IRC Meeting [1] is taking a 4-week break. The next
meeting will take place in 2019, on January 16.
Also, please take note that there’ll be only one time slot for the
Technical Advice IRC Meeting in 2019: 4 pm UTC.
See you in 2019!
Johanna (for the Technical Advice IRC Meeting crew)
[1] https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Reminder: Technical Advice IRC meeting again **Wednesday 4-5 pm UTC** on
#wikimedia-tech.
Question can be asked in English & German.
The Technical Advice IRC Meeting is a weekly support event for volunteer
developers. Every Wednesday, two full-time developers are available to help
you with all your questions about Mediawiki, gadgets, tools and more! This
can be anything from "how to get started" over "who would be the best
contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for the Technical Advice IRC Meeting crew)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
Hello,
Today we have disabled BigBrother in Toolforge. BigBrother was a tool
that monitored continuous jobs that failed to get restarted because they
ran into corner cases where Grid Engine wasn't sufficiently smart to
re-start them (e.g. out of memory). BigBrother would continuously
monitor those jobs and duplicate that functionality on a layer above
Grid Engine.
Although very few tools used BigBrother (0.65% to be more precise), it
taxed our NFS file server constantly so keeping it around didn't make
much sense. Additionally, its functionality could be easily implemented
with a shell script running from cron.
So we've converted all tools that had a .bigbrotherrc file to using a
bigbrother.sh script that is triggered every 5min to restart jobs. If
your tool used BigBrother, please check your crontab (`crontab -l`) and
will see a few entries like this:
```
# Ensure continuous jobs are running
*/5 * * * * jlocal /data/project/tool_name/bigbrother.sh job_name job_script
```
Documentation has also been updated to reflect this change:
https://wikitech.wikimedia.org/wiki/Help:Toolforge/Grid#Bigbrother_(Depreca…
In our tests everything worked fine but please let us know if your
tool is being impacted by this change.
Regards,
--
Giovanni Tirloni
Operations Engineer
Wikimedia Cloud Services
_______________________________________________
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
On Monday, December 3rd, 2018 at 1700 UTC, we will be rebooting one of the two dumps NFS servers (labstore1006.wikimedia.org <http://labstore1006.wikimedia.org/>). This should cause rising load issues briefly, but should be quick enough that failing over services is likely to not be helpful. We will be failing over the web service before that time and failing it back before rebooting the partner server (labstore1007.wikimedia.org <http://labstore1007.wikimedia.org/>) on Friday, December 7th at 1700 UTC. This should not interrupt services to dumps.wikimedia.org <http://dumps.wikimedia.org/> (the site hosted on these systems) since that should be failed over to the non-rebooting partner.
Brooke Storm
Operations Engineer
Wikimedia Cloud Services
bstorm(a)wikimedia.org <mailto:bstorm@wikimedia.org>
IRC: bstorm_
_______________________________________________
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
The Wikimedia Foundation security team is implementing a new password
policy and requirements. [0] You can learn more about the project on
MediaWiki.org. [1]
These new requirements will apply to new accounts and privileged
accounts. New accounts will be required to create a password with a
minimum length of 8 characters. Privileged accounts will be prompted
to update their password to one that is at least 10 characters in
length.
These changes are planned to be in effect on December 13th. If you
think your work or tools will be affected by this change, please let
us know on the talk page. [2]
[0] https://meta.wikimedia.org/wiki/Password_policy
[1] https://www.mediawiki.org/wiki/Wikimedia_Security_Team/Password_strengtheni…
[2] https://www.mediawiki.org/wiki/Talk:Wikimedia_Security_Team/Password_streng…
Yours,
Chris Koerner
Community Relations Specialist
Wikimedia Foundation
I recently noticed that some of our standard kvm/nova monitoring never
got copied over from the labvirt puppet code to the cloudvirt puppet
code. Tomorrow I will merge
https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/478113/ to fix that.
Once that patch is merged, icinga will be a bit touchier on the
cloudvirts. In particular, it will alert for any cloudvirt that has 0
VMs running on it. (This turns out to be a useful thing to watch for
because we've had cases where every single kvm process died at once.)
So, all 'idle' cloudvirts should nonetheless have a canary instance.
For example, on the new analytics cloudvirts I created canaries like this:
$ OS_PROJECT_ID=testlabs openstack server create --image
7c6371d1-8411-48c7-bf73-2ef6d6ff2a15 --flavor m1.small --nic
net-id=7425e328-560c-4f00-8e99-706f3fb90bb4 --availability-zone
host:cloudvirtan1004 canary-an1004-01
Once a virt host is in full service we can leave the canaries there or
delete them -- there hasn't been any real consistent policy there.
In related news, I'm attempting to silence cloudvirt1019 and 1020
altogether with
https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/478115/ because
we reboot them twice a day and a reboot always kills any running VMs.
-Andrew
_______________________________________________
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
With any luck we'll have some more hardware installed by next week, so
it's time to move more projects! This is probably the last round of
bulk moves; after this it's all special cases for which I'll contact
people directly.
Tuesday, 2018-12-11: maps, wm-bot
Wednesday, 2018-12-12: mwoffliner, wildcat
Thursday, 2018-12-13: snuggle, services, commonsarchive, wikitextexp
Friday, 2018-12-14: queryrapi, wikidumpparse, wikistats, butterfly
Monday 2018-12-17: huggle, incubator, iiab, openrefine, wcdo,
wikidataconcepts
Tuesday 2018-12-18: wikimetrics, newsletter, telnet, signwriting,
ogvjs-ingetration
Wednesday 2018-12-19: multimedia, orig, security-tools, phragile,
wikistream, otrs, yandex-proxy
Thursday 2018-12-20: dashiki, etytree, partnermetrics, graphql
Some context for what this is all about can be found here:
https://phabricator.wikimedia.org/phame/post/view/120/neutron_is_here/
Please let me know if you are involved in one those projects and need to
postpone the move, or schedule a to-the-minute migration window.
- 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
[Apologies if you got multiple copies of this invitation]
The Sixth (IEEE*) International Conference on Software Defined Systems
(SDS-2019)
Rome, Italy. June 10-13, 2019
http://emergingtechnet.org/SDS2019/
(*Technically Co-Sponsored by IEEE Italy Section)
*Call for Papers:*
Next generation cloud systems will require a paradigm shift in how they are
constructed and managed. Conventional control and management platforms are
facing considerable challenges regarding flexibility, dependability and
security that next generation systems will require. The cloud computing
paradigm has gone part of the way towards alleviating some of the problems
associated with resource allocation, utilization and managements (e.g., via
elasticity). However, many of the elements of a well-designed cloud
environment remain “stiff” and hard to modify and adapt in an integrated
fashion. This includes underlying networking topologies, many aspects of
the user control over IaaS, PaaS or SaaS layers when such is needed,
construction of XaaS services, provenance and meta-data collection, and so
on. In many situations the problem may be because service abstraction is
inadequate. Software Defined Systems (SDS) are systems that have added
software components which help abstract actual IT equipment and other
layers. One classical example, of course, are hypervisors. Such separation
provides a great opportunity for system administrators to more easily
construct and managing their systems through flexible software layers.
Software Defined Systems include Software Defined Networking (SDN),
Software Defined Storage, Software Defined Servers (Virtualization),
Software Defined Datacenters (SDD), Software Defined Security (SDSec), and
ultimately Software Defined Clouds (SDCloud) to name a few possibilities.
Individual solutions and seamless integration of these abstractions remains
in many respects a challenge. After the high success of the previous
editions (SDS'2014, SDS'2015, SDS'2016, SDS'2017 and SDS'2018), The sixth
International conference on Software Defined Systems 2019 (SDS'2019) will
continue to be a forum for scientists, researchers, students, and
practitioners to present their latest research results, ideas, and
developments in the area of software defined systems – both components and
their integration - and by implication advancement of next generation
clouds.
SDS 2019 aims to investigate the opportunities and in all aspects of
Software Defined Systems. In addition, it seeks for novel contributions
that help mitigating SDS challenges. That is, the objective of SDS 2019 is
to provide a forum for scientists, engineers, and researchers to discuss
and exchange new ideas, novel results and experience on all aspects of
Software Defined Systems.
Researchers are encouraged to submit original research contributions in all
major areas, which include, but not limited to:
* Software Defined Systems support for Cloud Computing.
* Software Defined Networking (SDN).
* SDN concepts, architecture, and APIs.
* Network Virtualization
* SDN and OpenFlow protocol
* Software Defined Radio
* Cognitive Radio Networks.
* Access Control models in SDN.
* Software Defined Storage.
* Storage Automation and Abstraction.
* Policy-driven storage provisioning.
* Software Defined Servers and Virtualization.
* Software Defined Datacenters.
* Software Defined Security o Security policies automation.
* Self-management systems.
* Autonomic Computing techniques.
* Real-time load prediction model to optimize the user satisfaction.
* Software Defined Systems Scalability.
* Software Defined Systems optimization.
* Software tools and frameworks to support SDS.
* Software Defined Systems challenges and opportunities
* Software Defined Systems surveys.
* Social engineering, insider threats system for SDS.
* Incident Handling and Penetration Testing with SDS.
* Software Defined Systems support if IoT.
* Security protocols in SDS.
* Security and privacy of mobile SDS based cloud computing
* Service-oriented architectures, service portability andP2P
* Network virtualization and cloud-based radio access networks
*Submission*
Papers selected for presentation will appear in the SDS Proceedings, which
will be submitted to IEEE Xplore for inclusion. Papers must be 8 pages in
IEEE format, 10pt font using the IEEE 8.5" x 11" two-column format, single
space, A4 format. All papers should be in PDF format, and submitted
electronically at Paper Submission Link. A full paper must not exceed the
stated length (including all figures, tables and references).
Submitted papers must present original unpublished research that is not
currently under review for any other conference or journal. Papers not
following these guidelines may be rejected without review. Also submissions
received after the due date, exceeding length limit, or not appropriately
structured may also not be considered. Authors may contact the Program
Chair for further information or clarification.
*Important Dates:*
Submission Date: 15 January 2019
Notification to Authors: 1 April 2019
Camera Ready Submission: 20 April 2019
Please send any inquiry on SDS 2019 to the Emerging Tech. Network Team at:
emergingtechnetwork(a)gmail.com
Reminder: Technical Advice IRC meeting again **Wednesday at 4-5 pm UTC AND
11-12 pm UTC** on #wikimedia-tech.
The Technical Advice IRC Meeting (TAIM) is a weekly support event for
volunteer developers. Every Wednesday, two full-time developers are
available to help you with all your questions about Mediawiki, gadgets,
tools and more! This can be anything from "how to get started" over "who
would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for the Technical Advice IRC Meeting crew)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.