vania-janet/multiturn-rag-retrieval-data huggingface dataset:
0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024 lb-subnet

Public IPs
Reserved IPs ID Address Subnet
0767-16871e0f-c43a-4b6e-8491-a3e075362046 10.241.64.11 0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024
0767-a7db5d37-42cf-473e-ab27-07b679d64ceb 10.241.64.12 0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024

Provision status update_pending
Operating status online
Is public false
Listeners
Pools ID Name

Resource group ID Name
42c4f51adc3147b4b4049ad9826c30a1 Default

Created 2023-02-10T13:36:44-06:00
Instance Group Supported -
SourceIP Session Supported -
Security groups ID Name
r014-b739c959-fb3c-44cc-9ec5-41c45b4d637e astonish-backing-shadiness-frostlike-cosmos-hunk

UDP Supported false







 Working with DNS zones with the API 

You can bind and unbind DNS zones to an application load balancer during provisioning, or to an existing load balancer.



 Creating a load balancer bound to a private DNS zone with the API 

You will need the CRN of the private DNS that you want to bind to your load balancer. To find it, click Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > Resource List from the IBM Cloud console. Click the table row of the DNS whose CRN you want to find.
Engage with an IBM Representative to further evaluate options, resources, and pricing at [https://www.ibm.com/cloud/api-connect](https://www.ibm.com/cloud/api-connect) by chat or email.

Self-service migration documentation: Read our detailed documentation specific to each option to assist you to extract your data and migrate your API assets using provided tooling.



* Option 1 - [Documentation for migrating to Reserved Plan](https://www.ibm.com/docs/api-connect/10_reserved_instance?topic=migrating-from-api-connect-v5-public-cloud)
* Option 2 - [Documentation for migrating to a software deployment](https://www.ibm.com/docs/en/api-connect/10.0.5.x_lts?topic=connect-migrating-from-api-v5-public-cloud)



Sincerely,

The IBM API Connect Team
apiconnect.webhook_updateCatalogScope.update Update the Webhook object by name or ID 







 Viewing events 

Events that are generated by an API Connect Reserved instance are automatically forwarded to the IBM Cloud Activity Tracker service instance that is available in the same location.

IBM Cloud Activity Tracker can have only one instance per location. To view events, you must access the web UI of the IBM Cloud Activity Tracker service in the same location where your service instance is available. For more information, see [Launching the web UI through the IBM Cloud UI](https://cloud.ibm.com/docs/Activity-Tracker-with-LogDNA?topic=Activity-Tracker-with-LogDNA-launchlaunch_step2).
[Edit icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc//images/edit.png) to update the name. 
 Resource group The resource group of the endpoint gateway. 
 Virtual private cloud The VPC where the endpoint gateway is located. Click to see the VPC's details. 
 Subnets The bound reserved IP addresses' subnets to this endpoint gateway. Click to see the subnet's details. 
 Service name The service offering name of the target for this endpoint gateway. 
 Service instance name The service instance name of the service target for this endpoint gateway. 
 Service endpoint The fully qualified domain name for the target service. 
 Target CRN The service instance's target CRN value. 



From the Attached resources section, you can select to view either Reserved IP or Security groups. Click Manage attached resources to switch to the Attached resources view.

The Reserved IPs table shows all bound, reserved IPs to this endpoint gateway. Descriptions of the fields in the Reserved IPs table are:



Table 2. Details about your endpoint gateway bound reserved IPs

 Field Description 

 Name The reserved IP name. 
 Subnet The subnet name of the reserved IP. Click to see the subnet's details. 
 Location The reserved IP's location and subnet. 
 IP address The IP address value of the reserved IP. Click to copy it. 
 Auto delete Move the Auto Delete switch to enable or disable deletion for the reserved IP. If it is enabled (green), this reserved IP is deleted automatically when the target is deleted. 
 Actions Click the Actions menu ![Actions menu](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/overflow.png) to display a menu of context-specific actions that you can take.
For single zone clusters, enter the name of the tiered storage class that you want to use. Example: ibmc-vpc-block-10iops-tier. For more information about VPC tiered storage classes, see the [Block Storage for VPC Storage class reference](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockvpc-block-reference). N/A 
 osdSize Enter a size for your storage devices. Example: 100Gi. The total storage capacity of your ODF cluster is equivalent to the osdSize multiplied by the numOfOsd. N/A 
 numOfOsd Enter the number object storage daemons (OSDs) that you want to create. ODF creates three times the numOfOsd value. For example, if you enter 1, ODF provisions 3 disks of the size and storage class that you specify in the osdStorageClassName field. 1 
 billingType Enter a billingType of either essentials or advanced for your ODF deployment. advanced 
 ocsUpgrade Enter true or false to upgrade the major version of your ODF deployment. false 
 workerNodes Optional: Enter the node names for the worker nodes that you want to use for your ODF deployment. Don't specify this parameter if you want to use all the worker nodes in your cluster. N/A 
 clusterEncryption Enter true or false to enable cluster wide encryption.
Names must be unique within the subnet that the reserved IP resides in. Names beginning with ibm- are reserved for provider-owned resources.
* --pnic-sgs: Comma-separated security group IDs for primary network interface.
* --pnic-allowed-vlans: Comma-separated VLAN IDs. Indicates which VLAN IDs (for VLAN interfaces only) can use the primary network interface. It can be passed as separate values or as any range of numbers.
* --pnic-ein: Enable Infrastructure NAT (EIN). If true, the VPC infrastructure performs any needed NAT operations. If false, the packet is passed unmodified to or from the network interface, allowing the virtual machine that is associated with the floating IP to perform any needed NAT operations. One of: true, false. (default: true).
* --pnic-ais: Allow IP Spoofing (AIS). If true, source IP spoofing is allowed on packets that are using this network interface. If false, source IP spoofing is prevented on this interface. One of: false, true. (default: false).
* --network-interfaces: NETWORK_INTERFACES_JSON|@NETWORK_INTERFACES_JSON_FILE. Network interface configuration in JSON or JSON file. For the data schema, check the network_interfaces property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-bare-metal-server).
* --enable-secure-boot: Indicates whether secure boot is enabled. If enabled, the image must support secure boot or the server fails to boot. One of: false, true. (default: false).
* --tpm-mode: The mode for the trusted platform module (TPM). One of: tpm_2, disabled.
* --resource-group-id: ID of the resource group. This ID is mutually exclusive with --resource-group-name.
* --resource-group-name: Name of the resource group.
* --new-reserved-ip: RESERVED_IP_JSON|@RESERVED_IP_JSON_FILE, new reserved IP configuration in JSON or JSON file.
* --sg: Comma-separated security group IDs or names for the endpoint gateway.
* --resource-group-id: ID of the resource group. This ID is mutually exclusive with --resource-group-name.
* --resource-group-name: Name of the resource group. This name is mutually exclusive with --resource-group-id.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is endpoint-gateway-update 

Update an endpoint gateway.

ibmcloud is endpoint-gateway-update ENDPOINT_GATEWAY --name NEW_NAME [--vpc VPC] [--output JSON] [-q, --quiet]



 Command options 



* ENDPOINT_GATEWAY: ID or name of the endpoint gateway.
* --vpc: ID or name of the VPC. It is only required to specify the unique resource by name inside this VPC.
* --name: New name of the endpoint gateway.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is endpoint-gateway-reserved-ip-bind 

Bind a reserved IP to an endpoint gateway.

ibmcloud is endpoint-gateway-reserved-ip-bind ENDPOINT_GATEWAY (--rip RIP [--subnet SUBNET]) [--vpc VPC] [--output JSON] [-q, --quiet]



 Command options 



* ENDPOINT_GATEWAY: ID or name of the endpoint gateway.
* --vpc: ID or name of the VPC.
Viewer View service instances but not modify them <br><br> * List available COS service instances<br> * View COS service plan details<br> * View usage details<br><br><br> 
 Editor Perform all platform actions except for managing the accounts and assigning access policies <br><br> * Create and delete COS service instances<br><br><br> 
 Operator Not used by COS None 
 Administrator Perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users, as well as setting PublicAccess policy on buckets. <br><br> * Update user policies<br> * Update pricing plans<br><br><br> 



The following table details actions that are mapped to service access roles. Service access roles enable users access to Object Storage as well as the ability to call the Object Storage API.



Table 3. IAM service access roles and actions

 Service access role Description of actions Example actions 

 Object Writer Upload and overwrite objects (including uploading objects in multiple parts). <br><br> * Upload objects<br><br><br> 
 Object Reader Download objects, read object metadata (headers), but not list objects or buckets. <br><br> * Download objects<br><br><br> 
 Content Reader Download and list objects, read object metadata (headers), but not list buckets. <br><br> * Download and list objects<br><br><br> 
 Reader In addition to Content Reader actions, Readers can list buckets and read bucket metadata, but not make modifications. <br><br> * List buckets<br><br><br> 
 Writer In addition to Reader actions, Writers can create buckets and upload objects. <br><br> * Create new buckets and objects<br> * Remove buckets and objects<br><br><br> 
 Manager In addition to Writer actions, Managers can complete privileged actions that affect access control.
In this case, you want to give department leads of the Marketing, Development, and Sales account groups access to manage their accounts and resource usage, and you want the Example Corp. financial officer to have access to view the entire enterprise's billing and usage. To give other users access, you invite them to the enterprise account and assign them the appropriate access.

First, invite the department leads and assign them access.



1. Go to the Enterprise dashboard by clicking Manage > Enterprise in the IBM Cloud console. In the Users section, click Invite users.
2. Enter the email address of the user you want to invite, such as jsmith@example.com.
3. Expand the Assign access to the users section.
4. Select Account management
5. Select Enterprise.
6. Select the Example Corp enterprise.
7. Select the first account group, Marketing. Leave the account selection blank. This scopes the access to only the particular account group.
8. Select the Editor role.
9. Click Add.
10. Click Invite.



Invite the other two department leads by clicking Invite users again and assigning the Editor access role for their department's respective account groups. Then, invite the financial officer and follow the same steps, but don't select an account group, and assign the Usage Report Viewer access instead.

With the Usage Report Viewer role, the financial officer can see usage from all accounts but can't create, import, or otherwise organize accounts. You then need to provide them access to billing in the enterprise.



1. From the Users page, click the name of the user from the list.
2. Click Access > Assign access.
3. Select the Billing service, and then select the Administrator role.
4. Click Review.
5. Click Add to add your policy configuration to your policy summary.
6. Click Assign.







 Step 7: Assign users in child accounts access to create resources 

Before you begin, make sure that you switch to the account where you want to create the resource. In this case, switch to the Print account.
In the Version list table, click the row that contains your Operator bundle.
2. Click Add license agreements > Add.
3. Enter the name and URL of the license agreement, and click Update.
4. After entering all additional license agreements, click Next.







 Step 5: Review your readme file 

When users install the software, they can select the link to your readme file to view product information. The information in the Readme link is generated from the readme file information in the Edit readme tab.



1. From the Edit readme tab, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/edit-tagging.svg).
2. Preview how the information in the readme file will be displayed to users when they install the Operator bundle.
3. If you need to make changes, edit the information in the source file and import the updated Operator bundle to your private catalog.
4. Click Next.







 Step 6: Validate your Operator bundle 

Validate that the Operator bundle can be successfully installed on the target Red Hat OpenShift on IBM Cloud cluster.



1. Click Validate product
2. Select the Update channel to receive version updates from.
3. Select whether you want to apply updates automatically or manually.
4. Select the target cluster and project, and click Next.
5. Enter the name of your Schematics workspace, select a resource group, select a Schematics region, and click Next.

In the Tags field, you can enter a name of a specific tag to attach to your Operator. Tags provide a way to organize, track usage costs, and manage access to the resources in your account.
6. Click Validate.







 Step 7: Manage compliance 

Controls are safeguards that are used to meet security and compliance requirements.
Editor View network zones<br><br>Create network zones<br><br>Update network zones<br><br>Remove network zones 
 Administrator View network zones<br><br>Create network zones<br><br>Update network zones<br><br>Remove network zones 







 Enterprise 

You can use the Enterprise service to assign users access to manage an enterprise by creating accounts within the enterprise, assigning accounts to account groups, naming account groups, and more. This type of policy works only if it is assigned within the enterprise account.



Table 7. Roles and example actions for the Enterprise service

 Roles Actions 

 Viewer View the enterprise, account groups, and accounts 
 Operator Not applicable 
 Editor View and update the enterprise name and domain, create accounts and account groups, view usage reports, and import accounts. 
 Administrator View and update the enterprise name and domain, create accounts and account groups, move accounts between account groups, import existing accounts, and view usage reports 
 Usage report viewer View the enterprise, accounts, and account groups and view usage reports for all accounts in the enterprise. 







 Global catalog 

You can give users access to view private products in the catalog or change the visibility of private products for other users in the account.



Table 8. Roles and example actions for the Global Catalog service

 Roles Actions 

 Viewer View private services 
 Operator Not applicable 
 Editor Change object metadata but can't change visibility for private services 
 Administrator Change object metadata or visibility for private services, and restrict visibility of a public service 







 IAM Access Groups 

You can give users access to view, create, edit, and delete access groups in the account by using the IAM Access Groups service.



Table 9. Roles and example actions for the IAM access groups service

 Roles Actions 

 Viewer View access groups and members 
 Operator Not applicable 
 Editor View, create, edit, and delete groups<br><br>Add or remove users from groups 
 Administrator View, create, edit, and delete groups<br><br>Add or remove users<br><br>Assign access to a group<br><br>Manage access for working with access groups<br><br>Enable or disable public access to resources at the account level 







 IAM Access Management service
Editor View network zones<br><br>Create network zones<br><br>Update network zones<br><br>Remove network zones 
 Administrator View network zones<br><br>Create network zones<br><br>Update network zones<br><br>Remove network zones 







 Enterprise 

You can use the Enterprise service to assign users access to manage an enterprise by creating accounts within the enterprise, assigning accounts to account groups, naming account groups, and more. This type of policy works only if it is assigned within the enterprise account.



Table 6. Roles and example actions for the Enterprise service

 Roles Actions 

 Viewer View the enterprise, account groups, and accounts 
 Operator Not applicable 
 Editor View and update the enterprise name and domain, create accounts and account groups, view usage reports, and import accounts. 
 Administrator View and update the enterprise name and domain, create accounts and account groups, move accounts between account groups, import existing accounts, and view usage reports 
 Usage report viewer View the enterprise, accounts, and account groups and view usage reports for all accounts in the enterprise. 







 Global catalog 

You can give users access to view private products in the catalog or change the visibility of private products for other users in the account.



Table 7. Roles and example actions for the Global Catalog service

 Roles Actions 

 Viewer View private services 
 Operator Not applicable 
 Editor Change object metadata but can't change visibility for private services 
 Administrator Change object metadata or visibility for private services, and restrict visibility of a public service 







 IAM Access Groups 

You can give users access to view, create, edit, and delete access groups in the account by using the IAM Access Groups service.



Table 8. Roles and example actions for the IAM access groups service

 Roles Actions 

 Viewer View access groups and members 
 Operator Not applicable 
 Editor View, create, edit, and delete groups<br><br>Add or remove users from groups 
 Administrator View, create, edit, and delete groups<br><br>Add or remove users<br><br>Assign access to a group<br><br>Manage access for working with access groups<br><br>Enable or disable public access to resources at the account level 







 IAM Access Management service
[Log in to the web console](https://cloud.ibm.com/docs/netezza?topic=netezza-getstarted-console).
2. Go to Administering > Workload patterns.
3. Review the smart scaling utilization graph.
In this example, as a database administrator, you want to to get a deeper understanding of your system utilization over time.

In this scenario, it turns out that every Sunday, your system utilization drops below average as compared to other days of the week. Basing on this information, you can update your scaling schedule to match anticipated peaks and dips in workloads.
4. Configure the scheduler to scale down the instance for every Sunday as described in [Editing scheduled scaling](https://cloud.ibm.com/docs/netezza?topic=netezza-scaling-consolescaling-console-editing).
5. Configure the scheduler to scale up back starting every Monday as described in [Editing scheduled scaling](https://cloud.ibm.com/docs/netezza?topic=netezza-scaling-consolescaling-console-editing).



As a result, you will see performance improvement and reduction in resource waste and costs in the future.
In the expression box, enter sum(node_namespace_pod_container:container_cpu_usage_seconds_total:sum_irate{namespace="<MYPROJECT>"}) by (container), replace <MYPROJECT> by your project name and click Run queries to see the total container cpu usage in seconds on a graph.
5. Under Observe, select Dashboards.
6. Click on the Dashboard dropdown and select Kubernetes / Compute Resources / Namespace (Workloads).
7. Change Namespace to your project.
8. Set Time Range to Last 5 minutes.
9. Check the CPU and memory usage.
10. Stop the above script using control+C. For logging, you can use the in-built oc logs command. Check [viewing logs for a resource](https://docs.openshift.com/container-platform/4.12/logging/viewing-resource-logs.html) to learn about the usage of oc logs.

You can also provision and use IBM Log Analysis and IBM Cloud Monitoring services for logging and monitoring your Red Hat OpenShift on IBM Cloud application. Follow the instructions mentioned in [this link](https://cloud.ibm.com/docs/openshift?topic=openshift-health) to setup logging and monitoring add-ons to monitor cluster health.







 Step 4: Scale the app 

In this section, you will learn how to manually and automatically scale your application.



 Manual scaling 



1. You can achieve manual scaling of your pods with oc scale command. The command sets a new size for a deployment configuration or replication controller

oc scale dc/$MYPROJECT --replicas=2
2. You can see a new pod being provisioned by running oc get pods command.
3. Rerun the [Monitoring](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-scalable-webapp-openshiftscalable-webapp-openshift-monitor_application) step to see the updated logs for both the pods using the oc logs command.
Check out [Pricing](https://cloud.ibm.com/docs/key-protect?topic=key-protect-pricing-plan) for more information.



 Rotating manually or automatically 

Only root keys can be rotated using Key Protect. Standard keys cannot be rotated.

Root keys can be rotated manually or on a schedule set by the owner of the key. The option you choose depends on your preferences and the needs of your use case.



* Setting a rotation policy
The simplest key rotation option, setting an [automatic rotation interval](https://cloud.ibm.com/docs/key-protect?topic=key-protect-key-rotationrotation-frequency) means root keys are updated without further effort from the user. These rotations can be set at 30 day intervals (in other words, every 30 days, or 60 days, or 90 days, up to 12 months, or 720 days). This policy can be managed in the UI or by using the Key Protect API. For more information about how to set a rotation policy, check out [Setting a rotation policy](https://cloud.ibm.com/docs/key-protect?topic=key-protect-set-rotation-policy). The process can also be set using the [CLI](https://cloud.ibm.com/docs/key-protect?topic=key-protect-key-protect-cli-referencekp-key-policy-update-rotation).

To rotate a key that you initially imported to the service, you must generate and provide new key material for the key with each rotation. As a result, automatic rotation policies are not available for keys that have imported key material. Imported root keys must therefore be rotated manually. Note that the metadata for imported keys, such as the key ID, do not change when the key is rotated, just as with a key generated with Key Protect.
* Rotating keys manually
As a security admin, you might want to have more control over the frequency of rotation for your root keys. If you don't want to set an automatic rotation policy for a key, you can manually create a new key to replace an existing key, and then update your applications so that they reference the new key.