Feature changed by: Jiří­ Suchomel (jsuchome) Feature #309592, revision 3 Title: GUI for SLEPOS Requested by: Joachim Werner (joachimwerner) Description: Create a GUI for managing the SLEPOS admin server and setting up branch servers. The most obvious approach would be to make this a WebYaST module. But other technical approaches are welcome, too. This would be a nice project for anybody who wants to learn about hooking up a backend system (in this case the SLEPOS command line interface and LDAP) to a web application (e.g. Ruby on Rails or another framework of your choice). The goal for hackweek wouldn't be a perfect solution, just a first hack. + Discussion: + #1: Jiří­ Suchomel (jsuchome) (2010-06-02 15:51:31) + Is there any list of features that should be included? And tools that + are currently used for these tasks? -- openSUSE Feature: https://features.opensuse.org/309592

Feature changed by: Joachim Werner (joachimwerner) Feature #309592, revision 5 Title: GUI for SLEPOS Requested by: Joachim Werner (joachimwerner) Developer: (Novell) Description: Create a GUI for managing the SLEPOS admin server and setting up branch servers. The most obvious approach would be to make this a WebYaST module. But other technical approaches are welcome, too. This would be a nice project for anybody who wants to learn about hooking up a backend system (in this case the SLEPOS command line interface and LDAP) to a web application (e.g. Ruby on Rails or another framework of your choice). The goal for hackweek wouldn't be a perfect solution, just a first hack. Discussion: #1: Jiří­ Suchomel (jsuchome) (2010-06-02 15:51:31) Is there any list of features that should be included? And tools that are currently used for these tasks? + #2: Joachim Werner (joachimwerner) (2010-06-07 19:58:18) + For the hackweek focus it's basically up to you how much you want to + cover. + One approach would be taking the basic structure of the SLEPOS setup + from LDAP (this will give you all the org units (e.g. regions or + cities) and their branch locations as well as individual servers and + terminals. + To trigger actions in LDAP you could use the posAdmin command. + Of course one could as well write LDAP directly using a lower-level + LDAP library, but using the posAdmin command (or maybe the underlying + Perl modules) abstracts from that. + I think the most immediate benefit one can have from the UI would be + with automating very repetitive tasks, like creating all the entries + needed for a branch server. -- openSUSE Feature: https://features.opensuse.org/309592

Feature changed by: Jiří­ Suchomel (jsuchome) Feature #309592, revision 7 Title: GUI for SLEPOS Requested by: Joachim Werner (joachimwerner) Developer: (Novell) Description: Create a GUI for managing the SLEPOS admin server and setting up branch servers. The most obvious approach would be to make this a WebYaST module. But other technical approaches are welcome, too. This would be a nice project for anybody who wants to learn about hooking up a backend system (in this case the SLEPOS command line interface and LDAP) to a web application (e.g. Ruby on Rails or another framework of your choice). The goal for hackweek wouldn't be a perfect solution, just a first hack. Relations: Discussion: #1: Jiří­ Suchomel (jsuchome) (2010-06-02 15:51:31) Is there any list of features that should be included? And tools that are currently used for these tasks? #2: Joachim Werner (joachimwerner) (2010-06-07 19:58:18) For the hackweek focus it's basically up to you how much you want to cover. One approach would be taking the basic structure of the SLEPOS setup from LDAP (this will give you all the org units (e.g. regions or cities) and their branch locations as well as individual servers and terminals. To trigger actions in LDAP you could use the posAdmin command. Of course one could as well write LDAP directly using a lower-level LDAP library, but using the posAdmin command (or maybe the underlying Perl modules) abstracts from that. I think the most immediate benefit one can have from the UI would be with automating very repetitive tasks, like creating all the entries needed for a branch server. #3: Jiří­ Suchomel (jsuchome) (2010-06-23 07:53:09) Added attachment screenshot of YaST prototype (slepos_configuration. png) + #4: Jiří­ Suchomel (jsuchome) (2010-06-23 08:14:13) + So, I thought about implementing the prototype in YaST (which is + quicker), while the result could be used for planning of webYaST + module. The screenshot above shows what has been done: the layout was + proposed by SLEPOS guys, I actually implemented only read-only version + of the configurator. + Current layout might be bit overcrowded, it may be better to reduce the + number of subwindows. On the other hand, the point of this one was + probably to see as much information as possible in one screen. + Technically, the solution is using generic LDAP queries to read the + configuration, so in this state, no SLEPOS-specific tools were needed. + For writing, usage of posAdmin or some upcoming configuration method + would be needed. However, the lack of need for SLEPOS tools means that + current read-only version could be run from any machine, not from the + one where Administration server is required. + I hope this example could server as a study for possible later webYaST + module. The UI could be probably very similar (although it would more + fit in webYaST philosophy if it could be simplified). Technically, + reading part could be implemented similar to that of the YaST one, e.g. + using some ruby-ldap library  directly from rest-service. However, + writing needs the root access to target machine, for which new DBUS + service should be written, enveloping the real access to the system. + The acutal write could be done either by calling posAdmin or modifying + configuration files (the future solution proposed by SLEPOS team). + The advantage of such webYaST module (apart of the advantage of remote + browser access) is that it does not have to use the original YaST as a + backend, which means that package dependency could be reduced quite a + lot. Disadvantage of current webYaST is the performance, mainly caused + by XML parser used. +   -- openSUSE Feature: https://features.opensuse.org/309592