vania-janet/multiturn-rag-retrieval-data huggingface dataset:
flow-log-collector is.flow-log-collector.flow-log-collector.read Flow log collector was read 
 flow-log-collector is.flow-log-collector.flow-log-collector.update Flow log collector was updated 







 Load balancer events 

The following table lists the actions that are related to load balancers and the generation of events.



Table 5. Actions that generate events for load balancers

 Resource Action Description 

 Load balancer is.load-balancer.load-balancer.create Load balancer was created 
 Load balancer is.load-balancer.load-balancer.update Load balancer was updated 
 Load balancer is.load-balancer.load-balancer.delete Load balancer was deleted 
 Load balancer is.load-balancer.load-balancer.read Load balancer was read 
 Listener is.load-balancer.load-balancer-listener.create Listener was created 
 Listener is.load-balancer.load-balancer-listener.update Listener was updated 
 Listener is.load-balancer.load-balancer-listener.delete Listener was deleted 
 Listener is.load-balancer.load-balancer-listener.read Listener was read 
 Pool is.load-balancer.load-balancer-pool.create Pool was created 
 Pool is.load-balancer.load-balancer-pool.update Pool was updated 
 Pool is.load-balancer.load-balancer-pool.delete Pool was deleted 
 Pool is.load-balancer.load-balancer-pool.read Pool was read 
 Member is.load-balancer.load-balancer-pool-member.create Member was created 
 Member is.load-balancer.load-balancer-pool-member.update Member was updated 
 Member is.load-balancer.load-balancer-pool-member.delete Member was deleted 
 Member is.load-balancer.load-balancer-pool-member.read Member was read 
 Policy is.load-balancer.load-balancer-listener-policy.create Policy was created 
 Policy is.load-balancer.load-balancer-listener-policy.update Policy was updated
