#[non_exhaustive]pub struct UpdateFileSystemOntapConfiguration {
pub automatic_backup_retention_days: Option<i32>,
pub daily_automatic_backup_start_time: Option<String>,
pub fsx_admin_password: Option<String>,
pub weekly_maintenance_start_time: Option<String>,
pub disk_iops_configuration: Option<DiskIopsConfiguration>,
pub throughput_capacity: Option<i32>,
pub add_route_table_ids: Option<Vec<String>>,
pub remove_route_table_ids: Option<Vec<String>>,
pub throughput_capacity_per_ha_pair: Option<i32>,
pub ha_pairs: Option<i32>,
}Expand description
The configuration updates for an Amazon FSx for NetApp ONTAP file system.
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.
fsx_admin_password: Option<String>Update the password for the fsxadmin user by entering a new password. You use the fsxadmin user to access the NetApp ONTAP CLI and REST API to manage your file system resources. For more information, see Managing resources using NetApp Application.
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.
disk_iops_configuration: Option<DiskIopsConfiguration>The SSD IOPS (input output operations per second) configuration for an Amazon FSx for NetApp ONTAP file system. The default is 3 IOPS per GB of storage capacity, but you can provision additional IOPS per GB of storage. The configuration consists of an IOPS mode (AUTOMATIC or USER_PROVISIONED), and in the case of USER_PROVISIONED IOPS, the total number of SSD IOPS provisioned. For more information, see Updating SSD storage capacity and IOPS.
throughput_capacity: Option<i32>Enter a new value to change the amount of throughput capacity for the file system 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.
add_route_table_ids: Option<Vec<String>>(Multi-AZ only) A list of IDs of new virtual private cloud (VPC) route tables to associate (add) with your Amazon FSx for NetApp ONTAP file system.
remove_route_table_ids: Option<Vec<String>>(Multi-AZ only) A list of IDs of existing virtual private cloud (VPC) route tables to disassociate (remove) from your Amazon FSx for NetApp ONTAP file system. You can use the API operation to retrieve the list of VPC route table IDs for a file system.
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.
This field and ThroughputCapacity cannot be defined in the same API call, but one is required.
This field and ThroughputCapacity are the same for file systems with 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.
ha_pairs: Option<i32>Use to update the number of high-availability (HA) pairs for a second-generation single-AZ file system. If you increase the number of HA pairs for your file system, you must specify proportional increases for 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.
Implementations§
Source§impl UpdateFileSystemOntapConfiguration
impl UpdateFileSystemOntapConfiguration
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 fsx_admin_password(&self) -> Option<&str>
pub fn fsx_admin_password(&self) -> Option<&str>
Update the password for the fsxadmin user by entering a new password. You use the fsxadmin user to access the NetApp ONTAP CLI and REST API to manage your file system resources. For more information, see Managing resources using NetApp Application.
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 disk_iops_configuration(&self) -> Option<&DiskIopsConfiguration>
pub fn disk_iops_configuration(&self) -> Option<&DiskIopsConfiguration>
The SSD IOPS (input output operations per second) configuration for an Amazon FSx for NetApp ONTAP file system. The default is 3 IOPS per GB of storage capacity, but you can provision additional IOPS per GB of storage. The configuration consists of an IOPS mode (AUTOMATIC or USER_PROVISIONED), and in the case of USER_PROVISIONED IOPS, the total number of SSD IOPS provisioned. For more information, see Updating SSD storage capacity and IOPS.
Sourcepub fn throughput_capacity(&self) -> Option<i32>
pub fn throughput_capacity(&self) -> Option<i32>
Enter a new value to change the amount of throughput capacity for the file system 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 add_route_table_ids(&self) -> &[String]
pub fn add_route_table_ids(&self) -> &[String]
(Multi-AZ only) A list of IDs of new virtual private cloud (VPC) route tables to associate (add) with your Amazon FSx for NetApp ONTAP file system.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .add_route_table_ids.is_none().
Sourcepub fn remove_route_table_ids(&self) -> &[String]
pub fn remove_route_table_ids(&self) -> &[String]
(Multi-AZ only) A list of IDs of existing virtual private cloud (VPC) route tables to disassociate (remove) from your Amazon FSx for NetApp ONTAP file system. You can use the API operation to retrieve the list of VPC route table IDs for a file system.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .remove_route_table_ids.is_none().
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.
This field and ThroughputCapacity cannot be defined in the same API call, but one is required.
This field and ThroughputCapacity are the same for file systems with 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 ha_pairs(&self) -> Option<i32>
pub fn ha_pairs(&self) -> Option<i32>
Use to update the number of high-availability (HA) pairs for a second-generation single-AZ file system. If you increase the number of HA pairs for your file system, you must specify proportional increases for 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.
Source§impl UpdateFileSystemOntapConfiguration
impl UpdateFileSystemOntapConfiguration
Sourcepub fn builder() -> UpdateFileSystemOntapConfigurationBuilder
pub fn builder() -> UpdateFileSystemOntapConfigurationBuilder
Creates a new builder-style object to manufacture UpdateFileSystemOntapConfiguration.
Trait Implementations§
Source§impl Clone for UpdateFileSystemOntapConfiguration
impl Clone for UpdateFileSystemOntapConfiguration
Source§fn clone(&self) -> UpdateFileSystemOntapConfiguration
fn clone(&self) -> UpdateFileSystemOntapConfiguration
1.0.0 · Source§const fn clone_from(&mut self, source: &Self)
const fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl PartialEq for UpdateFileSystemOntapConfiguration
impl PartialEq for UpdateFileSystemOntapConfiguration
Source§fn eq(&self, other: &UpdateFileSystemOntapConfiguration) -> bool
fn eq(&self, other: &UpdateFileSystemOntapConfiguration) -> bool
self and other values to be equal, and is used by ==.impl StructuralPartialEq for UpdateFileSystemOntapConfiguration
Auto Trait Implementations§
impl Freeze for UpdateFileSystemOntapConfiguration
impl RefUnwindSafe for UpdateFileSystemOntapConfiguration
impl Send for UpdateFileSystemOntapConfiguration
impl Sync for UpdateFileSystemOntapConfiguration
impl Unpin for UpdateFileSystemOntapConfiguration
impl UnwindSafe for UpdateFileSystemOntapConfiguration
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);