Dne 17.10.2013 10:40, Johannes Meixner napsal(a): Hi,
https://github.com/yast/yast-installation/wiki/New-Installer%3A-SLE12-Instal...
therein in section "3. Deployment (step 7 above) (§5)" reads: ------------------------------------------------------------------------- o Create filesystem, optionally untar pre-installed images, install RPMs. The images here are tar.xz images with pre-installed RPMs as are currently used in openSUSE.
For SLE the image functionality will be probably not needed... -------------------------------------------------------------------------
Ooops, sorry for confusion, this is *not* about deploying a system image (which will be supported), this is about the images currently used in openSUSE installation where they are used *just for speeding up* the RPM installation. Traditionally the system is installed from RPMs, which is slower than unpacking a tarball with already pre-installed packages. The installer knows which patterns/packages are contained in the pre-installed images and if user selects the known pattern then the image is deployed instead of installing huge amount of RPMs. (Of course, the missing extra packages selected by user are installed in traditional way from RPMs after the images are deployed.)
I disagree that "for SLE the image functionality is not needed".
The SLES/D managers are not much interested in this feature (FATE#310670), the problem is that the package selections chosen by admins are too different and there is a lack of free space on DVD medium (the images take about 0.5GB in openSUSE and the current SLED medium is almost full).
In particular for SLE it is needed that after a system disaster the new installer can re-create the system on new (compatible) replacement hardware as it was before by using a saved config of the system and deploying one or more backup.tar.gz images that contain the files of the system.
To support this the new installer has to do those steps: 1. Boot New Machine 2. Use given config (i.e. the saved system config) 3. Disk Activation (e.g. special stuff to make SAN accessible) 4. Storage/Partitioning 5. Create filesystems and mount them at the right mount points 6. Deploy the files (i.e. untar backup.tar.gz images)
So far we thought only about Studio images (raw disk images), but support for tar.gz is easy so it could be supported as well.
7. Install bootloader 8. Reboot
Ideally "Deploy the files" should support any mixture of installing RPMs and whatever kind of software packages plus untar backup.tar.gz images so that it would be possible to have only user data in backup.tar.gz but use RPMs for the basic system software and whatever kind of software packages for other software like third-party software.
We did not think about this possibility, but it is an interesting idea to mix both approaches...
Is it planned that such system recovery/restore functionality will be supported by the new installer in particular for SLE?
So far not, but the new installer will be modular so it should be possible to replace the deployment part by a custom tool, or we could add this functionality later... -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org