Feature changed by: Klaus Kämpf (kwk) Feature #308539, revision 3 Title: Import/Export of YaST installation settings openSUSE-11.3: New Priority Requester: Mandatory Requested by: Klaus Kämpf (kwk) Partner organization: openSUSE.org Description: Configuring the installation settings in YaST (timezone, partitioning, packages) takes some time. When you then hit a bug in the installer (i. e. partitioning failure) forcing you to restart, things get annoying. This request is asking for an import/export option in YaSTs 'installation settings' overview. (Actually, the 'import' is needed much earlier ...) Business case (Partner benefit): openSUSE.org: Usability. Disaster recovery. Discussion: #1: andrea florio (anubisg1) (2009-12-15 17:19:12) i usually do that using autoyast.. can you please explain better the difference? + #2: Klaus Kämpf (kwk) (2009-12-15 18:19:40) (reply to #1) + Getting to the 'installation settings' dialog in YaSTs installation + workflow can imply a lot of work. It did for me since I did a special + partitioning (encrypted "/home") and package selection. Having an + 'export' functionality at this point during the install workflow + appears as straightforward/natural to me. + Using AutoYaST is fine, its just not obvious how to do that in the + install workflow. The autoyast profile is saved at the end(!) of the + installation, but thats a) too late (in case partitioning crashes as it + happened to me) and b) non-obvious. -- openSUSE Feature: https://features.opensuse.org/308539

Feature changed by: Lukas Ocilka (locilka) Feature #308539, revision 7 Title: Import/Export of YaST installation settings openSUSE-11.3: Rejected by Duncan Mac-Vicar (dmacvicar) reject date: 2013-03-05 17:36:18 reject reason: not done for 11.3. Keeping for SLE12 Priority Requester: Mandatory Requested by: Klaus Kämpf (kwk) Partner organization: openSUSE.org Description: Configuring the installation settings in YaST (timezone, partitioning, packages) takes some time. When you then hit a bug in the installer (i. e. partitioning failure) forcing you to restart, things get annoying. This request is asking for an import/export option in YaSTs 'installation settings' overview. (Actually, the 'import' is needed much earlier ...) Business case (Partner benefit): openSUSE.org: Usability. Disaster recovery. Discussion: #1: andrea florio (anubisg1) (2009-12-15 17:19:12) i usually do that using autoyast.. can you please explain better the difference? #2: Klaus Kämpf (kwk) (2009-12-15 18:19:40) (reply to #1) Getting to the 'installation settings' dialog in YaSTs installation workflow can imply a lot of work. It did for me since I did a special partitioning (encrypted "/home") and package selection. Having an 'export' functionality at this point during the install workflow appears as straightforward/natural to me. Using AutoYaST is fine, its just not obvious how to do that in the install workflow. The autoyast profile is saved at the end(!) of the installation, but thats a) too late (in case partitioning crashes as it happened to me) and b) non-obvious. + #3: Lukas Ocilka (locilka) (2013-08-07 15:52:48) + What we still plan to have with a new installer is storing an + installation/system manifest just before the actual installation + starts. Once stored (and copied), it would make installation easy to + duplicate without much effort. -- openSUSE Feature: https://features.opensuse.org/308539

