When I was developing the SolidFire plug-in for 4.2, I noticed the folder column wasn't being used, as well.
I repurposed it for SolidFire plug-in volumes to store the ID of the iSCSI volume (LUN) on our SAN. On Tue, Jul 16, 2013 at 8:39 AM, Sanjay Tripathi <sanjay.tripa...@citrix.com > wrote: > Thanks for the reply Edison, I still have a query though... > > if CS has more than one primary storage in a cluster and admin wants to > know about > location of a volume i.e. in which primary storage this volume is in, than > as per current behavior, admin has to > search in all the primary storage by using the id given in "path" column. > > Is this the correct behavior or am I missing something. > > --Sanjay > > > -----Original Message----- > > From: Edison Su [mailto:edison...@citrix.com] > > Sent: Friday, July 12, 2013 10:55 PM > > To: dev@cloudstack.apache.org > > Subject: RE: NULL entry in folder colum in volumes table > > > > It's changed to use the "path" only. > > > > > -----Original Message----- > > > From: Sanjay Tripathi [mailto:sanjay.tripa...@citrix.com] > > > Sent: Friday, July 12, 2013 4:27 AM > > > To: dev@cloudstack.apache.org > > > Subject: NULL entry in folder colum in volumes table > > > > > > Hi, > > > > > > I have noticed a change in the "volumes" table that CloudStack is not > > > setting up the any value in "folder" column. The entry used to tell us > > > about the location of volume in the primary storage, but now it is > > > NULL. So we can't figure out the location where this volume is located. > > > > > > Can somebody clarify if this has been done purposefully or should we > > > treat this as a bug. > > > > > > --Sanjay > -- *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> *™*
