September 2009 - YaST Development - openSUSE Mailing Lists

[yast-devel] Distribution dependent Requires: in *.spec file (SLE11 vs. 11.2)
by Ladislav Slezak 22 Sep '09

22 Sep '09

Hi all, We need to have correct WebYaST package dependencies to YaST in both 11.2 and SLE11 distributions. Because yast packages have completely different version numbers we have to explicitly check this in *.spec file using %suse_version macro. Example (just committed in 'service' REST plugin): ----------------------------------------------------------- # YaPI/SERVICES.pm %if 0%{?suse_version} == 0 || %suse_version > 1110 # 11.2 or newer Requires: yast2 >= 2.18.24 %else # 11.1 or SLES11 Requires: yast2 >= 2.17.10.2 %endif ----------------------------------------------------------- Please adapt your packages accordingly. See http://en.opensuse.org/Build_Service/cross_distribution_package_how_to for more details. -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 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, 2009-09-21
by Jiri Srain 22 Sep '09

22 Sep '09

present: kkaempf, dmacvicar, schubi, mschmidkunz, lslezak, jsrain, jreidinger kkaempf: - administrative stuff dmacvicar: - merged log into master - ongoing discussion on ML schubi: - continued translation stuff jreidinger: - merged NTP code to master - exceptions discussion on ML - TBD: testing, bugfixing mschmidkunz: - learning jquery - redesign of network mock-up -- 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: [yast-commit] <rest-service> master : Change calling conventions for Invalid parameters to follow DRY
by Klaus Kaempf 22 Sep '09

22 Sep '09

* Josef Reidinger <jreidinger(a)suse.cz> [Sep 22. 2009 10:29]: > else > logger.warn("No argument to update") > - raise InvalidParameters.new [{:name => "language", :error => "Missing"}] > + raise InvalidParameters.new :language => "Missing" This is looking way better now, thanks Josef. Now I wonder if the "Missing" string shouldn't be replaced by a constant to make its semantic meaning clearer ?! 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

[yast-devel] WebYast: Error reporting in backend and how to use it in plugin
by Josef Reidinger 22 Sep '09

22 Sep '09

Hi, I done error reporting in backend based on exceptions (Universal exceptions is in file exceptions in webservice/lib). There is two type of error: First is invalid or missing parameters. For this case exist InvalidParameters exceptions. For example usage and details please see documentation of this exceptions. After you throw it, then if you don't catch it, it response 422 and use Error reporting structure for ActiveResource. So it return false on ActiveResource#save see ActiveResource::Base documentation for details (section validations errors). Second is problem on target machine like missing file, failed call of script, missing permissions etc. For this case exist ancestor BackendError which if not catched response 503 and serialized xml with description of problem (exceptions.rb contains few child for inspiration). If you don't catch error on frontend it end up in error reporting page which print error. For translated error is neccesarry to add translated string to ErrorConstructor module in libs directory at frontend (see already translated messages for usage). If you have any question, suggestion or problem please say it -- 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 3

[yast-devel] Hudson does not build anymore
by Stefan Schubert 22 Sep '09

22 Sep '09

-------- Original-Nachricht -------- Betreff: Hudson does not build anymore Datum: Tue, 22 Sep 2009 10:00:50 +0200 Von: Stefan Schubert <schubi(a)suse.de> An: YaST-devel <yast-devel(a)opensuse.org> Hi, since my last chances in translation Hudson reports errors while building packages. Sorry for that. I will take care .... Greetings Stefan -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi(a)suse.de ------------------------------------------------------------------------------- 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: [yast-commit] <rest-service> master : Switched to the InvalidParameters exception.
by Josef Reidinger 21 Sep '09

21 Sep '09

