Hello,
I'm trying to tunnel to my VPS Trove instance, so that I can test some code
against the production database.
I'm using the following:
ssh -N -L 4177:tdlqt33y3nt.svc.trove.eqiad1.wikimedia.cloud:3306
login.toolforge.org
I've also tried:
ssh -N -L 4177:tdlqt33y3nt.svc.trove.eqiad1.wikimedia.cloud:3306
mwcurator.mwoffliner.eqiad1.wikimedia.cloud
The initial connection seems to work, but in my application I'm getting
dropped connections. I see the following in the terminal where I set up the
tunnel:
channel 2: open failed: connect failed: Connection refused
channel 2: open failed: connect failed: Connection refused
I imagine this isn't a fully supported workflow but I'm wondering if
there's some way to get it to work?
Thanks,
-Travis
Hello Cloud users,
Just wanted to give a heads-up for an upcoming maintenance for our cloudelastic hosts <https://wikitech.wikimedia.org/wiki/Help:CirrusSearch_elasticsearch_replicas>. We will be migrating them to a new load balancer starting Thursday, Jun 20 at 1400 UTC . The service will be down through the maintenance, which is expected to last between 1 and 2 hours.
Fine details are available in this Phabricator task <https://phabricator.wikimedia.org/T367511> . If you have any questions about this, feel free to respond here or in IRC (see my nick below).
Best,
Brian King
SRE, Data Platform/Search Platform
Wikimedia Foundation
IRC: inflatador
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
Hi all!
This is to let you know that Toolforge continuous jobs now support internal
domain names!
This means you can now make a request from any job type to a continuous job
using the name of the continuous job directly, without having to know or
keep track of its internal ephemeral IP address.
To use it you need to specify `--port <number>` while creating
your continuous job. Once done your continuous job can now be reached from
other jobs with `https://<continuous-job-name>:<port>`.
Note: This can only be configured for continuous jobs.
Note: The name of the continuous job automatically becomes the internal
domain name and there is currently no way to specify a custom name.
Also, a reminder that you can find this and smaller user-facing updates
about
the Toolforge platform features here:
https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Changelog
Original task: https://phabricator.wikimedia.org/T348758
--
Ndibe Raymond Olisaemeka
Software Engineer - Technical Engagement
Wikimedia Foundation <https://wikimediafoundation.org/>
<https://wikimediafoundation.org>
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
Hi,
I've added a new set of flavors on Cloud VPS.[0] The new flavors are
almost identical to the existing `g3` flavors - the only difference is
that instances on the new `g4` flavors get scheduled on hypervisors
running more modern networking software.[1] When creating new
instances, either by hand or via some automated means, please use the
new flavors from now on. Using g3 flavors for new instances will be
disabled in the coming days.
We will be migrating existing VMs to the new flavors at some point in
the near future. This will most likely involve briefly shutting down
each VM as it's migrated from one network agent to the other. There
will be a dedicated announcement for that once the timeline on that is
more certain. As always, if your project needs some coordination
before restarting things or this is otherwise a problem, feel free to
contact us.[2]
Migrating a g3 instance to a g4 flavor (or the other way around)
without manual intervention would instead make that instance
inaccessible. For that reason instance resizing has temporarily been
disabled, if you need to resize an existing instance for whatever
reason before it's been migrated please contact us.
[0]: https://wikitech.wikimedia.org/wiki/Help:Cloud_VPS_Instances#Instance_infor…
[1]: https://phabricator.wikimedia.org/T364458
[2]: https://wikitech.wikimedia.org/wiki/Help:Cloud_Services_communication
Taavi
--
Taavi Väänänen (he/him)
Site Reliability Engineer, Cloud Services
Wikimedia Foundation
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
Cloud-vps users:
There are now a mere two weeks remaining before Debian Buster ends its
period of long term support. After June 30th, security upgrades will no
longer be available for this release and VMs running Buster will become
ever more risky and difficult to maintain.
As of today there are still 143 Buster servers running in our cloud[0]
-- some of them are probably yours! Please take some time to delete VMs
that are no longer needed, and rebuild those that are still needed with
a more modern release, ideally Debian Bookworm.
There is a task for your project on phabricator[1] where you can update
your progress. If you have vital VMs that you absolutely cannot rebuild
by July 15th, please update the associated task with your plan and
anticipated timeline. WMCS staff will start shutting down unacknowledged
VMs in mid July in order to attract the attention of users who do not
read email or follow phabricator.
Buster's end of life has been a long time coming, and frequently
announced. If you've been waiting for the right time to think about
this, the time is now.
Thank you!
-Andrew + WMCS staff
[0] https://os-deprecation.toolforge.org/
[1] https://phabricator.wikimedia.org/project/view/6373/
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
Following several requests from users over the past eight years [0],
we are finally enabling access to ToolsDB's "public" databases (the
ones with a name ending with "_p") [1] from both Quarry [2] and
Superset [3].
The data stored in those databases have always been accessible to
every Toolforge user, but after this change they will become more
broadly accessible, as Quarry can be accessed by anyone with a
Wikimedia account, and saved queries in Quarry can be shared with
public links that require no login at all.
== This change is planned to go live on Monday, July 1st. ==
If you have any concerns or questions related to this change, please
leave a comment in the Phabricator task or one of its subtasks. [0]
Thanks to everyone for your patience and for keeping the task alive
over the years!
[0] https://phabricator.wikimedia.org/T151158
[1] https://wikitech.wikimedia.org/wiki/Help:Toolforge/Database#Privileges_on_t…
[2] https://meta.wikimedia.org/wiki/Research:Quarry
[3] https://superset.wmcloud.org/
--
Francesco Negri (he/him) -- IRC: dhinus
Site Reliability Engineer, Cloud Services team
Wikimedia Foundation
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
Hello all,
The Code of Conduct Committee is a team of five trusted individuals (plus
five auxiliary members) with diverse affiliations responsible for general
enforcement of the Code of conduct for Wikimedia technical spaces.
Committee members are in charge of processing complaints, discussing with
the parties affected, agreeing on resolutions, and following up on their
enforcement. For more on their duties and roles, see
https://www.mediawiki.org/wiki/Code_of_Conduct/Committee.
This is a call for community members interested in volunteering for
appointment to this committee. Volunteers serving in this role should be
experienced Wikimedians or have had experience serving in a similar
position before.
The current committee is doing the selection and will research and discuss
candidates. Six weeks before the beginning of the next Committee term, they
will publish their candidate slate (a list of candidates) on-wiki. The
community can provide feedback on these candidates, via private email to
the group choosing the next Committee. The feedback period will be two
weeks. The current Committee will then either finalize the slate, or update
the candidate slate in response to concerns raised. If the candidate slate
changes, there will be another two week feedback period covering the newly
proposed members. After the selections are finalized, there will be a
training period, after which the new Committee is appointed. The current
Committee continues to serve until the feedback, selection, and training
process is complete.
If you are interested in serving on this committee or like to nominate a
candidate, please write an email to techconductcandidates AT wikimedia.org
with details of your experience on the projects, your thoughts on the code
of conduct and the committee and what you hope to bring to the role and
whether you have a preference in being auxiliary or main member of the
committee. The committee consists of five main members plus five auxiliary
members and they will serve for a year; all applications are appreciated
and will be carefully considered. The deadline for applications is *the end
of day on June 25, 2024*.
Please feel free to pass this invitation along to any users who you think
may be qualified and interested.
Best,
Amir Sarabadani, on behalf of the Code of Conduct Committee
There is as-of-yet undiagnosed issue with our storage system (ceph)
which is causing serious failures throughout cloud-vps and toolforge.
Multiple people are working on the issue, so watch this list for
updates. Sorry for the downtime!
-Andrew + wmcs team
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
Hello all,
The next language community meeting is scheduled in a few weeks - May 31st
at 16:00 UTC. If you're interested, you can sign up on this wiki page: <
https://www.mediawiki.org/w/index.php?title=Wikimedia_Language_engineering/…
>.
This is a participant-driven meeting, where we share language-specific
updates related to various projects, collectively discuss technical issues
related to language wikis, and work together to find possible solutions.
For example, in the last meeting, the topics included the machine
translation service (MinT) and the languages and models it currently
supports, localization efforts from the Kiwix team, and technical
challenges with numerical sorting in files used on Bengali Wikisource.
Do you have any ideas for topics to share technical updates related to your
project? Any problems that you would like to bring for discussion during
the meeting? Do you need interpretation support from English to another
language? Please reach out to me at ssethi(a)wikimedia.org and add
agenda items to the document here: <
https://etherpad.wikimedia.org/p/language-community-meeting-may-2024>.
We look forward to your participation!
Cheers,
Jon, Mary, Oscar, Amir and Srishti
*Srishti Sethi*
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>