@olivierlambert Yes, Vates is on another level of professionalism. Wow

What you guys say about it. I'm using open-stack at scale and automated everything using there sdk(python-based). Now I'm thinking to properly move to xcp-ng and use its apis(rest+json-rpc) for automating the process. What will you say about it? I need your suggestions on it?

What will you say on virtualization and public cloud? Can we make it to work like a public cloud.

@olivierlambert Yes, Vates is on another level of professionalism. Wow

@DustinB @cciecanuck Thank you.

@olivierlambert as shared earlier by @julien-f on this thread that we can only create vm on pool level and @olivierlambert said XO will automatically pick the host which has sufficient resources available for that vm. Can we manually pick the host in the pool to deploy a vm?

@DustinB If I add 20 hosts to a pool and create a VM in that pool, will it automatically pick the host that has sufficient resources available, such as CPU and RAM?

xcp-ng is a distribution which runs on a bare-metal and allow us to perform virtualization. I want to know more about hosts, pools. What is the difference between these two concepts. Also what is cluster and What about HA? Where does the HA happen? b/w pools or b/w hosts?

@Danp For now I'm going with JSON-RPC for only VM creation and for listings I'm using rest-apis. When XO6 will release I'll change the endpoint with rest endpoint. @olivierlambert any expected release date for XO6?

@olivierlambert omg I'll upgrade the XO. My question is still same, why the rest-api is not responding properly when I hit it from postman and the same api is responding with error when using xo-cli

@olivierlambert Thank you for your time. I've a paid subscription but I am using XO from sources. I've opened a ticket from the help desk

@Danp said in XO Rest API:

Is your VM up-to-date with the latest sources?

Yes I configured the XO from sources and it's not up to date. Should I update my XO and will it fix the issue or not?