vania-janet/multiturn-rag-retrieval-data huggingface dataset:
"creationDate": "2020-06-22T18:45:14Z",
"lastUpdated": "2020-06-22T18:45:14Z",
"updatedBy": "user id ...<redacted>...",
"policy_type": "dualAuthDelete",
"policy_data": { "enabled": true
}
}
]

 disable the instance dual authorization policy
$ ibmcloud kp instance policy-update dual-auth-delete --disable

Updating instance policy...
OK

 list the instance policies
$ ibmcloud kp instance policies --output json

[
{
"createdBy": "user id ...<redacted>...",
"creationDate": "2020-06-22T18:45:14Z",
"lastUpdated": "2020-06-22T18:51:33Z",
"updatedBy": "user id ...<redacted>...",
"policy_type": "dualAuthDelete",
"policy_data": { "enabled": false
}
}
]





 Example 2 

This example enables the dual authorization delete policy and creates a new key to show how a new key inherits the instance policy.

Disabling the dual authorization policy for an instance does not change the policy for existing keys. The instance policy applies to new keys created after the policy is updated.

 enable the instance dual authorization policy
$ ibmcloud kp instance policy-update dual-auth-delete --enable

Updating instance policy...
OK

 create a new key
$ ibmcloud kp key create my-protected-key

Creating key: 'my-protected-key', in instance: 'a192d603-0b8d-452f-aac3-f9e1f95e7411'...
OK
Key ID Key Name
ibmcloud is snapshot-create --name my-cli-snapshot-crc --source-snapshot-crn crn:v1:staging:public:is:us-south:a/2d1bace7b46e4815a81e52c6ffeba5cf::snapshot:r134-b9590a48-63a3-445e-b819-3f2c0b82daf8

Creating snapshot my-cli-snapshot-crc under account Test Account as user test.user@ibm.com...

ID r142-bd4532c0-e73c-44f9-a017-89e5368c521a
Name my-cli-snapshot-crc
CRN crn:v1:staging:public:is:us-east:a/2d1bace7b46e4815a81e52c6ffeba5cf::snapshot:r142-bd4532c0-e73c-44f9-a017-89e5368c521a
Status pending
Clones Zone Available Created

Source volume ID Name Remote Region
r134-be21061a-4dc6-4c9f-b17d-421838fde399 -remote-421838fde399 us-south

Snapshot Copies ID Name Remote Region CRN Resource type

Bootable true
Encryption provider_managed
Encryption key -
Source Snapshot ID Name Remote Region CRN Resource type
r134-b9590a48-63a3-445e-b819-3f2c0b82daf8 cli-snap-crc-test-sn us-south crn:v1:staging:public:is:us-south:a/2d1bace7b46e4815a81e52c6ffeba5cf::snapshot:r134-b9590a48-63a3-445e-b819-3f2c0b82daf8 snapshot
create a private service instance
$ ibmcloud resource service-instance-create <service-name> kms tiered-pricing us-south -p '{"allowed_network": "private-only"}'
Creating service instance <service-name> in resource group Default of account <account name> as <email address>...
OK
Service instance <service-name> was created.

Name: <service-name>
ID: crn:v1:bluemix:public:kms:us-south:a/ea988d3289c24739a0977651b46fb145:a152eee4-262e-4a39-ae13-a71b9882dcb6::
GUID: a152eee4-262e-4a39-ae13-a71b9882dcb6
Location: us-south
State: active
Type: service_instance
Sub Type: kms
Allow Cleanup: false
Locked: false
Created at: 2020-05-31T15:10:23Z
Updated at: 2020-05-31T15:10:23Z
Last Operation:
Status create succeeded
Message Completed create instance operation

 list the service instances
$ ibmcloud resource service-instances
Retrieving instances with type service_instance in resource group Default in all locations under account <account name> as <email address>...
OK
Name Location State Type
<service-name> us-south active service_instance

 list the private service instance
$ ibmcloud resource service-instance <service-name>
Retrieving service instance <service-name> in resource group Default under account <account name> as <email address>...
OK

Name: <service-name>
ID: crn:v1:bluemix:public:kms:us-south:a/ea988d3289c24739a0977651b46fb145:a152eee4-262e-4a39-ae13-a71b9882dcb6::
* Creating backup 5daa073c-2dd0-0a41-8274-a1ba1ee0d693/20081029151602

* Adjusting backup type (full)

* Backup storage: receiving backup file

* Preparing for backup operation

* Backing up private area

100% 

* Sending private backup data

* Backup storage: storing private backup data

* Backup storage: filling resultant backup info

