pvesh vs. vzlist, and storing extra attributes on containers.

[Martin Cleaver]

1) Pvesh vs vzlist

Because pvesh help doesn't work (http://forum.proxmox.com/threads/18765-pvesh-error-API-issue?p=97847#post97847), and the documentation lacks, I figured I'd use vzlist to get a list of objects (containers+kvm objects - sorry, don't know the generic term).

Apart from (I assume) no support for kvm, are there any substantial differences between pvesh and vzlist for getting this list? Does PVE do anything strange to openvz, or will all openvz commands work?

I want a list of objects as I plan to generate an apache.conf file for each object such that incoming web requests that hit the pve node can automatically reverse proxied to the right object. (See http://forum.proxmox.com/threads/19042-DNS-wildcard-to-peer-container-web-routing?p=97642#post97642)

2) I'd like to store extra attributes on each container.
Is that possible? In this case I'd need to store what port takes the incoming web traffic, and possibly what DNS like name to route web traffic from.

I'm new to proxmox, caveat emptor.

Thanks,
Martin.

 

[dietmar]

Apart from (I assume) no support for kvm, are there any substantial differences between pvesh and vzlist for getting this list? Does PVE do anything strange to openvz, or will all openvz commands work?

vzctl ommands will work, but please use pvectl to create new CTs.

2) I'd like to store extra attributes on each container.
Is that possible?

yes

 

[Martin Cleaver]

Thanks Dietmar. Now, can I add new attributes via the web UI? Is there a naming convention to ensure an attribute name I pick won't later get picked for system use?

 

[dietmar]

Now, can I add new attributes via the web UI?

no

Is there a naming convention to ensure an attribute name I pick won't later get picked for system use?

This is openvz specific, so please ask on the openvz lists.