Holger Levsen writes ("Re: Test instance of our infrastructure"):
> On Mon, Nov 28, 2016 at 12:04:17PM +0000, Ian Jackson wrote:
> > I suggest we should declare (perhaps as a DEP?)
>
> or a wiki page, at least at first…?
Sure, whatever.
> > * Most of our services are addressed via domain names,
> > *.debian.org or *.debian.net. Test instance of a service are
> > correspondingly at *.infratest.debian.{org,net}.
>
> I'm not sure .debian.net should be included, probably those services
> should be moved to .debian.org first?
Well, maybe, but maybe not. I don't think we should discourage anyone
who is running a .debian.net service from providing a test instance.
Rather we should encourage them to do so. (Moving a .debian.net
service to .debian.org will be easier if there is a test instance to
try moving first...)
> > I think it will be work at first but make a lot of things easier.
>
> I agree. And even if we cannot agree (or do!) this as a project at
> first, individual instances can do this now, already. eg, there *is*
> http://jenkins-test-vm.debian.net:8080/ though there is none for
> piuparts nor reproducible builds stuff… - patches welcome! ;-)
Right.
My idea is not that we will expect this of everyone. Rather, I want
to provide some mild encouragement, and a standardised framework about
what a test instance should probably look like.
Niels Thykier writes ("Re: Test instance of our infrastructure"):
> I am happy to setup a lintian and a britney for the test infrastructure
> (provided a server to do this). For both cases, we can set them up
> using the main archive as source until there is an test archive[1] (ftp
> + wanna-build).
Great.
> To be honest, I suspect we can bootstrap a test instance of most
> services very easily that way and then re-configure them as their
> integrations get their test instance ready.
Well, excellent.
> As an additional plus, we can use the test infrastructure as DSA's play
> ground for testing their upgrades to the next stable release!
That would be one of the possibilities, yes.
> Can we have all this before 5th of Feb please? ;)
Ha ha :-).
> [1] Obviously, the test Britney should discard its results rather than
> feeding them to the production instance of DAK. But that is a rather
> small part and in some glue code rather in Britney itself.
Well, if there is a test Britney it wouldn't have the keys etc. of the
real Britney. So if you misconfigured it, it would get a lot of
access control failures or signature mismatch meails or whatever.
If that's not the case then we have a bigger problem...
Ian.
