Thanks Chris.
Trying with SSL just results in an error about the packet being invalid/too large -- standard browser error message when you try to connect via SSL on a non-SSL enabled port.
The error I'm seeing is a standard Tomcat error indicating the webapp isn't there -- like it's been renamed, or wasn't installed.
Going to port 80 which, I believe, is supposed to be the normal management interface once everything is up and running just displays an Apache2 test page. "This page is used to test the proper operation of the Apache HTTP server after it has been installed. If you can read this page it means that the Apache HTTP server installed at this site is working properly." and then some thanks for installing/using apache2/centos stuff. This may be normal behavior.
The steps I've taken so far are really dead simple.
1. Install the OVA
2. During install, specify static IP options for the management server.
3. Power on the vApp (which powers up the management VM)
4. Navigate to the plugin registration page
I logged in on the console and checked the log in --------------- and it says, in part:
registering serengeti server as vc ext service
DEBUG VcExtension:92 - Registering extension vService at: https://my.vcenter.server/vsm/extensionService ExtensionKey: com.vmware.serengeti.b238f66a
INFO VcExtension:135 - Response Header: null :HTTP/1.1 200 OK
...
DEBUG VcExtension:148 - Successfully registered
etc. After that it properly shows the datastore, vApp name, cluster name, etc -- so it looks like it's working properly.
The error log says that the vhost and user already exist for 'chef' and that apache was unable to determine the server name. I'm going to add a static DNS entry for the server and see if that helps, though I don't remember anything in the documentation saying that the management server needed to have a host record in DNS.