#[non_exhaustive]pub struct CreateFileSystemOntapConfiguration {Show 13 fields
pub automatic_backup_retention_days: Option<i32>,
pub daily_automatic_backup_start_time: Option<String>,
pub deployment_type: Option<OntapDeploymentType>,
pub endpoint_ip_address_range: Option<String>,
pub fsx_admin_password: Option<String>,
pub disk_iops_configuration: Option<DiskIopsConfiguration>,
pub preferred_subnet_id: Option<String>,
pub route_table_ids: Option<Vec<String>>,
pub throughput_capacity: Option<i32>,
pub weekly_maintenance_start_time: Option<String>,
pub ha_pairs: Option<i32>,
pub throughput_capacity_per_ha_pair: Option<i32>,
pub endpoint_ipv6_address_range: Option<String>,
}Expand description
The ONTAP configuration properties of the FSx for ONTAP file system that you are creating.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.automatic_backup_retention_days: Option<i32>The number of days to retain automatic backups. Setting this property to 0 disables automatic backups. You can retain automatic backups for a maximum of 90 days. The default is 30.
daily_automatic_backup_start_time: Option<String>A recurring daily time, in the format HH:MM. HH is the zero-padded hour of the day (0-23), and MM is the zero-padded minute of the hour. For example, 05:00 specifies 5 AM daily.
deployment_type: Option<OntapDeploymentType>Specifies the FSx for ONTAP file system deployment type to use in creating the file system.
-
MULTI_AZ_1- A high availability file system configured for Multi-AZ redundancy to tolerate temporary Availability Zone (AZ) unavailability. This is a first-generation FSx for ONTAP file system. -
MULTI_AZ_2- A high availability file system configured for Multi-AZ redundancy to tolerate temporary AZ unavailability. This is a second-generation FSx for ONTAP file system. -
SINGLE_AZ_1- A file system configured for Single-AZ redundancy. This is a first-generation FSx for ONTAP file system. -
SINGLE_AZ_2- A file system configured with multiple high-availability (HA) pairs for Single-AZ redundancy. This is a second-generation FSx for ONTAP file system.
For information about the use cases for Multi-AZ and Single-AZ deployments, refer to Choosing a file system deployment type.
endpoint_ip_address_range: Option<String>(Multi-AZ only) Specifies the IPv4 address range in which the endpoints to access your file system will be created. By default in the Amazon FSx API, Amazon FSx selects an unused IP address range for you from the 198.19.* range. By default in the Amazon FSx console, Amazon FSx chooses the last 64 IP addresses from the VPC’s primary CIDR range to use as the endpoint IP address range for the file system. You can have overlapping endpoint IP addresses for file systems deployed in the same VPC/route tables, as long as they don't overlap with any subnet.
fsx_admin_password: Option<String>The ONTAP administrative password for the fsxadmin user with which you administer your file system using the NetApp ONTAP CLI and REST API.
disk_iops_configuration: Option<DiskIopsConfiguration>The SSD IOPS configuration for the FSx for ONTAP file system.
preferred_subnet_id: Option<String>Required when DeploymentType is set to MULTI_AZ_1 or MULTI_AZ_2. This specifies the subnet in which you want the preferred file server to be located.
route_table_ids: Option<Vec<String>>(Multi-AZ only) Specifies the route tables in which Amazon FSx creates the rules for routing traffic to the correct file server. You should specify all virtual private cloud (VPC) route tables associated with the subnets in which your clients are located. By default, Amazon FSx selects your VPC's default route table.
Amazon FSx manages these route tables for Multi-AZ file systems using tag-based authentication. These route tables are tagged with Key: AmazonFSx; Value: ManagedByAmazonFSx. When creating FSx for ONTAP Multi-AZ file systems using CloudFormation we recommend that you add the Key: AmazonFSx; Value: ManagedByAmazonFSx tag manually.
throughput_capacity: Option<i32>Sets the throughput capacity for the file system that you're creating in megabytes per second (MBps). For more information, see Managing throughput capacity in the FSx for ONTAP User Guide.
Amazon FSx responds with an HTTP status code 400 (Bad Request) for the following conditions:
-
The value of
ThroughputCapacityandThroughputCapacityPerHAPairare not the same value. -
The value of
ThroughputCapacitywhen divided by the value ofHAPairsis outside of the valid range forThroughputCapacity.
weekly_maintenance_start_time: Option<String>The preferred start time to perform weekly maintenance, formatted d:HH:MM in the UTC time zone, where d is the weekday number, from 1 through 7, beginning with Monday and ending with Sunday.
For example, 1:05:00 specifies maintenance at 5 AM Monday.
ha_pairs: Option<i32>Specifies how many high-availability (HA) pairs of file servers will power your file system. First-generation file systems are powered by 1 HA pair. Second-generation multi-AZ file systems are powered by 1 HA pair. Second generation single-AZ file systems are powered by up to 12 HA pairs. The default value is 1. The value of this property affects the values of StorageCapacity, Iops, and ThroughputCapacity. For more information, see High-availability (HA) pairs in the FSx for ONTAP user guide. Block storage protocol support (iSCSI and NVMe over TCP) is disabled on file systems with more than 6 HA pairs. For more information, see Using block storage protocols.
Amazon FSx responds with an HTTP status code 400 (Bad Request) for the following conditions:
-
The value of
HAPairsis less than 1 or greater than 12. -
The value of
HAPairsis greater than 1 and the value ofDeploymentTypeisSINGLE_AZ_1,MULTI_AZ_1, orMULTI_AZ_2.
throughput_capacity_per_ha_pair: Option<i32>Use to choose the throughput capacity per HA pair, rather than the total throughput for the file system.
You can define either the ThroughputCapacityPerHAPair or the ThroughputCapacity when creating a file system, but not both.
This field and ThroughputCapacity are the same for file systems powered by one HA pair.
-
For
SINGLE_AZ_1andMULTI_AZ_1file systems, valid values are 128, 256, 512, 1024, 2048, or 4096 MBps. -
For
SINGLE_AZ_2, valid values are 1536, 3072, or 6144 MBps. -
For
MULTI_AZ_2, valid values are 384, 768, 1536, 3072, or 6144 MBps.
Amazon FSx responds with an HTTP status code 400 (Bad Request) for the following conditions:
-
The value of
ThroughputCapacityandThroughputCapacityPerHAPairare not the same value for file systems with one HA pair. -
The value of deployment type is
SINGLE_AZ_2andThroughputCapacity/ThroughputCapacityPerHAPairis not a valid HA pair (a value between 1 and 12). -
The value of
ThroughputCapacityPerHAPairis not a valid value.
endpoint_ipv6_address_range: Option<String>(Multi-AZ only) Specifies the IPv6 address range in which the endpoints to access your file system will be created. By default in the Amazon FSx API and Amazon FSx console, Amazon FSx selects an available /118 IP address range for you from one of the VPC's CIDR ranges. You can have overlapping endpoint IP addresses for file systems deployed in the same VPC/route tables, as long as they don't overlap with any subnet.
Implementations§
Source§impl CreateFileSystemOntapConfiguration
impl CreateFileSystemOntapConfiguration
Sourcepub fn automatic_backup_retention_days(&self) -> Option<i32>
pub fn automatic_backup_retention_days(&self) -> Option<i32>
The number of days to retain automatic backups. Setting this property to 0 disables automatic backups. You can retain automatic backups for a maximum of 90 days. The default is 30.
Sourcepub fn daily_automatic_backup_start_time(&self) -> Option<&str>
pub fn daily_automatic_backup_start_time(&self) -> Option<&str>
A recurring daily time, in the format HH:MM. HH is the zero-padded hour of the day (0-23), and MM is the zero-padded minute of the hour. For example, 05:00 specifies 5 AM daily.
Sourcepub fn deployment_type(&self) -> Option<&OntapDeploymentType>
pub fn deployment_type(&self) -> Option<&OntapDeploymentType>
Specifies the FSx for ONTAP file system deployment type to use in creating the file system.
-
MULTI_AZ_1- A high availability file system configured for Multi-AZ redundancy to tolerate temporary Availability Zone (AZ) unavailability. This is a first-generation FSx for ONTAP file system. -
MULTI_AZ_2- A high availability file system configured for Multi-AZ redundancy to tolerate temporary AZ unavailability. This is a second-generation FSx for ONTAP file system. -
SINGLE_AZ_1- A file system configured for Single-AZ redundancy. This is a first-generation FSx for ONTAP file system. -
SINGLE_AZ_2- A file system configured with multiple high-availability (HA) pairs for Single-AZ redundancy. This is a second-generation FSx for ONTAP file system.
For information about the use cases for Multi-AZ and Single-AZ deployments, refer to Choosing a file system deployment type.
Sourcepub fn endpoint_ip_address_range(&self) -> Option<&str>
pub fn endpoint_ip_address_range(&self) -> Option<&str>
(Multi-AZ only) Specifies the IPv4 address range in which the endpoints to access your file system will be created. By default in the Amazon FSx API, Amazon FSx selects an unused IP address range for you from the 198.19.* range. By default in the Amazon FSx console, Amazon FSx chooses the last 64 IP addresses from the VPC’s primary CIDR range to use as the endpoint IP address range for the file system. You can have overlapping endpoint IP addresses for file systems deployed in the same VPC/route tables, as long as they don't overlap with any subnet.
Sourcepub fn fsx_admin_password(&self) -> Option<&str>
pub fn fsx_admin_password(&self) -> Option<&str>
The ONTAP administrative password for the fsxadmin user with which you administer your file system using the NetApp ONTAP CLI and REST API.
Sourcepub fn disk_iops_configuration(&self) -> Option<&DiskIopsConfiguration>
pub fn disk_iops_configuration(&self) -> Option<&DiskIopsConfiguration>
The SSD IOPS configuration for the FSx for ONTAP file system.
Sourcepub fn preferred_subnet_id(&self) -> Option<&str>
pub fn preferred_subnet_id(&self) -> Option<&str>
Required when DeploymentType is set to MULTI_AZ_1 or MULTI_AZ_2. This specifies the subnet in which you want the preferred file server to be located.
Sourcepub fn route_table_ids(&self) -> &[String]
pub fn route_table_ids(&self) -> &[String]
(Multi-AZ only) Specifies the route tables in which Amazon FSx creates the rules for routing traffic to the correct file server. You should specify all virtual private cloud (VPC) route tables associated with the subnets in which your clients are located. By default, Amazon FSx selects your VPC's default route table.
Amazon FSx manages these route tables for Multi-AZ file systems using tag-based authentication. These route tables are tagged with Key: AmazonFSx; Value: ManagedByAmazonFSx. When creating FSx for ONTAP Multi-AZ file systems using CloudFormation we recommend that you add the Key: AmazonFSx; Value: ManagedByAmazonFSx tag manually.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .route_table_ids.is_none().
Sourcepub fn throughput_capacity(&self) -> Option<i32>
pub fn throughput_capacity(&self) -> Option<i32>
Sets the throughput capacity for the file system that you're creating in megabytes per second (MBps). For more information, see Managing throughput capacity in the FSx for ONTAP User Guide.
Amazon FSx responds with an HTTP status code 400 (Bad Request) for the following conditions:
-
The value of
ThroughputCapacityandThroughputCapacityPerHAPairare not the same value. -
The value of
ThroughputCapacitywhen divided by the value ofHAPairsis outside of the valid range forThroughputCapacity.
Sourcepub fn weekly_maintenance_start_time(&self) -> Option<&str>
pub fn weekly_maintenance_start_time(&self) -> Option<&str>
The preferred start time to perform weekly maintenance, formatted d:HH:MM in the UTC time zone, where d is the weekday number, from 1 through 7, beginning with Monday and ending with Sunday.
For example, 1:05:00 specifies maintenance at 5 AM Monday.
Sourcepub fn ha_pairs(&self) -> Option<i32>
pub fn ha_pairs(&self) -> Option<i32>
Specifies how many high-availability (HA) pairs of file servers will power your file system. First-generation file systems are powered by 1 HA pair. Second-generation multi-AZ file systems are powered by 1 HA pair. Second generation single-AZ file systems are powered by up to 12 HA pairs. The default value is 1. The value of this property affects the values of StorageCapacity, Iops, and ThroughputCapacity. For more information, see High-availability (HA) pairs in the FSx for ONTAP user guide. Block storage protocol support (iSCSI and NVMe over TCP) is disabled on file systems with more than 6 HA pairs. For more information, see Using block storage protocols.
Amazon FSx responds with an HTTP status code 400 (Bad Request) for the following conditions:
-
The value of
HAPairsis less than 1 or greater than 12. -
The value of
HAPairsis greater than 1 and the value ofDeploymentTypeisSINGLE_AZ_1,MULTI_AZ_1, orMULTI_AZ_2.
Sourcepub fn throughput_capacity_per_ha_pair(&self) -> Option<i32>
pub fn throughput_capacity_per_ha_pair(&self) -> Option<i32>
Use to choose the throughput capacity per HA pair, rather than the total throughput for the file system.
You can define either the ThroughputCapacityPerHAPair or the ThroughputCapacity when creating a file system, but not both.
This field and ThroughputCapacity are the same for file systems powered by one HA pair.
-
For
SINGLE_AZ_1andMULTI_AZ_1file systems, valid values are 128, 256, 512, 1024, 2048, or 4096 MBps. -
For
SINGLE_AZ_2, valid values are 1536, 3072, or 6144 MBps. -
For
MULTI_AZ_2, valid values are 384, 768, 1536, 3072, or 6144 MBps.
Amazon FSx responds with an HTTP status code 400 (Bad Request) for the following conditions:
-
The value of
ThroughputCapacityandThroughputCapacityPerHAPairare not the same value for file systems with one HA pair. -
The value of deployment type is
SINGLE_AZ_2andThroughputCapacity/ThroughputCapacityPerHAPairis not a valid HA pair (a value between 1 and 12). -
The value of
ThroughputCapacityPerHAPairis not a valid value.
Sourcepub fn endpoint_ipv6_address_range(&self) -> Option<&str>
pub fn endpoint_ipv6_address_range(&self) -> Option<&str>
(Multi-AZ only) Specifies the IPv6 address range in which the endpoints to access your file system will be created. By default in the Amazon FSx API and Amazon FSx console, Amazon FSx selects an available /118 IP address range for you from one of the VPC's CIDR ranges. You can have overlapping endpoint IP addresses for file systems deployed in the same VPC/route tables, as long as they don't overlap with any subnet.
Source§impl CreateFileSystemOntapConfiguration
impl CreateFileSystemOntapConfiguration
Sourcepub fn builder() -> CreateFileSystemOntapConfigurationBuilder
pub fn builder() -> CreateFileSystemOntapConfigurationBuilder
Creates a new builder-style object to manufacture CreateFileSystemOntapConfiguration.
Trait Implementations§
Source§impl Clone for CreateFileSystemOntapConfiguration
impl Clone for CreateFileSystemOntapConfiguration
Source§fn clone(&self) -> CreateFileSystemOntapConfiguration
fn clone(&self) -> CreateFileSystemOntapConfiguration
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl PartialEq for CreateFileSystemOntapConfiguration
impl PartialEq for CreateFileSystemOntapConfiguration
Source§fn eq(&self, other: &CreateFileSystemOntapConfiguration) -> bool
fn eq(&self, other: &CreateFileSystemOntapConfiguration) -> bool
self and other values to be equal, and is used by ==.impl StructuralPartialEq for CreateFileSystemOntapConfiguration
Auto Trait Implementations§
impl Freeze for CreateFileSystemOntapConfiguration
impl RefUnwindSafe for CreateFileSystemOntapConfiguration
impl Send for CreateFileSystemOntapConfiguration
impl Sync for CreateFileSystemOntapConfiguration
impl Unpin for CreateFileSystemOntapConfiguration
impl UnwindSafe for CreateFileSystemOntapConfiguration
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self into a Left variant of Either<Self, Self>
if into_left is true.
Converts self into a Right variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self into a Left variant of Either<Self, Self>
if into_left(&self) returns true.
Converts self into a Right variant of Either<Self, Self>
otherwise. Read moreSource§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self with the foreground set to
value.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red() and
green(), which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg():
use yansi::{Paint, Color};
painted.fg(Color::White);Set foreground color to white using white().
use yansi::Paint;
painted.white();Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self with the background set to
value.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red() and
on_green(), which have the same functionality but
are pithier.
§Example
Set background color to red using fg():
use yansi::{Paint, Color};
painted.bg(Color::Red);Set background color to red using on_red().
use yansi::Paint;
painted.on_red();Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute value.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold() and
underline(), which have the same functionality
but are pithier.
§Example
Make text bold using attr():
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);Make text bold using using bold().
use yansi::Paint;
painted.bold();Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi Quirk value.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask() and
wrap(), which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk():
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);Enable wrapping using wrap().
use yansi::Paint;
painted.wrap();Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting() due to conflicts with Vec::clear().
The clear() method will be removed in a future release.
fn clear(&self) -> Painted<&T>
resetting() due to conflicts with Vec::clear().
The clear() method will be removed in a future release.Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted only when both stdout and stderr are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);