[yast-devel] WebYaST: Vendor service - Summary + TODO
(Resending to yast-devel for a broader discussion....) Dne 21.8.2009 10:08, Jiří Suchomel napsal(a):
On Thursday 20 of August 2009 13:30:12 Ladislav Slezak wrote:
The REST service ================
- provides a REST API for both LSB and custom services - uses YaPI for LSB services - custom services are handled directly, config files are read/parsed directly, SCR service is used for execution - uses new YaST::ConfigFile library
Web UI (webclient) ==================
- provides a separate view on LSB services and custom services - allows custom branding (via modifications in /public directory)
TODO
The REST service ================ - enhance testsuite - add function to query service status (Q: use new policy for query, or use the one for "execute"?)
I'd reuse the existing right, no need for extra one IMHO.
Web UI (webclient) ================== - testsuite - design the UI (talk to mschmidkunz), may be different for System vs. Custom services
The question is if vendors would like to change "Custom Services" to a better name (with real service name). With current implementation they need to change the name directly in .yml config file. Is that OK?
- show the service status: - for system services, probably first show list of services, that update the status of each one service with AJAX calls
Maybe one AJAX call for all services could be better (I'm not sure about the overhead, running 30 requests in parallel instead of big one might be too slow.) Any idea? I'm not an AJAX expert...
- custom service is expected to be only one currently, so the status could be load on loading index page
I'd keep the same functionality, this creates unnecessary complexity. More over reading the current status might take long time so the complete page would be displayed after a (possibly long) delay.
- think how the service execution result should be shown better
-- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@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@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
* Ladislav Slezak <lslezak@suse.cz> [Aug 21. 2009 11:47]:
Web UI (webclient) ================== - testsuite - design the UI (talk to mschmidkunz), may be different for System vs. Custom services
The question is if vendors would like to change "Custom Services" to a better name (with real service name).
The'll certainly do.
With current implementation they need to change the name directly in .yml config file. Is that OK?
I'd guess so. But how does this match with translations ?
- show the service status: - for system services, probably first show list of services, that update the status of each one service with AJAX calls
Maybe one AJAX call for all services could be better (I'm not sure about the overhead, running 30 requests in parallel instead of big one might be too slow.)
Any idea? I'm not an AJAX expert...
Just don't bother with 'system' services now. Its out of scope for WebYaST '1.0' currently.
- custom service is expected to be only one currently, so the status could be load on loading index page
I'd keep the same functionality, this creates unnecessary complexity. More over reading the current status might take long time so the complete page would be displayed after a (possibly long) delay.
The delay shouldn't be a problem. Getting the patch status is also taking its time. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Monday 24 of August 2009 12:33:42 Klaus Kaempf wrote:
* Ladislav Slezak <lslezak@suse.cz> [Aug 21. 2009 11:47]:
Web UI (webclient) ================== - testsuite - design the UI (talk to mschmidkunz), may be different for System vs. Custom services
The question is if vendors would like to change "Custom Services" to a better name (with real service name).
The'll certainly do.
With current implementation they need to change the name directly in .yml config file. Is that OK?
I'd guess so. But how does this match with translations ?
Currently, there's one shortcuts.yml in 'services' plugin, containing items for system services and custom services. Better solution could be: Create a new 'almost-empty' plugin custom-services (on webclient side). Such plugin would basically contain only its shortcuts.yml, example one would look like this: main: url: /services?custom=1 groups: [ Services ] tags: [ init, script, service ] title: Custom Service description: Manage custom service (So it's pointing to standard services plugin, which contains the actual functionality). Such plugin would be easily packaged in separate package (yast2-webclient-custom-services), and thus also easily available to include/exclude from control center. Vendor installing such package could only edit this one file to show the name of vendor specific service directly in the control center: main: title: IBM Service description: This is a big and blue service start and stop tool (ideally also the icon, currently we expect them in global webclient/public/icons directory) Directory structure looks this way: .../web-client/plugins/custom_services> ls -1 app config package README shortcuts.yml Looks like that such simple plugin without any real functionality is possible, but it is registered only when it contains "app" directory (it can be empty, though). Does anyone know if such requirement is necessary from the rails side? Or how does control center code know about list of available plugins? Jiri -- Jiri Suchomel SUSE LINUX, s.r.o. e-mail: jsuchome@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@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On 2.9.2009 15:35, Jiří Suchomel wrote:
Such plugin would be easily packaged in separate package (yast2-webclient-custom-services), and thus also easily available to include/exclude from control center. Vendor installing such package could only edit this one file to show the name of vendor specific service directly in the control center:
main: title: IBM Service description: This is a big and blue service start and stop tool
(ideally also the icon, currently we expect them in global webclient/public/icons directory)
BTW Duncan has added an overlay to web-client so plugins can also contain public/ directory. The custom service package can contain also an icon. -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@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@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Ladislav Slezak schrieb:
On 2.9.2009 15:35, Jiří Suchomel wrote:
Such plugin would be easily packaged in separate package (yast2-webclient-custom-services), and thus also easily available to include/exclude from control center. Vendor installing such package could only edit this one file to show the name of vendor specific service directly in the control center:
main: title: IBM Service description: This is a big and blue service start and stop tool
(ideally also the icon, currently we expect them in global webclient/public/icons directory)
BTW Duncan has added an overlay to web-client so plugins can also contain public/ directory. The custom service package can contain also an icon.
Yes, you are right: http://en.opensuse.org/YaST/Web/Development/TrainingKit#Add_new_images.2C_ic... -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (4)
-
Jiří Suchomel -
Klaus Kaempf -
Ladislav Slezak -
Stefan Schubert