#[non_exhaustive]pub struct UpdateSiteRackPhysicalPropertiesInput {
pub site_id: Option<String>,
pub power_draw_kva: Option<PowerDrawKva>,
pub power_phase: Option<PowerPhase>,
pub power_connector: Option<PowerConnector>,
pub power_feed_drop: Option<PowerFeedDrop>,
pub uplink_gbps: Option<UplinkGbps>,
pub uplink_count: Option<UplinkCount>,
pub fiber_optic_cable_type: Option<FiberOpticCableType>,
pub optical_standard: Option<OpticalStandard>,
pub maximum_supported_weight_lbs: Option<MaximumSupportedWeightLbs>,
}
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.site_id: Option<String>
The ID or the Amazon Resource Name (ARN) of the site.
power_draw_kva: Option<PowerDrawKva>
The power draw, in kVA, available at the hardware placement position for the rack.
power_phase: Option<PowerPhase>
The power option that you can provide for hardware.
-
Single-phase AC feed: 200 V to 277 V, 50 Hz or 60 Hz
-
Three-phase AC feed: 346 V to 480 V, 50 Hz or 60 Hz
power_connector: Option<PowerConnector>
The power connector that Amazon Web Services should plan to provide for connections to the hardware. Note the correlation between PowerPhase
and PowerConnector
.
-
Single-phase AC feed
-
L6-30P – (common in US); 30A; single phase
-
IEC309 (blue) – P+N+E, 6hr; 32 A; single phase
-
-
Three-phase AC feed
-
AH530P7W (red) – 3P+N+E, 7hr; 30A; three phase
-
AH532P6W (red) – 3P+N+E, 6hr; 32A; three phase
-
CS8365C – (common in US); 3P+E, 50A; three phase
-
power_feed_drop: Option<PowerFeedDrop>
Indicates whether the power feed comes above or below the rack.
uplink_gbps: Option<UplinkGbps>
The uplink speed the rack should support for the connection to the Region.
uplink_count: Option<UplinkCount>
Racks come with two Outpost network devices. Depending on the supported uplink speed at the site, the Outpost network devices provide a variable number of uplinks. Specify the number of uplinks for each Outpost network device that you intend to use to connect the rack to your network. Note the correlation between UplinkGbps
and UplinkCount
.
-
1Gbps - Uplinks available: 1, 2, 4, 6, 8
-
10Gbps - Uplinks available: 1, 2, 4, 8, 12, 16
-
40 and 100 Gbps- Uplinks available: 1, 2, 4
fiber_optic_cable_type: Option<FiberOpticCableType>
The type of fiber that you will use to attach the Outpost to your network.
optical_standard: Option<OpticalStandard>
The type of optical standard that you will use to attach the Outpost to your network. This field is dependent on uplink speed, fiber type, and distance to the upstream device. For more information about networking requirements for racks, see Network in the Amazon Web Services Outposts User Guide.
-
OPTIC_10GBASE_SR
: 10GBASE-SR -
OPTIC_10GBASE_IR
: 10GBASE-IR -
OPTIC_10GBASE_LR
: 10GBASE-LR -
OPTIC_40GBASE_SR
: 40GBASE-SR -
OPTIC_40GBASE_ESR
: 40GBASE-ESR -
OPTIC_40GBASE_IR4_LR4L
: 40GBASE-IR (LR4L) -
OPTIC_40GBASE_LR4
: 40GBASE-LR4 -
OPTIC_100GBASE_SR4
: 100GBASE-SR4 -
OPTIC_100GBASE_CWDM4
: 100GBASE-CWDM4 -
OPTIC_100GBASE_LR4
: 100GBASE-LR4 -
OPTIC_100G_PSM4_MSA
: 100G PSM4 MSA -
OPTIC_1000BASE_LX
: 1000Base-LX -
OPTIC_1000BASE_SX
: 1000Base-SX
maximum_supported_weight_lbs: Option<MaximumSupportedWeightLbs>
The maximum rack weight that this site can support. NO_LIMIT
is over 2000lbs.
Implementations§
Source§impl UpdateSiteRackPhysicalPropertiesInput
impl UpdateSiteRackPhysicalPropertiesInput
Sourcepub fn power_draw_kva(&self) -> Option<&PowerDrawKva>
pub fn power_draw_kva(&self) -> Option<&PowerDrawKva>
The power draw, in kVA, available at the hardware placement position for the rack.
Sourcepub fn power_phase(&self) -> Option<&PowerPhase>
pub fn power_phase(&self) -> Option<&PowerPhase>
The power option that you can provide for hardware.
-
Single-phase AC feed: 200 V to 277 V, 50 Hz or 60 Hz
-
Three-phase AC feed: 346 V to 480 V, 50 Hz or 60 Hz
Sourcepub fn power_connector(&self) -> Option<&PowerConnector>
pub fn power_connector(&self) -> Option<&PowerConnector>
The power connector that Amazon Web Services should plan to provide for connections to the hardware. Note the correlation between PowerPhase
and PowerConnector
.
-
Single-phase AC feed
-
L6-30P – (common in US); 30A; single phase
-
IEC309 (blue) – P+N+E, 6hr; 32 A; single phase
-
-
Three-phase AC feed
-
AH530P7W (red) – 3P+N+E, 7hr; 30A; three phase
-
AH532P6W (red) – 3P+N+E, 6hr; 32A; three phase
-
CS8365C – (common in US); 3P+E, 50A; three phase
-
Sourcepub fn power_feed_drop(&self) -> Option<&PowerFeedDrop>
pub fn power_feed_drop(&self) -> Option<&PowerFeedDrop>
Indicates whether the power feed comes above or below the rack.
Sourcepub fn uplink_gbps(&self) -> Option<&UplinkGbps>
pub fn uplink_gbps(&self) -> Option<&UplinkGbps>
The uplink speed the rack should support for the connection to the Region.
Sourcepub fn uplink_count(&self) -> Option<&UplinkCount>
pub fn uplink_count(&self) -> Option<&UplinkCount>
Racks come with two Outpost network devices. Depending on the supported uplink speed at the site, the Outpost network devices provide a variable number of uplinks. Specify the number of uplinks for each Outpost network device that you intend to use to connect the rack to your network. Note the correlation between UplinkGbps
and UplinkCount
.
-
1Gbps - Uplinks available: 1, 2, 4, 6, 8
-
10Gbps - Uplinks available: 1, 2, 4, 8, 12, 16
-
40 and 100 Gbps- Uplinks available: 1, 2, 4
Sourcepub fn fiber_optic_cable_type(&self) -> Option<&FiberOpticCableType>
pub fn fiber_optic_cable_type(&self) -> Option<&FiberOpticCableType>
The type of fiber that you will use to attach the Outpost to your network.
Sourcepub fn optical_standard(&self) -> Option<&OpticalStandard>
pub fn optical_standard(&self) -> Option<&OpticalStandard>
The type of optical standard that you will use to attach the Outpost to your network. This field is dependent on uplink speed, fiber type, and distance to the upstream device. For more information about networking requirements for racks, see Network in the Amazon Web Services Outposts User Guide.
-
OPTIC_10GBASE_SR
: 10GBASE-SR -
OPTIC_10GBASE_IR
: 10GBASE-IR -
OPTIC_10GBASE_LR
: 10GBASE-LR -
OPTIC_40GBASE_SR
: 40GBASE-SR -
OPTIC_40GBASE_ESR
: 40GBASE-ESR -
OPTIC_40GBASE_IR4_LR4L
: 40GBASE-IR (LR4L) -
OPTIC_40GBASE_LR4
: 40GBASE-LR4 -
OPTIC_100GBASE_SR4
: 100GBASE-SR4 -
OPTIC_100GBASE_CWDM4
: 100GBASE-CWDM4 -
OPTIC_100GBASE_LR4
: 100GBASE-LR4 -
OPTIC_100G_PSM4_MSA
: 100G PSM4 MSA -
OPTIC_1000BASE_LX
: 1000Base-LX -
OPTIC_1000BASE_SX
: 1000Base-SX
Sourcepub fn maximum_supported_weight_lbs(&self) -> Option<&MaximumSupportedWeightLbs>
pub fn maximum_supported_weight_lbs(&self) -> Option<&MaximumSupportedWeightLbs>
The maximum rack weight that this site can support. NO_LIMIT
is over 2000lbs.
Source§impl UpdateSiteRackPhysicalPropertiesInput
impl UpdateSiteRackPhysicalPropertiesInput
Sourcepub fn builder() -> UpdateSiteRackPhysicalPropertiesInputBuilder
pub fn builder() -> UpdateSiteRackPhysicalPropertiesInputBuilder
Creates a new builder-style object to manufacture UpdateSiteRackPhysicalPropertiesInput
.
Trait Implementations§
Source§impl Clone for UpdateSiteRackPhysicalPropertiesInput
impl Clone for UpdateSiteRackPhysicalPropertiesInput
Source§fn clone(&self) -> UpdateSiteRackPhysicalPropertiesInput
fn clone(&self) -> UpdateSiteRackPhysicalPropertiesInput
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl PartialEq for UpdateSiteRackPhysicalPropertiesInput
impl PartialEq for UpdateSiteRackPhysicalPropertiesInput
Source§fn eq(&self, other: &UpdateSiteRackPhysicalPropertiesInput) -> bool
fn eq(&self, other: &UpdateSiteRackPhysicalPropertiesInput) -> bool
self
and other
values to be equal, and is used by ==
.impl StructuralPartialEq for UpdateSiteRackPhysicalPropertiesInput
Auto Trait Implementations§
impl Freeze for UpdateSiteRackPhysicalPropertiesInput
impl RefUnwindSafe for UpdateSiteRackPhysicalPropertiesInput
impl Send for UpdateSiteRackPhysicalPropertiesInput
impl Sync for UpdateSiteRackPhysicalPropertiesInput
impl Unpin for UpdateSiteRackPhysicalPropertiesInput
impl UnwindSafe for UpdateSiteRackPhysicalPropertiesInput
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);