September 2009 - YaST Development - openSUSE Mailing Lists

[yast-devel] Webyast - base system module and error reporting
by Josef Reidinger 10 Sep '09

10 Sep '09

Hi, I merge basesystem branch to master. So after you login to your machine ,if you don't install it from rpm,you find another new cool feature - backend error reporting. It says that some file missing for basesystem settings. So just install file from package to location which error hint you ;) Welcome any bug reports on base system settings or backend error reporting. ( I plan write to wiki what you must do in your module to allow it in basesystem settings) -- 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 status, 2009-Sep-10
by Josef Reidinger 10 Sep '09

10 Sep '09

kkampf: - cleaning Patch module and continue with it - study rails constant for ENV versus env variable - continue with reviewing commited code dmacvicar: - vendor settings in log, will merge code to master mzugec: - network send data from frontend to backend to write and find problem with ruby dbus - will work on dbus write mvidner: - add tests yesterday fix - inspecting mzugec ruby dbus bug - start discussion on mailing list about change for ActiveResource in lslezak: - document debug rest service via curl - document restibility of plugin and generate output to public jsuchome: - commit rest api for administrator setting, simple webclient for it jsrain: no update jreidinger: - try merge basesystem branch to master - add reporting of backend problems to frontend jdns: - try solve registering repositories and services in backend -- 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] RFC logs API, settings
by Duncan Mac-Vicar Prett 10 Sep '09

10 Sep '09

Right now there is a resource /logs which support only index (in all formats) and show (only in txt format) <logs type="array"> <log> <id>system</id> <path>/var/log/messages</path> <description>System messages</description> </log> <log> <id>apache</id> <path>/var/log/apache2/access_log</path> <description>Apache</description> </log> </logs> The other supported API is /logs/id?lines=x which only answers in .txt format. I experimented with two ways to define those logs, you can't pass an arbitrary filename to the API because that would be a security hole, but you can define them in vendor config files. Here are the two approaches. 1) in /etc/YaST2/vendor.yml together with other vendor settings: bug_url: http://www.bugs.com packages: - mydb-server - mydb-console log_files: - /var/log/messages - /var/log/apache2/access_log And then you get them as /logs/0, logs/1 However, this has the drawback that you dont know anything else from the log to display it in the user interface. Then a second approach, cat /etc/YaST2/vendor/logs.yml system: path: /var/log/messages description: System messages apache: description: Apache path: /var/log/apache2/access_log Then the client can display more information about them. Which approach seems better? simplicity vs usefulness? -- 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

1 0

[yast-devel] Ruby-Perl binding
by J. Daniel Schmidt 09 Sep '09

09 Sep '09

Hi Hackers, In case somebody needs to evaluate Perl code from Ruby you can get the package "ruby-perl" from: https://build.opensuse.org/package/show?package=ruby- perl&project=home%3Ajdsn%3Atesting I only did some small tests with it (but now went for a different solution of my problem). Please report if there are any issues with the package. Don't know yet if I submit it to factory as it is not maintained. 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

1 0

[yast-devel] Using curl for sending REST API requests
by Ladislav Slezak 09 Sep '09

09 Sep '09

Hi all, While documenting a REST API I realized that I'd like to test the XML examples which I have created. I have added a new section on the Tips wiki page [1] describing how to use curl for this task. The page describes how to authenticate to the REST API, how to send PUT/POST requests and how to send a XML input file. Enjoy! [1] http://en.opensuse.org/YaST/Web/Development/Tips#Using_curl_for_sending_RES… -- 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

2 1

[yast-devel] WebYaST: Registration RFC
by J. Daniel Schmidt 09 Sep '09

09 Sep '09

