Document how to use Admiral to manage the VCH lifecycle

[vmware]

Document how to use Admiral to manage the VCH lifecycle

[stuclem]

See https://github.com/vmware/admiral/wiki/User-Guide for inspiration (old doc).

[stuclem]

Here are some notes from my experimentations with the Management Portal and from conversation with @martin-borisov:

• The option to create VCHs will not be exposed in the Management Portal in 1.1

• Authentication options are currently certificate-based or none. Username/password is not an option. Was wondering whether the --ops-user creds could be used, but Martin says no (at least not at this time - he was unaware of the ops user options).

• When adding a VCH to the Management Portal, the authentication you use depends on how you deployed the VCH.

  • Deployed with --no-tls: Specify http://vch_ip:2375 (i.e. not https and not port 2376). Management portal does not request any authentication.
  • Deployed with --tls-cname but specifying --no-tlsverify: Create a new Public Key credential in Management Portal and paste in the contents of the server-key file that was generated when the VCH was created.
  • Deployed with --tls-cname without specifying --no-tlsverify: Create a new Certificate credential in Management Portal and paste in the contents of the server-cert and server-key files that were generated when the VCH was created.
  • Deployed with custom certs: Create a new Certificate credential in Management Portal and paste in the contents of the custom certs.

[stuclem]

Added skeleton topic here: https://github.com/vmware/vic-product/blob/master/docs/user_doc/vic_dev_ops/add_vchs_in_portal.md