On Wed, 2008-10-08 at 15:15 +0200, Lars Marowsky-Bree wrote: > On 2008-10-07T23:33:14, Xinwei Hu <[EMAIL PROTECTED]> wrote: > > > em. > > Not always so. GUI calls the crm shell in a lot of scenarios. > > Exactly. But it should be so. At least, I'd like it to be so ;-) Most of the management functionalities have been reimplemented through invoking crm_* command. It's no difference comparing with calling crm shell but forking one less time.
> > Calling the crm shell and logging which commands were called, instead of > directly modifying the XML via the CIB libraries, allows users to use > the log from the GUI for building up their own setup scripts, improves > traceability & debugging, and ensures uniformity between GUI and CLI. > > > But still, it provides an XML view so that user can interact with xml > > snip directly. > > Sure. If users edit the XML directly, this is not directly possible - > though even then the GUI could use the CLI to update the (shadow) CIB > and commit changes. We might need more options provided by the API of cib cmds, such as query cib locally before the DC is elected to prevent the request from hanging there. Maybe we could just use cibadmin directly. But there's still another promblem. For now I use regular expressions to check the parameters given by the frontend to avoiding security issues when the backend executing system shell. Though it's more difficult to make sure a string expressing a CIB object is sanity. I don't really want to bring security leaks before we have a good solution. Regards, -- Yan Gao China R&D Software Engineer [EMAIL PROTECTED] Novell, Inc. SUSE® Linux Enterprise 10 Your Linux is ready http://www.novell.com/linux _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
