Updates version with mentioning the scenario we are targeting
This commit is contained in:
Xintia Gyenge 2020-10-16 13:55:02 +02:00 коммит произвёл GitHub
Родитель 110709b3a9
Коммит eab88f7d0a
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4AEE18F83AFDEB23
1 изменённых файлов: 1 добавлений и 1 удалений

2
toc.md
Просмотреть файл

@ -187,7 +187,7 @@ More information: [Azure Virtual Datacenter: a network perspective](https://docs
## Select the Largest Vnet CIDR
*Impact: Very High*
> ***This recommendation only applies if you're using the Bring Your Own Vnet feature.***
> ***This recommendation only applies if you're using the Bring Your Own Vnet feature.***
Recall the each Workspace can have multiple clusters. The total capacity of clusters in each workspace is a function of the masks used for the workspace's enclosing Vnet and the pair of subnets associated with each cluster in the workspace. The masks can be changed if you use the [Bring Your Own Vnet](https://docs.azuredatabricks.net/administration-guide/cloud-configurations/azure/vnet-inject.html#vnet-inject) feature as it gives you more control over the networking layout. It is important to understand this relationship for accurate capacity planning.