"softlayer",
"net"
],
"path":
"{{bucket}}"
]
},
"description": "Create new bucket"
},
"response": ]
},
{
"name": "Create new bucket (different storage class)",
"event":
{
"listen": "test",
"script": {
"id": "5cf3d531-13f1-4cf6-a4fc-2f8d2d8e48af",
"type": "text/javascript",
"exec":
"pm.test("Request was successful", function() {",
" pm.response.to.be.success; ",
"});"
]
}
}
],
"request": {
"auth": {
"type": "bearer",
"bearer":
{
"key": "token",
"value": "{{iamtoken}}",
"type": "string"
}
]
},
"method": "PUT",
"header":
{
"key": "ibm-service-instance-id",
"value": "{{serviceid}}"
},
{
"key": "Content-Type",
"value": "application/x-www-form-urlencoded"
}
],
"body": {
"mode": "raw",
"raw": "<CreateBucketConfiguration>nt<LocationConstraint>{{bucketlocationvault}}</LocationConstraint>n</CreateBucketConfiguration>"
},
"url": {
AU-SYD 130.198.66.144/28 <br>130.198.80.152/29 <br>135.90.73.96/29 <br>135.90.78.192/28 <br>135.90.94.96/27 <br>168.1.115.192/27 <br>168.1.213.32/27 <br>168.1.213.72/29 <br>168.1.41.96/28 
 CA-TOR 158.85.78.224/27 <br>158.85.94.128/29 <br>163.74.67.192/28 <br>163.74.69.184/29 <br>163.74.71.96/27 <br>163.75.65.232/29 <br>163.75.72.192/27 <br>169.55.129.208/28 
 BR-SAO 163.107.66.96/29 <br>163.107.68.128/28 <br>163.107.71.32/27 <br>163.109.67.240/29 <br>163.109.73.128/27 <br>169.57.141.40/29 <br>169.57.186.0/27 <br>169.57.195.0/28
* [Removing the Azure Disk storage configuration from the cli](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azuredisk-csi-driverazure-disk-template-rm-cli)



* [Parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azuredisk-csi-driverazuredisk-csi-driver-parameter-reference)



* [1.4.0 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azuredisk-csi-driverazuredisk-csi-driver-1.4.0-parameters)
* [1.18.0 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azuredisk-csi-driverazuredisk-csi-driver-1.18.0-parameters)
* [1.23.0 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azuredisk-csi-driverazuredisk-csi-driver-1.23.0-parameters)



* [Storage class reference for Azure Disk](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azuredisk-csi-driverazure-disk-sc-ref)
* [Getting help and support for Azure Disk storage](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azuredisk-csi-driversat-azure-disk-support)



[Azure File CSI Driver](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azurefile-csi-driverstorage-azurefile-csi-driver)



* [Prerequisites for using Azure File](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azurefile-csi-driversat-storage-azure-file-csi-prereq)
Routing all cloud traffic originating at the spokes through the transit VPC firewall-router in the same zone as the originating instance is accomplished by these routes in the spoke's default egress routing table (shown for Dallas/us-south):



 Zone Destination Next hop 

 Dallas 1 10.0.0.0/8 10.1.0.196 
 Dallas 2 10.0.0.0/8 10.2.0.196 
 Dallas 3 10.0.0.0/8 10.3.0.196 



Similarly in the transit VPC route all enterprise and cloud traffic through the firewall-router in the same zone as the originating instance. For example a transit test instance 10.1.0.4 (Dallas 1) attempting contact with 10.2.1.4 (spoke 0, zone 2) will be sent through the firewall-router in zone 1: 10.1.0.196.

Routes in transit's default egress routing table (shown for Dallas/us-south):



 Zone Destination Next hop 

 Dallas 1 10.0.0.0/8 10.1.0.196 
 Dallas 2 10.0.0.0/8 10.2.0.196 
 Dallas 3 10.0.0.0/8 10.3.0.196 
 Dallas 1 192.168.0.0/16 10.1.0.196 
 Dallas 2 192.168.0.0/16 10.2.0.196 
 Dallas 3 192.168.0.0/16 10.3.0.196 







 Do not route Intra VPC traffic to the firewall-router 

In this example Intra-VPC traffic will not pass through the firewall-router. For example resources in spoke 0 can connect to other resources on spoke 0 directly. To accomplish this additional more specific routes can be added to delegate internal traffic. For example in spoke 0, which has the CIDR ranges: 10.1.1.0/24, 10.2.1.0/24, 10.3.1.0/24 the internal routes can be delegated.

Routes in spoke 0's default egress routing table (shown for Dallas/us-south):



 Zone Destination Next hop
* ibmcloud is load-balancer-listener-create 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --port 443 --protocol http --default-pool 70294e14-4e61-11e8-bcf4-0242ac110004
* ibmcloud is load-balancer-listener-create my-lb --port 443 --protocol http --default-pool my-pool
* ibmcloud is load-balancer-listener-create 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --port 443 --protocol http --policies '[{"name": "my-policy", "priority": 5, "action": "reject" }]' The priority of the policy can have a range of 1 to 10, where a lower value indicates a higher priority. The possible values for action are "forward", "redirect", "reject", or "https_redirect".
* ibmcloud is load-balancer-listener-create 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --port 443 --protocol http --policies '[{"priority": 5, "action": "forward", "target": { "id": 70294e14-4e61-11e8-bcf4-0242ac110004 }}]' When the action is forward, the pool identity is required to specify which pool the load balancer forwards the traffic to.
The specified availability zone must reside in the gateway's region. Use the IBM Cloud global catalog to list zones within the desired region. This field is required for and only applicable to gre_tunnel and unbound_gre_tunnel type connections. 
 <br><br> * name <br> string<br><br><br> Availability zone name. <br>Example:us-south-1 





 Example request 

This example illustrates requesting a GRE connection:

curl -X POST "https://transit.cloud.ibm.com/v1/transit_gateways/test/connections?version=2022-01-27" -H "accept: application/json" -H "Content-Type: application/json" -d "{"local_gateway_ip":"192.168.100.1","local_tunnel_ip":"192.168.129.2","name":"Transit_Service_BWTN_SJ_DL","network_type":"unbound_gre_tunnel","base_network_type":"classic","remote_bgp_asn":65010,"remote_gateway_ip":"10.242.63.12","remote_tunnel_ip":"192.168.129.1","zone":{"name":"us-south-1"}}"

{
"local_gateway_ip": "192.168.100.1",
"local_tunnel_ip": "192.168.129.2",
"name": "Transit_Service_BWTN_SJ_DL",
"network_type": "unbound_gre_tunnel",
"base_network_type": "classic",
"remote_bgp_asn": 65010,
"remote_gateway_ip": "10.242.63.12",
"remote_tunnel_ip": "192.168.129.1",
"zone": {
"name": "us-south-1"
}
}







 Response
: Annotation to specify a VLAN that the load balancer service deploys to. To see VLANs, run ibmcloud ks vlan ls --zone <zone>.

service.kubernetes.io/ibm-load-balancer-cloud-provider-enable-features: "ipvs"
: Annotation to specify a version 2.0 load balancer.

service.kubernetes.io/ibm-load-balancer-cloud-provider-ipvs-scheduler:
: Optional: Annotation to specify the scheduling algorithm. Accepted values are "rr" for round-robin (default) or "sh" for Source Hashing. For more information, see [2.0: Scheduling algorithms](https://cloud.ibm.com/docs/containers?topic=containers-loadbalancer-v2scheduling).

selector
: The label key (<selector_key>) and value (<selector_value>) that you used in the spec.template.metadata.labels section of your app deployment YAML.

port
: The port that the service listens on.

loadBalancerIP
: Optional: To create a private NLB or to use a specific portable IP address for a public NLB, specify the IP address that you want to use. The IP address must be in the zone and VLAN that you specify in the annotations. If you don't specify an IP address: If your cluster is on a public VLAN, a portable public IP address is used. Most clusters are on a public VLAN. If your cluster is on a private VLAN only, a portable private IP address is used.

externalTrafficPolicy: Local
: Set to Local.

Example configuration file to create an NLB 2.0 service in dal12 that uses the round-robin scheduling algorithm:

apiVersion: v1
kind: Service
metadata:
name: myloadbalancer
annotations:
service.kubernetes.io/ibm-load-balancer-cloud-provider-zone: "dal12"
Why is my load balancer in maintenance_pending state? 

Use the information in this topic to troubleshoot your load balancer if it is in a maintenance_pending state.

  What’s happening 

Your load balancer displays it is in a maintenance_pending state.

  Why it’s happening 

An NLB enters a maintenance_pending state during various maintenance activities, such as:



*  Recovery activities
*  Load balancer failover
*  Upgrades to address vulnerabilities and appllication of security patches



  How to fix it 

The maintenance_pending state will resolve once the associated maintenance activity completes.
* [Migrating a Local Load Balancer to an IBM Cloud Load Balancer](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-migrating-llb-to-cloud)
* [Local Load Balancer migration FAQs](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-migration-faq)





* Reference



* [IBM Cloud Load Balancer API reference](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-api-reference)
* [Terraform reference](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/lb_service)



* Help



* [Known issues and limitations with IBM Cloud Load Balancer](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-known-issues-and-limitations-with-ibm-cloud-load-balancer)
* [FAQs for IBM Cloud Load Balancer](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-faqs-for-ibm-cloud-load-balancer)
* Troubleshooting



* [Why is my back-end server's health failing?](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-the-back-end-server-is-unhealthy)
* [Common issues when creating a new load balancer](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-load-balancer-provisioning-troubleshooting)
* [Error message troubleshooting](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-error-message-troubleshooting)
"href": "https://eu-gb.iaas.cloud.ibm.com/v1/load_balancers/r018-808fedde-2650-46cc-9cd1-4b828b92970a",
"id": "r018-808fedde-2650-46cc-9cd1-4b828b92970a",
"is_public": true,
"listeners": [
{
"href": "https://eu-gb.iaas.cloud.ibm.com/v1/load_balancers/r018-808fedde-2650-46cc-9cd1-4b828b92970a/listeners/r018-3811d7ad-3bbe-4cb4-82de-8608f767866a",
"id": "r018-3811d7ad-3bbe-4cb4-82de-8608f767866a"
}
],
"name": "test-alb",
"operating_status": "online",
"pools": [
{
"href": "https://eu-gb.iaas.cloud.ibm.com/v1/load_balancers/r018-808fedde-2650-46cc-9cd1-4b828b92970a/pools/r018-df11657f-63cf-49b5-af0f-6eeab32b3559",
"id": "r018-df11657f-63cf-49b5-af0f-6eeab32b3559",
"name": "pool1"
},
{
isPublic,i'datacenter']'longName'],i'operatingStatus']])

