September 2009 - YaST Development - openSUSE Mailing Lists

[yast-devel] use-activeresource: continuation
by Martin Kudlvasr 12 Oct '09

12 Oct '09

Hi, I've been continuing with the work, which Martin Vidner and Karel started 2 weeks ago - trying to use ActiveResource without service_resource.rb . This is currently the "use-activeresource" branch. I've added support for discovering controller paths from interface name. So currently there are no hard coded controller paths. Previously resources were used like this: *** Example from network_controller.rb *** hn = load_proxy "org.opensuse.yast.modules.yapi.network.hostname" *** Now they can be used like this: *** plugins/network/app/model/hostname.rb *** class Hostname < YastResource uses_interface "org.opensuse.yast.modules.yapi.network.hostname" end *** Example from network_controller.rb *** Hostname.initialize_from_interface hn = Hostname.find :one *** I think, that: - this newer approach better follows the MVC philosophy (with service_resource.rb, no model class is possible) - the YastResource < ActiveResource class is much shorter and more readable - individual model classes can be enriched by resource-specific methods - YastResource and individual models are not created dynamically - and so are easier to test (in contrast with service_resource.rb) - test can be made for the model. Currently we depend on tests in controller. - it is Black Magic Free (TM) :-) Please note, that "use-activeresource" branch depends on "resource-restful" branch, because it needs to discover individual resources (which is not possible with current "/resources" on web-service). This work was done to show, that there are other (and many think better) approaches to the problem than dynamic creation of classes in service_resource.rb. So I especially ask Duncan and Klaas, what other problems service_resource solves and YastResource does not. Please let me know what you think. Martin Kudlvasr -- 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] appliance status
by Martin Vidner 05 Oct '09

05 Oct '09

VM: - I have appliance #202, sized 1GB - if you want access, I need to share a browser session with you and add your openid (which is NOT used by another istudio account) to my account - or download http://istudio.suse.de/download/8e499474d56157c0b46b041762fc1c5b/WebYaST_on… Webyast: - REST runs on port 443 so that it is accessible from outside the test drive - this fix is needed: (%post only migrates in development env.) cd /srv/www/yastws su yastws -s /bin/sh -c 'RAILS_ENV=production rake db:migrate' rcyastws restart - collectd does not run and complains about fqdn lookup, a fix is easy Next: - add mising webservice rpms, fix dependencies -- 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

8 20

[yast-devel] WebYaST status call 25-Sep-2009
by Ladislav Slezak 05 Oct '09

05 Oct '09

WebYaST call 25-Sep-2009 kkaempf, jsrain, lslezak, mzugec, jreidinger Status update - kkaempf: DBus service mocking - jsrain: no update - lslezak: admin config - fixed input validation - mzugec: network - data validation - jreidinger: bugfixes, build fixes -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 4

[yast-devel] Re: [yast-commit] <rest-service> master : yast2-webservice.spec - fixed yast2-core requires
by josef reidinger 01 Oct '09

01 Oct '09

Ladislav Slezak napsal(a): > ref: refs/heads/master > commit f7da8445fb1e5e934ce6d88e12f9a5b9e6f714f1 > Author: Ladislav Slezak <lslezak(a)novell.com> > Date: Wed Sep 30 18:10:41 2009 +0200 > > yast2-webservice.spec - fixed yast2-core requires > > - requires yast2-core >= 2.18.10 in Factory and > yast2-core >= 2.17.31 in SLE11 > --- > webservice/package/yast2-webservice.spec | 11 ++++++++++- > 1 files changed, 10 insertions(+), 1 deletions(-) > > diff --git a/webservice/package/yast2-webservice.spec b/webservice/package/yast2-webservice.spec > index b018153..b67d1a8 100644 > --- a/webservice/package/yast2-webservice.spec > +++ b/webservice/package/yast2-webservice.spec > @@ -10,7 +10,16 @@ > > > Name: yast2-webservice > -Requires: yast2-core >= 2.18.10, lighttpd-mod_magnet, ruby-fcgi, ruby-dbus, sqlite > + > +%if 0%{?suse_version} == 0 || %suse_version > 1110 > +# 11.2 or newer > +Requires: yast2-core >= 2.18.10 > +%else > +# 11.1 or SLES11 > +Requires: yast2-core >= 2.17.31 > +%endif > + > +Requires: lighttpd-mod_magnet, ruby-fcgi, ruby-dbus, sqlite > Requires: rubygem-yast2-webservice-tasks > Recommends: avahi-utils > Requires: yast2-dbus-server ^^^^ Hi, yast2-dbus-server is also on SLE11? I think that in factory is dbus splitted, but SLE11 has it in one package. Josef -- 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] WebYaST packages building
by Jiri Srain 30 Sep '09

30 Sep '09

