shibboleth-dev - RE: resolver.xml scope default
Subject: Shibboleth Developers
List archive
- From: "Carmody, Steven" <>
- To: "Shib Design Team" <>
- Subject: RE: resolver.xml scope default
- Date: Thu, 12 Jun 2003 12:30:54 -0400
> Is it possible to use XML-Include stuff to pull the scoping
> information for resolver.xml from origin.properties?
>
I think the larger point is that we have to make the install process in
general easier, and less intimating, and ensure that there are fewer
"opportunities to make mistakes" embedded in the process. For reasons
that we're all familiar with, we haven't worried too much about this
until recently. But we all know that, even for relatively clueful
people, the install process can be long and arduous.
There are lots of places where it can be simplified and improved.
Unfortunately, tho, I don't think we can take the time right now to
identify them, and address them. We HAVE to get 1.0 out the door.....
One suggestion, tho, that may well be doable -- in the deploy guide
create a checklist -- a list of items (which are links) of the tasks
which have to be addressed when deploying an origin or target.
Hopefully, the list wouldn't be too long, but would be complete (eg
would include "edit resolver.xml to add appropriate scope value").
I think the current guide is complete (and in the early stages we needed
to ensure it was complete). But, at this point, some sections are more
"reference material" than install guide. And, I think its very easy for
the first time installer to get lost.
I'm somewhat hopeful that the checklist would look short because the
people who have done test installs of 1.0 have been able to do them
relatively quickly. Part of this is experience, part of it is that
we're cheating (ie not, in general, creating new keys and certs). I
think the major part, tho, is that we've managed to internalize the kind
of checklist I'm describing. And, I know in my own case, that checklist
isn't too long.
Thoughts?
------------------------------------------------------mace-shib-design-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at
http://archives.internet2.edu/
------------------------------------------------------mace-shib-design--
- resolver.xml scope default, RL 'Bob' Morgan, 06/11/2003
- RE: resolver.xml scope default, Scott Cantor, 06/11/2003
- RE: resolver.xml scope default, RL 'Bob' Morgan, 06/12/2003
- Re: resolver.xml scope default, Derek Atkins, 06/12/2003
- Re: resolver.xml scope default, Ryan Muldoon, 06/12/2003
- RE: resolver.xml scope default, Scott Cantor, 06/12/2003
- RE: resolver.xml scope default, Scott Cantor, 06/12/2003
- Re: resolver.xml scope default, Ryan Muldoon, 06/12/2003
- <Possible follow-up(s)>
- RE: resolver.xml scope default, Carmody, Steven, 06/12/2003
- RE: resolver.xml scope default, Scott Cantor, 06/12/2003
- RE: resolver.xml scope default, wassa, 06/12/2003
- RE: resolver.xml scope default, Scott Cantor, 06/11/2003
Archive powered by MHonArc 2.6.16.