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/ncc-services-wg@ripe.net/
[ncc-services-wg] New on RIPE Labs: RIPE NCC and the Cloud - Let’s Start Again
- Previous message (by thread): [ncc-services-wg] New on RIPE Labs: RIPE NCC and the Cloud - Let’s Start Again
- Next message (by thread): [ncc-services-wg] New on RIPE Labs: RIPE NCC and the Cloud - Let’s Start Again
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Fri Jun 25 18:51:47 CEST 2021
>> avoiding vendor lock-in. I think that is a reasonable requirement. > How could we forget to mention that? Probably overlooked it because it > because it is soooooo obvious. to be sure to get some solutioneering in <g>, i do not see how one really gets to this place (well described by shane as being able to easily move between vendors) if one buys services above metal as a service (aka MASS). a side benefit of buying MAAS, is that this brings in emea vendors, not just aws, azure, or goog. randy
- Previous message (by thread): [ncc-services-wg] New on RIPE Labs: RIPE NCC and the Cloud - Let’s Start Again
- Next message (by thread): [ncc-services-wg] New on RIPE Labs: RIPE NCC and the Cloud - Let’s Start Again
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]