As far as setting it up in the Assimilation project - that's completely
automatic. There is nothing to do. It does discovery, and then starts
monitoring it if the OCF agent is installed.
As far as setting it up in Pacemaker, etc. - a blog post would be
reasonable. I should add the meta-data before writing the blog post -
because Pacemaker needs it ;-). I should also eventually make use of
meta-data in the Assimilation project - but that will come later.
By the way, I patterned the metadata in my Query objects -- that is
graph nodes that describe queries, after the metadata in OCF - except
the Query object metadata is JSON instead of XML.
To correct a typo in the original note:
"Mine would also make a perfectly _fine_ init script".
In other words, it could easily serve both purposes.
In fact, it would make sense to distribute this as part of Neo4j. You
would have to install it in /usr/lib/ocf/resource.d/neotechnology/neo4j
or something similar. You could also install it under /etc/init.d/ as
well...
In my view, the provider of a system should ideally provide the scripts
that manage it under init and also as an HA resource.
On 12/21/2013 04:31 AM, Michael Hunger wrote:
> Would be cool to see a blog post on how to set it up and use it.
>
> Cool stuff.
>
> Michael
>
> On Saturday, December 21, 2013 5:16:41 AM UTC+1, AlanR wrote:
>
> Hi,
>
> I have a working OCF resource agent for Neo4j. OCF resource
> agents are
> basically supersets of LSB init scripts. Mine would also make a
> perfectly find init script.
>
> The main extra things are:
> You can configure them through environment variables - to support
> multiple instances and alternative configurations
> They support "real" monitoring, including multiple levels of
> monitoring difficulty/expense/depth
> They provide metadata describing how to configure them (I haven't
> added that to mine yet)
>
> Both the Pacemaker project and Red Hat's older cluster offerings
> support
> OCF resource agents.
>
> The code for this resource agent can be found here:
>
> http://hg.linux-ha.org/assimilation/file/ac5e22344a48/ocf/neo4j
> <http://hg.linux-ha.org/assimilation/file/ac5e22344a48/ocf/neo4j>
>
> This one supports two levels of monitoring depth - as we talked
> about my
> previous emails.
>
> I also have the code in the Assimilation project to recognize
> neo4j is
> running and automatically start monitoring it with this resource
> agent.
>
> So, now whenever I see neo4j, I start monitoring it for correct
> operation -- automatically ;-)
>
> [We do it for many other things as well, but the neo4j part seems
> most
> interesting to this mailing list].
>
> --
> Alan Robertson <[email protected]> - @OSSAlanR
>
> "Openness is the foundation and preservative of friendship... Let
> me claim from you at all times your undisguised opinions." -
> William Wilberforce
>
> --
> You received this message because you are subscribed to the Google
> Groups "Neo4j" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
--
Alan Robertson <[email protected]> - @OSSAlanR
"Openness is the foundation and preservative of friendship... Let me claim
from you at all times your undisguised opinions." - William Wilberforce
--
You received this message because you are subscribed to the Google Groups
"Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
