Custom Variables Tab in VM, Template, Container, Host, Storage etc.

[Marek Wajdzik]

Hello,

Is there a possibility to define variable, that is accessible by proxmox API in each object type like VM, Template, Container, Host or Datastore?

If no, simple tab with key and value added to all objects in proxmox gui will be awesome, because this will allow to build extensions for ansible dynamic inventory or cloudinit datasource using proxmox API returning those KVs. Also, it will be great if proxmox API could listen also on link-local address in vmbr0 (accessibility to it, before network will be up especially to use with cloudinit)

Or, just tell me how to start writing code with you guys )

 

[dcsapak]

no that is not possible at the moment, but what exactly are you trying to save there ?

Or, just tell me how to start writing code with you guys )

https://pve.proxmox.com/wiki/Developer_Documentation

if you have questions on this, just ask on the pve-devel list

 

[LnxBil]

I can relate to the idea of custom variables. We currently deploy "custom variables" by using a special ascii format for the notes of the VM, which will be parsed and then further processing will be performed. Another part of customization is via pools and furthermore via DHCP for each, so it would be great to have all necessary and possibly configuration in one place: the PVE vm/container.

 

[Marek Wajdzik]

First of all I wanted to create development VM - I've used vagrant for it:

github.com/consi/proxmox-devel-vagrant

But well, documentation is incomplete (5.x does not use jessie, it uses other apt key and so on) - that was easy to fix, but I don't have read access to some repositories defined in documentation:
failed: [proxmox-devel] (item=libpve-http-server-perl) => {"changed": false, "cmd": ["/usr/bin/git", "fetch", "--tags", "origin"], "failed": true, "item": "libpve-http-server-perl", "msg": "Failed todownload remote objects and refs: fatal: remote error: access denied or repository not exported: /git/libpve-http-server-perl.git\n"}
failed: [proxmox-devel] (item=libpve-apiclient-perl) => {"changed": false, "cmd": ["/usr/bin/git", "fetch", "--tags", "origin"], "failed": true, "item": "libpve-apiclient-perl", "msg": "Failed to download remote objects and refs: fatal: remote error: access denied or repository not exported: /git/libpve-apiclient-perl.git\n"}

How could I fix that?

Regards
Marek

 

[LnxBil]

But well, documentation is incomplete (5.x does not use jessie, it uses other apt key and so on) - that was easy to fix, but I don't have read access to some repositories defined in documentation:

Where did you read that 5.x is using jessie? The installation is well documented on the wiki:

https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Stretch

failed: [proxmox-devel] (item=libpve-http-server-perl) => {"changed": false, "cmd": ["/usr/bin/git", "fetch", "--tags", "origin"], "failed": true, "item": "libpve-http-server-perl", "msg": "Failed todownload remote objects and refs: fatal: remote error: access denied or repository not exported: /git/libpve-http-server-perl.git\n"}
failed: [proxmox-devel] (item=libpve-apiclient-perl) => {"changed": false, "cmd": ["/usr/bin/git", "fetch", "--tags", "origin"], "failed": true, "item": "libpve-apiclient-perl", "msg": "Failed to download remote objects and refs: fatal: remote error: access denied or repository not exported: /git/libpve-apiclient-perl.git\n"}

How could I fix that?

I have no idea where you get these errors from, yet those git repositories are not listed here: https://git.proxmox.com/

 

[Marek Wajdzik]

Well, on stretch I can't even install prerequisities from instruction above, also, those repositories are listed in this README - so I think, that it's outdated

I'll try first to install it without development files, then I add rest

 

[LnxBil]

Please be more precise what you did and where you get your information from (what prerequisites and what readme). Neither the Developer page as nor the install on stretch nor the https://git.proxmox.com/ does not mention the repositories you're talking about.

 

[Marek Wajdzik]

I'm talking about this instruction: https://git.proxmox.com/?p=pve-common.git;a=blob_plain;f=README.dev;hb=HEAD

(which doesn't work on stretch, but goes completly fine on jessie)

 

[LnxBil]

Okay, I see. Please open a bug report to get this file updated on https://bugzilla.proxmox.com/

 

[Marek Wajdzik]

Okay, I see. Please open a bug report to get this file updated on https://bugzilla.proxmox.com/

Modified vagrant with instruction from: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Stretch works fine, but I'm not sure that it will be good base for development, as I don't have latest source from git

 

[LnxBil]

but I'm not sure that it will be good base for development, as I don't have latest source from git

Just find out to which package the file belongs to and check out the corresponding GIT repository from https://git.proxmox.com/, build the debian package etc.

 

[Marek Wajdzik]

So after some time I've migrated vagrant to git submodules and it works, I've made first changes to pve-manager and it seems to be fairly easy Thanks for pointing instructions that helped me to start development environment

 

[LnxBil]

Hope to see you again on the pve-devel mailing list.

 

[damies13]

Did this ever get developed? It's something that would be really useful to me, and probably others.
Years ago I worked with a dev team that used a similar feature in VMWare for their orchestration for dynamic environments, they would put host names in the variables,
e.g. spin up a db server and note the hostname, then spin up multiple app servers and use this feature for the db server's hostname, the app server then used this value to connect to the db