Skip to content

Commit

Permalink
Misc edits and formatting changes (#2498)
Browse files Browse the repository at this point in the history
  • Loading branch information
vidya-v authored Jun 20, 2019
1 parent b8e0536 commit c9f9a55
Show file tree
Hide file tree
Showing 3 changed files with 17 additions and 11 deletions.
16 changes: 9 additions & 7 deletions docs/user_doc/vic_vsphere_admin/access_h5_ui.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,28 +25,30 @@ If you have installed the HTML5 plug-in for vSphere Integrated Containers, you c
- The version of the vSphere Integrated Containers plug-in for the vSphere Client.
- The number of VCHs registered with this vCenter Server instance.
- The version of the vSphere Integrated Containers appliance to which the client plug-in is connected.
- The IP address of the vSphere Integrated Containers appliance. You can click on the IP address to go to the the vSphere Integrated Containers Getting Started page.
- The IP address of the vSphere Integrated Containers appliance. You can click on the IP address to go to the vSphere Integrated Containers Getting Started page.

This information allows you to know which appliance instance is providing the vSphere Integrated Containers API endpoint. This is useful in environments in which you have deployed multiple appliances. The appliance that the client connects to might not be the one that was most recently registered with vCenter Server. Consequently, if you have deployed different versions of the appliance to vCenter Server, it is useful to know which one the client is connecting to.

4. Select the **Virtual Container Hosts** tab.

The **Virtual Container Hosts** tab provides information about the VCHs that are registered with this vCenter Server instance:

- Lists all VCHs by name. You can click the VCH name to go to the Summary tab for the VCH endpoint VM.
- Indicates that the VCH is running correctly.
- Displays the `DOCKER_HOST` environment variable that container developers use to connect to this VCH.
- Provides the link to the VCH Admin Portal for this VCH.

5. (Optional) Click the 3 vertical dots next to a VCH.

- Select **Delete** to remove the VCH.
- Select **Download VCH certificate** to download the server certificate for the VCH. Container developers might require the server certificate when they run Docker commands in `--tlsverify` client mode, if you use certificates that are not signed by a trusted certificate authority.

**NOTE**: You cannot download client certificates for VCHs from the vSphere Client. vSphere administrators distribute client certificates directly.

5. Select the **Containers** tab.

The **Containers** tab shows information about all of the container VMs that are running in this vCenter Server instance, for all VCHs:

- Lists all containers by name.
- Indicates whether the container VM is powered on or off.
- Provides information about the memory, CPU, and storage consumption of the container VM.
Expand Down
9 changes: 6 additions & 3 deletions docs/user_doc/vic_vsphere_admin/deploy_vic_appliance.md
Original file line number Diff line number Diff line change
Expand Up @@ -101,6 +101,7 @@ You can also deploy the vSphere Integrated Containers Appliance using the `ovfto
- In the **Password for Example Users** text boxes, modify the password for the example user account from the default, `VicPro!23`. The new password must comply with the password policy for the Platform Services Controller, otherwise the creation of the example user accounts fails. If you unchecked the **Create Example Users** checkbox, this option is ignored.

**IMPORTANT**: If you did not uncheck the **Create Example Users** checkbox, it is strongly recommended that you change the default password for the example users.

8. Expand the **Syslog Configuration** to optionally configure the Syslog server to forward the appliance logs.

- In the **Remote Syslog Server** text box, specify the IP address or host name of the Syslog server that you want to forward the appliance logs to. Leave this property blank if you do not want to forward the logs.
Expand All @@ -116,10 +117,10 @@ You can also deploy the vSphere Integrated Containers Appliance using the `ovfto
If you deployed the appliance so that it obtains its address via DHCP, go to the **Summary** tab for the appliance VM and note the address.

1. (Optional) If you provided a static network configuration, view the network status of the appliance.

1. In the **Summary** tab for the appliance VM, launch the VM console
2. In the VM console, press the right arrow key.

The network status shows whether the network settings that you provided during the deployment match the settings with which the appliance is running. If there are mismatches, power off the appliance and select **Edit Settings** > **vApp Options** to correct the network settings.

1. In a browser, go to the vSphere Integrated Containers appliance welcome page.
Expand All @@ -142,9 +143,11 @@ You can also deploy the vSphere Integrated Containers Appliance using the `ovfto
**IMPORTANT**: The installation process requires administrator credentials to register vSphere Integrated Containers Management Portal and Registry with the Platform Services Controller and to tag the appliance VM for use in Docker content trust. Administrator credentials are not stored on the appliance VM after use in the installation process. The vSphere Integrated Containers Management Portal and Registry services cannot start if you do not complete this step.

1. Enter the root password for the vSphere Integrated Containers appliance, that you set when you deployed the OVA.

1. To automatically install the vSphere Integrated Containers plug-in for vSphere Client, leave the **Install UI Plugin** check box selected, and click **Continue**.

**NOTE**: By default, in an environment in which multiple vSphere Integrated Containers are deployed to the same vCenter Server instance, the vSphere Integrated Containers plug-in connects to one appliance only. This appliance instance might not be the one that registered most recently with vCenter Server. Consequently, if there are older instances of the appliance registered with vCenter Server and you do not want the plug-in to automatically upgrade to the latest version, deselect the **Install UI Plugin** check box. You can see version information about the plug-in and the appliance in the Summary tab of the vSphere Integrated Containers plug-in. If you deselect the **Install UI Plugin** check box, you can install or upgrade the plug-in later.

**NOTE**: By default, in an environment in which multiple vSphere Integrated Containers are deployed to the same vCenter Server instance, the vSphere Integrated Containers plug-in connects to one appliance only. This appliance instance might not be the one that registered most recently with vCenter Server. Consequently, if there are older instances of the appliance registered with vCenter Server and you do not want the plug-in to automatically upgrade to the latest version, deselect the **Install UI Plugin** check box. You can see version information about the plug-in and the appliance in the Summary tab of the vSphere Integrated Containers plug-in. If you deselect the **Install UI Plugin** check box, you can install or upgrade the plug-in later.
1. Verify that the certificate thumbprint for vCenter Server is valid, and click **Continue** to complete the installation of the appliance.

## Result
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -276,8 +276,9 @@ Add transfer header data to the log. Use this option with care. The default valu

The following command sets the appliance root password and uses the default values for other options:

ovftool --datastore=vsanDatastore --noSSLVerify --acceptAllEulas --name=<vch_name> --diskMode=thin --powerOn --X:waitForIp --X:injectOvfEnv --X:enableHiddenProperties --prop:appliance.root_pwd=<root_pwd>' --prop:appliance.permit_root_login=True --net:"Network"="vm-network" installer/bin/vic-*.ova 'vi://<vc_username>:<vc_pwd>@10.160.222.221/vcqaDC/host/cls' 2>&1
ovftool --datastore=vsanDatastore --noSSLVerify --acceptAllEulas --name=<ova_name> --diskMode=thin --powerOn --X:waitForIp --X:injectOvfEnv --X:enableHiddenProperties --prop:appliance.root_pwd=<root_pwd>' --prop:appliance.permit_root_login=True --net:"Network"="vm-network" installer/bin/vic-*.ova 'vi://<vc_username>:<vc_pwd>@10.160.222.221/vcqaDC/host/cls' 2>&1

For password requirements, see [Deploy the vSphere Integrated Containers Appliance](deploy_vic_appliance.md).

For more information about the VMware OVF Tool and how to use it, see the [OVF Tool Documentation](https://www.vmware.com/support/developer/ovf/).

Expand Down

0 comments on commit c9f9a55

Please sign in to comment.