Skip to Content.
Sympa Menu

per-entity - Re: [Per-Entity] distribution of aggregate metadata

Subject: Per-Entity Metadata Working Group

List archive

Re: [Per-Entity] distribution of aggregate metadata


Chronological Thread 
  • From: Scott Koranda <>
  • To: "Cantor, Scott" <>
  • Cc: Tom Scavo <>, Per-Entity Metadata Working Group <>
  • Subject: Re: [Per-Entity] distribution of aggregate metadata
  • Date: Thu, 11 Aug 2016 12:33:11 -0500
  • Ironport-phdr: 9a23:hw8GcB0T0HqtrX1AsmDT+DRfVm0co7zxezQtwd8ZsesfLfad9pjvdHbS+e9qxAeQG96Eu7QZ0KGP7ujJYi8p39WoiDg6aptCVhsI2409vjcLJ4q7M3D9N+PgdCcgHc5PBxdP9nC/NlVJSo6lPwWB6lX71zMZGw3+OAxpPay1X9eK14Xkn9y1rtf4agNUgyD5KYh5Kwmq502FvcAQnYx4bPwZzQDU5HZEZrIF63lvIAeolBHg+o+T+4Rq9ShZ86Y69MlaWKP2dow3SLVZCHItNGVjt56jjgXKUQbavihUaW4RiBcdRlGdtBw=

> > I think there would have to be some real benefit (not just experience
> > gained) before we would consider doing that. From where I sit, the
> > current distribution method Just Works (TM) so I have to turn around
> > and ask InCommon deployers: Is there something about the current
> > distribution method that is suboptimal or not working for you (apart
> > from the size of the aggregate of course)?
>
> I don't think the point was to help us (and nobody is
> suggesting the URL would change), so if Ops doesn't think
> incorporating a cloud/CDN delivery strategy under cover of a
> name controlled by InCommon is a useful step for its own MDQ
> direction-setting, I don't think any of us would motivate
> it.

Right.

I understand your sentiment Tom that the current method "Just
Works", and you need to be conservative about risks to
delivering the aggregate, but I think the experience gained
could be quite valuable.

It isn't the role of this working group to tell TSG/Ops how to
deliver a service and how to manage its organizational risk,
but I think we should be identifying opportunities that could
fit into a roadmap.

Thanks,

Scott K



Archive powered by MHonArc 2.6.19.

Top of Page