> Well, it "works" in the sense that it produces a valid config file - but
> in many ways it would be better if it didn't, then you might notice the
> problem sooner. It won't work in the sense of doing anything useful. For
> example, if you have pool accounts called dteama, dteamb, dteamc etc
> YAIM will put in a mapping of all DNs to ".dteama". At most that will
> allow one user to get in (I'm not clear if the mapping algorithm allows
> null suffixes) but it certainly isn't what was intended.
yes, but the code is not making assumptions. A code cannot check
everything so the best tactic is to reduce the places where to check and
simplify the code. A configuration is difficult and error prone when it
requires to set coeherent values in different places like in this case the
VO is dteam, the sgm is dteamsgm, the pool accounts are dteamNNN, the
prefix is dteam.......
As I said if only fields were used and there was a prefix field this would
have been much easier to debug and the space for mistakes would be reduced
because the prefix wouldn't depend on an sgm field being there and numbers
being removed and......
If this user name scheme, i.e. all the accounts of a VO are prefixed with
the name of the VO, keep on being used another thing that can be done
to reduce mistakes is to enforce
VO name == VO user prefix
VO name is from site-info.def
I think I'll open a bug in savannah.
cheers
alessandra
>
>> If the fields in user.conf were the only thing used we'd have a much
>> simpler parsing and only 1 convention: each field is separated by a
>> colon. Which is reasonable. This wouldn't have avoided the original
>> problem, but it makes it easier to debug it (also because it
>> simplifies the code!).
>
> Even there I would say that the code reading it should validate the
> input and not just assume that it's correct. Right from the start of EDG
> a major complaint has been "configuration is difficult", and a large
> component of that is the fact that small mistakes can lead to very
> obscure failure modes.
>
> Stephen
>
--
********************************************
* Dr Alessandra Forti *
* Technical Coordinator - NorthGrid Tier2 *
* http://www.hep.man.ac.uk/u/aforti *
********************************************
|