Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 8 Feb 2013 17:47:12 +0000 (UTC)
From: "Chip Childers (JIRA)" <jira@apache.org>
To: cloudstack-dev@incubator.apache.org
Message-ID: <JIRA.12615137.1352286366451.266633.1360345632877@arcas>
In-Reply-To: <JIRA.12615137.1352286366451@arcas>
References: <JIRA.12615137.1352286366451@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-449) Disk I/O polling for instances
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574661#comment-13574661 ] 

Chip Childers commented on CLOUDSTACK-449:
------------------------------------------

I'm not sure if Wido has started working on this or not, but if you want to try to build it, that would be great!
                
> Disk I/O polling for instances
> ------------------------------
>
>                 Key: CLOUDSTACK-449
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-449
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM, Management Server, Usage, VMware, Xen
>            Reporter: Wido den Hollander
>            Priority: Minor
>
> Disk I/O polling for instances would gather disk I/O statistics for root and data volumes attached to instancesn, just like we do with network traffic.
> This enables administrators to figure out how much I/O each instance is doing. In public clouds users might want to start billing for this.
> This is not a monitoring solution for the backing storage, it doesn't alarm about high disk I/O, it simply accounts how much I/O each instance is doing.
> The function specification for this is online at: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Feature+Disk+IO+statistics+for+instances

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira