VMware Aria Suite Lifecycle 8.16

8.18 8.16 8.14 8.12
Português (Brasil) 简体中文 Deutsch Español Français Italiano 日本語 한국어 Nederlands 繁體中文 English

Add a
vCenter
 content endpoint in
VMware Aria Suite Lifecycle

To add a
vCenter
 content endpoint to an environment to capture, test, deploy, or check in a content package, use the Content Management service in
VMware Aria Suite Lifecycle
.
Verify that you have added at least one
vCenter
 endpoint in the
Content Settings
vSphere Template Repository
.
  1. On the
    My Services
     dashboard, click
    Content Management
    .
  2. Under
    Endpoints
    , click
    NEW ENDPOINT
  3. Click
    vCenter
    .
  4. Enter the information for the
    vCenter
     content endpoint.
    1. In the
      Name
       field, enter a unique name for the endpoint.
    2. In the
      Tags
       field, enter tags associated with the endpoint.
      Using tags allow you to deploy a content to multiple endpoints at the same time. When you deploy a content, you can select a tag instead of individual content endpoint names, and the content deploys to all endpoints that have that tag.
  5. In the
    Server FQDN/IP
     text box, enter the fully qualified server name, IP address, or host name for the content endpoint server.
  6. To access the endpoint, enter the
    User name
     and
    Password
     values.
  7. Click
    Test Connection
     and then click
    Next
    .
  8. Select the appropriate policies for the content endpoint.
    For more information about policies, see Working with content endpoints in VMware Aria Suite Lifecycle.
  9. Click
    Next
     and provide the
    vCenter
     details.
  10. Click
    Next
    .
  11. To import an existing data center, click
    Import LCM Data center
    .
    After data collection is complete, you can add
    vCenter
     settings to
    VMware Aria Suite Lifecycle
    . The virtual machine folder path (
    /Templates/MyTemplates/
    ) is not imported.
    When the endpoint is created, it validates that the configuration of the local subscriber details point to the publisher as defined in
    Content Settings/vSphere Template Repository
     setting. If there is a problem, the endpoint is deactivated and an error is displayed.

Content feedback and comments