#[non_exhaustive]pub struct CreateFileSystemInput {Show 13 fields
pub client_request_token: Option<String>,
pub file_system_type: Option<FileSystemType>,
pub storage_capacity: Option<i32>,
pub storage_type: Option<StorageType>,
pub subnet_ids: Option<Vec<String>>,
pub security_group_ids: Option<Vec<String>>,
pub tags: Option<Vec<Tag>>,
pub kms_key_id: Option<String>,
pub windows_configuration: Option<CreateFileSystemWindowsConfiguration>,
pub lustre_configuration: Option<CreateFileSystemLustreConfiguration>,
pub ontap_configuration: Option<CreateFileSystemOntapConfiguration>,
pub file_system_type_version: Option<String>,
pub open_zfs_configuration: Option<CreateFileSystemOpenZfsConfiguration>,
}
Expand description
The request object used to create a new Amazon FSx 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.client_request_token: Option<String>
A string of up to 63 ASCII characters that Amazon FSx uses to ensure idempotent creation. This string is automatically filled on your behalf when you use the Command Line Interface (CLI) or an Amazon Web Services SDK.
file_system_type: Option<FileSystemType>
The type of Amazon FSx file system to create. Valid values are WINDOWS
, LUSTRE
, ONTAP
, and OPENZFS
.
storage_capacity: Option<i32>
Sets the storage capacity of the file system that you're creating, in gibibytes (GiB).
FSx for Lustre file systems - The amount of storage capacity that you can configure depends on the value that you set for StorageType
and the Lustre DeploymentType
, as follows:
-
For
SCRATCH_2
,PERSISTENT_2
, andPERSISTENT_1
deployment types using SSD storage type, the valid values are 1200 GiB, 2400 GiB, and increments of 2400 GiB. -
For
PERSISTENT_1
HDD file systems, valid values are increments of 6000 GiB for 12 MB/s/TiB file systems and increments of 1800 GiB for 40 MB/s/TiB file systems. -
For
SCRATCH_1
deployment type, valid values are 1200 GiB, 2400 GiB, and increments of 3600 GiB.
FSx for ONTAP file systems - The amount of storage capacity that you can configure depends on the value of the HAPairs
property. The minimum value is calculated as 1,024 * HAPairs
and the maximum is calculated as 524,288 * HAPairs
.
FSx for OpenZFS file systems - The amount of storage capacity that you can configure is from 64 GiB up to 524,288 GiB (512 TiB).
FSx for Windows File Server file systems - The amount of storage capacity that you can configure depends on the value that you set for StorageType
as follows:
-
For SSD storage, valid values are 32 GiB-65,536 GiB (64 TiB).
-
For HDD storage, valid values are 2000 GiB-65,536 GiB (64 TiB).
storage_type: Option<StorageType>
Sets the storage class for the file system that you're creating. Valid values are SSD
, HDD
, and INTELLIGENT_TIERING
.
-
Set to
SSD
to use solid state drive storage. SSD is supported on all Windows, Lustre, ONTAP, and OpenZFS deployment types. -
Set to
HDD
to use hard disk drive storage, which is supported onSINGLE_AZ_2
andMULTI_AZ_1
Windows file system deployment types, and onPERSISTENT_1
Lustre file system deployment types. -
Set to
INTELLIGENT_TIERING
to use fully elastic, intelligently-tiered storage. Intelligent-Tiering is only available for OpenZFS file systems with the Multi-AZ deployment type and for Lustre file systems with the Persistent_2 deployment type.
Default value is SSD
. For more information, see Storage type options in the FSx for Windows File Server User Guide, FSx for Lustre storage classes in the FSx for Lustre User Guide, and Working with Intelligent-Tiering in the Amazon FSx for OpenZFS User Guide.
subnet_ids: Option<Vec<String>>
Specifies the IDs of the subnets that the file system will be accessible from. For Windows and ONTAP MULTI_AZ_1
deployment types,provide exactly two subnet IDs, one for the preferred file server and one for the standby file server. You specify one of these subnets as the preferred subnet using the WindowsConfiguration > PreferredSubnetID
or OntapConfiguration > PreferredSubnetID
properties. For more information about Multi-AZ file system configuration, see Availability and durability: Single-AZ and Multi-AZ file systems in the Amazon FSx for Windows User Guide and Availability and durability in the Amazon FSx for ONTAP User Guide.
For Windows SINGLE_AZ_1
and SINGLE_AZ_2
and all Lustre deployment types, provide exactly one subnet ID. The file server is launched in that subnet's Availability Zone.
security_group_ids: Option<Vec<String>>
A list of IDs specifying the security groups to apply to all network interfaces created for file system access. This list isn't returned in later requests to describe the file system.
You must specify a security group if you are creating a Multi-AZ FSx for ONTAP file system in a VPC subnet that has been shared with you.
The tags to apply to the file system that's being created. The key value of the Name
tag appears in the console as the file system name.
kms_key_id: Option<String>
Specifies the ID of the Key Management Service (KMS) key to use for encrypting data on Amazon FSx file systems, as follows:
-
Amazon FSx for Lustre
PERSISTENT_1
andPERSISTENT_2
deployment types only.SCRATCH_1
andSCRATCH_2
types are encrypted using the Amazon FSx service KMS key for your account. -
Amazon FSx for NetApp ONTAP
-
Amazon FSx for OpenZFS
-
Amazon FSx for Windows File Server
If a KmsKeyId
isn't specified, the Amazon FSx-managed KMS key for your account is used. For more information, see Encrypt in the Key Management Service API Reference.
windows_configuration: Option<CreateFileSystemWindowsConfiguration>
The Microsoft Windows configuration for the file system that's being created.
lustre_configuration: Option<CreateFileSystemLustreConfiguration>
The Lustre configuration for the file system being created.
The following parameters are not supported for file systems with a data repository association created with .
-
AutoImportPolicy
-
ExportPath
-
ImportedFileChunkSize
-
ImportPath
ontap_configuration: Option<CreateFileSystemOntapConfiguration>
The ONTAP configuration properties of the FSx for ONTAP file system that you are creating.
file_system_type_version: Option<String>
For FSx for Lustre file systems, sets the Lustre version for the file system that you're creating. Valid values are 2.10
, 2.12
, and 2.15
:
-
2.10
is supported by the Scratch and Persistent_1 Lustre deployment types. -
2.12
is supported by all Lustre deployment types, except forPERSISTENT_2
with a metadata configuration mode. -
2.15
is supported by all Lustre deployment types and is recommended for all new file systems.
Default value is 2.10
, except for the following deployments:
-
Default value is
2.12
whenDeploymentType
is set toPERSISTENT_2
without a metadata configuration mode. -
Default value is
2.15
whenDeploymentType
is set toPERSISTENT_2
with a metadata configuration mode.
open_zfs_configuration: Option<CreateFileSystemOpenZfsConfiguration>
The OpenZFS configuration for the file system that's being created.
Implementations§
Source§impl CreateFileSystemInput
impl CreateFileSystemInput
Sourcepub fn client_request_token(&self) -> Option<&str>
pub fn client_request_token(&self) -> Option<&str>
A string of up to 63 ASCII characters that Amazon FSx uses to ensure idempotent creation. This string is automatically filled on your behalf when you use the Command Line Interface (CLI) or an Amazon Web Services SDK.
Sourcepub fn file_system_type(&self) -> Option<&FileSystemType>
pub fn file_system_type(&self) -> Option<&FileSystemType>
The type of Amazon FSx file system to create. Valid values are WINDOWS
, LUSTRE
, ONTAP
, and OPENZFS
.
Sourcepub fn storage_capacity(&self) -> Option<i32>
pub fn storage_capacity(&self) -> Option<i32>
Sets the storage capacity of the file system that you're creating, in gibibytes (GiB).
FSx for Lustre file systems - The amount of storage capacity that you can configure depends on the value that you set for StorageType
and the Lustre DeploymentType
, as follows:
-
For
SCRATCH_2
,PERSISTENT_2
, andPERSISTENT_1
deployment types using SSD storage type, the valid values are 1200 GiB, 2400 GiB, and increments of 2400 GiB. -
For
PERSISTENT_1
HDD file systems, valid values are increments of 6000 GiB for 12 MB/s/TiB file systems and increments of 1800 GiB for 40 MB/s/TiB file systems. -
For
SCRATCH_1
deployment type, valid values are 1200 GiB, 2400 GiB, and increments of 3600 GiB.
FSx for ONTAP file systems - The amount of storage capacity that you can configure depends on the value of the HAPairs
property. The minimum value is calculated as 1,024 * HAPairs
and the maximum is calculated as 524,288 * HAPairs
.
FSx for OpenZFS file systems - The amount of storage capacity that you can configure is from 64 GiB up to 524,288 GiB (512 TiB).
FSx for Windows File Server file systems - The amount of storage capacity that you can configure depends on the value that you set for StorageType
as follows:
-
For SSD storage, valid values are 32 GiB-65,536 GiB (64 TiB).
-
For HDD storage, valid values are 2000 GiB-65,536 GiB (64 TiB).
Sourcepub fn storage_type(&self) -> Option<&StorageType>
pub fn storage_type(&self) -> Option<&StorageType>
Sets the storage class for the file system that you're creating. Valid values are SSD
, HDD
, and INTELLIGENT_TIERING
.
-
Set to
SSD
to use solid state drive storage. SSD is supported on all Windows, Lustre, ONTAP, and OpenZFS deployment types. -
Set to
HDD
to use hard disk drive storage, which is supported onSINGLE_AZ_2
andMULTI_AZ_1
Windows file system deployment types, and onPERSISTENT_1
Lustre file system deployment types. -
Set to
INTELLIGENT_TIERING
to use fully elastic, intelligently-tiered storage. Intelligent-Tiering is only available for OpenZFS file systems with the Multi-AZ deployment type and for Lustre file systems with the Persistent_2 deployment type.
Default value is SSD
. For more information, see Storage type options in the FSx for Windows File Server User Guide, FSx for Lustre storage classes in the FSx for Lustre User Guide, and Working with Intelligent-Tiering in the Amazon FSx for OpenZFS User Guide.
Sourcepub fn subnet_ids(&self) -> &[String]
pub fn subnet_ids(&self) -> &[String]
Specifies the IDs of the subnets that the file system will be accessible from. For Windows and ONTAP MULTI_AZ_1
deployment types,provide exactly two subnet IDs, one for the preferred file server and one for the standby file server. You specify one of these subnets as the preferred subnet using the WindowsConfiguration > PreferredSubnetID
or OntapConfiguration > PreferredSubnetID
properties. For more information about Multi-AZ file system configuration, see Availability and durability: Single-AZ and Multi-AZ file systems in the Amazon FSx for Windows User Guide and Availability and durability in the Amazon FSx for ONTAP User Guide.
For Windows SINGLE_AZ_1
and SINGLE_AZ_2
and all Lustre deployment types, provide exactly one subnet ID. The file server is launched in that subnet's Availability Zone.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .subnet_ids.is_none()
.
Sourcepub fn security_group_ids(&self) -> &[String]
pub fn security_group_ids(&self) -> &[String]
A list of IDs specifying the security groups to apply to all network interfaces created for file system access. This list isn't returned in later requests to describe the file system.
You must specify a security group if you are creating a Multi-AZ FSx for ONTAP file system in a VPC subnet that has been shared with you.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .security_group_ids.is_none()
.
The tags to apply to the file system that's being created. The key value of the Name
tag appears in the console as the file system name.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .tags.is_none()
.
Sourcepub fn kms_key_id(&self) -> Option<&str>
pub fn kms_key_id(&self) -> Option<&str>
Specifies the ID of the Key Management Service (KMS) key to use for encrypting data on Amazon FSx file systems, as follows:
-
Amazon FSx for Lustre
PERSISTENT_1
andPERSISTENT_2
deployment types only.SCRATCH_1
andSCRATCH_2
types are encrypted using the Amazon FSx service KMS key for your account. -
Amazon FSx for NetApp ONTAP
-
Amazon FSx for OpenZFS
-
Amazon FSx for Windows File Server
If a KmsKeyId
isn't specified, the Amazon FSx-managed KMS key for your account is used. For more information, see Encrypt in the Key Management Service API Reference.
Sourcepub fn windows_configuration(
&self,
) -> Option<&CreateFileSystemWindowsConfiguration>
pub fn windows_configuration( &self, ) -> Option<&CreateFileSystemWindowsConfiguration>
The Microsoft Windows configuration for the file system that's being created.
Sourcepub fn lustre_configuration(
&self,
) -> Option<&CreateFileSystemLustreConfiguration>
pub fn lustre_configuration( &self, ) -> Option<&CreateFileSystemLustreConfiguration>
The Lustre configuration for the file system being created.
The following parameters are not supported for file systems with a data repository association created with .
-
AutoImportPolicy
-
ExportPath
-
ImportedFileChunkSize
-
ImportPath
Sourcepub fn ontap_configuration(&self) -> Option<&CreateFileSystemOntapConfiguration>
pub fn ontap_configuration(&self) -> Option<&CreateFileSystemOntapConfiguration>
The ONTAP configuration properties of the FSx for ONTAP file system that you are creating.
Sourcepub fn file_system_type_version(&self) -> Option<&str>
pub fn file_system_type_version(&self) -> Option<&str>
For FSx for Lustre file systems, sets the Lustre version for the file system that you're creating. Valid values are 2.10
, 2.12
, and 2.15
:
-
2.10
is supported by the Scratch and Persistent_1 Lustre deployment types. -
2.12
is supported by all Lustre deployment types, except forPERSISTENT_2
with a metadata configuration mode. -
2.15
is supported by all Lustre deployment types and is recommended for all new file systems.
Default value is 2.10
, except for the following deployments:
-
Default value is
2.12
whenDeploymentType
is set toPERSISTENT_2
without a metadata configuration mode. -
Default value is
2.15
whenDeploymentType
is set toPERSISTENT_2
with a metadata configuration mode.
Sourcepub fn open_zfs_configuration(
&self,
) -> Option<&CreateFileSystemOpenZfsConfiguration>
pub fn open_zfs_configuration( &self, ) -> Option<&CreateFileSystemOpenZfsConfiguration>
The OpenZFS configuration for the file system that's being created.
Source§impl CreateFileSystemInput
impl CreateFileSystemInput
Sourcepub fn builder() -> CreateFileSystemInputBuilder
pub fn builder() -> CreateFileSystemInputBuilder
Creates a new builder-style object to manufacture CreateFileSystemInput
.
Trait Implementations§
Source§impl Clone for CreateFileSystemInput
impl Clone for CreateFileSystemInput
Source§fn clone(&self) -> CreateFileSystemInput
fn clone(&self) -> CreateFileSystemInput
1.0.0 · Source§const fn clone_from(&mut self, source: &Self)
const fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for CreateFileSystemInput
impl Debug for CreateFileSystemInput
Source§impl PartialEq for CreateFileSystemInput
impl PartialEq for CreateFileSystemInput
impl StructuralPartialEq for CreateFileSystemInput
Auto Trait Implementations§
impl Freeze for CreateFileSystemInput
impl RefUnwindSafe for CreateFileSystemInput
impl Send for CreateFileSystemInput
impl Sync for CreateFileSystemInput
impl Unpin for CreateFileSystemInput
impl UnwindSafe for CreateFileSystemInput
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);