November 2015 - YaST Development - openSUSE Mailing Lists

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 13 Nov '15

13 Nov '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-audit-laf: - Fixed validation of AutoYaST profile (bsc#805275). (22 days) https://github.com/yast/yast-audit-laf/pull/5 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (9 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (37 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Poc recover values (17 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (59 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (20 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (21 days) https://github.com/yast/yast-auth-server/pull/21 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Planning the Next Sprint (#12)
by Lukas Ocilka 12 Nov '15

12 Nov '15

Guys, As you can see in Trello, I'm currently planning new sprint (planning meeting will be tomorrow for both sub-teams). This time, the focus should be "The future of SLE 12 (SP2 + Leap 42.2) & Critical SLE issues (SP1-P1s and Maintenance updates)". Team A ====== - In general, I wanted to continue with the trend set by Jiri before he left for his vacation, just check the current Sprint Backlog Team 1 ====== - The team has some PBIs under waterline in the current backlog, but I believe you can make all of them and then there are some new interesting PBIs the Incoming Board. For both teams ============== - This time, I'd like to focus more on development (with refactoring) than on fixing P1s - we do not have that many P1s now anyway - I would like you all to check the current queue (first the current backlog, then the planned one) and think about it: Is this what will bring the best value for customers/us? Isn't there anything more important? Considering what we know now, is it important at all? - Please, suggest shifting priorities, adding important stuff that has been left out of planning, or suggest removal of items if you believe they are unimportant (now). Always provide explanation "why". Thanks in advance Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 4

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 12 Nov '15

12 Nov '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-audit-laf: - Fixed validation of AutoYaST profile (bsc#805275). (21 days) https://github.com/yast/yast-audit-laf/pull/5 Pending requests in repository yast-bootloader: - Fixed validation of AutoYaST profile (bsc#805275). (21 days) https://github.com/yast/yast-bootloader/pull/272 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (8 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (36 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Poc recover values (16 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (58 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (19 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (20 days) https://github.com/yast/yast-auth-server/pull/21 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Running AutoYaST integration tests on openQA
by Imobach González Sosa 11 Nov '15

11 Nov '15

After meeting Schubi and Ancor, we've reached an agreement about how we could run AutoYaST integration tests on openQA. = Background On the openQA side, it looks like: * They use an openQA variable to set the profile name (called 'AUTOYAST')[1]. Also an AUTOUPGRADE variable is available. * They have some modules/tests to check the AutoYaST installation process[2]. On our side, we have a set of profiles and tests. Those tests are just RSpec aspects which run some scripts to check everything is ok. Profile and tests are matched by name. So, if you install a system using the 'sles12.xml' profile, you should run 'sles12.rb' test. = Proposed solution The idea is to create a RPM package containing profiles and tests (basically, the 'test' directory[3] from AutoYaST integration tests). Then, we'll add a new openQA module/test which: * Install the tests package (can be fetched from OBS/IBS). * Install RSpec. * Run the tests which match the AutoYaST profile and report the result. * Clean-up the installed packages. There're some minor issues to solve like, if we finally use RSpec to run the tests, the helper should be smart enough to run those tests locally. But it's something really easy to solve. Also this solution opens the door to use openQA as a backend for AutoYaST integration tests in the future. Please, feedback is welcome! Regards, Imo [1] https://openqa.suse.de/tests/157785 [2] https://openqa.suse.de/tests/157785/modules/system/steps/1 [3] https://github.com/yast/autoyast-integration-test/tree/master/test -- Imobach González Sosa YaST Team at SUSE LINUX GmbH

2 4

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 11 Nov '15

11 Nov '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-audit-laf: - Fixed validation of AutoYaST profile (bsc#805275). (20 days) https://github.com/yast/yast-audit-laf/pull/5 Pending requests in repository yast-bootloader: - Fixed validation of AutoYaST profile (bsc#805275). (20 days) https://github.com/yast/yast-bootloader/pull/272 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (7 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (35 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Poc recover values (15 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-packager: - Backport raw URL editing and a repo filter to SLE12-GA [do not merge/submit yet] (18 days) https://github.com/yast/yast-packager/pull/139 Pending requests in repository yast-pkg-bindings: - Backport Pkg::SourceRawURL() and Pkg:ExpandedUrl() to SLE12 [do not merge/submit yet] (18 days) https://github.com/yast/yast-pkg-bindings/pull/54 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (57 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (18 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (19 days) https://github.com/yast/yast-auth-server/pull/21 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] is TW installer on mirrors currently known to be broken?
by Felix Miata 10 Nov '15

10 Nov '15

I just tried a 32 bit HTTP installation initialized from Grub using previously downloaded from online repos boot/i386/loader linux and initrd. Process starts with license agreement, does system probe, stops for adding online repos and/or include add-on...., then jumps directly to suggested partitioning, within which none of the existing 31 partitions on the single SATA HD on ICH6 are found by YaST, even though fdisk on vtty2 shows a normal listing of all 31. I found no corresponding existing bug for component installation and product Tumbleweed opened in past 2 weeks, or 2 months. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 7

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 10 Nov '15

