December 2016 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 310338] Always create /root/autoyast.xml for every installation
by fate_noreply＠suse.de 27 Jun '17

27 Jun '17

Feature added by: Darryl Miles (dlmiles) Feature #310338, revision 1 Title: Always create /root/autoyast.xml for every installation openSUSE-11.4: Unconfirmed Priority Requester: Desirable Requested by: Darryl Miles (dlmiles) Description: Distribution such as RHEL (and any of its blood line) always leave a file /root/anaconda.ks which can be used to repeat the installation via their anaconda/kickstart process. The parallel to this with openSUSE is YaST2 and AutoYaST. The feature request is asking that at the end of every installation in the home directory of the root user the necessary file or files are created to allow the user to repeast the installation with the same options. If multiple files are needed then it maybe better provided as a single file using any archiver (tar/cpio/zip). Also making sure this format could be used directly with AutoYaST. There should be a YaST2 option to disable the emitting of configuration but the default should be to enabled it just like with RHEL. The process of making the user use another program to create an autoyast.xml descriptor is no where near as efficient as running through the entire installation process once and knowing you always get a descriptor out at the end of it. Which you can then if you like open up the editor to modify. This has far superior usability IMHO. If there are concerns over encoding hashed/encrypted passwords into the file then the generation of this installation configuration to file(s) in the root users home directory should have a tri-state value. * Off (meaning do no create any files), * On (meaning to create file(s) in the root home directory that would be necessary to perform the installation that just happened again with a new set of defaults and mostly unattended, however any security sensitive information such as passwords would not be included at all, this would be the new default for everyone), * On with Passwords (meaning the same as On but any security senstive information would also be emitted in the best possible way to retain as much security as possible, for example the password hash is in the file no the plain text password). -- openSUSE Feature: https://features.opensuse.org/310338

1 2

[openFATE 307862] zypper parallel dowloading of packages
by fate_noreply＠suse.de 27 Jun '17

27 Jun '17

Feature added by: Aris Karagiannidis (arkara) Feature #307862, revision 1 Title: zypper parallel dowloading of packages openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Aris Karagiannidis (arkara) Partner organization: openSUSE.org Description: Now, i think that this is already done with apt. What should happen is that zypper should download packages concurrently and when it does download them all, then it should install them Business case (Partner benefit): openSUSE.org: Faster package management -- openSUSE Feature: https://features.opensuse.org/307862

1 13

[New: openFATE 318807] practical steps to parallel downloadinging of updates
by fate_noreply＠suse.de 27 Jun '17

27 Jun '17

Feature added by: Jason Newton (jenewton) Feature #318807, revision 1 Title: practical steps to parallel downloadinging of updates openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Jason Newton (jenewton) Partner organization: openSUSE.org Description: Yet another night I had to do updates, and 50-75 percent of that time I am watching being squandered away. This goes on year after year (been using SuSE since 2008 after Ubuntu, Gentoo, SlackWare before it in reverse order of usage). With typically over 700 updates equating out to about 60 minutes I think we can establish that updates on OpenSUSE are slow - even provided infinite bandwidth and SSDs. I've cracked open the zypper sources more than once with the intension of starting to rectify this but I cannot find the time to accomplish it. The problem is that the downloading used by zypper needs to be made parallel. The reasons for this are to support overlapping transfers to keep downloads going - there is a significant setup time to start a http based download and it adds up over 700 packages in a typical development installation. It gets worse when patches come up and shift execution to disk, throwing away precious internet bandwidth timeslots. This is the case with zypper (d)up --download=in-advance. The good news is this doesn't have to involve threads. I've taken a look before at adding support of this nature to zypper and while the codebase for zypper is all nice and OOPed, it is super tighly coupled to single task at a time execution. It is however using curl if I recall correctly. Parallel downloading with curl is very easy if already using curl and can be done without threads. Another way to do this without massive complications to the code base are executing a plan of what to do as is current and then entering a special "sync mode" (like rsync for updates) or exporting a shell script or text file of links so a user can download the updates to cache with an external tool designed for efficient batched downloading with pipelining and multiple outbound requests and either isolates the parallel tasks to a local module or gives the problem to an external tool. Zypper, after running this download tool or "sync mode" just sees alot of cache hits and proceeds as normal thereafter. The epitime is having a seperate download thread(pool) and connect it all up over something like DDS or ZMQ. You can build more stuff inhouse if you're into that. As dependencies are resolveed in the download threads, the update is installed in the main thread. This way update installation downloading is performed concurrently or overlapping which is going to be the fastest updates get to be installed. I think the last bit should be put on the roadmap but really this needs addressed and not repeated kicking forever and ever and so I urge SUSE zypper maintainers to provide a practical way for power users and suse admins to do this basically now if they were to go add a factory zypper repo - if this means "sync mode" or script/batch file generation for something like aria2c, that is really not so bad. Business case (Partner benefit): openSUSE.org: Resolving the problem in the right way will increase efficiency on SUSE's servers and reduce time of the update process both for SUSE and user (also read $ and time). Everybody wins and SuSE admins/power users/developers get to spend more time on other tasks. -- openSUSE Feature: https://features.opensuse.org/318807

