July 2010 - YaST Development - openSUSE Mailing Lists

[yast-devel] additional requirement for WebYaST: static hostname
by Jiří Suchomel 22 Jul '10

22 Jul '10

Hi! We've already talked about it, but it is nowhere written, so I'm putting it into this mail. When machine is joined to Active Directory domain, it is important its hostname does not change. On regular YaST-managed system, we can configure dynamic network settings, while keep hostname static. This is not possible in current WebYaST, and it would be good to have such option. Than we could advice customers to a) have such DHCP setup that does not change the hostname for given IP b) or confiure DHCP + static hostnames on the clients Jiri -- 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: YaST:Web open
by Josef Reidinger 22 Jul '10

22 Jul '10

Hi, after release is YaST:Web again open. Feel free to submit new version there. Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, parts of webyast -- 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 for Appliance Toolkit 1.1 Beta2 released
by Josef Reidinger 21 Jul '10

21 Jul '10

WebYaST for Appliance Toolkit 1.1 Beta2 Release Notes About WebYaST ============= This is the first public release of WebYaST for Appliance Toolkit 1.1, combining improved modules from the SP1 release with newly developed functions. WebYaST is a simple, easy to use, web-based administration tool targeted at casual Linux administrators. About this release ================== WebYaST for Appliance Toolkit 1.1 is available as an repository during appliance build. Repository is in http://dist.suse.de/ibs/SUSE:/SLE-11-SP1:/GA:/Products:/Test/standard/ ( internal only ) The WebYaST team has also made available a vmware demo appliance: http://www.suse.de/~jreidinger/webyast/SLES_11_SP1__webyast.i686-0.0.1.vmx.… (201MiB) (public available) (due to bug in studio it doesn't contain vmx, but it is not mandatory) This release includes the following modules ([*] == new module/function compared to SP1) - Administrator root password, forward mails to an external account - Eula display product EULA - Mail configure outgoing mail server - Patch and update show system patch status update system selective update - Software repositories manage software repositories - Registration register system against Novell Customer Center - Users manage local users - Services manage system services (/etc/init.d) manage custom service - Firewall simple firewall configuration - Network simple network configuration DNS, Hostname Routing - Status display system health status (cpu, network, disk) display system logs navigation option in logfile viewer - Time and date configure time and date can set hardware clock format (UTC/localtime) can set Ntp server - Roles Management [*] allows create role, assign to the role permissions and assign role to user - LDAP [*] configure LDAP and get users from it - ActiveDirectory [*] configure users from activeDirectory Known Bugs ========== Please report bugs via https://bugzilla.novell.com/enter_bug.cgi?product=WebYaST;format=guided There are already a couple of bugs known for the release, the major ones are: - After configuration samba users yastws service must be restarted to refresh user database (bnc#622897) - missing module for kerberos configuration (common LDAP setup is to authentificate againts Kerberos) - Roles assigned to ActiveDirectory users is not applied (bnc#624243) - Cannot install patches Happy testing! Your YaST teams, -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, parts of webyast -- 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 on the Wiki
by Martin Vidner 20 Jul '10

20 Jul '10

Hi Henne, on Tuesday you said you were transferring the content to http://wiki.opensuse.org/Portal:YaST . Do you plan to do more there or can we take over now? Now when I look at http://old-en.opensuse.org/Category:YaST and http://old-en.opensuse.org/Category:WebYaST , where should we put the content to ensure that it is not swept away by a well-meant reorganization? I guess that using the oS wiki for project development documents is somewhat unusual, perhaps we should use some other place? -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

4 13

[yast-devel] On WebYaST design
by Martin Kudlvasr 14 Jul '10

14 Jul '10