print (table)
Show more





 Retrieve details of a specific load balancer 

import SoftLayer
from pprint import pprint

 Your load balancer UUID
uuid = 'set me'
 mask to retrieve the load balancer's listeners and healthMonitors
_mask = "mask[listeners, healthMonitors]"

 Create the api client
client = SoftLayer.Client()
lbaas_service = client['Network_LBaaS_LoadBalancer']

try:
 Retrieve a specific load balancer object
details = lbaas_service.getLoadBalancer(uuid, mask=_mask)
pprint(details)
except SoftLayer.SoftLayerAPIError as e:
print("Unable to retrieve LBaaS details: %s, %s" % (e.faultCode, e.faultString))
Show more







 Updating a load balancer 



 Add a member 

import SoftLayer
from pprint import pprint

 Your load balancer UUID
uuid = 'set me'

 Update with the correct IP addresses
serverInstances = [
{ "privateIpAddress": "10.131.11.46", "weight": 80 },
{ "privateIpAddress": "10.131.11.6" } Default weight=50
]

 Create the api client
client = SoftLayer.Client()
member_service = client['Network_LBaaS_Member']

_mask = "mask[members]"

try:
response = member_service.addLoadBalancerMembers(uuid, serverInstances, mask=_mask)
pprint(response)
except SoftLayer.SoftLayerAPIError as e:
print("Unable to add members: %s, %s" % (e.faultCode, e.faultString))
Show more





 Add a protocol 

