I don't mean to be rude but you said you only have 1 month of experience with Linux. I don't know you or your previous experience but if I were to guide myself based on people who I've worked with who only have 1 month of Linux experience, setting up an orchestrating solution for VMs might be a bit much. Why not try to make use of the built-in management tools instead?
We run open source Xen for virtualization purposes and although I have to admit I didn't do the setup, here's what I know:
- If you're coming from a Linux system, you should be able to manage the host using the "xm" command, i.e.:
[root@xen02 ~]# xm
Usage: xm [args]
Control, list, and manipulate Xen guest instances.
Common 'xm' commands:
console Attach to 's console.
create Create a domain based on .
destroy Terminate a domain immediately.
dump-core Dump core for a specific domain.
help Display this message.
list List information about all/some domains.
mem-set Set the current memory usage for a domain.
migrate Migrate a domain to another machine.
pause Pause execution of a domain.
reboot Reboot a domain.
restore Restore a domain from a saved state.
save Save a domain state to restore later.
shutdown Shutdown a domain.
trigger Send a trigger to a domain.
top Monitor a host and the domains in real time.
unpause Unpause a paused domain.
uptime Print uptime for a domain.
vcpu-set Set the number of active VCPUs for allowed for
If you're coming from a Windows workstation OR you want a GUI to use when managing from Linux, there's (either by default or perhaps it requires additional configuration, not 100% sure) a VNC session you should be able to connect to. That VNC session will give you a GUI to stop/start/restart VMs. In my case:
[root@xen02 ~]# ps auxwwwf |grep xen02 |grep vnc
root 11319 0.1 0.1 71300 4068 ? S 2012 379:31 Xvnc :X -desktop xen02.domain.com:X (root) -httpd /usr/share/vnc/classes -auth /root/.Xauthority -geometry 1024x768 -depth 16 -rfbwait 30000 -rfbauth /root/.vnc/passwd -rfbport NNNN -pn
So xen02.domain.com is the FQDN of my system running Xen. The :X represents the "Desktop number" in VNC speak. The NNNN would be the port number on which VNC listens to. To connect to the VNC console, I would then open a VNC session to xen02.domain.com:NNNN and I'll see a nice GUI to manage everything.