[New: openFATE 315590] Support non-numeric names for md/raid devices.

Feature added by: Neil Brown (neilbrown) Feature #315590, revision 1 Title: Support non-numeric names for md/raid devices. Requested by: Neil Brown (neilbrown) Partner organization: openSUSE.org Description: mdadm-3.3 (due to be released July 2013) will support md device named like "md_home" as well as the traditional "md4". However these names are likely to confuses installers and other system managers so they are disabled by default. To get full benefit from these we need to: 1) Make sure initrd scripts in mdadm package handle these names. 2) teach yast-storage to be able to use non-numeric names and not to be confused by them 3) update any system administration documentation 4) check any system monitoring tools to ensure they won't get confused. Business case (Partner benefit): openSUSE.org: More friendly device names make for an improved user experience. -- openSUSE Feature: https://features.opensuse.org/315590

Feature changed by: Ihno Krumreich (ihno) Feature #315590, revision 5 Title: Support non-numeric names for md/raid devices. Requested by: Neil Brown (neilbrown) Partner organization: openSUSE.org Description: mdadm-3.3 (due to be released July 2013) will support md device named like "md_home" as well as the traditional "md4". However these names are likely to confuses installers and other system managers so they are disabled by default. To get full benefit from these we need to: 1) Make sure initrd scripts in mdadm package handle these names. 2) teach yast-storage to be able to use non-numeric names and not to be confused by them 3) update any system administration documentation 4) check any system monitoring tools to ensure they won't get confused. Business case (Partner benefit): openSUSE.org: More friendly device names make for an improved user experience. + Discussion: + #3: Ihno Krumreich (ihno) (2013-08-28 18:11:26) + No Problem. + Can you please comment on point 2? -- openSUSE Feature: https://features.opensuse.org/315590

Feature changed by: Jiri Srain (jsrain) Feature #315590, revision 6 Title: Support non-numeric names for md/raid devices. Requested by: Neil Brown (neilbrown) Partner organization: openSUSE.org Description: mdadm-3.3 (due to be released July 2013) will support md device named like "md_home" as well as the traditional "md4". However these names are likely to confuses installers and other system managers so they are disabled by default. To get full benefit from these we need to: 1) Make sure initrd scripts in mdadm package handle these names. 2) teach yast-storage to be able to use non-numeric names and not to be confused by them 3) update any system administration documentation 4) check any system monitoring tools to ensure they won't get confused. Business case (Partner benefit): openSUSE.org: More friendly device names make for an improved user experience. Discussion: #3: Ihno Krumreich (ihno) (2013-08-28 18:11:26) No Problem. Can you please comment on point 2? + #4: Jiri Srain (jsrain) (2013-08-29 08:48:21) (reply to #3) + Sure, I can comment on my own comment :-) + YaST currently does not offer changing the MD array name (the first one + is always md0 etc.), so some changes will definitely be needed there. -- openSUSE Feature: https://features.opensuse.org/315590

Feature changed by: Antoine Ginies (aginies) Feature #315590, revision 16 Title: Support non-numeric names for md/raid devices. Requested by: Neil Brown (neilbrown) Partner organization: openSUSE.org Description: mdadm-3.3 (due to be released July 2013) will support md device named like "md_home" as well as the traditional "md4". However these names are likely to confuses installers and other system managers so they are disabled by default. To get full benefit from these we need to: 1) Make sure initrd scripts in mdadm package handle these names. 2) teach yast-storage to be able to use non-numeric names and not to be confused by them 3) update any system administration documentation 4) check any system monitoring tools to ensure they won't get confused. + Documentation Impact: + RN Business case (Partner benefit): openSUSE.org: More friendly device names make for an improved user experience. Discussion: #3: Ihno Krumreich (ihno) (2013-08-28 18:11:26) No Problem. Can you please comment on point 2? #4: Jiri Srain (jsrain) (2013-08-29 08:48:21) (reply to #3) Sure, I can comment on my own comment :-) YaST currently does not offer changing the MD array name (the first one is always md0 etc.), so some changes will definitely be needed there. -- openSUSE Feature: https://features.opensuse.org/315590

