Great stuff, looking forward and will try the CSI in the next couple of weeks

@bvitnik There is an old CSI for xcp-ng (5 years old) which directly talks to the Xen-API, but I'd rather have a middleware which as @olivierlambert already stated has ACL's and security build-in.
Eventually you will end up in a broken xen cluster because you have a k8s node with cluster wide privileges to the XenAPI.

@olivierlambert Is there any loose roadmap for the CSI?

Cheers,
Jan

@olivierlambert Uh very nice now I got something to play with in the evening I'll let you know once I've created a PoC

@olivierlambert As said, I would be a starting point if the fields of the /vms call will be extended to include ipaddesses, pool_name/id and maybe host_affinity

@olivierlambert sure its a new service discovery plugin in the prometheus core which scrapes http endpoints:
https://prometheus.io/docs/prometheus/latest/http_sd/

It requires this json format:

[
  {
    "targets": [ "<host>", ... ],
    "labels": {
      "<labelname>": "<labelvalue>", ...
    }
  },
  ...
]

Hi,

I was wondering if we could get a REST API Endpoint to discover vms via the prometheus build-in http_sd?

As a starting point it would be nice the get the ips and pool association of vms through the /vms call so that it would be possible to write a wrapper script to match the http_sd format.

Or is this possible and I haven't found the correct fields yet?

Cheers,
Jan

@olivierlambert ah good to know thats fine I'll take a look at the metrics maybe I'll write a small rrd stats pusher script as an interim solution for my usecase until XO6 is available.

Thanks for letting me know

@olivierlambert I'll check later this afternoon, as the loads keeps increasing through the day and let you know if the counter moves.

Should I file a feature request for XOA as support ticket to get the counter into the stats section? Might be an interesting counter for others as well.

@olivierlambert yeah i thought so too is there any way to visualize this in XOA/netdata?

Hi,

I'm trying to get some metrics and info about CPU overcommitment and if there are hosts in my cluster which are fairly unbalanced (not in a configuration kind of way, but where vms fighting to get CPU time).

I've read that other Hypervisors show this kind of data as "CPU ready" counter and that the Xen equivalent should be "runstate_full_contention" (Fraction of time that all vCPUs are runnable (that is, waiting for CPU)). Sadly this counter does not seem to move in my xen center and the netdata plugin does not track the value.

Does anyone have more info around that topic?

Cheers,
Jan