10 Nov '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-audit-laf: - Fixed validation of AutoYaST profile (bsc#805275). (19 days) https://github.com/yast/yast-audit-laf/pull/5 Pending requests in repository yast-bootloader: - Fixed validation of AutoYaST profile (bsc#805275). (19 days) https://github.com/yast/yast-bootloader/pull/272 Pending requests in repository yast-country: - Some changes in the tumbleweed mappings (bsc#942899 and bsc#942896) (6 days) https://github.com/yast/yast-country/pull/61 - Ensure ntp is installed (when Install Recommended Packages is off) (34 days) https://github.com/yast/yast-country/pull/55 Pending requests in repository yast-installation: - Poc recover values (14 days) https://github.com/yast/yast-installation/pull/319 Pending requests in repository yast-packager: - Backport raw URL editing and a repo filter to SLE12-GA [do not merge/submit yet] (17 days) https://github.com/yast/yast-packager/pull/139 Pending requests in repository yast-pkg-bindings: - Backport Pkg::SourceRawURL() and Pkg:ExpandedUrl() to SLE12 [do not merge/submit yet] (17 days) https://github.com/yast/yast-pkg-bindings/pull/54 Pending requests in repository yast-storage: - Propose /boot for encrypted root on PowerPC (56 days) https://github.com/yast/yast-storage/pull/155 - don't create btrfs subvolumes outside the root fs (bsc#940797) (17 days) https://github.com/yast/yast-storage/pull/148 Pending requests in repository yast-auth-server: - Drop ca mgm (18 days) https://github.com/yast/yast-auth-server/pull/21 Pending requests in repository autoyast-integration-test: - Check Kdump configuration with multiple crashkernel options (9 days) https://github.com/yast/autoyast-integration-test/pull/30 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Adding snapper/libstorage to Jenkins
by Lukas Ocilka 09 Nov '15

09 Nov '15

Moin, I've been working on this task ($SUBJECT, https://trello.com/c/Rg7bI6rP/367-3-add-libstorage-snapper-to-jenkins) for some time and implemented a simple but ugly solution: 1. New Jenkins project: https://ci.suse.de/view/openSUSE/job/snapper/configure 2. New simple Rakefile at https://github.com/kobliha/snapper/tree/jenkins_support 3. Several newly installed packages at vm-yast-ci-worker (automake, libtool, gcc-c++, libmount-devel, dbus-1-devel, libacl-devel) 4. make -f Makefile.repo && rake osc:build This currently SUCCEEDS! :) Yast projects have .spec files in their /package directories, but snapper has snapper.spec.in and the .spec file is then generated on-the-fly. Although the current Jenkins solution is really ugly as it brings too many new dependencies into the infrastructure, it's a step forward (at least I hope so). So, what do you think of that? How bad is 'bad', how ugly is 'ugly' :)? PS: If you can't access some pieces of the infrastructure, then you just can't, and I'm sorry -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 37

[yast-devel] A multi-billion company living SCRUM?
by Lukas Ocilka 06 Nov '15

06 Nov '15

Moin, Today I came across these two great articles (see below) about SCRUM in a really big company, they've been developing in this way for 4-5 years already. I've quoted some parts of these articles, maybe you find it interesting. As we are going to have new retro meeting next week and plan new sprint after that, we might try to "get inspired" by these articles. http://www.forbes.com/sites/stevedenning/2015/10/27/surprise-microsoft-is-a… There would be two distinct phases: a coding phase, and then a test-and-stabilization phase. They would have a big celebration at a milestone which they called “code complete.” They would hold a big party, because it was a big achievement. It was when they moved on to testing and stabilizing and delivering the beta version of the code that the trouble started. They would find an unexpectedly large number of bugs in the code. And they kept discovering more bugs. They would also get feedback that some of the features they had built were not quite right. What they hadn’t realized in those celebrations at the end of the coding phase is that they were actually sitting on top of a mountain of unresolved quality problems. They had no idea that instead of a huge achievement, they had just incurred a massive amount of technical debt. If there is a problem, the team fixes it if they can. If they can’t, they just don’t deploy that feature. The team decides. The team does its own stress testing and documentation. http://www.forbes.com/sites/stevedenning/2015/10/29/microsofts-sixteen-keys… The team is talking about the issues and discussing with the managers and reviewing what they have learned. In every sprint, they are taking a fresh look at things from the user’s viewpoint. Of course, if you ask an engineering team, as Aaron does, “What does leadership make you do that is slowing you down?” he gets a ton of stuff, not just one or two things. They often pull out a whole scroll of issues. They were just waiting for him to ask! They tell him everything he’s doing wrong and they have a conversation. The point is that the conversation takes place and it’s a safe conversation to have. Continuous delivery has meant more modularity in design and a change in architecture. “In the old days,” says Aaron, “when the code had been written, the team had a party. They were celebrating. They felt they had accomplished something. But in reality, they were sitting on a mountain of bugs. In fact, they hadn’t even found all the bugs. Now they had to go back and find them all. And fix them. And they were still months away from delivering software. It was a nightmare.” “Now the bugs never grow. There ‘s a Key Performance Indicator (KPI) we call ‘the bug cap.’ It’s the number of engineers on your team times four. So if you have ten engineers, your bug cap is 40. If you get to 40 bugs, the team needs to stop work on new features and the next sprint, get the bug count back down below 40. It’s self-managing. Teams know this. It means that we can ship product all the time now, because we know we’re always in a healthy state.” The sales teams hooks the developers up with customers. The program managers talk to customers on Twitter all the time. Get good at the science of Agile and Scrum but don’t be overly prescriptive; Don’t copy others: learn from others; Stop trying to predict the future; Optimize around customer feedback. Maybe I've spoiled the whole thing by quoting these parts, but hopefully not. Also please, don't take these as "those that are the most important for Lukas and we need to argue" ;) These are just "interesting" for several reasons. Happy reading & Have a nice weekend Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] storage redesign review meeting
by Arvin Schnell 05 Nov '15

05 Nov '15

Hi, I just created a doodle poll http://doodle.com/poll/em4mg6exxpu8z98v to schedule a jangouts meeting for some final discussion about the storage redesign. Since we need this for the sprint review next week there are only a few slots. Regards, Arvin -- Arvin Schnell, <aschnell(a)suse.com> Senior Software Engineer, Research & Development SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 1