public class ScheduledInstancesBlockDeviceMapping
extends java.lang.Object
implements java.io.Serializable
Describes a block device mapping for a Scheduled Instance.
Constructor and Description |
---|
ScheduledInstancesBlockDeviceMapping() |
Modifier and Type | Method and Description |
---|---|
boolean |
equals(java.lang.Object obj) |
java.lang.String |
getDeviceName()
The device name exposed to the instance (for example,
/dev/sdh or xvdh ). |
ScheduledInstancesEbs |
getEbs()
Parameters used to set up EBS volumes automatically when the instance
is launched.
|
java.lang.String |
getNoDevice()
Suppresses the specified device included in the block device mapping
of the AMI.
|
java.lang.String |
getVirtualName()
The virtual device name (
ephemeral N). |
int |
hashCode() |
void |
setDeviceName(java.lang.String deviceName)
The device name exposed to the instance (for example,
/dev/sdh or xvdh ). |
void |
setEbs(ScheduledInstancesEbs ebs)
Parameters used to set up EBS volumes automatically when the instance
is launched.
|
void |
setNoDevice(java.lang.String noDevice)
Suppresses the specified device included in the block device mapping
of the AMI.
|
void |
setVirtualName(java.lang.String virtualName)
The virtual device name (
ephemeral N). |
java.lang.String |
toString()
Returns a string representation of this object; useful for testing and
debugging.
|
ScheduledInstancesBlockDeviceMapping |
withDeviceName(java.lang.String deviceName)
The device name exposed to the instance (for example,
/dev/sdh or xvdh ). |
ScheduledInstancesBlockDeviceMapping |
withEbs(ScheduledInstancesEbs ebs)
Parameters used to set up EBS volumes automatically when the instance
is launched.
|
ScheduledInstancesBlockDeviceMapping |
withNoDevice(java.lang.String noDevice)
Suppresses the specified device included in the block device mapping
of the AMI.
|
ScheduledInstancesBlockDeviceMapping |
withVirtualName(java.lang.String virtualName)
The virtual device name (
ephemeral N). |
public ScheduledInstancesBlockDeviceMapping()
public java.lang.String getDeviceName()
/dev/sdh
or xvdh
)./dev/sdh
or xvdh
).public void setDeviceName(java.lang.String deviceName)
/dev/sdh
or xvdh
).deviceName
- The device name exposed to the instance (for example,
/dev/sdh
or xvdh
).public ScheduledInstancesBlockDeviceMapping withDeviceName(java.lang.String deviceName)
/dev/sdh
or xvdh
).
Returns a reference to this object so that method calls can be chained together.
deviceName
- The device name exposed to the instance (for example,
/dev/sdh
or xvdh
).public java.lang.String getNoDevice()
public void setNoDevice(java.lang.String noDevice)
noDevice
- Suppresses the specified device included in the block device mapping
of the AMI.public ScheduledInstancesBlockDeviceMapping withNoDevice(java.lang.String noDevice)
Returns a reference to this object so that method calls can be chained together.
noDevice
- Suppresses the specified device included in the block device mapping
of the AMI.public java.lang.String getVirtualName()
ephemeral
N). Instance store
volumes are numbered starting from 0. An instance type with two
available instance store volumes can specify mappings for
ephemeral0
and ephemeral1
.The number of
available instance store volumes depends on the instance type. After
you connect to the instance, you must mount the volume.
Constraints: For M3 instances, you must specify instance store volumes in the block device mapping for the instance. When you launch an M3 instance, we ignore any instance store volumes specified in the block device mapping for the AMI.
ephemeral
N). Instance store
volumes are numbered starting from 0. An instance type with two
available instance store volumes can specify mappings for
ephemeral0
and ephemeral1
.The number of
available instance store volumes depends on the instance type. After
you connect to the instance, you must mount the volume.
Constraints: For M3 instances, you must specify instance store volumes in the block device mapping for the instance. When you launch an M3 instance, we ignore any instance store volumes specified in the block device mapping for the AMI.
public void setVirtualName(java.lang.String virtualName)
ephemeral
N). Instance store
volumes are numbered starting from 0. An instance type with two
available instance store volumes can specify mappings for
ephemeral0
and ephemeral1
.The number of
available instance store volumes depends on the instance type. After
you connect to the instance, you must mount the volume.
Constraints: For M3 instances, you must specify instance store volumes in the block device mapping for the instance. When you launch an M3 instance, we ignore any instance store volumes specified in the block device mapping for the AMI.
virtualName
- The virtual device name (ephemeral
N). Instance store
volumes are numbered starting from 0. An instance type with two
available instance store volumes can specify mappings for
ephemeral0
and ephemeral1
.The number of
available instance store volumes depends on the instance type. After
you connect to the instance, you must mount the volume.
Constraints: For M3 instances, you must specify instance store volumes in the block device mapping for the instance. When you launch an M3 instance, we ignore any instance store volumes specified in the block device mapping for the AMI.
public ScheduledInstancesBlockDeviceMapping withVirtualName(java.lang.String virtualName)
ephemeral
N). Instance store
volumes are numbered starting from 0. An instance type with two
available instance store volumes can specify mappings for
ephemeral0
and ephemeral1
.The number of
available instance store volumes depends on the instance type. After
you connect to the instance, you must mount the volume.
Constraints: For M3 instances, you must specify instance store volumes in the block device mapping for the instance. When you launch an M3 instance, we ignore any instance store volumes specified in the block device mapping for the AMI.
Returns a reference to this object so that method calls can be chained together.
virtualName
- The virtual device name (ephemeral
N). Instance store
volumes are numbered starting from 0. An instance type with two
available instance store volumes can specify mappings for
ephemeral0
and ephemeral1
.The number of
available instance store volumes depends on the instance type. After
you connect to the instance, you must mount the volume.
Constraints: For M3 instances, you must specify instance store volumes in the block device mapping for the instance. When you launch an M3 instance, we ignore any instance store volumes specified in the block device mapping for the AMI.
public ScheduledInstancesEbs getEbs()
public void setEbs(ScheduledInstancesEbs ebs)
ebs
- Parameters used to set up EBS volumes automatically when the instance
is launched.public ScheduledInstancesBlockDeviceMapping withEbs(ScheduledInstancesEbs ebs)
Returns a reference to this object so that method calls can be chained together.
ebs
- Parameters used to set up EBS volumes automatically when the instance
is launched.public java.lang.String toString()
toString
in class java.lang.Object
Object.toString()
public int hashCode()
hashCode
in class java.lang.Object
public boolean equals(java.lang.Object obj)
equals
in class java.lang.Object
Copyright © 2018 Amazon Web Services, Inc. All Rights Reserved.