1 3

[New: openFATE 309996] zypper download speed up
by fate_noreply＠suse.de 27 Jun '17

27 Jun '17

Feature added by: Robert Xu (bravoall1552) Feature #309996, revision 1 Title: zypper download speed up openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Robert Xu (bravoall1552) Partner organization: openSUSE.org Description: I think we should have zypper use aria2 or some similar program to allow 2 consecutive downloads at once. While there is an option in zypp.conf, it does not work naturally with zypper and GUI tools. Having 2 downloads at once can speed up installation rapidly. For those who aren't in the DownloadInAdvance mode, maybe they can: * download 2 at once, add them to install queue, and have the install queue process as soon as the first download is done. Business case (Partner benefit): openSUSE.org: Because Zypper is a little slow, and that's preventing a lot of packages from being installed in time. We should be able to have zypper as speedy as possible. -- openSUSE Feature: https://features.opensuse.org/309996

1 9

[New: openFATE 319679] HTTP/2
by fate_noreply＠suse.de 27 Jun '17

27 Jun '17

Feature added by: Jorge Hernandez (jurgen73) Feature #319679, revision 1 Title: HTTP/2 openFATE: Unconfirmed Priority Requester: Important Requested by: Jorge Hernandez (jurgen73) Partner organization: openSUSE.org Description: Would you please include HTTP/2 module in Factory (Tumbleweed)? HTTP/2 is almost here and it would be great if Tumbleweed is ready for it, right now there are 2 modules that look like they would do it, mod_h2 and mod_spdy, whichever is better would be appreciated. Thanks. -- openSUSE Feature: https://features.opensuse.org/319679

1 2

[New: openFATE 318397] do not delete required Windows partitions
by fate_noreply＠suse.de 27 Jun '17

27 Jun '17

Feature added by: Chris Murphy (kopathangawa) Feature #318397, revision 1 Title: do not delete required Windows partitions Requested by: Chris Murphy (kopathangawa) Partner organization: openSUSE.org Description: The 13.2 installer makes an inappropriate suggestion that results in the deletion of the Intel Rapid Start partition used by Windows 8 for fast boots. There are certain cases where this could lead to corrupted boots. Test Case: dual-boot default installation proposes deleting a required partition https://bugzilla.suse.com/show_bug.cgi?id=914582 Use Case: UEFI Windows dual-boot installation with openSUSE. Installer should recommend options that don't result in possible corruption or data loss. -- openSUSE Feature: https://features.opensuse.org/318397

1 1

[New: openFATE 311366] Integrate biosdevname into the openSUSE installer
by fate_noreply＠suse.de 26 Jun '17

26 Jun '17

Feature added by: Narendra K - (narendra_k) Feature #311366, revision 1 Title: Integrate biosdevname into the openSUSE installer openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Narendra K - (narendra_k) Partner organization: openSUSE.org Description: Description: On a Dell PowerEdge server with multiple add-in cards, the naming of the network interfaces is non-deterministic. This results in 'eth0' not mapping to "Embedded NIC 1" as labeled on the server chassis. This issue is seen on Dell PowerEdge 10G above. This feature addresses this issue by renaming network interfaces based on their location on the system motherboard at install time. The naming policy it suggests are as follows:    <![endif]--> Embedded devices: em<port> Add-in PCI cards: pci<slot>p<port>_<virtual function instance> On a PER710 with 4 Lan-On-Motherboard interfaces and a dual port add-in network controller, the interface names would look like - Onboard interfaces - em1 em2 em3 em4 Interface names for the dual port add-in controller on pci slot 2 pci2p0, pci2p1 If the second port has virtual functions enabled -pci2p1_0, pci2p1_2 ... etc Business case (Partner benefit): openSUSE.org: This feature request addresses the non-determinism in network interface naming and allows referring to the interfaces based on their physical location on the motherboard. This would help in easy administration and eliminates the need for embedded state such as HWADDR into the configuration files and names will be consistent across reboots. -- openSUSE Feature: https://features.opensuse.org/311366

