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: Rhys Smith <>
  • To: Nick Roy <>
  • Cc: Scott Cantor <>, Thomas Scavo <>, Per-Entity Metadata Working Group <>
  • Subject: Re: [Per-Entity] distribution of aggregate metadata
  • Date: Wed, 10 Aug 2016 19:40:33 +0000
  • Accept-language: en-GB, en-US
  • Authentication-results: spf=none (sender IP is ) ;
  • Ironport-phdr: 9a23:Edf7WxXgKz03o2RypTuf5DL5O0DV8LGtZVwlr6E/grcLSJyIuqrYZhWFt8tkgFKBZ4jH8fUM07OQ6P+wHzFbqs/c+Fk5M7VyFDY9wf0MmAIhBMPXQWbaF9XNKxIAIcJZSVV+9Gu6O0UGUOz3ZlnVv2HgpWVKQka3HUNPK+/0Ao/fidisn6D3osWLIlZlmjenXrNzMBjz6CyZ9oxP2dMjee4NzU7vo3BLM95R1Cs8I0iUjj794Nu95phu734Wtv48oZ1uS6L/Kp44XKcQNzEnL2B9sPfrpAKFdg6O+ns0UGQNmVxBCE7Y70epDd/KriLmu78li2GhNsrsQOVxA2z64g==
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

By the way, if anyone wants to try a CDN version of the UK fed distribution
service (not particularly exciting, I must admit), I already have one set up
using the Azure CDN. I haven’t yet got our tooling to send a purge command to
manually refresh the CDN on publication of a new set of aggregates; it’s easy
to do, I just haven’t had time yet. Will be doing that soon then having a
more thorough play with it.

http://ukf-md-cdn.azureedge.net

Rhys.
--
Dr Rhys Smith
Chief Technical Architect, Trust & Identity
Jisc

T: +44 (0) 1235 822145
M: +44 (0) 7968 087821
Skype: rhys-smith
GPG: 0x4638C985
Lumen House, Library Avenue, Harwell Oxford, Didcot, OX11 0SG

jisc.ac.uk

Jisc is a registered charity (number 1149740) and a company limited by
guarantee which is registered in England under Company No. 5747339, VAT No.
GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill,
Bristol, BS2 0JA. T 0203 697 5800.

> On 10 Aug 2016, at 19:22, Nick Roy
> <>
> wrote:
>
>
>> On Aug 10, 2016, at 12:12 PM, Cantor, Scott
>> <>
>> wrote:
>>
>>> 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.
>
> Well, I just found out from Tom last week that TSG is planning an upgrade
> to the Ann Arbor network, in part motivated by the "storm" of network
> traffic that our metadata updates cause when clients fetch a new aggregate
> each business day. In that regard, trying out a CDN would probably help
> alleviate our demand on at least that one network. It would also gain us
> operational experience working with a CDN service. If I had my 'drothers,
> I would have two new ops staff already hired who would be part of this and
> gain operational knowledge from it. I don't think that will happen until
> later this year or next, so if IJ and others in TSG think they might be
> able to get some useful experience out of this, and that it would help with
> the network issue or in other ways, I'd be in support.
>
> Nick
>
>> -- Scott
>>
>

Attachment: smime.p7s
Description: S/MIME cryptographic signature




Archive powered by MHonArc 2.6.19.

Top of Page