Azure / Azure/AzureDatabricksBestPractices

Vnet IP Configuration - is that right?

Aperta
#7 1 commento 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Nessun dato sulla lingua
Stelle
470
Fork
181
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

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.

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.