ah sorry. Yes. From the CloudStack management UI, you can force cloudstack to reconnect to the host. This forces cloudstack to flush it's connection and restablish the connection. On restablishing the connection, there's a series of checks and information gathered. Size of the storage pool is one such information.
--Alex > -----Original Message----- > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > Sent: Wednesday, July 10, 2013 3:13 PM > To: dev@cloudstack.apache.org > Subject: Re: Expanding a volume on a SAN > > Hey Alex, > > When you say, "force a reconnection," I'm not sure to what part of the > system you're referring. Is this an action performed on the CloudStack side? > > Thanks! > > > On Wed, Jul 10, 2013 at 4:10 PM, Alex Huang <alex.hu...@citrix.com> wrote: > > > You might have to force a reconnection to the xenserver in order for > > CS to see it. On every connection, CS checks these items and updates > > its database. > > > > --Alex > > > > > -----Original Message----- > > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > > > Sent: Wednesday, July 10, 2013 2:14 PM > > > To: dev@cloudstack.apache.org > > > Subject: Re: Expanding a volume on a SAN > > > > > > OK, great - thanks! > > > > > > So, it sounds like on XenServer, you have to perform some manual > > > activity for it to see the new size of the iSCSI target (and there > > > is probably a > > similar > > > requirement with ESX), but CloudStack will notice the size > > > difference automatically (once the storage repository or datastore > > > has been manually re-configured). > > > > > > > > > On Wed, Jul 10, 2013 at 2:48 PM, Anthony Xu <xuefei...@citrix.com> > > wrote: > > > > > > > CS will see the new size, > > > > > > > > > > > > Anthony > > > > > > > > -----Original Message----- > > > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > > > > Sent: Tuesday, July 09, 2013 5:25 PM > > > > To: dev@cloudstack.apache.org > > > > Subject: Re: Expanding a volume on a SAN > > > > > > > > Hey Anthony, > > > > > > > > I assume this would be a candidate situation where you'd put the > > > > primary storage in maintenance mode and then perform the steps you > > > referred me to? > > > > > > > > When the storage is brought out of maintenance mode, will it see > > > > the new size or is there something more that has to be done on the CS > side? > > > > > > > > Thanks! > > > > > > > > > > > > On Tue, Jul 9, 2013 at 6:09 PM, Mike Tutkowski < > > > > mike.tutkow...@solidfire.com > > > > > wrote: > > > > > > > > > Thanks! > > > > > > > > > > Anyone know if CloudStack will recognize the new size of a > > > > > storage repository or datastore on its own? > > > > > > > > > > > > > > > On Tue, Jul 9, 2013 at 4:01 PM, Anthony Xu > > > > > <xuefei...@citrix.com> > > > wrote: > > > > > > > > > >> http://support.citrix.com/article/CTX120865 > > > > >> > > > > >> for XenServer, VMs need to be shut down or migrated away before > > > > >> expanding a volume. > > > > >> > > > > >> > > > > >> Anthony > > > > >> > > > > >> -----Original Message----- > > > > >> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > > > > >> Sent: Tuesday, July 09, 2013 2:25 PM > > > > >> To: dev@cloudstack.apache.org > > > > >> Cc: Edison Su; John Burwell > > > > >> Subject: Expanding a volume on a SAN > > > > >> > > > > >> Hi everyone, > > > > >> > > > > >> I had a question posed to me today regarding how CloudStack and > > > > >> the underlying hypervisor deal with an iSCSI volume that is > expanded. > > > > >> > > > > >> For example, let's say I'm using XenServer or ESX and I create > > > > >> a storage repository or datastore, respectively, for each > > > > >> hypervisor based on an iSCSI target. I then tie this into > > > > >> CloudStack as Primary > > > > Storage. > > > > >> > > > > >> If I increase the size of the iSCSI target (the SAN > > > > >> volume/LUN), does this increased size feed into the hypervisor and > CloudStack? > > > > >> > > > > >> 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)* > > > > >> > > > > > > > > > > > > > > > > > > > > -- > > > > > *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)* > > > > > > > > > > > > > > > > > > > > > -- > > > > *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)* > > > > > > > > > > > > > > > > -- > > > *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)* > > > > > > -- > *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)*
