 |
 |
On 01/23/2013 11:36 PM, Christopher J. Walker wrote: > I also think that the operations-portal is de facto the best place to > put technical > information, and it should be recommended as the best technical means > of distributing this information, but I don't think we need to make it > a policy > requirement. I call these Maverick VOs. Is there a better, non-pejorative term? Maverick VOs are an issue. Sites can support any VO they like. It is only a (proposed) policy requirement for Approved VOs to be in the Operations Portal. This is because the Operations Portal facilitates standard change control functions that (e.g.) VomsSnooper or VOID cards etc. depend on. The process for keeping the Approved VOs document up to date depends on VomsSnooper, and VomsSnooper depends on the data in the Operations Portal. Changing that causes a plethora of technical impacts (believe it or not). At present, there is a big set of VOs in the Operations Portal, and a subset of those in the Approved VOs. If we wanted to have Approved VOs that are not in the Operations Portal we would need other repositories for those maverick VOs. This implies that we would need many separate repositories for the maverick VOs. Else we would need a centralized repository (a functional copy of the Operations Portal). And we'd need all the database editing, querying and formatting as well. In short, if we allow maverick VOs to be approved, we open a Pandora's box of admin difficulties. Let me know what you think. It can be done, but is it worth the candle? Cheers, Steve -- Steve Jones [log in to unmask] System Administrator office: 220 High Energy Physics Division tel (int): 42334 Oliver Lodge Laboratory tel (ext): +44 (0)151 794 2334 University of Liverpool http://www.liv.ac.uk/physics/hep/