DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Addressing git.dpdk.org downtime
Date: Thu, 22 May 2025 10:05:58 +0100	[thread overview]
Message-ID: <aC7o9q3zGx9d0FG_@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <PH7PR12MB91737F14D62A8ADDCAE475CDDA99A@PH7PR12MB9173.namprd12.prod.outlook.com>

On Thu, May 22, 2025 at 08:36:28AM +0000, Ali Alnubani wrote:
> Hello everyone,
> 
> We’re aware that https://git.dpdk.org has been experiencing availability 
> issues lately, largely due to abusive bots and crawlers overloading the servers and ignoring traditional controls like robots.txt.
> 
> To address this, we're preparing to deploy Anubis, a traffic-challenging tool, to help ensure reliable and continued access for the community, starting with our cgit instance. This approach has been adopted by several other open-source projects recently to reduce disruptive automated traffic.
> 
> Please reach out if you have questions or encounter issues.
> 
> See: https://github.com/TecharoHQ/anubis
> 
> Thanks,
> Ali

Thanks Ali, (and others involved) for taking action on this.

To everyone else in the community, just a reminder that, rather than
accessing dpdk.org site directly, you can use
"https://github.com/DPDK/dpdk" as a source for getting and browsing the
DPDK source code. The github mirror is always in sync with the main tree,
and, as an added convenience, also has the various "next" trees mirrored to
it too. This means that you don't need to clone multiple trees to get e.g.
next-net tree as well as main tree.

For any companies looking to have internal mirrors of the DPDK repository
for internal use, it's recommended that those mirrors be based on github
rather than on dpdk.org directly. This all helps reduce load on the server.

Thanks,
/Bruce

  reply	other threads:[~2025-05-22  9:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22  8:36 Ali Alnubani
2025-05-22  9:05 ` Bruce Richardson [this message]
2025-05-22 13:00   ` David Marchand
2025-05-22 14:31 ` Ali Alnubani

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aC7o9q3zGx9d0FG_@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=alialnu@nvidia.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).