bug 6684: return 'attached' parameter as part of listVolumes response. For the diskOffering information looking like service offering information, this is because the diskOffering on the root volume is set to be the service offering of the VM. If this is a change from 2.1.x please re-open this bug, but for the time being I'm going to assume this is working as expected.

status 6684: resolved fixed
This commit is contained in:
Kris McQueen 2010-10-22 16:53:49 -07:00
parent eccab6880f
commit a5dd8a5bc7
2 changed files with 12 additions and 0 deletions

View File

@ -206,6 +206,7 @@ public class ListVolumesCmd extends BaseListCmd {
volResponse.setSourceType(volume.getSourceType().toString());
}
volResponse.setHypervisor(ApiDBUtils.getVolumeHyperType(volume.getId()).toString());
volResponse.setAttached(volume.getAttached());
volResponse.setResponseName("volume");
volResponses.add(volResponse);

View File

@ -104,6 +104,9 @@ public class VolumeResponse extends BaseResponse {
@SerializedName("snapshotid") @Param(description="ID of the snapshot from which this volume was created")
private Long snapshotId;
@SerializedName("attached") @Param(description="the date the volume was attached to a VM instance")
private Date attached;
public Long getId() {
return id;
}
@ -319,4 +322,12 @@ public class VolumeResponse extends BaseResponse {
public void setSnapshotId(Long snapshotId) {
this.snapshotId = snapshotId;
}
public Date getAttached() {
return attached;
}
public void setAttached(Date attached) {
this.attached = attached;
}
}