Hi all, today we (me, jsrain, jreidinger) had a small chat about what we'd like to change in webyast from the appliance users POV. This is the result. We think that these changes really should get into appliance toolkit 1.1. == Name the appliance == The "My appliance" string in header does not give any information to the user. Let's put there something useful - like the appliance name defined in Studio. == Don't mention localhost == In appliance toolkit 1.1, let's specialize the WebYaST interface for appliance use. The webyast-UI is always connected to the localhost webyast-WS (webservice, restful). We should hide this information from the user. == Move System Actions == System actions on the main controlpanel screen is a control, which will not be used very often. Let's make it a separate UI module. == Status into header == The status control in controlpanel is taking a lot of space and distracts from the module links/icons. Let's make it as small as possible (icons only or just a short text) and move it to the header. == Reuse status and updates == Display the old status (and updates) information immediately and exchange it for the new one when the new one is loaded. Don't use the waiting animations, they make the user wait and he should not be kept waiting in this situation. The ajax must not block the other use of the page, of course. == Categories of modules == By making the list of modules the main (only) part of the controlpanel page, we can use this to separate the modules into several categories (system, networking, users & groups, webyast settings, ...). == Show only usable modules == Currently an icon for module is shown the same way whether the user has permission to work with it or not. Let's hide (or display differently) those, which the user doesn't have full permissions for. == Speed up == Currently too many http requests to webyast-WS happen before a single page is displayed. Page loads are very slow. Josef (jreidinger) offered himself to work on this issue. == Send js and css together == We have many separate js and css files. Let's implement some system (or process) to collects them and send them in a single request. == Get rid of jquery styles == Currently we use many css files, but most of the useful definitions are in a few of them. For example we don't use much of the original jquery styles. Let's redefine what is left and use only our styles. Let's also gather them into 1 file using sass. == Remake selection controls == Our selection controls in Firewall, Users and Groups module uses 2 separate lists of items. User can click the items to switch between the 2 lists (selected items/unselected items). The original motivation was to have the selected items easily distinguished from the unselected items. But the 2 lists change often (layout moves) and the movements are confusing. Let's use a non- moving list of checkboxes with labels. Labels of checked checkboxes will be highlighted, so the user can quickly overview, which items are selected. == Popup notes == Let's start to use popup notes to give user more information when he hovers over a control. Let's use it in controlpanel for each module icon, in selection controls to say, what's going to happen, in navigation buttons to say, what's going to be saved or lost. Let's give user this additional information in a way which doesn't clutter the page. == You can change this later == When using Studio, I really liked that I was informed that the name of appliance was not fixed (and could be changed later). We should tell the user during Firstboot (basesystem setup) that the chosen values can be changed later. == Headline whitespace == We use too much whitespace around our module headlines (those with the module icon). We can move the whole headline into header, or just save the space around it. == Show unsaved changes == The user can forget or not feel the need to save his changes. This can happen in a multi-tab form for example. We should inform the user that he is leaving some changes unsaved. We can do it by giving a special highlight to the Save button (with a corresponding popup note) when user makes the first change. We can treat the Back link in a similar way. == Use headline as breadcrumbs == In some modules there are more than 1 page and the user often wants to go to the root page of the module. The Back link in navigation buttons can be at the bottom of the page (which means scrolling). Let's use the module headline as breadcrumbs - by clicking pieces of the headline user can go up in the module. == Highlight active controls == Whenever some control is changeable, it should react on hover. This applies particularly to accordions. == Reduce the frames == There are many border frames on a single page. Let's reduce it (ultimately to 0). There is no need to have them other that they sometimes look nice. == All status graphs at once == To get a specific status information it takes several clicks with long page/partial loads between them. An 1 page overview of all status graphs would be really helpful. The graphs would have to be returned fast. This calls for asynchronous generation of the status data. Let's generate them regularly, show user the old ones immediately and then exchange them when the new ones are generated. == Separate logs view == System logs does not fit well with the other parts of status. They should be viewed separately. Either in a different tab or in a different UI module. == Waiting animations == Use of waiting/hourglass animations is inconsistent between webyast modules. Let's unify it in a similar way to how we prevent Submit button doubleclick. Congratulations if you actually read all this list. We really think these changes are important. After some brief discussion, I'll file individual bugreports for all the items. Please comment! Martin Kudlvasr -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

5 5

[yast-devel] icons for webyast modules?
by Jiří Suchomel 14 Jul '10

14 Jul '10

Hi, for AD+LDAP plugins, I had to find new icons. Of course I took the ones from YaST, but the question is what is the correct source for webYaST icons? I took ones (yast-samba-client.png, yast-ldap.png) from SLE11 theme package (theme/SLE/icons/48x48/apps/yast-ldap.png), is this the correct place? If so, what about other icons (currently residing in webyast-base-ui)? Are there from SLE theme as well? We definitely should have this consistent... Jiri -- 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 1

[yast-devel] Building WebYaST 1.1
by Martin Vidner 08 Jul '10

08 Jul '10

Hi, Later this summer we are going to release WebYaST 1.1, featuring user roles, LDAP, and Active Directory plugins. So far the development was done in Git only, but Pepa has started submitting packages to YaST:Web. We expect the first dirty build tomorrow and a build suitable for the QA team (who are Bcc'd) early next week. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

1 0

[yast-devel] Gtk Button Icons?
by Karl Eichwalder 07 Jul '10

07 Jul '10

On my 11.3 RC2 installation, the yast config modules (gtk ui) lack the small icon on buttons such as Cancel or Ok. Do you know the reason why? What's the default now on openSUSE? With or without icon? -- Karl Eichwalder R&D / Documentation 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 2

[yast-devel] branches?
by Arvin Schnell 05 Jul '10

05 Jul '10

Hi, how about making branches for openSUSE 11.3 and Code11 SP2? Some hackers here always had strong opinions about branching but I cannot recall those. Fact is that I have fixes now that coolo does not want in openSUSE 11.3. ciao 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

1 1

[yast-devel] AD + LDAP: new webyast plugins ready for testing
by Jiří Suchomel 02 Jul '10

02 Jul '10

Hi! Two new webyast plugins are already residing in git repository as well as in YaST:Web project webyast-ldap-* webyast-activedirectory-* Their task is configure the authentication against the network source (LDAP, AD). Testing the LDAP one is easy as we have LDAP servers in suse.de and suse.cz. So you can try to turn your LDAP authentication off :-) Active Directory configuration could be more problematic, but if you have time and AD domain available, I'd like to ask you to test it and report the results. The problematic part of AD plugin is that there are some time consuming actions going in the backend (and even repeating), so there's a possibility to time out. Another minus of both plugins is poor UI design, not even fitting our current level. You'll see. Jiri -- 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