March 2010 - YaST Development - openSUSE Mailing Lists

[yast-devel] WebYaST status 26-Mar-2010
by Thomas Goettlicher 26 Mar '10

26 Mar '10

tgoettlicher, jsrain, mzugec, mvidner, jsuchome, jreidinger, jdsn, schubi, vgorobets missing: kkaempf, lslezak, mkudlvasr, mschmidkunz jdsn: - debugged virtual box issues jreidinger: - used tools known for training with webyast jsrain: - booted latest image jsuchome: - worked on service dependencies - submitted rest part - next: work on ui part mvidner: - worked on changelog aggregator - next: look at bugs in modules mzugec: - worked on group management - next: submit to master schubi: - worked on mechanism for messages from modules - next: continue tgoettlicher - busy with non-webyast bugs vgorobets - implemented regexp functions in javascript -- 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 24-Mar-2010
by Thomas Goettlicher 24 Mar '10

24 Mar '10

tgoettlicher, jdsn, schubi, mschmidkunz, vgorobets missing: kkaempf, jreidinger, jsrain, jsuchome, lslezak, mkudlvasr, mvidner, mzugec Joke of the day: "Hurvínku, víš kolik pracovníků Microsoftu je potřeba na výměnu žárovky?", ptá se Steven. Hurvínke chvíli přemýšlí a a pak si to nechá říci. "Žádný přece, oni prohlásí tmu za standart." tgoettlicher: - busy with non-webyast bugs (sles10sp1) jdsn: - busy with non-webyast topics (hudson) mschmidkunz: - busy with non-webyast bugs - next: navigation buttons schubi: - bug fixing vgorobets: - tested and committed fixes - jquery validator - css 3.0 tutorial -- 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 status 23-Mar-2010
by Thomas Goettlicher 23 Mar '10

23 Mar '10

tgoettlicher, jsuchome, vgorobets, schubi, jdsn, jreidinger, mvidner, mkudlvasr, lslezak, mzugec missing: kkaempf, jsrain, mschmidkunz mzugec: - web client part of group - next: merge with rest service schubi: - bug fixing jsuchome, - bug fixing - next: implement service dependencies vgorobets: - java script / ruby gem problem (thanks to mvidnder) - hostname validation - next: bug fixing and jquery jreidinger: - bug fixing - next: bug fixing jdsn: - no update - next: bug fixing mvidner: - osc overview, - next: look into webyast crash while updating mkudlvasr: - rest service of groups - next: rest service for groups lslezak: - auto status reload - next: submit packages tgoettlicher: - busy with non-webyast bugs -- 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 - control panel configuration
by Ladislav Slezak 23 Mar '10

23 Mar '10

Hi all, I have added a new config file for the WebYaST control panel. It's stored in /etc/webyast/control_panel.yml file. This change allowed me to fix bugs: Bug 558027 - Regularly update patch status Bug 558028 - Health status needs to be updated regularly Bug 580025 - It should be possible to disable "update status" and "system status" in the control center So the overall statuses are automatically refreshed now or they can be completely turned off (that can be useful during development or testing, you don't need to wait for checking updates and system status). Here I'd like to discuss some issues I found: The config is stored in /etc/webyast/control_panel.yml and there are some other files in that directory, but I found that there is /etc/webyast/vendor/logs.yml config file. So my question is what is /etc/webyast/vendor directory for? Is there any difference between /etc/webyast/vendor*.yml and /etc/webyast/*.yml files? Which one should I use in this case? Another problem I see is in the defaults: 1) The requested default for patch status refresh is 24 hours. I agree that this refresh timeout should be rather longer, but this is too long - the problem is that 24 hours refresh time out collides with session time out. After 24 hours the session will be invalid and no status will be displayed and thus the feature with this particular refresh value is useless. So I'd like to change it to something like 6 or 8 hours. 2) A similar problem is with the system status time out (but the other way round in this case). The requested default value is 1 minute which I find too low. Evaluating system status is a quite expensive operation and takes a long time. Doing that every minute creates extra load on the target machine. More over if users really need such an immediate warning I guess they will very likely use other means (like email, SMS message, custom scripts, etc.) without WebYaST involved. So here I propose to use default time out value of 5 or 10 minutes. What do you think about it? -- 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] Showing state of WebYaST plugins in status plugin.
by Stefan Schubert 22 Mar '10

22 Mar '10

