This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ncc-services-wg] New on RIPE Labs: RPKI Repositories and the RIPE Database in the Cloud
- Previous message (by thread): [ncc-services-wg] New on RIPE Labs: RPKI Repositories and the RIPE Database in the Cloud
- Next message (by thread): [ncc-services-wg] New on RIPE Labs: RPKI Repositories and the RIPE Database in the Cloud
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Wed May 12 09:19:11 CEST 2021
Hi, On Mon, May 10, 2021 at 01:40:07PM +0200, Alun Davies wrote: > The mission critical services the RIPE NCC provides to the Internet > community require a solid technical foundation. In this new article > on RIPE Labs, Felipe Silveira looks at plans to use cloud infrastructure > as a means to that end. The full article is available here: As a member, I do not want the RIPE NCC to spend our money on "give away control on critical services". Use of cloud services (or any other "outsourced infrastructure") is something I consider acceptable as a *backup* in case of something catastrophic happening to the RIPE NCC operated machines, to restore services to members and community quicker. Using cloud services generally implies - loss of control --> so the NCC *must* be primary authority on all data, and the cloud can only be a cache - loss of contact and responsibility --> if a NCC provided service does not work, I do not want to talk to a cloud provider hotline, or hear from the NCC "well, there is nothing we can do, something in the cloud is broken" All this cloudstuff is really great if you need "elastic services" (like, when the big run on the last IPv4 space starts, scale up the LIR portal to 200 instances - oh, wait, this opportunity got missed), or "low latency for high bandwidth content delivery" (so, yeah, ... no?). But for the services the NCC provides, "cloud" sounds like "yeah, someone else to blaim if it explodes", and this is not why we give the NCC money. (And no, there is not much trust from my side, since the ticket system is *still* a major annoyance in our day to day dealing with the NCC - despite promises, two years ago, to make this more usable) Gert Doering -- voting LIR contact -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: </ripe/mail/archives/ncc-services-wg/attachments/20210512/c0907cb5/attachment.sig>
- Previous message (by thread): [ncc-services-wg] New on RIPE Labs: RPKI Repositories and the RIPE Database in the Cloud
- Next message (by thread): [ncc-services-wg] New on RIPE Labs: RPKI Repositories and the RIPE Database in the Cloud
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]