original_docstring: 
          Returns a list of Volumes (matching those specified on input) with
          enough additional details about each Volume to be able to import the
          Volume into the Cinder Database such as OpenStack can start managing.
          For each Volume the driver needs to return a dictionary containing
          the following attributes:
              uuid:      The UUID of the Volume when created thru OS
              name:      The Name of the Volume defined on the Storage Provider
              status:    The Status of the Volume, matching the definition
              size:      The Size of the Volume in GB
              restricted_metadata: The Additional Meta-data from the Driver
                vdisk_id:   The Identifier for the Volume on the Back-end
                vdisk_name: The Name of the Volume on the Back-end
  
          :param context:   The security context for the query
          :param volumes: A list of dictionary objects for each Volume with:
              uuid:      The UUID of the Volume when created thru OS
              name:      The Name of the Volume defined on the Storage Provider
              restricted_metadata: The Additional Meta-data from the Driver
                vdisk_id:   The Identifier for the Volume on the Back-end
                vdisk_name: The Name of the Volume on the Back-end
          :param server_info: The host info for the attached servers
          
docstring: Returns a list of Volumes (matching those specified on input) with
  enough additional details about each Volume to be able to import the
  Volume into the Cinder Database such as OpenStack can start managing.
docstring_tokens: Returns a list of Volumes ( matching those specified on input ) with enough additional details about each Volume to be able to import the Volume into the Cinder Database such as OpenStack can start managing .
code: def query_volumes(self, context, volumes, server_info={}, mark_boot=True):
          """
          Returns a list of Volumes (matching those specified on input) with
          enough additional details about each Volume to be able to import the
          Volume into the Cinder Database such as OpenStack can start managing.
          For each Volume the driver needs to return a dictionary containing
          the following attributes:
              uuid:      The UUID of the Volume when created thru OS
              name:      The Name of the Volume defined on the Storage Provider
              status:    The Status of the Volume, matching the definition
              size:      The Size of the Volume in GB
              restricted_metadata: The Additional Meta-data from the Driver
                vdisk_id:   The Identifier for the Volume on the Back-end
                vdisk_name: The Name of the Volume on the Back-end
  
          :param context:   The security context for the query
          :param volumes: A list of dictionary objects for each Volume with:
              uuid:      The UUID of the Volume when created thru OS
              name:      The Name of the Volume defined on the Storage Provider
              restricted_metadata: The Additional Meta-data from the Driver
                vdisk_id:   The Identifier for the Volume on the Back-end
                vdisk_name: The Name of the Volume on the Back-end
          :param server_info: The host info for the attached servers
          """
          #Currently the discover/query methods return the same data, so we can
          #return the values passed in since discover was called to get the info
          return volumes
code_tokens: def query_volumes ( self , context , volumes , server_info = { } , mark_boot = True ) : return volumes
short_docstring: Returns a list of Volumes (matching those specified on input) with
  enough additional details about each Volume to be able to import the
  Volume into the Cinder Database such as OpenStack can start managing.
short_docstring_tokens: Returns a list of Volumes ( matching those specified on input ) with enough additional details about each Volume to be able to import the Volume into the Cinder Database such as OpenStack can start managing .
comment: """
          Returns a list of Volumes (matching those specified on input) with
          enough additional details about each Volume to be able to import the
          Volume into the Cinder Database such as OpenStack can start managing.
          For each Volume the driver needs to return a dictionary containing
          the following attributes:
              uuid:      The UUID of the Volume when created thru OS
              name:      The Name of the Volume defined on the Storage Provider
              status:    The Status of the Volume, matching the definition
              size:      The Size of the Volume in GB
              restricted_metadata: The Additional Meta-data from the Driver
                vdisk_id:   The Identifier for the Volume on the Back-end
                vdisk_name: The Name of the Volume on the Back-end
  
          :param context:   The security context for the query
          :param volumes: A list of dictionary objects for each Volume with:
              uuid:      The UUID of the Volume when created thru OS
              name:      The Name of the Volume defined on the Storage Provider
              restricted_metadata: The Additional Meta-data from the Driver
                vdisk_id:   The Identifier for the Volume on the Back-end
                vdisk_name: The Name of the Volume on the Back-end
          :param server_info: The host info for the attached servers
          """$SEP$#Currently the discover/query methods return the same data, so we can$SEP$#return the values passed in since discover was called to get the info