Feature changed by: Joachim Wagner (jowagner) Feature #315590, revision 17 Title: Support non-numeric names for md/raid devices. Requested by: Neil Brown (neilbrown) Partner organization: openSUSE.org Description: mdadm-3.3 (due to be released July 2013) will support md device named like "md_home" as well as the traditional "md4". However these names are likely to confuses installers and other system managers so they are disabled by default. To get full benefit from these we need to: 1) Make sure initrd scripts in mdadm package handle these names. 2) teach yast-storage to be able to use non-numeric names and not to be confused by them 3) update any system administration documentation 4) check any system monitoring tools to ensure they won't get confused. Documentation Impact: RN Business case (Partner benefit): openSUSE.org: More friendly device names make for an improved user experience. Discussion: #3: Ihno Krumreich (ihno) (2013-08-28 18:11:26) No Problem. Can you please comment on point 2? #4: Jiri Srain (jsrain) (2013-08-29 08:48:21) (reply to #3) Sure, I can comment on my own comment :-) YaST currently does not offer changing the MD array name (the first one is always md0 etc.), so some changes will definitely be needed there. + #7: Joachim Wagner (jowagner) (2013-11-20 22:00:34) + 13.1 tries to implement this but fails: + https://bugzilla.novell.com/show_bug.cgi?id=849752 (https://bugzilla.novell.com/show_bug.cgi?id=849752) -- openSUSE Feature: https://features.opensuse.org/315590

Feature changed by: Frank Sundermeyer (fsundermeyer) Feature #315590, revision 18 Title: Support non-numeric names for md/raid devices. Requested by: Neil Brown (neilbrown) Partner organization: openSUSE.org Description: mdadm-3.3 (due to be released July 2013) will support md device named like "md_home" as well as the traditional "md4". However these names are likely to confuses installers and other system managers so they are disabled by default. To get full benefit from these we need to: 1) Make sure initrd scripts in mdadm package handle these names. 2) teach yast-storage to be able to use non-numeric names and not to be confused by them 3) update any system administration documentation 4) check any system monitoring tools to ensure they won't get confused. Documentation Impact: RN + Storage Guide ? Business case (Partner benefit): openSUSE.org: More friendly device names make for an improved user experience. Discussion: #3: Ihno Krumreich (ihno) (2013-08-28 18:11:26) No Problem. Can you please comment on point 2? #4: Jiri Srain (jsrain) (2013-08-29 08:48:21) (reply to #3) Sure, I can comment on my own comment :-) YaST currently does not offer changing the MD array name (the first one is always md0 etc.), so some changes will definitely be needed there. #7: Joachim Wagner (jowagner) (2013-11-20 22:00:34) 13.1 tries to implement this but fails: https://bugzilla.novell.com/show_bug.cgi?id=849752 (https://bugzilla.novell.com/show_bug.cgi?id=849752) -- openSUSE Feature: https://features.opensuse.org/315590

Feature changed by: Joachim Wagner (jowagner) Feature #315590, revision 20 Title: Support non-numeric names for md/raid devices. Requested by: Neil Brown (neilbrown) Partner organization: openSUSE.org Description: mdadm-3.3 (due to be released July 2013) will support md device named like "md_home" as well as the traditional "md4". However these names are likely to confuses installers and other system managers so they are disabled by default. To get full benefit from these we need to: 1) Make sure initrd scripts in mdadm package handle these names. 2) teach yast-storage to be able to use non-numeric names and not to be confused by them 3) update any system administration documentation 4) check any system monitoring tools to ensure they won't get confused. Documentation Impact: RN Storage Guide ? Business case (Partner benefit): openSUSE.org: More friendly device names make for an improved user experience. Discussion: #3: Ihno Krumreich (ihno) (2013-08-28 18:11:26) No Problem. Can you please comment on point 2? #4: Jiri Srain (jsrain) (2013-08-29 08:48:21) (reply to #3) Sure, I can comment on my own comment :-) YaST currently does not offer changing the MD array name (the first one is always md0 etc.), so some changes will definitely be needed there. #7: Joachim Wagner (jowagner) (2013-11-20 22:00:34) 13.1 tries to implement this but fails: https://bugzilla.novell.com/show_bug.cgi?id=849752 (https://bugzilla.novell.com/show_bug.cgi?id=849752) + #8: Joachim Wagner (jowagner) (2013-11-29 15:38:18) + Changed to "Unconfirmed" as it's not "Done" as there's an open bug + report, see previous comment. -- openSUSE Feature: https://features.opensuse.org/315590