* Operation backup_env with the Env(s) vz201.domain.com is finished successfully

.

Backup operation for node 'virtuozzo01.softlayer.local' was finished successfully.
Show more



Two things to note about the preceding command:



1. You must log in and run the backup command on the “destination” server (the server that you want the backup to be on). After you run the command, a request for the container ID from the original hardware node is made.
2. The option -e is used to designate a single container. Without this option, the command backs up all containers on the host server to the new location.

[root@virtuozzo00 vz] vzabackup virtuozzo01.softlayer.local

Operation backup_env with the Env(s) vz201.domain.com,VZTest01.softlayer.local is started



You can view the backups that are made and stored on the server by using the following command:

[root@virtuozzo00 vz] vzarestore --list --full

Show existing backups...

CTID: 100

Title: migrateme

Type: full

BackupID: ab8743f4-d436-3a44-b35d-090f2bd2ea35/20081023173802

Description: This is the initial full backup of migrateme on virtuozzo00.

Parent environment: virtuozzo00.softlayer.local

Size: 97.78 Mb

Creation date: 2008-10-23T123802-005

CTID: 101
"created_by": "IBMid-xxxxxQExx",
"crn": "crn:v1:staging:public:apprapp:us-south:a/abcdf222595g44d598c178525i60jc77:f4fca3f2-fdd3-485e-b86c-1234dd3eabc4::",
"guid": "a4bcc3f2-dee3-485f-a86b-4818dd3eabc4",
"last_operation": {
"description": "Completed create instance operation",
"state": "succeeded",
"type": "create"
},
"name": "App Configuration-z0",
"region_id": "us-south",
"resource_group_id": "ee24533eed37412e988179fe694062bc",
"resource_id": "apprapp-a6bcce47-d840-45b0-8ab9-ad15354defgea",
"state": "active",
"type": "service_instance",
"updated_at": "2022-09-30T16:18:55.295780335Z"
},
"event_type": "resource-controller.instance.create",
"timestamp": "2022-09-30T16:18:55Z"
}
Show more
ibmcloud cbr zone-create --addresses 129.XX.XX.XX --description "Allow only client IP" --name allow-client-ip
2. Verify the network zone was created.

ibmcloud cbr zones







 Step 2: Creating your CBR rule 



1. After you create your network zone (allowlist), create a CBR rule and add the network zone you created in the previous step. The following example creates a rule that uses the cluster API type. Replace NETWORK-ZONE-ID with the ID of the allow-client-ip network zone that you created in step 1.

ibmcloud cbr rule-create --api-types crn:v1:bluemix:public:containers-kubernetes::::api-type:cluster --description "privateAccess=allowAll, publicAccess=oneIP" --service-name containers-kubernetes --service-instance CLUSTER-ID --context-attributes endpointType=private --context-attributes endpointType=public,networkZoneId=NETWORK-ZONE-ID

Understanding the command options.

--api-types crn:v1:bluemix:public:containers-kubernetes::::api-type:cluster
: Set the crn:v1:bluemix:public:containers-kubernetes::::api-type:cluster API to allow only resources in the network zone you created earlier to access only the cluster APIs, which include the APIs for various oc commands.

--service-instance CLUSTER-ID
: Scope the rule to a single cluster so that only resources in the network zone you created earlier can access only the CLUSTER-ID.

--context-attributes endpointType=private
: Set the context attribute endpointType=private without associating a network zone allows all private traffic to the cluster.

--context-attributes endpointType=public,networkZoneId=all-client-ip
: Set the context attribute endpointType=public and associate the networkZoneId=allow-client-ip that you created earlier to allow only the resources in the allow-client-ip zone to access the cluster over the public network.
> "name": "my-policy-plan-c"
> }]'
Show more

The result shows that two plans were created.

Creating backup policy backup-policy-v1 under account Test Account as user test.user@ibm.com...

ID r138-0521986d-963c-4c18-992d-d6a7a99d115f
Name backup-policy-v1
CRN crn:v1:bluemix:public:is:eu-de:a/a10d63fa66daffc9b9b5286ce1533080::backup-policy:r138-0521986d-963c-4c18-992d-d6a7a99d115f
Status pending
Plans ID Name Resource type
r138-2129a79a-5629-4069-bf79-7bb0af3b0bd3 my-policy-plan-a backup_policy_plan
r138-6f4f08ba-e0bb-470f-bbfb-f3a22aebbfa9 my-policy-plan-c backup_policy_plan

Backup tags dev:test
Backup resource type volume
Resource group defaults
Created at 2023-02-21T22:42:10+00:00

