Freeze break request: add branched f17 to boot.fedoraproject.org

[Kevin Fenzi]

Greetings. 

I need to sync up this commit: 
http://git.fedorahosted.org/git/?p=fedora-infrastructure.git;a=commit;h=0...

to secondary01 for boot.fedoraproject.org.

It removes some old serverbeach1 links (making them
dl.fedoraproject.org), and adds a 'f17 branched' prerelease install
option to boot.fedoraproject.org. 

Impact should be very low.

kevin

[Matt Domsch]

+1

--
Matt Domsch
Technology Strategist
Dell | Office of the CTO

-----Original Message-----
From: infrastructure-bounces(a)lists.fedoraproject.org
[mailto:[e-mail]] On Behalf Of Kevin Fenzi
Sent: Friday, February 17, 2012 10:20 AM
To: Fedora Infrastructure
Subject: Freeze break request: add branched f17 to boot.fedoraproject.org

Greetings. 

I need to sync up this commit: 
http://git.fedorahosted.org/git/?p=fedora-infrastructure.git;a=commit;h=0...

to secondary01 for boot.fedoraproject.org.

It removes some old serverbeach1 links (making them dl.fedoraproject.org), and adds a
'f17 branched' prerelease install option to boot.fedoraproject.org. 

Impact should be very low.

kevin

[Toshio Kuratomi]

+1

-Toshio

On Fri, Feb 17, 2012 at 10:27:08AM -0600, Matt_Domsch(a)Dell.com wrote:
>  +1
>  
>  --
>  Matt Domsch
>  Technology Strategist
>  Dell | Office of the CTO
>  
>  -----Original Message-----
>  From: infrastructure-bounces(a)lists.fedoraproject.org
> [mailto:[e-mail]] On Behalf Of Kevin Fenzi
>  Sent: Friday, February 17, 2012 10:20 AM
>  To: Fedora Infrastructure
>  Subject: Freeze break request: add branched f17 to boot.fedoraproject.org
>  
>  Greetings. 
>  
>  I need to sync up this commit: 
>
> http://git.fedorahosted.org/git/?p=fedora-infrastructure.git;a=commit;h=0...
>  
>  to secondary01 for boot.fedoraproject.org.
>  
>  It removes some old serverbeach1 links (making them dl.fedoraproject.org), and adds a
> 'f17 branched' prerelease install option to boot.fedoraproject.org. 
>  
>  Impact should be very low.
>  
>  kevin
>  _______________________________________________
>  infrastructure mailing list
>  infrastructure(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/infrastructure

[Marko Myllynen]

Hi,

>  I need to sync up this commit:
>
> http://git.fedorahosted.org/git/?p=fedora-infrastructure.git;a=commit;h=0...
>
>  to secondary01 for boot.fedoraproject.org. 
I think I never received a reply to my question over a year ago whether 
BFO is still using the mostly abandoned gPXE or have you already 
switched to iPXE?

http://lists.fedoraproject.org/pipermail/infrastructure/2011-January/0098...

Cheers,

-- 
Marko Myllynen

[Kevin Fenzi]

On Fri, 17 Feb 2012 18:27:55 +0200
Marko Myllynen <myllynen(a)redhat.com&gt; wrote:

>  Hi,
>  
>  > I need to sync up this commit:
>  >
> http://git.fedorahosted.org/git/?p=fedora-infrastructure.git;a=commit;h=0...
>  >
>  > to secondary01 for boot.fedoraproject.org.
>  
>  I think I never received a reply to my question over a year ago
>  whether BFO is still using the mostly abandoned gPXE or have you
>  already switched to iPXE? 
I wasn't involved with boot.fedoraproject.org last year. ;) 

> http://lists.fedoraproject.org/pipermail/infrastructure/2011-January/0098... 
No, we are using gPXE. 

I'm happy with moving to iPXE if it's better/more supported upstream. 
Do you want to work on that? Our setup is all in the
fedora-infrastructure git repo: 

http://git.fedorahosted.org/git/?p=fedora-infrastructure.git;a=tree;f=bfo...

If you want to work on it that would be great. 
Otherwise I will add it to my list, but it's not likely to be high
priority. 

kevin

[Marko Myllynen]

Hi,

>  I'm happy with moving to iPXE if it's better/more supported
> upstream. 
iPXE should be just a drop-in replacement for gPXE so what is mostly 
needed is to build the iPXE images. You can decide yourself which one 
seems to be more actively developed and maintained:

http://git.etherboot.org/gpxe.git/shortlog
http://git.ipxe.org/ipxe.git/shortlog

>  Otherwise I will add it to my list, but it's not likely to be
> high
>  priority. 
Basically all what's needed is to have a system with the needed tools to 
build the iPXE images (adjust the embedded image as needed):

yum install git make gcc perl syslinux genisoimage
git clone git://git.ipxe.org/ipxe.git ipxe.git
cd ipxe.git/src
make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.iso
make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.usb
make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.dsk
make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.lkrn

The current README suggests that the web based rom-o-matic has been used 
for generating the gPXE images but for iPXE no such service exists so 
you'd need to compile the images on a suitable system and make them 
available then on b.f.o.

Thanks,

-- 
Marko Myllynen

[Kevin Fenzi]

On Mon, 20 Feb 2012 13:04:48 +0200
Marko Myllynen <myllynen(a)redhat.com&gt; wrote:

>  Hi,
>  
>  > I'm happy with moving to iPXE if it's better/more supported
>  > upstream. 
Hey Marko.

>  iPXE should be just a drop-in replacement for gPXE so what is mostly
>
>  needed is to build the iPXE images. You can decide yourself which one 
>  seems to be more actively developed and maintained:
>  
>  http://git.etherboot.org/gpxe.git/shortlog
>  http://git.ipxe.org/ipxe.git/shortlog
>  
>  > Otherwise I will add it to my list, but it's not likely to be high
>  > priority.
>  
>  Basically all what's needed is to have a system with the needed tools
>  to build the iPXE images (adjust the embedded image as needed):
>  
>  yum install git make gcc perl syslinux genisoimage
>  git clone git://git.ipxe.org/ipxe.git ipxe.git
>  cd ipxe.git/src
>  make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.iso
>  make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.usb
>  make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.dsk
>  make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.lkrn 
I tried this and got: 

make: *** No rule to make target `bin/ipxe.iso'.  Stop.

basically it doesn't seem they understand a EMBEDDED_IMAGE option. 

Thoughts?

kevin

[Marko Myllynen]

Hi Kevin,

> > Basically all what's needed is to have a system with the
> needed tools
> > to build the iPXE images (adjust the embedded image as needed):
> >
> > yum install git make gcc perl syslinux genisoimage
> > git clone git://git.ipxe.org/ipxe.git ipxe.git
> > cd ipxe.git/src
> > make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.iso
> > make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.usb
> > make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.dsk
> > make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.lkrn
>
>  I tried this and got:
>
>  make: *** No rule to make target `bin/ipxe.iso'.  Stop.
>
>  basically it doesn't seem they understand a EMBEDDED_IMAGE option.
>
>  Thoughts? 
well, forgive me asking, but are you sure you were in the right 
directory when you tried to build?-)