Hi! We have inconsistencies in the WebYaST build (see details below (*)). In order to move forward, we need to have the package versions consistent. Therefore I suggest: - keep the webyast-specific packages the same for both build targets (as it is now); just ensure proper dependencies of the packages (see http://lists.opensuse.org/yast-devel/2009-09/msg00123.html) - use Factory (without modifications) yast2 packages to build against Factory - for SLE11 use the Code11-SP1 branch in the YaST SVN and submit the packages to YaST:Web enabling build only for SLE11. Any comments? Jiri (*) Currently, yast2-network is still not building in the YaST:Web (resp. Devel:WebYaST) repository for SLE11, some packages are failing to build against Factory. yast2-network is currently failing in initializing the build system because of conflict between yast2-2.18 and yast2-installation-2.17. The classic YaST packages with API for WebYaST, which are in the repo, are mostly coming from the SVN trunk (2.18), however, not all of YaST are there. This results in an incompatible mix of SLE11 and 11.2 packages in the buildsystem. -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 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

2 4

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

30 Sep '09

* Hudson Integration Service <hudson(a)suse.de> [Sep 30. 2009 13:40]: > See http://yast.suse.de:3334/job/webyast-service-11.1-i586/378/ I've re-opened bnc#542845 to track this now. Any help appreciated. 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] WebYaST: My status for today
by Klaus Kaempf 30 Sep '09

30 Sep '09

Hi, I've catched a cold and will stay at home for today. As I won't be able to attend our WebYaST call, here's my status. Exec summary: We haven't reached our goal yet. AI, everyone: Get your packages to build and install. Schubi did a great job yesterday in submitting packages, but we still have e.g. file conflicts. - External buildservice (OBS) is slow, so we moved to the internal one (IBS) -> See https://wiki.innerweb.novell.com/index.php/Build_Service/Internal on how to use it - The internal project is Devel:WebYaST and linked to YaST:Web, so we can continue to check into OBS. - Hudson, our test and build server, still has problems in completing a build. -> Submit your packages directly to OBS - The Hudson setup is still a mystery. Although the test and build succeeds, Hudson reports failure. - Coverage testing crashed with an internal rcov error. I've added rubygem-rcov-0.9.3 to YaST:Web and changed the buildroot on Hudson accordingly. - Current problem: Systemtime(s) test failing. All issues are tracked in Bugzilla (product 'openSUSE 11.2', component 'WebYaST'). 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] yast2 package and SLES11
by Stefan Schubert 29 Sep '09

29 Sep '09

Hi, ich have tried to build the version yast2-2.18.26 on SLES11 and have gotten missing directories. After I have changed the spec file manually it has build. Has anyone an idea why these directories are not available on SLES11 ? Greetings Stefan Index: yast2.spec =================================================================== --- yast2.spec (revision 12) +++ yast2.spec (working copy) @@ -219,17 +219,17 @@ %doc %{prefix}/share/doc/packages/yast2/autodocs %doc %{prefix}/share/doc/packages/yast2/commandline -%doc %{prefix}/share/doc/packages/yast2/control +#%doc %{prefix}/share/doc/packages/yast2/control %doc %{prefix}/share/doc/packages/yast2/cron %doc %{prefix}/share/doc/packages/yast2/cwm %doc %{prefix}/share/doc/packages/yast2/desktop %doc %{prefix}/share/doc/packages/yast2/gpg %doc %{prefix}/share/doc/packages/yast2/log -%doc %{prefix}/share/doc/packages/yast2/network +#%doc %{prefix}/share/doc/packages/yast2/network %doc %{prefix}/share/doc/packages/yast2/packages %doc %{prefix}/share/doc/packages/yast2/runlevel %doc %{prefix}/share/doc/packages/yast2/sequencer %doc %{prefix}/share/doc/packages/yast2/system %doc %{prefix}/share/doc/packages/yast2/types %doc %{prefix}/share/doc/packages/yast2/wizard -%doc %{prefix}/share/doc/packages/yast2/xml +#%doc %{prefix}/share/doc/packages/yast2/xml -- 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] JFYI: Ruby/Rails screencasts and conference recorgings
by Jiri Srain 29 Sep '09

29 Sep '09

Hi! I updated the WebYaST learning page and added links to Ruby/Rails screencasts and conference reconrdings which I got from our local consultant. Hope that helps, Jiri http://en.opensuse.org/YaST/Web/Development/TrainingKit#General_knowledge_f… -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 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: Submit packages manually to OBS !
by Klaus Kaempf 29 Sep '09

29 Sep '09

Hi, Hudson, our integration testing tool, still has troubles submitting packages to the build service. Since the inner workings of this beast are a complete mystery, I do not want to lose further time by depending on it. Stefan will now submit all WebYaST packages to the build service. After that, the respective package maintainers are responsible for regular submissions to obs. 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] UI workflow network during first boot
by Martin Schmidkunz 29 Sep '09