Feature changed by: Joachim Werner (joachimwerner) Feature #308539, revision 9 Title: Import/Export of YaST installation settings openSUSE-11.3: Rejected by Duncan Mac-Vicar (dmacvicar) reject date: 2013-03-05 17:36:18 reject reason: not done for 11.3. Keeping for SLE12 Priority Requester: Mandatory Requested by: Klaus Kämpf (kwk) Partner organization: openSUSE.org Description: Configuring the installation settings in YaST (timezone, partitioning, packages) takes some time. When you then hit a bug in the installer (i. e. partitioning failure) forcing you to restart, things get annoying. This request is asking for an import/export option in YaSTs 'installation settings' overview. (Actually, the 'import' is needed much earlier ...) Business case (Partner benefit): openSUSE.org: Usability. Disaster recovery. Discussion: #1: andrea florio (anubisg1) (2009-12-15 17:19:12) i usually do that using autoyast.. can you please explain better the difference? #2: Klaus Kämpf (kwk) (2009-12-15 18:19:40) (reply to #1) Getting to the 'installation settings' dialog in YaSTs installation workflow can imply a lot of work. It did for me since I did a special partitioning (encrypted "/home") and package selection. Having an 'export' functionality at this point during the install workflow appears as straightforward/natural to me. Using AutoYaST is fine, its just not obvious how to do that in the install workflow. The autoyast profile is saved at the end(!) of the installation, but thats a) too late (in case partitioning crashes as it happened to me) and b) non-obvious. #3: Lukas Ocilka (locilka) (2013-08-07 15:52:48) What we still plan to have with a new installer is storing an installation/system manifest just before the actual installation starts. Once stored (and copied), it would make installation easy to duplicate without much effort. #4: Jiri Srain (jsrain) (2013-08-07 18:59:16) (reply to #3) Exactly, in the SLE11 terminology: With the new installer, AutoYaST profile can be stored right before the installation itself starts (and when all data is filled in). Klaus, does this fulfill your requirement? + #5: Joachim Werner (joachimwerner) (2013-08-09 12:04:43) + Klaus' request is a completely new use case for what we have in mind + with the new installer improvements, but I think it's 100% covered if + we make sure the new installer really separates the data gathering + phase strictly from the execution phase. + Thinking about the use case, here are a few additional remarks: + * the first goal should be to minimize breakage in the first place, so + the uses should not hit any bugs in the installer ;-) + * to handle the bug case we may consider automatically storing the + settings permanently where this is possible, so next time the + installation is tried a user can choose to resume with the old data; + otherwise you need to always think of exporting your settings in time, + which would usually mean that you need to enter the data at least + twice: once before the first failure, then again, because you forgot to + export in the first run -- openSUSE Feature: https://features.opensuse.org/308539

Feature changed by: Jiri Srain (jsrain) Feature #308539, revision 11 Title: Import/Export of YaST installation settings openSUSE-11.3: Rejected by Duncan Mac-Vicar (dmacvicar) reject date: 2013-03-05 17:36:18 reject reason: not done for 11.3. Keeping for SLE12 Priority Requester: Mandatory Requested by: Klaus Kämpf (kwk) Partner organization: openSUSE.org Description: Configuring the installation settings in YaST (timezone, partitioning, packages) takes some time. When you then hit a bug in the installer (i. e. partitioning failure) forcing you to restart, things get annoying. This request is asking for an import/export option in YaSTs 'installation settings' overview. (Actually, the 'import' is needed much earlier ...) Business case (Partner benefit): openSUSE.org: Usability. Disaster recovery. Discussion: #1: andrea florio (anubisg1) (2009-12-15 17:19:12) i usually do that using autoyast.. can you please explain better the difference? #2: Klaus Kämpf (kwk) (2009-12-15 18:19:40) (reply to #1) Getting to the 'installation settings' dialog in YaSTs installation workflow can imply a lot of work. It did for me since I did a special partitioning (encrypted "/home") and package selection. Having an 'export' functionality at this point during the install workflow appears as straightforward/natural to me. Using AutoYaST is fine, its just not obvious how to do that in the install workflow. The autoyast profile is saved at the end(!) of the installation, but thats a) too late (in case partitioning crashes as it happened to me) and b) non-obvious. #3: Lukas Ocilka (locilka) (2013-08-07 15:52:48) What we still plan to have with a new installer is storing an installation/system manifest just before the actual installation starts. Once stored (and copied), it would make installation easy to duplicate without much effort. #4: Jiri Srain (jsrain) (2013-08-07 18:59:16) (reply to #3) Exactly, in the SLE11 terminology: With the new installer, AutoYaST profile can be stored right before the installation itself starts (and when all data is filled in). Klaus, does this fulfill your requirement? #6: Klaus Kämpf (kwk) (2013-08-09 12:11:21) (reply to #4) Its not about storing but about importing a 'set of predefined configuration values'. This is also touched by the request for 'templates' for the new installer. #5: Joachim Werner (joachimwerner) (2013-08-09 12:04:43) Klaus' request is a completely new use case for what we have in mind with the new installer improvements, but I think it's 100% covered if we make sure the new installer really separates the data gathering phase strictly from the execution phase. Thinking about the use case, here are a few additional remarks: * the first goal should be to minimize breakage in the first place, so the uses should not hit any bugs in the installer ;-) * to handle the bug case we may consider automatically storing the settings permanently where this is possible, so next time the installation is tried a user can choose to resume with the old data; otherwise you need to always think of exporting your settings in time, which would usually mean that you need to enter the data at least twice: once before the first failure, then again, because you forgot to export in the first run + #7: Jiri Srain (jsrain) (2013-08-09 14:39:53) (reply to #5) + This is what the installer intends to do. + I fully agree with what you wrote, with one exception: Until the disk + is partitioned, there is hardly a location where you can store the + settings _automatically_. + For the rest, it is what the new installer virtual team covered in the + research. -- openSUSE Feature: https://features.opensuse.org/308539