For more information about available command options, see [ibmcloud is backup-policy-create](https://cloud.ibm.com/docs/cli?topic=cli-vpc-referencebackup-policy-create).





 Creating a backup plan from the CLI 

Run the backup-policy-plan-create command to create a backup plan and attach it to an existing policy. Identify the policy by ID or name.

Syntax:
If you don't use multipath aliases, replace the line (starting with devices=$() that is used to identify devices. Instead, use following line: devices=$(multipath -ll | grep -B 1 $pv_size | grep dm- | awk '{print "/dev/"$2}' | tr 'n' ' ')





 Creating file systems by using ansible automation 



1. To create file systems by using ansible automation, download the ibm.power_linux_sap ansible-galaxy collection.

ansible-galaxy collection install ibm.power_linux_sap

Ansible role, powervs_fs_creation is used to create filesystem for SAP HANA, SAP NetWeaver or for SAP shared file systems instance. This role performs the following tasks:



* Creates file systems with user-defined stripe size by using ansible built-in LVM logical volumes modules.
* Mounts the file systems on provided mount points
* Adds an entry to /etc/fstab for automount on reboot.



2. To run this role, you can pass two types of variables. The first as a dictionary and other as a list. See the following example.



* Example A. Data structure for disks_configuration as dictionary value example:

disks_configuration:
{
counts: [2,2,1],
names: [data,log,shared],
paths: [/hana/data,/hana/log,/hana/shared],
wwns: [600507681082018bc8000000000057e4,600507681082018bc8000000000057e8,600507681082018bc8000000000057e5,600507681082018bc8000000000057e6, 600507681082018bc8000000000057e7]
}
* Example B. Data structure for disks_configuration as list value example:

disks_configuration: [
{
name: data,
path: /hana/data,
ibmcloud cbr zone-create --addresses 129.XX.XX.XX --description "Allow only client IP" --name allow-client-ip
2. Verify the network zone was created.

ibmcloud cbr zones







 Step 2: Creating your CBR rule 



1. After you create your network zone (allowlist), create a CBR rule and add the network zone you created in the previous step. The following example creates a rule that uses the cluster API type. Replace NETWORK-ZONE-ID with the ID of the allow-client-ip network zone that you created in step 1.

ibmcloud cbr rule-create --api-types crn:v1:bluemix:public:containers-kubernetes::::api-type:cluster --description "privateAccess=allowAll, publicAccess=oneIP" --service-name containers-kubernetes --service-instance CLUSTER-ID --context-attributes endpointType=private --context-attributes endpointType=public,networkZoneId=NETWORK-ZONE-ID

Understanding the command options.

--api-types crn:v1:bluemix:public:containers-kubernetes::::api-type:cluster
: Set the crn:v1:bluemix:public:containers-kubernetes::::api-type:cluster API to allow only resources in the network zone you created earlier to access only the cluster APIs, which include the APIs for various kubectl commands.

--service-instance CLUSTER-ID
: Scope the rule to a single cluster so that only resources in the network zone you created earlier can access only the CLUSTER-ID.

--context-attributes endpointType=private
: Set the context attribute endpointType=private without associating a network zone allows all private traffic to the cluster.

--context-attributes endpointType=public,networkZoneId=all-client-ip
: Set the context attribute endpointType=public and associate the networkZoneId=allow-client-ip that you created earlier to allow only the resources in the allow-client-ip zone to access the cluster over the public network.
"env:test",
"env:prod"
]
}
}'

A successful response indicates that the clone was created in the specified zone.

{
"bootable": true,
"clones": [
{
"available": false,
"created_at": "2022-12-18T14:58:32Z",
"zone": {
"name": "us-south-2",
"href": "https:ibm.com/v1/regions/us-south/zones/us-south-1",
"resource_type": "zone"
}
}
],
"created_at": "2022-12-18T20:18:18Z",
"crn": "crn:[...]",
"deletable": false,
"encryption": "user_managed",
"encryption_key": {
"crn": "crn:[...]"
},
"href": "https://us-south.iaas.cloud.ibm.com/v1/snapshots/12917904-3771-424d-8391-53ec9e305d52",
"id": "12917904-3771-424d-8391-53ec9e305d52",
"lifecycle_state": "pending",
}





 Creating a cross-regional copy of a snapshot with the API 

New

When you create a snapshot, you can also copy the snapshot to another region. By creating a snapshot copy in another region and create new instances with the help of that snapshot, you can expand your VPC to a different region. This feature can be used in disaster recovery scenarios, as well.
The enable event indicates the key has been restored (and is now enabled) and the key can be used for encrypt and decrypt operations, such as wrap, unwrap, and rewrap.