29 Sep '09

Hi, please find a first idea of network UI workflow during first boot at: http://en.opensuse.org/YaST/Web/Docu/Workflow_Network_Firstboot Thanks, Martin --- 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™ -- 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] <web-client> network : correctly handle netmask/prefixlen (bnc#539889)
by josef reidinger 28 Sep '09

28 Sep '09

Michal Zugec napsal(a): > ref: refs/heads/network > commit 409cd7667168c6d03628ef0cc3b78f1fb280a54f > Author: Michal Zugec <mzugec(a)suse.cz> > Date: Mon Sep 28 21:56:38 2009 +0200 > > correctly handle netmask/prefixlen (bnc#539889) > --- > .../network/app/controllers/network_controller.rb | 16 +++++----------- > 1 files changed, 5 insertions(+), 11 deletions(-) > > diff --git a/plugins/network/app/controllers/network_controller.rb b/plugins/network/app/controllers/network_controller.rb > index 65c8f46..8c82060 100644 > --- a/plugins/network/app/controllers/network_controller.rb > +++ b/plugins/network/app/controllers/network_controller.rb > @@ -50,26 +50,20 @@ class NetworkController < ApplicationController > ipaddr = "-/-" > end > @ip, @netmask = ipaddr.split "/" > - > + # when detect PREFIXLEN with leading "/" > + @netmask = "/"+@netmask if ifc.bootproto == "static" && @netmask.to_i >= 0 && @netmask.to_i <= 32 ^^^ I think that this complex condition should be in separated if statement. This version is not much readable. I suggest use constant for netmask and test range. Somethink like: NETMASK_RANGE = 0..32 if ifc.bootproto == "static" && NETMASK_RANGE.include?(netmask.to_i) @netmask = "/"+@netmask end > + > @name = hn.name > @domain = hn.domain > @nameservers = dns.nameservers > @searchdomains = dns.searches > @default_route = rt.via > - #FIXME: this is ugly and keys are duplicated, but otherwise seems it doesn't work > - @conf_modes = [["",""], ["static","static"], ["dhcp", "dhcp"]] > - # if unknown item, just add it into list > - found = false > - @conf_modes.each {|a| found=true if a[0] == @conf_mode} > - @conf_modes << [@conf_mode, @conf_mode] if !found > + @conf_modes = {""=>"", _("static")=>"static", _("dhcp")=>"dhcp"} > + @conf_modes[@conf_mode] ||=@conf_mode Hi, you mix two sollution which I suggest to you and this doesn't work For example you have static...translated to cz is staticky and on second line you test if exist @conf_modes["static"] but you have @conf_mode["staticky"] so this is not produce valid output. As I suggest revert this hash (so conf_mode is keys and localized strings is values) and in options_for use @conf_modes.invert. When I come to work we should look at it together. > > end > > > - # GET /users/1/edit > - def edit > - end > - > > # PUT /users/1 > # PUT /users/1.xml -- 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] Building WebYaST packages locally
by Klaus Kaempf 28 Sep '09

28 Sep '09

Hi, at http://en.opensuse.org/YaST/Web/Development/Packaging you can now find a page describing how to build WebYaST packages locally. Enjoy ! 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] Re: [yast-commit] <rest-service> master : small fixes to restfull resource
by Josef Reidinger 25 Sep '09

25 Sep '09

Martin Kudlvasr write: > ref: refs/heads/master > commit aa80f8228d1d0d9cd349a7b0d2f054b0138e67ed > Author: Martin Kudlvasr <mkudlvasr(a)suse.cz> > Date: Tue Sep 15 16:15:15 2009 +0200 > > small fixes to restfull resource > --- > webservice/app/controllers/resources_controller.rb | 14 ++++++-------- > webservice/app/models/resource.rb | 10 ++++++++-- > webservice/app/views/resources/index.html.erb | 5 ++--- > webservice/app/views/resources/show.html.erb | 4 ++-- > webservice/config/routes.rb | 3 ++- > 5 files changed, 20 insertions(+), 16 deletions(-) > > diff --git a/webservice/app/controllers/resources_controller.rb > b/webservice/app/controllers/resources_controller.rb index > 087010a..ae90e04 100644 > --- a/webservice/app/controllers/resources_controller.rb > +++ b/webservice/app/controllers/resources_controller.rb > @@ -3,23 +3,21 @@ class ResourcesController < ApplicationController > > def index > @resources = Resource.all > + do_respond > + end > + > + def do_respond > @node = "Yast" > > - logger.debug("Ahoj!") > - debugger > respond_to do |format| > format.html > format.xml { render :xml => @resources.to_xml } > + format.json{ render :json=> @resources.to_json} > end > end > > def show > @resources = Resource.find(params[:id]) > - @node = "Yast" > - > - respond_to do |format| > - format.html > - format.xml { render :xml => @resources.to_xml } > - end > + do_respond > end > end > diff --git a/webservice/app/models/resource.rb > b/webservice/app/models/resource.rb index 8cd8b1e..417ec2b 100644 > --- a/webservice/app/models/resource.rb > +++ b/webservice/app/models/resource.rb > @@ -7,6 +7,8 @@ class Resource > attr_accessor :implementations > > class Implementation > + attr_accessor :controller, :interface > + > def initialize(interface, impl_hash) > @interface = interface > @policy = impl_hash[:policy] > @@ -15,18 +17,22 @@ class Resource > end > > def link_to > - "/#{@controller}/#{@singular ? "show" : "index"}" > + "/#{@controller}/#{action}" ^^^ This is root of actual problems. It is not true, that route is controller. It is not how is routes created in lib/resource_registration. So this two values dismatch and all plugin that have different last identifier from interface and controller name is broken. (now systemtime plugin) -- 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] Webyast - Serious problem with backend routing
by Josef Reidinger 25 Sep '09

