vania-janet/multiturn-rag-retrieval-data huggingface dataset:
: Operator platform access role for the cluster in IBM Cloud Kubernetes Service.

Command options:

--name NAME
: Required: Set the name for the worker pool.

-c, --cluster CLUSTER
: Required: Specify the name or ID of the cluster. To list VPC clusters, run ibmcloud ks cluster ls --provider vpc-gen2.

--size-per-zone NUMBER_WORKERS_PER_ZONE
: Specify the number of worker nodes to create per zone in this worker pool. No worker nodes are created until you [add zones](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clicli_zone-add-vpc-gen2) to the worker pool. This value is required, and must be 1 or greater. For more information, see [What is the smallest size cluster that I can make?](https://cloud.ibm.com/docs/containers?topic=containers-faqssmallest_cluster).

--operating-system SYSTEM
: Optional. The operating system of the worker nodes you want to provision in your cluster. For a list of available operating systems by cluster version, see [IBM Cloud Kubernetes Service version information](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions).

--flavor FLAVOR
: Choose a flavor for your worker nodes. You can deploy your worker nodes as virtual machines on shared or dedicated hardware. To see flavors that are available in a VPC zone, run ibmcloud ks flavors --zone <vpc_zone> --provider vpc-gen2.

--vpc-id VPC_ID
: Optional: Specify the ID of the VPC in which to create the worker pool's worker nodes. The value must match the VPC ID that the cluster is in. To list the cluster's VPC ID, run ibmcloud ks cluster get -c <cluster_name_or_ID>.
Deploying SAP HANA db backup to iCOS on existing IBM Cloud VPC with automation 

You can use Terraform scripts to Hana db backup to iCOS automation module on existing HANA database already deployed instance on the VPC. The Terraform scripts use the VPC information that you provide and then call the Ansible playbook to create the SAP architecture on the specified VPC. Terraform on IBM Cloud enables predictable and consistent provisioning of IBM Cloud Virtual Private Cloud (VPC) infrastructure resources so that you can rapidly build complex, cloud environments. IBM Cloud VPC infrastructure consists of SAP certified hardware that uses Intel Xeon CPUs and additional Intel technologies.



 Solution implemented 

Zoom

![Figure 1. SAP HANA db backup to iCOS from a standard SAP NW on HANA db architecture](https://cloud.ibm.com/docs-content/v1/content/f89cc64b006ca59b35404693959c83d5747fee3e/sap/images/sap-hana-backup-on-vpc.svg)

Figure 1. SAP HANA db backup to iCOS from a standard SAP NW on HANA db architecture





 What is created 

This automation solution is designed for the implementation of an SAP HANA Backup solution that uses Backint and [IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage). It is based on SAP note "2935898 - Install and Configure SAP HANA Backint Agent for Amazon S3".

The minimum version of SAP HANA Backint Agent for Amazon S3 to be used for IBM Cloud Object Storage is 1.2.17. "SAP HANA Backint Agent for Amazon S3" requires Python3.7, including SSL support. The Python package delivered as part of the SAP HANA 2 installation does not include SSL support. Python 3.7 with SSL support is installed in addition in /usr/local/bin directory, in case it isn't previously installed. SAP HANA Backint Agent for Amazon S3 is installed in /hana/shared/< SID >/backint_agent directory.
Cluster nodes that are deployed with this offering include IBM Spectrum LSF 10.1 Standard Edition plus Data Manager plus License Scheduler. See the following for a brief description of each of those programs: [IBM Spectrum LSF 10 family of products](https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/4/897/ENUS220-174/index.html&lang=en&request_locale=en)

If the cluster uses Spectrum Scale storage, the storage nodes include IBM Spectrum Scale 5.1.3.1 software. For more information, see the [IBM Spectrum Scale](https://www.ibm.com/docs/en/spectrum-scale/5.1.3) product documentation.





 How many compute worker and storage nodes can I deploy in my Spectrum LSF cluster through this offering when spectrum_scale is enabled? 

Before you deploy a cluster, it is important to ensure that the VPC resource quota settings are appropriate for the size of the cluster that you would like to create (see [Quotas and service limits](https://cloud.ibm.com/docs/vpc?topic=vpc-quotas)).

The maximum number of compute nodes that are supported for the deployment value total_compute_cluster_instances is 64. The maximum number of storage nodes that are supported for the deployment value total_storage_cluster_instances is 18.





 Why is the CPU number displayed on an LSF worker node different than what is shown in the LSF Application Center GUI? 

The CPU column in the LSF Application Center GUI and the ncpus column when you run the lscpu command on an LSF worker node might not show the same value.

The CPU column output that you get by running lscpu | egrep 'Model name|Socket|Thread|NUMA|CPU(s)' on an LSF worker node shows the number of CPU threads (not physical cores) on that compute instance.

If EGO_DEFINE_NCPUS=threads, then “ncpus=number of processors x number of cores x number of threads” and the CPU column value in the LSF Application Center GUI will match what you see when running lscpu on an LSF worker node.
To request a cross-account connection, set the following parameters:



Table 1. Path parameters for adding a cross-account connection

 Path parameters Details 

 transit_gateway_id <br>Required <br>string The transit gateway identifier 





Table 2. Query parameters for adding a cross-account connection

 Query parameters Details 

 version <br>Required <br>string Requests the version of the API as of a date in the format YYYY-MM-DD. Any date up to the current date may be provided. Specify the current date to request the latest version. <br>Possible values: Value must match regular expression ^[0-9]{4}-[0-9]{2}-[0-9]{2}$ 
 Request Body <br>Required <br>TransitGatewayConnectionTemplate The connection template 
 network_type <br>Required <br>string Defines what type of network is connected via this connection. <br>Allowable values:classic, vpc, unbound_gre_tunnel, or directlink <br>Example:vpc 
 name <br>Name The user-defined name for this transit gateway connection. Network type vpc connections are defaulted to the name of the VPC. Network type classic connections are named Classic. <br>Possible values:1 ≤ length ≤ 63, Value must match regular expression ^([a-zA-Z]-[a-zA-Z][a-zA-Z0-9])$ <br>Example:Transit_Service_BWTN_SJ_DL 
 network_account_id <br>AccountID The ID of the account which owns the network that is being connected. Generally only used if the network is in a different account than the gateway. <br>This field is used when gateway connection is in network type classic. <br>This field is required to be unspecified for network type gre_tunnel. <br>Example:28e4d90ac7504be694471ee66e70d0d5 
 network_id <br>string The ID of the network being connected via this connection. This field is required for vpc and directlink.
In addition to the built-in methods, you can use standard methods of the java.util.Date class.

To get the date of the day that falls a week from today, you can use the following syntax.

{
"context": {
"week_from_today": "<? new Date(new Date().getTime() +
(7 * (2460601000L))) ?>"
}
}

This expression first gets the current date in milliseconds (since January 1, 1970, 00:00:00 GMT). It also calculates the number of milliseconds in 7 days. (The (2460601000L) represents one day in milliseconds.) It then adds 7 days to the current date. The result is the full date of the day that falls a week from today. For example, Fri Jan 26 16:30:37 UTC 2018. Note that the time is in the UTC time zone. You can always change the 7 to a variable ($number_of_days, for example) that you can pass in. Just be sure that its value gets set before this expression is evaluated.

If you want to be able to subsequently compare the date with another date that is generated by the service, then you must reformat the date. System entities (@sys-date) and other built-in methods (now()) convert dates to the yyyy-MM-dd format.

{
"context": {
"week_from_today": "<? new Date(new Date().getTime() +
(7 * (2460601000L))).format('yyyy-MM-dd') ?>"
}
}

After reformatting the date, the result is 2018-01-26. Now, you can use an expression like @sys-date.after($week_from_today) in a response condition to compare a date specified in user input to the date saved in the context variable.

The following expression calculates the time 3 hours from now.

{
* UI
* CLI
* API







 Viewing custom resolver details 

You view details of a single custom resolver and view a list of all custom resolvers in IBM Cloud® DNS Services by using the UI, CLI, or API.



 Viewing custom resolver details using the UI 

To view the details of a custom resolver using the UI, navigate to the custom resolver tab in the DNS Services instance. From the custom resolver view, you can view a list of all custom resolvers. There, you can view information about a specific custom resolver by clicking the custom resolver name.





 Get details of a custom resolver using the CLI 

To get the details of a custom resolver using the CLI, run the following command:

ibmcloud dns custom-resolver RESOLVER_ID [-i, --instance INSTANCE] [--output FORMAT]

Where:



* RESOLVER_ID is the ID of custom resolver.
* -i, --instance is the instance name or ID. If this is not set, the context instance specified by dns instance-target INSTANCE is used instead.
* --output specifies output format. Currently, JSON is the only supported format.





 List all custom resolvers 

To list all custom resolvers using the CLI, run the following command:

ibmcloud dns custom-resolvers [-i, --instance INSTANCE] [--output FORMAT]

Where:



* -i, --instance is the instance name or ID. If this is not set, the context instance specified by dns instance-target INSTANCE is used instead.
* --output specifies output format. Currently, JSON is the only supported format.









 Get details of a custom resolver using the API 



 Get details of a single custom resolver 

To get the details of a custom resolver using the API, follow these steps:



1. Set up your API environment with the correct variables.
2. Store the following values in variables to be used in the API command:



* instance_id, which is the unique identifier of a service instance.
Setting up an Application Load Balancer for VPC 

Expose your app to the public or to the private network by setting up a Kubernetes LoadBalancer service in your cluster. When you expose your app, an Application Load Balancer for VPC (VPC ALB) that routes requests to your app is automatically created for you in your VPC outside of your cluster.

Do not confuse the Application Load Balancer for VPC with IBM Cloud Kubernetes Service Ingress applications load balancers. Application Load Balancers for VPC (VPC ALBs) run outside your cluster in your VPC and are configured by Kubernetes LoadBalancer services that you create. [Ingress applications load balancers (ALBs)](https://cloud.ibm.com/docs/containers?topic=containers-managed-ingress-aboutmanaged-ingress-albs) are Ingress controllers that run on worker nodes in your cluster.



 Setting up a public or private VPC ALB 

Before you begin



* Ensure that you have the [Writer or Manager IBM Cloud IAM service access role](https://cloud.ibm.com/docs/containers?topic=containers-userschecking-perms) for the namespace in which you deploy the Kubernetes LoadBalancer service for the VPC NLB.
* [Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)
* To view VPC ALBs, install the infrastructure-service plug-in. The prefix for running commands is ibmcloud is.

ibmcloud plugin install infrastructure-service





* When cluster nodes are reloaded or when a cluster master update includes a new keepalived image, the load balancer virtual IP is moved to the network interface of a new node. When this occurs, any long-lasting connections to your load balancer must be re-established. Consider including retry logic in your application so that attempts to re-establish the connection are made quickly.



To enable your app to receive public or private requests,



1.
If the address prefix range is out of scope or doesn't belong to the family of the IP address range of the VPC, then you get an error that the address is not in range.

 How to fix it 

Validate if the address prefix range that's provided for subnet creation is from the same range of addresses that are used for the VPC. For example, if the VPC address prefix is 10.241.0.0/18, then the subnet should be in the 10.241.x.x range. If a different IP address range is used, then you need to divide the subnets and choose the IP address range that's required for subnet creation.





 Why does the deployment fail with a "process exited with status 2" error message? 

 What’s happening 

You are receiving the following error when you try to apply a plan to your workspace: Apply failed due to Error: Error: remote-exec provisioner error and error executing "/tmp/terraform_1756078506.sh": Process exited with status 2.

 Why it’s happening 

The solution is implemented with a logic to evaluate whether the provided license number is valid. This feature is designed on top of the custom image, so every time the deployment is done it evaluates and decrypts the required package for the product deployment to complete. If an image is used that doesn't have this functionality, the automation code errors out.

 How to fix it 

Use the appropriate custom image that is provided by the solution team, which has the function of evaluating the license and decrypting the packages.





 Why is IBM Cloud Schematics not able to provision the cluster and fails with an Enabling the Custom resolver error? 

 What’s happening 

While Schematics tries to create the VPC resources, it attempts to create a custom resolver but fails with the following error: [ERROR] Error Enabling the Custom resolver : MaxTimeout

 Why it’s happening 

Terraform attempts to create the custom resolver environment and waits for the custom resolver state to reach an active state. During this process, if the custom resolver takes more time than expected, Terraform throws the error message.

 How to fix it 

After a failed deployment, clean up all resources.
A null value in a JSON merge patch request body MUST NOT be accepted unless the field can be removed from the observable resource state.

An operation MUST NOT accept any other sentinel value in a request body to omit or remove a field from the subsequently observable state.

Omitted and null values offer similarly "empty" meaning, but the JSON merge patch type [employs the null value as a sentinel](https://datatracker.ietf.org/doc/html/rfc7386section-1) to remove an existing value. The recommendation of JSON merge patch by this handbook provides precedent for a client sending an explicit null value for a field to expect it to be subsequently omitted from the observable resource state. It is therefore considered dangerous to accept a null value from a client for a field that is required in the resource state reflected in responses. Finally, even for a field in a POST or PUT request that is optional and omitted from the subsequently observable state by default, it is both unnecessary and in violation of the principle of avoiding [input canonicalization](https://cloud.ibm.com/docs/api-handbook?topic=api-handbook-robustnessinput-canonicalization) to accept a null value.





 In responses 

A field in a response body SHOULD be required except where an aspect of a request or the state of a resource might make a value inapplicable or unknown and no industry convention for a sentinel value already exists for the value type.

If a field is optional in a response body, the circumstances where the field will be omitted and the significance of the field's omission (or, conversely, the circumstances and significance of its inclusion) MUST be well defined.

A field MUST NOT be omitted from a response body because an internal failure is currently preventing the system from retrieving its value. An internal failure of the service to populate a value MUST cause the entire request to fail with a 500 status code and appropriate error response model.

A field SHOULD NOT be omitted from a response body because the system hasn't yet computed its value. If a field is optional for that reason, its omission MUST be limited to a specific and observable resource state, such as a status value of pending.
For SAP HANA release versions (including SPS and Revision and Patch numbers), support is only available for pre-defined and specific major.minor releases of an Operating System (for example, RHEL 7.6). This information is shown in [SAP 2235581 - SAP HANA: Supported Operating Systems](https://launchpad.support.sap.com//notes/2235581). An example is available in the SAP Note attachment SAP_HANA_OS_Release_Support_Matrix.pdf.

For SAP NetWeaver release versions, support is available for each major release of an Operating System (for example, SLES 12) meaning each subsequent release is available for use (example: SLES 12 SPS4, SLES 12 SP5, and so on). This information is shown in the [SAP Product Availability Matrix (PAM)](https://support.sap.com/en/release-upgrade-maintenance.htmlsection_1969201630).





 OS configuration for SAP 

Each infrastructure has various operating systems with various images for those operating systems available on-demand.

Each of these on-demand OS images (for example, RHEL 7.6 for SAP HANA) is provided as shipped (also known as the "general availability" / "stock image" release) by each of the vendors (for example, Red Hat). These OS images are provided with access from the OS Package Manager (for example, RHEL4SAP, which is yum) to the OS package update channels specific to the OS Packages for SAP. The OS package update channels permit updates to the OS according to the latest SAP Notes for the relevant Operating System with the specified OS kernel versions, OS package versions, and OS package for SAP versions that are required.

Therefore, for OS images, you need to perform the following actions.



* OS configuration according to SAP guidance.
* OS package updates according to SAP guidance, which includes updates to specified OS kernel versions (for example, RHEL4SAP 7.6 ships with 3.10.0-957.el7.x86_64. However, SAP requires the 1.3 version 3.10.0-957.1.3.el7.x86_64).







 OS for Virtual Servers on VPC Infrastructure
In other words, the replicator database implementation is similar to a _changes feed consumption application, with ?include_docs=true set.

For replication, this implementation difference means that for nonadmin users, a user_ctx property that includes the user's name and a subset of their roles must be defined in the replication document. This requirement is addressed by a validation function present in the default design document of the replicator database. The function validates each document update. This validation function also ensures that a nonadmin user can't set a username property in the user_ctx property that doesn't correspond to the correct username. The same principle also applies for roles.

See the following example delegated replication document:

{
"_id": "my_rep",
"source": "https://$ACCOUNT:$PASSWORD@$SERVER.com:5984/foo",
"target": "https://$ACCOUNT:$PASSWORD@$ACCOUNT.cloudant.com/bar",
"continuous": true,
"user_ctx": {
"name": "joe",
"roles": ["erlanger", "researcher"]
}
}

For admins, the user_ctx property is optional. If the property is missing, the value defaults to a user context with the name null and an empty list of roles.

The empty list of roles means that design documents aren't written to local targets during replication. If you want to write design documents to local targets, then a user context with the _admin role must be set explicitly.

Also, for admins, the user_ctx property can be used to trigger a replication for another user. This user context is passed to local target database document validation functions.

The user_ctx property applies to local endpoints only.

In summary, for admins, the user_ctx property is optional. While for regular (nonadmin) users, it's mandatory. When the roles property of user_ctx is missing, it defaults to the empty list [ ].





 Performance-related options
In the Assign users additional access section, select IAM services and complete the following tasks:



* From the What type of access do you want to assign? list, select VPC Infrastructure Services.
* From the in list, select Resource group: default.
* From the Resource type list, select All resource types.
* In the Platform access area, select Editor.
* Make sure that the Resource group access option is set to Viewer.
* In the Service access area, select Console Administrator.
* Scroll to the end of the page and click Add.
* Review the Access summary side pane, and click Assign.









 Team access scenario 

This scenario shows how an account administrator can assign authorization so that different teams have access to separate VPC resources. The example uses resource groups to set up separate resource access for two teams. For the purposes of this example, resources are not shared across teams.

The example takes you through the process of creating resource groups, creating access groups, and assigning the appropriate policies to provide your teams with access to separate VPC resources.

In this scenario, you're setting up two different project teams to use separate VPCs. You'll assign access so that each team has access to their team's VPC resources only.



* Your first team is a test team. You've decided to assign them access to VPCs in a resource group named test_vpcs.
* The second team is your production team. They'll be assigned access to VPCs in a resource group named production_vpcs.



This strategy can be used to assign separate VPC resources to any number of teams. However, all resources share the same VPC quotas for the account. For more information about quotas and limits, see [VPC quotas](https://cloud.ibm.com/docs/vpc?topic=vpc-quotasquotas).



 Step 1: Create resource groups 

Create resource groups that contain each of your teams' VPC resources.



1. Create a resource group called test_team.
2. Create a resource group called production_team.
started_on Time when the task was started. The value is an integer that includes the UNIX™ time UTC. 
 total_changes Total number of documents to be processed by the task. The exact meaning depends on the type of the task. 
 type Operation Type 
 updated_on Time that the task status was updated. The field updates every few seconds. Returns the most recent update. 



In the type field, the possible values include:



* database_compaction
* view_compaction
* replication
* indexer
* search_indexer



The meaning of other fields in the JSON response depends on the type of the task.

See the example JSON response array that includes details of currently running tasks:

[
{
"user": null,
"updated_on": 1363274088,
"type": "replication",
"target": "https://repl:@tsm.cloudant.com/user-3dglstqg8aq0uunzimv4uiimy/",
"docs_read": 0,
"doc_write_failures": 0,
"doc_id": "tsm-admin__to__user-3dglstqg8aq0uunzimv4uiimy",
"continuous": true,
"checkpointed_source_seq": "403-g1AAAADfeJzLYWBgYMlgTmGQS0lKzi9KdUhJMjTRyyrNSS3QS87JL01JzCvRy0styQGqY0pkSLL___9_VmIymg5TXDqSHIBkUj1YUxyaJkNcmvJYgCRDA5AC6tuflZhGrPsgGg9ANAJtzMkCAPFSStc",
"changes_pending": 134,
"pid": "<0.1781.4101>",
"node": "dbcore@db11.julep.cloudant.net",
"docs_written": 0,