February 2010 - YaST Development - openSUSE Mailing Lists

[yast-devel] Webyast - models in webclient and webservice - summary
by Josef Reidinger 16 Mar '10

16 Mar '10

Hi, because on Friday I finally merge in webclient yast model I create short summary of both models, its features and why you should use it. webservice model: Inspired by ActiveModel. It adds methods for easy validation, serialization, mass loading and callbacks. for example usage see Ntp and time plugins. For documentation see - class BaseModel::Base (I cannot connect to hudson for direct link) why use it? smart to_xml and to_json so you don't need to define own method unless you have hash with problematic keys (see time model for example how to solve it) validations which checks attributes before save same behavior as ActiveRecord and ActiveResource webclient model: Adaptation of ActiveResource to our case of changing site and credentials to target machine. It adds method model_interface which sets interface for model and fix finding single resource. Also helper methods for HttpMock which tests ActiveResource is added. for example usage see Time plugin or network plugin. For documentation see module YastModel::Base example of usage: class Stime < ActiveResource::Base extend YastModel::Base model_interface :'org.opensuse.yast.modules.yapi.time' end why use it? you can add functionality to model, so no more controllers which have more then one page same usage as any ActiveResource model, so new programmer is not confused what we using easier testing (there is still place to improve it), but I found that many plugins doesn't have test or test is really simple and don't cover enough code. for testing see how looks tests in network or time module. Thanks for attention and I welcome any comments, suggestion or bugs ( ..bugs are not so much welcome, but I fix it) Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast (language,time,basesystem,ntp) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 3

[yast-devel] results enable disable survey
by Martin Schmidkunz 02 Mar '10

02 Mar '10

Hi! Please find the results of enable/disable a settings at: http://en.opensuse.org/UX/Enable_Disable_in_webYaST The results show that it is more usable for webYaST to provide additional text providing the current status of a setting. Thanks for your participation! Martin -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

11 19

[yast-devel] WebYaST: javascript per-plugin library
by Michal Zugec 01 Mar '10

01 Mar '10

Hi! I'd like to share my observation: I needed to share my javascript code between two files (it was form validation for new and edit action + some more) I created webyast-users-ui/plugins/users/public/javascripts/users_edit.js and included it into my files with <%= javascript_include_tag "users_edit.js" %> It's important to use $pluginname as prefix to be unique in whole project! That's it ... Bye, Michal -- Best Regards, Michal Zugec Software developer --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: mzugec(a)suse.cz Lihovarska 1060/12 tel: +420 284 028 960 190 00 Praha 9 fax: +420 296 542 374 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 6

[yast-devel] Pattern and one click install
by Duncan Mac-Vicar Prett 26 Feb '10

26 Feb '10

The repository now has a one-click http://download.opensuse.org/repositories/YaST:/Web/openSUSE_11.2/webyast.y… And also generates a pattern browsable by YaST/zypper for the repository automatically. The pattern/one click can be installed by doing: osc meta pattern YaST:Web webyast -e YaST:Web/openSUSE_11.2 automatically builds on top of YaST:Web:11.2 so if a one click install is clicked in the first, the later repo is automatically included/added. Only problem we have is that we have right now 5 package lists to maintain: - 3 different appliances - addon - pattern/one click Any ideas how to improve here? -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] WebYaST status update, Fre Feb 26nd
by Klaus Kaempf 26 Feb '10

26 Feb '10