Feature changed by: Lukas Ocilka (locilka) Feature #308539, revision 17 Title: Import/Export of YaST installation settings openSUSE-11.3: Rejected by Duncan Mac-Vicar (dmacvicar) reject date: 2013-03-05 17:36:18 reject reason: not done for 11.3. Keeping for SLE12 Priority Requester: Mandatory Requested by: Klaus Kämpf (kwk) Partner organization: openSUSE.org Description: Configuring the installation settings in YaST (timezone, partitioning, packages) takes some time. When you then hit a bug in the installer (i. e. partitioning failure) forcing you to restart, things get annoying. This request is asking for an import/export option in YaSTs 'installation settings' overview. (Actually, the 'import' is needed much earlier ...) Documentation Impact: RN Business case (Partner benefit): openSUSE.org: Usability. Disaster recovery. Discussion: #1: andrea florio (anubisg1) (2009-12-15 17:19:12) i usually do that using autoyast.. can you please explain better the difference? #2: Klaus Kämpf (kwk) (2009-12-15 18:19:40) (reply to #1) Getting to the 'installation settings' dialog in YaSTs installation workflow can imply a lot of work. It did for me since I did a special partitioning (encrypted "/home") and package selection. Having an 'export' functionality at this point during the install workflow appears as straightforward/natural to me. Using AutoYaST is fine, its just not obvious how to do that in the install workflow. The autoyast profile is saved at the end(!) of the installation, but thats a) too late (in case partitioning crashes as it happened to me) and b) non-obvious. #3: Lukas Ocilka (locilka) (2013-08-07 15:52:48) What we still plan to have with a new installer is storing an installation/system manifest just before the actual installation starts. Once stored (and copied), it would make installation easy to duplicate without much effort. #4: Jiri Srain (jsrain) (2013-08-07 18:59:16) (reply to #3) Exactly, in the SLE11 terminology: With the new installer, AutoYaST profile can be stored right before the installation itself starts (and when all data is filled in). Klaus, does this fulfill your requirement? #6: Klaus Kämpf (kwk) (2013-08-09 12:11:21) (reply to #4) Its not about storing but about importing a 'set of predefined configuration values'. This is also touched by the request for 'templates' for the new installer. #5: Joachim Werner (joachimwerner) (2013-08-09 12:04:43) Klaus' request is a completely new use case for what we have in mind with the new installer improvements, but I think it's 100% covered if we make sure the new installer really separates the data gathering phase strictly from the execution phase. Thinking about the use case, here are a few additional remarks: * the first goal should be to minimize breakage in the first place, so the uses should not hit any bugs in the installer ;-) * to handle the bug case we may consider automatically storing the settings permanently where this is possible, so next time the installation is tried a user can choose to resume with the old data; otherwise you need to always think of exporting your settings in time, which would usually mean that you need to enter the data at least twice: once before the first failure, then again, because you forgot to export in the first run #7: Jiri Srain (jsrain) (2013-08-09 14:39:53) (reply to #5) This is what the installer intends to do. I fully agree with what you wrote, with one exception: Until the disk is partitioned, there is hardly a location where you can store the settings _automatically_. For the rest, it is what the new installer virtual team covered in the research. + #8: Lukas Ocilka (locilka) (2014-01-22 18:26:15) (reply to #7) + Isn't this done already? What is missing? -- openSUSE Feature: https://features.opensuse.org/308539

