June 2014 - YaST Development - openSUSE Mailing Lists

[yast-devel] RFC: Yast Team Infrastructure: Yast Jenkins Node
by Lukas Ocilka 24 Jun '14

24 Jun '14

Hi, Today we have an outage of the Yast Jenkins node because of "No space left on device". This is a virtual machine maintained by a team member (including scripts around). It's not the first time this node has died for some reason. https://ci.opensuse.org/computer/yast-jenkins/executors/0/causeOfDeath Thread has died java.io.IOException: No space left on device As this is a core infrastructure of the Yast team and everyone depends on it (as we got used to it and OBS/IBS also expects SRs to be done this way), I would like to change the current rules this way: 1. This is a core infrastructure --> it should run on a Yast-team-owned server (we have a HW ready in server room) 2. Any (core) infrastructure, including scripts, should be owned by Yast team 3. Everything needs to be at GitHub following the same (but stricter) rules for merging changes (continuous deployment from GitHub?) For instance, I'd recommend to require two different LGTMs instead of one as it is now 4. Everything needs to be well documented in a way that "everyone" in the team should be able to recover from such error or even start a new node if something goes really bad 5. Everyone in the team needs to have a root (e.g., via ssh keys) access but not to change anything they do not understand (documentation) 6. We need monitoring, maybe internal IT guys can do that for us and they might have and access to that system for urgent cases as well All this doesn't need to be changed "right now". One little step at the time. Then another. Thanks in advance Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader Cloud & Systems Management 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

2 1

[yast-devel] snapper timeline_limit not working as expected...
by Zorn, Sascha 23 Jun '14

23 Jun '14

2 2

[yast-devel] libstorage plans?
by Roman Neuhauser 23 Jun '14

23 Jun '14

hello, Arvin mentioned in libstorage/pull/69 that there are "important and fundamental changes required in libstorage". i'd like to know what you (both Arvin and the team as a whole) plan in this regard? after seeing some real-world problems with libstorage, and from my short venture into its code i'd say the most pressing problem is the cylinder as the base unit for partition positions and sizes, with the broken class hierarchy (dynamic_cast...) distant second. while these two may be the "worst", it does not necessarily make sense to approach them first; it may be easier to postpone that until after some other cleanup is done to make the code clearer. in this regard, libstorage could use wider adoption of C++11 features like "auto" and range-based loops. so, what is your roadmap? -- roman -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 3

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 20 Jun '14

20 Jun '14

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-ldap: - Do not add MenuButton to ButtonBox (6 days) https://github.com/yast/yast-ldap/pull/17 - do not add MenuButton to ButtonBox (7 days) https://github.com/yast/yast-ldap/pull/16 -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 19 Jun '14

19 Jun '14

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-ldap: - Do not add MenuButton to ButtonBox (5 days) https://github.com/yast/yast-ldap/pull/17 - do not add MenuButton to ButtonBox (6 days) https://github.com/yast/yast-ldap/pull/16 -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 18 Jun '14

18 Jun '14

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-ldap: - Do not add MenuButton to ButtonBox (4 days) https://github.com/yast/yast-ldap/pull/17 - do not add MenuButton to ButtonBox (5 days) https://github.com/yast/yast-ldap/pull/16 -- 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] Bugs Priority: Explanation
by Lukas Ocilka 17 Jun '14

17 Jun '14

Hi, I've asked SLE 12 release managers to explain their understanding of priorities for SLE 12m this explanation comes from Thorsten Kukuk: --- cut --- P1: ship stopper for GMC, best all of them are fixed before RC1 P1s are also those bugs, that you cannot fix with a maintenance update P2: should be fixed best before GMC, but can be solved with a maintenance update, too P3: something which can wait for the next service pack P4: fix it if it is easy to fix and you have to touch the package anyway, ignore or reject otherwise P5: release manager had no time to prioritize or important info is missing --- cut --- What needs to be fixed in "the current beta/RC" is marked as "Blocker=yes". Hope this helps. Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader Cloud & Systems Management 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] Pending Pull Requests
by yast-ci＠opensuse.org 17 Jun '14

17 Jun '14

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-network: - Fixed internal error raised when cloning config in AY moduleb (12 days) https://github.com/yast/yast-network/pull/168 -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 16 Jun '14

16 Jun '14

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-network: - Fixed internal error raised when cloning config in AY moduleb (11 days) https://github.com/yast/yast-network/pull/168 -- 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] Pending Pull Requests
by yast-ci＠opensuse.org 13 Jun '14

13 Jun '14

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-network: - Fixed internal error raised when cloning config in AY moduleb (8 days) https://github.com/yast/yast-network/pull/168 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0