Feature changed by: Joachim Wagner (jowagner) Feature #315590, revision 21 Title: Support non-numeric names for md/raid devices. Requested by: Neil Brown (neilbrown) Partner organization: openSUSE.org Description: mdadm-3.3 (due to be released July 2013) will support md device named like "md_home" as well as the traditional "md4". However these names are likely to confuses installers and other system managers so they are disabled by default. To get full benefit from these we need to: 1) Make sure initrd scripts in mdadm package handle these names. 2) teach yast-storage to be able to use non-numeric names and not to be confused by them 3) update any system administration documentation 4) check any system monitoring tools to ensure they won't get confused. Documentation Impact: RN Storage Guide ? Business case (Partner benefit): openSUSE.org: More friendly device names make for an improved user experience. Discussion: #3: Ihno Krumreich (ihno) (2013-08-28 18:11:26) No Problem. Can you please comment on point 2? #4: Jiri Srain (jsrain) (2013-08-29 08:48:21) (reply to #3) Sure, I can comment on my own comment :-) YaST currently does not offer changing the MD array name (the first one is always md0 etc.), so some changes will definitely be needed there. #7: Joachim Wagner (jowagner) (2013-11-20 22:00:34) 13.1 tries to implement this but fails: https://bugzilla.novell.com/show_bug.cgi?id=849752 (https://bugzilla.novell.com/show_bug.cgi?id=849752) #8: Joachim Wagner (jowagner) (2013-11-29 15:38:18) Changed to "Unconfirmed" as it's not "Done" as there's an open bug report, see previous comment. + #9: Joachim Wagner (jowagner) (2013-11-29 15:59:35) + Additional (more wide) related feature request: + https://features.opensuse.org/316749 -- openSUSE Feature: https://features.opensuse.org/315590

Feature changed by: Joachim Wagner (jowagner) Feature #315590, revision 23 Title: Support non-numeric names for md/raid devices. Requested by: Neil Brown (neilbrown) Partner organization: openSUSE.org Description: mdadm-3.3 (due to be released July 2013) will support md device named like "md_home" as well as the traditional "md4". However these names are likely to confuses installers and other system managers so they are disabled by default. To get full benefit from these we need to: 1) Make sure initrd scripts in mdadm package handle these names. 2) teach yast-storage to be able to use non-numeric names and not to be confused by them 3) update any system administration documentation 4) check any system monitoring tools to ensure they won't get confused. Documentation Impact: RN Storage Guide ? Business case (Partner benefit): openSUSE.org: More friendly device names make for an improved user experience. Discussion: #3: Ihno Krumreich (ihno) (2013-08-28 18:11:26) No Problem. Can you please comment on point 2? #4: Jiri Srain (jsrain) (2013-08-29 08:48:21) (reply to #3) Sure, I can comment on my own comment :-) YaST currently does not offer changing the MD array name (the first one is always md0 etc.), so some changes will definitely be needed there. #7: Joachim Wagner (jowagner) (2013-11-20 22:00:34) 13.1 tries to implement this but fails: https://bugzilla.novell.com/show_bug.cgi?id=849752 (https://bugzilla.novell.com/show_bug.cgi?id=849752) #8: Joachim Wagner (jowagner) (2013-11-29 15:38:18) Changed to "Unconfirmed" as it's not "Done" as there's an open bug report, see previous comment. #9: Joachim Wagner (jowagner) (2013-11-29 15:59:35) Additional (more wide) related feature request: https://features.opensuse.org/316749 + #10: Joachim Wagner (jowagner) (2013-12-02 11:31:26) + The discussion in bug #849752 points out that this should either be + implemented with the mdadm option "--homehost=any", or some thought + would have to be put in how to make it clear to the user that RAID + assembly depends on the hostname the system uses before the network is + up (before dhcp) and to ask the user for this hostname during + installation. Some users will want this hostname to be the name + provided by dhcp during installation but this could lead to confusion + if dhcp provides a different name later. + An idea may be a to have (1) a checkbox "restrict to hostname" in the + "Add RAID..." page that is off by default and if clicked inserts a link + to (2) a configuration page for the initial hostname (before dhcp). The + network setup page in YaST then needs to implement a check whether a + hostname-based RAID setup is present and should warn about the + consequences of changing the initial hostname or offer to adjust the + RAID meta-data accordingly. -- openSUSE Feature: https://features.opensuse.org/315590

