[jira] [Commented] (CLOUDSTACK-6472) listUsageRecords generates NPEs for expunging instances
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13988617#comment-13988617 ] Pierre-Yves Ritschard commented on CLOUDSTACK-6472: --- This can now be closed listUsageRecords generates NPEs for expunging instances --- Key: CLOUDSTACK-6472 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6472 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Usage Affects Versions: 4.3.0 Environment: linux Reporter: Pierre-Yves Ritschard Attachments: 0001-handle-removed-entities.patch The listUsageRecords API command, pulls down the list of usage records in the cloud_usage database and augments records with information pulled from the cloud database. When dealing with instance records, only instances which are do not have a value for the removed field are considered. Unfortunately, since the output of _entityMgr.findById is not checked this means that Null Pointer Exceptions are generated when trying to access the output for expunged VMs. The attached patch fixes the issue and applies a similar fix for other similar cases. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6568) API:createVolume: Volume gets created with wrong domain ID
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13988658#comment-13988658
]
ASF subversion and git services commented on CLOUDSTACK-6568:
-
Commit 71e0cff46ecbbce204032e6467a66cf740859f6e in cloudstack's branch
refs/heads/4.4 from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=71e0cff ]
CLOUDSTACK-6568:API:createVolume: Volume gets created with wrong domain
ID.
API:createVolume: Volume gets created with wrong domain ID
--
Key: CLOUDSTACK-6568
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6568
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: API, Volumes
Affects Versions: 4.3.0, 4.4.0, 4.3.1
Reporter: Parth Jagirdar
Assignee: Min Chen
Attachments: createVolume.jpg
http://10.223.49.210:8080/client/api?command=createVolumename=d22-volumezoneid=05f156b6-cf10-4891-b7d7-6421f4d87e91diskofferingid=099a28b3-12d2-461e-9558-1c08e8eb5a2ddomainid=82d02e0c-4f25-42a6-9e5b-dc3fae90eb34account=d22response=jsonsessionkey=7ChzlM0hZkWuWUIPlS%2BkV%2BwHghU%3D
2014-05-02 13:37:41,544 INFO [a.c.c.a.ApiServer]
(catalina-exec-22:ctx-669b420f ctx-a9da8d5c) (userId=2 a
ccountId=2 sessionId=B19BA8EED26B975AA6AAEB9E8F25EFC5) 10.215.2.19 -- GET
command=createVolumename=d22-vo
lumezoneid=05f156b6-cf10-4891-b7d7-6421f4d87e91diskofferingid=099a28b3-12d2-461e-9558-1c08e8eb5a2ddomai
nid=82d02e0c-4f25-42a6-9e5b-dc3fae90eb34account=d22response=jsonsessionkey=7ChzlM0hZkWuWUIPlS%2BkV%2BwH
ghU%3D 200 { createvolumeresponse :
{id:224bc4e6-9ecc-4ccf-bd58-09f47ca5b7a2,jobid:d537170d-ab2b-
4880-ae35-f9846e5ef88d} }
{ createvolumeresponse :
{id:224bc4e6-9ecc-4ccf-bd58-09f47ca5b7a2,jobid:d537170d-ab2b-4880-ae35-f9846e5ef88d}
}
createVolume is invoked as ROOT Admin with account and Domain, (To
create Vol for other User).
Volume gets created with specified account. But domain ID is of ROOT.
| 2 | 1 | test|
| 2 | 1 | root-volume |
| 7 | 1 | root-volume |
| 7 | 1 | d22-volume |
++---+-+
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6170) Support managed storage for root disks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13988659#comment-13988659 ] ASF subversion and git services commented on CLOUDSTACK-6170: - Commit dd3076987f5120bf5bee1457a1b980125139191d in cloudstack's branch refs/heads/4.4 from [~mike-tutkowski] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=dd30769 ] CLOUDSTACK-6170 Corrected an issue related to the Reinstall VM command and managed storage with VMware Support managed storage for root disks -- Key: CLOUDSTACK-6170 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6170 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Environment: I expect to support managed storage for root disks on XenServer and ESX (KVM is targeted for 4.5). Reporter: Mike Tutkowski Assignee: Mike Tutkowski Fix For: 4.4.0 Cloud environments have a need for guaranteed storage performance. By this I mean having the ability to specify a minimum and maximum number of IOPS on a volume-by-volume basis. I added support for this for XenServer and ESX in 4.2 for data disks. I added support for this for KVM in 4.3 for data disks. It is my intent to add support for this for XenServer and ESX in 4.4 for root disks (with subsequent support for root disks on KVM expected in 4.5). The main changes are expected to occur in CloudStack logic that controls hypervisors and additions to the way root-volume orchestration happens. -- This message was sent by Atlassian JIRA (v6.2#6252)
