com.pulumi.azurenative.batch.inputs.NetworkConfigurationArgs Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of azure-native Show documentation
Show all versions of azure-native Show documentation
A native Pulumi package for creating and managing Azure resources.
// *** WARNING: this file was generated by pulumi-java-gen. ***
// *** Do not edit by hand unless you're certain you know what you are doing! ***
package com.pulumi.azurenative.batch.inputs;
import com.pulumi.azurenative.batch.enums.DynamicVNetAssignmentScope;
import com.pulumi.azurenative.batch.inputs.PoolEndpointConfigurationArgs;
import com.pulumi.azurenative.batch.inputs.PublicIPAddressConfigurationArgs;
import com.pulumi.core.Output;
import com.pulumi.core.annotations.Import;
import com.pulumi.core.internal.Codegen;
import java.lang.Boolean;
import java.lang.String;
import java.util.Objects;
import java.util.Optional;
import javax.annotation.Nullable;
/**
* The network configuration for a pool.
*
*/
public final class NetworkConfigurationArgs extends com.pulumi.resources.ResourceArgs {
public static final NetworkConfigurationArgs Empty = new NetworkConfigurationArgs();
@Import(name="dynamicVnetAssignmentScope")
private @Nullable Output dynamicVnetAssignmentScope;
public Optional> dynamicVnetAssignmentScope() {
return Optional.ofNullable(this.dynamicVnetAssignmentScope);
}
/**
* Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, which may lead to improved networking performance. For more details, see: https://learn.microsoft.com/azure/virtual-network/accelerated-networking-overview.
*
*/
@Import(name="enableAcceleratedNetworking")
private @Nullable Output enableAcceleratedNetworking;
/**
* @return Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, which may lead to improved networking performance. For more details, see: https://learn.microsoft.com/azure/virtual-network/accelerated-networking-overview.
*
*/
public Optional> enableAcceleratedNetworking() {
return Optional.ofNullable(this.enableAcceleratedNetworking);
}
/**
* Pool endpoint configuration is only supported on pools with the virtualMachineConfiguration property.
*
*/
@Import(name="endpointConfiguration")
private @Nullable Output endpointConfiguration;
/**
* @return Pool endpoint configuration is only supported on pools with the virtualMachineConfiguration property.
*
*/
public Optional> endpointConfiguration() {
return Optional.ofNullable(this.endpointConfiguration);
}
/**
* This property is only supported on Pools with the virtualMachineConfiguration property.
*
*/
@Import(name="publicIPAddressConfiguration")
private @Nullable Output publicIPAddressConfiguration;
/**
* @return This property is only supported on Pools with the virtualMachineConfiguration property.
*
*/
public Optional> publicIPAddressConfiguration() {
return Optional.ofNullable(this.publicIPAddressConfiguration);
}
/**
* 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. 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 cloudServiceConfiguration pools, only 'classic' VNETs are supported. For more details see: https://docs.microsoft.com/en-us/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration
*
*/
@Import(name="subnetId")
private @Nullable Output subnetId;
/**
* @return 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. 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 cloudServiceConfiguration pools, only 'classic' VNETs are supported. For more details see: https://docs.microsoft.com/en-us/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration
*
*/
public Optional> subnetId() {
return Optional.ofNullable(this.subnetId);
}
private NetworkConfigurationArgs() {}
private NetworkConfigurationArgs(NetworkConfigurationArgs $) {
this.dynamicVnetAssignmentScope = $.dynamicVnetAssignmentScope;
this.enableAcceleratedNetworking = $.enableAcceleratedNetworking;
this.endpointConfiguration = $.endpointConfiguration;
this.publicIPAddressConfiguration = $.publicIPAddressConfiguration;
this.subnetId = $.subnetId;
}
public static Builder builder() {
return new Builder();
}
public static Builder builder(NetworkConfigurationArgs defaults) {
return new Builder(defaults);
}
public static final class Builder {
private NetworkConfigurationArgs $;
public Builder() {
$ = new NetworkConfigurationArgs();
}
public Builder(NetworkConfigurationArgs defaults) {
$ = new NetworkConfigurationArgs(Objects.requireNonNull(defaults));
}
public Builder dynamicVnetAssignmentScope(@Nullable Output dynamicVnetAssignmentScope) {
$.dynamicVnetAssignmentScope = dynamicVnetAssignmentScope;
return this;
}
public Builder dynamicVnetAssignmentScope(DynamicVNetAssignmentScope dynamicVnetAssignmentScope) {
return dynamicVnetAssignmentScope(Output.of(dynamicVnetAssignmentScope));
}
/**
* @param enableAcceleratedNetworking Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, which may lead to improved networking performance. For more details, see: https://learn.microsoft.com/azure/virtual-network/accelerated-networking-overview.
*
* @return builder
*
*/
public Builder enableAcceleratedNetworking(@Nullable Output enableAcceleratedNetworking) {
$.enableAcceleratedNetworking = enableAcceleratedNetworking;
return this;
}
/**
* @param enableAcceleratedNetworking Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, which may lead to improved networking performance. For more details, see: https://learn.microsoft.com/azure/virtual-network/accelerated-networking-overview.
*
* @return builder
*
*/
public Builder enableAcceleratedNetworking(Boolean enableAcceleratedNetworking) {
return enableAcceleratedNetworking(Output.of(enableAcceleratedNetworking));
}
/**
* @param endpointConfiguration Pool endpoint configuration is only supported on pools with the virtualMachineConfiguration property.
*
* @return builder
*
*/
public Builder endpointConfiguration(@Nullable Output endpointConfiguration) {
$.endpointConfiguration = endpointConfiguration;
return this;
}
/**
* @param endpointConfiguration Pool endpoint configuration is only supported on pools with the virtualMachineConfiguration property.
*
* @return builder
*
*/
public Builder endpointConfiguration(PoolEndpointConfigurationArgs endpointConfiguration) {
return endpointConfiguration(Output.of(endpointConfiguration));
}
/**
* @param publicIPAddressConfiguration This property is only supported on Pools with the virtualMachineConfiguration property.
*
* @return builder
*
*/
public Builder publicIPAddressConfiguration(@Nullable Output publicIPAddressConfiguration) {
$.publicIPAddressConfiguration = publicIPAddressConfiguration;
return this;
}
/**
* @param publicIPAddressConfiguration This property is only supported on Pools with the virtualMachineConfiguration property.
*
* @return builder
*
*/
public Builder publicIPAddressConfiguration(PublicIPAddressConfigurationArgs publicIPAddressConfiguration) {
return publicIPAddressConfiguration(Output.of(publicIPAddressConfiguration));
}
/**
* @param subnetId 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. 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 cloudServiceConfiguration pools, only 'classic' VNETs are supported. For more details see: https://docs.microsoft.com/en-us/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration
*
* @return builder
*
*/
public Builder subnetId(@Nullable Output subnetId) {
$.subnetId = subnetId;
return this;
}
/**
* @param subnetId 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. 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 cloudServiceConfiguration pools, only 'classic' VNETs are supported. For more details see: https://docs.microsoft.com/en-us/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration
*
* @return builder
*
*/
public Builder subnetId(String subnetId) {
return subnetId(Output.of(subnetId));
}
public NetworkConfigurationArgs build() {
$.dynamicVnetAssignmentScope = Codegen.objectProp("dynamicVnetAssignmentScope", DynamicVNetAssignmentScope.class).output().arg($.dynamicVnetAssignmentScope).def(DynamicVNetAssignmentScope.None).getNullable();
return $;
}
}
}
© 2015 - 2024 Weber Informatics LLC | Privacy Policy