Feature changed by: Joachim Wagner (jowagner) Feature #315590, revision 24 Title: Support non-numeric names for md/raid devices. Requested by: Neil Brown (neilbrown) Partner organization: openSUSE.org Description: mdadm-3.3 (due to be released July 2013) will support md device named like "md_home" as well as the traditional "md4". However these names are likely to confuses installers and other system managers so they are disabled by default. To get full benefit from these we need to: 1) Make sure initrd scripts in mdadm package handle these names. 2) teach yast-storage to be able to use non-numeric names and not to be confused by them 3) update any system administration documentation 4) check any system monitoring tools to ensure they won't get confused. Documentation Impact: RN Storage Guide ? Business case (Partner benefit): openSUSE.org: More friendly device names make for an improved user experience. Discussion: #3: Ihno Krumreich (ihno) (2013-08-28 18:11:26) No Problem. Can you please comment on point 2? #4: Jiri Srain (jsrain) (2013-08-29 08:48:21) (reply to #3) Sure, I can comment on my own comment :-) YaST currently does not offer changing the MD array name (the first one is always md0 etc.), so some changes will definitely be needed there. #7: Joachim Wagner (jowagner) (2013-11-20 22:00:34) 13.1 tries to implement this but fails: https://bugzilla.novell.com/show_bug.cgi?id=849752 (https://bugzilla.novell.com/show_bug.cgi?id=849752) #8: Joachim Wagner (jowagner) (2013-11-29 15:38:18) Changed to "Unconfirmed" as it's not "Done" as there's an open bug report, see previous comment. #9: Joachim Wagner (jowagner) (2013-11-29 15:59:35) Additional (more wide) related feature request: https://features.opensuse.org/316749 #10: Joachim Wagner (jowagner) (2013-12-02 11:31:26) The discussion in bug #849752 points out that this should either be implemented with the mdadm option "--homehost=any", or some thought would have to be put in how to make it clear to the user that RAID assembly depends on the hostname the system uses before the network is up (before dhcp) and to ask the user for this hostname during installation. Some users will want this hostname to be the name provided by dhcp during installation but this could lead to confusion if dhcp provides a different name later. An idea may be a to have (1) a checkbox "restrict to hostname" in the "Add RAID..." page that is off by default and if clicked inserts a link to (2) a configuration page for the initial hostname (before dhcp). The network setup page in YaST then needs to implement a check whether a hostname-based RAID setup is present and should warn about the consequences of changing the initial hostname or offer to adjust the RAID meta-data accordingly. + #11: Joachim Wagner (jowagner) (2013-12-02 11:39:38) (reply to #10) + The initrd may have to be updated as well. -- openSUSE Feature: https://features.opensuse.org/315590

