12:39 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 29 May 2014 13:13:19 -0700
Adam Williamson <awilliam(a)redhat.com> wrote:
So, I wish we'd noticed this sooner, but hacking at the release
criteria today I happened to notice a bit of a problem in the Fedora
Server product planning.
The Server PRD states
(https://fedoraproject.org/wiki/Server/Product_Requirements_Document#Deliv...
):
"Fedora Server will produce two main installation resources, a
netinstall image and an offline install iso image that allows one to
install and configure featured roles offline. "
the Server tech spec states
(https://fedoraproject.org/wiki/Server/Technical_Specification#Supported_A...
):
"Fedora Server will run on and provide install media for i686, x86_64,
and armv7hl servers.
There will be two official install media for the Fedora Server
A network installation media (either a traditional netinst.iso or
a boot.fedoraproject.org style)
A local installation media providing the default package set as
well as any featured roles that are meaningfully installed without a
network connection.
The local installation media will be allowed a maximum size to
fit on a 4.0GB USB device.
The local installation media can be pointed at network
resources to make available a larger package set."
So...we're planning to release Server with ARM as a primary supported
arch, but so far we'd only planned to do two traditional install media
(a netinst image and a DVD-type 'trad installer plus packages' image).
Fedora ARM releases so far have emphasized disk image-type release
media much more strongly than installer release media, and I believe
the ARM installer media only work at all on one particular ARM
platform.
I need to work on some patches for anaconda, but the plan is that with
the changes I've been working on for u-boot that anaconda will be able
to just work on most arm systems. simply that is only a pxe tree
install.
It shouldnt take too much work to be able to make a install image as
well as a boot image to be able to launch the installer. it would
require some work on tooling to setup the image to boot on systems that
do not ship with an onboard u-boot. but we really need that work done
for the existing installed system images.
So, the reward for work being more work ;), I've been nominated
by
Server WG to liaise with ARM team on this one. What should we do here?
Is Server going to have to grow a set of ARM disk image media, or is
there any possibility of it being plausible to release Fedora 21 with
just installer-type images for ARM?
It shoudl be possible to have only installer images for arm for the
Server product
Looking at it in a bit wider scope, what kind of media has the ARM
team been expecting would be part of the Fedora 21 release? If, say,
we did make a set of images just like images done for Fedora releases
so far - the appropriate set of disk images plus installer media for
whatever ARM platforms are 'supported' - only had those be 'Fedora
Server' media, would it be OK to release those as the only Fedora 21
ARM images, or at least the only official / promoted / supported /
whatever set of images? Or would ARM team also be expecting to have a
'generic' set of ARM images produced?
I realize that's a lot of questions, sorry! Any thoughts would be
appreciated. Thanks!
We have dropped the vfat images so we only have one type of
preinstalled images now. I am honestly pretty sure we have not thought
greatly about what the actual deliverables for f21 will be and we need
to.
Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJTiMJaAAoJEH7ltONmPFDRmrsQAJ4MK7fQXq9fTIwokB7pgX4D
FdyAnXFF9Tf8EruSrCJGeh3k+O+HpZnoomiM/TP4r2gk5i3WXD6CYt9e7nwoGXmv
EdW+uI04OsOzggJJ0UB6UlomaZ6wqp7JBItdG+42HKAuoqavD9H+WB5G3SHwv/wv
0SCGr8devXicLBQQpK4Sa+7032NE5XFsVmm8stKMi7u82ADE0ptU9lATJHUjSqVs
etD6zSl5LKor7MjjaV+DMVvpMMsyyiMB6+CCIS29hDD7azpx2fe4XtTwyUDw07x5
MGepuGIyZL0Ipjk+86O+1B1MDiytMH2w1FrYYfTAgmVReoXR21aDaEL9vV+a9z5y
3PWL33CQrFmv4fm1hhNMDyj8rCHrtNQFODDKERzBukWngoT+B5BqlFr3xMaX4a26
szpRD7T/aknVd+I902CfSHMEqlvFa2CbVs1wH8hSOuA0se8ZLJ2B+36NSITKNPGb
9CdXaLgi5IWgCo52FAIlRTNDNrCFvlJGeAYRkNkObD66yvr33gVcLf1/4BNakSsz
lgg6ZnplUfv+8B67MvNAWKdr2lNtW2B4dq2cSpuRl+PA4QqPBZnsxmeS9fRGcQ45
0mQFJHidAL+ff/i6Q4xvt2avSu4AMRW0yPrkWkI8PDHNcJlrMLHfvV+oSJnQIBGg
TLSKGd0Bn5wp7B8sPY7r
=+bom
-----END PGP SIGNATURE-----