import SoftLayer
* HCX™ - VMware HCX application migration enables the scheduling and migration of thousands of VMs. For more information, see [VMware HCX Migration Types](https://docs.vmware.com/en/VMware-HCX/4.3/hcx-user-guide/GUID-8A31731C-AA28-4714-9C23-D9E924DBB666.html).
* Advanced vCenter vMotion - From vSphere 7.0 Update 1c (Patch 02), vCenter supports the import of VMs from another vCenter Server that is not part of the same SSO Domain. The source vCenter Server must be version 6.5 or later. For more information, see [Introducing the Advanced Cross vCenter Server vMotion Capability](https://core.vmware.com/resource/introducing-advanced-cross-vcenter-server-vmotion-capability).
* Zerto or Veeam® - You might have Zerto or Veeam installed on your NAX-V environment and be competent in their usage. These products can be used to replicate VMs from the source data store to the target data store and then initiate a fail-over. And also to replicate a backup from the source cluster to a recovery on the target cluster.







 Network L2 extension 

From a network perspective, the requirement for Layer 3 and Layer 2 connectivity during the migration must be understood. L2 extension allows bridging the NSX-T logical switches to NSX-T segments. You can move the workloads between the NSX-V and NSX-T environments, while you keep the default gateway either on the NSX-V or move it to the new NSX-T. This action allows a smoother network migration. However, it is not mandatory if your environment can tolerate downtime.

Consider the following details for Layer 3 network migration:



* VM by VM migration – This approach moves a VM at a time and /32 route for that host is injected into the NSX-T environment.
CloudFoundryService:
serviceName: gateway
ContainerizationOptions:
- Maven
- transformerName: Maven
name: gateway
type: Service
paths:
ServiceDirectories:
- gateway
ServiceRootDirectory:
- gateway
pomFiles:
- gateway/pom.xml
configs:
Maven:
mavenAppName: gateway
packagingType: jar
mavenProfiles:
- local
- dev
- prod
isMvnwPresent: true
childModules:
- name: gateway
pomPath: pom.xml
inventory:
- transformerName: CloudFoundry
paths:
BuildArtifact:
- inventory/target/inventory-0.0.1-SNAPSHOT.jar
CfManifest:
- inventory/manifest.yml
ServiceDirectories:
- inventory
configs:
CloudFoundryService:
serviceName: inventory
ContainerizationOptions:
- Maven
- transformerName: Maven
name: inventory
type: Service
paths:
ServiceDirectories:
- inventory
ServiceRootDirectory:
- inventory
pomFiles:
- inventory/pom.xml
configs:
Maven:
mavenAppName: inventory
packagingType: jar
mavenProfiles:
- local
- dev-inmemorydb
- prod-externaldb
isMvnwPresent: true
childModules:
- name: inventory
pomPath: pom.xml
orders:
- transformerName: CloudFoundry
paths:
BuildArtifact:
- orders/target/orders-2.0.0-SNAPSHOT.jar
CfManifest:
- orders/manifest.yml
ServiceDirectories:
- orders
configs:
While an IBM Cloud Load Balancer can sit in between CIS and the web server, in this case, it is deployed as an internal load balancer between the web and the app tier.

Zoom

![Three tier web app with CIS and Load Balancer.](https://cloud.ibm.com/docs-content/v1/content/df269b100c3499f1efcbb7d030dce8dec25c539b/ha-infrastructure/images/HA-tier-web-app.svg)

Figure 6. 3 tier web app with CIS and Load Balancer.









 Additional resources 



* [Architecting highly available cloud solutions](https://www.ibm.com/garage/method/practices/run/cloud-platform-for-ha)
* [Enhanced Reliability and Security for IBM Cloud Load Balancer](https://www.ibm.com/cloud/blog/announcements/enhanced-reliability-and-security-for-ibm-cloud-load-balancer)
* [Why Deploy Applications on IBM Cloud Availability Zones?](https://www.ibm.com/cloud/blog/why-deploy-applications-on-ibm-cloud-availability-zones)
* [Load Balancing](https://www.ibm.com/cloud/learn/load-balancing)



Demo change
* ibmcloud is load-balancer-listener-update 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 --certificate-instance-crn crn:v1:bluemix:public:secrets-manager:us-south:a/aa5a471f75bc456fac416bf02c4ba6de:aace9348-39da-4498-b132-e5ab918237f4:secret:e3bd96ce-1e4c-f642-d1f2-0d0ab025f510
* ibmcloud is load-balancer-listener-update my-lb 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 --certificate-instance-crn crn:v1:bluemix:public:secrets-manager:us-south:a/aa5a471f75bc456fac416bf02c4ba6de:aace9348-39da-4498-b132-e5ab918237f4:secret:e3bd96ce-1e4c-f642-d1f2-0d0ab025f510
* ibmcloud is load-balancer-listener-update 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 --connection-limit 2000
The following list is not exhaustive, but suggests some of the items to validate:



* Application
* Licensing
* Reachability (host-level configuration changes)
* Remove RMM SSH key after migration successful







 More resources 



1. [Discovery Tool](https://github.com/IBM-Cloud/vpc-migration-tools/blob/main/v2v-discovery-tool-rmm/VMware/README.md)
2. [FAQs](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-faqs-vmware)
3. [RackWare usage guide](https://www.rackwareinc.com/cloud-migration)
[High-level Satellite reference architecture for IBM Cloud for Financial Services](https://cloud.ibm.com/docs-content/v1/content/9ac5c38b41e0aa1cb4ccc6cc7f547751ec805221/framework-financial-services/satellite/images/satellite-crawl/Satellite_FS_Cloud_draft_04-06_with_Labels_beta2.svg)

Figure 1. High-level Satellite reference architecture for IBM Cloud for Financial Services

The following table provides an index to the components in the diagram.



Table 2. Index of components in the Satellite reference architecture diagram
Index of components in the Satellite reference architecture diagram

 IBM Cloud Satellite location on-premises Supporting components on-premises 

 ⁣1. [Satellite link tunnel server](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutcomponents-ibm-cloud) ⁣5. [Storage](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutcomponents-satellite-location-infrastructure-components) ⁣11. [Edge plane](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutcomponents-other-supporting) 
 ⁣2. [Monitoring](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutcomponents-ibm-cloud) ⁣6. [Satellite hosts](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutcomponents-satellite-location-infrastructure-components) ⁣12. [Management plane](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutcomponents-other-supporting) 
 ⁣3.
* UI
* CLI
* API







 Listing routes of a routing table 

You can list the routes of a VPC routing table by using the UI, CLI, or API.



 Listing routes of a routing table in the UI 

To list the routes of a VPC routing table in the UI, follow these steps:



1. From the [IBM Cloud console](https://cloud.ibm.com/login), select the Navigation Menu ![Navigation Menu](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc//images/menu_icon.png), then click VPC Infrastructure > Routing tables in the Network section. The Routing tables for VPC page appears.
2. Click the routing table name or number of routes that are associated with the routing table. The Routing table details page appears, listing the routes associated with the routing table.



Descriptions of these columns are as follows:



Table 1. Destination routes details

 Column Description 

 Name Name of the route. 
 Destination Destination CIDR of the route. 
 State The lifecycle state. Custom route states are:<br><br><br><br> * Pending - In the process of being provisioned in the specified VPC and zone.<br> * Stable - Provisioning was successful.<br> * Deleting - A Stable or Failed route is in the process of being deleted.<br> * Deleted - Deletion was successful.<br> * Failed - The route is not functional. From this state, you can delete only the route.<br><br><br> 
 Zone xxx 
 Action Values are:<br><br><br><br> * Deliver - Routes the packet to the next hop target. You can add multiple routes with the same address prefix.
"domain": "softlayer.local",
"hostname": "public-01-mex01"
}
],
"complexType": "SoftLayer_Container_Product_Order_Virtual_Guest"
}
]
}
Show more







 Upgrading public virtual servers 

Upgrading a public virtual server is done by using the SoftLayer_Product_Order/placeOrder API service.

Not applicable for transient virtual servers.

To provision a public virtual server by using REST, a POST request would be submitted to [https://softlayer.github.io/reference/services/SoftLayer_Product_Order/placeOrder/](https://softlayer.github.io/reference/services/SoftLayer_Product_Order/placeOrder/) with the following JSON in the request body.

The item descriptions are not required on the prices. They are included only to show the product options that are being submitted.

The following JSON request body is a generic example.



 JSON Request Body 3 

{
"parameters":[
{
"complexType": "SoftLayer_Container_Product_Order_Virtual_Guest_Upgrade",
"presetId": 494,
"prices":
{
"id":"274",
"item": {
"description": "1 Gbps Public & Private Network Uplinks"
},
"categories":
{
"categoryCode": "port_speed"
}
]
}
],
"properties":
{
"name": "MAINTENANCE_WINDOW",
"value": "2017-07-20T13:48:31-05:00"
}
],
"virtualGuests":
{
"id": 36189167
}
]
}
]
}
Show more







 Provisioning a transient virtual server with Create Object 

The SoftLayer_Virtual_Guest/createObject API service is the simplest way to provision a transient virtual server.