On Fri, Aug 16, 2019 at 01:35:58PM +0800, Aron Xu wrote:
> even we can have its own Openstack
> installation if the team really like it.
You really want to maintain an OpenStack installation? Have you done
so already? Have you done upgrades of this installation for at
Hello,
Missatge de Thomas Goirand del dia dg., 18 d’ag.
2019 a les 0:15:
> I'm all for it. The DSA team can use my installer, who's in Buster [1].
Great! DSA will evaluate such option now that it is in Buster.
> But last time I checked, the DSA team refused both my help and the idea
> to run
On 8/16/19 7:35 AM, Aron Xu wrote:
> On Thu, Aug 15, 2019 at 6:23 PM Thomas Goirand wrote:
>> [...]
>> 1/ CI Jobs going faster
>> 2/ Have a way more workers
>> 3/ Don't have all our eggs on the same Google basket
>> 4/ Use free software platforms instead of GCE
>> 5/ Stop being bound to a single
gregor herrmann writes ("Re: salsa.debian.org partially down"):
> Ack. And that's all I wanted to say: that I found Ian's term "foolish
> user action" inappropriate in this case of an accidental DOS.
Err, yes. I retract that comment. I had misunderstood what had
occur
On Fri, 16 Aug 2019 10:30:07 +0200, Alexander Wirt wrote:
> > > On Fri, 16 Aug 2019, gregor herrmann wrote:
> > > > I don't see any reason for calling this action itself foolish.
> And as I said, you will always find ways to ddos a service (that does not
> mean the user was foolish, intended to
On Fri, 16 Aug 2019, Alexander Wirt wrote:
> I am a bit surprised, from the first day on we said that there are limited
> ressources for ci and that you should be nice to the service. Thats even
> documented:
>
> "We mean that. Really. Be nice to the server. At some point in the future we
>
On Fri, 16 Aug 2019, Raphael Hertzog wrote:
> Hi,
>
> On Fri, 16 Aug 2019, gregor herrmann wrote:
> > From what I know, this what not a "foolish user action" but an action
> > by a dedicated maintainer who enabled salsa-ci for all packages
> > ("projects") of a specific team; so they used a
Hi,
On Fri, 16 Aug 2019, gregor herrmann wrote:
> From what I know, this what not a "foolish user action" but an action
> by a dedicated maintainer who enabled salsa-ci for all packages
> ("projects") of a specific team; so they used a service advertised by
> the salsa and salsa-ci teams. That
On Fri, 16 Aug 2019, Daniel Leidert wrote:
> Am Freitag, den 16.08.2019, 08:58 +0200 schrieb Alexander Wirt:
> > On Fri, 16 Aug 2019, gregor herrmann wrote:
>
> [..]
> > > From what I know, this what not a "foolish user action" but an action
> > > by a dedicated maintainer who enabled salsa-ci
Am Freitag, den 16.08.2019, 08:58 +0200 schrieb Alexander Wirt:
> On Fri, 16 Aug 2019, gregor herrmann wrote:
[..]
> > From what I know, this what not a "foolish user action" but an action
> > by a dedicated maintainer who enabled salsa-ci for all packages
> > ("projects") of a specific team; so
On Fri, 16 Aug 2019, gregor herrmann wrote:
> On Wed, 14 Aug 2019 08:39:22 +0100, Ian Jackson wrote:
>
> > Alexander Wirt writes ("Re: salsa.debian.org partially down"):
> > > It is already recovered. We will investigate where we can extend the
> > &
On Thu, Aug 15, 2019 at 6:23 PM Thomas Goirand wrote:
> [...]
> 1/ CI Jobs going faster
> 2/ Have a way more workers
> 3/ Don't have all our eggs on the same Google basket
> 4/ Use free software platforms instead of GCE
> 5/ Stop being bound to a single VM provider [1]
>
Would it be more
On Wed, 14 Aug 2019 08:39:22 +0100, Ian Jackson wrote:
> Alexander Wirt writes ("Re: salsa.debian.org partially down"):
> > It is already recovered. We will investigate where we can extend the
> > ressources. But some misusages (like requesting >1300 merge requests
Hi Thomas
On Thu, Aug 15, 2019 at 12:22:58PM +0200, Thomas Goirand wrote:
> I probably should have mentioned that my remark was not so much related
> to the crash, but more to what I experienced using Salsa's CI.
If your remarks don't relate to the subject, please start a new thread,
or at least
On 8/15/19 11:03 AM, Ian Jackson wrote:
> (off-list)
>
> Ian.
You replied off-list, so I wont quote you, though I would like my answer
to be public.
I probably should have mentioned that my remark was not so much related
to the crash, but more to what I experienced using Salsa's CI. It's
On Wed, Aug 14, 2019 at 10:53:56AM +0200, Thomas Goirand wrote:
> On 8/13/19 1:59 PM, Alexander Wirt wrote:
> > It is already recovered. We will investigate where we can extend the
> > ressources. But some misusages (like requesting >1300 merge requests via API
> > on a big project, that in
On 8/13/19 1:59 PM, Alexander Wirt wrote:
> It is already recovered. We will investigate where we can extend the
> ressources. But some misusages (like requesting >1300 merge requests via API
> on a big project, that in consequence run >1300 ci jobs, that...) can't be
> solved regardless on how
Alexander Wirt writes ("Re: salsa.debian.org partially down"):
> It is already recovered. We will investigate where we can extend the
> ressources. But some misusages (like requesting >1300 merge requests via API
> on a big project, that in consequence run >1300 ci jobs, t
On Tue, 13 Aug 2019, Hector Oron wrote:
> Hello,
>
> Missatge de Bastian Blank del dia dt., 13 d’ag.
> 2019 a les 11:51:
> >
> > Hi folks
> >
> > salsa.debian.org is partially down for now. Especially everything that
> > concerns Salsa CI.
> >
> > Someone decided to inject a few thousand CI
Hello,
Missatge de Bastian Blank del dia dt., 13 d’ag.
2019 a les 11:51:
>
> Hi folks
>
> salsa.debian.org is partially down for now. Especially everything that
> concerns Salsa CI.
>
> Someone decided to inject a few thousand CI jobs using Salsa CI
> yesterday evening. Since then the system
20 matches
Mail list logo
