I still don`t understand why I need to give out Sys.Config to have the node download an iso to it`s datastore.
There`s:
Datastore.AllocateTemplate: allocate/upload templates and ISO images
And you don't need the power to modify the host network to do that task afaik... can someone try to...
Unfortunetly the /cluster/status page is not string match friendly, not for my use case anyways.
Wondering if everyone is simply using / and don't care if they reach an isolated node.
Could you point me in the general direction to extend pveproxy to add a /health/ready endpoint?
I'll try to do...
Having multiple proxmox instances (in various state) behind a load balancer and wanting to pass API request to live and ready instances only, I need a simple endpoint (return 200 OK) to show that the required services on each instance is in a good state.
A proxmox instance that has no (or lost)...
Probably the same answer as here: https://forum.proxmox.com/threads/proxmox-ui-caddy-and-reverse-proxy.83198/
You need to deal with the self-signed certificate proxmox generated or add a valide certificate.
And you most likely will need ip_hash instead of least_conn for the load balancing...
Health_uri being simply /, does it exclude hosts in maintenance or perhaps not part of the cluster?
I'm searching for a /live and /ready endpoint on the api but not finding anything close to that...
ref. https://testfully.io/blog/api-health-check-monitoring/#api-health-check-endpoint-types
Yes, got it working simply using the GUI
The catch is in the "key" field where you don't paste juste the key but the whole block like:
[client.admin]
key = .....
And make sure to put all the ceph mon space delimited.
Thanks
The SNV3400 do not have power loss protection so may not be ideal for write caching.
Ref: https://www.synology.com/en-ca/products/solid_state_drives/SNV3000#specs
Anyone has recommendations for m.2 nvme good to use, I know of Micron 7300 and Samsung DCT 983... what else?
Your latest patch works on pve-manager >= 6.1-8 ?
If so, could you also paste a link here I'd like to manually patch in the mean time... worried about staying pinned to 6.1-7 while the rest of proxmox is updated frequently.
Thanks
It seems the last update to pve-manager (6.1-8) don't work proper even after re-applying the patches.
I now get a "Unable to parse network options" in the GUI trying to open Hardware -> Network Device (net0).
[edit] Reverted pve-manager to 6.1-7 and applied your patch for pvemanagerlib.js and...
The pvesh list doesn't tell use the name of the vm and there's no way to tell which are template.
I've been searching around and cannot find how to list all vm in the cluster but also have their names and whether it's a template or not.
qm list isn't working either as no cpu info nor template or...
I've applied the patch and restarted pveproxy, but I get:
Error
Parameter verification failed. (400)
net0: invalid format - format error net0.mtu: property is not defined in schema and the schema does not allow additional properties
What else needs a restart to make it work? [edit: answering my...
Thanks @Alwin
I was hoping to see a clear indication to keep the keyring option under [osd] since it's using a different path than the client keyring. The ending of the phrase: "[...], and remove it everywhere else." will still cause confusion and should be removed/reworded imho.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.