1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
|
# coding=utf-8
# --------------------------------------------------------------------------
# Copyright (c) Microsoft Corporation. All rights reserved.
# Licensed under the MIT License. See License.txt in the project root for
# license information.
#
# Code generated by Microsoft (R) AutoRest Code Generator.
# Changes may cause incorrect behavior and will be lost if the code is
# regenerated.
# --------------------------------------------------------------------------
from msrest.serialization import Model
class NetworkConfiguration(Model):
"""The network configuration for a pool.
:param subnet_id: The ARM resource identifier of the virtual network
subnet which the compute nodes of the pool will join. This is of the form
/subscriptions/{subscription}/resourceGroups/{group}/providers/{provider}/virtualNetworks/{network}/subnets/{subnet}.
The virtual network must be in the same region and subscription as the
Azure Batch account. The specified subnet should have enough free IP
addresses to accommodate the number of nodes in the pool. If the subnet
doesn't have enough free IP addresses, the pool will partially allocate
compute nodes, and a resize error will occur. The 'MicrosoftAzureBatch'
service principal must have the 'Classic Virtual Machine Contributor'
Role-Based Access Control (RBAC) role for the specified VNet. The
specified subnet must allow communication from the Azure Batch service to
be able to schedule tasks on the compute nodes. This can be verified by
checking if the specified VNet has any associated Network Security Groups
(NSG). If communication to the compute nodes in the specified subnet is
denied by an NSG, then the Batch service will set the state of the compute
nodes to unusable. For pools created with virtualMachineConfiguration only
ARM virtual networks ('Microsoft.Network/virtualNetworks') are supported,
but for pools created with cloudServiceConfiguration both ARM and classic
virtual networks are supported. If the specified VNet has any associated
Network Security Groups (NSG), then a few reserved system ports must be
enabled for inbound communication. For pools created with a virtual
machine configuration, enable ports 29876 and 29877, as well as port 22
for Linux and port 3389 for Windows. For pools created with a cloud
service configuration, enable ports 10100, 20100, and 30100. Also enable
outbound connections to Azure Storage on port 443. For more details see:
https://docs.microsoft.com/en-us/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration
:type subnet_id: str
:param endpoint_configuration: The configuration for endpoints on compute
nodes in the Batch pool. Pool endpoint configuration is only supported on
pools with the virtualMachineConfiguration property.
:type endpoint_configuration:
~azure.batch.models.PoolEndpointConfiguration
"""
_attribute_map = {
'subnet_id': {'key': 'subnetId', 'type': 'str'},
'endpoint_configuration': {'key': 'endpointConfiguration', 'type': 'PoolEndpointConfiguration'},
}
def __init__(self, **kwargs):
super(NetworkConfiguration, self).__init__(**kwargs)
self.subnet_id = kwargs.get('subnet_id', None)
self.endpoint_configuration = kwargs.get('endpoint_configuration', None)
|