ibmcloud kp key enable KEY_ID
-i, --instance-id INSTANCE_ID



 Examples 

This is an example of kp key enable.

 create a root key
$ ibmcloud kp key create my-root-key --output json

{
"id": "264fadc3-7667-4b25-916e-5825fe70de0b",
"name": "my-root-key",
"type": "application/vnd.ibm.kms.key+json",
"extractable": false,
"state": 1,
"crn": "crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:390086ac-76fa-4094-8cf3-c0829bd69526:key:264fadc3-7667-4b25-916e-5825fe70de0b"
}

 show key details - a state of "1" is "active"
$ ibmcloud kp key show 264fadc3-7667-4b25-916e-5825fe70de0b --output json

{
"id": "264fadc3-7667-4b25-916e-5825fe70de0b",
"name": "my-root-key",
"type": "application/vnd.ibm.kms.key+json",
"algorithmType": "AES",
"createdBy": "user id ...<redacted>...",
"creationDate": "2020-06-09T21:21:55Z",
[carousel thumbnail](https://cloud.ibm.com/docs-content/v1/content/dl//images/thumbnail.png)<br><br>IBM Cloud Direct Link for hybrid cloud](https://cloud.ibm.com/docs/dl?topic=dl-offering-video)

 Learn more 

[IBM Developer<br><br>Visit IBM Developer for technical articles, code patterns, tutorials, and more.<br><br>![112-Developer-tools.svg](https://cloud.ibm.com/media/docs/images/homepage/112-Developer-tools.svg)](https://developer.ibm.com/depmodels/cloud/)[Architecture Center<br><br>Discover the architecture references available for this product.<br><br>![190-Application-Platform.svg](https://cloud.ibm.com/media/docs/images/homepage/190-Application-Platform.svg)](https://www.ibm.com/cloud/architecture)[IBM Training<br><br>Build your skills with IBM Cloud training.<br><br>![83-Elements-of-the-cloud.svg](https://cloud.ibm.com/media/docs/images/homepage/83-Elements-of-the-cloud.svg)](https://www.ibm.com/training/cloud)[Community<br><br>Join the IBM Cloud community and collaborate with others.<br><br>![35-Connectivity.svg](https://cloud.ibm.com/media/docs/images/homepage/35-Connectivity.svg)](https://community.ibm.com/community/user/publiccloud/search?executeSearch=true&SearchTerm=direct%20link&rf=%5EMulti04%3Adirect%5E)

 Latest updates
Learn more 

[IBM Developer<br><br>Visit IBM Developer for technical articles, code patterns, tutorials, and more.<br><br>![112-Developer-tools.svg](https://cloud.ibm.com/media/docs/images/homepage/112-Developer-tools.svg)](https://developer.ibm.com/depmodels/cloud/gettingstarted/)[Architecture Center<br><br>Discover the architecture references available for this product.<br><br>![190-Application-Platform.svg](https://cloud.ibm.com/media/docs/images/homepage/190-Application-Platform.svg)](https://www.ibm.com/cloud/architecture/architectures/public-cloud)[IBM Training<br><br>Build your skills with IBM Cloud training.<br><br>![83-Elements-of-the-cloud.svg](https://cloud.ibm.com/media/docs/images/homepage/83-Elements-of-the-cloud.svg)](https://www.ibm.com/training/cloud)[Community<br><br>Join the IBM Cloud community and collaborate with others.<br><br>![35-Connectivity.svg](https://cloud.ibm.com/media/docs/images/homepage/35-Connectivity.svg)](https://community.ibm.com/community/user/cloud/home)

 Latest updates 

[View more](https://cloud.ibm.com/docs/overview?topic=overview-whatsnew)03 April 2023 | Customize your private catalog and private products

You can enhance the appearance of your private catalog to match your brand by adding a custom banner image to your private catalogs. You can also make it easier for users to search for your products added to a private catalog by specifying a custom provider name. Adding a custom provider name for your private products can help users find them quickly by using the Provider filter in the catalog.
Why use the architecture framework? 

Designing a cloud solution by using the architecture framework enables a more consistent approach to solutioning across the breadth of your cloud portfolio, which in turn decreases the solution process time and delivery risks.

Using the architecture framework also provides the structure to create reusable, repeatable solution architecture references and guidance which leads to the standardization of enterprise cloud solution design and the avoidance of one-of-a-kind snowflake solutions that are expensive to deploy, enhance, and maintain.

The architecture framework can be used as a guide to ensure you have considered applicable requirements for each "aspect" and "domain". After you have identified the applicable requirements, you can evaluate and select the best fit for purpose components for your enterprise cloud solution.
Using environment variables with workspaces 

Terraform uses environment variables to customize aspects of its behavior. Environment variables are used to increase the output verbosity for debugging or to set rarely used runtime parameters.

For example, parallelism is one of the environment variable with a number flag range between 1 and 256, the default value is 10. Parallelism is used to configure infrastructure providers that error on concurrent operations or use during non-standard rate limiting, when you execute terraform plan and terraform apply at runtime.

Environment variables can only be set using the workspace update API and the CLI passing a JSON file. See the [Workspace update CLI command](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-update) for more details.



 Usage 



 Passing TF_CLI_ARGS as env-vars 

You can pass Terraform command-line arguments TF_CLI_ARGS as environment variables, like TF_CLI_ARGS_plan, and TF_CLI_ARGS_apply in the Schematics Workspaces to customize operations.

Terraform reads these environment variables and applies them runtime. For more information about Terraform command-line arguments, see [TF_CLI_ARGS and TF_CLI_ARGS_name](https://developer.hashicorp.com/terraform/cli/config/environment-variablestf_cli_args-and-tf_cli_args_name).





 Example setting parallelism or TF_LOGS 

The examples shown here can be used to set any environment variable to be passed to Terraform.



 Setting parallelism at create time 

The code block is the sample payload for creating workspace with the Schematics [Create API](https://cloud.ibm.com/apidocs/schematics/schematicscreate-workspace) with parallelism passed as an environment variable.

{
"name": "bb",
"type": [
"terraform_v1.0"
],
129.42.0.101 – 129.42.0.3 (VPS1)
129.42.0.102 – 129.42.0.3 (VPS1)
129.42.0.103 – 129.42.0.3 (VPS1)

In summary, this scenario used a portable subnet to make IP addresses available to all virtual machine hosts, and then made additional IP addresses available to a virtual machine by using a static subnet. You can use addresses out of the original portable subnet, or add another portable subnet. This scenario illustrates that not only is it OK to route static subnets to IP addresses on portable subnets, but it is efficient and useful to do so.
Using environment variables with blueprints 

Environment variables are used to modify the behavior and execution of Terraform and Ansible without modifying the IaC code itself. They are set independently of the IaC code and environment inputs. Terraform uses environment variables to customize several aspects of its behavior. For example environment variables are used to increase the output verbosity for debugging or to set rarely used runtime options.

Refer to the section [Using environment variables with workspaces](https://cloud.ibm.com/docs/schematics?topic=schematics-set-parallelism) for more information about the environment variables that can be passed to configure Terraform runtime behavior in Schematics.



  Blueprints usage 

When using Blueprints, environment variables to modify Terraform and Ansible execution are configured using the settings parameters in the blueprint YAML template. Refer to the [Blueprint template YAML schema](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-template-schema-yamlbp-settings) specification for details on setting env-vars at the global blueprint level or the module level.
* A service IP address that is tied to DNS, so you can avoid DNS caching delays when shifting workloads to new servers; in other words, the service IP won't change simply because a server's primary IP address does
* High availability configurations, which use floating IP address protocols



IBM offers different routing options for secondary subnets. To help illustrate the differences between these routing options, the following example is referenced in further explanations.

Available IP addresses provided by the subnet 10.0.0.0/29:

10.0.0.0
10.0.0.1
10.0.0.2
10.0.0.3
10.0.0.4
10.0.0.5
10.0.0.6
10.0.0.7





 Static subnets 

A secondary static subnet provides a single destination with access to all IP addresses defined by that subnet. One benefit of using a static subnet is that the destination device is able to use all IP addresses defined; not suffering the usual network, gateway, and broadcast address usage penalty. So, using the example subnet 10.0.0.0/29, all addresses are usable:

10.0.0.0 - Usable by device
10.0.0.1 - Usable by device
10.0.0.2 - Usable by device
10.0.0.3 - Usable by device
10.0.0.4 - Usable by device
10.0.0.5 - Usable by device
10.0.0.6 - Usable by device
10.0.0.7 - Usable by device

As a result, if a server has the IP address 10.0.0.13, and you routed 10.0.0.0/29 statically to 10.0.0.13, that server can now bind eight more IP addresses, receiving traffic on each individually. Note that Network Address Translation (NAT) is not done for any of the addresses provided. Each address can be used natively on servers, and so can be used for discrete purposes.

The following IP addresses are eligible as route targets for static subnets within the same data center: