Le jeudi 18 juin 2015 à 10:19 +0200, Niels de Vos a écrit : > On Thu, Jun 18, 2015 at 12:57:05AM +0100, Justin Clift wrote: > > On 17 Jun 2015, at 20:14, Niels de Vos <ndevos@xxxxxxxxxx> wrote: > > > On Wed, Jun 17, 2015 at 03:14:31PM +0200, Michael Scherer wrote: > > >> Le mercredi 17 juin 2015 à 11:58 +0100, Justin Clift a écrit : > > >>> 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? > > >> > > >> They are online. > > >> $ ssh root@xxxxxxxxxxxxxx uptime > > >> 09:13:37 up 33 days, 16:34, 0 users, load average: 0,00, 0,01, 0,05 > > > > > > Can it run some Jenkins Slave VMs too? > > > > There are two boxes. A pretty beefy one for running Jenkins slave VM's (probably > > about 40 VM's simultaneously), and a slightly less beefy one for running > > Jenkins/Gerrit/whatever. > > Good to know, but it would be much more helpful if someone could install > VMs there and add them to the Jenkins instance... Who can do that, or > who can guide someone else to get it done? Justin and I have our keys automatically added to all salt managed servers and this one is one of them ( and I plan to make sure it stay one of them, so any change should be pushed to salt ). The issue is getting more public IP for the VMs. Since we have a model where jenkins push to the slaves, they need to communicate. Either we set a VPN, or we try to find public ips. But since we are in a hurry, I will take the VPN road. Installing the VM in some automated way shouldn't be too hard, 90% of it is in salt now. The biggest issue is the virtualisation infra to setup in a proper way, and what kind of slave do we want. -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
