No reply to this topic but just seen same thing.

And same "workaround" : disabling vTPM at VM creation from template to avoid crashing.

I can confirm that XOA want to add a second vTPM, any fix ?

Indeed, I have 39 commits behind...

I can't do it now, as I have several users working on it.

I'll do this before next week, I come back if it's changing something.

@olivierlambert Hi,

I use xo from sources. Update two weeks ago.

From CHANGELOG :

• @vates/types 1.10.0
• @xen-orchestra/web-core 0.27.0
• @xen-orchestra/rest-api 0.14.0
• @xen-orchestra/web 0.25.0
• xo-server 5.185.0

Thank you

Update : same thing when adding or changing "tags" field.

Hi,

I have a big trouble with playing with xo-cli to update my resource sets.

First, it's really annoying that templates and tags assigned to them aren't update (I want that user "X" cans use all tamplates with "X" tags; I tag a new template, I have to add manually it to resource set...).

Whatever, I build a script who list object, list taggued templates and with resourceSet.set "rebuild" objects array.

What a surprise when I realize that my new template is here, but all of my limits aren't!
So, to see if it's my script which blow away quotas, I test manually on one resource set, it's the same.

For exemple :

{
  "id": "h-PSp-FzCb0",
  "ipPools": [],
  "limits": {
    "cpus": {
      "total": 6,
      "usage": 1
    },
    "memory": {
      "total": 17179869184,
      "usage": 2147483648
    },
    "disk": {
      "total": 80530636800,
      "usage": 17179869184
    },
    "vms": {
      "usage": 1
    }
  },

I launch

xo-cli resourceSet.set id="h-PSp-FzCb0" objects=json:"["71359f87-2297-a2d9-1236-77ebfcbe71eb","74f92165-9f40-a6b0-26e2-6377409d3911","92751eb2-0007-fa22-9001-1b08db171145","dd467579-027a-21a7-5c81-1a396312befb","89ef16d0-9fc6-3bb0-8161-37dc69e64b3b","94f4a9be-5614-9a2b-a389-d0b2c8228b60"]"

And tadaaa !

limits: {"cpus":{"usage":1},"memory":{"usage":2147483648},"disk":{"usage":17179869184},"vms":{"usage":1}}

Is there anything that I'm missing ??

@olivierlambert thank you for your response.

Just tested with another laptop : no more issue...

Well, we will inform our future users and wait for v6 !

Re: VM console borks with "Alt Gr" key

This topic was opened in 2020 and five years later, this issue is still here.

Weird thing : yesterday, working all the day with my Ubuntu laptop : no issue.
This morning : working with my Win11 PC : issue is here.

Will test with laptop later this day

And yes, no more issue on v6 version.

No reply to this topic but just seen same thing.

And same "workaround" : disabling vTPM at VM creation from template to avoid crashing.

I can confirm that XOA want to add a second vTPM, any fix ?

Thanx !

I will check out with your team at the start of the new year for subscription, maybe we will discuss about it.

@olivierlambert said in User self-service creation automation:

I don't think it's possible to treat that "automatically" as it's a very specific use case. However, it should be possible to script that using our API.

I don't think so. It's definetivly not an hypervisor must-have feature, but cloud yes. If you are a cloud provider and providing compute to customers, you will want to build "plans" for subscritpion and assign it automatically when user create his account and choose is plan.

It is the same thing here, instead of not having bilings and several plans.

Have a nice Christmas !

Yes, all students will have a self-service with same quotas, templates, etc.
And all teacher will have also their own "template" for self-service.

And yes, there is some webhook in LemonLDAP, I don't know if it's the best solution for me now. I started to build a user dashboard with homer (because computing will not be the only service), with a button used by the user to create their self-service space in order to track it and send ticket if it fails.

I will try to script it with a flask API triggered by clicking the button, I don't know something like :

class Config:
    XO_API_URL = os.getenv('XO_API_URL', 'https://xo.domain.com/api/')
    XO_ADMIN_USER = os.getenv('XO_ADMIN_USER')
    XO_ADMIN_PASSWORD = os.getenv('XO_ADMIN_PASSWORD')
    JWT_SECRET = os.getenv('JWT_SECRET')
    POOL_NAME = "AMI"
    NETWORK_COUNT = 5
    RESOURCES = {
        'cpus': 6,
        'memory': 16 * 1024 * 1024 * 1024,  
        'disk': 150 * 1024 * 1024 * 1024     
    }

And then pass it to XOA API...

I will try it and see if it work, in that case, I will post code here.

@olivierlambert

OK, I will try to make it as clear as possible :

Context : Group of schools or training center which want to have a private cloud infrastructure for eduational purpose
Number of user : around 500, not at the same time
Essentials need : each user can use a sandboxed space to run their own virtuals machines, with internal networks inside. They cannot acces to hypervisor stack, and they cannot access to other's spaces
Optional need : if teachers wants, two or more student can work on a shared space. They cannot acces to hypervisor stack, and they cannot access to other's spaces
Workflow : users will be created in an OpenLDAP server, upon it a LemonLDAP will bring user portal and SSO. XOA will use this SSO to allow access.

So, satrting at this point, SSO connexion is not a problem, it's well handled by XOA.
But as I said, when a new user comes, admin must create manually is self-service "pod"

I'm starting to create a plugin who handles first user login and create a related self-service with quotas and internals network.

EDIT : just found this : https://github.com/vatesfr/xen-orchestra/issues/768 exactly what I mean.

julien-f created this issue in vatesfr/xen-orchestra

closed Self service: resource-set templates #768