#[non_exhaustive]pub struct UpdateFileSystemLustreConfiguration {
pub weekly_maintenance_start_time: Option<String>,
pub daily_automatic_backup_start_time: Option<String>,
pub automatic_backup_retention_days: Option<i32>,
pub auto_import_policy: Option<AutoImportPolicyType>,
pub data_compression_type: Option<DataCompressionType>,
pub log_configuration: Option<LustreLogCreateConfiguration>,
pub root_squash_configuration: Option<LustreRootSquashConfiguration>,
pub per_unit_storage_throughput: Option<i32>,
pub metadata_configuration: Option<UpdateFileSystemLustreMetadataConfiguration>,
pub throughput_capacity: Option<i32>,
pub data_read_cache_configuration: Option<LustreReadCacheConfiguration>,
}Expand description
The configuration object for Amazon FSx for Lustre file systems used in the UpdateFileSystem operation.
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.weekly_maintenance_start_time: Option<String>(Optional) The preferred start time to perform weekly maintenance, formatted d:HH:MM in the UTC time zone. d is the weekday number, from 1 through 7, beginning with Monday and ending with Sunday.
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.
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 0.
auto_import_policy: Option<AutoImportPolicyType>(Optional) When you create your file system, your existing S3 objects appear as file and directory listings. Use this property to choose how Amazon FSx keeps your file and directory listing up to date as you add or modify objects in your linked S3 bucket. AutoImportPolicy can have the following values:
-
NONE- (Default) AutoImport is off. Amazon FSx only updates file and directory listings from the linked S3 bucket when the file system is created. FSx does not update the file and directory listing for any new or changed objects after choosing this option. -
NEW- AutoImport is on. Amazon FSx automatically imports directory listings of any new objects added to the linked S3 bucket that do not currently exist in the FSx file system. -
NEW_CHANGED- AutoImport is on. Amazon FSx automatically imports file and directory listings of any new objects added to the S3 bucket and any existing objects that are changed in the S3 bucket after you choose this option. -
NEW_CHANGED_DELETED- AutoImport is on. Amazon FSx automatically imports file and directory listings of any new objects added to the S3 bucket, any existing objects that are changed in the S3 bucket, and any objects that were deleted in the S3 bucket.
This parameter is not supported for file systems with a data repository association.
data_compression_type: Option<DataCompressionType>Sets the data compression configuration for the file system. DataCompressionType can have the following values:
-
NONE- Data compression is turned off for the file system. -
LZ4- Data compression is turned on with the LZ4 algorithm.
If you don't use DataCompressionType, the file system retains its current data compression configuration.
For more information, see Lustre data compression.
log_configuration: Option<LustreLogCreateConfiguration>The Lustre logging configuration used when updating an Amazon FSx for Lustre file system. When logging is enabled, Lustre logs error and warning events for data repositories associated with your file system to Amazon CloudWatch Logs.
root_squash_configuration: Option<LustreRootSquashConfiguration>The Lustre root squash configuration used when updating an Amazon FSx for Lustre file system. When enabled, root squash restricts root-level access from clients that try to access your file system as a root user.
per_unit_storage_throughput: Option<i32>The throughput of an Amazon FSx for Lustre Persistent SSD-based file system, measured in megabytes per second per tebibyte (MB/s/TiB). You can increase or decrease your file system's throughput. Valid values depend on the deployment type of the file system, as follows:
-
For
PERSISTENT_1SSD-based deployment types, valid values are 50, 100, and 200 MB/s/TiB. -
For
PERSISTENT_2SSD-based deployment types, valid values are 125, 250, 500, and 1000 MB/s/TiB.
For more information, see Managing throughput capacity.
metadata_configuration: Option<UpdateFileSystemLustreMetadataConfiguration>The Lustre metadata performance configuration for an Amazon FSx for Lustre file system using a PERSISTENT_2 deployment type. When this configuration is enabled, the file system supports increasing metadata performance.
throughput_capacity: Option<i32>The throughput of an Amazon FSx for Lustre file system using an Intelligent-Tiering storage class, measured in megabytes per second (MBps). You can only increase your file system's throughput. Valid values are 4000 MBps or multiples of 4000 MBps.
data_read_cache_configuration: Option<LustreReadCacheConfiguration>Specifies the optional provisioned SSD read cache on Amazon FSx for Lustre file systems that use the Intelligent-Tiering storage class.
Implementations§
Source§impl UpdateFileSystemLustreConfiguration
impl UpdateFileSystemLustreConfiguration
Sourcepub fn weekly_maintenance_start_time(&self) -> Option<&str>
pub fn weekly_maintenance_start_time(&self) -> Option<&str>
(Optional) The preferred start time to perform weekly maintenance, formatted d:HH:MM in the UTC time zone. d is the weekday number, from 1 through 7, beginning with Monday and ending with Sunday.
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 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 0.
Sourcepub fn auto_import_policy(&self) -> Option<&AutoImportPolicyType>
pub fn auto_import_policy(&self) -> Option<&AutoImportPolicyType>
(Optional) When you create your file system, your existing S3 objects appear as file and directory listings. Use this property to choose how Amazon FSx keeps your file and directory listing up to date as you add or modify objects in your linked S3 bucket. AutoImportPolicy can have the following values:
-
NONE- (Default) AutoImport is off. Amazon FSx only updates file and directory listings from the linked S3 bucket when the file system is created. FSx does not update the file and directory listing for any new or changed objects after choosing this option. -
NEW- AutoImport is on. Amazon FSx automatically imports directory listings of any new objects added to the linked S3 bucket that do not currently exist in the FSx file system. -
NEW_CHANGED- AutoImport is on. Amazon FSx automatically imports file and directory listings of any new objects added to the S3 bucket and any existing objects that are changed in the S3 bucket after you choose this option. -
NEW_CHANGED_DELETED- AutoImport is on. Amazon FSx automatically imports file and directory listings of any new objects added to the S3 bucket, any existing objects that are changed in the S3 bucket, and any objects that were deleted in the S3 bucket.
This parameter is not supported for file systems with a data repository association.
Sourcepub fn data_compression_type(&self) -> Option<&DataCompressionType>
pub fn data_compression_type(&self) -> Option<&DataCompressionType>
Sets the data compression configuration for the file system. DataCompressionType can have the following values:
-
NONE- Data compression is turned off for the file system. -
LZ4- Data compression is turned on with the LZ4 algorithm.
If you don't use DataCompressionType, the file system retains its current data compression configuration.
For more information, see Lustre data compression.
Sourcepub fn log_configuration(&self) -> Option<&LustreLogCreateConfiguration>
pub fn log_configuration(&self) -> Option<&LustreLogCreateConfiguration>
The Lustre logging configuration used when updating an Amazon FSx for Lustre file system. When logging is enabled, Lustre logs error and warning events for data repositories associated with your file system to Amazon CloudWatch Logs.
Sourcepub fn root_squash_configuration(
&self,
) -> Option<&LustreRootSquashConfiguration>
pub fn root_squash_configuration( &self, ) -> Option<&LustreRootSquashConfiguration>
The Lustre root squash configuration used when updating an Amazon FSx for Lustre file system. When enabled, root squash restricts root-level access from clients that try to access your file system as a root user.
Sourcepub fn per_unit_storage_throughput(&self) -> Option<i32>
pub fn per_unit_storage_throughput(&self) -> Option<i32>
The throughput of an Amazon FSx for Lustre Persistent SSD-based file system, measured in megabytes per second per tebibyte (MB/s/TiB). You can increase or decrease your file system's throughput. Valid values depend on the deployment type of the file system, as follows:
-
For
PERSISTENT_1SSD-based deployment types, valid values are 50, 100, and 200 MB/s/TiB. -
For
PERSISTENT_2SSD-based deployment types, valid values are 125, 250, 500, and 1000 MB/s/TiB.
For more information, see Managing throughput capacity.
Sourcepub fn metadata_configuration(
&self,
) -> Option<&UpdateFileSystemLustreMetadataConfiguration>
pub fn metadata_configuration( &self, ) -> Option<&UpdateFileSystemLustreMetadataConfiguration>
The Lustre metadata performance configuration for an Amazon FSx for Lustre file system using a PERSISTENT_2 deployment type. When this configuration is enabled, the file system supports increasing metadata performance.
Sourcepub fn throughput_capacity(&self) -> Option<i32>
pub fn throughput_capacity(&self) -> Option<i32>
The throughput of an Amazon FSx for Lustre file system using an Intelligent-Tiering storage class, measured in megabytes per second (MBps). You can only increase your file system's throughput. Valid values are 4000 MBps or multiples of 4000 MBps.
Sourcepub fn data_read_cache_configuration(
&self,
) -> Option<&LustreReadCacheConfiguration>
pub fn data_read_cache_configuration( &self, ) -> Option<&LustreReadCacheConfiguration>
Specifies the optional provisioned SSD read cache on Amazon FSx for Lustre file systems that use the Intelligent-Tiering storage class.
Source§impl UpdateFileSystemLustreConfiguration
impl UpdateFileSystemLustreConfiguration
Sourcepub fn builder() -> UpdateFileSystemLustreConfigurationBuilder
pub fn builder() -> UpdateFileSystemLustreConfigurationBuilder
Creates a new builder-style object to manufacture UpdateFileSystemLustreConfiguration.
Trait Implementations§
Source§impl Clone for UpdateFileSystemLustreConfiguration
impl Clone for UpdateFileSystemLustreConfiguration
Source§fn clone(&self) -> UpdateFileSystemLustreConfiguration
fn clone(&self) -> UpdateFileSystemLustreConfiguration
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 UpdateFileSystemLustreConfiguration
impl PartialEq for UpdateFileSystemLustreConfiguration
Source§fn eq(&self, other: &UpdateFileSystemLustreConfiguration) -> bool
fn eq(&self, other: &UpdateFileSystemLustreConfiguration) -> bool
self and other values to be equal, and is used by ==.impl StructuralPartialEq for UpdateFileSystemLustreConfiguration
Auto Trait Implementations§
impl Freeze for UpdateFileSystemLustreConfiguration
impl RefUnwindSafe for UpdateFileSystemLustreConfiguration
impl Send for UpdateFileSystemLustreConfiguration
impl Sync for UpdateFileSystemLustreConfiguration
impl Unpin for UpdateFileSystemLustreConfiguration
impl UnwindSafe for UpdateFileSystemLustreConfiguration
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);