On Monday 21 September 2009 12:48:10 Martin Vidner wrote: > ref: refs/heads/master > commit 31a423025739c568c47ccd8a49faca381da583da > Author: Martin Vidner <mvidner(a)suse.cz> > Date: Mon Sep 21 12:18:07 2009 +0200 > > Switched to the InvalidParameters exception. > --- > .../app/controllers/network/dns_controller.rb | 2 +- > .../app/controllers/network/hostname_controller.rb | 2 +- > .../controllers/network/interfaces_controller.rb | 2 +- > .../app/controllers/network/routes_controller.rb | 2 +- > 4 files changed, 4 insertions(+), 4 deletions(-) > > diff --git a/plugins/network/app/controllers/network/dns_controller.rb > b/plugins/network/app/controllers/network/dns_controller.rb index > 810b7df..bcfe961 100644 > --- a/plugins/network/app/controllers/network/dns_controller.rb > +++ b/plugins/network/app/controllers/network/dns_controller.rb > @@ -11,7 +11,7 @@ class Network::DnsController < ApplicationController > def update > root = params[:dns] > if root == nil > - render ErrorResult.error(404, 2, "format or internal error") and > return + raise InvalidParameters.new [{:name => "Dns", :error => > "Missing"}] end > > root["searches"]=root["searches"].split > diff --git a/plugins/network/app/controllers/network/hostname_controller.rb > b/plugins/network/app/controllers/network/hostname_controller.rb index > cd85d66..86c51d3 100644 > --- a/plugins/network/app/controllers/network/hostname_controller.rb > +++ b/plugins/network/app/controllers/network/hostname_controller.rb > @@ -12,7 +12,7 @@ class Network::HostnameController < ApplicationController > def update > root = params[:hostname] > if root == nil > - render ErrorResult.error(404, 2, "format or internal error") and > return + raise InvalidParameters.new [{:name => "Hostname", :error => > "Missing"}] end > > @hostname = Hostname.new(root) > diff --git > a/plugins/network/app/controllers/network/interfaces_controller.rb > b/plugins/network/app/controllers/network/interfaces_controller.rb index > 5571039..a377a09 100644 > --- a/plugins/network/app/controllers/network/interfaces_controller.rb > +++ b/plugins/network/app/controllers/network/interfaces_controller.rb > @@ -11,7 +11,7 @@ class Network::InterfacesController < > ApplicationController def update > root = params[:interfaces] > if root == nil > - render ErrorResult.error(404, 2, "format or internal error") and > return + raise InvalidParameters.new [{:name => "Interfaces", :error > => "Missing"}] end > > @iface = Interface.new(root) > diff --git a/plugins/network/app/controllers/network/routes_controller.rb > b/plugins/network/app/controllers/network/routes_controller.rb index > 571d132..011620a 100644 > --- a/plugins/network/app/controllers/network/routes_controller.rb > +++ b/plugins/network/app/controllers/network/routes_controller.rb > @@ -11,7 +11,7 @@ class Network::RoutesController < ApplicationController > def update > root = params[:routes] > if root == nil > - render ErrorResult.error(404, 2, "format or internal error") and > return + raise InvalidParameters.new [{:name => "Routes", :error => > "Missing"}] end > @route = Route.find(root[:id]) > @route.via = root[:via] > Hi, just note, that you don't need set name to humanized string, I already do it, so just name parameter like if routes is not set, then you can set name to "routes" -- 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] user feedback for webyast
by Martin Vidner 21 Sep '09

21 Sep '09

