On 11/08/2021 16:51, Rob Evans wrote:
Hi Hank,
Since a week has gone by and Gert's question of: "Most notably the "why?" part is still missing from the whole procedural discussion on the "how?"" I will ask it as well: Why? What problem are we trying to solve? The document posted does not address that question.
I don’t want to speak for the NCC, but the first 8 slides from the presentation at RIPE 82 provide some background.
<https://ripe82.ripe.net/presentations/72-RIPE-NCC-Cloud-Strategy-RIPE82.pdf>
In my limited experience, these drivers aren’t that uncommon as businesses consider moving services to various “cloud” offerings.
Cheers, Rob
Rob, Thanks for pointing out the PDF. Now to the reasons stated: a) resilience: what services have been knocked out that need further resilience? Perhaps RIPE NCC can make a list from the past 3 years of each service and how long that service was down so we can determine whether there is need for further resilience? Then we should compare that with some other major, important, well engineered service from any company that relies strictly on the cloud and see whether their uptime was better or worse than RIPE NCC's record. b) agility: perhaps the community can indicate here what services we requested that RIPE NCC was not able to provide in a timely fashion? c) focus on core business: every bullet listed on slide 8 is a reason for keeping services on-prem. Every one of the bullets on slides 3-8 can be argued to be incorrect or vague with little substance behind it. Regards, Hank