From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] SAP resource agents
Date: Mon, 17 Nov 2008 08:54:16 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0811170851100.7841@trider-g7> (raw)
In-Reply-To: <200811121356.38965.hlawatschek@atix.de>
Hi Mark,
On Wed, 12 Nov 2008, Mark Hlawatschek wrote:
> Hi,
>
> we have made another step to improve the way how to run SAP on a Red Hat high
> availability cluster.
thanks for the submission.
>
> As a result, you'll find the latest versions of the following resource agents
> and event-scripts attached:
A few things tho...
> Many thanks to Alexander Krauth for providing the SAP resource agents.
>
> - SAPDatabase:
> The purpose of the resource agent is to start, stop and monitor the database
> instance of a SAP system.
>
> - SAPInstance:
> Manages a single SAP Instance as a High-Availability resource.
on what platform have those scripts been tested?
> - follow-service.sl
> Implements the "follow service" logic based on rgmanagers RIND event
> mechanism. This is needed to implement a replicated enqueue failover
> scenario.
depending on what branch this should land, we need to look into the
licence. master/stable2 are now gpl2+. New submission should respect that
licence. Updating old bits (like the SAP* files is still ok with the old
licence for now).
I'd also like to have a proper diff on top of the branch with explanation
of the changes. Some of them are related to defaults and depending where
they should be applied, it might be important to review them all together.
Fabio
--
I'm going to make him an offer he can't refuse.
prev parent reply other threads:[~2008-11-17 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 12:56 [Cluster-devel] SAP resource agents Mark Hlawatschek
2008-11-17 7:54 ` Fabio M. Di Nitto [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0811170851100.7841@trider-g7 \
--to=fdinitto@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).