-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/08/15 10:54, Karanbir Singh wrote: > On 10/08/15 09:43, Fabian Arrotin wrote: >> On 10/08/15 10:22, Karanbir Singh wrote: >>> hi, >> >>> What are the main concerns for hosting some builder hardware >>> geo-distributed from the main koji hub ? Apart from the >>> latency thing, but given that most builders spend all their >>> time in mock root builds and then the rpmbuild, if we can get >>> gbit links to the remote machines, we should be ok right ? >> >>> regards, >> >> >> well, a robust vpn solution in place, as all koji builders need >> access to the (nfs shared) central repo. But instead of just >> having gbit link at the remote machines end, we should start then >> by having gbit link at the origin, which will not be the case. > > Are you saying that the blades in the same blade center dont have a > gbit link to each other ? isnt that where / how the present koji > origin is setup ? > No, but you were talking about geo-distributed, so surely not in the same DC, and so the remark for the need for a gbit internet connection. The link we have is actually shared with multiple projects, so no QoS on that and I don't know how the nfs-though-vpn IO operations will handle that. I guess remote builders don't need really gbit either .. people experienced with Koji should now answer :-) - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlXIZ/EACgkQnVkHo1a+xU5uyACaAjiG9ry78cuoeOXi+2LxyNl0 9rMAoIgQJLtiwKkNxVPQZGueCx1nLiFt =RBKY -----END PGP SIGNATURE-----