Hi, The last days I did some research about how to implement the registration in WebYaST. And the more I found out about the stuff the more complicated everthing got. I want to give a short summary and ask for your comments here. The registration itself is realised in a Perl module. There are currently two wrappers that do the workflow for this module. The first is a command line tool called "suse_register" and the second is the YaST module "inst_suse_register" which represents the GUI pendant. My first idea was to use the Perl module directly from Ruby. After a lot failures it finally works with the bindings from: http://www.yoshidam.net/Ruby.html#perl I will prepare a package of these in the BS in case somebody needs to evaluate Perl code from Ruby. When I realised that the rest-service does not run as root (it did on my workstation) but registration must run as root it made the bindings worthless. So we have to go through the needle eye of a DBus-SCR-call and run a commandline script (as root) and parse its output. Well, as I only need to call a script I don't see the need to go over DBus here. What about configuring sudo for the webservice user? Or using a tiny setuid wrapper script? Security-wise this would make no difference, as we can do everything via SCR-calls as root anyway. It would just make things less complicated (1). Fortunately I can rely on the fact that the NCC registration server (and soon SLMS as well) offer server side caching, that means, I don't need to implement a client side statemachine (which is hard in REST context where each next call is the first one). One tricky part is the zypp lock. If somebody locked the package manager on the system and then somebody else tries to register, the zypper calls will fail. The YaST module tells the user about it as it initialises the package manager on startup. But how to this in REST contect? Just return an error like "The service you are calling is temporarily not available. Please call again later"? :) This gets less funny when it happens during a registration, as we can/should not keep a package management lock in a REST service and thus the lock might be taken in the meanwhile. 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 (1) For me all this has too many layers already: Ok, lets skip the users browser that does HTTP(S) requests to the web-client which in turn does HTTP(S) requests to the rest-service. The rail rest-service then needs to do an SCR-DBus call which starts a DBus- Service and so does an Execute as root and runs a new script (the current suse_register is not sufficient for this) which is a new wrapper for the registration Perl module that talks to the NCC-server via HTTPS requests and parses their XML. The dumped result needs to get parsed again in the rest- service. In case there is information missing the user needs to get asked again. In case the registration is done there are (most likely) changes to be done to the package system (which might fail because of a zypp lock of a different user) that need to go there the SCR-DBus-way. Can we reduce the number of layers somehow? Or did I forget about some, that need to be added to make it more interesting? :) -- 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] Lazy package requirements of YaST modules
by Martin Vidner 09 Sep '09

09 Sep '09

Hi, yast2-nfs-server requires nfs-kernel-server, but it does not say so in .spec. Instead, it checks at run time and offers to install it then. Other modules are similar. Should we not list these packages as Recommends in .spec? IIRC the current practice was esablished before Recommends was available. ( https://bugzilla.novell.com/show_bug.cgi?id=535544 ) -- 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

3 2

[yast-devel] Re: [Bug 537200] [task] [fate 307141] Admin password and e-mail rest service
by Jiří Suchomel 08 Sep '09

08 Sep '09

On Tuesday 08 of September 2009 13:44:03 Bugzilla_NoReply Bugzilla_NoReply wrote: > http://bugzilla.novell.com/show_bug.cgi?id=537200 > > User kkaempf(a)novell.com added comment > http://bugzilla.novell.com/show_bug.cgi?id=537200#c3 > > > > > > --- Comment #3 from Klaus Kämpf <kkaempf(a)novell.com> 2009-09-08 05:44:01 > MDT --- (In reply to comment #2) > > > Lets discuss such things on yast-devel ! > > Move the final documentation into git, link it from the wiki, and put the > wiki url here. > > > Admin password module proposal (fate #307141) > > --------------------------------------------- > > > > Tasks: > > - change administrator (root's) password > > - configure notification e-mail addresses > > (mail aliases for root) > > - possibly more in the future > > > Model > > > > singleton class Administrator > > > > attributes > > string password > > list aliases > > Why would aliases be a list ? I understand the request as "single email > address" to send mails to. And, is 'alias' the right name for this ? I'm thinking about the implementation as an entry in /etc/aliases (we have MailAliases.ycp for that). And here it is possible to assign multiple aliases for one e-mail. > > methods > > (access the system, probably using YaPI::USERS) > > > > set_password > > set_aliases > > get_aliases > > You don't need set/get prefixes in Ruby. Ah, well, get_aliases is actually part of find method. set_password and set_aliases are meant as a methods that actually access the system (call YaPI or whatever), not that they just fill the variables. Or there can be one save method, handling both, but I thought more granularity can help testing. > > > Policies > > > > org.opensuse.yast.modules.yapi.users.administrator.read > > org.opensuse.yast.modules.yapi.users.administrator.write > > > > API > > > > URL: /administrator > > > > REST service pseudo-code: > > > > # GET method > > def show > > > > read and return current mail aliases > > > > # PUT method > > def update (params) > > > > if password changed > > > > save the new password > > > > if aliases changed > > > > save new list of aliases -- 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

2 1

[yast-devel] ** [webyast] Reminder: set your tasks to 'assigned'
by Klaus Kaempf 08 Sep '09

08 Sep '09

WebYaST developers, this is a friendly reminder to set the tasks you're working on to 'assigned' in Bugzilla. 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: Transition of tasks to Bugzilla complete
by Klaus Kaempf 07 Sep '09

07 Sep '09

Hi, the initial round of moving tasks from the Wiki to Bugzilla is now done. All tasks are for 'WebYaST'/'openSUSE 11.2' and start with '[task]' in the summary. The tasks are sized to be reasonably small, typically two to three days. Every WebYaST developer should have one or more tasks assigned to him via bugzilla. ** Please check that the task assignment matches your current ** work. Set the bug to 'assigned' if this hasn't been done before. All tasks must have a 'target date' set. Please set this field according to your own estimate. Thanks ! 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