vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Creating an image template 

With image templates, you can replicate various configuration options for Virtual Servers.

At any point during the life of a virtual server, you can create an image template. Then, you can use it to quickly replicate portions of its configuration in another virtual server. You can create image templates from any virtual server, regardless of its operating system. When your image template is complete, you can use it to create another virtual server.

ISO images of licensed operating systems, such as Windows and Red Hat Enterprise Linux, and open source operating systems, such as CentOS and Ubuntu, are not provided by IBM. If you need these ISO images, you can download them from the respective vendor website.



 Before you begin 

First, go to the device menu and make sure that you have the correct account permissions to complete the tasks.



* Go to your console's device menu. For more information, see [Navigating to devices](https://cloud.ibm.com/docs/image-templates?topic=virtual-servers-navigating-devices).
* Make sure that you have any necessary account permissions and device access. Only the account owner, or a user with the Manage Users classic infrastructure permission, can adjust the permissions.



For more information about permissions, see [Classic infrastructure permissions](https://cloud.ibm.com/docs/account?topic=account-infrapermissioninfrapermission) and [Managing device access](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-device-access).





 Creating an image template 

Complete the following steps to create an image template of a virtual server.



1. From the Devices menu, select Device List.
2. Click the virtual server that you want to use to create an image template.

Check the Passwords tab of the Device Details page. Make sure that any passwords that are listed on the Device Details page match the actual operating system passwords and any other software add-on passwords. If passwords don't match, virtual servers that are created from this image template fail.
3. From the Actions menu, select Create Image Template.
Code Engine equivalents to Cloud Foundry commands 

Find and compare the Code Engine CLI command that is equivalent to your Cloud Foundry commands.



 Connect to the deployment API region commands 

Cloud Foundry
: ibmcloud target --cf-api api.us-south.cf.cloud.ibm.com

Code Engine
: ibmcloud target -r [region]





 Create a deployment location for your workload commands 

Cloud Foundry
: ibmcloud cf create-org [orgName]
: ibmcloud target -o [orgName]
: ibmcloud target -s [spaceName]

Code Engine
: ibmcloud ce project create --name [projectName] To create and select a new project.
: ibmcloud ce project select --name [projectName] To select an existing project.

You can also create a project from the [Code Engine console](https://cloud.ibm.com/codeengine/overview).





 List your apps and jobs commands 

Cloud Foundry
: ibmcloud cf apps

Code Engine
: ibmcloud ce app list
: ibmcloud ce job list

You can also view your applications and jobs from the [Code Engine console](https://cloud.ibm.com/codeengine/overview).





 Deploy an image as an app or job commands 

Cloud Foundry
: ibmcloud cf push

Code Engine
: ibmcloud ce build create Define a build.
: ibmcloud ce buildrun submit Run a build.
: ibmcloud ce app create Deploy image as an app.
: ibmcloud ce job create Create a batch job.
: ibmcloud ce app create --build-source . --strategy buildpacks Build your code and deploy the app in a single step.
: ibmcloud ce job create --build-source . --strategy buildpacks Build your code and deploy the job in a single step.

You can perform these tasks from a single web page in the [Code Engine console](https://cloud.ibm.com/codeengine/overview).





 Bind a Service to a workload 

Cloud Foundry
Creating a custom bare metal server image template 

With custom image templates, you can capture an image of a bare metal server to replicate its configuration with minimal changes in the order process. Image templates provide an imaging option for all Bare Metal Servers, regardless of operating system. When your image template is complete, you can use it to create another bare metal server.



 Before you begin 

Make sure that you have the correct account permissions to complete the tasks.



1. Go to the device menu and ensure you have the correct account permissions to complete the tasks.
2. Go to your console's device menu. For more information, see [Navigating to devices](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-navigating-devices).
3. Make sure that you have any necessary account permissions and device access. Only the account owner, or a user with the Manage Users classic infrastructure permission, can adjust the permissions.



For more information about permissions, see [Classic infrastructure permissions](https://cloud.ibm.com/docs/account?topic=account-infrapermission) and [Managing device access](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-device-access).





 Creating an image template 

Use the following steps to capture a bare metal server image.

For tips and best practices about creating an image template, see this [blog post](https://www.ibm.com/cloud/blog/best-practices-for-successfully-creating-custom-images-on-ibm-cloud-bare-metal-servers).



1. Go to your console's device menu and make sure that you have the correct account permissions to complete the tasks.
2. From the Devices menu, select Device List, and click the device that you want to use to create an image template.
3. Click the Actions dropdown and click Create image template. Make sure that the usernames and passwords that are listed match the operating system passwords and any other software add-on passwords.
[Onboarding a virtual server image for Power Systems Virtual Server](https://cloud.ibm.com/docs/account?topic=account-catalog-vsipower-tutorial)Onboarding a virtual server image for Power Systems Virtual Server

This tutorial walks you through how to onboard a sample virtual server image for Power Systems Virtual Server to your account. By completing this tutorial, you learn how to create a private catalog, import the sample, validate that it can be installed on a selected deployment target, and make the virtual server image available to users who have access to your account.

Object Storage Virtual Private Cloud (VPC)

+1

Managing your account, resources, and access



* 20 minutes
* 2023-03-03



[Onboarding a virtual server image for VPC](https://cloud.ibm.com/docs/account?topic=account-catalog-vsivpc-tutorial)Onboarding a virtual server image for VPC

This tutorial walks you through how to onboard a sample virtual server image for virtual private cloud (VPC) to your account. By completing this tutorial, you learn how to create a private catalog, import the image, validate that it can be installed on a selected deployment target, and make the virtual server image available to users who have access to your account. As you complete the tutorial, adapt each step to match your organization's goal.

Object Storage Virtual Private Cloud (VPC)

+1

Managing your account, resources, and access



* 20 minutes
* 2022-08-25



[Securing data using context-based restrictions](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-cos-tutorial-cbr)Securing data using context-based restrictions

In this tutorial, you will establish context-based restrictions that prevent any access to object storage data unless the request originates from a trusted network zone.

Object Storage



* 10 minutes
* 2022-05-02
Creating a custom image from volume and provisioning an instance in the UI 

This tutorial demonstrates how to create a custom image from the boot volume of a virtual server instance, and then use that image to create a new instance.



 Before you begin 

This tutorial requires the following prerequisites.



* An IBM Cloud billable account.
* An IBM Cloud [VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started).
* An IBM Cloud [SSH key](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys).
* An IBM Cloud [virtual server instance](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers).







 Objectives 



* Create a resource group, Image resources.
* Create a custom image from an instances' boot volume.
* Create a new virtual server instance by using the custom image.







 Step 1: Creating a resource group 

You can use [resource groups](https://cloud.ibm.com/docs/vpc?topic=vpc-iam-getting-startedresources-and-resource-groups) to organize images.



1. Log in to the [IBM Cloud console](https://cloud.ibm.com/login).
2. Click Manage > Account.
3. From the Account page, click Resource groups > Create.
4. Give the resource group a unique name such as Image resources.
5. Click Add.







 Step 2: Creating an image from a volume in the UI 

You can use the UI to create an image from a volume that is attached to an available virtual server instance as the primary boot volume.



 Choose the source for your custom image 

Complete the following actions to import your custom image in the UI.



1. In [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon !
[Deploy to the default Kubernetes namespace](https://cloud.ibm.com/docs/openshift?topic=openshift-imagesnamespace).
2. [Deploy to a different Kubernetes namespace, or from a different IBM Cloud region or account](https://cloud.ibm.com/docs/openshift?topic=openshift-registryother).









 Enabling image security enforcement in your cluster 

When you enable image security enforcement in your cluster, you install the open-source Portieris Kubernetes project. Then, you can create image policies to prevent pods that don't meet the policies, such as unsigned images, from running in your cluster.

For more information, see the [Portieris documentation](https://github.com/IBM/portieris).

Mutated images: By default, Portieris uses the MutatingAdmissionWebhook admission controller to mutate your image to refer to the image by a digest instead of a tag. However, you might have some deployment technology that rejects a mutated image. If so, you can use the [image mutation option](https://github.com/IBM/portieris/blob/main/README.mdimage-mutation-option) and [policy](https://github.com/IBM/portieris/blob/main/POLICIES.mdimage-mutation-option) to change the default behavior.



 Enabling or disabling image security enforcement 

You can enable or disable image security enforcement for your cluster from the CLI or console. For earlier versions, see the [Portieris documentation](https://github.com/IBM/portieris).



 Enabling or disabling image security enforcement with the CLI 

See the following commands.



* [ibmcloud oc cluster image-security enable](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics-image-security-enable)
* If you're using a secret, select Yes and click Select from Secrets Manager. Select your service instance, secret group, and secret. If you don't see your secret, make sure you're using the correct secret group and service instance.



The message No service instance available might be displayed if you haven't created a secret or if you don't have the correct access to use secrets, even if you have service instances that are created.
4. Enter your source URL. You can review the following list of supported formats per software type:



* Helm chart: https://raw.githubusercontent.com/IBM/charts/master/repo/ibm-helm
* Node-RED Operator: https://github.com/IBM-Cloud/operator-bundle-sample/archive/refs/tags/v0.0.3.tar.gz
* Operator bundle from a Red Hat OpenShift on IBM Cloud registry: For an example, select the Akka Cluster Operator from the list of available Operators in the Certified repository.
* OVA image: https://github.com/gcatalog/OVA-sample/blob/main/ova-sample.yaml
* Terraform template: https://github.com/IBM-Cloud/terraform-sample/releases/tag/v1.0.0
* Virtual server image with Terraform: https://github.com/IBM-Cloud/isv-vsi-product-deploy-sample/releases/download/v1.0/isv-vsi-product-deploy-sample.tar.gz
* Virtual server image for VPC: Select an image from the list of available images, or import a new image to onboard it.



A virtual server image for VPC can only be added to one product within one private catalog at a time. If the virtual server image you want to import is already imported into another product, you must remove the image from that product or delete the product before you add the virtual server image to a new product.
5. If applicable, enter the version of the software in the format of major version, minor version, and revision.
* If you plan to use a Hardware Security Module (HSM) to generate and store the private key for your peer and ordering nodes, you can configure the HSM before you deploy the platform. Along with deploying the HSM device itself, in order for the blockchain components to access the HSM partition, you also need to publish an HSM client image to a container registry. If you decide to publish an HSM client image to a container registry, you can enable HSM support for the platform by providing the image URL when you link the service to your cluster. See the instructions in [Configuring a node to use a Hardware Security Module](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-cfg-hsm) to learn how to deploy the HSM and publish the HSM client image. If the HSM device is not yet available, you can always come back later and enable the HSM support for the platform when it is ready.
* Zero downtime is an important goal of your blockchain network. Review the topic on [High Availability](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-ha) for considerations when configuring your Kubernetes cluster and blockchain components.
* If you plan to use a Kubernetes cluster that contains multiple zones, ensure that [VLAN spanning](https://cloud.ibm.com/docs/vlans?topic=vlans-vlan-spanningmanage-vlan-spanning) is enabled in your account. This setting allows worker nodes to communicate between zones.
* The user who links the service to the Kubernetes cluster must have Storage Manage permissions. From the IBM Cloud dashboard, navigate to Manage > Access (IAM), then choose Users, and click the user who will link the service to the Kubernetes cluster. Click the Classic infrastructure tab, expand the Services twistie, and select Storage Manage. Click Apply to add this permission for the user.





 Browsers
The following diagram shows the components of an example service instance with two recovery crypto units:

Zoom

![The architecture of using recovery crypto units to initialize service instances](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/hs-crypto//images/minimum-touch-architecture.svg)

Figure 2. Initializing service instances by using recovery crypto units

The following sections explain each component in detail.



 Understanding IBM Cloud TKE CLI plug-in 

The TKE CLI plug-in is an addition to the IBM Cloud command-line interface (CLI). With the TKE CLI plug-in, you can send commands to the crypto units in your service instance to load the master key. The TKE CLI plug-in supports two approaches for loading the master key.

If your service instance has recovery crypto units, you can load the master key by running the ibmcloud tke auto-init command. This command guides you through steps to add administrators and set the signature thresholds, and then generates a random master key value in one of the recovery crypto units in your service instance and copies the value to the other crypto units. For more information about this approach, see [Initializing service instances by using recovery crypto units](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-recovery-crypto-unit).

You can also use the TKE CLI plug-in to load the master key using key parts stored in key part files. This approach can be taken regardless of whether your service instance has any recovery crypto units. Using this approach, you run a series of commands to generate signature keys and master key parts, add administrators, set the signature thresholds, and load the master key registers. For more information, see [Initializing service instances by using key part files](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm).
ibmcloud ce build update --name helloworld-build --source https://github.com/IBM/CodeEngine --context-dir /hello --commit main --timeout 900





 Example output 

Updating build helloworld-build...
OK









 Buildrun commands 

A build, or image build, is a mechanism that you can use to create a container image from your source code. Code Engine supports building from a Dockerfile and Cloud Native Buildpacks. Use buildrun commands to submit, display details, and delete build runs.

You must be within the context of a [project](https://cloud.ibm.com/docs/cli?topic=cli-clicli-project) before you use buildrun commands.

For more information about working with builds and build runs, see [Building a container image](https://cloud.ibm.com/docs/codeengine?topic=codeengine-build-image).

You can use either buildrun or br in your buildrun commands. To see CLI help for the buildrun commands, run ibmcloud ce br -h.



 ibmcloud ce buildrun cancel 

Cancel a build run.

ibmcloud ce buildrun cancel --name BUILDRUN_NAME [--quiet]



 Command Options 

--name, -n
: The name of the build run. This value is required.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.





 Example 

ibmcloud ce buildrun cancel --name mybuildrun





 Example output 

Cancelling build run 'mybuildrun'...
OK







 ibmcloud ce buildrun delete 

Delete a build run.

ibmcloud ce buildrun delete (--name BUILDRUN_NAME | --build BUILD_NAME) [--force] [--ignore-not-found] [--quiet]



 Command Options 

--build, -b
: Use this option to delete all build runs of the specified build.
ibmcloud ce build update --name helloworld-build --source https://github.com/IBM/CodeEngine --context-dir /hello --commit main --timeout 900





 Example output 

Updating build helloworld-build...
OK









 Buildrun commands 

A build, or image build, is a mechanism that you can use to create a container image from your source code. Code Engine supports building from a Dockerfile and Cloud Native Buildpacks. Use buildrun commands to submit, display details, and delete build runs.

You must be within the context of a [project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project) before you use buildrun commands.

For more information about working with builds and build runs, see [Building a container image](https://cloud.ibm.com/docs/codeengine?topic=codeengine-build-image).

You can use either buildrun or br in your buildrun commands. To see CLI help for the buildrun commands, run ibmcloud ce br -h.



 ibmcloud ce buildrun cancel 

Cancel a build run.

ibmcloud ce buildrun cancel --name BUILDRUN_NAME [--quiet]



 Command Options 

--name, -n
: The name of the build run. This value is required.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.





 Example 

ibmcloud ce buildrun cancel --name mybuildrun





 Example output 

Cancelling build run 'mybuildrun'...
OK







 ibmcloud ce buildrun delete 

Delete a build run.

ibmcloud ce buildrun delete (--name BUILDRUN_NAME | --build BUILD_NAME) [--force] [--ignore-not-found] [--quiet]



 Command Options 

--build, -b
: Use this option to delete all build runs of the specified build.
[checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/icons/checkmark-icon.svg) 







 Crawl schedule options 

When you create a collection, the initial crawl starts immediately. The frequency that you choose for the crawl schedule determines when the next crawl will start.

To create a crawl schedule, complete the following steps:



1. In the in Crawl schedule section, choose a frequency.

IBM Cloud Pak for Data

Installed deployments have more schedule options:



* If you want to crawl every 12 hours or every 10 days, choose Custom intervals. You can schedule the crawler to run on a custom number of days or hours.
* By default, the crawl is scheduled to start during off-peak hours.
* Do not set the interval to a frequency that is shorter than the time it takes for the crawl to finish.
* Do not configure multiple crawlers to run at short intervals.
* You can schedule the crawler to run at a specific day and time. This option is helpful if you want to avoid heavy load on a target system during business hours. If you specify an hour in the range 1 - 9, add a zero before the hour digit. You can schedule the crawl for 01:00 AM on Saturdays, for example.
* If you open a collection in a time zone other than the one in which the collection was created, the Coordinated Universal Time (UTC) offset information is displayed.



2.
IBM Cloud Pak for Data

Installed deployments have a More scheduling settings section where you can choose the type of schedule to use to crawl the data source.

The choices for all of the connectors (except the Web crawl connector) are as follows:



* Full crawling: Recrawls the external data source to update documents in the collection.
* Crawling updates (look for new, modified, and deleted contents): Updates the collection only if data in the external data source was added, modified, or deleted since the last crawl.
AutoMaint 

You can schedule database maintenance jobs and view information about scheduled maintenance windows by using the the web console. The scheduled maintenance of your database includes grooms and genstats.



  Scheduling maintenance jobs with the web console 

To schedule a database maintenance job:



1.  Log in to the web console.
2.  Go to Administration >> Settings >> Maintenance.
3.  Click Edit.
4.  Select a time for the maintenance job.
5.  Select a day or days for the maintenance job.
6.  Click Save.
Best practices for lowering your account's carbon emissions 

These best practices help you to learn about IBM Cloud's carbon calculator features and options that you can use to track carbon emissions and reduce the carbon footprint of your account. To view your carbon emissions data, go to the [carbon calculator page](https://cloud.ibm.com/billing/carbon-calculator). If you'd like to know more about the carbon calculator, see [Working with IBM Cloud's carbon calculator](https://cloud.ibm.com/docs/allowlist/carbon-calculator?topic=carbon-calculator-what-is-cloud-calc).



 Compress your data 

Compression is the conversion of data to a format that requires less storage space as measured in bits. This typically involves looking for patterns in data and eliminating redundancies. Audit video files, images, and archived files to determine if any can be compressed. Using less disc space means using less energy, which lowers emissions.





 Schedule jobs during off times 

Utilization reports are reviewed and updated monthly on the 15th of the month. This makes the final monthly data for the month available 7-10 days later in our system. If you do not need a month to day view, you should schedule your data pull for the last week of the month to have the final reviewed report for the month.

It is possible due to the high amount of users pulling data simultaneously, that the page load and refresh times may increase a little during the last week of the month. If you do not need to have a month to date report, use the download option, this allows you to get the report data downloaded to your system. The report has all of the same data that is used to build the charts, but it is more efficient than gathering the information through the graphical interface.





 Leverage Envizi ESG reporting 

IBM Envizi is a robust data management foundation that is designed to create a single, trusted data source for all your ESG reporting and opportunity identification. Use ESG reporting to meet compliance and reporting requirements. For more information, see [IBM Envizi ESG Suite](https://www.ibm.com/products/envizi).