Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Co-locating grouper, fail-over and replication

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Co-locating grouper, fail-over and replication


Chronological Thread 
  • From: Gabby Capitanchik <>
  • To: "GW Brown, Information Systems and Computing" <>
  • Cc: Grouper Users Mailing List <>
  • Subject: Re: [grouper-users] Co-locating grouper, fail-over and replication
  • Date: Wed, 13 May 2009 12:37:38 +0100
  • Organization: The University of Edinburgh

Sorry, my reply wasn't as clear as it should have been. All databases and applications are co-located.

cheers

Gabby

GW Brown, Information Systems and Computing wrote:
What do you currently do with databases?

Gary

--On 13 May 2009 11:57 +0100 Gabby Capitanchik <> wrote:

Hi,

All of our application/system are co-located for disaster recovery
reasons. So we'd probably have to look at creating something to allow
Grouper to be clustered.

We are looking to a provisioning system that will map groups to services.
For example, group A may have access to AD supported services and our
Central Wiki service but may not have access to Student, related,
services.

Cheers

Gabby

GW Brown, Information Systems and Computing wrote:
Gabby,

I'm afraid not.

Are you concerned with database availability or UI/WS? Are you planning
for consumer applications to access grouper directly or do you plan to
provision groups to LDAP / Active Directory?

Gary

--On 13 May 2009 11:11 +0100 Gabby Capitanchik
<>
wrote:

Gary,

Thanks for your reply, I don't suppose you are aware of any other users
of Grouper who have looked into clustering Grouper?

Cheers

Gabby

GW Brown, Information Systems and Computing wrote:
Hi Gabby,

There is no clustering at present. All data is held in a central
database so database specific synchronisation / clustering / failover
techniques can be used to ensure high availability.

The API (and UI and Web service components) can be installed on
multiple machines. The UI and WS can be load balanced (sticky
sessions).

We are currently working on 'notifications' and improved provisioning
capabilities so it may become possible to propagate changes from one
Grouper instance to another, though additional work might be needed to
ensure that IDs were propagated appropriately.

Gary

--On 12 May 2009 11:20 +0100 Gabby Capitanchik
<>
wrote:

Hi,

I was wondering if it was possible to deploy Grouper across multiple
servers to allow for fail over. If Grouper was deployed in that what
would be the best way to replicate groups and group memberships and
any changes to those.

Cheers

Gabby Capitanchik

--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.




----------------------
GW Brown, Information Systems and Computing



--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.




----------------------
GW Brown, Information Systems and Computing



--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.




----------------------
GW Brown, Information Systems and Computing



--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.




Archive powered by MHonArc 2.6.16.

Top of Page