Azure / Azure/AzureDatabricksBestPractices

Vnet IP Configuration - is that right?

Abierto
#7 1 comentario 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Sin datos de lenguaje
Estrellas
470
Forks
181
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

The vnet recommendation doesn't quite make sense to me.
It seems to be telling me that to get the max number host I should use a /16 vnet address. So for example:

10.0.0.0/16 - this will give the 255*255 - 2 assignable host / = aprox 16000 cluster hosts.
However I don't understand the table. Next it seems to be telling me that I should subnet the /16 into /18 for the public and private sub net. If I do that then the table doesn't make sense.

The public hosts will be slashed - so how can I achieve 16000 cluster host (64000 host IP's) on /18 subnet?
So based on the info the document following that it indicates that I need to create 2 subnets in the vnet range with a 2 borrowed subnet bits. It says the private and the public borrowed bits have to be the same:

private: 10.0.0.0/18 -> That's not 64000 host ip's? This doesn't make any sense to me

Can you give an example for public and private subnet values that achieve the maximum available clusters?

The best you can achieve is aprox 4000 cluster host (/4) but that wastes an awful lot IP's in the private range.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.