Hi, currently we have two requests for showing special states of WebYaST plugins in the status plugin: Mail Settings: When the user has submitted a test mail he will be asked in the status module, if he has received the email. This message disappears after he has confirmed the receive in the status module. Registration: A warning will be displayed in the status module if the user has skipped over the registration. This warning disappears only after the user has successfully finished the registration. I believe that we will have more such requests in the future. So we should think about a generic solution. One proposal would be: Webservice side: The status module checks each installed plugin if it has an interface "status" like: registration/registration/status [GET|POST] [GET| returns: <states> <state> <level>info|warning|error</level> <message_id>id-string</message_id> <short_description>....</short_description> <long_description>...</long_description> <confirm_button>true|false</confirm_button> </state> <state> .... </state> </states> So each plugin can return more than one message. The "level" will be displayed in the status module. "*_description" is a English default description which will be displayed if there is no translation on the WebYaST client side available. "message_id" indicates the translated message in the WebYaST client status module. If the user press the "confirm_button" a POST request will be send to the concerning service plugin. Then it is up to the service plugin to reset the state. Not more would be needed from a plugin which intents to display a message/error in the status module. The service status module "collects" all these messages and send it to the client status module which has to display the messages. That would be one solution for displaying plugin messages. But perhaps there is another smarter one too. Suggestions :-) Greetings Stefan Webclient side: The status module checks each installed plugin if it has an interface "status" and status_reset" "status" -- 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 22-Mar-2010
by Thomas Goettlicher 22 Mar '10

22 Mar '10

tgoettlicher, jsrain, mzugec, jsuchome, mvidner, vgorobets, schubi, jreidinger, jdsn missing: kkaempf, lslezak, mkudlvasr, mschmidkunz jsrain: no update tgoettlicher worked on non-webyast bugs next: continue on non-webyast mzugec (micahel) no update legacy yast next: group management jsuchome: find solution services dependencies next: continue on services services dependencies mvidner: yast2 next: osc overview / release procedure vgorobets: added webyast page to wiki next: bug fixing schubi: added "start" button to status module next: find solution how to enable modules to show message in the status module jreidinger: non-webyast bugs next: bug fixing jdsn: returned from sick leave -- 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 configuration for LDAP
by Developer Coldfusion developer 22 Mar '10

22 Mar '10

Hi. I am trying to configure LDAP auth threw Yast2. I am using OpenDS as LDAP server. I have the following error: ...violates the Directory Server schema configuration because it includes multiple conflicting structural objectclasses suseObjectTemplate and suseGroupTemplate Can anyone help me? Thanks -- 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] jQuery for Complete Beginners
by Klaus Kaempf 19 Mar '10

19 Mar '10

This might be interesting: http://www.1stwebdesigner.com/tutorials/jquery-beginners-1/ 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 status 19-Mar-2010
by Thomas Goettlicher 19 Mar '10

19 Mar '10

tgoettlicher, jsrain, vgorobets, mzugec, jsuchome, mvidner, lslezak mvidner missing: kkaempf, jdsn, jreidinger, mkudlvasr, mschmidkunz, schubi jsrain: - no update tgoettlicher: - no update - busy with sle11sp1 bugs vgorobets: - osc build, edited wiki page next: webyast wiki deployment mvidner: - rc1 - code review mzugec: - test appliance with ie, reported bugs - next: legacy yast jsuchome: - fixed bugs (ui) - next: submit latest version lslezak: - tested latest appliance - next: auto status update in control center -- 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 18-Mar-2010
by Thomas Goettlicher 18 Mar '10

18 Mar '10

jsrain, tgoettlicher, mzugec, schubi, vgorobets, mvidner, jsuchome, mschmidkunz, mkudlvasr, lslezak missing: kkaempf, jdsn, jreidinger jsrain: - no update sp1 - next: check build mvidner: - rc1 done - next: fix if rc1 build is not ok jsuchome: - services, enable/disable, present in latest build - next: services dependencies lslezak: - fixed bugs in repo module - next: continue with bug fixing mkudlvasr: - fixed bugs - next: continue with bug fixing mzugec: - fixed bugs - creating/editing users - fixed ie incompatibility - next: non-webyast bug fixing, test webyast with ie schubi: - fixed bugs - next: continue with bug fixing tgoettlicher: - slms/webyast appliances done - next: non-webyast bug fixing vgorobets: - fixed webyast crash - next: submit changes to head/master -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0