July 2009 - YaST Development - openSUSE Mailing Lists

[yast-devel] WebYaST daily sync - 07/08/09
by Bjoern Geuken 08 Jul '09

08 Jul '09

WebYaST daily sync - 07/08/09 Status: ---------- Stephan: - Worked on jqery plot widgets - Has problems to get studio stuff run - Started documentations on wiki: http://en.opensuse.org/YaST/Web/Development#System_Monitoring_module Björn: - Nearly done with status module (rest-service), some things(features) missing - Will be at vocational school and vacation for 4 weeks, beginning on friday. Someone needs to care for test cases/robustness Jiri Suchomel: - Test suite for systemtime is in progress Jiri Srain: - no status yet Martin V.: - Got reply from rdbus developer - Looked at rbus: developers are also inactive, but api looks nicer and license is gpl, not lgpl like at rdbus. Worth having a close look -- 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 data model
by Klaus Kaempf 08 Jul '09

08 Jul '09

Hi, yesterday's commit by jsuchome (model adapted to the YaST data structure, see http://lists.opensuse.org/yast-commit/2009-07/msg00158.html) raised an important topic which hasn't been discussed before - the data model we use for WebYaST. REST only defines the architecture how to manage resources, it does not describe how resources look like. In WebYaST, all the RESTful stuff is nicely handled by Rails ActiveResource. It manages Ruby objects according to the REST style. However, this leaves the responsibility for a good data model on the developer when defining the Ruby classes. A couple of rules should apply here, e.g.: - Honor Ruby style when naming attributes and classes. Classes have CamelCase, attributes have lower_case_with_underscores (see http://www.caliban.org/ruby/rubyguide.shtml for the 'Unofficial Ruby Usage Guide') - Limit the attribute types to - numerical (int, float) - string - boolean - array (list) - hash (map) Hash is probably questionable as it might be more useful to use a separate class for this. Its probably a case-by-case decision. - Document the resource class rDoc (http://rdoc.sourceforge.net/doc/index.html) is included with Ruby and quite useful for in-line documentation. - Make the resource introspectable This is mostly covered by ActiveRecord itself, we're still missing a classification on what a resource represents (i.e. 'logical device', 'physical device', 'identity' (user), etc.). Proposals welcome ! If anyone has pointers to applicable data models already in use, send them in ! Klaus --- 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

2 1

Re: [yast-devel] Prague YaST Team Meeting Minutes: 2009-06-25 + 2009-07-02
by Thomas Goettlicher 07 Jul '09

07 Jul '09

On Tuesday 07 July 2009 13:52:39 Lukas Ocilka wrote: > Qt4 Control Center > ------------------ > YaST Control Center has been finally ported to Qt4 and submitted into > FACTORY. You'll see that in the very next openSUSE 11.2. Cool! I can hardly wait to use it! Thomas -- 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] Prague YaST Team Meeting Minutes: 2009-06-25 + 2009-07-02
by Lukas Ocilka 07 Jul '09

07 Jul '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Minutes of Prague YaST Team Meeting: 2009-06-25 + 2009-07-02 ============================================================ http://en.opensuse.org/YaST/Team Present: Prague YaST Team Absent: Some of the team members Minutes: Lukas Ocilka PDB - --- We're going to stop building packages using information written into PDB, especially the package description and license. Use the updated yast2-devtools for creating a spec file for 11.2 and adjust spec.in file accordingly. Qt4 Control Center - ------------------ YaST Control Center has been finally ported to Qt4 and submitted into FACTORY. You'll see that in the very next openSUSE 11.2. YaPI && Mode() == test - ---------------------- The current YaPI implementation adjusts the 'Mode' to 'test' which may actually produce some unexpected errors if a YaPI module checks for Mode::test() for whatever reason. SMT - --- We are currently just about to finish the SMT 11 product. Staging of mirrored repositories has been changed quite a lot. WebYaST Erroneous Dependency - ---------------------------- WebYaST is currently dependent on X server because of some testsuite. This will be fixed as soon as possible (but not sooner). YaST ISNS - --------- Mzugec has added yast2-isns into our svn: http://svn.opensuse.org/svn/yast/trunk/isns/ - -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) - ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFKUzcHVSqMdRCqTiwRAmFwAJ9NGE/606syefQOeLhifsCT3U/JrgCcCQ+Z xL0IpzfyAaEBNPoJuCdJMyU= =vApT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 3

[yast-devel] Webyast, Ajax and javascript
by Josef Reidinger 07 Jul '09

07 Jul '09

Hi, I do some changes in javascipt in webyast. At first I remove all javascript attached to rest-service as it is useless and should not be used. (also it decrease size of package) At second I add jrails plugin for ajax, as discussed previous. All problems report to me. How you can use this plugin? it is simple just use rails helpers ( http://api.rubyonrails.org/classes/ActionView/Helpers/PrototypeHelper.htm ) only difference is that don't use directly including tag like "prototype" or "effects" and use :defaults. For example usage look at time module frontend (its view). -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast modules language and time -- 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 daily sync - 07/07/09
by Bjoern Geuken 07 Jul '09

07 Jul '09

WebYaST daily sync - 07/07/09 Status: ------- Duncan: - worked on setup automation yesterday, eg chroot environment - Björn: - is works on status module (rest-service) Joseph: - worked on test suite for time - played with jquery functionality - plans to work on tests for time, had problems with Ajax Michal: - don't know what to work on - will talk with klaus Martin V.: - fixes ruby dbus - will make rpms with fixes and send them upstream Stephan: - designed rest-interface with Björn - had a look how collectd works - looked at jqery plot query functionality og studio Klaus: - looked at code robustness of WebYast - worked on test cases - cleaned up code Focus Areas: ------------ Duncan: Quality Björn: Status Joseph: Time, Infrastructure Michal: Martin: Infrastructure Stephan: Status Klaus: Robustness, Infrastructure Klaus will get WebYast into Bugzilla -- 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 and permission to call yast dbus backend
by Josef Reidinger 07 Jul '09

07 Jul '09

Hi, I study permissions problem on 11.1 in language module. I found (with mvidner help) root of problem in yast dbus backend call from yast-webservice. I check in webservice if user has rights (in this case root) and then I call to dbus. Problem is that dbus backend check not again root but again caller which is yastws user. So first solution which work is grant yastws all rights in rpm post-script as we do for root. But I think that this is quite big security issue as this mean that anyone who crack into webservice has all rights because he can act as yastws user with all rights to yast backend. This should be somehow solved. MVidner have idea that we could run backend as logged user instead yastws. This has problem that we must somehow handle sending passwords and also multiuser process (another user need maybe another port). My idea is use ssh with keys authentication and execute dbus call via this ssh, so then we can act as logged user and not as yastws. Any other ideas or comments? thanks JR -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 6

[yast-devel] Webyast and jrails plugin
by Josef Reidinger 07 Jul '09

07 Jul '09

Hi, after short discussion on ruby-dev channel and my attempt to write ajax remote call in jquery, I found that if we use jrails plugin we don't break anything as current script.aulo helpers break jquery stuff and cannot be used. So if developer want use rails helper, jrails at least don't break jquery functionality and if it doesn't work they can always use pure jquery without any helpers. Does anyone have any opinion why don't add jrails plugin? (and if so, then please specify fully working jquery stuff that act as observer ajax helper :) -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast modules language and time -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 2

[yast-devel] Rest-service and basic tests
by Josef Reidinger 07 Jul '09

07 Jul '09

Hi, I write tests for time module after language module and find, that some tests is same and maybe should be added automatic, to ensure that all rest-service module act in basic situation same. Basic tests should be if it return same MIME-type on calls, if they correctly handle no permissions and if they act correctly on non-valid update data. Do you have any idea how add that tests automatic to each module's testsuite (and how automatic mockup model)? my basic tests how it could look like: def test_access_show Systemtime.any_instance.stubs(:read) get :show assert_response :success end def test_access_denied #mock model to test only controller Systemtime.any_instance.stubs(:read) @controller.stubs(:permission_check).returns(false); get :show assert_response :forbidden end def test_access_show_xml Systemtime.any_instance.stubs(:read) mime = Mime::XML @request.accept = mime.to_s get :show, :format => :xml assert_equal mime.to_s, @response.content_type end def test_access_show_json Systemtime.any_instance.stubs(:read) mime = Mime::JSON @request.accept = mime.to_s get :show, :format => :json assert_equal mime.to_s, @response.content_type end def test_update_noparams Language.any_instance.stubs(:save) put :update assert_response :missing end def test_update_noperm #ensure that nothink is saved Language.any_instance.expects(:save).never @controller.stubs(:permission_check).returns(false); put :update, Data assert_response :forbidden end -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast modules language and time -- 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] ruby-dbus
by Martin Vidner 06 Jul '09

06 Jul '09

Hi, I have been fixing ruby-dbus over the weekend, and I've published my git tree on Github: http://github.com/mvidner/ruby-dbus/tree/master It has a fix for Jirka's array-in-variant problem, a fix for Pepa's variant-in-array problem (ticket #30) and for a complex-variant "major" ticket #27. And of course test cases for that (TDD FTW). Now I feel skilled enough to contact the authors to help them with the project :-) -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0