vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Getting started with the Power Edge Router 

A Power Edge Router (PER) is a high-performance router that provides advanced routing capabilities for IBM® Power® Systems Virtual Server users.

PER improves network communication across different parts of IBM network. The PER solution creates a direct connection to the IBM Cloud MPLS (Multi Protocol Label Switching) backbone, making it easy for different parts of the IBM network to communicate with each other. The PER solution is comprised of two routers that enable an aggregate connectivity of 400 Gbps to each Power Systems Virtual Server POD (acronym for Performance Optimized Datacenter that are modular datacenters).

The PER solution is currently available in DAL10. PER will be deployed in other datacenters over time.

PER associates specific Power Systems Virtual Server networks with unique MPLS route distinguishers (RDs). This makes it easy for different networks to communicate with each other across the IBM Cloud MPLS backbone.

To facilitate communication between Power Systems Virtual Server instances and other parts of the network, such as [Classic infrastructure](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-getting-started-tutorial), [Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started), and remote Power Systems Virtual Server instances, [Transit Gateway](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-getting-started&interface=ui) is used.

One of the benefits of the PER solution is that it makes it easier for a Power Systems Virtual Server user to access other IBM Cloud services, such as IBM Cloud DNS, NTP, and Cloud Object Storage. You can connect to these services without having to use proxies or virtual routers, as the PER solution includes a Network Address Translation (NAT) device that simplifies the access process.

The following network architecture diagram explains how the PER is integrated into the IBM Cloud environment:

Zoom

