comanage-dev - [comanage-dev] on COs, COUs, and groups
Subject: COmanage Developers List
List archive
- From: Scott Koranda <>
- To: comanage-dev <>
- Subject: [comanage-dev] on COs, COUs, and groups
- Date: Tue, 3 Apr 2012 09:47:51 -0500
Hi,
We had been thinking of a CO and COU structure like this:
CO: LIGO Laboratory
COU: Caltech
COU: MIT
COU: LHO
COU: LLO
CO: LIGO Laboratory Collaborators
COU: GEO
COU: AEI
COU: Theory
COU: Experiment
COU: Cardiff
COU: UW-Milwaukee
COU: Syracuse
CO: Virgo
We need, however, some groups to have members across all COs
and COUs. A good example is the LIGO Identity Managment
Project. It has members from at least 2 different COs and
multiple COUs.
Right now the data model assumes a group is rooted in a CO. Is
that correct for all use cases?
Do we need a CMP wide option on whether groups must be
"rooted" (and hence only visible) to a CO?
Scott
- [comanage-dev] on COs, COUs, and groups, Scott Koranda, 04/03/2012
- Re: [comanage-dev] on COs, COUs, and groups, Benn Oshrin, 04/03/2012
- Re: [comanage-dev] on COs, COUs, and groups, Scott Koranda, 04/03/2012
- Re: [comanage-dev] on COs, COUs, and groups, Benn Oshrin, 04/03/2012
- Re: [comanage-dev] on COs, COUs, and groups, Scott Koranda, 04/03/2012
- Re: [comanage-dev] on COs, COUs, and groups, Benn Oshrin, 04/03/2012
Archive powered by MHonArc 2.6.16.