Inbound Hosts
Inbound Hosts
#340340
Description
Full Control Hosting Venues
This API supports only full control hosting venues (i.e. infrastructure groups), as hosts are not managed in other hosting venues.
Available Capacity
The available capacity is immediately increased when an Inbound Host is created, for all timeframes after the planned start date. An environment refresh is not required. This increased capacity allows for new planned workloads coming in after the inbound host is scheduled for provisioning.
Similarly, the available capacity is immediately decreased if the Inbound Host is deleted. An environment refresh is not required.
Resource
/inbound-hosts
Supported Operations
Table: Inbound Host Supported Operations
Operation |
HTTP Method |
Input |
Output |
Description |
Get Collection |
GET /inbound-hosts |
None |
Inbound Host collection of [id, name, href] |
|
Get Individual |
GET /inbound-hosts/<id> |
None |
Retrieve the Inbound Host elements of the specified id. |
|
Create Individual |
POST /inbound-hosts |
One or more Inbound Hosts can be created. |
||
Create Multiple |
POST /inbound-hosts |
Inbound Hosts: Resource Elements> With "num_copy" : <number> specified |
Similar to the Create Individual operation, but specifying the number of Inbound Hosts to create using "num_copy" : <number> with no limit to the number of instances created at a time. The names of the Inbound Hosts are auto-generated by appending a number after name. For example, if name=Host, then the generated names would be Host1, Host2, etc. |
|
Modify Individual |
PUT /inbound-hosts/<id> |
None |
An Inbound Host that is in PENDING or COMMITTED state can be modified through the PUT command. Only the name can be modified. |
|
Delete Individual |
DELETE /inbound-hosts/<id> |
None |
None |
An Inbound Host in any state can be deleted. |
Delete Multiple |
DELETE /inbound-hosts |
ids: [<id>, <id>,…] |
None |
Similar to deleting a single Inbound Host above, however, this command deletes multiple Inbound Hosts in one call. |
Table: Inbound Host Resource Elements
Element |
Type |
Create/Mod- |
Sort By |
Filter |
Description |
id, name, href |
strings |
CM-R for name |
S by name |
F by name |
See ID, Name and Self Reference (id, name, href). The expected system name of the incoming host, required for auto-reconciliation. For details, see section Auto-Reconciliation of Systems of Booking Overview (Help Topic ID 230350). |
attributes |
[id, name, value] |
C |
|
F only as that defined in cfg\bookings\bookings-config.xml |
On a create request, defines any other attributes of the incoming system. If the attribute name or value is incorrectly specified, an error is returned and the Inbound Host object is not created. For a create, only the name-value pairs are required. The id is not required. For a single-valued attribute, if the name-value pair is defined more than once, then only the first occurrence is used and the second one is ignored. For a multi-valued attribute, the name-value pair can be specified multiple times as required for the same named attribute. Duplicates when specifying the same value more than once for the same named attribute are ignored. On a GET request, only those attributes that have values are returned. The name corresponds to the actual field label. For example: |
|
|
|
To filter on an attribute, use attribute.id. For example, to filter all Inbound Hosts that belong to Level 1 Security Zone: |
||
control_environment |
id, name, href, icon |
|
|
F using control_environment_id |
This is the link to the associated Control Environment where the host is to be placed. This environment must consist of full control hosting venues. |
cores_per_cpu |
string |
C-R |
|
Cores per CPU on the Plan and Manage Supply > Add Host Supply dialog box. Cores per CPU, from the System Summary DSE page. |
|
cpu_allocation |
string |
C |
|
|
Not displayed on the Plan and Manage Supply > Add Host Supply dialog box. CPU Allocation of the system. |
cpu_benchmarks |
[name, score_type, value] |
C |
|
The CPU benchmark. If not specified, the benchmark is automatically calculated. To recalculate manually, see Helper Utilities.
|
|
cpu_model |
string |
C-R |
|
|
CPU Architecture on the Plan and Manage Supply > Add Host Supply dialog box. CPU Architecture, as from the System Summary DSE page. |
cpu_speed |
string |
C-R |
|
|
CPU Speed on the Plan and Manage Supply > Add Host Supply dialog box. Normalized CPU Speed (MHz), as from the System Summary DSE page. |
creation_time |
number |
|
S |
F |
The date and time this Inbound Host object was created, in UTC. |
description |
string |
C |
|
|
An arbitrary string that describes the new host. |
expected_date |
number |
C |
S |
F |
The expected date this Inbound Host is expected to be running and available for placing VMs, in UTC format. The time portion is ignored and always set to 04:00:00. A default of tomorrow's date is used, meaning the host must be provisioned today. |
infrastructure_group |
id, name, href |
C-R |
|
F using infrastructure_group_id or infrastructure_group |
This is the link to the associated Infrastructure Group where the host is to be placed. Note that when filtering on Infrastructure Groups, you must use the element infrastructure_group_id with a UUID specified or element infrastructure_group with a name specified. |
I/O_benchmarks |
[name, score_type, value] |
C |
|
The list of all available I/O benchmarks.
|
|
manufacturer |
string |
C-R |
Manufacturer on the Plan and Manage Supply > Add Host Supply dialog box. Manufacturer, from the System Summary DSE page. |
||
memory |
number |
C-R |
S |
|
Normalized Total Memory (MB), as from the System Summary DSE page. |
owner |
string |
C |
S |
|
Used to define the owner or Customer Name of this Inbound Host. If not set, this field is set to the user who is creating the Inbound Host. |
owner_email |
string |
C |
|
|
The email address of the owner. |
platform_model |
string |
C-R |
|
Platform/Model on the Plan and Manage Supply > Add Host Supply dialog box. Model, from the System Summary DSE page. |
|
project |
string |
C |
|
|
Used to define the Project. If not set, the Project is defined as "__Unknown__". |
status |
string |
|
S |
F |
The status of the Inbound Host. See State Diagrams for Supply for state details.
|
total_logical_cpus |
string |
|
|
|
Total Logical CPUs, as from the System Summary DSE page. This is defined by the system catalog (if specified) or is calculated from total_physical_cpus x cores_per_cpu x threads_per_core. |
total_physical_cpus |
string |
C-R |
|
|
Physical CPUs on the Plan and Manage Supply > Add Host Supply dialog box. Total Physical CPUs, from the System Summary DSE page. |
threads_per_core |
string |
C-R |
|
|
Threads Per Core on the Plan and Manage Supply > Add Host Supply dialog box. Threads Per Core, as from the System Summary DSE page. |
Examples
Example: Getting a Collection of Inbound Hosts
The following example shows you how to obtain the collection of current Inbound Hosts.

