HUB Templates



  • Can't blame them for trying to pay the bills. ☺

    However, if the Hub feature is going to be available in XOA Free then it would make sense to include it in the Community version as well.


  • XCP-ng Team

    @Biggen said in HUB Templates:

    Nothing has "moved to being paid", all the things you list started as paid only features in XOA - Cloud-init did have a bug where it would be able to be used in lesser license levels, but this was accidental - you can check our commit history on the documentation for it, we intended it to be a premium only feature. What I mean to say is if a feature is going to be paid we make that clear from the get go, we do not release a feature/product for free and then change that later. It's for this reason you do not need to worry about the netdata plugin changing to paid only. It's also worth noting we publish the source code for all the aforementioned paid features - I know there's at least a couple people out there using our XOSAN glusterfs driver in their own (free) projects

    I do understand the frustration with some things only being in paid products, but we have to find a balance of being able to pay the bills so our developers can keep xcp-ng going and release stuff like new plugins


  • XCP-ng Team

    It's even simpler than that: XOA Hub is a service we added, with templates we are hosting.

    All the code is Open Source, but the templates are made and hosted by us. This is a free service we offer for people using Xen Orchestra virtual Appliance (XOA). If you want to use it, then use XOA 🙂

    Regarding Cloudinit, we decided to also offer this feature to all XOA users (including free).

    In short, we are raising value of XOA with extra services, and all the code we do is still fully Open Source. It means you can create your own templates with cloud init (as before) if you use XO from the sources. Only "turnkey" templates we build/provide/deliver are for XOA.

    I hope it's more clear for everyone now 🙂



  • @fohdeesha What I meant by the phrase “Moved to being paid” was that after they were designed, they were moved to the pay model. They were never part of the community version.

    Is the community version frozen as far as new features go? Are we just talking about bug fixes at this point?


  • XCP-ng Team

    Cloudinit was always accessible from the sources. In XOA, it was only officially available in Premium until yesterday (now it's in all XOA plans, even Free).



  • Thank you for clarifying. Just didn't want to bang my head against the wall trying to make it work if its not there in a first place.
    Cheers!



  • I just installed the XOA appliance through the webpage of the server, entered my registration (free), and updated to 5.38 (no newer updates available).
    I also do not see the "Hub" tab.
    Is there something I do wrong?



  • @HeMaN Try refreshing the page. If that doesn't work, then reboot the VM.


  • XCP-ng Team

    You need to be on latest release channel, not stable.



  • @olivierlambert Thank you, this was the solution.
    I was able to create an additional pfSense VM and a Debian 10 VM.
    One question, how do I know the username/pw for the installed Debian VM?


  • XCP-ng Team

    @HeMaN you need to use Cloudinit for Debian VM, using you SSH key for example. User is debian.



  • I can't install any of the templates. I think it's a proxy problem. My XOA gets updates fine through the proxy, but not the templates, it seems.
    dfab8cad-c9bd-4164-9898-db5f208673ed-image.png


  • XCP-ng Team

    Are you sure about your DNS settings? Ping @julien-f if he remembers regarding proxy configuration and XO Hub 🙂 It might be something we didn't check.


  • XO Team

    This is a XenServer/XCP-ng error, I don't know what it means.

    @S-Pam please open a support ticket and a support tunnel if you want us to investigate further.



  • Well, not entirely sure. However both support tunnel and XOA updates work 🙂 Also YUM updates.



  • It's not production critical. Was just curious. I can create VMs and boot with ISOs from my ISO SR.
    What happens is that I click Install
    afd23e67-f265-4acb-ba5b-b6e5169f6b33-image.png
    The little circle spins around for a bit and then a red error box comes up.
    4e05ea4f-3f15-4c23-be7a-91ea6abc5fd6-image.png
    I can't really see any errors in any log on the xcp-ng server or in the xoa console.

    Perhaps it is because I have not updated xcp-ng to latest patch levels yet?


  • XCP-ng Team

    Can you display the whole message? (in Settings/logs, eye icon)



  • This is the error log when I click the little Eye icon. This is from today. I have the latest xcp-ng patches installed.

    cloud.downloadAndInstallResource
    {
      "namespace": "CentOS8",
      "id": "a5e60c2e-cf38-4205-b51f-6fe6d5550f86",
      "version": "1.0.0",
      "sr": "de54f828-dfd2-c44f-c8c8-552c9392deed"
    }
    {
      "code": "ECONNRESET",
      "url": "http://localhost:9002/",
      "message": "socket hang up",
      "name": "Error",
      "stack": "Error: socket hang up
        at createHangUpError (_http_client.js:342:15)
        at Socket.socketOnEnd (_http_client.js:437:23)
        at emitNone (events.js:111:20)
        at Socket.emit (events.js:208:7)
        at Socket.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/src/configure.js:94:16)
        at endReadableNT (_stream_readable.js:1064:12)
        at _combinedTickCallback (internal/process/next_tick.js:139:11)
        at process._tickCallback (internal/process/next_tick.js:181:9)"
    }
    

    EDIT: Also tested Alpine Linux. Same issue.

    XOA has connectivity and can update itself through the proxy.I'm thinking that the problem with the HUB installer is that it doesn't use the pre-configured proxy.

    cloud.downloadAndInstallResource
    {
      "namespace": "Alpine3",
      "id": "053f2391-a122-4b09-98d0-c0902a8eb342",
      "version": "1.0.0",
      "sr": "de54f828-dfd2-c44f-c8c8-552c9392deed"
    }
    {
      "code": "ECONNRESET",
      "url": "http://localhost:9002/",
      "message": "socket hang up",
      "name": "Error",
      "stack": "Error: socket hang up
        at createHangUpError (_http_client.js:342:15)
        at Socket.socketOnEnd (_http_client.js:437:23)
        at emitNone (events.js:111:20)
        at Socket.emit (events.js:208:7)
        at Socket.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/src/configure.js:94:16)
        at endReadableNT (_stream_readable.js:1064:12)
        at _combinedTickCallback (internal/process/next_tick.js:139:11)
        at process._tickCallback (internal/process/next_tick.js:181:9)"
    }
    

    6c0a9c43-4cdf-4b18-8d78-7e8a7ffbc8b4-image.png


  • XCP-ng Team

    Ping @pdonias do we have an issue opened with this?


  • XO Team

    I'm not seeing any. And I don't think this would be fixed by @julien-f's recent change on xo-server-xoa since it should already use the configured proxy by going through the updater.

    /cc @Mohamedox


Log in to reply
 

XCP-ng Pro Support