vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* CLI







 Using IBM Cloud Monitoring with IBM Cloud Object Storage 

Use the IBM Cloud® Monitoring service to monitor your IBM Cloud® Object Storage (COS) data in the IBM Cloud. The results of the activity can be measured for compliance and other analysis through the web dashboard UI.

This feature is not currently supported in Object Storage for Satellite. [Learn more.](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-about-cos-satellite)



 Features 

IBM Cloud Monitoring is a cloud-native management system. Documentation from [Monitoring](https://cloud.ibm.com/docs/monitoring?topic=monitoring-dashboards) can guide you in how to use the comprehensive dashboards. In this guide we will focus on how to measure activity on individual buckets in your instance of IBM Cloud Object Storage.



 Working with Metrics 

According to the [Monitoring documentation](https://cloud.ibm.com/docs/monitoring?topic=monitoring-getting-startedgetting-started), "A metric is a quantitative measure that has one or more labels to define its characteristics." When you configure your buckets to forward data to a Monitoring instance, that data is automatically collected and available for analysis through the web UI.







 Before you begin 

Before you provision an instance of IBM Cloud Monitoring, consider the following guidance:



* The account owner can create, view, and delete an instance of a service in the IBM Cloud. This user can also grant permissions to other users to work with the IBM Cloud Monitoring service.
* Other IBM Cloud users with administrator or editor permissions can manage the IBM Cloud Monitoring service in the IBM Cloud. These users must also have platform permissions to create resources within the context of the resource group where they plan to provision the instance.



In this guide, we will examine using both the IBM Cloud Console as well as the IBM Cloud Developer Tools (CLI) to integrate Monitoring in your Object Storage instance. For more information about IBM Cloud Developer Tools, check out the [documentation](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).
Setting up the integration between your App ID instance, which is already configured with your IdP, and your IBM Cloud account makes it so you can continue to manage all users externally in your IdP. It also simplifies the log in process to your cloud account for users in your enterprise. After the integration is complete, you must provide your users with a custom URL that they use to log in each time. There is no need to invite anyone to your account because if they exist as a user in your connected IdP's user repository, they can log in with their credentials through the custom URL.



 Before you begin 



* To decide which is the right federation option for you, check the [IBM Cloud SAML Federation Guide](https://www.ibm.com/cloud/blog/ibm-cloud-saml-federation-guide).
* Create an instance of App ID from the IBM Cloud catalog. For more information, see the [Getting started tutorial](https://cloud.ibm.com/docs/appid?topic=appid-getting-started).
* Configure your App ID instance. For more information about how to do this depending on your use case, see the App ID documentation about [managing authentication](https://cloud.ibm.com/docs/appid?topic=appid-managing-idp).
* Make sure you have the required access to view and manage IdP references, if you aren't the account owner. You must be assigned the operator role or higher on the App ID instance and the operator or administration role on the [IAM Identity Service](https://cloud.ibm.com/docs/account?topic=account-account-servicesidentity-service-account-management).







 Configuration of your App ID instance for IAM integration 

Review the following requirements about how your App ID instance must be configured to work properly as an IAM IdP for your IBM Cloud account.

If you plan to use your App ID instance for IAM IdP integration, then any user can log in to your account who can authenticate with that App ID instance. Therefore, consider following these guidelines when you configure your instance:

Disable the following types of authentication:



* Facebook
[Access management policies by using IAM or classic infrastructure permissions.](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/account/images/access-management.svg)

Figure 1. Access management policies by using IAM or classic infrastructure permissions

For IAM policies, the subject can be an access group, user, service ID, or trusted profile. And, the target can be an account management service, resource group, service in the account, specific service instance, or resource type within a service. Platform and service roles can be selected to scope the level of access for the subject. For classic infrastructure, a user is selected, and then the access can be scoped to a service or device with specific permissions assigned.



 Watch and learn 



* Video transcript

Welcome back to another installment of the IBM Cloud Console Guide. In this video, we will talk about the different roles you can assign within the console.

An account owner can invite as many users as they would like to their IBM Cloud account. Access management enables you to control which users are able to see, create, use, and manage resources in the account.

The way that you manage access in IBM Cloud depends on the type of resource that you want to assign access to. The user access policy for available resources and services within the cloud catalog is managed by either Classic infrastructure and/or IAM or Cloud Foundry.

As the account owner or the administrator of an account management service, you can use these services to grant users access to All Account Management services, Billing, Global Resource Catalog, IAM Access Groups Service, IAM Identity Service, Support Center, and User Management. Account Management roles include Administrator, Editor, Operator, or Viewer.

With Classic Infrastructure, you can select from three permission sets that will assign bulk access: View Only, Basic User, and Super User. You can give users access to Classic Infrastructure service or Classic Infrastructure device with specific permissions for Account, Network, Devices, and Services.

Cloud Foundry roles grant access to organizations and spaces within the account.
By completing this tutorial, you learn how to create a private catalog, import your CSV or TGZ file, validate that it can be installed on a Red Hat OpenShift cluster, and make the Operator available to users who have access to your account.

Container Registry Managing your account, resources, and access



* 45 minutes
* 2022-10-26



[Onboarding a Terraform template by using the CLI](https://cloud.ibm.com/docs/account?topic=account-catalog-terraform-template-cli)Onboarding a Terraform template by using the CLI

This tutorial walks you through how to onboard a Terraform template to your account by using the CLI. By completing this tutorial, you learn how to create a private catalog and import the template. After that, you can validate that the template can create resources, or run a script, and you can make it available to users who have access to your account.

Managing your account, resources, and access



* 20 minutes
* 2023-03-31



[Onboarding a Terraform template](https://cloud.ibm.com/docs/account?topic=account-catalog-terraform-template-tutorial)Onboarding a Terraform template

This tutorial walks you through how to onboard a Terraform template to your account. By completing this tutorial, you learn how to create a private catalog and import the template. After that, you can validate that the template can create resources, or run a script, and you can make it available to users who have access to your account.

Managing your account, resources, and access



* 20 minutes
* 2022-07-27



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

This tutorial walks you through how to onboard a sample virtual server image with Terraform to your account.
These users must also have platform permissions to create resources within the context of the resource group where they plan to provision the instance.



In this guide, we will examine using both the IBM Cloud Console as well as the IBM Cloud Developer Tools (CLI) to integrate Monitoring in your Object Storage instance. For more information about IBM Cloud Developer Tools, check out the [documentation](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).

Using either set of instructions, Console or CLI, you will be able to get started using this guide. If the instructions that you seek do not appear in this guide, click on the appropriate item using the context switcher.



 Instantiating and Provisioning IBM Cloud Object Storage 

If you have not already done so, [set up and provision](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-provision) your instance of Object Storage. If you already have an instance of Monitoring to work with, verify you have either the manager or writer[role](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam-bucket-permissions) to work with this guide.







 Manage User Access 

There are many ways to manage access to your Object Storage instance, but for this guide we'll focus on how to access the dashboard you are going to create.

Users in an account [must be assigned a platform role](https://cloud.ibm.com/docs/Monitoring-with-Sysdig?topic=Monitoring-with-Sysdig-iam) in order to manage instances as well as launching the IBM Cloud Monitoring UI from the IBM Cloud console. In addition, users must have a service role that defines the permissions to work with IBM Cloud Monitoring.





 Provisioning an instance of Monitoring 

From the [catalog](https://cloud.ibm.com/login) choose IBM Cloud Monitoring from the available services. When selected, you will be taken to the configuration shown in Figure 1. At the bottom of the screen under "IBM platform metrics:" select Enable before creating the instance.
Access the VPC+ Cloud Migration tool 

After you create an instance of VPC+ Cloud Migration through the IBM Cloud catalog, you can access the VPC+ Cloud Migration tool.



1. On the service details page of your VPC+ Cloud Migration instance, select the Manage tab.
2. When you are ready to access the tool, click Migrate.
3. Log in to VPC+ Cloud Migration by using your IBMid.



After you log in to the VPC+ Cloud Migration tool, you can access the User Guide and Tutorial Videos that were developed by Wanclouds. These resources are located in the Help menu in the VPC+ Cloud Migration interface.





 Step 5. Add your IBM Cloud account to VPC+ Cloud Migration 

In order for VPC+ Cloud Migration to access details of your IBM Cloud configuration, you must add your IBM Cloud accounts information. Complete the following steps to add your IBM Cloud accounts.



1. In the VPC+ Cloud Migration interface, click Get Started.
2. On the IBM Cloud Classic tab, provide account information for your IBM Cloud classic infrastructure environment. This information is used to discover your current environment.
3. On the IBM Cloud VPC tab, provide account information for your VPC environment. See [Gathering IBM Cloud account information](https://cloud.ibm.com/docs/wanclouds-vpc-plus?topic=wanclouds-vpc-plus-planning-for-migrationgather-account-information) for information on where to get these values.







 Next steps 

After you add your IBM Cloud accounts to VPC+ Cloud Migration, you are now ready to discover the resources in your classic infrastructure. See [Discovering your IBM Cloud classic infrastructure](https://cloud.ibm.com/docs/wanclouds-vpc-plus?topic=wanclouds-vpc-plus-migrate-discovery).
After that, you can validate that the template can create resources, or run a script, and you can make it available to users who have access to your account.

Managing your account, resources, and access



* 20 minutes
* 2022-07-27



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

This tutorial walks you through how to onboard a sample virtual server image with Terraform 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 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.
Access policies can only be set for IAM-enabled services and account management services (clicks "Assign access" button on the Access policies tab for the created access group, then highlights two tiles for IAM-enabled services and Account management services). Cloud Foundry and Classic Infrastructure are separate.

The role defines the level of access granted to a user (Starts creating a policy by selecting All identity and access enabled services, then scrolling the available roles that display). The most commonly used roles are viewer, editor, and administrator. The viewer role provides the least amount of access for viewing instances and resource groups. The editor role allows more access to create, edit, delete, and bind service instances. While the administrator includes everything for working with a service instance and can also assign access to others.

To make assigning access as easy as possible, you can organize resources into a resource group and users and service IDs into an access group. After you set up each one, you can then create access policies for the access groups to give users access to the resources you’ve created.

To get started, click “Manage” in the IBM Cloud console, then click “Access (IAM)” and select “Access Groups.”

Then, select the name of the access group that you want to assign access.

Select the “Access policies” tab, and then click “Assign access.”

Now you will select the type of access that you want to assign (clicks IAM services, selects All identity and access-enabled services, selects Administrator platform role, selects Reader service role). Then, click “Add” and “Assign.” (Then, clicks "Invite" button.)

Inviting users to the access group is easy. You can add users directly to each access group by clicking on “Users” and the blue “Invite Users” button.

Thank you for watching this installment of the IBM Cloud Console Guide.







 Before you begin 

To manage or create new access groups, you must have the following type of access:



* Account owner
* Administrator or editor on the IAM Access Groups account management service in the account
* Administrator or editor for the All Account Management services



Additionally, an administrator or editor can be assigned access to manage an individual group by creating an access policy where the resource is the Access group ID.
Administering a queue manager using MQ Explorer and the runmqsc command line 

This guide documents how to adminster an IBM MQ on Cloud queue manager using the MQ Explorer application and the runmqsc command line interface.



 MQ Explorer: 

MQ Explorer is an Eclipse-based tool for administering IBM MQ that you install on a machine of your choice and which connects remotely to one or more queue managers using a client connection. There are native installers for Windows and Linux 64-bit environments and it can be run on Mac OS via a Docker container as described in the prerequisites below.

The Eclipse plugin for MQ explorer on Mac OS does not, at the time of writing, support TLS connection. The administration channel for MQ on Cloud queue managers newer than version 9.2.1 revision 1 will have TLS enabled. These should be administered from Linux or Windows.





 runmqsc 

Part of the "MQ clients" bundle, runqmsc is a command-line interface (CLI) tool that allows you to automate the configuration of MQ queue managers by executing a series of pre-defined steps at the command-line or in a script file. It is supported on a range of operating systems including Windows and Linux (but is not currently supported on Mac OS).

There are many actions you can perform by using MQ Explorer or runmqsc from an MQ client. You can



* Connect to a queue manager
* Create a new queue
* Put a message onto a queue
* Delete a queue



In addition to this, on MQ Explorer, you can browse a queue to view messages In the runmqsc command line, you can also get messages from a queue





 Before you begin 



* An existing queue manager (for instructions, follow the [creating a queue manager](https://cloud.ibm.com/docs/services/mqcloud?topic=mqcloud-mqoc_create_qm) guide).
}
EOF
Show more

This example policy triggers autoscaling based on memory utilization when the defined threshold is breached for at least 120 seconds. See the [App AutoScaler User Guide](https://github.com/cloudfoundry/app-autoscaler/blob/master/docs/Readme.md) for more information about how to create your own autoscaling policy.
3. Attach the policy to your app by running the following command:

ibmcloud cf aasp <YOUR_APP> <YOUR_POLICY_FILE>







 Metric statistics 

You can query the most recent aggregated metrics for your app. The App Autoscaler supports multiple [metric types](https://github.com/cloudfoundry/app-autoscaler/blob/master/docs/Readme.mdmetric-types), but you can retrieve only the metrics that are defined in your policy. For example, memoryutil in the previous CLI example.

ibmcloud cf asm <YOUR_APP> <METRIC_TYPE> --desc





 Scaling history 

You can use the following command to query autoscaling history for an app.

ibmcloud cf ash <YOUR_APP> --desc









 More information about autoscaling 



* [Cloud Foundry App Autoscaler CLI plug-in guide](https://github.com/cloudfoundry/app-autoscaler-cli-plugincloud-foundry-cli-autoscaler-plug-in-)
* [Best practices when setting up autoscaling policies](https://www.ibm.com/cloud/blog/autoscale-your-cloud-foundry-applications-on-ibm-cloud)
* [Bring Your Own Metrics to Autoscale Your IBM Cloud Foundry Apps](https://www.ibm.com/cloud/blog/bring-your-own-metrics-to-autoscale-your-ibm-cloud-foundry-applications)
* UI
* CLI
* API
* Terraform







 Setting up access groups 

An access group can be created to organize a set of users, service IDs, and trusted profiles into a single entity that makes it easy for you to assign access. You can assign a single policy to the group instead of assigning the same access multiple times for an individual user or service ID.

Access groups are assigned policies that grant roles and permissions to the members of that group. Members of an access group can include multiple identity types, like users, service IDs, and trusted profiles. The members inherit the policies, roles, and permissions that are assigned to the access group, and also keep the roles that they are assigned individually.

For example, if a user is assigned the viewer role on the billing service and they are added to an access group that has the publisher role on the catalog management service, they keep their viewer role even though that isn't part of the access group permissions.

To make assigning and managing access even easier, you can set up resource groups to organize a set of resources that you want a group of users to have access to. When your resource group is set up, you can assign a policy that gives access to all resources within that group instead of creating access policies for individual service instances within your account.



 Watch and learn 



* Video transcript

Welcome back to another installment of the IBM Cloud Console Guide. In this video, we will be showing you how to set up an access group.

Assigning access to users in IBM Cloud individually can be time consuming, especially if you have a large organization. That’s where access groups come in to play.

Access groups allow you to assign a minimal number of policies by giving the same access to all users and service IDs that belong to the same access group. In other words, instead of assigning the same access multiple times to multiple users or service IDs, you can create a group and assign a single policy to that group. This helps save time and keep access permissions organized.

The best practice for setting up access groups is to create one access group per wanted level of access. Then, you can map each access group to the previously created resource groups.
For detailed instructions to complete Steps 2 and 3, other GPU tools, and examples, see [How to Use V100-Based GPUs on IBM Cloud VPC](https://www.ibm.com/cloud/blog/how-to-use-v100-based-gpus-on-ibm-cloud-vpc).

For a Linux focused guide on installing the NVIDIA drivers, see the [NVIDIA Driver Installation Quickstart Guide](https://docs.nvidia.com/datacenter/tesla/tesla-installation-notes/index.html).

If you want to automate the installation of the drivers, you can use the [User data](https://cloud.ibm.com/docs/vpc?topic=vpc-user-data) section of the VSI. By using the user data field, you can input a script that issues the commands to install the NVIDIA drivers.





 Integrating the GPU driver into a custom image from volume 



1. Provision a virtual server instance with a GPU and install the drivers.
2. Create an image from the virtual server instance stock image boot volume. For more information, see [Creating an image from a volume](https://cloud.ibm.com/docs/vpc?topic=vpc-create-ifv&interface=ui).
3. Repeat the Image from volume process to deploy across multiple instances.







 Next steps 

For more information, see the [NVIDIA driver documentation](https://docs.nvidia.com/datacenter/tesla/index.html).