Hi, On Fri, Sep 12, 2008 at 01:10:37PM +0200, [EMAIL PROTECTED] wrote: > Dejan, > > thanks for replying ... > > > This should be taken care of, but I'm not sure if the solution > > you proposed is optimal. What I'm worried about is that people > > will simply forget to update the configuration file when they > > change the xen store. What would be great is to devise a way to > > have this happen automatically for certain xen configurations, > > i.e. those marked as managed by the cluster. I don't have any > > experience with the xen store. Any ideas? > > I wanted to ask about this after getting the first responses on the general > question. > With just adding the ability to use the new sxp format, a lot of people > might benefit from. > But having later on a solution that also synchronizes the xen store > frequently with the config file would be much better. The problem that I > see on this is that different people use different methods to adopt the > domU config. Some use the virt-manager, some use pure command line tools > and so on. So from my point as administrator I simply would add another > operation to the ocf resource agent like monitor that's maybe called > synhronize or so, that compares the xen store config on a time based > interval with the config file and if something has changed update that one. > I know the ocf resource agents because I have written a few for our company > (after attending heartbeat Session from Lars) but I'm not sure if the > operations a ocf script can support is limited. Adding such a new operation > might be an easy but dirty way, so not sure about this.
I don't think that'd be a right(tm) thing to do. Though, I still can't think of a right solution: how to keep the sxp file in sync with the xen store. The problem is that the configuration file is not the origin (the store is) and the xen store is not persistent. If you couple that with the problem of keeping the file in sync on all nodes where the VM can run... looks like a maintenance nightmare. On Fri, Sep 12, 2008 at 11:49:19AM -0400, Ciro Iriarte wrote: > 2008/9/12 Dejan Muhamedagic <[EMAIL PROTECTED]>: > > Hi, > > > > On Thu, Sep 11, 2008 at 09:52:09PM +0200, [EMAIL PROTECTED] wrote: > >> Just a question, are we both the only one interested in enhancing the xen > >> ocf resource agent to work with the sxp files ? I thought this posting > >> might result in a discussion about the enhancement and hopped to get other > >> opinions on it. > > > > Makes me wonder too ;-) > > > > Sorry, for being so late with the reply. > > > > This should be taken care of, but I'm not sure if the solution > > you proposed is optimal. What I'm worried about is that people > > will simply forget to update the configuration file when they > > change the xen store. What would be great is to devise a way to > > have this happen automatically for certain xen configurations, > > i.e. those marked as managed by the cluster. I don't have any > > experience with the xen store. Any ideas? > > > > Thanks, > > > > Dejan > > > > Leaving out the Xen store synchronization, this patch could add > support to load SXP configuration files. "xm create" and "xm new" seem > to be the same (both accept Python style and SXP config), but only "xm > new" makes the configuration persistent on the Xen Store (please > correct me)... Thanks for the patch, but if we go with support for the SXP configuration files, then I'd prefer to have the configuration type explicitly set, e.g. OCF_RESKEY_format or similar. Parsing python code is, well, not easy to do right. Thanks, Dejan > Regards, > Ciro > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
