Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Entering compute resource provider registration information

This procedure continues the process described in Registering resource providers.

BMC Server Automation is the default compute resource provider for BMC Cloud Lifecycle Management. This procedure describes how to register an instance of BMC Server Automation.

To register BMC Server Automation as a compute resource provider

  1. Access the Register Provider dialog box.
  2. Select Compute (Default) as the resource provider type to register.
  3. Type a name for this instance of the provider.
  4. Type a useful description.
    Descriptions can help you distinguish provider instances from each other and can help you find a provider by using Search.
  5. Type tag names in the space provided.
    Tags are keywords that can help you find this provider quickly.
  6. Enter the following information:
    • Name — Lists the name of the provider.
    • Description — Lists the user-created description of the provider.
    • Host — Enter the name of the BMC Server Automation host computer.
    • Port — Enter the web services communication port number for the BMC Server Automation instance.
    • Protocol — Enter the web services protocol needed to connect to the BMC Server Automation instance, such as https.
    • Username — Enter the BMC Server Automation user name.
    • Password — Enter the password for the user name provided.
    • Role — Enter the BMC Server Automation role.
    • Cache Refresh Time — Enter the cache refresh interval in milliseconds. This provider uses a local disk-based cache to store non-onboarded virtual cluster information so that the search for non-onboarded resources can be provided based on the data in the cache. This refresh interval determines the latency of the list of available of resources to be onboarded compared to what is present in the Virtual Center. Default value: 1800000 milliseconds.
    • Job Start Poll Interval — Used with Job Start Polls, enter the interval, in seconds, between any two outgoing Job Start BMC Server Automation API calls. Default value: 60 seconds.
    • Job Start Polls — Enter the total number of polls before the system times out on a job that is started. Default value: 60.
    • Register Servers by Hostname — Enter true to register newly provisioned virtual machines or physical servers by host name. Enter false to register them by IP Address. This is useful in a network environment with potential DNS resolution issues.
    • Software Job Status Poll Interval — Used with Software Job Status Polls. Enter the interval, in seconds, between any two outgoing BMC Server Automation software job status API calls. Default value: 60 seconds.
    • Software Job Status Polls — Enter the number of status polls before a time out occurs. This is the number of outgoing BMC Server Automation software job status poll API calls from BMC Cloud Lifecycle Management for software job status before the software resource constructor operation times out, which might lead to a software deployment failure. The default is 10.
    • VG Agent Status Poll Interval — Used with VG Agent Status Polls. Enter the interval between any two outgoing BMC Server Automation virtual guest agent status API calls. Default value: 60 seconds.
    • VG Agent Status Polls — Enter the number of status polls before a time out occurs. This is the number of outgoing BMC Server Automation virtual guest status poll API calls from BMC Cloud Lifecycle Management for agent status before the Virtual Guest constructor operation times out, which might lead to a service provisioning timeout. The default is 60.
    • VG Job Status Poll Interval: Used with VG Job Status Poll.  Enter the interval between any two outgoing BMC Server Automation virtual guest job status API calls. Default value: 60 seconds.
    • VG Job Status Polls — Enter the number of status polls before a time out occurs. This is the number of outgoing BMC Server Automation virtual guest job API calls from BMC Cloud Lifecycle Management for job status before the virtual guest constructor operation times out, which might lead to a service provisioning timeout. The default is 60.
    • Enable Job Deletion — Set to true to enable BMC Server Automation job deletion from BMC Cloud Lifecycle Management. The default is false. For more information about job deletion and the job retention policy, see Marking data for deletion.

      Note

      After upgrading, do not enable job deletion until you have read Preparing for BMC Server Automation job deletion from BMC Cloud Lifecycle Management; otherwise, performance issues could occur in BMC Server Automation.

    • Job Deletion Initial Delay (Mins) — Enter the delay (in minutes) after container startup before BMC Cloud Lifecycle Management submits job deletion requests to BMC Server Automation. The default is 5 minutes. This field is active only when Enable Job Deletion is set to true.
    • Job Deletion Delay (Hours) — Enter the delay (in hours) between BMC Cloud Lifecycle Management requests to delete jobs in BMC Server Automation. The default is 24 hours. This field is active only when Enable Job Deletion is set to true.
    • Job Retention (Days) — Enter the number of days that BMC Server Automation jobs created by BMC Cloud Lifecycle Management are retained before being deleted. The default is 7 days. This field is active only when Enable Job Deletion is set to true.
  7. Click Submit.

After you register a resource provider, you can then onboard resources from that provider as described in Editing and removing resources.

Related topics

Onboarding and offboarding network pods

Was this page helpful? Yes No Submitting... Thank you

Comments