25 Sep '09

Hi, I think it is related to last mkudlvasr changes, but he maybe just fix something which open Pandora box. So where is problem - backend create routes based on interace last item (so from org.opensuse.yast.modules.YaPI.time it create /time route). Problem is that for systemtime controller name is systemtime route which expect another part of code from resource_service. So I ended up with non-working frontend because proxy_for return me /systemtimes path but on backend is registered /time path. I create test case and send it to git. So now git is broken, but I think it is better then created broken package. -- 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 on SLE11: no ruby-fcgi
by Martin Vidner 25 Sep '09

25 Sep '09

Hi, I have tried installing from RPMs on SLE11, and now I have another thing to consider when choosing our webserver: the availability of SLE packages. So far I miss - lighttpd-mod_magnet (in OBS server:http SLE_11) - ruby-fcgi (no build for SLE_11) If we do want a provisional demo on SLE11, I suggest using an available OBS repo (for mod_magnet) or copying the package (ruby-fcgi) to YaST:Web with a fat note like PROVISIONAL, NOT IN SLE, REPLACE WITH SOMETHING SUPPORTABLE Sorry, I will not have time to fix this, I am on vacation from Friday to Tuesday. -- 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

2 1

[yast-devel] SuSE-Code-11-SP1-Branch created
by Martin Vidner 25 Sep '09

25 Sep '09

Hi, >From SuSE-Code-11-Branch r58747 (which should have only SLE11 maintenance updates) I have branched SuSE-Code-11-SP1-Branch. The changes in the SP1-Stash (there are 80 of them BTW) will be merged soon by jsrain. As always, please refer to http://en.opensuse.org/YaST/Development/SVN_branches -- 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

2 1