Feature changed by: Neil Brown (neilbrown) Feature #315590, revision 28 Title: Support non-numeric names for md/raid devices. Requested by: Neil Brown (neilbrown) Partner organization: openSUSE.org Description: mdadm-3.3 (due to be released July 2013) will support md device named like "md_home" as well as the traditional "md4". However these names are likely to confuses installers and other system managers so they are disabled by default. To get full benefit from these we need to: 1) Make sure initrd scripts in mdadm package handle these names. 2) teach yast-storage to be able to use non-numeric names and not to be confused by them 3) update any system administration documentation 4) check any system monitoring tools to ensure they won't get confused. Documentation Impact: RN Storage Guide ? Business case (Partner benefit): openSUSE.org: More friendly device names make for an improved user experience. Discussion: #3: Ihno Krumreich (ihno) (2013-08-28 18:11:26) No Problem. Can you please comment on point 2? #4: Jiri Srain (jsrain) (2013-08-29 08:48:21) (reply to #3) Sure, I can comment on my own comment :-) YaST currently does not offer changing the MD array name (the first one is always md0 etc.), so some changes will definitely be needed there. #7: Joachim Wagner (jowagner) (2013-11-20 22:00:34) 13.1 tries to implement this but fails: https://bugzilla.novell.com/show_bug.cgi?id=849752 (https://bugzilla.novell.com/show_bug.cgi?id=849752) #8: Joachim Wagner (jowagner) (2013-11-29 15:38:18) Changed to "Unconfirmed" as it's not "Done" as there's an open bug report, see previous comment. #9: Joachim Wagner (jowagner) (2013-11-29 15:59:35) Additional (more wide) related feature request: https://features.opensuse.org/316749 #10: Joachim Wagner (jowagner) (2013-12-02 11:31:26) The discussion in bug #849752 points out that this should either be implemented with the mdadm option "--homehost=any", or some thought would have to be put in how to make it clear to the user that RAID assembly depends on the hostname the system uses before the network is up (before dhcp) and to ask the user for this hostname during installation. Some users will want this hostname to be the name provided by dhcp during installation but this could lead to confusion if dhcp provides a different name later. An idea may be a to have (1) a checkbox "restrict to hostname" in the "Add RAID..." page that is off by default and if clicked inserts a link to (2) a configuration page for the initial hostname (before dhcp). The network setup page in YaST then needs to implement a check whether a hostname-based RAID setup is present and should warn about the consequences of changing the initial hostname or offer to adjust the RAID meta-data accordingly. #11: Joachim Wagner (jowagner) (2013-12-02 11:39:38) (reply to #10) The initrd may have to be updated as well. + Release Notes: Meaningful names for "md" RAID devices. + Challenge: + Names for "md" RAID devices, particularly as they appear in + /proc/mdstat, traditionally have numeric names like "md4". Working with + these names can be clumsy. + Solution: + In SLE-12 the option is available to use textual names. Adding the line + "CREATE names=yes" to /etc/mdadm.conf will cause names like "md_home" + to be used in place of e.g. "md127" if a name was given when creating + the array. This will likely be enabled by default in future releases of + SLE. -- openSUSE Feature: https://features.opensuse.org/315590