present: jsrain, dmacvicar, kkaempf, bbrunner, vgorobets, mvidner, jdsn, jreidinger, mzugec, lslezak, bubli, jsuchome absent: schubi, mschmidkunz, tgoettlicher, mkudlvasr Status ------ Big thanks to Benjamin for his contributions and much fun in his next team ! bbrunner: - moving on (trainee rotation plan) - next: different team jsrain: - released Wiki tutorial - next: non-webyast dmacvicar: - cleaned up buildservice - took care for openSUSE 11.2 build - added pattern and one-click-install - next: review tutorial kkaempf: - non-webyast vgorobets: - worked through tutorial - next: find bugs to fix mvidner: - going through bugs - next: help WebYaST users jdsn: - bug fixing - product creation (update channel) - next: add more exception catchers jreidinger: - working on bugs - next: bug fixing mzugec: - working on bugs - next: users form validation lslezak: - working on bugs - digged into jQuery bug (will write mail about it) - next: caching in repo module - next: fixing more bugs bubli: - fixed UI bugs (spacing and layout) - added class for fieldsets - fixed systemtime UI - next: make buttons more visual attractive jsuchome: - worked on UI related bugs - still working on mail bugs - next: non-webyast work --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] WebYaST tutorial review finished
by Jiri Srain 25 Feb '10

25 Feb '10

Hi! I finished the review of the WebYaST development tutorial, which is available at http://en.opensuse.org/YaST/Web/Development/Tutorial . It should be up-to- date and it should be possible to crete a new WebYaST module following this tutorial. If you find any issues in the document (I don't claim that it is perfect, also it may be just that something is not clear from reading it), please, either report them to me via bzilla or fix them - it's a wiki :-) Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.cz Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] WebYaST status update, Thu Feb 25nd
by Klaus Kaempf 25 Feb '10

25 Feb '10

present: jsrain, dmacvicar, kkaempf, schubi, tgoettlicher, mvidner, mzugec, jsuchome, bubli, vgorobets, mkudlvasr absent: bbrunner, mschmidkunz, jdsn, schubi, bbrunner, jreidinger, lslezak Status ------ WebYaST for SLES11 SP1 Beta5 is done, thank you all! This was a much smoother process than with Beta4. Everyone: Please update your bugs and close the fixed ones. jsrain: - worked on wiki (tutorial) - next: wiki dmacvicar: - built service appliance - shortened package list - next: non-webyast schubi: - created SP1 and 11.2 appliances and addons - testing - next: status module bugs tgoettlicher: - testing - next: addon product test - next: vacation & yast2 mvidner: - testing - pushed updates for the 1.0 release - next: leftover bugs mkudlvasr: - testing - firewall module tests - next: fixing bugs jsuchome: - bug fixes - testing 1.1.11 - next: bug fixing mzugec: - testing 1.1.11 - added test cases - next: yast2 bugs - next: bug fixing bubli: - looked through UI related bugs - replaced icons (using 'Tango' icons now) - next: pick UI bugs to fix vgorobets: - learned by reading WebYaST wiki - testing - next: learn more about webyast - next: check with jsrain kkaempf: - testing, testing, and more testing - writing release notes - next: release WebYaST Beta5 - next: go through bug list --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Re: Webyast - roles management
by Josef Reidinger 24 Feb '10

24 Feb '10

