[Gluster-devel] [Gluster-infra] NetBSD regressions not being triggered for patches
mscherer at redhat.com
Wed Jun 17 13:14:31 UTC 2015
Le mercredi 17 juin 2015 à 11:58 +0100, Justin Clift a écrit :
> On 17 Jun 2015, at 10:53, Michael Scherer <mscherer at redhat.com> wrote:
> > Le mercredi 17 juin 2015 à 11:48 +0200, Michael Scherer a écrit :
> >> Le mercredi 17 juin 2015 à 08:20 +0200, Emmanuel Dreyfus a écrit :
> >>> Venky Shankar <yknev.shankar at gmail.com> wrote:
> >>>> If that's the case, then I'll vote for this even if it takes some time
> >>>> to get things in workable state.
> >>> See my other mail about this: you enter a new slave VM in the DNS and it
> >>> does not resolve, or somethimes you get 20s delays. I am convinced this
> >>> is the reason why Jenkins bugs.
> >> But cloud.gluster.org is handled by rackspace, not sure how much control
> >> we have for it ( not sure even where to start there ).
> > So I cannot change the DNS destination.
> > What I can do is to create a new dns zone, and then, we can delegate as
> > we want. And migrate some slaves and not others, and see how it goes ?
> > slaves.gluster.org would be ok for everybody ?
> Try it out, and see if it works. :)
> On the "scaling the infrastructure" side of things, are the two OSAS servers
> for Gluster still available?
They are online.
$ ssh root at ci.gluster.org uptime
09:13:37 up 33 days, 16:34, 0 users, load average: 0,00, 0,01, 0,05
> If so, we should get them online ASAP, as that will give us ~40 new VMs
> + get us out of iWeb (which I suspect is the problem).
I suspect too. But then that mean migrating jenkins and everything, and
I would prefer a quick fix. I am looking at the dns solution.
Sysadmin, Community Infrastructure and Platform, OSAS
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: This is a digitally signed message part
More information about the Gluster-devel