December 2009 - YaST Development - openSUSE Mailing Lists

[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

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

09 Dec '09

participants: jsuchome, jdsn, jsrain, mvidner, jreidinger, kkaempf, dmacvicar all: testing jreidinger: dbus models ancestor, work in branch mvidner: package kit bug fix, build problems passed, working on final release dmacvicar: moving to gitorious: see yast-internal after release: check bugzilla bugs, set priorities, 11.2 status not clear yet -- 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] Profiling rest-service
by Josef Reidinger 08 Dec '09

08 Dec '09

Hi, I profile also rest-service. Its result is quite good. I choose time plugin index action. It shows that it spend the most of time in building XML. DBus layer takes just few percents (around 3%). So bottleneck of rest-service (beside YaPI) is creating XML, but I don't know better alternative. 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

2 2

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

08 Dec '09

WebYaST status call 07-Dec-2009 participants: jsuchome, jdsn, mvidner, schubi, jsrain, jreidinger, mschmidkunz, dmacvicar, bbrunner, visnov jsuchome: testing lighty bug fix jdsn: testing, building appliance mvidner: Friday fixes are ready, but not sufficient (sysvinit). Should we ship? Yes, after this bug is solved. schubi: testing, looking for other possible solutions for lighttpd jreidinger: client profiling: Rails XML parser slow - some promising results mschmidkunz: testing with RC4, talk with Garret about jquery dmacvicar: mail about UI review, see yast-internal -- 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] Re: WebYaST on 11.2
by Martin Vidner 08 Dec '09

08 Dec '09

On Mon, Dec 07, 2009 at 10:50:54PM +0000, Tim Schuermann wrote: > Hi Martin! > > Which package I have to install? > > (rubygem-rails-2_3 is already installed at my openSUSE 11.2-installation.) > > Regards, > > Tim Hi Tim, I think there is some other rails dependency missing, but due to the bug below it is not so easy to know which. You will know once you resolve the sysvinit dependency. You need sysvinit from http://download.opensuse.org/repositories/Base://System/openSUSE_Factory and lighttpd, cannot find it now :-( https://bugzilla.novell.com/show_bug.cgi?id=559534#c69 > > See http://bugzilla.novell.com/show_bug.cgi?id=561392 for > > the > > details. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

1 0

[yast-devel] WebYaST on 11.2
by Martin Vidner 07 Dec '09

07 Dec '09

Hi, on IRC we looked at a problem where WebYaST on 11.2 gives only a minimal 500 page. I haven't resolved all issues yet, but one problem is that ignoring a lighttpd dependency ignored also entire Rails :-) See http://bugzilla.novell.com/show_bug.cgi?id=561392 for the details. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

1 0

[yast-devel] Profiling web-client
by Josef Reidinger 07 Dec '09

07 Dec '09

Hi, I profile web-client to find where is bottleneck. I run tests on network plugin (index action) as it takes the most serious amount of time. To profile I use ruby-prof in specified part of code. 1) almost all time takes internal parsing in REXML (more then 80%) (waiting on rest-service is not measured). 2) permissions recognition take around 7% of time. 3) resource_for_interface takes around 20% of time. comments: add 2) I create bug - https://bugzilla.novell.com/show_bug.cgi?id=561265 . It should be easily cached, as permission for target host is not changed often. So on login it could be stored in local db information about permissions. add 3) I create bug -https://bugzilla.novell.com/show_bug.cgi?id=561283 . It can be cached as well, as routes for interface is not changed. So at least during login it should be stored and then used. add 1) I read some articles and there is much better alternatives then default REXML. The easiest usage and good support in rails has nokogiri. I try it and it is more then 3x faster ( 960k cycles REXML versus 290k cycles for nokogiri). I try it also visually and it looks little faster (flickr says that its speedup is 40%). You can also try it. Just install rubygem-nokogiri, then add this line to your enviroment.rb: ActiveSupport::XmlMini.backend = 'Nokogiri' And it works (I am not sure if this package is in SLE11. How can I find it?). 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

2 2

[yast-devel] WebYaST status call 03-Dec-2009
by Jiri Srain 03 Dec '09

03 Dec '09

participants: jsrain, mvidner, schubi, lslezak, kkaempf, dmacvicar, visnov, mkudlvasr jsrain - confirmed that lighttpd fix did not solve the problem mvidner - working on lighttpd issue and image building shubi - lighttpd bug lslezak - testing, looking into bugs - looking for performance bottlenecks, identified calls to optimize kkaempf - lighttpd bug mkudlvasr - testing RC7, researching caching in Rails mkudlvasr + lslezak TODO: look what can get broken on package update -- 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] Is it allowed to modify one same list via foreach?
by Johannes Meixner 02 Dec '09

02 Dec '09

Hello, is such code allowed: -------------------------------------------------------------------- list < string > words = [ "Jane", "John" ]; integer index = -1; foreach( string word, words, { index = index + 1; words[index] = "Hello " + word; } ); -------------------------------------------------------------------- Is in any case the result words == [ "Hello Jane", "Hello John" ] ? If the above is allowed, what about even more evil looking code: -------------------------------------------------------------------- list < string > words = [ "Jane", "John", "Joe" ]; integer index = -1; foreach( string word, words, { index = index + 1; if( "John" == word ) { remove( words, index ); } } ); -------------------------------------------------------------------- Is in any case the result words == [ "Jane", "Joe" ] ? If it is not allowed, how to copy a list? Does -------------------------------------------------------------------- list < string > words = [ "Jane", "John", "Joe" ]; list < string > copy = words; -------------------------------------------------------------------- result two totally separated lists words and copy or does copy contain only a reference which points to words so that -------------------------------------------------------------------- remove( copy, 1 ); -------------------------------------------------------------------- would actually result copy == words == [ "Jane", "Joe" ] ? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 3

[yast-devel] WebYaST status call 02-Dec-2009
by Jiri Srain 02 Dec '09

02 Dec '09

participants: jsrain, jdsn, jsuchome, schubi, mvidner, kkaempf, mschidkunz, dmacvicar everybody - testing - last image did not solve the key issue jsuchome - found solution of mail problem with Petr Varkoly, suggesting wait for maintenance update - observed crash after upgrade of lighttpd schubi - will have a look at the lighttpd problem mvidner - created initial release notes - will also have a look at the lighttps problem -- 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-gtk sw_single thread
by Ricardo Cruz 01 Dec '09

01 Dec '09

Hi there, There is an ongoing discussion over the future of yast2-gtk's software manager UI at: http://groups.google.com/group/yast2-gtk Feel free to subscribe and throw your 2 cents. Cheers, Ricardo ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. -- 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 01-Dec-2009
by Jiri Srain 01 Dec '09

01 Dec '09

participants: jsrain, visnov, mvidner, lslezak, kkaempf, jdsn, dmacvicar, schubi, jsuchome, mschmidkunz mvidner - built RC6, still reports "No Updates" - keys are not imported, UI does not detect this error - release notes are missing lslezak - testing, debugging some bugs in classic YaST which may affect WebYaST and lead into infinite loop (actually not affecting) kkaempf - busy with effort estimates - we have to fix patch installation (the only blocker) jdsn - various tests, found missing GPG keys schubi - testing - will look into patch stuff jsuchome - testing & fixing esp. mail settings, still no idea what's wrong with mail everybody - testing latest builds, working on bugfixes - we need to verify that documenting how to add keys is sufficient -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1