On Fri, 2015-12-04 at 13:57 +0000, Ian Jackson wrote: > Specify both HttpProxy and DebianMirrorProxy. In my tests this seems > to improve some of the apparently-intercepting-proxy-related failures, > and it will certainly improve logging. > > I set DebianMirrorProxy too so that queries to security.d.o go through > the proxy. Ideally we would have a apt cache that could be used as an > http proxy rather than as an origin server; when that happens we can > set DebianMirrorProxy to point to it and do away with DebianMirrorHost > (as we do in Massachusetts). > > Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
Acked-by: Ian Campbell <ian.campb...@citrix.com> Do you want to go pretest in Cambridge then merge back to colo or do you want to push it to the colo and let it flow through in time? > --- > production-config-cambridge | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/production-config-cambridge b/production-config-cambridge > index f801303..012a056 100644 > --- a/production-config-cambridge > +++ b/production-config-cambridge > @@ -82,6 +82,9 @@ XenUseUser osstest > #DebianMirrorHost debian.uk.xensource.com > DebianMirrorHost 10.80.16.196 > > +HttpProxy http://osstest.xs.citrite.net:3128/ > +DebianMirrorProxy http://osstest.xs.citrite.net:3128/ > + > HostProp_NtpServer ntp.uk.xensource.com > HostProp_DhcpWatchMethod leases dhcp3 dns1.uk.xensource.com:5556 > _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