[yast-devel] Re: [yast-commit] <web-client> network : for configuration mode use combo box (bnc#540229)
by josef reidinger 24 Sep '09

24 Sep '09

Michal Zugec napsal(a): > ref: refs/heads/network > commit da9fb271b2b1b5b2885702cc7a2ca1261da29664 > Author: Michal Zugec <mzugec(a)suse.cz> > Date: Thu Sep 24 19:23:44 2009 +0200 > > for configuration mode use combo box (bnc#540229) > --- > .../network/app/controllers/network_controller.rb | 8 +++++++- > plugins/network/app/views/network/index.html.erb | 2 +- > 2 files changed, 8 insertions(+), 2 deletions(-) > > diff --git a/plugins/network/app/controllers/network_controller.rb b/plugins/network/app/controllers/network_controller.rb > index 29c2f74..65c8f46 100644 > --- a/plugins/network/app/controllers/network_controller.rb > +++ b/plugins/network/app/controllers/network_controller.rb > @@ -56,7 +56,13 @@ class NetworkController < ApplicationController > @nameservers = dns.nameservers > @searchdomains = dns.searches > @default_route = rt.via > - > + #FIXME: this is ugly and keys are duplicated, but otherwise seems it doesn't work ^^^^^^ If you properly read how options for select works you understand why it is. You can read it here -> http://api.rubyonrails.org/classes/ActionView/Helpers/FormOptionsHelper.htm… > + @conf_modes = [["",""], ["static","static"], ["dhcp", "dhcp"]] so you can change it to hash version or use array, but translate it ;) @conf_modes = {""=>"", _("static") =>"static", _("dhcp") => "dhcp"} # disclaimer - writed without try, so maybe it can be buggy, just for demonstration ;) > + # if unknown item, just add it into list > + found = false > + @conf_modes.each {|a| found=true if a[0] == @conf_mode} > + @conf_modes << [@conf_mode, @conf_mode] if !found change to: @conf_modes[@conf_mode]=@conf_mode unless @conf_modes.has_value(@conf_mode) #warning, unknown mode is not translated, at least log it > + > end > > > diff --git a/plugins/network/app/views/network/index.html.erb b/plugins/network/app/views/network/index.html.erb > index 50a20b1..104d2e4 100644 > --- a/plugins/network/app/views/network/index.html.erb > +++ b/plugins/network/app/views/network/index.html.erb > @@ -34,7 +34,7 @@ > </tr> > <tr> > <td class="first" width="120"><strong><%=_("Configuration Mode")%></strong></td> > - <td class="last"><%=text_field_tag :conf_mode, @conf_mode, :disabled => disabled %></td> > + <td class="last"><%= select_tag(:conf_mode, options_for_select(@conf_modes, @conf_mode), :disabled => disabled)%></td> > </tr> > <tr> > <td class="first" width="120"><strong><%=_("IP Address")%></strong></td> If you have any question, you can ask me tomorrow. Josef -- 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] r58757 - in /trunk/registration/src: config/org.opensuse.yast.modules.yapi.ysr.policy modules/YSR.pm_web
by josef reidinger 24 Sep '09

24 Sep '09

jdsn(a)svn.opensuse.org napsal(a): > Author: jdsn > Date: Thu Sep 24 18:51:20 2009 > New Revision: 58757 > > URL: http://svn.opensuse.org/viewcvs/yast?rev=58757&view=rev > Log: > files for webyast support - not yet included > > Added: > trunk/registration/src/config/org.opensuse.yast.modules.yapi.ysr.policy > trunk/registration/src/modules/YSR.pm_web > > Added: trunk/registration/src/config/org.opensuse.yast.modules.yapi.ysr.policy > URL: http://svn.opensuse.org/viewcvs/yast/trunk/registration/src/config/org.open… > ============================================================================== > --- trunk/registration/src/config/org.opensuse.yast.modules.yapi.ysr.policy (added) > +++ trunk/registration/src/config/org.opensuse.yast.modules.yapi.ysr.policy Thu Sep 24 18:51:20 2009 > @@ -0,0 +1,20 @@ > +<?xml version="1.0" encoding="UTF-8"?> > +<!DOCTYPE policyconfig PUBLIC "-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN" > + "http://www.freedesktop.org/standards/PolicyKit/1.0/policyconfig.dtd"> > + > +<policyconfig> > + <vendor>Novell, Inc.</vendor> > + <vendor_url>http://www.novell.com</vendor_url> > + > + <action id="org.opensuse.yast.modules.yapi.ysr.stateless_register"> > + <description>Run a registration in stateless context.</description> > + <message>Could not run YSR.stateless_register.</message> > + <defaults> > + <allow_any>no</allow_any> > + <allow_inactive>no</allow_inactive> > + <allow_active>auth_admin_keep_session</allow_active> > + </defaults> > + </action> > + > +</policyconfig> > + > > Added: trunk/registration/src/modules/YSR.pm_web > URL: http://svn.opensuse.org/viewcvs/yast/trunk/registration/src/modules/YSR.pm_… > ============================================================================== > --- trunk/registration/src/modules/YSR.pm_web (added) > +++ trunk/registration/src/modules/YSR.pm_web Thu Sep 24 18:51:20 2009 > @@ -0,0 +1,308 @@ > +# > +# Copyright (c) 2008 SUSE LINUX Products GmbH. All rights reserved. > +# > +# Author: Michael Calmer <mc(a)suse.de>, 2008 > +# Editor: J. Daniel Schmidt <jdsn(a)suse.de>, 2008,2009 > +# > +# YSR.pm - interface for YaST to interact with SUSE::SuseRegister > +# > + > +package YSR; > + > +use strict; > +use SUSE::SuseRegister; > +use Data::Dumper; > + > +use YaPI; > + > +our %TYPEINFO; > + > +my $global_ctx = {}; > + > + > +BEGIN { $TYPEINFO{init_ctx} = ["function", "void", [ "map", "string", "any"]]; } > +sub init_ctx > +{ > + my $self = shift; > + my $data = shift; > + > + if(defined $global_ctx && ref($global_ctx) eq "HASH" && exists $global_ctx->{debug}) > + { > + # ctx is initialized; clean it before we re-init it > + $self->del_ctx(); > + } > + > + $global_ctx = SUSE::SuseRegister::init_ctx($data); > +} > + > +BEGIN { $TYPEINFO{del_ctx} = ["function", "void"]; } > +sub del_ctx > +{ > + my $self = shift; > + > + if(defined $global_ctx && ref($global_ctx) eq "HASH" && exists $global_ctx->{debug}) > + { > + # only call del_ctx if it is initialized > + SUSE::SuseRegister::del_ctx($global_ctx); > + } > + > + $global_ctx = {}; > +} > + > +BEGIN { $TYPEINFO{get_errorcode} = [ "function", "integer"]; } > +sub get_errorcode > +{ > + my $self = shift; > + > + return $global_ctx->{errorcode}; > +} > + > +BEGIN { $TYPEINFO{get_errormsg} = [ "function", "string"]; } > +sub get_errormsg > +{ > + my $self = shift; > + > + return $global_ctx->{errormsg}; > +} > + > +BEGIN { $TYPEINFO{listParams} = ["function", "string"]; } > +sub listParams > +{ > + my $self = shift; > + > + return SUSE::SuseRegister::listParams($global_ctx); > +} > + > +BEGIN { $TYPEINFO{register} = ["function", "integer"]; } > +sub register > +{ > + my $self = shift; > + > + my $ret = SUSE::SuseRegister::register($global_ctx); > + > + return $ret; > +} > + > +BEGIN { $TYPEINFO{getTaskList} = ["function", [ "map", "string", "any"] ]; } > +sub getTaskList > +{ > + my $self = shift; > + > + return SUSE::SuseRegister::getTaskList($global_ctx); > +} > + > +BEGIN { $TYPEINFO{get_args} = [ "function", [ "map", "string", ["map", "string", "string"]]]; } > +sub get_args > +{ > + my $self = shift; > + > + return $global_ctx->{args}; > +} > + > +BEGIN { $TYPEINFO{set_args} = [ "function", "void", [ "map", "string", ["map", "string", "string"]]]; } > +sub set_args > +{ > + my $self = shift; > + my $args = shift; > + > + if(defined $args && ref($args) eq "HASH") > + { > + $global_ctx->{args} = $args; > + } > +} > + > +BEGIN { $TYPEINFO{set_arg} = [ "function", "void", "string", [ "map", "string", "string"]]; } > +sub set_arg > +{ > + my $self = shift; > + my $key = shift; > + my $value = shift; > + > + if(defined $key && $key ne "") > + { > + if(defined $value && ref($value) eq "HASH" ) > + { > + $global_ctx->{args}->{key} = $value; > + } > + else > + { > + delete $global_ctx->{args}->{key}; > + } > + } > +} > + > +BEGIN { $TYPEINFO{get_manualURL} = [ "function", "string"]; } > +sub get_manualURL > +{ > + my $self = shift; > + > + return $global_ctx->{registerManuallyURL}; > +} > + > +BEGIN { $TYPEINFO{get_registerReadableText} = [ "function", "string"]; } > +sub get_registerReadableText > +{ > + my $self = shift; > + > + return join('', @{$global_ctx->{registerReadableText}}); > +} > + > +BEGIN { $TYPEINFO{get_registerPrivPol} = [ "function", "string"]; } > +sub get_registerPrivPol > +{ > + my $self = shift; > + > + return $global_ctx->{registerPrivPol}; > +} > + > +BEGIN { $TYPEINFO{saveLastZmdConfig} = [ "function", ["list", "any"]]; } > +sub saveLastZmdConfig > +{ > + my $self = shift; > + > + return SUSE::SuseRegister::saveLastZmdConfig($global_ctx); > +} > + > +BEGIN { $TYPEINFO{set_proxy} = ["function", "void", "string", "string"]; } > +sub set_proxy > +{ > + my $self = shift; > + my $http_proxy = shift; > + my $https_proxy = shift; > + > + if(defined $http_proxy && $http_proxy =~ /^http/) > + { > + $ENV{http_proxy} = $http_proxy; > + } > + > + if(defined $https_proxy && $https_proxy =~ /^http/) > + { > + $ENV{https_proxy} = $https_proxy; > + } > +} > + > + > +BEGIN { $TYPEINFO{stateless_register} = ["function", [ "map", "string", "any"], ["map", "string", "any"] ]; } > +sub stateless_register > +{ > + my $self = shift; > + my $args = shift; > + > +#return { 'msg' => '4711' }; > + > + unless ( defined $args && ref($args) eq "HASH" ) > + { > + print "args is not a hash in YSR::statless_register. This is a bug. Please report this error.\n"; > + #return { 'error' => 'The call of the registration failed because of missing arguments.' } > + return { 'error' => { 'args' => 'The call of the registration failed because of missing arguments.' } }; > + } > + > +#return { 'msg' => '4712' }; > + # check if the system is still initialized - otherwise run init_ctx again > + unless ( defined $global_ctx && ref($global_ctx) eq "HASH" && exists $global_ctx->{debug} ) > + { > + # not initialized - need to reinitialize > + > +#return { 'msg' => '4713' }; > + # 1. proxy > + if ( exists $args->{'proxy'} && ref($args->{'proxy'}) eq "HASH" ) > + { > + my $http = $args->{'proxy'}{'http_proxy'} || undef; > + my $https = $args->{'proxy'}{'https_proxy'} || undef; > + $self->set_proxy($http, $https); > + } > + > +#return { 'msg' => '4714' }; > + # 2. registration context > + if ( exists $args->{'ctx'} && $args->{'ctx'} eq "HASH" ) > + { > + $self->init_ctx($args->{'ctx'}); > + my $init_err = $self->get_errorcode(); > + > + unless ($init_err == 0) > + { > + # init failed > + return { 'error' => { 'init' => 'The initialization of the registration failed.' } }; > + } > + } > + else > + { > +#return { 'msg' => '4715' }; > + # context is broken - return error message > + return { 'error' => { 'ctx' => 'The context for the registration is invalid.' } }; > + } > + } > + > + return { 'success' => { 'msg' => 'This is the return string.' } }; > + > +} > + > +1; > + > +############################################################################# > +############################################################################# > +# > +# internal functions that should not be used directly by YaST (to prevent zypp deadlocks) > +# they are here for documentation purposes or future use > +# > + > +# BEGIN { $TYPEINFO{get_ctx} = ["function", [ "map", "string", "any"]]; } > +# sub get_ctx > +# { > +# my $self = shift; > + > +# return $global_ctx; > +# } > + > +# BEGIN { $TYPEINFO{manageUpdateSources} = ["function", "void", [ "map", "string", "any"] ]; } > +# sub manageUpdateSources > +# { > +# my $self = shift; > + > +# return SUSE::SuseRegister::manageUpdateSources($global_ctx); > +# } > + > + > +# BEGIN { $TYPEINFO{addService} = ["function", ["list", "any"], [ "map", "string", "any"], [ "map", "string", "any"]]; } > +# sub addService > +# { > +# my $self = shift; > +# $global_ctx = shift; > +# my $service = shift || undef; > + > +# return SUSE::SuseRegister::addService($global_ctx, $service); > +# } > + > + > +# BEGIN { $TYPEINFO{enableCatalog} = ["function", ["list", "any"], [ "map", "string", "any"], "string", [ "map", "string", "string"]]; } > +# sub enableCatalog > +# { > +# my $self = shift; > +# $global_ctx = shift; > +# my $name = shift || undef; > +# my $catalog = shift || undef; > + > +# return SUSE::SuseRegister::enableCatalog($global_ctx, $name, $catalog); > +# } > + > +# BEGIN { $TYPEINFO{deleteService} = ["function", ["list", "any"], [ "map", "string", "any"], [ "map", "string", "any"]]; } > +# sub deleteService > +# { > +# my $self = shift; > +# $global_ctx = shift; > +# my $service = shift || undef; > + > +# return SUSE::SuseRegister::deleteService($global_ctx, $service); > +# } > + > +# BEGIN { $TYPEINFO{disableCatalog} = ["function", ["list", "any"], [ "map", "string", "any"], "string", [ "map", "string", "string"]]; } > +# sub disableCatalog > +# { > +# my $self = shift; > +# $global_ctx = shift; > +# my $name = shift || undef; > +# my $catalog = shift || undef; > + > +# return SUSE::SuseRegister::disableCatalog($global_ctx, $name, $catalog); > +# } > + > Hi, I think it is not good idea to add to YaPI methods which doesn't have defined permissions. You can add this function to internal function without exporting signature or add to permissions list. (these methods is placed to dbus service, but you have problems to get this permissions) Josef -- 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] on webyast local builds
by Martin Kudlvasr 24 Sep '09

24 Sep '09

Hi, well, that was quick. When finding out how to make local build work (because packages from other projects are needed), I have found out that they actually DO work! In particular packages from devel:languages:ruby:extensions are used in the build by default and without any problem. # osc meta prj YaST:Web ... <repository name="openSUSE_Factory"> <path project="devel:languages:ruby:extensions" repository="openSUSE_Factory"/> <arch>x86_64</arch> <arch>i586</arch> </repository> ... So it is the <path> element, which does the work. Cheers, Martin -- 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 call 2009-09-24
by Jiri Srain 24 Sep '09

24 Sep '09

present: kkaempf, schubi, lslezak, jsrain, mzugec, mkudlvasr, mvidner kkaempf: - looked into patch model mocking (D-Bus, PackageKit) - refactored, added more comments - TODO: factor out generic D-Bus and PackageKit mocking schubi: - finished language translation stuff, sent to translators - fixing bugs (looks like gettext gem) lslezak: - REST API documentation - looking at administrator UI validation problems mzugec: - no progress mkudlvasr: - merged resource restful branch to master - finished YaST resource class - TODO: research local package build mvidner: - fixing base system setup workflow - put yast2-network for SLES11 into OBS to make network plug-in working from RPM AI everybody: check that all packages build -- 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] custom log merged
by Duncan Mac-Vicar Prett 23 Sep '09

23 Sep '09

I have just merged the log monitor into master. The documentation will go here: http://en.opensuse.org/YaST/Web/VendorCustomization However the config file format is still on RFC: http://lists.opensuse.org/yast-devel/2009-09/msg00056.html Known bugs: - If the service goes down, the ajax update shows infinite errors ( https://bugzilla.novell.com/show_bug.cgi?id=540623 ) Together with the merge, a new model class called Metrics went into the service, together with a MetricsController. This classes are supposed to replace Status and StatusController by providing a cleanuped version using collectd name conventions and a more ActiveResource complaint interface, plus tests done from the beginning, and I intend to port the client so the graphs can be overlapped by instance (see http://auxesis.github.com/visage/) but this is no priority for now. -- Duncan Mac-Vicar P. - Engineering Manager, YaST 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] 6.17.1: New method ui::Selectable::updateCandidateObj
by Michael Andres 23 Sep '09

23 Sep '09

Hi! I added a new method ui::Selectable::updateCandidateObj. As you know it's not sufficient to simply look for an available package with higher version, when looking for an update candidate. There are more policies to respect, like the ones for arch and vendor changes. Also repo priorities may influence the result. updateCandidateObj will return you whether the candidateObj matches the active solver policies and has a greater version, and no PoolItem otherwise. So if the UI wants to suggest Selectables that could be updated, it could suggest the ones providing an updateCandidateObj, and not all where the candidate has 'just' a greater version. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma(a)novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- 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 call 2009-09-23
by Jiri Srain 23 Sep '09

23 Sep '09

present: mschmidkunz, lslezak, jsrain, jreidinger, mzugec jdsn: - no progress mschimidkunz: - UI mock-ups for network administration and time - TODO: look at bugs lslezak: - spec-file versioning on ML - documenting the documentation process of REST service jreidinger: - debugging problems of FireFox and base system, working on testcase for Firefox mzugec: - no progress - TODO: bzilla -- 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] Registration Rest Api
by J. Daniel Schmidt 22 Sep '09

