vania-janet/multiturn-rag-retrieval-data huggingface dataset:
$ ibmcloud sl order place CLOUD_SERVER DALLAS13 GUEST_CORES_4,RAM_16_GB,REBOOT_REMOTE_CONSOLE,1_GBPS_PUBLIC_PRIVATE_NETWORK_UPLINKS,BANDWIDTH_0_GB_2,1_IP_ADDRESS,GUEST_DISK_100_GB_SAN,OS_UBUNTU_18_04_LTS_BIONIC_BEAVER_LAMP_64_BIT,MONITORING_HOST_PING,NOTIFICATION_EMAIL_AND_TICKET,AUTOMATED_NOTIFICATION,UNLIMITED_SSL_VPN_USERS_1_PPTP_VPN_USER_PER_ACCOUNT,NESSUS_VULNERABILITY_ASSESSMENT_REPORTING,EVAULT_20_GB --billing monthly --extras '{"virtualGuests": [{"hostname": "test", "domain": "softlayer.com"}]}' --complex-type SoftLayer_Container_Product_Order_Virtual_Guest
This action will incur charges on your account. Continue?> y

ID 105021440
Created 2023-04-24T20:04:57Z
Status PENDING_AUTO_APPROVAL

For more information, see [ibmcloud sl order place](https://cloud.ibm.com/docs/cli?topic=cli-sl-manage-classic-orders).





 Provisioning IBM Cloud Backup for Classic with Terraform 

To use Terraform, download the Terraform CLI and configure the IBM Cloud Provider plug-in. For more information, see [Getting started with Terraform](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started).

Use the ibm_storage_evault resource to create or update your IBM Cloud® Backup for Classic instance. The following example creates a 20-GB vault in DAL13 data center. The virtual_instance_id defines the server that is going to be backed up in this vault.

resource "ibm_storage_evault" "test" {
datacenter = "dal13"
capacity = "20"
virtual_instance_id = "137028172"
To specify multiple locations, use one option for each location, such as -l dal -l seo.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.

Example:

ibmcloud ks subnets -l ams03 -l wdc -l ap





 vlan commands 

Classic infrastructure

List public and private VLANs for a zone and view the VLAN spanning status.



 ibmcloud ks vlan ls 

Classic infrastructure

List the public and private VLANs that are available for a zone in your classic IBM Cloud infrastructure account. To list available VLANs, you must have a paid account.

ibmcloud ks vlan ls --zone ZONE [--all] [--output json] [-q]

Minimum required permissions:



* To view the VLANs that the cluster is connected to in a zone: Viewer platform access role for the cluster in IBM Cloud Kubernetes Service
* To list all available VLANs in a zone: Viewer platform access role for the region in IBM Cloud Kubernetes Service



Command options:

--zone ZONE
: Required: Enter the zone where you want to list your private and public VLANs. To see available zones, run ibmcloud ks zone ls.

--all
: Lists all available VLANs. By default VLANs are filtered to show only those VLANs that are valid. To be valid, a VLAN must be associated with infrastructure that can host a worker with local disk storage.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example vlan ls command 

ibmcloud ks vlan ls --zone dal10







 ibmcloud ks vlan spanning get 

Classic infrastructure

View the VLAN spanning status for an IBM Cloud infrastructure account. VLAN spanning enables all devices on an account to communicate with each other through the private network, regardless of its assigned VLAN.
The IBM Cloud Direct Link offerings are useful when you must implement hybrid workloads, cross-provider workloads, large or frequent data transfers, or private workloads. To choose an IBM Cloud Direct Link offering and set up an IBM Cloud Direct Link connection, see [Get Started with IBM Cloud IBM Cloud Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl) in the IBM Cloud Direct Link documentation.
* Virtual Router Appliance (VRA) or Fortigate Security Appliance (FSA): You might choose to set up a [VRA (Vyatta)](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-about-the-vra) or [FSA](https://cloud.ibm.com/docs/vmwaresolutions/services?topic=vmwaresolutions-fsa_considerations) to configure an IPSec VPN endpoint. This option is useful when you have a larger cluster, want to access multiple clusters over a single VPN, or need a route-based VPN. To configure a VRA, see [Setting up VPN connectivity with VRA](https://cloud.ibm.com/docs/containers?topic=containers-vpnvyatta).



If you plan to connect your cluster to on-premises networks, check out the following helpful features.



* You might have subnet conflicts with the IBM-provided default 172.30.0.0/16 range for pods and 172.21.0.0/16 range for services. You can avoid subnet conflicts when you [create a cluster from the CLI](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_create) by specifying a custom subnet CIDR for pods in the --pod-subnet option and a custom subnet CIDR for services in the --service-subnet option.
* UI
* CLI
* API







 Applying a plan 

When you apply a plan, the IBM Cloud® resources are deployed to build a IBM Spectrum Symphony cluster instance on your IBM Cloud account with your specific choice of configuration properties.



 Applying a plan using the UI 



1. After you generate a plan in the IBM Cloud console, click Apply plan. This action generates a new log that can be viewed in the Jobs tab.
2. Review the log file for any errors, fix the errors, and then click Apply plan again.
3. After you successfully apply a plan, you can review all of the resources that are deployed under this workspace by clicking the Resources tab.







 Applying a plan using the CLI 

Run the following command to apply a plan to your workspace:

ibmcloud schematics apply --id <WORKSPACE_ID>

While the resources are being deployed, you can monitor the log files for errors or confirm that the action was completed successfully. This step can take some time based on how many virtual servers are being provisioned as part of your configuration file. Run the following command to monitor your log files:

ibmcloud schematics logs --id <WORKSPACE_ID>

Sample response:

2021/04/05 09:44:54 Terraform apply | Apply complete! Resources: 14 added, 0 changed, 0 destroyed.
2021/04/05 09:44:54 Terraform apply 
2021/04/05 09:44:54 Terraform apply | Outputs:
2021/04/05 09:44:54 Terraform apply 
2021/04/05 09:44:54 Terraform apply | sshcommand = ssh -J root@52.116.124.67  root@10.241.0.6
2021/04/05 09:44:54 Command finished successfully.
2021/04/05 09:45:00 Done with the workspace action

After the plan is successfully applied, it generates an sshcommand in the Outputs section in the Terraform code. You can use this command to log in to the IBM Spectrum Symphony cluster.
Installing Direct Link to an HPC cluster 

IBM® Spectrum LSF multi-cluster capability allows you to share resources between clusters through resource leasing or job forwarding. Multiple LSF clusters can also solve problems that are related to ease of administration, scalability, and sites in different geographic locations. IBM Cloud hybrid cloud HPC solution uses these core functions of Spectrum LSF to create a seamless integration of IBM Spectrum LSF cluster in IBM Cloud and on-premises. Job forwarding configurations can be used as an easy way to transparently schedule the workload execution on the IBM Spectrum LSF cluster on IBM Cloud, while having the full administration and control possible from the IBM Spectrum LSF cluster on-premises.

You can use IBM Cloud Direct Link for your hybrid connection between on-premises and your IBM Cloud® account. For more information on how to get started and order Direct Link, see [Getting started with IBM Cloud Direct Link (2.0)](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl).



  Next steps 

After you configure and validate the connectivity from on-premises to your IBM Cloud account, you are ready to [Set up the multi-cluster and job forwarding using Spectrum LSF](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-set-up-multi-cluster-job-forwarding).
[Account with one resource group for Satellite-related resources](https://cloud.ibm.com/docs-content/v1/content/9ac5c38b41e0aa1cb4ccc6cc7f547751ec805221/framework-financial-services/satellite/images/resource-organization/satellite-accounts-single-with-one-resource-group-beta2.drawio.svg)

Figure 2. Account with one resource group for Satellite-related resources







 Organization for multiple deployments 

It is required that you have [separate test and production deployments](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-non-production-environments) of the reference architecture, and that those deployments are managed by separate accounts. This means you need at least two accounts, each with a dedicated resource group.



 VPC reference architecture 

The following diagram shows a depiction of this organization for the VPC reference architecture.

Zoom

![Multiple accounts for VPC reference architecture with two resource groups](https://cloud.ibm.com/docs-content/v1/content/9ac5c38b41e0aa1cb4ccc6cc7f547751ec805221/framework-financial-services/vpc/images/resource-organization/vpc-accounts-multiple-with-two-resource-groups-beta2.drawio.svg)

Figure 3. Multiple accounts for VPC reference architecture with two resource groups





 Satellite reference architecture 

The following diagram shows a depiction of this organization for the Satellite reference architecture.

Zoom

![Multiple accounts for Satellite reference architecture](https://cloud.ibm.com/docs-content/v1/content/9ac5c38b41e0aa1cb4ccc6cc7f547751ec805221/framework-financial-services/satellite/images/resource-organization/satellite-accounts-multiple-with-one-resource-group-beta2.drawio.svg)

Figure 4. Multiple accounts for Satellite reference architecture
The new IBM Cloud Direct Link offering differs from "Direct Link on Classic" in that the new Direct Link is decoupled from classic IaaS, and exists only in the local cross-connect router (XCR). This design enables native connectivity to VPC and future capabilities without being forced into the classic IaaS network.

The zone-region model allows for multiple data centers to exist in a single zone.

The new Direct Link offering allows connectivity to both Classic IaaS as well as VPCs, whereas the Classic Direct Link always connects to IaaS network and a global VRF first. Classic Direct Link can only reach VPC on a limited basis utilizing a VPC feature called Classic Access and by adding global routing to the direct link. For more information, see [Setting up access to your Classic Infrastructure from VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-setting-up-access-to-classic-infrastructure).

For information about the differences between the new Direct Link offerings and the "on Classic" versions, see [How do I know which Direct Link solution to order?](https://cloud.ibm.com/docs/direct-link?topic=direct-link-get-started-with-ibm-cloud-direct-linkget-started-solution-to-order) and [Getting started with IBM Cloud Direct Link Dedicated](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl).
* How does IBM Cloud Direct Link work?

For every Direct Link customer, the IBM Cloud® team assigns a small private subnet to build a point-to-point network between the IBM Cloud cross-connect router (XCR) and the customer's edge router (CER). Then, IBM Cloud and the customer configure Border Gateway Protocol (BGP) to exchange routes between the environments. Finally, IBM Cloud places the customer into a VRF to allow for the implementation of non-unique routes to the private address space of the customer's remote network.
* Where do I find cost estimates for Direct Link offerings?

You can estimate the cost of a service using the cost estimator on the provisioning pages for Direct Link on Classic offerings.
The following diagram shows an example of a multisite – multitenant topology. It consists of a two layer Tier-0 design with three edge clusters. The routing table separation is done at Tier-1 and optionally, also at the regional Tier-0 level. Two edge clusters in the two data centers or zones in a multizone region, and one edge cluster deployed across the multizone region with edge nodes in each participating zone or data center.

Zoom

![Multisite – multitenant example topology](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/arch-pattern-2-zone-mt.svg)

Figure 2. Multisite – multitenant example topology



1. The vCenter Server automation deploys a single site solution, which can be manually expanded to support the target multisite topology. The deployment includes a single vCenter and three NSX-T Managers deployed in the cluster on the initial IBM Cloud data center location. You must expand the compute capacity to have resources available in the other IBM Cloud data center or zone in the specific IBM Cloud multizone region.
2. The vCenter Server automation deploys two edge cluster transport nodes and a single edge cluster for your Tier-0 and Tier-1 Gateways. You do not need the default Tier-1 Gateway, and it can be removed.
3. In the initial IBM Cloud data center, the access to private network is provided through private uplinks. They are attached to a portable subnet on a private primary VLAN on the IBM Cloud private network. If you provision your instance with public interfaces, the access to public network is provided through public uplinks. They are attached to a portable subnet on a public VLAN on the IBM Cloud public network. The uplinks have IP addresses specific to this data center and they cannot move between the data centers.
4. You must manually deploy two additional edge cluster transport nodes and create a new edge cluster for your Tier-0 and Tier-1 Gateways in the second IBM Cloud data center hosts.
Endpoints 



  Standard and Enterprise plans 

The Standard and Enterprise plans offer the choice of Public, Private, or both Public and Private endpoints.



*  Public network service endpoint is accessible from anywhere on the internet.
*  Private network service endpoint access traverses only the IBM Cloud backbone network, not the public internet.





  Instance creation 

At the time of instance creation, you can select your choice of endpoint from the Service Endpoints box on IBM Cloud.

Zoom

![Instance creation endpoints](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/creation_endpoint.png)

Figure 1. Endpoint choice at instance creation





  Changing endpoints after creation 

You can change endpoints at any time after creating an instance of a Standard or Enterprise plan.

To change endpoints, complete the following steps:



*  Select your Db2 service from IBM Cloud.
*  From the Manage tab, click Open Console.
*  Select Administration from the left side menu.
*  Select the Access restriction tab.
*  Select either Public endpoints, Private endpoints, or Public-and-private endpoints.
*  Click Update. The change occurs immediately.



Zoom

![Change endpoints](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/change_endpoint.png)

Figure 2. Change endpoint after instance creation





  View endpoints 

To view your endpoints:



*  Select your Db2 service from IBM Cloud.
*  From the Manage tab, click Open Console.
*  Select Administration from the left side menu.
*  Select the Connections tab. Endpoint information will be displayed in Connection configuration resources.



Zoom

![Endpoint information](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/endpoint_info.png)

Figure 3. Viewing endpoint information
No, billing and subscriptions are managed at the enterprise level rather than at the child account level. Your child account cannot have a different subscription. For more information about enterprise billing, see [Billing options](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-enterprise&interface=uienterprise-billing-options).
* Can I change the domain for my enterprise account?

Yes, domains can be updated. You can use the [Enterprise Management API](https://%7BDomainName%7D/apidocs/enterprise-apis/enterpriseupdate-enterprise) to update your domain.
* Do individual child accounts receive separate invoices if they are in an enterprise account?

You can view usage for individual child accounts, but they are not individually invoiced. For more information about enterprise usage, see [Viewing usage in an enterprise](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-enterprise-usage&interface=ui).

For more information about enterprise billing, see [Centrally managing billing and usage with enterprises](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-enterprise).
* What account type do I need to create an enterprise account?

Only Subscription accounts can create an enterprise account.
* How many child accounts can I have in an enterprise account?

You can have a maximum of 300 child accounts that can be distributed across a maximum of 300 account groups. An enterprise can contain up to five tiers of accounts and account groups. For more information, see [Enterprise hierarchy](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-what-is-enterprise&interface=uienterprise-hierarchy)
* Can I create common resources for all of my child accounts?

Although you can create resources at the enterprise account level, this method is not a best practice. You can follow best practice by using resource groups and access groups to create and share resources.
Volumetric analysis 

To accommodate [maximum scaling requirements](https://cloud.ibm.com/docs/enterprise-account-architecture?topic=enterprise-account-architecture-account-reqs) while remaining within IBM Cloud limits, you can group multiple IBM Cloud accounts within IBM Cloud enterprises to enable consolidated management and billing.

Use of two enterprise accounts are recommended to separate development and production resources for operational, accounting, and scaling benefits. Within each account, applications and shared infrastructure are placed within a hierarchy of account groups that represent business units and optional subgroups. These subgroups can be used to represent portfolios or other parts of a business unit org tree.

Zoom

![volumetric analysis diagram](https://cloud.ibm.com/docs-content/v1/content/f18e964848e0337fedc42d43e246fa446f4b9646/enterprise-account-architecture/images/volume.svg)

Figure 1. Volumetric Analysis: how basic account structure scales to required number of applications

The two enterprise account model increases separation between the development and production environments, enables separate billing and accounting, and improves scale. However, it increases complexity and requires duplication of some work, for example, setting up enterprises and configuring certain shared services. This duplication of work is largely mitigated through automation.

Business unit account groups do not have to map directly to an enterprise's internal org structure. If needed, two or more smaller BUs can be placed in a single BU account group, or large BUs can be split into two. Beneath the BU layer, an optional layer of "portfolio" account groups can be used to further separate workloads and accounts to align with organizational needs.

IBM Cloud has a limit of 300 account groups and 300 total accounts per enterprise.
Adding a private network endpoint 

You add a private endpoint to a paid service instance from the service details page if you have a Manager or Writer service access role.



1. Go to your [Resource list](https://cloud.ibm.com/resources).
2. Click the name of a service instance that is on a paid plan. Lite plans do not support private network endpoints.
3. In the service details page, click the Manage tab.
4. Click Add private network endpoint.









 Viewing your endpoint URL 

The service endpoint URLs are different for private and public network endpoints. You can view the URL for an endpoint from the service details page.



1. Go to your [Resource list](https://cloud.ibm.com/resources).
2. Click the name of a service instance that has a private network endpoint.
3. In the service details page, click the Manage tab, and then click Private Network Endpoint.







 What to do next 



* [Configure your account](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint) for VRF and Service endpoints.
* Modify your applications to use the new service endpoint URL.
* Read more about [service endpoints](https://cloud.ibm.com/docs/account?topic=account-service-endpoints-overview).
If you want to add the account to an account group, find the names and IDs of existing account groups in the enterprise.

ibmcloud enterprise account-groups --recursive
3. Import the account into the enterprise, specifying the account ID for the --account ID parameter. If you don't specify a parent account group, the account is added directly under the enterprise.

ibmcloud enterprise account-import --account-id ID
[--parent-account-group ACCOUNT_GROUP_NAME | --parent-account-group-id ACCOUNT_GROUP_ID]







 Importing accounts by using the API 

To import an existing account to the enterprise, call the [Enterprise Management API](https://cloud.ibm.com/apidocs/enterprise-apis/enterpriseimport-an-account-into-an-enterprise) as shown in the following sample request. Replace the IBM Cloud Identity and Access Management (IAM) token and ID variables with the values from your enterprise.



* Curl
* Java
* Python
* Go
* Node



curl -X PUT "https://enterprise.cloud.ibm.com/v1/enterprises/$ENTERPRISE_ID/import/accounts/$ACCOUNT_ID" -H "Authorization: Bearer <IAM_Token>" -H 'Content-Type: application/json' -d '{
"parent": "crn:v1:bluemix:public:enterprise::a/$ENTERPRISE_ACCOUNT_ID::enterprise:$ENTERPRISE_ID",
"billing_unit_id": "$BILLING_UNIT_ID"
}'

ImportAccountToEnterpriseOptions importAccountToEnterpriseOptions = new ImportAccountToEnterpriseOptions.Builder()
.enterpriseId(enterpriseId)
.accountId(importAccountId)
.build();

Response<Void> response = service.importAccountToEnterprise(importAccountToEnterpriseOptions).execute();

response = enterprise_management_service.import_account_to_enterprise(
enterprise_id=enterprise_id,
Managing enterprises, account groups, and accounts (ibmcloud enterprise) 

Use the following commands from the IBM Cloud® Command Line Interface to manage enterprise, account groups, and accounts.



 ibmcloud enterprise create 

Create an enterprise.

ibmcloud enterprise create NAME [-d, --domain DOMAIN_NAME] [--primary-contact-id PRIMARY_CONTACT_USER_ID]



 Command options 

NAME (required)
: Enterprise name.

-d, --domain DOMAIN_NAME (optional)
: Domain name.

--primary-contact-id PRIMARY_CONTACT_USER_ID (optional)
: Primary contact user ID of the enterprise.







 ibmcloud enterprise update 

Update enterprise information.

ibmcloud enterprise update (-n, --name NEW_NAME) [-f, --force]



 Command options 

-f, --force (optional)
: Update without confirmation.

-n, --name NEW_NAME (required)
: New name of the enterprise.







 ibmcloud enterprise show 

Display details of the enterprise.

ibmcloud enterprise show





 ibmcloud enterprise account-group-create 

Create an account group.

ibmcloud enterprise account-group-create NAME [--parent-account-group ACCOUNT_GROUP_NAME] [--primary-contact-id PRIMARY_CONTACT_USER_ID]



 Command options 

NAME (required)
: Account group name.

--parent-account-group ACCOUNT_GROUP_NAME (optional)
: Name of the parent account group. If omitted, the parent would be the current enterprise.

--primary-contact-id PRIMARY_CONTACT_USER_ID (optional)
: Primary contact user ID of the account group.







 ibmcloud enterprise account-group-update 

Update an account group.

ibmcloud enterprise account-group-update (-n, --name NAME | --id ID) (--new-name NEW_NAME)



 Command options 

--id ID (required)
: ID of target account group. This option is exclusive with -n, --name.

-n, --name NAME (required)