Feature changed by: Josef Reidinger (jreidinger) Feature #308539, revision 19 Title: Import/Export of YaST installation settings openSUSE-11.3: Rejected by Duncan Mac-Vicar (dmacvicar) reject date: 2013-03-05 17:36:18 reject reason: not done for 11.3. Keeping for SLE12 Priority Requester: Mandatory Requested by: Klaus Kämpf (kwk) Partner organization: openSUSE.org Description: Configuring the installation settings in YaST (timezone, partitioning, packages) takes some time. When you then hit a bug in the installer (i. e. partitioning failure) forcing you to restart, things get annoying. This request is asking for an import/export option in YaSTs 'installation settings' overview. (Actually, the 'import' is needed much earlier ...) Documentation Impact: RN + Test Case: + Do installation and in summary screen click on Export button and store + autoyast profile. Then try to install with autoyast profile, all + changes done in previous installation should be respected. Business case (Partner benefit): openSUSE.org: Usability. Disaster recovery. Discussion: #1: andrea florio (anubisg1) (2009-12-15 17:19:12) i usually do that using autoyast.. can you please explain better the difference? #2: Klaus Kämpf (kwk) (2009-12-15 18:19:40) (reply to #1) Getting to the 'installation settings' dialog in YaSTs installation workflow can imply a lot of work. It did for me since I did a special partitioning (encrypted "/home") and package selection. Having an 'export' functionality at this point during the install workflow appears as straightforward/natural to me. Using AutoYaST is fine, its just not obvious how to do that in the install workflow. The autoyast profile is saved at the end(!) of the installation, but thats a) too late (in case partitioning crashes as it happened to me) and b) non-obvious. #3: Lukas Ocilka (locilka) (2013-08-07 15:52:48) What we still plan to have with a new installer is storing an installation/system manifest just before the actual installation starts. Once stored (and copied), it would make installation easy to duplicate without much effort. #4: Jiri Srain (jsrain) (2013-08-07 18:59:16) (reply to #3) Exactly, in the SLE11 terminology: With the new installer, AutoYaST profile can be stored right before the installation itself starts (and when all data is filled in). Klaus, does this fulfill your requirement? #6: Klaus Kämpf (kwk) (2013-08-09 12:11:21) (reply to #4) Its not about storing but about importing a 'set of predefined configuration values'. This is also touched by the request for 'templates' for the new installer. #5: Joachim Werner (joachimwerner) (2013-08-09 12:04:43) Klaus' request is a completely new use case for what we have in mind with the new installer improvements, but I think it's 100% covered if we make sure the new installer really separates the data gathering phase strictly from the execution phase. Thinking about the use case, here are a few additional remarks: * the first goal should be to minimize breakage in the first place, so the uses should not hit any bugs in the installer ;-) * to handle the bug case we may consider automatically storing the settings permanently where this is possible, so next time the installation is tried a user can choose to resume with the old data; otherwise you need to always think of exporting your settings in time, which would usually mean that you need to enter the data at least twice: once before the first failure, then again, because you forgot to export in the first run #7: Jiri Srain (jsrain) (2013-08-09 14:39:53) (reply to #5) This is what the installer intends to do. I fully agree with what you wrote, with one exception: Until the disk is partitioned, there is hardly a location where you can store the settings _automatically_. For the rest, it is what the new installer virtual team covered in the research. #8: Lukas Ocilka (locilka) (2014-01-22 18:26:15) (reply to #7) Isn't this done already? What is missing? #9: Josef Reidinger (jreidinger) (2014-01-23 08:48:23) (reply to #8) Export is done, just do not work, but we can handle it as bugs. Import is not done as special button, you can use it only as autoyast profile, replay common installation from installation profile is not possible and is really big intrusive change to current installation workflow. + #10: Josef Reidinger (jreidinger) (2014-01-29 13:24:19) + Implemented. There is now Export button in summary screen, that allows + to export autoyast profile. It can be used later as common autoyast + profile. Special Import is postponed till system manifest will be ready + to use. -- openSUSE Feature: https://features.opensuse.org/308539