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.

ServiceOfferingInstance onboard request

Description

This API creates a service offering instance (SOI) for an existing virtual machine (VM). The API supports Single-tier and Multi-tier service offering instances. For additional information, see Onboarding-existing-VMs-checklist.
 The following constraints apply to this API:

  • BMC Cloud Lifecycle Management supports the onboarding of VMware and Amazon Web Services virtual machines.
  • The onboarding of Service Offering Instances can be done with two different input formats:
    • Format1—Requires manual steps to enroll the servers in BMC Server Automation.
    • Format 2—Servers are enrolled automatically in BMC Server Automation.
  • There will be no validations on whether the LogicalHostingEnvironment passed to the API is topologically correct to have connectivity between the computes as defined in the blueprint.
  • You can onboard only VMs that do not have load balancers or firewalls, that is, you cannot onboard any existing load balancer entries and firewall rules. However, after the VM is onboarded, you can create firewall rules and load balancer entries for the VM.
  • You cannot apply options when you onboard a VM. However, after the VM is onboarded, you can use options associated with the SOI.
  • This API does not support onboarding VMs that have NAT IP addresses.
  • You cannot enable VM monitoring with blueprint configuration when you onboard a VM. However, after the VM is onboarded, you can enable monitoring through a post-deployment option.
  • Onboard does not support reused blueprints or blueprints without aaplications.
  • When using Format 1 for onboarding Service Offering Instances (manual enrollment), the VM must be configured correctly in BMC Server Automation. For information about enrolling VMs in BMC Server Automation, see Knowledge Base article KA383365 (Support login required).
  • The VM must be powered on.
  • The VM should have the same name in both BMC Server Automation and VMware vCenter Server. If BMC Server Automation and VMware vCenter Server each use a different name for the VM, then set "name" parameter in serverObject to the name used in VMware vCenter Server. Console actions such as start, stop, decommission, modify CPU or memory, and attach or detach storage work only for onboarded service offering instances that have the same name in BMC Server Automation and VMware vCenter Server. Only the offboard service offering instance action can be done through the REST API.
  • If a static IP address is already marked as reserved in BMC Network Automation IP address management (IPAM), the VM onboard process fails to reserve the static IP address. Failure to reserve a static IP address triggers a rollback of the onboarding process that frees the allocated IP address. This case occurs only when two VMs in the network have the same static IP address.
  • Enforced validations to this API:
    • The number of networks defined in the resource set in the service blueprint must be equal to the number of interfaces of the VM
    • Resource set names in the API request should match to the resource set names in blueprint
    • The number of Resource Sets defined in the blueprint must be equal to the number of Resource Sets passed in input for the API.
    • VM should be deployed on an CLM onboarded VirtualCluster/VirtualHost/VirtualResourcePool.
    • The associated VirtualCluster/VirtualHost/VirtualResourcePool of the VM, should be member of a compute pool which is attached to the Network Container passed as input argument.
    • The associated datastores of the VM, should be member of a VDR pool.
    • Switch ports attached to the VM should match to the switch ports of the Network Container (or POD) passed as input argument.

API stability classification

Uncommitted

API overview

HTTP request message

Query string parameters

This API does not use query string parameters.

Request message headers

This API uses only common headers listed in HTTP-request-and-response-headers.

Request message body

This API uses the following objects in the request message body JSON.

Top-level objects

Input parameters to include in operationParams

HTTP response message

Response message headers

This API uses only common headers listed in HTTP-request-and-response-headers.

Response message body

The response message body contains a Task object.

Unknown macro: confluence_report-block. Click on this message for details.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*