-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 27 Mar 2014 10:07:39 -0400 Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxx> wrote: > On Fri, Mar 7, 2014 at 1:37 PM, drago01 <drago01@xxxxxxxxx> wrote: > > On Fri, Mar 7, 2014 at 6:37 PM, Dennis Gilmore <dennis@xxxxxxxx> > > wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA1 > >> > >> Hi All, > >> > >> So I asked in the FESCo meeting how you expect upgrades to work > >> without an install tree? the building on the upgrade initramfs and > >> the tree for upgrades is tied into the creation of an install > >> tree. additionally all the future options that have been looked at > >> for livecd creation plan to use anaconda, as such an install tree > >> really is a requirement. > >> > >> I am trying to understand how you expect things to work if you do > >> not produce an install tree. > > > > Can't we just create a minimum install tree (and don't ship an iso) > > that has everything that is required for fedup and point it to the > > "everything + updates" repo? > > Reviving this thread because 1) It seems like an important question, > and 2) I'm not sure everyone on the list understood the implications > Dennis was trying to convey. I know I didn't. > > So with the idea that Workstation is doing a live image delivery for > _installs_, how do we foresee upgrades from e.g. F20 to Workstation > working? > > Dennis, can you elaborate on what you mean by "install tree", why you > think there wouldn't be an install tree if we focus on a live image, > the requirements fedup would need to allow upgrades, etc? > > The suggestion you got in the only other reply seems to be viable to > me, but I don't think anyone here understands from a rel-eng > perspective what is required to make this feasible. > > josh So a live image delivery is just what spins deliver today, i.e. just live media. There is no associated install tree that goes with it. fedup requires a install tree to work, it needs a kernel and a upgrade initramfs to provide the target environment to do the upgrade in, they are produced along with the install tree, the production of them is tightly coupled. so without an install tree we hit a few issues today, you can not upgrade to a new release, you can not network install the workstation product. going forward we will hit an issue where we can not produce live media, the anaconda devs have stated that they no longer want to support livecd-creator the tool we use for livecd creation today, the path going forward is planned to be anaconda based tooling which will require an install tree to make a livecd. I guess the result is that you have to have a install tree if you wish to produce anything. There are use cases that should be considered that require an install tree, developers inside a company who wish to install their development workstations. the easiest way is to pxe boot the installer and do an install. not something that you can do with a live image as an example. Today we require a install DVD as part of the install tree creation, we could make that optional. so you would end up with an install tree that contains a boot.iso, pxe tree and upgrade bits, and a livecd as the part of the deliverables. It does mean you will have additional install paths to be tested. Dennis -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJTPZjjAAoJEH7ltONmPFDRBUkP/Aw3a6cxZWC8lclUJCwYN4gI gY1iQZ1f+QaN0ZoOjQJofmo2u1vUBRdyUC9BvESFANC3BRkuy/QSA/OVPDMio4Yk UWifY/VdObktHwkz3rTB2kUBgFUJyNIh9+bF/DKnBMcIECPcQ2rslzoCanCS8dP0 9WHLnoj0KePreA/KU0wWtuwf61HwcXs0UOpUEHKpsHBkL8GFOh+Qk9+1e24Kovau o9HVrmcwQH6eMNnCbw8hGtxxvtSEfCmoKjjhQ0ls3/0wEl6uI9+CVLa/g3kz4h46 b7yMAklQzb1+5TwQSmo+PnwsMM/psLUp/ww/y2fZnxMKih1CJeg4p9PhnKnR5e6n Z1pPq8NeyVhcVj2yZrA8Rq0Y8xCsjmZgRM4/VNBP944VU+IMcRsBD5ScKTaqUbPE 5FtVi/DJrOAoFT32cx6Je2pkEHoNoJNS+tcC8+dVe6bXxc1L5C+skUwS2Kd+6CSU 3+8QNxR7gT6lNa+zYlupyzqPITCoukXx+mYPohOLbEkmnYkfOJgoNquMxXHueHcB 6tC30EWY9DWj2Ud3Gpqk9zejXtPLJyYJDN3A98/sifgDxUNGVIvdjZ7aeIBkVA06 5H/+VOzYuO7KlkF7xZ6mk4Mqet/6y3gSFXJNiaT+KwMrtehCGQpQAsaWNZ/9Exhx qGzl3VhmlLIza8omZmI7 =BjC/ -----END PGP SIGNATURE----- -- desktop mailing list desktop@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/desktop
