In our experience with both XenServer and KVM by increasing the size of the underlying system CS automatically noticed and updated itself. I know this is a bit different with regard to what you're doing since you're talking about individual volumes and I'm referring to primary storage repositories. But in the past we have increased a primary storage repo by several TB and shortly after the hypervisor noticed the change CS updated itself to reflect the new size of the primary storage repo. This was true with sharedMountPoint on KVM as well as LVMoISCSI on XenServer. I would imagine it would react in a similar fashion to VMFS and VMware.
-Clayton -----Original Message----- From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] Sent: Thursday, February 28, 2013 10:37 AM To: cloudstack-dev@incubator.apache.org Subject: CS Administration Question Hi, Can someone give me an idea what a CS Admin might do when a volume begins to reach its capacity? For example, let's say we start with a 100 GB iSCSI volume. We create a storage repo for it in XenServer or a datastore for it in VMware. When we're getting close to the 100 GB capacity, does he go into the SAN and extend the volume, then make the hypervisor aware of the extended size? Is there anything he can do in CS? Perhaps he creates a new iSCSI volume, then new Primary Storage in CS (tagging it the same as the other PS based on our 100 GB iSCSI volume)? Thanks! -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *(tm)*
