December 2009 - YaST Development - openSUSE Mailing Lists

[yast-devel] WebYaST feedback
by Martin Vidner 14 Dec '09

14 Dec '09

Hi, Stano has already entered the individual problems to bugzilla, but I thought it would be useful to summarize them - Customization is lacking Style sheets are kind of messy. It is hard to replace "My Appliance" with "ACME Foobarizer". Help cannot be customized. Oh wait, there is no help. - Module offer is enough For Foobarizer, his first boot would contain License Root password (maybe Network) Registration He does not expect a need to write a new module for the first boot. But if he needs to, he would write it in their application's framework, not in WebYaST. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

2 1

[yast-devel] [ANNOUNCE] ZYpp source repositories on gitorious.org/opensuse
by Duncan Mac-Vicar Prett 11 Dec '09

11 Dec '09

The ZYpp repositories previously published at git.opensuse.org repositories are now available on http://gitorious.org/opensuse http://gitorious.org/opensuse/sat-solver http://gitorious.org/opensuse/libzypp http://gitorious.org/opensuse/zypper http://gitorious.org/opensuse/zypp-utils (previously zypp/tools) http://gitorious.org/opensuse/libzypp-bindings http://gitorious.org/opensuse/libzypp-testsuite http://gitorious.org/opensuse/zypp-dialogsolver http://gitorious.org/opensuse/cmpi-zypp http://gitorious.org/opensuse/zypp-zmd-backend (previously zypp/backend) There is an initial opensuse-zypp team defined with access to those repositories. To switch you only need to edit your .git/config origin remote If before it was git@git.opensuse.org:projects/zypp/zypper.git Now it would be: git@gitorious.org:opensuse/zypper.git The repositories in git.opensuse.org are still accessible, but you can't push to them anymore. They will stay there until no repositories are left on that machine. Gitorious provides feeds for each repository pushes, and per each branch commits. To make it easier to follow the overall project, I have created this feed which merges various feeds and make the titles more similar to the old mails: http://pipes.yahoo.com/pipes/pipe.info?_id=36dc1dc1c0380cca92df9ddaa5b6e26d In the next days we will look for a solution to mail those feed updates to the commits mailing list. -- 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] Nokogiri branch
by Josef Reidinger 11 Dec '09

11 Dec '09

Hi, I create use_nokogiri branch for webclient. My quick test doesn't show any problem. Could you try it and report me if any problem occur in your modules [1]? Nokogiri advantage is better performance without almost any cost. thanks Josef [1] howto run nokogiri branch: zypper in rubygem-nokogiri git checkout -t origin/use-activeresource #in webclient directory start.sh #start webclient -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast (language,time,basesystem,ntp) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 2

[yast-devel] questions concerning yast2-testsuite
by Arvin Schnell 11 Dec '09

11 Dec '09

Hi, I have some problems with the yast2 testsuite. When I run tests in storage y2base cannot find the libstorage bindings since they are not installed in the system. So I need to modify the Makefile.am get unfortunately gets overwritten by the testsuite. Is there any mechanism to handle specific changes to the files from the testsuite skeleton? Also I would like to change testsuite.exp to run all tests even after a failure. Objections? -foreach file $filenames { - if {[testsuite-run $file] < 0} { - return - } -} +foreach file $filenames { testsuite-run $file } caio Arvin -- Arvin Schnell, <aschnell(a)suse.de> Senior Software Engineer, Research & Development 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

3 5

[yast-devel] wiki - updated Rails debugging page
by Ladislav Slezak 11 Dec '09

11 Dec '09