Request:
GET /inbound-hosts
Response:
[
{
"id": "d274c5ed-b53e-4020-9e42-bc072c6d4816",
"name": "ucs-host2",
"href": "/inbound-hosts/d274c5ed-b53e-4020-9e42-bc072c6d4816"
},
{
"id": "ab143af5-f7c1-4b6d-865d-739b71d20a07",
"name": "ucs-host4",
"href": "/inbound-hosts/ab143af5-f7c1-4b6d-865d-739b71d20a07"
},
// ... *SNIP* of Inbound Hosts...
]
Example: Getting an Individual Inbound Host
The following example shows you how to get a single Inbound Host.

Request:
GET /inbound-hosts/d274c5ed-b53e-4020-9e42-bc072c6d4816
Response:
{
"id": "d274c5ed-b53e-4020-9e42-bc072c6d4816",
"name": "ucs-host2",
"href": "/inbound-hosts/d274c5ed-b53e-4020-9e42-bc072c6d4816",
"manufacturer": "Cisco",
"platform_model": "Cisco UCS B230 M2",
"cpu_model": "Intel Xeon E7-2870",
"total_logical_cpus": "40",
"total_physical_cpus": "2",
"cores_per_cpu": "10",
"threads_per_core": "2",
"cpu_allocation": "-1.00",
"cpu_speed": "2400",
"memory": "256000",
"status": "COMMITTED",
"owner": "Bill",
"project": "UCS hardware refresh",
"description": "",
"attributes": [
{
"id": "attr_SecurityZone",
"name": "Security Zone",
"value": "Level 1"
}
],
"expected_date": 1436068800000,
"creation_time": 1432815005590,
"owner_email": "",
"cpu_benchmarks": [
{
"name": "CINT2006 Rate",
"score_type": "cint2006rate",
"value": 549
}
],
"I/O_benchmarks": [
{
"name": "Maximum Network Throughput (bytes/s)",
"score_type": "net",
"value": -1
},
{
"name": "Maximum Disk Throughput (bytes/s)",
"score_type": "disk",
"value": -1
}
],
"infrastructure_group": {
"id": "2baa1ac4-4ffe-4e79-a73d-d038145bca8d",
"name": "Prod2_BDVC-01",
"href": "/infrastructure-groups/2baa1ac4-4ffe-4e79-a73d-d038145bca8d"
},
"control_environment": {
"id": "26092815-9d17-4e6a-abbd-f5b05a853bff",
"name": "Boston",
"href": "/control-environments/26092815-9d17-4e6a-abbd-f5b05a853bff",
"icon": "/control-environments/26092815-9d17-4e6a-abbd-f5b05a853bff/icon"
}
}
Example: Creating Multiple Inbound Hosts
The following example shows you how to create 2 Inbound Hosts.

