On Wed, 2019-09-04 at 10:07 +0200, Jehan-Guillaume de Rorthais wrote: > On Tue, 03 Sep 2019 09:35:39 -0500 > Ken Gaillot <kgail...@redhat.com> wrote: > > > On Mon, 2019-09-02 at 15:23 +0200, Ulrich Windl wrote: > > > Hi! > > > > > > Are there any recommendations where to place (fixed content) > > > files an > > > RA uses? > > > Usually my RAs use a separate XML file for the metadata, just to > > > allow editing it in XML mode automatically. > > > Traditionally I put the file in the same directory as the RA > > > itself > > > (like "cat $0.xml" for meta-data). > > > Are there any expectations that every file in the RA directory is > > > an > > > RA? > > > (Currently I'm extending an RA, and I'd like to provide some > > > additional user-modifiable template file, and I wonder which path > > > to > > > use) > > > > > > Regards, > > > Ulrich > > > > I believe most (maybe even all modern?) deployments have both lib > > and > > resource.d under /usr/lib/ocf. If you have a custom provider for > > the RA > > under resource.d, it would make sense to use the same pattern under > > lib. > > Shouldn't it be $OCF_FUNCTIONS_DIR?
Good point -- if the RA is using ocf-shellfuncs, yes. $OCF_ROOT/lib should be safe if the RA doesn't use ocf-shellfuncs. It's a weird situation; the OCF standard actually specifies /usr/ocf, but everyone implemented /usr/lib/ocf. I do plan to add a configure option for it in pacemaker, but it shouldn't be changed unless you can make the same change in every other cluster component that needs it. > Could this be generalized to RA for their > own lib or permanent dependencies files? The OCF standard specifies only the resource.d subdirectory, and doesn't comment on adding others. lib/heartbeat is a common choice for the resource-agents package shell includes (an older approach was to put them as dot files in resource.d/heartbeat, and there are often symlinks at those locations for backward compatibility). Since "heartbeat" is a resource agent provider name, and the standard specifies that agents go under resource.d/<provider-name>, it does make sense that lib/<provider-name> would be where RA files would go. -- Ken Gaillot <kgail...@redhat.com> _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
