hi,

I understand what you mean, and this makes sens. I dislike a lot tcl/tk + 
perl-Qt3 either. perl-Qt3 will be a big problem to replace when distro will 
abandon qt3 support.
the Tcl/tk interface is for sure not intuitive and buggy. package descriptions 
are truncated, setup networking buttons are half freezed when MAC aquisition is 
on, and such, but for the moment, it works, so, yes, V7 could include this 
change.
For the database, I agree that mysql is big comared to its load, but it's easy 
to manage by everyone and it works fine. Moving to another database or berkley 
db system will make it harder to update the database by hand in case of problem 
(and need developpement). For sure, the end user is not meant to manage by hand 
the database, but perfection is not in this world and sometimes it's cool to 
have the ability to do a mysql -u root oscar...

IMHO, the priorities for the moment are:

- Make a stable release for centos-6 and other recent distros (debian, fedora, 
maybe suse). V6.2 ?
- fix build system so external missing packages like perl-Qt, systemimager, 
aftp, bittorent, flamethower, ...are built
  fix build system so opkg are in pkgsrc allowing a package upgrade without 
requiring a new oscar release. V6.3 ?
- Fix packages like gridengine (sge is broken and obsolete) and maybe others 
V6.4
- Add cluster management utilities (put nodes offline for maintenance, move 
jobs, hybernate cluster, update cluster (packages), deploy rpms, ...) V6.5
- Prepare for the future: pre-V7
   - Update / rewrite GUI
   - move to modern architecture (systemd, ...)
   - detach database backend

Best regards,

Olivier.

PS: I'm still working on systemimager (stuck with dhcp that fails to detect 
broadcast interface)

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

________________________________________
De : Chuck Ritter [cfr...@psu.edu]
Date d'envoi : mardi 19 mars 2013 13:09
À : oscar-devel@lists.sourceforge.net
Objet : Re: [Oscar-devel] RE : OSCAR GUI

A reasonable perspective. Those are all good things to prioritize.

DongInn seemed to be suggesting a GSoC project. I think GSoCs are more
geared toward something like a new interface and not general code
maintenance. In that respect, I think, a new GUI might still be a good
project (particularly if the oscarcli was fixed in the process).

I'm not a big java fan either. Javascript is not java, but java may
have been implied anyway. The current Tk interface works, but is not
always intuitive. As for the databases, I just wanted to point out the
duplication of function and suggest something lighter or integrated. I
think these database instances have so few writes that they could be
replaced with something like sleepycat. Granted, mysql has not been a
big problem to date, but it is a complex beast and complexity can
introduce problems. By saying v7.0, I intended to imply not a high
priority.

On Tue, Mar 19, 2013 at 5:13 AM, LAHAYE Olivier <olivier.lah...@cea.fr> wrote:
> Hi,
>
> IMHO, Java is hipe and  fashion, but leads to many eadaches concerning 
> compatibility, to the point that each application requireing java is forced 
> to ship its own java machine. I end up having 3 or 4 java machines installed 
> on my systems (matlab, netbackup, ....) A pure nightmare when you need to 
> upgrade.
> More over, oscar is already written in many languages (perl, python, bash, 
> tcl, Tk, C, C++, ...), and I don't think that adding one more language will 
> ease maintenance.
>
> Regarding the database, mysql is used by systeminstaller and oscar, and I 
> don't understand why removing it could be a progress. It's a stand alone 
> database and can be secured easily.
>
> I agree that jobmonarch using postgresql is not cool (2 database engines 
> while one is far sufficient), but it's an upstream choice unfortunately. I've 
> been in contact with developpers, and the project is not dead. v0.4 will be 
> released some day. The TODO says that in the future, we should be able to 
> choose the database backend. (no work done yet though).
>
> I understand that GUI is sometimes a problem, but honestly, on a cluster, you 
> often have access to a X display on the local network. I think that there are 
> far more urgent stuff to work on like:
> - having grindengine that works (current sge package is completely broken)
> - having blcr build for dkms
> - having a maintenance mode to:
>   - put online or offline nodes for maintenance
>   - move jobs (hybern,ate on a node and restore on another: usefull to 
> isolate a node for maintenance)
>   - update nodes
>   - deploy new packages.
>   - stop the cluster hybernating nodes using a simple click.
>   - manage work queues
> - having a console log...
>
> My 2 cents,
>
> Olivier.

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to