Re: [OSSTEST v6 13/24] distros: support PV guest install from Debian netinst media.

[Ian Campbell <ian.campbell@citrix.com>]

On Thu, 2015-05-14 at 19:01 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [OSSTEST v6 13/24] distros: support PV guest install from Debian netinst media."):
> > On Tue, 2015-05-12 at 16:52 +0100, Ian Jackson wrote:
> > > Wrap damage on my screen.  I appreciate that you want to retain the
> > > tabular nature, but perhaps 
> > > 
> > >     my %arch_props = (
> > > 	amd64 => [ "multi-arch", "amd64-i386", "/install.amd/xen" },
> > > 	i386  => [ "multi-arch", "amd64-i386", "/install.386/xen" },
> > > 	armhf => [ "armhf",      "armhf",      "/install.armhf" },
> > >         )
> > >     my           ( $path_arch,   $file_arch,   $iso_path ) =
> > >         @{ $arch_props{$arch} };
> ...
> > More Perl-fu than I could muster by myself, but looks good to me ;-)
> 
> You didn't spot the [...} then ? :-)

I did when I copied it, before I ran it even.

Actually, this all goes away (or rather becomes case..esac in the
make-flight bash script) with the proposal below.

> > > > +    my $baseurl = $cd eq "current" ?
> > > > +      "http://cdimage.debian.org/debian-cd/current/$props->{PathArch}/jigdo-cd" :
> > > > +      "http://cdimage.debian.org/cdimage/weekly-builds/$props->{PathArch}/jigdo-cd";
> > > 
> > > This should surely come from a runvar (or perhaps a config option)
> > > rather than being hardcoded.
> > 
> > $cd above came from $r{"$gho->{Guest}_cd"} and takes the values either
> > "current" or "weekly".
> > 
> > I could push the logic which mas those to an actual URL into
> > make-distros-flight if you would prefer? Or perhaps push the two
> > prefixes (up to but not including "$props->.../jigdo-cd") into the cfg
> > file? So it would become "$c{DebianCdURL_
> > $cd}/$props->{PathArch}/jigdo-cd"
> 
> (We had a conversation IRL about some of this, but:)
> 
> Hardcoding something in make-flight is not as bad as hardcoding it in
> the script, IMO, but:
> 
> > The latter sounds a bit preferable I think, hardcoding URLs in
> > make-flight seems as wrong as hardcoding them here.
> 
> Having it in the config is best.  You might want to consider whether
> the config ought to be plumbed through a runvar by make-flight, so
> that it is possible to (eg) use cs-adjust-flight or whatever to do
> tests of different things.

After our RL conversation I've moved the URLs to make-flight and
actually it looks ok, I've got a few kinks to work out but I think it
should work ok.

Ian.