Hi all, I have updated the Rails debugging page (http://en.opensuse.org/YaST/Web/Development/Tips) Added sections: * starting Rails app directly in the ruby debugger * debugging a Ruby process using GDB debugger - if the app does not respond at all you can still get the backtrace or introspect the objects (actually it's just a link to http://eigenclass.org/hiki.rb?ruby+live+process+introspection ) -- 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 call 11-Dec-2009
by Jiří Suchomel 11 Dec '09

11 Dec '09

participants: jsuchome, kkaempf, mvidner, jsrain, schubi, lslezak, jdsn, dmacvicar mvinder: plan to learn new things, encourages others lslezak: testing and preparing patches patch, seen DBUS problems kkaempf: working on announcements, release notes, until noon schubi: fixing bugs in branch, looking for status page improvement dmacvicar: research on autocompletion, validation Next call: 4th January 2010 -- 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

1 0

[yast-devel] Webyast Serialize hash to xml
by Josef Reidinger 11 Dec '09

11 Dec '09

Hi, when I work on ancestor for rest-service I found interesting problem. How to serialize hash with general keys. Problem is that key could contain prohibited characters and there is no way how to escape it in xml tag (in json it works without problems). I see few solution and want discuss which one is preferred. 1) prohibit general keys and allow only developer defined string: It is how it is done now, as we manually create xml and hash is encoded to different tags ( so eg replace general key => value with [ :key => key, :value => value] ) (it is solved e.g. in time where is map with id_of_timezone => name of timezone) advantage: - easy to do - same as we did it now - easy to use for customer which want use directly rest-service disadvantage: - key must be checked otherwise it could be security problem - more work in rest-service and webclient as hash must be transformer before and after serialization 2) use inlined yaml - serialize hash to yaml and inline to xml. It escaped any problematic patterns advantage: - work out of box - easy to use - no additional transformation disadvantage: - problem for customer which want to use directly rest-service as he must define hash as yaml - on webclient hash must be saved as yaml (easy call hash.to_yaml) which is unintuitive 3) hack webclient Hash.from_xml. I can modify hash.from_xml behavior so if he get hash type it expects array with tags key and value, so result looks same as in 1) and hack it also on backend so it is automatic recognize and just works. advantage - - work out of box - developer doesn't know about it, just works disadvantage - - if customer use nonmodified rails, then it doesn't read correctly as hash (but still can work with it) - need modifications in webclient and rest-service xml serialization and deserialization 4) Use only json - Provide only json in rest-service advantage: - json has better performance then xml, as it is easier to parse and create disadvantage: - no XML, so customer could complain I welcome any comments about solutions or propose of new solution. Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast (language,time,basesystem,ntp) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] a few notes on autocompletion
by Duncan Mac-Vicar Prett 11 Dec '09

11 Dec '09

After playing some days with forms and the users module in order to achieve the following goals: - autocompletion of form data - examples for fields - browser side validation I want to share some results of those experiments and how they affect our design The first limitation I found is mostly likely present in various models. Users.find(:all) returns less data than Users.find(id), only the username and something else. If you want to autocomplete/suggest all known login shells ( something like Users.find(:all).map { |x| x.login_shell } ) you need a way on the client side to get all login shells. I ended modifying the /users service to - accept ?attributes[]=attr1&attributes[]=attr2... so that the caller could chose which attributes to insert - be sure that it was able to return json Once you have that, doing autocompletion is trivial, but very repeat-yourself prone. Biggest problem is that you can't call from the browser the rest- service unless: - you set the url of the resource in the view - you use JSON-P, using $.getJSON and setting a jsonp callback ( http://en.wikipedia.org/wiki/JSON#JSONP ) Or you can create an action in the controller which calls the service and returns the result. I can't get the jsonp call to actually process the data. Then you need to set the right autocomplete data in the javascript document.ready callback inlined in the view (at least until we solve the problem I mentioned in opensuse-ruby mailing list ), by using jquery.autocomplete calls on the right form fields, giving the autocomplete data you got from the service or the controller action We can avoid duplication of Javascript by emulating what rails implements with protoype, so that you specify the autocompletions in the model class. For that we would need to swtich from find_proxy to a real User class using the class Martin Kudlvasr and Martin Vidner where working on. Once you have a model we could use something like: http://github.com/grosser/simple_auto_complete combined with the jquery.autocomplete plugin to achieve a more or less standard to apply validation to our forms. Any ideas? -- 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] WebYaST GMC (gold master candidate)
by Martin Vidner 10 Dec '09

