to summarize what thomas and i discussed off-list:
1. i'll try to integrate arrays into the section config in pve(pbs has
rudimentary support,
but no "automatic" api integration)
including a sensible api create/update/delete schema:
- plan is to have the inner properties exposed but require an id parameter
that identify which entry of which array property is to be updated
i'll send this as a separate series, since for the remaining code it's
not really relevant where the schema/config comes from, the internal
api of that will probably be similar
2. Config should be per type (as mentioned in the last responses)
and on create/update we'll not check for existence/correctness etc. for now
(we can do that still when we broadcast the relevant info in pmxcfs in the
future)
we'll do the checks for that and insert the info in the gui and on vm
start/migration/etc.
also i'll combine some id properties when we don't require them separately,
e.g. vendor/device.
and make it clear in the description that these are for consistency checks
on start
3. API will probably go to /cluster/resource/$type/$id
where the get/create/put/delete depends on the above mentioned map id
parameter for editing
single entries
(pending a better name than 'resource' since it's very similar to
/cluster/resources
which is an entirely different thing)
4. Most of Markus' permission structure is ok, besides replacing 'Map.' with
'Resource.'
depending on which name we choose in the api
5. we'll probably remove the usermgmt permissions for PVEAdmin (to set it apart
from the
Administrator role)
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
