Hi,
we have shown Multiportal to our Customers a few times and noticed that for showcasing it could be useful to hide features like the Backup settings, for example if its run over a different application like Veeam. Maybe this could be added as a function?
Additionally, would a toggle switch for changing a Template or ISO from private to public be a possible addition?
Hello everyone,
would it be possible to add a Handler to Multiportal that deals with the Warnings that recent Proxmox Updates give when using a virtio version newer than 0.1.271? Because currently, from what i can tell, Mutliportal sees the warning, reads it as an error, and sends a deletion task to proxmox instead of letting the create task finish.
Hi,
Is there a feature like Migration or cloning between tenants on the roadmap?
At the moment we use vApp Templates with vCloud Director which have several configured machines in one template.
We would like for example a Tenant or any other repository that holds all these configured setups and then be able to clone them to whichever other tenant needs a specific setup.
Thanks!
@stell / @woody - any update on this? It’s been 70+ days since last MP update. I know you guys were all hands on the migration tool, but MP really needs some love, and we have a number of clients wanting to programmatically (via API) be able to spin up machines. Especially in the new AI age, where agents can do this themselves on any other platform, we are really behind because we do not have this yet.
Hi,
It would be really nice to be able to share specific templates and ISO to specific tenants.
If a reseller has 10 tenants and they want to use a particular template or ISO at present this needs to be uploaded and shared to each tenant (or globally), if they don’t want it to be made globally available then the option to share to just a sub set of tenants would be very handy and save a lot of time and disk space.
Regards,
Mike
Environment
Description
When we create a virtual datacenter via the API, the “reseller” and “tenant” variables in the Proxmox resource pool do not appear to be populated. However, when a datacenter is created via the GUI, the reseller and tenant names do appear there.
Datacenter Name (GUI): Reseller_XYZ.Kunde_ABC.vdc.9672ec9c-4199-43b0-b258-f2ce4135673c
Datacenter Name (API): reseller.tenant.vdc.bbfa10c2-7c52-4d6e-986f-d6c0c156fd80
I also checked the swagger documentation but couldn’t find a way to change this behavior.
Expected Behavior
The ressource pool on Promox includes the reseller and tenant names also when created via api.
Actual Behavior
The ressource pool on Proxmox only includes the id of the virtual datacenter, and doesn’t include the showname of the reseller and tenant when created via api.
Hi,
Just looking at the branding options and found a couple of issues so far ;)
If you choose one of the colour tokens, and then adjust the colours, save to apply, all works fine, but if you then click the option you edited it changes all the colour values back to their default. So would be good to have an option to create a new ‘custom’ token that saves the values you set as defaults.
With the login page settings, after uploading a background image (saving) then loading the page the background image only appears in the top as the height is hardcoded in the CSS as 380px
.auth-one-bg-position {
position: absolute;
top: 0;
left: 0;
right: 0;
width: 100%;
height: 380px;
}
Would be nice to have an option to set this either px or %, whilst changing the CSS will fix this, I’m guessing on an update this will be overwritten.
Thanks,
Mike
|
0
Posts
0
Reputation
|
|
0
Posts
0
Reputation
|
|
0
Posts
0
Reputation
|
|
2
Posts
0
Reputation
|
|
2
Posts
5
Reputation
|