10 Dec '09

0. Introduction =============== WebYaST is a web-based remote console plugging into a stateless interface exposed by an SLE-based appliance and providing a set of configuration modules appropriate to enable minimal user control of the appliance "black box" environment. 1. Installation =============== WebYaST is not "installable" per se. It is a component available for building of appliances. To build appliances using webYaST, set up the repository in your SUSE Studio instance. See also these documentation packages for vendors: webyast-vendor_en.rpm webyast-vendor_en-pdf.rpm REPOSITORY: zypper ar http://www.suse.de/~mvidner/webyast-gmc webyast-gmc zypper ar http://www.suse.de/~mvidner/webyast-lighty webyast-lighty (webyast-lighty contains fixes for SLES and SDK which will appear as maintenance updates for these base products) APPLIANCE DOWNLOAD: http://www.suse.de/~mvidner/webyast-gmc/vm/Signed_WebYaST_on_SLES11.i686-0.… http://www.suse.de/~mvidner/webyast-gmc/vm/Signed_WebYaST_on_SLES11.i686-0.… ( gpg --verify Signed_WebYaST_on_SLES11.i686-0.26.0.vmx.tar.gz.asc ) sha1sum: a79fb9c417eee226d9199403d0cbf02545a5cc64 internal: ftp://cml.suse.cz/testing/webyast/Signed_WebYaST_on_SLES11.i686-0.26.0.vmx.tar.gz MODULE SPECIFIC NEWS: http://www.suse.de/~mvidner/webyast-gmc/ChangeLog 2. Usage ======== Run our sample appliance. The WebYaST console is running at port 54984 in the resulting appliance. Point the browser to https://<appliance-hostname>:54984/ (**) Log in as root, with password linux yast2-webservice-basesystem is included, go through the base setup (language, eulas, admin, network, time, mail, registration) See also these documentation packages for users: webyast-user_en.rpm webyast-user_en-pdf.rpm 3. Known Issues =============== No P1, 4 P2s: 559145,"Major","mvidner(a)novell.com","schubi(a)novell.com","NEW","Changed Domain name not reflected when sending mail" 560701,"Major","mvidner(a)novell.com","jsuchome(a)novell.com","NEW","[build 24.1] webYaST appears to crash after installing webclient patch" 560292,"Normal,"dmacvicar(a)novell.com","schubi(a)novell.com","NEW","Error while updating yast2-webclient package" 561642,"Normal","lslezak(a)novell.com","thomas(a)novell.com","ASSIGNED","WebYAST RC4 webservice mail_settings fuzzing causes dozens of sh processes to hang around" See this query for a complete bug list: https://bugzilla.novell.com/buglist.cgi?query_format=advanced&product=openS… 4. Feedback =========== We are eager to get your feedback. Please, report the bugs, post general comments and questions to the yast-devel(a)opensuse.org mailing list. Other alternatives: - irc://irc.opensuse.org/yast - https://bugzilla.novell.com/enter_bug.cgi?component=WebYaST&product=openSUS… (please disregard the oS11.2 version and instead remember to mention the appliance version.) See http://en.opensuse.org/Bugs/WebYaST - mailto:yast-devel@opensuse.org -- Martin Vidner, WebYaST release engineer http://www.youtube.com/watch?v=PDwH9UlRIjc 3... 2... 1...

5 8

[yast-devel] WebYaST status call 10-Dec-2009
by Jiří Suchomel 10 Dec '09

10 Dec '09

participants: jdsn, jsuchome, jsrain, mvidner, lslezak, schubi, dmacvicar all: testing mvidner: GMC released in time (before the party) lslezak: fixed bnc #561642, not for GM schubi: checking permissions, work in branch -- 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

1 0