Feature changed by: Antoine Ginies (aginies) Feature #315590, revision 29 Title: Support non-numeric names for md/raid devices. Requested by: Neil Brown (neilbrown) Partner organization: openSUSE.org Description: mdadm-3.3 (due to be released July 2013) will support md device named like "md_home" as well as the traditional "md4". However these names are likely to confuses installers and other system managers so they are disabled by default. To get full benefit from these we need to: 1) Make sure initrd scripts in mdadm package handle these names. 2) teach yast-storage to be able to use non-numeric names and not to be confused by them 3) update any system administration documentation 4) check any system monitoring tools to ensure they won't get confused. Documentation Impact: - RN Storage Guide ? Business case (Partner benefit): openSUSE.org: More friendly device names make for an improved user experience. Discussion: #3: Ihno Krumreich (ihno) (2013-08-28 18:11:26) No Problem. Can you please comment on point 2? #4: Jiri Srain (jsrain) (2013-08-29 08:48:21) (reply to #3) Sure, I can comment on my own comment :-) YaST currently does not offer changing the MD array name (the first one is always md0 etc.), so some changes will definitely be needed there. #7: Joachim Wagner (jowagner) (2013-11-20 22:00:34) 13.1 tries to implement this but fails: https://bugzilla.novell.com/show_bug.cgi?id=849752 (https://bugzilla.novell.com/show_bug.cgi?id=849752) #8: Joachim Wagner (jowagner) (2013-11-29 15:38:18) Changed to "Unconfirmed" as it's not "Done" as there's an open bug report, see previous comment. #9: Joachim Wagner (jowagner) (2013-11-29 15:59:35) Additional (more wide) related feature request: https://features.opensuse.org/316749 #10: Joachim Wagner (jowagner) (2013-12-02 11:31:26) The discussion in bug #849752 points out that this should either be implemented with the mdadm option "--homehost=any", or some thought would have to be put in how to make it clear to the user that RAID assembly depends on the hostname the system uses before the network is up (before dhcp) and to ask the user for this hostname during installation. Some users will want this hostname to be the name provided by dhcp during installation but this could lead to confusion if dhcp provides a different name later. An idea may be a to have (1) a checkbox "restrict to hostname" in the "Add RAID..." page that is off by default and if clicked inserts a link to (2) a configuration page for the initial hostname (before dhcp). The network setup page in YaST then needs to implement a check whether a hostname-based RAID setup is present and should warn about the consequences of changing the initial hostname or offer to adjust the RAID meta-data accordingly. #11: Joachim Wagner (jowagner) (2013-12-02 11:39:38) (reply to #10) The initrd may have to be updated as well. Release Notes: Meaningful names for "md" RAID devices. Challenge: Names for "md" RAID devices, particularly as they appear in /proc/mdstat, traditionally have numeric names like "md4". Working with these names can be clumsy. Solution: In SLE-12 the option is available to use textual names. Adding the line "CREATE names=yes" to /etc/mdadm.conf will cause names like "md_home" to be used in place of e.g. "md127" if a name was given when creating the array. This will likely be enabled by default in future releases of SLE. -- openSUSE Feature: https://features.opensuse.org/315590

Feature changed by: Antoine Ginies (aginies) Feature #315590, revision 31 Title: Support non-numeric names for md/raid devices. Requested by: Neil Brown (neilbrown) Partner organization: openSUSE.org Description: mdadm-3.3 (due to be released July 2013) will support md device named like "md_home" as well as the traditional "md4". However these names are likely to confuses installers and other system managers so they are disabled by default. To get full benefit from these we need to: 1) Make sure initrd scripts in mdadm package handle these names. 2) teach yast-storage to be able to use non-numeric names and not to be confused by them 3) update any system administration documentation 4) check any system monitoring tools to ensure they won't get confused. Documentation Impact: Storage Guide ? Business case (Partner benefit): openSUSE.org: More friendly device names make for an improved user experience. Discussion: #3: Ihno Krumreich (ihno) (2013-08-28 18:11:26) No Problem. Can you please comment on point 2? #4: Jiri Srain (jsrain) (2013-08-29 08:48:21) (reply to #3) Sure, I can comment on my own comment :-) YaST currently does not offer changing the MD array name (the first one is always md0 etc.), so some changes will definitely be needed there. #7: Joachim Wagner (jowagner) (2013-11-20 22:00:34) 13.1 tries to implement this but fails: https://bugzilla.novell.com/show_bug.cgi?id=849752 (https://bugzilla.novell.com/show_bug.cgi?id=849752) #8: Joachim Wagner (jowagner) (2013-11-29 15:38:18) Changed to "Unconfirmed" as it's not "Done" as there's an open bug report, see previous comment. #9: Joachim Wagner (jowagner) (2013-11-29 15:59:35) Additional (more wide) related feature request: https://features.opensuse.org/316749 #10: Joachim Wagner (jowagner) (2013-12-02 11:31:26) The discussion in bug #849752 points out that this should either be implemented with the mdadm option "--homehost=any", or some thought would have to be put in how to make it clear to the user that RAID assembly depends on the hostname the system uses before the network is up (before dhcp) and to ask the user for this hostname during installation. Some users will want this hostname to be the name provided by dhcp during installation but this could lead to confusion if dhcp provides a different name later. An idea may be a to have (1) a checkbox "restrict to hostname" in the "Add RAID..." page that is off by default and if clicked inserts a link to (2) a configuration page for the initial hostname (before dhcp). The network setup page in YaST then needs to implement a check whether a hostname-based RAID setup is present and should warn about the consequences of changing the initial hostname or offer to adjust the RAID meta-data accordingly. #11: Joachim Wagner (jowagner) (2013-12-02 11:39:38) (reply to #10) The initrd may have to be updated as well. Release Notes: Meaningful names for "md" RAID devices. Challenge: Names for "md" RAID devices, particularly as they appear in /proc/mdstat, traditionally have numeric names like "md4". Working with these names can be clumsy. Solution: In SLE-12 the option is available to use textual names. Adding the line - "CREATE names=yes" to /etc/mdadm.conf will cause names like "md_home" - to be used in place of e.g. "md127" if a name was given when creating - the array. This will likely be enabled by default in future releases of + CREATE names=yes to /etc/mdadm.conf will cause names like md_home to be + used in place of e.g. md127 if a name was given when creating the + array. This will likely be enabled by default in future releases of SLE. -- openSUSE Feature: https://features.opensuse.org/315590