> > Hi, > I found a plugin that seems to do what you want. > http://code.google.com/p/rolerequirement/ Thanks for source. I read it, but I think that it give check to much high-level. We have permissions on layer which communicate with dbus as permission is mapped (name of permission is constructed from dbus call) to dbus call > ... and it seems to be maintained. quote from first paragraph: "NOTE: I am no longer maintaining this project. Please see the note on the github page (http://github.com/timcharper/roll_requirement) for more information. Thanks, Tim" :) > > You are talking about roles in the context of web-yast not in > the context of the underlying OS, right? in context of web-yast > Or do you plan to allow web-yast users to change the OS config > by using yast, read/write to system files etc.? Now webyast users = users in OS. But it can change in future. Klaus can give you more information on this topic. > > From a security point of view it is important to have a complete code > coverage of RBAC to avoid bypassing the ACLs by using another interface > (RESTful vs. UI vs. ...) or delegate an automatic and user-defined task > to the web-application which is then executed with the role of the web-app not > with the role of the web-yast user (something equal to a cron job). Because RBAC is just interface and inside it is about distribution permissions, It works like now..users has individual permissions. Just administrator manage it with roles, do not directly touch each permissions. So another interface cannot bypass this permissions. Josef > > Bye > Thomas > > > Am Dienstag 23 Februar 2010 19:02:54 schrieb Josef Reidinger: > > Hi, > > I get this task and I think it is time to little discussion what is > > possible and how it should be done. (how it looks I think is decided - it > > is similar to groups). > > > > Roles is something like mark which grants user set of actions. So e.g. role > > HR admin can add/remove users and edits its details it is one role but it > > contains more permissions. > > > > At first I investigate little how lib/yast_roles.rb work...and it doesn't > > work. I try play with polkit and if you ask for user which doesn't have > > UID it fails. Problem is that roles doesn't have UID. So roles must be > > stored beside. > > > > My proposal how it could work. > > > > We have defined list of roles in one yaml file. owned by yastws, strict > > permissions. This list contain role and its permissions. Then we have > > second list which assign to role its users. > > If user get into role it get permissions of this role. > > If user remove from role all permissions is removed and again all roles is > > applied. If role is modified then all users in this role has removed > > permissions and all roles is again applied (the longest variant but roles > > should change only rare). > > > > So permission module is changed that it act on roles not on users for > > appliance. For non-appliance usage it acts on users. ( I plan create two > > package to easier maintenance). > > > > I welcome any comments, hints or questions > > > > Josef > > > > -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, parts of webyast -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] WebYaST status update, Wed Feb 24nd
by Klaus Kaempf 24 Feb '10

24 Feb '10

jsrain, dmacvicar, kkaempf, mschmidkunz, jdsn, schubi, bbrunner, tgoettlicher, mvidner, jreidinger, mkudlvasr, jsuchome, mzugec, lslezak, bubli, vgorobets jsrain - testing 1.1.11 appliance - worked on wiki - next: wiki dmacvicar: - build service appliance - rubygem fixes - next: non-webyast kkaempf: - testing - fixing ruby-dbus mess I introduced - next: testing 1.1.11 appliance, bug prioritization mschmidkunz: - ui work - next: repository module jdsn: - registration bugs schubi: - creating appliances - testing - next: status module bugs bbrunner: - testing - next: testing tgoettlicher: - testing - next: 1.1.11 test mvidner: - testing - next: leftover bugs jreidinger: - testing - rubygems problems - next: bugs mkudlvasr: - fix language module - next: testing, bug fixing jsuchome: - users module fixes - testing 1.1.11 - next: bug fixing mzugec: - testing 1.1.11 - L3 work - next: test coverage improvement in users lslezak: - improved repository test suite - bug fixing - next: bug fixing bubli: - users main screen design - users filters jQuery - next: ui improvements vgorobets: - setting up - build webyast - next: learn more about webyast --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Webyast - roles management
by Josef Reidinger 24 Feb '10

24 Feb '10

Hi, I get this task and I think it is time to little discussion what is possible and how it should be done. (how it looks I think is decided - it is similar to groups). Roles is something like mark which grants user set of actions. So e.g. role HR admin can add/remove users and edits its details it is one role but it contains more permissions. At first I investigate little how lib/yast_roles.rb work...and it doesn't work. I try play with polkit and if you ask for user which doesn't have UID it fails. Problem is that roles doesn't have UID. So roles must be stored beside. My proposal how it could work. We have defined list of roles in one yaml file. owned by yastws, strict permissions. This list contain role and its permissions. Then we have second list which assign to role its users. If user get into role it get permissions of this role. If user remove from role all permissions is removed and again all roles is applied. If role is modified then all users in this role has removed permissions and all roles is again applied (the longest variant but roles should change only rare). So permission module is changed that it act on roles not on users for appliance. For non-appliance usage it acts on users. ( I plan create two package to easier maintenance). I welcome any comments, hints or questions Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, parts of webyast -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 2