FOO=bar defines a variable FOO for the build and the error you got was 
about the missing definition of the actual target, bin/ipxe.iso.

Cheers,

-- 
Marko Myllynen

[Kevin Fenzi]

On Mon, 05 Mar 2012 10:20:03 +0200
Marko Myllynen <myllynen(a)redhat.com&gt; wrote:

>  Hi Kevin,
>  
>  >> Basically all what's needed is to have a system with the needed
>  >> tools to build the iPXE images (adjust the embedded image as
>  >> needed):
>  >>
>  >> yum install git make gcc perl syslinux genisoimage
>  >> git clone git://git.ipxe.org/ipxe.git ipxe.git
>  >> cd ipxe.git/src
>  >> make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.iso
>  >> make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.usb
>  >> make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.dsk
>  >> make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.lkrn
>  >
>  > I tried this and got:
>  >
>  > make: *** No rule to make target `bin/ipxe.iso'.  Stop.
>  >
>  > basically it doesn't seem they understand a EMBEDDED_IMAGE option.
>  >
>  > Thoughts?
>  
>  well, forgive me asking, but are you sure you were in the right 
>  directory when you tried to build?-) 
I hope so. I was in my ipxe.git/src/ dir. 

>  FOO=bar defines a variable FOO for the build and the error you got
>  was about the missing definition of the actual target, bin/ipxe.iso. 
Right. What I get is: 

...bunch of compile... 
  [BUILD] bin/rc80211.o
  [BUILD] bin/sec80211.o
  [BUILD] bin/wep.o
  [BUILD] bin/wpa_psk.o
  [BUILD] bin/wpa_tkip.o
  [BUILD] bin/script.o
  [BUILD] bin/elf.o
  [BUILD] bin/efi_image.o
  [BUILD] bin/segment.o
make: *** No rule to make target `bfo.gpxe', needed by
`bin/embedded.o'.  Stop.

kevin

[Marko Myllynen]

Hi,

> >>> yum install git make gcc perl syslinux genisoimage
> >>> git clone git://git.ipxe.org/ipxe.git ipxe.git
> >>> cd ipxe.git/src
> >>> make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.iso
> >>> make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.usb
> >>> make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.dsk
> >>> make EMBEDDED_IMAGE=bfo.gpxe bin/ipxe.lkrn
> >>
> >> I tried this and got:
> >>
> >> make: *** No rule to make target `bin/ipxe.iso'.  Stop.
> >>
> >> basically it doesn't seem they understand a EMBEDDED_IMAGE option.
> >
> > well, forgive me asking, but are you sure you were in the right
> > directory when you tried to build?-)
>
>  I hope so. I was in my ipxe.git/src/ dir.
>
> > FOO=bar defines a variable FOO for the build and the error you got
> > was about the missing definition of the actual target, bin/ipxe.iso.
>
>  Right. What I get is:
>
>  ...bunch of compile... 
Ok, now you're running make in the correct directory, however ...

>     [BUILD] bin/segment.o
>  make: *** No rule to make target `bfo.gpxe', needed by
>  `bin/embedded.o'.  Stop. 
... this means that the embedded script was not found.

As mentioned the script contents and path need to be adjusted for what's 
appropriate for bfo. The reason I didn't say anything explicitly is that 
there seems to be conflicting information in the files README vs 
FEDORA-INFRA in fedora-infrastructure.git.

After a bit of investigation it seems that README corresponds to current 
situation while FEDORA-INFRA does not.

Perhaps we could continue to discussion about these details off-list or 
on IRC as needed?

Thanks,

-- 
Marko Myllynen