<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <tt>I by mistake sent this earlier to users@ovirt<br>
      I think the right list is engine-devel, hence resending. Sorry for
      the mispost earlier.<br>
    </tt>
    <div class="moz-forward-container"><br>
      <br>
      -------- Original Message --------
      <table class="moz-email-headers-table" border="0" cellpadding="0"
        cellspacing="0">
        <tbody>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
            </th>
            <td>vfs_type not being sent by engine to VDSM for GLUSTER
              DOMAIN case</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
            <td>Mon, 18 Mar 2013 20:23:57 +0530</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
            <td>Deepak C Shetty <a class="moz-txt-link-rfc2396E" href="mailto:deepakcs@linux.vnet.ibm.com">&lt;deepakcs@linux.vnet.ibm.com&gt;</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Organization:
            </th>
            <td>IBM India Pvt. Ltd.</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:users@ovirt.org">users@ovirt.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:users@ovirt.org">&lt;users@ovirt.org&gt;</a>, Sharad Mishra
              <a class="moz-txt-link-rfc2396E" href="mailto:snmishra@us.ibm.com">&lt;snmishra@us.ibm.com&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <meta http-equiv="content-type" content="text/html;
        charset=ISO-8859-1">
      <tt>Hi All,<br>
        &nbsp;&nbsp;&nbsp; I am validating GLUSTERFS Storage domain engine patches
        (worked on by Sharad, in Cc) as posted here...<br>
        <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://gerrit.ovirt.org/#/q/status:open+project:ovirt-engine+branch:master+topic:glusterfs,n,z">http://gerrit.ovirt.org/#/q/status:open+project:ovirt-engine+branch:master+topic:glusterfs,n,z</a><br>
        against VDSM Glusterfs domain support (already upstream in VDSM)<br>
        <br>
        I see the below issue as part of me creatign a new Gluster
        Storage DOmain in the UI<br>
        <br>
        Engine logs...<br>
        <br>
        2013-03-18 13:27:29,149 INFO&nbsp;
        [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]

        (http--0.0.0.0-8700-1) [4b751967] START,
        ConnectStorageServerVDSCommand(HostName = vm-vdsm-de-1, HostId =
        c0ff5edc-4e30-4553-9125-2d1cee9f19ec, storagePoolId =
        00000000-0000-0000-0000-000000000000, storageType = GLUSTERFS,
        connectionList = [{ id: null, connection: vm-vdsm-de-1:dpkvol4,
        iqn: null, vfsType: glusterfs, mountOptions: null, nfsVersion:
        null, nfsRetrans: null, nfsTimeo: null };]), log id: f88d42d<br>
        <br>
        VDSM Logs...<br>
        <br>
        Thread-77::<a moz-do-not-send="true"
          class="moz-txt-link-freetext" href="INFO::2013-03-18">INFO::2013-03-18</a>
        13:32:35,541::logUtils::44::dispatcher::(wrapper) Run and
        protect: connectStorageServer(domType=7,
        spUUID='00000000-0000-0000-0000-000000000000',
        conList=[{'connection': 'vm-vdsm-de-1:dpkvol4', 'iqn': '',
        'portal': '', 'user': '', 'password': '******', 'id':
        '00000000-0000-0000-0000-000000000000', 'port': ''}],
        options=None)<b> --&gt; Notice no vfs_type here !!!</b><br>
        <br>
        VDSM doesn't recv. the vfs_type in the conList dict !!!<br>
        <br>
        I had this small chat with Saggi of VDSM, just to confirm that
        there isn't a possibility that VDSM might be stripping args that
        are recd. from Engine.. and it doesn't.<br>
        <br>
      </tt><br>
      <tt><tt>---------------------------------------------------------------------------------------------------------------------<br>
        </tt>&lt;deepakcs&gt; saggi, Hi<br>
        &lt;saggi&gt; deepakcs: hi<br>
        <br>
        &lt;deepakcs&gt; saggi, Is it possible that VDSM might strip
        down some of the connparams that are recd. as part of
        connectStorageServer ?<br>
        &lt;deepakcs&gt; saggi, In engine log for GLUSTERFS_DOMAIN i see
        vfsType being passed, but connectStorageServer log doesn't show
        vfs_type in the params dict<br>
        &lt;deepakcs&gt; saggi, so wodering where vfs_type is getting
        dropped in this whole process<br>
        &lt;saggi&gt; Probably not being sent<br>
        &lt;saggi&gt; if it's not being logged<br>
        &lt;deepakcs&gt; saggi, engine log has this....<br>
        &lt;deepakcs&gt; 2013-03-18 13:27:29,149 INFO&nbsp;
        [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]

        (http--0.0.0.0-8700-1) [4b751967] START,
        ConnectStorageServerVDSCommand(HostName = vm-vdsm-de-1, HostId =
        c0ff5edc-4e30-4553-9125-2d1cee9f19ec, storagePoolId =
        00000000-0000-0000-0000-000000000000, storageType = GLUSTERFS,
        connectionList = [{ id: null, connection: vm-vdsm-de-1:dpkvol4,
        iqn: null, vfsType: glusterfs, mountOptions: null, nfsVersion:
        nul<br>
        &lt;deepakcs&gt; l, nfsRetrans: null, nfsTimeo: null };]), log
        id: f88d42d<br>
        &lt;deepakcs&gt; saggi,&nbsp; on VDSM side i see this...<br>
        &lt;deepakcs&gt; Thread-77::<a moz-do-not-send="true"
          class="moz-txt-link-freetext" href="INFO::2013-03-18">INFO::2013-03-18</a>
        13:32:35,541::logUtils::44::dispatcher::(wrapper) Run and
        protect: connectStorageServer(domType=7,
        spUUID='00000000-0000-0000-0000-000000000000',
        conList=[{'connection': 'vm-vdsm-de-1:dpkvol4', 'iqn': '',
        'portal': '', 'user': '', 'password': '******', 'id':
        '00000000-0000-0000-0000-000000000000', 'port': ''}],
        options=None) --&gt; Notice no vfs_type here !!!<br>
        &lt;saggi&gt; Then you are not sending the correct connection
        type<br>
        <br>
        &lt;deepakcs&gt; saggi, 'you' means the engine side of code ?
        engine patches is being done by Sharad, and I amtrying to work
        with them on this issue<br>
        <br>
        &lt;deepakcs&gt; saggi, domType=7 is GLUSTERFS_DOMAIN, so its
        correct on that front<br>
        &lt;saggi&gt; If it show nfsRetrans you are using nfs which
        doesn't have a vfs_type argument<br>
        &lt;deepakcs&gt; saggi, but engine log says storageType =
        GLUSTERFS<br>
        &lt;deepakcs&gt; saggi, maybe i can send mail to users@ovirt
        list to see if anybody can provide more clues<br>
        &lt;deepakcs&gt; saggi, but definitely this doesn't looks like a
        vdsm side of issue rite ?<br>
        &lt;saggi&gt; We log the params as we get them<br>
        <br>
        &lt;deepakcs&gt; saggi, right, thats what i also see.. just
        wanted to confirm once with you, before i sent mail to ovirt
        folks<br>
        <br>
---------------------------------------------------------------------------------------------------------------------<br>
        <br>
        <br>
        Can someone help provide any clues on what might be the issue
        here ?<br>
        Because VDSM doesn't see vfs_type, the connectStorageServer
        fails and hence new SD cannot be created !<br>
        <br>
        thanx,<br>
        deepak<br>
        <br>
      </tt><br>
      <br>
    </div>
    <br>
  </body>
</html>