[New: openFATE 320342] Add btrfs subvolume options to autoyast
Feature added by: Matthias Eckermann (mge1512) Feature #320342, revision 1 Title: Add btrfs subvolume options to autoyast Requested by: Matthias Eckermann (mge1512) Partner organization: openSUSE.org Description: Currently you can't specify btrfs subvolume options is a autoYaST control file. E.g. the standard install of Leap 42.1 creates four subvolumes with option "no copy on write": @/var/lib/libvirt/images @/var/lib/mariadb @/var/lib/mysql @/var/lib/pgsql There ought to be a way to achieve this with autoYaST. Currently subvolumes are specified as: <subvolumes config:type="list"> <listentry>boot/grub2/i386-pc</listentry> <listentry>boot/grub2/x86_64-efi</listentry> <listentry>home</listentry> </subvolumes> a possibly syntax could be e.g.: <subvolumes config:type="list"> <subvolume> <subvolume-path>var/lib/pgsql</subvolume-path> <subvolume-options>nodatacow,noacl</subvolume-options> </subvolume> </subvolumes> or make the subvolume-options a list.. Also the installer should respect these options and autoyast should use them when creating a reference profile. Relations: - Add btrfs subvolume options to autoyast (feature/copiedfrom: 319895) -- openSUSE Feature: https://features.opensuse.org/320342
Feature changed by: Hannes Kühnemund (hkuehnemund) Feature #320342, revision 3 Title: Add btrfs subvolume options to autoyast Requested by: Matthias Eckermann (mge1512) Partner organization: openSUSE.org Description: Currently you can't specify btrfs subvolume options is a autoYaST control file. E.g. the standard install of Leap 42.1 creates four subvolumes with option "no copy on write": @/var/lib/libvirt/images @/var/lib/mariadb @/var/lib/mysql @/var/lib/pgsql There ought to be a way to achieve this with autoYaST. Currently subvolumes are specified as: <subvolumes config:type="list"> <listentry>boot/grub2/i386-pc</listentry> <listentry>boot/grub2/x86_64-efi</listentry> <listentry>home</listentry> </subvolumes> a possibly syntax could be e.g.: <subvolumes config:type="list"> <subvolume> <subvolume-path>var/lib/pgsql</subvolume-path> <subvolume-options>nodatacow,noacl</subvolume-options> </subvolume> </subvolumes> or make the subvolume-options a list.. Also the installer should respect these options and autoyast should use them when creating a reference profile. Relations: - Add btrfs subvolume options to autoyast (feature/copiedfrom: 319895) + - YaST- AutoYaST Alignment (feature/id: 320287) + Discussion: + #2: Hannes Kühnemund (hkuehnemund) (2016-01-18 08:24:35) + Jri, another AutoYaST one which we either implement solely - or + together with 320287 (my preference). Let's discuss later today. -- openSUSE Feature: https://features.opensuse.org/320342
Feature changed by: Jiri Srain (jsrain) Feature #320342, revision 4 Title: Add btrfs subvolume options to autoyast Requested by: Matthias Eckermann (mge1512) Partner organization: openSUSE.org Description: Currently you can't specify btrfs subvolume options is a autoYaST control file. E.g. the standard install of Leap 42.1 creates four subvolumes with option "no copy on write": @/var/lib/libvirt/images @/var/lib/mariadb @/var/lib/mysql @/var/lib/pgsql There ought to be a way to achieve this with autoYaST. Currently subvolumes are specified as: <subvolumes config:type="list"> <listentry>boot/grub2/i386-pc</listentry> <listentry>boot/grub2/x86_64-efi</listentry> <listentry>home</listentry> </subvolumes> a possibly syntax could be e.g.: <subvolumes config:type="list"> <subvolume> <subvolume-path>var/lib/pgsql</subvolume-path> <subvolume-options>nodatacow,noacl</subvolume-options> </subvolume> </subvolumes> or make the subvolume-options a list.. Also the installer should respect these options and autoyast should use them when creating a reference profile. Relations: - Add btrfs subvolume options to autoyast (feature/copiedfrom: 319895) - YaST- AutoYaST Alignment (feature/id: 320287) + Use Case: + Allow to adjust subvolumes attributes properly for the specific + workload - e.g. when having a 3rd party database at a custom path, + there is no way to create a subvolume for the database on a specific + path with NoCoW option. Discussion: #2: Hannes Kühnemund (hkuehnemund) (2016-01-18 08:24:35) Jri, another AutoYaST one which we either implement solely - or together with 320287 (my preference). Let's discuss later today. + #3: Jiri Srain (jsrain) (2016-01-25 14:21:41) (reply to #2) + This is to be handled solely, independently on the AutoYaST unification + with YaST. -- openSUSE Feature: https://features.opensuse.org/320342
Feature changed by: Lukas Ocilka (locilka) Feature #320342, revision 7 Title: Add btrfs subvolume options to autoyast Requested by: Matthias Eckermann (mge1512) Partner organization: openSUSE.org Description: Currently you can't specify btrfs subvolume options is a autoYaST control file. E.g. the standard install of Leap 42.1 creates four subvolumes with option "no copy on write": @/var/lib/libvirt/images @/var/lib/mariadb @/var/lib/mysql @/var/lib/pgsql There ought to be a way to achieve this with autoYaST. Currently subvolumes are specified as: <subvolumes config:type="list"> <listentry>boot/grub2/i386-pc</listentry> <listentry>boot/grub2/x86_64-efi</listentry> <listentry>home</listentry> </subvolumes> a possibly syntax could be e.g.: <subvolumes config:type="list"> <subvolume> <subvolume-path>var/lib/pgsql</subvolume-path> <subvolume-options>nodatacow,noacl</subvolume-options> </subvolume> </subvolumes> or make the subvolume-options a list.. Also the installer should respect these options and autoyast should use them when creating a reference profile. Relations: - Add btrfs subvolume options to autoyast (feature/copiedfrom: 319895) - YaST- AutoYaST Alignment (feature/id: 320287) Use Case: Allow to adjust subvolumes attributes properly for the specific workload - e.g. when having a 3rd party database at a custom path, there is no way to create a subvolume for the database on a specific path with NoCoW option. Discussion: #2: Hannes Kühnemund (hkuehnemund) (2016-01-18 08:24:35) Jri, another AutoYaST one which we either implement solely - or together with 320287 (my preference). Let's discuss later today. #3: Jiri Srain (jsrain) (2016-01-25 14:21:41) (reply to #2) This is to be handled solely, independently on the AutoYaST unification with YaST. + #4: Lukas Ocilka (locilka) (2016-02-05 13:00:46) (reply to #3) + But we should do it in sync with #317775: AutoYaST support for + arbitrary btrfs subvolume structure -- openSUSE Feature: https://features.opensuse.org/320342
Feature changed by: Anja Stock (Neyleah) Feature #320342, revision 10 Title: Add btrfs subvolume options to autoyast + Requested by: Anja Stock (neyleah) Requested by: Matthias Eckermann (mge1512) Partner organization: openSUSE.org Description: Currently you can't specify btrfs subvolume options is a autoYaST control file. E.g. the standard install of Leap 42.1 creates four subvolumes with option "no copy on write": @/var/lib/libvirt/images @/var/lib/mariadb @/var/lib/mysql @/var/lib/pgsql There ought to be a way to achieve this with autoYaST. Currently subvolumes are specified as: <subvolumes config:type="list"> <listentry>boot/grub2/i386-pc</listentry> <listentry>boot/grub2/x86_64-efi</listentry> <listentry>home</listentry> </subvolumes> a possibly syntax could be e.g.: <subvolumes config:type="list"> <subvolume> <subvolume-path>var/lib/pgsql</subvolume-path> <subvolume-options>nodatacow,noacl</subvolume-options> </subvolume> </subvolumes> or make the subvolume-options a list.. Also the installer should respect these options and autoyast should use them when creating a reference profile. Relations: - Add btrfs subvolume options to autoyast (feature/copiedfrom: 319895) - YaST- AutoYaST Alignment (feature/id: 320287) Use Case: Allow to adjust subvolumes attributes properly for the specific workload - e.g. when having a 3rd party database at a custom path, there is no way to create a subvolume for the database on a specific path with NoCoW option. Discussion: #2: Hannes Kühnemund (hkuehnemund) (2016-01-18 08:24:35) Jri, another AutoYaST one which we either implement solely - or together with 320287 (my preference). Let's discuss later today. #3: Jiri Srain (jsrain) (2016-01-25 14:21:41) (reply to #2) This is to be handled solely, independently on the AutoYaST unification with YaST. #4: Lukas Ocilka (locilka) (2016-02-05 13:00:46) (reply to #3) But we should do it in sync with #317775: AutoYaST support for arbitrary btrfs subvolume structure -- openSUSE Feature: https://features.opensuse.org/320342
Feature changed by: Frank Sundermeyer (fsundermeyer) Feature #320342, revision 13 Title: Add btrfs subvolume options to autoyast Requested by: Anja Stock (neyleah) Requested by: Matthias Eckermann (mge1512) Partner organization: openSUSE.org Description: Currently you can't specify btrfs subvolume options is a autoYaST control file. E.g. the standard install of Leap 42.1 creates four subvolumes with option "no copy on write": @/var/lib/libvirt/images @/var/lib/mariadb @/var/lib/mysql @/var/lib/pgsql There ought to be a way to achieve this with autoYaST. Currently subvolumes are specified as: <subvolumes config:type="list"> <listentry>boot/grub2/i386-pc</listentry> <listentry>boot/grub2/x86_64-efi</listentry> <listentry>home</listentry> </subvolumes> a possibly syntax could be e.g.: <subvolumes config:type="list"> <subvolume> <subvolume-path>var/lib/pgsql</subvolume-path> <subvolume-options>nodatacow,noacl</subvolume-options> </subvolume> </subvolumes> or make the subvolume-options a list.. Also the installer should respect these options and autoyast should use them when creating a reference profile. Relations: - Add btrfs subvolume options to autoyast (feature/copiedfrom: 319895) - YaST- AutoYaST Alignment (feature/id: 320287) + Documentation Impact: + AutoYaST Guide Use Case: Allow to adjust subvolumes attributes properly for the specific workload - e.g. when having a 3rd party database at a custom path, there is no way to create a subvolume for the database on a specific path with NoCoW option. Discussion: #2: Hannes Kühnemund (hkuehnemund) (2016-01-18 08:24:35) Jri, another AutoYaST one which we either implement solely - or together with 320287 (my preference). Let's discuss later today. #3: Jiri Srain (jsrain) (2016-01-25 14:21:41) (reply to #2) This is to be handled solely, independently on the AutoYaST unification with YaST. #4: Lukas Ocilka (locilka) (2016-02-05 13:00:46) (reply to #3) But we should do it in sync with #317775: AutoYaST support for arbitrary btrfs subvolume structure -- openSUSE Feature: https://features.opensuse.org/320342
Feature changed by: Hannes Kühnemund (hkuehnemund) Feature #320342, revision 14 Title: Add btrfs subvolume options to autoyast Requested by: Anja Stock (neyleah) Requested by: Matthias Eckermann (mge1512) Partner organization: openSUSE.org Description: Currently you can't specify btrfs subvolume options is a autoYaST control file. E.g. the standard install of Leap 42.1 creates four subvolumes with option "no copy on write": @/var/lib/libvirt/images @/var/lib/mariadb @/var/lib/mysql @/var/lib/pgsql There ought to be a way to achieve this with autoYaST. Currently subvolumes are specified as: <subvolumes config:type="list"> <listentry>boot/grub2/i386-pc</listentry> <listentry>boot/grub2/x86_64-efi</listentry> <listentry>home</listentry> </subvolumes> a possibly syntax could be e.g.: <subvolumes config:type="list"> <subvolume> <subvolume-path>var/lib/pgsql</subvolume-path> <subvolume-options>nodatacow,noacl</subvolume-options> </subvolume> </subvolumes> or make the subvolume-options a list.. Also the installer should respect these options and autoyast should use them when creating a reference profile. Relations: - Add btrfs subvolume options to autoyast (feature/copiedfrom: 319895) - YaST- AutoYaST Alignment (feature/id: 320287) Documentation Impact: AutoYaST Guide Use Case: Allow to adjust subvolumes attributes properly for the specific workload - e.g. when having a 3rd party database at a custom path, there is no way to create a subvolume for the database on a specific path with NoCoW option. Discussion: #2: Hannes Kühnemund (hkuehnemund) (2016-01-18 08:24:35) Jri, another AutoYaST one which we either implement solely - or together with 320287 (my preference). Let's discuss later today. #3: Jiri Srain (jsrain) (2016-01-25 14:21:41) (reply to #2) This is to be handled solely, independently on the AutoYaST unification with YaST. #4: Lukas Ocilka (locilka) (2016-02-05 13:00:46) (reply to #3) But we should do it in sync with #317775: AutoYaST support for arbitrary btrfs subvolume structure + Release Notes: Added btrfs subvolume options in autoyast + Solution: + It is now possible to specify btrfs subvolume options is a autoYaST + control file to overwrite default settings. -- openSUSE Feature: https://features.opensuse.org/320342
Feature changed by: Stefan Knorr (stfnknorr) Feature #320342, revision 15 Title: Add btrfs subvolume options to autoyast Requested by: Anja Stock (neyleah) Requested by: Matthias Eckermann (mge1512) Partner organization: openSUSE.org Description: Currently you can't specify btrfs subvolume options is a autoYaST control file. E.g. the standard install of Leap 42.1 creates four subvolumes with option "no copy on write": @/var/lib/libvirt/images @/var/lib/mariadb @/var/lib/mysql @/var/lib/pgsql There ought to be a way to achieve this with autoYaST. Currently subvolumes are specified as: <subvolumes config:type="list"> <listentry>boot/grub2/i386-pc</listentry> <listentry>boot/grub2/x86_64-efi</listentry> <listentry>home</listentry> </subvolumes> a possibly syntax could be e.g.: <subvolumes config:type="list"> <subvolume> <subvolume-path>var/lib/pgsql</subvolume-path> <subvolume-options>nodatacow,noacl</subvolume-options> </subvolume> </subvolumes> or make the subvolume-options a list.. Also the installer should respect these options and autoyast should use them when creating a reference profile. Relations: - Add btrfs subvolume options to autoyast (feature/copiedfrom: 319895) - YaST- AutoYaST Alignment (feature/id: 320287) Documentation Impact: AutoYaST Guide Use Case: Allow to adjust subvolumes attributes properly for the specific workload - e.g. when having a 3rd party database at a custom path, there is no way to create a subvolume for the database on a specific path with NoCoW option. Discussion: #2: Hannes Kühnemund (hkuehnemund) (2016-01-18 08:24:35) Jri, another AutoYaST one which we either implement solely - or together with 320287 (my preference). Let's discuss later today. #3: Jiri Srain (jsrain) (2016-01-25 14:21:41) (reply to #2) This is to be handled solely, independently on the AutoYaST unification with YaST. #4: Lukas Ocilka (locilka) (2016-02-05 13:00:46) (reply to #3) But we should do it in sync with #317775: AutoYaST support for arbitrary btrfs subvolume structure + #8: Stefan Knorr (stfnknorr) (2017-06-20 10:53:46Z) + Removing this from the release notes by adding [SKIP], because the + content seems very similar to the RN for FATE#317775. + Please scream if my judgment is off here. - Release Notes: Added btrfs subvolume options in autoyast + Release Notes: [SKIP] Added Btrfs Subvolume Options in AutoYaST Solution: It is now possible to specify btrfs subvolume options is a autoYaST control file to overwrite default settings. -- openSUSE Feature: https://features.opensuse.org/320342
participants (1)
-
fate_noreply@suse.de