Just moving Gerrit and Jenkins out of iWeb should help a lot. On Wed, Jun 17, 2015 at 4:28 PM, Justin Clift <justin@xxxxxxxxxxx> wrote: > On 17 Jun 2015, at 10:53, Michael Scherer <mscherer@xxxxxxxxxx> 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@xxxxxxxxx> 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? > > 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). > > Regards and best wishes, > > Justin Clift > > -- > GlusterFS - http://www.gluster.org > > An open source, distributed file system scaling to several > petabytes, and handling thousands of clients. > > My personal twitter: twitter.com/realjustinclift > > _______________________________________________ > Gluster-infra mailing list > Gluster-infra@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-infra _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
