[an error occurred while processing the directive]
cosign-discuss at umich.edu
general discussion of cosign development and deployment
 

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: COSIGN: service name policies?



On Thu, 25 Mar 2004, Jim Zajkowski wrote:

> > Other approaches?
>
> We've named ours (where necessary) lsi-something, like lsi-nagios,
> lsi-intranet, etc.

I think the "cosign-" at the start of each service name is unnecessary
filler.  We've been naming cosign services similar to how LSI has,
but I'd rather than having a lot of domain info, I've been envisioning
"UNIT-SERVICE".  For example lsa-footprints (for a College-run service)
math-www (for www.math.lsa.umich.edu), math-instruct or math-egrade
(for instruct.math.lsa.umich.edu, which runs the eGrade software), etc.
I think this is easier than cosign-instruct.math.lsa (assuming that
serice names won't be used for anything other than cosign services
and that there is only one Math department at the UofM, of course).

                Mark Montague
                LS&A Information Technology
                markmont@xxxxxxxxx



[an error occurred while processing the directive]