(randy-sk in irc://irc.freenode.net/susecz) He installed it from YaST:Web, I helped him with https://bugzilla.novell.com/show_bug.cgi?id=538039#c4 - collectd is not working [he needed to start collectd] - I need to install termcap... did not help [he tried Users, did not work] Cannot find termcap: TERM not set at /usr/lib/perl5/5.10.0/Term/ReadLine.pm line 351 false Cannot find termcap: TERM not set at /usr/lib/perl5/5.10.0/Term/ReadLine.pm line 351 0 false 0 pali false pali 0 randy false randy 0 - it is mostly working. it is funny. it is only missing icons in the control panel [he means to launch webyast locally. I told him we don't want that] - pity that you can't install packages - getting the health status is slow. (I would understand patches being slow, but not this) - a log viewer would be useful [ ;-) ] -- 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

[yast-devel] WebYaST status, 2009-Sep-07
by Josef Reidinger 21 Sep '09

21 Sep '09

missing: duncan, daniel(public transport),mschidkunz (vacation) kkampf - moving things to bugzilla dmacvicar (reported by klaus) - log feature (highlight), vendor settings, review collectd (new version) schubi - working on package module mvidner - working on network ( provide available interfaces) mzugec - same as mvidner jsrain - no update jsuchome - no webyast related issues jreidinger - finishing basic system setup, start on setting time via ntp all - look at bugzilla and check if something is not clear -- 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

7 14

[yast-devel] Re: [yast-commit] <rest-service> master : more unit tests, exception handling
by josef reidinger 18 Sep '09

18 Sep '09

Jiri Suchomel napsal(a): > ref: refs/heads/master > commit 942d45274e1c9ca229bba8768436cced98d17e56 > Author: Jiri Suchomel <jsuchome(a)suse.cz> > Date: Fri Sep 18 09:41:46 2009 +0200 > > more unit tests, exception handling > --- > .../app/controllers/administrator_controller.rb | 2 +- > plugins/administrator/app/models/administrator.rb | 4 +- > .../administrator/test/unit/administrator_test.rb | 27 +++++++++++++++++++- > 3 files changed, 29 insertions(+), 4 deletions(-) > > diff --git a/plugins/administrator/app/controllers/administrator_controller.rb b/plugins/administrator/app/controllers/administrator_controller.rb > index 5a06f0a..3478c45 100644 > --- a/plugins/administrator/app/controllers/administrator_controller.rb > +++ b/plugins/administrator/app/controllers/administrator_controller.rb > @@ -37,7 +37,7 @@ class AdministratorController < ApplicationController > begin > @admin.save_aliases(data[:aliases]) > rescue Exception => e > - render ErrorResult.error(500, 2, e.message) and return > + render ErrorResult.error(404, 2, e.message) and return Please don't return 404 when error occure, this is quite confusing. I write separate mail about error handling when I mention it. If you use my second suggestion you don't need catch anything unless you want somehow rescue from it (which render is not). > end > end > show > diff --git a/plugins/administrator/app/models/administrator.rb b/plugins/administrator/app/models/administrator.rb > index 2327ebe..7580965 100644 > --- a/plugins/administrator/app/models/administrator.rb > +++ b/plugins/administrator/app/models/administrator.rb > @@ -35,7 +35,7 @@ class Administrator > new_aliases = "" if new_aliases.nil? || new_aliases == "NONE" > if @aliases.split(",").sort == new_aliases.split(",").sort > Rails.logger.debug "mail aliases have not been changed" > - return > + return true > end > parameters = { > "aliases" => ["as", new_aliases.split(",")] > @@ -43,7 +43,7 @@ class Administrator > yapi_ret = YastService.Call("YaPI::ADMINISTRATOR::Write", parameters) > Rails.logger.debug "YaPI returns: '#{yapi_ret}'" > > - raise yapi_ret unless yapi_ret.empty? > + raise Exception.new(yapi_ret) unless yapi_ret.empty? Don't raise anonymous exception, please use error handling feature and define own exception with proper handling. for example see how I handle response from NTP: http://git.opensuse.org/?p=projects/yast/rest-service.git;a=blob;f=plugins/… > @aliases = new_aliases > end > > diff --git a/plugins/administrator/test/unit/administrator_test.rb b/plugins/administrator/test/unit/administrator_test.rb > index 008977d..374b1d2 100644 > --- a/plugins/administrator/test/unit/administrator_test.rb > +++ b/plugins/administrator/test/unit/administrator_test.rb > @@ -6,6 +6,8 @@ class AdministratorTest < ActiveSupport::TestCase > > def setup > @model = Administrator.instance > + YastService.stubs(:Call).with('YaPI::ADMINISTRATOR::Read').returns({ "aliases" => [ "a@b" ] }) > + @model.read_aliases > end > > def test_save_password > @@ -15,7 +17,7 @@ class AdministratorTest < ActiveSupport::TestCase > end > > def test_read_aliases > - YastService.stubs(:Call).with('YaPI::ADMINISTRATOR::Read').returns({ "aliases" => [ "a@b" ] }) > + YastService.stubs(:Call).with('YaPI::ADMINISTRATOR::Read').returns({ "aliases" => [ "a(a)b.c" ] }) > ret = @model.read_aliases > assert ret > assert @model.aliases.split(",").size == 1 > @@ -29,4 +31,27 @@ class AdministratorTest < ActiveSupport::TestCase > assert @model.aliases.split(",").size == 2 > end > > + def test_save_empty_aliases > + new_aliases = "NONE" > + YastService.stubs(:Call).with('YaPI::ADMINISTRATOR::Write', {"aliases" => [ "as", [] ]}).returns("") > + ret = @model.save_aliases(new_aliases) > + assert ret > + assert @model.aliases.empty? > + end > + > + def test_save_failure > + new_aliases = [ "test(a)domain.com" ]; > + YastService.stubs(:Call).with('YaPI::ADMINISTRATOR::Write', {"aliases" => [ "as", new_aliases ]}).returns("YaPI error") > + assert_raise Exception do > + ret = @model.save_aliases(new_aliases.join(",")) > + end > + end > + > + def test_save_no_change > + new_aliases = [ "a@b" ]; > + ret = @model.save_aliases(new_aliases.join(",")) > + assert ret > + assert @model.aliases.split(",").size == 1 > + end > + > end -- 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] reverting the Yast icon in 11.2
by Jakub Steiner 18 Sep '09

18 Sep '09

Hi folks, I'd like to propose to revert the Yast launcher icon to the original wrench for usability reasons. This would be the first time we'd expose people to a cute little animal as an icon. Of course it's a chicken and egg problem setting up a brand. There are a few cases where building a brand for a product has preference over a clear metaphor giving insight on what the tool does. But I don't think it's the case with Yast. Yasti, the aardvark is a great mascot, perfect for conference swag. Exposing him everywhere it mentions Yast is a bad choice in my opinion. I don't think we aim for people on Fedora or Ubuntu to switch their configuration tools to YaST. We want people to switch to openSUSE. Our brand focus should be on openSUSE. I think it's best to revert back to the wrench for the icon. cheers -- Jakub Steiner <jimmac(a)gmail.com> http://jimmac.musichall.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] rest-service ResourcesController should be more RESTful
by Martin Kudlvasr 17 Sep '09

17 Sep '09

Hi, see http://bugzilla.novell.com/show_bug.cgi?id=539290 for introduction. Basically, we currently discover resources from interface using path like: /resources.xml?interface=org.opensuse.yast.modules.yapi.network this is not restful, so service_resource.rb circumvents this by always using "proxy.find :all" and then searching for the resource in the list (/resources.xml works well). Simply because "proxy.find 'org.opensuse.yast.modules.yapi.network'" does not work ("proxy" is a proxy for /resources). Goal: Make it work! Currently finding a single resource is not used, so we have a bit of freedom, when figuring that out. There are 2 problems: 1) /resources/org.opensuse.yast.modules.yapi.network is a problematic path, because "." is a format separator (for .xml, .json, ...). proposed solution: use dashes instead of dots in the URI. /resources/org-opensuse-yast-modules-yapi-network.xml We can say, that dashes cannot be part of interface name (thanks to mvidner for http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol- names). The interface name has to be transliterated, but this happens only once on server and once on client. 2) there can be more resources found for a single interface name. In current implementation, ResourcesController returns this for /resources.xml: <resources> <resource> <interface> ... </resource> ... </resources> and the same format for /resources.xml?interface=org.opensuse.yast.modules.yapi.network . Returning a list of items, where (according to ActiveResource) a single item is expected. ActiveResource has a problem with that. **imho optimal solution:** remake the xml format, so that single resource can contain several implementations (the same way it is in internal structures of rest- service/webservice/lib/resource_registration.rb). The format for /resources.xml can then look like this: <resources> <resource> <implementations> <implementation> <interface> ... </implementation> </implementations> </resource> ... </resources> with the same (but only single <resource>) for /resources/$interface_name.xml . By remaking the xml, service_resource.rb would have to be changed. I tried that and did not succeed. **proposed solution:** Make server return only single implementation/resource, when asked for a single interface. This would preserve current format of /resources.xml and work with ActiveResource mechanisms at the same time. The only thing that changes is, that server decides which implementation of resource is used by the client. Until now, this was decided in web-client by the rule "take first" (service_resource.rb:315). Both proposed solutions are implemented in resource-restful branch and pushed to git.opensuse.org. Please comment, if this can be merged, and say why, if not. Martin Kudlvasr -- 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 02-Sep-2009
by J. Daniel Schmidt 17 Sep '09

17 Sep '09

WebYaST 02-Sep-2009 =================== present: kkaempf, dmacvicar, schubi, mschmidkunz, jdsn, mzugec, mvidner, jsuchomel absent: jsrain, visnov, lslezak, fnadge Status: ----------- kkaempf: no progress due to a day off dmacvicar: error handling, see wiki page for details (and eMail on ML) http://en.opensuse.org/YaST/Web/Development/Error_Handling schubi: find a way for the customer to change setup (like theming paths) mschmidkunz: extended the styleguide (message boxes) jdsn: investigation for the registration module underlying perl module might be problematic to integrate in REST context mzugec: no progress due to L3 work plan to read system data via YaPI for network plugin mvidner: several fixes for tests (in own branch) not yet commited due to pending bugs jsuchomel: plan to do customizations for custom services plugin Ciao, Daniel -- J. Daniel Schmidt <jdsn(a)suse.de> SUSE Linux Products GmbH Research & Development Maxfeldstr. 5 GF: Markus Rex, HRB 16746 (AG Nürnberg) D-90409 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

[yast-devel] WebYaST build still failing
by Klaus Kaempf 17 Sep '09

17 Sep '09

Hi, building WebYaST on Hudson is failing since yesterday afternoon. Currently its a packaging bug in yast2-webclient-administrator. 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

1 0

[yast-devel] Installation server, tftp and netinstall
by Birger Kollstrand 16 Sep '09

16 Sep '09

Hi, I'm wondering if there is a possibility to do some adaptations to the "Installation server" module in 11.2? I would very much like to see that when I start the Installation Server module the first time that it asks for installtion of the tftp module. For a netinstall system the two are linked together. I use this kind of setup now when I'm testing openSUSE and its realy nifty to be able to select between a number of releases and being able to have it running in a few minutes by netinstalling with the relevant release. The next step would be to enhance the Instalation server module to: - edit the pxelinux.cfg/default config file with the new version to make available. below is a copy of my current netinstall config. DEFAULT pxelinux.cfg/vesamenu.c32 #DEFAULT OS11.1_32 PROMPT 0 MENU TITLE Birger's boot palace MENU BACKGROUND pxelinux.cfg/background.jpg #TIMEOUT 300 # Install i386 Linux LABEL OS11.1_32 kernel OS11.1_32/linux append initrd=OS11.1_32/initrd splash=silent vga=0x317 showopts install=ftp://10.0.0.2/distros/openSUSE11.1/CD1/ # Sub menu for x86_64 linux with different VGA modes MENU BEGIN OS11.1_64_sub LABEL OS11.1_64_0x317 kernel OS11.1_64/linux append initrd=OS11.1_64/initrd splash=silent vga=0x317 showopts install=ftp://10.0.0.2/distros/openSUSE11.1/CD1/ LABEL OS11.1_64_0x318 kernel OS11.1_64/linux append initrd=OS11.1_64/initrd splash=silent vga=0x318 showopts install=ftp://10.0.0.2/distros/openSUSE11.1/CD1/ LABEL OS11.1_64_0x323_Elitebook 6930p kernel OS11.1_64/linux append initrd=OS11.1_64/initrd acpi=off pnpbios=off splash=silent vga=0x323 showopts install=ftp://10.0.0.2/distros/openSUSE11.1/CD1/ LABEL OS11.1_64_0x31B_1280x1024 kernel OS11.1_64/linux append initrd=OS11.1_64/initrd splash=silent splash=silent vga=0x31B showopts install=ftp://10.0.0.2/distros/openSUSE11.1/CD1/ LABEL OS11.1_64_0x346 kernel OS11.1_64/linux append initrd=OS11.1_64/initrd splash=silent splash=silent vga=0x346 showopts install=ftp://10.0.0.2/distros/openSUSE11.1/CD1/ MENU END # Sub menu for x86_64 linux with different autoyast files MENU BEGIN OS11.1_64_autoyast LABEL OS11.1_64_homeserv kernel OS11.1_64/linux append initrd=OS11.1_64/initrd splash=silent vga=0x346 autoyast=ftp://10.0.0.192/distros/autoyast/homeserv_22_12_08.xml showopts install=ftp://10.0.0.192/distros/OS11.1_64/CD1/ LABEL OS11.1_64_0x318 kernel OS11.1_64/linux append initrd=OS11.1_64/initrd splash=silent vga=0x318 showopts install=ftp://10.0.0.192/distros/OS11.1_64/CD1/ LABEL OS11.1_64_0x346 kernel OS11.1_64/linux append initrd=OS11.1_64/initrd splash=silent splash=silent vga=0x346 showopts install=ftp://10.0.0.192/distros/OS11.1_64/CD1/ MENU END # Sub menu for 11.2 MENU BEGIN OS11.2 LABEL OS11.2MS5_32 kernel OS11.2MS5_32/linux append initrd=OS11.2MS5_32/initrd splash=silent showopts install=ftp://10.0.0.2/distros/openSUSE11.2MS5_32/CD1/ LABEL OS11.2MS5_64_0x346 kernel OS11.2MS5_64/linux append initrd=OS11.2MS5_64/initrd splash=silent splash=silent vga=0x346 showopts install=ftp://10.0.0.2/distros/openSUSE11.2MS5_64/CD1/ LABEL OS11.2MS5_32 kernel OS11.2MS5_32/linux append initrd=OS11.2MS5_32/initrd splash=silent showopts install=ftp://10.0.0.2/distros/openSUSE11.2MS5_32/CD1/ LABEL OS11.2MS5_64_0x346 kernel OS11.2MS5_64/linux append initrd=OS11.2MS5_64/initrd splash=silent splash=silent vga=0x346 showopts install=ftp://10.0.0.2/distros/openSUSE11.2MS5_64/CD1/ LABEL OS11.2MS6_32 kernel OS11.2MS6_32/linux append initrd=OS11.2MS6_32/initrd splash=silent showopts install=ftp://10.0.0.2/distros/openSUSE11.2MS6_32/CD1/ LABEL OS11.2MS6_64 kernel OS11.2MS6_64/linux append initrd=OS11.2MS6_64/initrd splash=silent splash=silent showopts install=ftp://10.0.0.2/distros/openSUSE11.2MS6_64/CD1/ LABEL OS11.2MS7_32 kernel OS11.2MS7_32/linux append initrd=OS11.2MS7_32/initrd splash=silent showopts install=ftp://10.0.0.2/distros/openSUSE11.2Build0268_32/CD1/ MENU END - and copy the initrd and linux file from the new image to the tftpserver directory. this looks like this on one of my servers now: linserve2:/srv/tftpboot # ls OS11.1_32 OS11.2MS5_32 OS11.2MS6_32 OS11.2MS7_32 pxelinux.cfg OS11.1_64 OS11.2MS5_64 OS11.2MS6_64 pxelinux.0 vesamenu.c32 :-) Much to ask for, but it would be lovely! It is really neat when I do installs on 5 computers at a time and with different version. cu / birger.... -- 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: how to pass empty string to rest-service?
by Jiří Suchomel 16 Sep '09

16 Sep '09

Hi, in administrator module I have a POST request from client that contains the information about root password and mail aliases. Sometimes I would like to pass an empty value (for mail aliases, to reset it to no alias) and to distinguish the empty value from nil (nil has a meaning do not try to save this, while empty means save empty). So, for example I have this object in webclient controller: @administrator.password = nil @administrator.aliases = "" and I'm calling POST with @administrator.save However, on the server part, I get this as parameters: {"format"=>"xml", "action"=>"create", "administrator"=>{"aliases"=>nil, "password"=>nil}, "controller"=>"administrator"} So both values are set to nil. When debugging, we saw that the RAW_POST_DATA has a value "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<administrator>\n <aliases></aliases>\n <password nil=\"true\"></password>\n</administrator>\n" which is converted by from_xml this way even if aliases tag looks differently from password tag: Hash.from_xml("<?xml?>\n<administrator>\n <aliases></aliases>\n <password nil=\"true\"></password>\n</administrator>\n") {"administrator"=>{"aliases"=>nil, "password"=>nil}} It would work if the request would contain <aliases type='string'></aliases> instead of <aliases></aliases>, however I don't know how to achieve this; using xml.aliases aliases, {:type => "string"} in models/administrator.rb's to_xml doesn't seem to help. Jiri -- Jiri Suchomel SUSE LINUX, s.r.o. e-mail: jsuchome(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Praha 9, 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 5

[yast-devel] WebYaST status, 2009-09-14
by Jiri Srain 16 Sep '09

16 Sep '09

present: kkaempf, dmacvicar, jdsn, schubi, mschmidkunz, mvidner, mzugec, jsrain kkaempf: - looking into patch model dmacvicar: - log module - refactoring the status controller, to be merged jdsn: - working on registration, YaPI interface - first working version ETA today (general registration working) schubi: - patch installation - should be able to install patch today or tomorrow mschmidkunz: - getting glimpse on what happened during FTO mvidner: - REST documentation of network WIP - will submit RPMs mzugec: - small progress in network - can configure default route + hostname, DNS in progress - interface setting - hopefully today jsuchome (via jsrain): - admin module basically working - TBD: testcases, docu -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 1

[yast-devel] Re: [yast-commit] <rest-service> network : Added a note to s/404/422/ in test_update_noparams.
by Josef Reidinger 15 Sep '09

15 Sep '09

Martin Vidner wrote: > ref: refs/heads/network > commit 95f714b375f3dadfb35060427a0280c8a9f04bc6 > Author: Martin Vidner <mvidner(a)suse.cz> > Date: Tue Sep 15 13:13:48 2009 +0200 > > Added a note to s/404/422/ in test_update_noparams. > --- > webservice/test/plugin_basic_tests.rb | 2 ++ > 1 files changed, 2 insertions(+), 0 deletions(-) > > diff --git a/webservice/test/plugin_basic_tests.rb b/webservice/test/plugin_basic_tests.rb > index f77ffb7..11907cd 100644 > --- a/webservice/test/plugin_basic_tests.rb > +++ b/webservice/test/plugin_basic_tests.rb > @@ -66,6 +66,8 @@ module PluginBasicTests > def test_update_noparams > @model_class.stubs(:save) > put :update > + # FIXME: it is not 404, but 422 unprocessable entity, > + # see "Validation errors" in http://api.rubyonrails.org/classes/ActiveResource/Base.html > assert_response :missing > end > Hi, I think that this is one of thinks when we should use our new error reporting in backend. So I prefer throwing exception where is defined what parameter is invalid or missing (due to rest service should be used without webclient). I prefer solution with exception because it provide better description of problem and also it is easier to handle in frontend. Any reason why not use exceptions? Josef -- 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] style guide add-on: module titles
by Martin Schmidkunz 15 Sep '09

15 Sep '09

Hi everybody, because of the recent version of webYaST it was necessary to add some lines about module titles into the style guide (http:// en.opensuse.org/YaST/Web/Docu/Style_Guide). Again: this is all to increase consistency and therefore the usability of webYaST. So, when you create a module title, please keep the following in mind: * Use title style for the module title. * Keep the title short and meaningful. * The module title is consistent with the module title in „Show All“ or "Home" page. * Do not use "Configure" or any other verb in the title. * If the module is used to configure a client, use the word "Client" in the title. * If the module is used to configure a server, use the word "Server" in the title. Thanks and have a nice week! Martin -- Crossmedialer Kontakt via: Martin Schmidkunz Forchheimer Str. 3 90542 Eckental Tel.: +499126/2090189 Mobil: +49176/80127858 ICQ: 457001671/Schmidi1803 --- Martin Schmidkunz User Experience Specialist mschmidkunz(a)novell.com +49 (0) 911 740 53-346 --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --- Novell® Making IT Work As One™

1 0

[yast-devel] Power Outage
by ml-admin＠opensuse.org 11 Sep '09

11 Sep '09

Broadcast message from ml-admin(a)opensuse.org (/dev/pts/0) at 07:30 GMT ... The system is going down for halt NOW! -- 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: Documenting REST API - findings
by Ladislav Slezak 10 Sep '09

10 Sep '09

Hi all, Currently we don't have any standard or guidelines how to document Yast REST API. Duncan sent me two links: Rapidoc ------- (http://code.google.com/p/rapidoc/) It generates on-line documentation (controller and view) which is part of the application. The API is documented in the code (inline). Unfortunately it needs quite a lot of changes (where to search for input files, where stote generated files) and the templates need to be modified for our needs. This seems be not a trivial task... Anyway, I like the fact that the documentation is provided by the REST server itself - the documentation is automatically available (no need to install extra packages or search the web) and there is no problem with versions, the documentation will (or should) always match the current API on the server. Vasco ----- (http://blog.thinkrelevance.com/2008/10/22/introducing-vasco-a-route-explore…) Actually this is not a documentation generator, but it provides a nice GUI to REST API (see the link). This would be a good tool for testing during development - you should be able to browse the available methods and even test them without need to code a frontend first. Unfortunately it didn't work for me, the page was empty telling me to run a rake task to collect the data even though it had been already called and the data file was present... I'd like to discuss the REST documentation problem with Karel tomorrow, maybe he knows better tools... BTW I found that twitter documentation might be a good example how a REST API documentation could look like and what it should contain. (See e.g. http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search) -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 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 7

[yast-devel] Documenting REST API using restility
by Ladislav Slezak 10 Sep '09

10 Sep '09

Hi all, I have integrated restility to WebYaST - restility is now available as a ruby gem (rubygem-restility) and there is a new rake task 'restdoc' which is called from 'package' task (the REST documentation is automatically generated during package build). If you want to check how it looks like then - install restility gem from YaST:Web repository [ well, the build has not been finished completely yet, e.g. FACTORY package still waits in the queue... :-( ] - update to the latest rest service from GIT - call 'rake restdoc' in plugins/system - restart the rest service (because of the new public/ overlay) - and finally point your browser to http://localhost:8080/system/restdoc/index.html You can look at plugins/system/restdoc/api.txt to see the source. (I'm going to write a wiki page how to create a REST documentation...) -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 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

3 2

[yast-devel] Re: [yast-commit] Build failed in Hudson: webyast-service-11.1-i586 #296
by Klaus Kaempf 10 Sep '09

10 Sep '09

* Hudson Integration Service <hudson(a)suse.de> [Sep 10. 2009 16:53]: > error: Failed build dependencies: > rubygem-restility is needed by yast2-webservice-0.0.3-0.noarch Can we postpone requiring rubygem-restility until after the power-down ? Else I guess the build will fail until next week. 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

1 0

[yast-devel] Howto prepare your module for base system settings
by Josef Reidinger 10 Sep '09

10 Sep '09

Hi, if your module should be used in base system sequence it needs little change. I describe it in wiki http://en.opensuse.org/YaST/Web/Development/Client It is just two lines changes that allows correct redirect and use different labels for form submit buttons. If you have any question I welcome it. jsuchome - administration should be used in basic system settings so please read it and add it to code, thanks. -- 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] Re: [yast-commit] <rest-service> master : call the real YaPI, update tests
by Josef Reidinger 10 Sep '09

10 Sep '09

Jiri Suchomel wrote: > ref: refs/heads/master > commit 61f65df178461f324728e5de041e91936a62d2b3 > Author: Jiri Suchomel <jsuchome(a)suse.cz> > Date: Thu Sep 10 16:07:16 2009 +0200 > > call the real YaPI, update tests > --- > .../app/controllers/administrator_controller.rb | 9 ++++++++- > plugins/administrator/app/models/administrator.rb | 20 ++++++++++++++++---- > .../administrator/test/unit/administrator_test.rb | 19 ++++++++++--------- > 3 files changed, 34 insertions(+), 14 deletions(-) > > diff --git a/plugins/administrator/app/controllers/administrator_controller.rb b/plugins/administrator/app/controllers/administrator_controller.rb > index 2542c4c..60b90e0 100644 > --- a/plugins/administrator/app/controllers/administrator_controller.rb > +++ b/plugins/administrator/app/controllers/administrator_controller.rb > @@ -4,7 +4,10 @@ class AdministratorController < ApplicationController > > # GET action > def show > -# @aliases = Administrator.instance.aliases > + unless permission_check("org.opensuse.yast.modules.yapi.administrator.read") > + render ErrorResult.error(403, 1, "no permission for reading") and return > + end > + Hi, new error reporting uses exceptions os for check if permission is set use just permission_check("org.opensuse.yast.modules.yapi.administrator.read") and because I create for yapi shortcut you can use just yapi_perm_check "administrator.read" > @admin = Administrator.instance > @aliases = @admin.read_aliases > > @@ -17,6 +20,10 @@ class AdministratorController < ApplicationController > > # PUT action > def update > + > + unless permission_check("org.opensuse.yast.modules.yapi.administrator.write") > + render ErrorResult.error(403, 1, "no permission for writing") and return > + end > > @admin = Administrator.instance > > diff --git a/plugins/administrator/app/models/administrator.rb b/plugins/administrator/app/models/administrator.rb > index c51bbf5..87186fd 100644 > --- a/plugins/administrator/app/models/administrator.rb > +++ b/plugins/administrator/app/models/administrator.rb > @@ -22,13 +22,25 @@ class Administrator > end > > def save_password(pw) > - Rails.logger.debug "--------------------- saving password #{pw}--------" > + parameters = { > + "password" => ["s", pw ] > + } > + yapi_ret = YastService.Call("YaPI::ADMINISTRATOR::Write", parameters) > + Rails.logger.debug "YaPI returns: '#{yapi_ret}'" > end > > def save_aliases(new_aliases) > - # TODO compare new_aliases with aliases > - Rails.logger.debug "--------------------- current aliases #{aliases.inspect}" > - Rails.logger.debug "--------------------- saving aliases #{new_aliases.inspect}" > + if @aliases.sort == new_aliases > + Rails.logger.debug "mail aliases have not been changed" > + return > + end > + parameters = { > + "aliases" => ["as", new_aliases] > + } > + yapi_ret = YastService.Call("YaPI::ADMINISTRATOR::Write", parameters) > + Rails.logger.debug "YaPI returns: '#{yapi_ret}'" > + > + raise yapi_ret unless yapi_ret.empty? > @aliases = new_aliases > end > > diff --git a/plugins/administrator/test/unit/administrator_test.rb b/plugins/administrator/test/unit/administrator_test.rb > index bff12ab..1e8ef08 100644 > --- a/plugins/administrator/test/unit/administrator_test.rb > +++ b/plugins/administrator/test/unit/administrator_test.rb > @@ -9,21 +9,22 @@ class AdministratorTest < ActiveSupport::TestCase > end > > def test_save_password > + YastService.stubs(:Call).with('YaPI::ADMINISTRATOR::Write', {"password" => ["s", "new password"]}).returns("") > ret = @model.save_password("new password") > assert ret > end > > -# def test_read_aliases > -# assert @model.aliases.size == 0 > -# YastService.stubs(:Call).with('YaPI::ADMINISTRATOR::Read').returns({ "aliases" => [ "a@b" ] }) > -# ret = @model.read_aliases > -# assert ret > -# assert @model.aliases.size == 1 > -# end > + def test_read_aliases > + YastService.stubs(:Call).with('YaPI::ADMINISTRATOR::Read').returns({ "aliases" => [ "a@b" ] }) > + ret = @model.read_aliases > + assert ret > + assert @model.aliases.size == 1 > + end > > def test_save_aliases > - assert @model.aliases.size == 0 > - ret = @model.save_aliases([ "test(a)domain.com", "a@b" ]) > + new_aliases = [ "test(a)domain.com", "a@b" ]; > + YastService.stubs(:Call).with('YaPI::ADMINISTRATOR::Write', {"aliases" => [ "as", new_aliases ]}).returns("") > + ret = @model.save_aliases(new_aliases) > assert ret > assert @model.aliases.size == 2 > 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] SLE-11 SP1 development, which svn branch?
by Ralf Haferkamp 10 Sep '09

10 Sep '09

Hi, will there be a special development branch in svn for SP1 features? If not, which branch should SP1 features go to? -- regards, Ralf -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1