Feature changed by: Frank Sundermeyer (fsundermeyer) Feature #315590, revision 32 Title: Support non-numeric names for md/raid devices. Requested by: Neil Brown (neilbrown) Partner organization: openSUSE.org Description: mdadm-3.3 (due to be released July 2013) will support md device named like "md_home" as well as the traditional "md4". However these names are likely to confuses installers and other system managers so they are disabled by default. To get full benefit from these we need to: 1) Make sure initrd scripts in mdadm package handle these names. 2) teach yast-storage to be able to use non-numeric names and not to be confused by them 3) update any system administration documentation 4) check any system monitoring tools to ensure they won't get confused. Documentation Impact: - Storage Guide ? + Storage Guide, Post GA Delivery Business case (Partner benefit): openSUSE.org: More friendly device names make for an improved user experience. Discussion: #3: Ihno Krumreich (ihno) (2013-08-28 18:11:26) No Problem. Can you please comment on point 2? #4: Jiri Srain (jsrain) (2013-08-29 08:48:21) (reply to #3) Sure, I can comment on my own comment :-) YaST currently does not offer changing the MD array name (the first one is always md0 etc.), so some changes will definitely be needed there. #7: Joachim Wagner (jowagner) (2013-11-20 22:00:34) 13.1 tries to implement this but fails: https://bugzilla.novell.com/show_bug.cgi?id=849752 (https://bugzilla.novell.com/show_bug.cgi?id=849752) #8: Joachim Wagner (jowagner) (2013-11-29 15:38:18) Changed to "Unconfirmed" as it's not "Done" as there's an open bug report, see previous comment. #9: Joachim Wagner (jowagner) (2013-11-29 15:59:35) Additional (more wide) related feature request: https://features.opensuse.org/316749 #10: Joachim Wagner (jowagner) (2013-12-02 11:31:26) The discussion in bug #849752 points out that this should either be implemented with the mdadm option "--homehost=any", or some thought would have to be put in how to make it clear to the user that RAID assembly depends on the hostname the system uses before the network is up (before dhcp) and to ask the user for this hostname during installation. Some users will want this hostname to be the name provided by dhcp during installation but this could lead to confusion if dhcp provides a different name later. An idea may be a to have (1) a checkbox "restrict to hostname" in the "Add RAID..." page that is off by default and if clicked inserts a link to (2) a configuration page for the initial hostname (before dhcp). The network setup page in YaST then needs to implement a check whether a hostname-based RAID setup is present and should warn about the consequences of changing the initial hostname or offer to adjust the RAID meta-data accordingly. #11: Joachim Wagner (jowagner) (2013-12-02 11:39:38) (reply to #10) The initrd may have to be updated as well. Release Notes: Meaningful names for "md" RAID devices. Challenge: Names for "md" RAID devices, particularly as they appear in /proc/mdstat, traditionally have numeric names like "md4". Working with these names can be clumsy. Solution: In SLE-12 the option is available to use textual names. Adding the line CREATE names=yes to /etc/mdadm.conf will cause names like md_home to be used in place of e.g. md127 if a name was given when creating the array. This will likely be enabled by default in future releases of SLE. -- openSUSE Feature: https://features.opensuse.org/315590
participants (1)
-
fate_noreply@suse.de