Request:
POST /inbound-hosts
{
"num_copy":2,
"name": "ucs-host2",
"manufacturer": "HP",
"platform_model": "ProLiant DL380 G7",
"cpu_model": "Intel Xeon X5690",
"total_physical_cpus": "2",
"cores_per_cpu": "6",
"threads_per_core": "2",
"cpu_allocation": "12.00",
"cpu_speed": "3466",
"memory": "131072",
"owner": "Melissa",
"owner_email": "[email protected]",
"project": "UCS hardware refresh",
"attributes": [
{
"name": "Security Zone",
"value": "Level 1"
}
],
"expected_date": 1472659206000,
"cpu_benchmarks": [
{
"name": "CINT2006 Rate",
"score_type": "cint2006rate",
"value": 404.47
}
],
"I/O_benchmarks": [
{
"name": "Maximum Network Throughput (bytes/s)",
"score_type": "net",
"value": 1342177280
},
{
"name": "Maximum Disk Throughput (bytes/s)",
"score_type": "disk",
"value": 1342177280
}
],
"infrastructure_group": {
"id": "2baa1ac4-4ffe-4e79-a73d-d038145bca8d"
}
}
Response:
[
{
"id": "0d69655a-d10b-4d76-88e2-5bc3916c8e07",
"name": "ucs-host21",
"href": "/inbound-hosts/0d69655a-d10b-4d76-88e2-5bc3916c8e07",
"manufacturer": "HP",
"platform_model": "ProLiant DL380 G7",
"cpu_model": "Intel Xeon X5690",
"total_logical_cpus": 24,
"total_physical_cpus": 2,
"cores_per_cpu": 6,
"threads_per_core": 2,
"cpu_allocation": "12.0",
"cpu_speed": 3466,
"memory": 131072,
"status": "PENDING",
"owner": "Melissa",
"project": "UCS hardware refresh",
"description": "",
"expected_date": 1472659206000,
"creation_time": 1470844834427,
"owner_email": "[email protected]",
"attributes": [
{
"id": "attr_SecurityZone",
"name": "Security Zone",
"value": "Level 1"
}
],
"cpu_benchmarks": [
{
"name": "CINT2006 Rate",
"score_type": "cint2006rate",
"value": 404.47
}
],
"I/O_benchmarks": [
{
"name": "Maximum Disk Throughput (bytes/s)",
"score_type": "disk",
"value": 1342177280
},
{
"name": "Maximum Network Throughput (bytes/s)",
"score_type": "net",
"value": 1342177280
}
],
"infrastructure_group": {
"id": "2baa1ac4-4ffe-4e79-a73d-d038145bca8d",
"name": "Prod2_BDVC-01",
"href": "/infrastructure-groups/2baa1ac4-4ffe-4e79-a73d-d038145bca8d"
},
"control_environment": {
"id": "26092815-9d17-4e6a-abbd-f5b05a853bff",
"name": "Boston",
"href": "/control-environments/26092815-9d17-4e6a-abbd-f5b05a853bff",
"icon": "/control-environments/26092815-9d17-4e6a-abbd-f5b05a853bff/icon"
}
},
{
// ... *SNIP* of Inbound Host "ucs-host22 ...
}
]
Example: Modifying an Inbound Host Name
The following example updates an Inbound Host name from "ucs-host21" to "ucs-host1".
Example: Deleting Multiple Inbound Hosts
The following example deletes three Inbound Hosts, as specified, in one call.