!
The pipeline runs a number of dynamic scans, and it is recommended to use your staging environment. IBM Cloud API key: The API key that you created and used during your CI toolchain setup. Optionally you can create a new key and store it in your preferred choice of secrets vault. Environment tag in your inventory: It is the [tag in your Inventory repository that reflects the state of your current deployed environment. This tag is the snapshot of current running application on target.

Zoom

![DevSecOps CC target definition](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/devsecops-cc-toolchain-setup-specify-target.png)

Figure 6. DevSecOps CC target definition





 Issues 

The Git Repos and Issue Tracking repository records incident issues that are found while the CC pipeline is running.

Zoom

![DevSecOps incident issues repository](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/devsecops-cc-toolchain-setup-issues-repo.png)

Figure 7. DevSecOps incident issues repository





 Pipeline configuration 

The toolchain comes with an integrated Tekton pipeline to automate continuous compliance scans of the deployed artifacts and source application repositories. This repository contains Tekton resources that are defined in YAML files that run the pipeline tasks. These repositories can be contributed to or can be forked although it is highly recommended to use the default repository provided by this step.

Zoom

!
Event fields 

IBM Cloud Activity Tracker events are based on the Cloud Auditing Data Federation (CADF) standard.

The CADF standard defines a full event model that includes the information that is needed to certify, manage, and audit security of applications in cloud environments.

The CADF event model includes the following components:



Table 1. Components that are available in a CADF event model

 Component Description 

 Action The action is the operation or activity that an initiator performs, attempts to perform, or is waiting to complete. 
 Initiator The initiator is the resource that makes an API call and generates a CADF event. The event that is triggered depends on the action that is requested by the API call. 
 Observer The observer is the resource that creates and stores a CADF record from information available in a CADF event. 
 Outcome The outcome is the status of the action against the target. 
 Target The target is the resource against which the action is performed, attempted to perform, or is pending to complete. 



The following fields are included in each Activity Tracker event:



 action (string) 

This field indicates the action that triggers an event.

The format of this field is the following:

serviceName.objectType.action

Where



* servicename is the name of the service.

There is an exception on the servicename that is set for actions reported by the VPC infrastructure. The format of the servicename is composed of 2 parts that are separated by a dot (.).
* objectType describes the resource or resource attribute on which the action is requested.
* action defines the task requested by the initiator.
stringEqualsAnyOf Case-sensitive exact string matching any of the strings in an array of strings. 
 stringMatchAnyOf Case-sensitive string matching any of the strings in an array of strings. The values can include a multi-character wildcard (), which matches any sequence of zero or more characters, a single-character wildcard (?), matching any single character, or both. You can also express an asterisk * and question mark ? as a literal value by enclosing each within two sets of curly brackets {{}}. 







 Step 7: Set the license requirements 

If users are required to accept any license agreements beyond the IBM Cloud Services Agreement, provide the URL to each agreement. Or, if users can bring their own licenses, you can provide that URL as well.



1. Click Add license agreements > Add.
2. Enter the name and URL, and click Update.
3. After you enter the additional license agreements, click Next.







 Step 8: Validate the Terraform template 



1. From the Validate product tab, enter the name of your 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 template. This tag is put on the IBM Cloud Schematics workspace. Tags provide a way to organize, track usage costs, and manage access to the resources in your account.
2. From the Deployment values section, review your parameter values, and click Next.
3. In the Validation product section, select I have read and agree to the following license agreements.
4. Click Validate.

To monitor the progress of the validation process, click View logs.







 Step 9: Manage compliance 

Controls are safeguards that are used to meet security and compliance requirements. Only controls that are supported by Security and Compliance Center, formatted correctly, and validated by Code Risk Analysis and Security and Compliance Center scans appear in the catalog. For more information, see [Adding compliance details](https://cloud.ibm.com/docs/account?topic=account-catalog-format-controls).



 Manage compliance controls
For example, see the [naming conventions for Snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-manage&interface=uisnapshots-vpc-naming). 
 <br><br> * Resource group<br><br><br> Optionally, specify a resource group for your policy. It can't be changed after you enter it. <br>For more information, see [best practices for organizing resources in a resource group](https://cloud.ibm.com/docs/account?topic=account-account_setup). 
 <br><br> * Tags<br><br><br> Add user tags that you want to apply to this policy. This tag must match a Block Storage for VPC volume tag. 
 <br><br> * Access management tags<br><br><br> Access management tags are used to manage access to resources, and they can be created in advance for use in access policies. Access policies control access to the resources where the tags are attached. Only the account administrator can create access management tag. 
 Tags for target resources Specify the user tags to apply to your target resources (Block Storage for VPC volumes) in your region. If multiple resources use the same tag, backups are created for all tagged resources. If a resource has multiple tags, it needs to match only one tag that is associated with the backup policy. After the backup policy is created, existing resources with any of the tags for target resources are automatically associated. 
 Plan Click Create to create backup plans for this policy. In the side panel, specify the plan details. When finished, click Create. The page refreshes with a summary of the plan details. You can create up to four backup plans. All apply to the volumes with tags that match the backup policy. <br>For more information about options, see [Specify a backup plan](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-planbackup-plan-ui). 



3.
* How does IBM handle maintenance?

For more information, see [Understanding Cloud Maintenance Operations](https://cloud.ibm.com/docs/vpc?topic=vpc-about-cloud-maintenance).
* What happens if my virtual server host fails?

For more information, see [Understanding Cloud Maintenance Operations](https://cloud.ibm.com/docs/vpc?topic=vpc-about-cloud-maintenance).
* What are the disks that I see associated with my new Windows virtual server instance?

When you provision a Windows virtual server instance with a stock image, disk manager might show unexpected disks. After a new Windows instance is provisioned from a stock image, a cloud-init disk and a swap disk are present. The cloud-init disk might display a size of 378 KB. The swap disk might display a size of 44 KB; the swap disk is turned off eventually. These small disks are working as designed. You are not to attempt to delete or format either of these disks that are associated with your new Windows virtual server instance.
* What is image from volume and how does it relate to virtual server instances?

You can create a custom image from a boot volume that is attached to a virtual server instance. Then, you can use the custom image to provision new virtual server instances. For more information, see [About creating an image from a volume](https://cloud.ibm.com/docs/vpc?topic=vpc-image-from-volume-vpc).
* What is the virtual server instance identifier and SMBIOS system-uuid?

The virtual server instance is automatically assigned an instance identifier (ID), which includes the SMBIOS system-uuid as a portion of the ID, when the instance is created. IDs are immutable, globally unique, and never reused, so the ID uniquely identifies a particular instantiation of a virtual server instance across all of IBM Cloud. The ID, including the SMBIOS system-uuid portion, is static and persists for the lifecycle of the virtual server instance until that virtual server instance is deleted.
You must enable virtual routing and forwarding (VRF) and connectivity to service endpoints for your account. [Learn more](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint)





 Step 4. Deploy the logging agent in the cluster 

Create a Kubernetes daemonset to deploy the logging agent on every worker node of your Kubernetes cluster.

The logging agent collects the following logs:



* STDOUT and STDERR
* Logs with the extension .log, and extensionsless files that are stored in the /var/log directory of your pod.



By default, logs are collected from all namespaces, including kube-system, and automatically forwarded to the IBM Log Analysis service.



 Logging agent V2 and V3 

The logging agent version 2 and version 3 are supported for Red Hat OpenShift (version 4.5 or later).

To configure the logging agent by using kubectl commands, run the following command:



Table 1. Commands by endpoint type

 Type of endpoint Command 

 Public endpoint kubectl apply -f https://assets.<REGION>.logging.cloud.ibm.com/clients/logdna-agent/<VERSION>/agent-resources-openshift.yaml 
 Private endpoint kubectl apply -f https://assets.<REGION>.logging.cloud.ibm.com/clients/logdna-agent/<VERSION>/agent-resources-openshift-private.yaml 



Where



* <REGION> indicates the region where the logging instance is available. For more information about regions, see [Locations](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-regions).
* <VERSION> indicates the version of the agent that you want to deploy. You must use a version that has a tag with the following format: X.Y.Z.



If you need to use a version that has a tag with any of the following formats: X.Y.Z-<date>.
{object data} | openssl dgst -md5 -binary | openssl enc -base64

After running the multipart-upload-complete command, run part-upload for each file part you want to upload. For multipart uploads, every file part (except for the last part) must be at least 5 MB. To split a file into separate parts, you can run split in a terminal window. For example, if you have a 13 MB file that is named TESTFILE on your Desktop, and you would like to split it into file parts of 5 MB each, you can run split -b 3m /Desktop/TESTFILE part-file-. This command generates three file parts into two file parts of 5 MB each, and one file part of 3 MB, with the names part-file-aa, part-file-ab, and part-file-ac.

As each file part is uploaded, the CLI print its ETag. You must save this ETag into a formatted JSON file, along with the part number. Use this template to create your own ETag JSON data file.

{
"Parts": [
{
"PartNumber": 1,
"ETag": "The ETag of the first file part goes here."
},
{
"PartNumber": 2,
"ETag": "The ETag of the second file part goes here."
}
]
}

Add more entries to this JSON template as necessary.

To see the status of your multipart upload instance, you can always run the part-list command, providing the bucket name, key, and the upload ID. This print raw information about your multipart upload instance. Once you have completed uploading each part of the file, run the multipart-upload-complete command with the necessary parameters. If all goes well, you receive a confirmation that the file uploaded successfully to the wanted bucket.



 Upload a part 



* Action: Upload a part of a file in an existing multipart upload instance.
For example, see the [naming conventions for Snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-manage&interface=uisnapshots-vpc-naming). 
 <br><br> * Resource group<br><br><br> Optionally, specify a resource group for your policy. It can't be changed after you enter it. <br>For more information, see [best practices for organizing resources in a resource group](https://cloud.ibm.com/docs/account?topic=account-account_setup). 
 <br><br> * Tags<br><br><br> Add user tags that you want to apply to this policy. This tag must match a Block Storage for VPC volume tag. 
 <br><br> * Access management tags<br><br><br> Access management tags are used to manage access to resources, and they can be created in advance for use in access policies. Access policies control access to the resources where the tags are attached. Only the account administrator can create access management tag. 
 Tags for target resources Specify the user tags to apply to your target resources (Block Storage for VPC volumes) in your region. If multiple resources use the same tag, backups are created for all tagged resources. If a resource has multiple tags, it needs to match only one tag that is associated with the backup policy. After the backup policy is created, existing resources with any of the tags for target resources are automatically associated. 
 Plan Click Create to create backup plans for this policy. In the side panel, specify the plan details. When finished, click Create. The page refreshes with a summary of the plan details. You can create up to four backup plans. All apply to the volumes with tags that match the backup policy. <br>For more information about options, see [Specify a backup plan](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan&interface=clibackup-plan-ui). 



3.
For example, see the [naming conventions for Snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-manage&interface=uisnapshots-vpc-naming). 
 <br><br> * Resource group<br><br><br> Optionally, specify a resource group for your policy. It can't be changed after you enter it. <br>For more information, see [best practices for organizing resources in a resource group](https://cloud.ibm.com/docs/account?topic=account-account_setup). 
 <br><br> * Tags<br><br><br> Add user tags that you want to apply to this policy. This tag must match a Block Storage for VPC volume tag. 
 <br><br> * Access management tags<br><br><br> Access management tags are used to manage access to resources, and they can be created in advance for use in access policies. Access policies control access to the resources where the tags are attached. Only the account administrator can create access management tag. 
 Tags for target resources Specify the user tags to apply to your target resources (Block Storage for VPC volumes) in your region. If multiple resources use the same tag, backups are created for all tagged resources. If a resource has multiple tags, it needs to match only one tag that is associated with the backup policy. After the backup policy is created, existing resources with any of the tags for target resources are automatically associated. 
 Plan Click Create to create backup plans for this policy. In the side panel, specify the plan details. When finished, click Create. The page refreshes with a summary of the plan details. You can create up to four backup plans. All apply to the volumes with tags that match the backup policy. <br>For more information about options, see [Specify a backup plan](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan&interface=terraformbackup-plan-ui). 



3.
For example, see the [naming conventions for Snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-manage&interface=uisnapshots-vpc-naming). 
 <br><br> * Resource group<br><br><br> Optionally, specify a resource group for your policy. It can't be changed after you enter it. <br>For more information, see [best practices for organizing resources in a resource group](https://cloud.ibm.com/docs/account?topic=account-account_setup). 
 <br><br> * Tags<br><br><br> Add user tags that you want to apply to this policy. This tag must match a Block Storage for VPC volume tag. 
 <br><br> * Access management tags<br><br><br> Access management tags are used to manage access to resources, and they can be created in advance for use in access policies. Access policies control access to the resources where the tags are attached. Only the account administrator can create access management tag. 
 Tags for target resources Specify the user tags to apply to your target resources (Block Storage for VPC volumes) in your region. If multiple resources use the same tag, backups are created for all tagged resources. If a resource has multiple tags, it needs to match only one tag that is associated with the backup policy. After the backup policy is created, existing resources with any of the tags for target resources are automatically associated. 
 Plan Click Create to create backup plans for this policy. In the side panel, specify the plan details. When finished, click Create. The page refreshes with a summary of the plan details. You can create up to four backup plans. All apply to the volumes with tags that match the backup policy. <br>For more information about options, see [Specify a backup plan](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan&interface=apibackup-plan-ui). 



3.
For example, see the [naming conventions for Snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-manage&interface=uisnapshots-vpc-naming). 
 <br><br> * Resource group<br><br><br> Optionally, specify a resource group for your policy. It can't be changed after you enter it. <br>For more information, see [best practices for organizing resources in a resource group](https://cloud.ibm.com/docs/account?topic=account-account_setup). 
 <br><br> * Tags<br><br><br> Add user tags that you want to apply to this policy. This tag must match a Block Storage for VPC volume tag. 
 <br><br> * Access management tags<br><br><br> Access management tags are used to manage access to resources, and they can be created in advance for use in access policies. Access policies control access to the resources where the tags are attached. Only the account administrator can create access management tag. 
 Tags for target resources Specify the user tags to apply to your target resources (Block Storage for VPC volumes) in your region. If multiple resources use the same tag, backups are created for all tagged resources. If a resource has multiple tags, it needs to match only one tag that is associated with the backup policy. After the backup policy is created, existing resources with any of the tags for target resources are automatically associated. 
 Plan Click Create to create backup plans for this policy. In the side panel, specify the plan details. When finished, click Create. The page refreshes with a summary of the plan details. You can create up to four backup plans. All apply to the volumes with tags that match the backup policy. <br>For more information about options, see [Specify a backup plan](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan&interface=uibackup-plan-ui). 



3.
To display the current signature threshold values, run the ibmcloud tke cryptounit-thrhlds command.





 Step 4: Create a set of master key parts to use 

Each master key part is saved in a password-protected file on the workstation.

You must create at least two master key parts. For security considerations, a maximum of three master key parts can be used and each key part can be owned by a different person. The key part owner needs to be the only person who knows the password that is associated with the key part file.



* To display the existing master key parts on the workstation, use the following command:

ibmcloud tke mks
* To create and save a random master key part on the workstation, use the command:

ibmcloud tke mk-add --random

When prompted, enter a description for the key part and a password to protect the key part file. You must remember the password. If the password is lost, you can't use the key part.
* To enter a known key part value and save it in a file on the workstation, use the following command:

ibmcloud tke mk-add --value

When prompted, enter the key part value as a hexadecimal string for the 32-byte key part. And then enter a description for the key part and a password to protect the key part file.







 Step 5: Load the new master key register 

To load a master key register, all master key part files and signature key files to be used must be present on a common workstation. If the files were created on separate workstations, make sure that the file names are different to avoid collision. The master key part file owners and the signature key file owners need to enter the file passwords when the master key register is loaded on the common workstation.

For information about how the master key is loaded, see the detailed illustrations at [Master key registers](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-introduce-serviceunderstand-key-ceremony).

To load the new master key register, use the following command:

ibmcloud tke cryptounit-mk-load