22 Sep '09

Hi hackers, I want to share my current thoughts about the Rest Api for the registration. Please have a look and feel free to comment and ask. Registration Configuration: --------------------------------- * /registration/config GET get registration server returns: <registrationconfig> <server> <url>https://myregistration.server.com/center/regsvc</url> </server> </registrationconfig> PUT set new registration server the certificate is inclueded as well post data: <registrationconfig> <server> <url>https://somewhere.else.com/center/regsvc</url> </server> <certificate> <data> <![CDATA[ -----BEGIN CERTIFICATE----- MIIFIDCCBAigAwIBAgIJAPP6cY6saTFlMA0GCSqGSIb3DQEBBQUAMIGPMQswCQYD VQQGEwJERTEPMA0 ......... 60QTef32lxeuVH9Kve8gGZiMwDqcJfl J8NLO3kNW3Zys2p4agg22yttmUs= -----END CERTIFICATE----- ]]> </data> </certificate> </registrationconfig> return value is the same as for GET Run Registration: --------------------------------- * /registration POST run registration and return the/a result post data: <registration> <options> <debug>2</debug> <nooptional>1</nooptional> <nohwdata>1</nohwdata> <forcereg>0</forcereg> <httpproxy>http://my.proxy</httpproxy> <httpsproxy>http://my.proxy</httpsproxy> </options> <arguments> <argument> <name>key</name> <value>val</value> </argument> ... </arguments> <registration> returns: <registration> <status>finished|missinginfo|error</status> <message>Some text to display</message> <guid>systemsguid</guid>  <missingarguments> <argument> <name>missingkey</name> <type>string|text|number</type> </argument> ... </missingarguments>  <changedrepos> <repo> <name>repoName</name> <alias>myRepoName</alias> <urls> <url>http://some.host/repo/xy</url> ... </urls> <priority>80</priority> <autorefresh>true</autorefresh> <enabled>true</enabled> <status>added|deleted</status> </repo> ... </changedrepos> <changedservices> <service> <name>some-serv1</name> <url>http://some.host/services/serv1</url> <status>added|deleted</status> </service> ... </changedservices> </registration> There is only one action to perform the registration. And all data has to be send for each request, as it operates in stateless context. The following action depends on the answer to the request. If there are arguments missing a following call is needed (together with the additional arguments). Otherwise the changes to the package system are returned if the registration succeeded. Thanks for comments. 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

5 11