In v2.0, the 'Capacity' option seems to have replaced Instance templates. This is fine if it worked as expected.
I've tried playing around with this, but while the memory selection is fine, the CPU selection is now harder. I like the idea of end users being able to select a number of CPU's from a list or slider, but only if it's simple!
If I set the 'CPU' selection as fixed to 1, but set the vCPU to between 1-4,then deploy a VM with the vCPU set to '2', I end up with a VM with 2 x 1 core virtual sockets (not what I wanted). If I set vCPU fixed to 1, then modify the CPU setting, the slider is now allowing settings in the 1.xx range (not logical for the user). I've tried various ways of configuring the Sunstone template without success. The VMware template has a default setting of 1 socket, 1 core.
So, what I'm saying is, I need a simple way for end-users to just specify the number of CORES for the VM. Keep the CPU sockets locked at 1 in the template if possible.
Can you do this? I've checked the OpenNebula docs, but that's a bit vague as well.