1 4

[New: openFATE 311364] Include biosdevname udev helper utility into openSUSE
by fate_noreply＠suse.de 26 Jun '17

26 Jun '17

Feature added by: Narendra K - (narendra_k) Feature #311364, revision 1 Title: Include biosdevname udev helper utility into openSUSE openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Narendra K - (narendra_k) Partner organization: openSUSE.org Description: This feature is needed to implement the "Consistent Network device naming-Name network interfaces to match chassis labels" (https://features.opensuse.org/310896). Biosdevname is a udev helper which can suggest chassis based names to network interfaces. Please find latest version of biosdevname here - http://linux.dell.com/files/biosdevname/permalink/biosdevname-0.3.7.tar.gz http://linux.dell.com/files/biosdevname/permalink/biosdevname-0.3.7.tar.gz.… git://linux.dell.com/biosdevname.git -- openSUSE Feature: https://features.opensuse.org/311364

1 7

[New: openFATE 313430] Safe snapper snapshot creation / restoration during boot / shutdown
by fate_noreply＠suse.de 26 Jun '17

26 Jun '17

Feature added by: Ivar Nikolaisen (Quantumboredom) Feature #313430, revision 1 Title: Safe snapper snapshot creation / restoration during boot / shutdown openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Ivar Nikolaisen (quantumboredom) Partner organization: openSUSE.org Description: Currently Snapper takes snapshots both when doing system changes using YaST / Zypper, and also automatically on a schedule. The problem with these snapshots is that system integrity is not guaranteed (i.e., a snapshot can be taken while a file is being written, leaving the file in a corrupted state upon restoring the snapshot). I propose a mechanism where snapper takes a snapshot upon system shutdown at a stage where the snapshot can be guaranteed to be consistent. This could for example be just like a timeline snapshot, except the description should highlight that it was taken at system shutdown. It would also be very nice if it was possible to restore snapshots when booting (I believe Fedora is already working on something like this), but perhaps this should be a separate feature request? Business case (Partner benefit): openSUSE.org: It is obviously useful to have known-good restore points. Especially useful for the many users of proprietary display drivers (even more so if using Tumbleweed!). -- openSUSE Feature: https://features.opensuse.org/313430

1 3

[New: openFATE 310713] put /etc under (git) version control
by fate_noreply＠suse.de 26 Jun '17

26 Jun '17

Feature added by: Christoph Obexer (cobexer) Feature #310713, revision 1 Title: put /etc under (git) version control openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Christoph Obexer (cobexer) Description: put /etc under (git) version control to track changes made to the configuration, merge new configuration options coming from package updates / security fixes an handle the case where RPM decides to create a .rpmsave - where a administrator would need to migrate all changes from the old version to the new one in order to not end up with an unusable system upon reboot. Integration in YaST would be very cool, you could have a look at what an update changed in your system, and YaST could force you to migrate changes to configuration files that are no longer in effect. there are a fewsilly things in /etc (CUPS, alsa, ld.so.cache, and the bootsplash images i recall) that cause a lot of "fake" changes, but they would be easy to "fix". checking differences in configurations between multiple systems(to diagnose problems...) would be easy too, simply clone them and diff them, very efficient ;) . making backups of the system configuration would be easy too (simply back up /etc/.git and restoring would be non destructive in that you could check what changes will be restored) (subversion would not work well, for example because of gconf IIRC) Use Case: there was a security update once concerning session entropy in PHP, since the php.ini has been modified on the system in question the update process created a .rpmnew file, a file i would have never found it if I had not put /etc under git version control. With git however it was easy to see the file, I moved it over the php.ini and had a look at the changes, merged them in and committed the changes. -- openSUSE Feature: https://features.opensuse.org/310713

1 8