I would like to start from user's point.
There are two ways:
1. Input a group with first resource, then add the second.
2. Input a group without resource, then add the first, then the second.
What we are discussing is such little defference from user's view.
And, what the user like to use mostly? I am not sure.

You may think, why not let user input all the resources one dialog(wizard, 
maybe)?
I think that dialog would be more like a kind of xml editor, or a pure 
configure tool.
User can using a xml editor to do that, if the user want to write the whole 
configuration at one time.
This kind of users (usually experts) may don't need GUI to configure the 
cluster.

However, the GUI can help them in monitoring the status of cluster and
management(start/stop resource, standby/active node,...)







Lars Marowsky-Bree wrote:
On 2006-06-21T05:40:52, [email protected] wrote:


Log Message:
The GUI creates meaningless placeholders first, which only in a second
step can be filled with content. Allow this for 2.0.6 so we don't have
to turn DTD validation off completely.


I'd like to re-raise my continued concern that a GUI workflow shouldn't
cause meaningless objects to be entered into the CIB. That's IMHO bad
style in general.

Further, as Andrew just reminded me, this causes an additional CIB
update in the cluster per each step, which seems harmless enough, but
also causes a PE/TE iteration. For _each_ step, as none is aggregrated.
That may or may not be desireable.

We need a better way than the current one, the GUI really needs to way
to aggregate some changes. If that was present, we wouldn't need to
create meaningless containers. (Which is NOT the same as full-scale
transactions.)

And no, I'll keep flogging this horse until it gets better.


Sincerely,
    Lars Marowsky-Brée



--
Best Regards,
Huang Zhen
Linux-HA, Linux Technology Center, China Systems & Technology Lab
China Development Labs, Beijing Tel: 86-10-82782244 Ext. 2845
Email: [EMAIL PROTECTED]
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

Reply via email to