In my recent endeavors upgrading to OVM 3 I am questioning the decision to make everything dependent on the VM Manager - and the fact that it's not recommended or easily virtualized (at least on Oracle VM itself) has made things a PITA. I can somewhat see the reasoning behind having it on a separate physical server, but the VM manager becomes the downfall of the whole thing if there's a disaster. If you can't start or stop VM's except from the manager, you are totally helpless until you get a manager up and running again (in the case it goes down), at least with OVM 2 you could do things from the CLI on the server itself. If this is how Oracle wants to do things they could at least create a real client software like Vsphere that could be installed on any machine in a quick scenario.
HA can somewhat alleviate this problem but for those of us running in non-SAN/shared storage environments this is not ideal. The same fundamental benefits of virtualizing should be able to apply to the VM Manager as well.
So, how does everyone else have their VM Manager setup? Has anyone found a good work around or successfully virtualized?
Hope this helps, Russell
Thanks for the links but it appears VM utilities is still reliant on the VM Manager host:
"These utilities make a connection to the Oracle VM Manager host server, using the server host name and an administrative user name and password. After authentication, commands can be submitted to Oracle VM Manager from the command line."
And the new CLI is run by the manager itself, so again if your manager is down you have no way of performing actions on the server. If my physical server running the VM Manger suffers hardware failure, my only and quickest option is to setup new VM manager and restore the MySQL or database backup. Good luck if your Manager repository is on a virtualized Oracle database under the VM server! You won't be able to start it if your manager is down...
So when you are asking for management at the server Level are you referring to the “xm” command that was referenced in section "A Command-Line Tools" in OVM 2.2 users guide, if so the command is still there in OVM 3 as this is a Xen command and is not specific to Oracle VM.
Usage: xm <subcommand> [args]
Control, list, and manipulate Xen guest instances.
Common 'xm' commands:
console Attach to <Domain>'s console.
vncviewer Attach to <Domain>'s VNC server.
create Create a domain based on <ConfigFile>.
new Adds a domain to Xend domain management
delete Remove a domain from Xend domain management.
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.
reset Reset a domain.
restore Restore a domain from a saved state.
resume Resume a Xend managed domain
save Save a domain state to restore later.
shell Launch an interactive shell.
shutdown Shutdown a domain.
start Start a Xend managed domain
suspend Suspend a Xend managed domain
top Monitor a host and the domains in real time.
unpause Unpause a paused domain.
uptime Print uptime for all/some domains.
usb-add Add the usb device to FV VM.
usb-del Delete the usb device to FV VM.
domstate get the state of a domain
vcpu-set Set the number of active VCPUs for allowed for
<Domain> can either be the Domain Name or Id.
For more help on 'xm' see the xm(1) man page.
For more help on 'xm create' see the xmdomain.cfg(5) man page.
For a complete list of subcommands run 'xm help'.
Ah! That is exactly what I was getting at. Oracle is implying these commands can't be used or don't exist anymore in the new OVM 3 documentation and you must use the manager. Not sure why they are pushing that.
Are those commands still "supported" by oracle for management in OVM3?
As the xm command is part of the core of Xen and Oracle VM 3 is still Xen I would think its use would still be supported.I really cannot see why Oracle would not support the use of core Xen commands in the Oracle VM Server envoriment.
I see lots of recent OracleVM docs on My Oracle Support that still list the xm command so I assume its use is still supported. However,I would recommend that you start a Service Request with Oracle Support and verify support for your own piece of mind.
Oracle VM relies on the Manager user interface (UI) component to start, stop and manage the Oracle VM Guests (VM). Oracle VM of course is built upon the Xen product, so the xm commands are all still available. The idea behind the Oracle VM Manager is to give you a "single pane of glass" to view the status of all servers and VMs at a glance.
However, keep in mind that starting, stopping or migrating a VM from the command line does not update the status of the VM within the Manager since whatever action you took was on the command line and was not initiated by Manager UI. You would need to rediscover the servers in order to update the manager after performing some action on a VM from the command line.
The Oracle VM Manager does not need to be running for the automated restart of VMs in the event of a server crash or the VM itself crashing.
There are many ways to deploy the Oracle VM Manager application:
Running the Oracle VM Manager as a virtual machine can also include the Manager as a VM of the same server pool it is managing; this is documented in the Oracle VM Installation and User Guide. I personally prefer this paradigm since it also makes my Oracle VM manager highly available (remember, the HA features still work even if the Manager is not running). You can even use the Manager to live migrate itself to another server in the pool while you watch using the Manager as it is migrating.
So, there are many ways to deploy the Manager