XOSAN Feedback



  • Short answer: you are correct.

    Longer answer: XenServer can't create a VM disk larger than 2 TiB. This is a limit due to VHD file format, which can't be larger than 2 TiB (FYI, this limit is far higher for VHDX format, but not yet supported in XenServer).

    So will it be a "final" limit for XOSAN? Nope. Because we planned to have multiple data disk possibility by XOSAN VM. So we could have 2x2 TiB in each VM, and use those disks in the whole cluster. It's not possible yet, but it's a goal we are ready to reach in few releases (before the end of the year at worst).

    The main issue will be probably an UI issue because it starts to be complex in the end to expose all those possibilities 🙂



  • Tried to install it on a 2 node xen7.2 cluster. It installed 2x VMs on each node, then deleted them. Then the web console said "Unknown error from peer"



  • Check the log entry in Settings/logs please



  • It says "SR_UNKNOWN_DRIVER(xosan)"!



  • xosan.createSR
    {
      "template": {
        "id": "1",
        "version": "0.0.2",
        "name": "xosan",
        "description": "XOSAN Beta",
        "size": 730000000,
        "type": "xva",
        "data": {
          "public": {
            "any": "any"
          }
        }
      },
      "pif": "d6b6f979-04ec-94e7-33ca-a72d0c30686d",
      "vlan": "0",
      "srs": [
        "4d8fc1c7-7f0e-50c8-892a-d654dd7720d7",
        "33e8df90-41ae-c484-7d66-726fa3d70f69"
      ],
      "glusterType": "replica_arbiter",
      "redundancy": 3,
      "memorySize": 2147483648
    }
    {
      "message": "SR_UNKNOWN_DRIVER(xosan)",
      "stack": "XapiError: SR_UNKNOWN_DRIVER(xosan)
        at wrapError (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/src/index.js:81:34)
        at /usr/local/lib/node_modules/xo-server/node_modules/xen-api/src/index.js:873:16
        at tryCatcher (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/util.js:16:23)
        at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:512:31)
        at Promise._settlePromise (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:569:18)
        at Promise._settlePromise0 (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:614:10)
        at Promise._settlePromises (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:689:18)
        at Async._drainQueue (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:133:16)
        at Async._drainQueues (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:143:10)
        at Immediate.Async.drainQueues (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:17:14)
        at runCallback (timers.js:672:20)
        at tryOnImmediate (timers.js:645:5)
        at processImmediate [as _immediateCallback] (timers.js:617:5)",
      "code": "SR_UNKNOWN_DRIVER",
      "params": [
        "xosan"
      ],
      "method": "SR.create"
    }
    


  • Have you restarted toolstack on your 2 nodes? Try this and then install again XOSAN. Let me know.



  • Is Xosan across pools something that is being considered?
    It would be useful for those who have servers that cannot be in the same pool but would like to share storage.



  • No, because of XenServer pool structure mainly. So it's not a fit for hyperconvergence.

    However, another option would be to connect XenServer to a single (large) Gluster storage, with various shares (one per pool).



  • @olivierlambert said in XOSAN Feedback:

    However, another option would be to connect XenServer to a single (large) Gluster storage, with various shares (one per pool).

    Actually, this is where I would like to go. Is this on the roadmap?



  • @timrash the driver will be available on GitHub. You will be able to install it manually. And obviously, if you have XOSAN, you still have the possibility to easily add an external Gluster storage.



  • When trying to create a new XOSAN, upon submission it quietly fails part way through, and this error message appears in the log, Could a patch have removed xosan? from the hosts? If so how would i force a re-install?

    task.destroy
    {
      "id": "e227120a-fe86-4eba-85a2-5418b19ce8bd"
    }
    {
      "message": "HANDLE_INVALID(task, OpaqueRef:d9dfaa5b-c3dc-615f-12f0-89dfb659e3d7)",
      "stack": "XapiError: HANDLE_INVALID(task, OpaqueRef:d9dfaa5b-c3dc-615f-12f0-89dfb659e3d7)
        at wrapError (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/src/index.js:83:34)
        at /usr/local/lib/node_modules/xo-server/node_modules/xen-api/src/index.js:868:16
        at tryCatcher (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/util.js:16:23)
        at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:512:31)
        at Promise._settlePromise (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:569:18)
        at Promise._settlePromise0 (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:614:10)
        at Promise._settlePromises (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:689:18)
        at Async._drainQueue (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:133:16)
        at Async._drainQueues (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:143:10)
        at Immediate.Async.drainQueues (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:17:14)
        at runCallback (timers.js:672:20)
        at tryOnImmediate (timers.js:645:5)
        at processImmediate [as _immediateCallback] (timers.js:617:5)",
      "code": "HANDLE_INVALID",
      "params": [
        "task",
        "OpaqueRef:d9dfaa5b-c3dc-615f-12f0-89dfb659e3d7"
      ],
      "method": "task.destroy"
    }
    
    


  • Never saw this error before 😞 Have you restarted the toolstack?



  • Trying to install XOSAN but not working.

    The message is

    No compatible XOSAN pack found for your XenServer versions.
    At least one of these version requirements must be satisfied by all the hosts in this pool:

    0_1516032144352_Screen Shot 2018-01-15 at 10.53.49.png

    And there is no log

    Configuration is 2 nodes like this :

    CPU model Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
    Core (socket) 32 (2)
    RAM 256 GiB
    Local Storage 14.55 TiB (LVM)
    Citrix XenServer 7.2.0 (free)
    Fully patch



  • Hey there! That's strange. Can you send me a private message with the result of xoa support tunnel, this way I can access your XOA and take a look myself 🙂



  • Sorry if this is an obvious question. But does each XenServer participating in the XOSAN need to be a member of the same pool?



  • @markhewitt1978 Yes, otherwise it won't make sense at all.



  • Giving XOSAN a try - as it would seem it would fit my requirements if it worked.

    Got 2x XenServer 7.0 clean installs. Put the two machines into one pool. Then I've created an XOSAN on the pool. It went ahead and created 1x VM on server 1 and 2x VM on server 2, and a shared repository called XOSAN of 50gb.

    I created a 10GB CentOS7 VM and attempted to move it to the XOSAN but it fails with the machine on or off with the error "The attempt to create a VDI failed"

    The logs section of XOSAN says "No logs so far"

    Any advice?



  • Everything is healthy in the XOSAN tab of XOSAN SR?



  • @olivierlambert
    Yes the four icons across the top are green.



  • And if you try to create a disk directly on XOSAN?