Description of problem: - How we can check the amount of space utilized on storage domain by any task. - Customer want to know storage space utilized for below activities. * Migrating * Moving to other storage domains * Pausing * Snapshotting * Power on, power off, reboot * Creating * Deleting * Attach and remove direct attached LUNs Version-Release number of selected component (if applicable):not applicable. Additional info: We need RHEV documentation for detailed information about usage of storage domain by above mentioned activities of RHEV.
Yaniv - not sure what's the AI here. Is this a documentation issue or a product issue?
(In reply to Allon Mureinik from comment #1) > Yaniv - not sure what's the AI here. Is this a documentation issue or a > product issue? It's storage issue, since they are looking to tack the storage space utilized for tasks that can be task dependent. We need to provide the stats on this.
(In reply to Yaniv Dary from comment #2) > (In reply to Allon Mureinik from comment #1) > > Yaniv - not sure what's the AI here. Is this a documentation issue or a > > product issue? > > It's storage issue, since they are looking to tack the storage space > utilized for tasks that can be task dependent. We need to provide the stats > on this. Still not clear what the ask is here. Each such operation is checked in the engine, and if there isn't enough free space it fails with a pretty clear message. Can you elaborate what you mean?
Hi Yaniv, Seems yaniv and amureini accounts are disabled. Can you please provide a few quick clarifications? 1. Create storage domain -- depends on size. What does that mean? Can you provide an example or two? 2. Snapshot clone -- how does this affect storage? 3. Snapshot undo -- how does this affect storage? Thanks.
(In reply to Scott Borella from comment #6) > 1. Create storage domain -- depends on size. What does that mean? Can you > provide an example or two? When creating a block storage domain the following lvs will be created: ids 64f87b0f-88d6-49e9-b797-60d36c9df497 -wi-ao---- 128.00m inbox 64f87b0f-88d6-49e9-b797-60d36c9df497 -wi-a----- 128.00m leases 64f87b0f-88d6-49e9-b797-60d36c9df497 -wi-a----- 2.00g master 64f87b0f-88d6-49e9-b797-60d36c9df497 -wi-ao---- 1.00g metadata 64f87b0f-88d6-49e9-b797-60d36c9df497 -wi-a----- 512.00m outbox 64f87b0f-88d6-49e9-b797-60d36c9df497 -wi-a----- 128.00m xleases 64f87b0f-88d6-49e9-b797-60d36c9df497 -wi-a----- 1.00g So you have about 5GB to be used by the system Same goes for file storage > 2. Snapshot clone -- how does this affect storage? Suppose you have a snapshot with a 1GB disk, cloning a VM from it will result in another 1GB disk > 3. Snapshot undo -- how does this affect storage? This clears up storage actually, when you preview a snapshot, a volume is created based on it, so on file domain you will only have the qcow overhead. On block domains, it will be 1GB. Once you undo it is discarded.
RHV 4.3 published.