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







 Getting started with bandwidth metering 

Use bandwidth metering to manage your device's bandwidth and bandwidth pools. Learn how to choose the best value bandwidth solution, how to respond to overage notices, and how to create and manage bandwidth pools and other bandwidth metering for your devices.



 Understanding bandwidth metering versus bandwidth pools 

To use your allocated bandwidth more efficiently, it's important to understand how bandwidth in the Classic IaaS platform works and understand the bandwidth management options.

You can purchase and manage bandwidth metering for classic in two ways. You can manage bandwidth on a single device by purchasing a fixed amount of bandwidth allocation for that device during a billing cycle. You receive a notification when the device uses 85% of its allocated bandwidth for the billing cycle.

Additionally, you can add a device's bandwidth allocation to a bandwidth pool. A bandwidth pool aggregates each added device's individual bandwidth allocation into a collective bandwidth allocation. As devices in the pool use bandwidth during the month, the usage is metered for the bandwidth pool and measured against the collective bandwidth allocation limit. Notifications are sent to users when the devices in the pool collectively use 85% of the pool's allocated bandwidth.

Figure 1 illustrates how adding servers with individual bandwidth allocations to a bandwidth pool increases the bandwidth pool's collective bandwidth allocation. In this case, three servers are added to a bandwidth pool: Virtual server instance 1 with 5,000 GB of bandwidth, Bare metal server 1 with 20,000 GB of bandwidth, and Bare metal server 2 with 10,000 GB of bandwidth. Therefore, the bandwidth pool's collective bandwidth allocation is 35,000 GB, the sum of each server's allocated bandwidth in the pool.

Bandwidth pool highlights include:



* defined geographically (charges vary depending on the region of your pool)
* allocated a bandwidth amount that's the sum of allocations for devices in the pool
* billed a pool overage fee when bandwidth usage exceeds bandwidth allocation
* billed a membership fee per device in the pool



100 percent of the bandwidth from each server added to a bandwidth pool is added to the pool's collective bandwidth allocation.

Zoom

!
* Click Add file and browse to the Multiregion OS CA_ca.json file that you exported from the console in Region 1 and click Add Certificate Authority.
* Open the imported Multiregion OS CA tile.
* Click Associate identity.
* Specify the enroll ID and secret we used when we created the CA, admin and adminpw then Associate identity.



2. Import the Ordering service.



* From the Nodes tab, click Add ordering service, then Import an existing ordering service.
* Click Add file and browse to the Multiregion Ordering Service_orderer.json file that you exported from the console in Region 1 and click Add ordering service.



3. Import the orderer organization msp.



* From the Organizations tab, click Import MSP definition and then click Add file.
* Browse to the Multiregion OS MSP_msp.json file that you exported from the console in Region 1 and click Import MSP definition.



4. Import the MSP admin identity.



* From the Wallet tab, click Add identity then Upload JSON.
* Browse to the Multiregion OS MSP Admin_identity.json file that you exported from the console in Region 1 and click Add identity.









 Add third ordering node from Region 2 

Now we are ready to create a third ordering node that resides in Region 2 and add it to the ordering service. The steps that are required are largely repeated from when we added the second ordering node to the ordering service in Region 1.



1. Navigate to the Nodes tab.
2. Scroll down to the Multiregion Ordering Service ordering service that you imported and click the tile to open it.
3. Because the ordering service was not created in this console, you need to associate the admin identity with it. Click Associate identity and then select the Multiregion OS MSP Admin and click Associate identity.
4. Click the Ordering nodes tab where you can see the two ordering nodes contributed by the console in Region 1. Click Add another node to add a new node from Region 2.
5. Click Create an ordering node and Next.
6. Provide a name for this ordering node, OS3-Region2.
7.
The application forwards the transaction, which includes the read/write set and endorsements, to the ordering service.
4. The transaction is then relayed to the ordering service. All channel peers validate each transaction in the block by applying the chaincode-specific Validation Policy and running a Concurrency Control Version Check.



* Any transaction that fail the validation process is marked as invalid in the block, and the block is appended to the channel's ledger.
* All valid transactions update the state database accordingly with the modified key/value pairs.





The gossip data dissemination protocol continually broadcasts ledger data across the channel to ensure synchronized ledgers among peers. For more information, see [Gossip data dissemination protocol](https://hyperledger-fabric.readthedocs.io/en/release-1.4/gossip.html) in [Hyperledger Fabric documentation](https://hyperledger-fabric.readthedocs.io/en/release-1.4/).

For a step-by-step introduction on transaction flow, see [Transaction Flow](https://hyperledger-fabric.readthedocs.io/en/release-1.4/txflow.html) in [Hyperledger Fabric documentation](https://hyperledger-fabric.readthedocs.io/en/release-1.4/).
Successfully enrolled client "user1" and imported it into the wallet

You can find the wallet that was created in the identity folder of the magnetocorp directory.





 Step four: Use the connection profile to build a Fabric gateway 

The Hyperledger Fabric [Transaction Flow](https://hyperledger-fabric.readthedocs.io/en/release-2.2/txflow.html) spans multiple components, with the client applications playing a unique role. Your application needs to connect to the peers that need to endorse the transaction and needs to connect to the ordering service that will order the transaction and add it into a block. You can provide the endpoints of these nodes to your application by using your connection profile to construct a Fabric gateway. The gateway then conducts the low-level interactions with your Fabric network. To learn more, visit the [Fabric gateway](https://hyperledger-fabric.readthedocs.io/en/release-2.2/developapps/gateway.html) topic in the Fabric documentation.

You have already downloaded your connection profile and used it to connect to your organization's Certificate Authority. Now we use the connection profile to build a gateway.

Open the file issue.js in a text editor. Before you edit the file, notice that it imports the FileSystemWallet and Gateway classes from fabric-network library.

const { FileSystemWallet, Gateway } = require('fabric-network')

You will need to import the path class to build the gateway from the connection profile you downloaded from your console. Add the following line to the file to import the path class:

const path = require('path');

The Gateway class is used to construct a gateway that you will use to submit your transaction.

const gateway = new Gateway()

The FileSystemWallet class is used to load the wallet you created in the previous step. Edit the following line if you changed the location of the wallet on your file system.

const wallet = new FileSystemWallet('../identity/user/isabella/wallet');

After you import your wallet, use the following code to pass your connection profile and wallet to the new gateway.
* Click Add file and browse to the Multiregion Ordering Service_orderer.json file and click Add ordering service.



3. Import the orderer organization msp.



* From the Organizations tab, click Import MSP definition and then click Add file.
* Browse to the Multiregion OS MSP_msp.json file and click Import MSP definition.



4. Import the MSP admin identity.



* From the Wallet tab, click Add identity then Upload JSON.
* Browse to the Multiregion OS MSP Admin_identity.json file and click Add identity.









 Add fourth and fifth ordering nodes from Region 3 

Almost done. Let's create the last two ordering nodes that will reside in Region 3 and add them to the ordering service:



1. Navigate to the Nodes tab.
2. Scroll down to the Multiregion Ordering Service ordering service that you imported and click the tile to open it.
3. Because the ordering service was not created in this console, you need to associate the admin identity with it. Click Associate identity and then select the Multiregion OS MSP Admin and click Associate identity.
4. Click the Ordering nodes tab where you can see the two ordering nodes contributed by the console in Region 1. Click Add another node to add a new node from Region 3.
5. Click Create an ordering node and Next.
6. Provide a name for this ordering node, OS4-Region3.
7. Again, if you want to choose the zone where this node is deployed, click the advanced deployment option that is labeled Deployment zone selection. Otherwise, leave it unchecked and let the system choose for you. Click Next.
8. On the Add ordering service page



* Select Multiregion OS CA as your CA.
* Then, select os1 as the enroll ID for the node identity.
* Enter the associated secret, os1pw.
* Select your MSP, Multiregion OS MSP from the drop-down list.
* For purposes of this tutorial you can skip the TLS CSR hostname option.
Unlike a subscription, when you have a commitment, you commit to spend a certain amount and receive discounts across the platform even after your commitment term ends. Any overage that is incurred on the account continues to receive a discount.
* How do I sign up for an Enterprise Savings Plan?

Contact [IBM Cloud Sales](https://www.ibm.com/cloud?contactmodule) to sign up for IBM Cloud Enterprise Savings Plan. To view your account ID, select "Register with a Code" during account registration. After you consult with a sales representative, you receive a confirmation email with your commitment quote details and information about IBM Cloud's Terms and Conditions. Your account is activated upon order processing.
* How do I view existing commitments?

To view your existing commitments, in the IBM Cloud® console, go to Manage > Billing and usage, and select Commitments & subscriptions.

Click the tabs to view the remaining credit in your active commitments and any upcoming commitments that aren't yet valid. A commitment is expired if its term expires or all of its credit is spent.
* How do I view my commitment usage?

To view your commitment usage, in the IBM Cloud® console, go to Manage > Billing and usage, and select Commitments & subscriptions.



* Click the tabs to view information on active or upcoming commitments.
* Use the graph to view what you've spent toward your overall committed amount.
* View monthly breakdown of the spending history for the commitment in the table.



* How do I view my commitment terms?

After you consult with a sales representative to sign up for IBM Cloud Enterprise Savings Plan, the sales team will email you a copy of your quote and information about IBM Cloud's Terms and Conditions.
* How do I add a new commitment?

Contact your [IBM Cloud Sales](https://www.ibm.com/cloud?contactmodule) representative to add a new commitment to your account.
* Why am I getting invoiced for a commitment I didn’t use?

Since you committed to a certain amount for a certain period of time and you didn't reach it, IBM Cloud® have the rights to charge you with the remaining amount.
* Platform management roles cover a range of actions, including the ability to create and delete instances, manage aliases, bindings, and credentials, and manage access. The platform roles are administrator, editor, operator, viewer. Platform management roles also apply to account management services that enable users to invite users, manage service IDs, access policies, catalog entries, and track billing and usage depending on their assigned role on an account management service.
* Service access roles define a user or service’s ability to perform actions on a service instance. The service access roles are manager, writer, and reader.



To manage the IBM Log Analysis service, a user needs the following roles:



* Platform role: Administrator.
* Service role: Manager.



[Learn more](https://cloud.ibm.com/docs/services/activity-tracker?topic=activity-tracker-iamiam).

Complete the following steps to assign a policy to an access group through the UI:



1. From the menu bar, click Manage > Access (IAM), and select Access Groups.
2. Select the name of the group that you want to assign access to.
3. Click Access policies.
4. Click Assign access.
5. Choose to assign access by resources within a resource group, or by individual resources available within the account. For example, you can choose any of the following options to grant a user an administrator role to manage IBM Log Analysis:





 Option 1. Grant permissions on the service 

Complete the following steps to assign a user administrator role to the IBM Log Analysis service in the account:



1. Select Assign access to resources.
2. Select IBM Log Analysis.
3. Select All current regions.
4. Select All current service instances.
5. Select the platform role Administrator.
6. Select the service role Manager.
7. Click Assign.







 Option 2. Grant permissions within the context of a resource group 

Complete the following steps to assign a user administrator role to the IBM Log Analysis service within the context of a resource group:



1. Select Assign access within a resource group.
2.
* Platform management roles cover a range of actions, including the ability to create and delete instances, manage aliases, bindings, and credentials, and manage access. The platform roles are administrator, editor, operator, viewer. Platform management roles also apply to account management services that enable users to invite users, manage service IDs, access policies, catalog entries, and track billing and usage depending on their assigned role on an account management service.
* Service access roles define a user or service’s ability to perform actions on a service instance. The service access roles are manager, writer, and reader.



To manage the IBM Cloud Activity Tracker service, a user needs the following roles:



* Platform role: Administrator.
* Service role: Manager.



[Learn more](https://cloud.ibm.com/docs/services/activity-tracker?topic=activity-tracker-iamiam).

Complete the following steps to assign a policy to an access group through the UI:



1. From the menu bar, click Manage > Access (IAM), and select Access Groups.
2. Select the name of the group that you want to assign access to.
3. Click Access policies.
4. Click Assign access.
5. Choose to assign access by resources within a resource group, or by individual resources available within the account. For example, you can choose any of the following options to grant a user an administrator role to manage IBM Cloud Activity Tracker:





 Option 1. Grant permissions on the service 

Complete the following steps to assign a user administrator role to the IBM Cloud Activity Tracker service in the account:



1. Select Assign access to resources.
2. Select IBM Cloud Activity Tracker with LogDNA.
3. Select All current regions.
4. Select All current service instances.
5. Select the platform role Administrator.
6. Select the service role Manager.
7. Click Assign.







 Option 2. Grant permissions within the context of a resource group 

Complete the following steps to assign a user administrator role to the IBM Cloud Activity Tracker service within the context of a resource group:



1.
Platform management roles also apply to account management services that enable users to invite users, manage service IDs, access policies, catalog entries, and track billing and usage depending on their assigned role on an account management service.
* Service access roles define a user or service’s ability to perform actions on a service instance. The service access roles are manager, writer, and reader.



To manage the IBM Cloud Activity Tracker service, a user needs the following roles:



* Platform role: Viewer.
* Service role: Reader.



[Learn more](https://cloud.ibm.com/docs/services/activity-tracker?topic=activity-tracker-iamiam).

Complete the following steps to assign a policy to an access group through the UI:



1. From the menu bar, click Manage > Access (IAM), and select Access Groups.
2. Select the name of the group that you want to assign access to.
3. Click Access policies.
4. Click Assign access.
5. Grant permissions. Choose one of the following options:





 Option 1. Grant permissions on the service 

Complete the following steps:



1. Select Assign access to resources.
2. Select IBM Cloud Activity Tracker with LogDNA.
3. Select All current regions.
4. Select All current service instances.
5. Select the platform role Viewer.
6. Select the service role Reader.
7. Click Assign.







 Option 2. Grant permissions within the context of a resource group 

Complete the following steps:



1. Select Assign access within a resource group.
2. Select a resource group.
3. If the user does not have a role that is already granted for the selected resource group, choose a role for the Assign access to a resource group field.

Depending on the role that you select, the user can view the resource group on their dashboard, edit the resource group name, or manage user access to the group.

You can select No access, if you want the user to have access only to the IBM Cloud Activity Tracker service in the resource group.
4.
transfer_manager = AsperaTransferManager(client=client,
transfer_config=ms_transfer_config)

For best performance in most scenarios, always make use of multiple sessions to minimize any processing that is associated with instantiating an Aspera high-speed transfer. If your network capacity is at least 1 Gbps, you should use 10 sessions. Lower bandwidth networks should use two sessions.





 File Upload 

bucket_name = "<bucket-name>"
upload_filename = "<absolute-path-to-file>"
object_name = "<item-name>"

 Create Transfer manager
with AsperaTransferManager(client) as transfer_manager:

 Perform upload
future = transfer_manager.upload(upload_filename, bucket_name, object_name)

 Wait for upload to complete
future.result()

Key Values



* <bucket-name> - name of the target bucket
* <absolute-path-to-file> - directory path and file name to the file to be uploaded
* <item-name> - name of the new file added to the bucket







 File Download 

bucket_name = "<bucket-name>"
download_filename = "<absolute-path-to-file>"
object_name = "<object-to-download>"

 Create Transfer manager
with AsperaTransferManager(client) as transfer_manager:

 Get object with Aspera
future = transfer_manager.download(bucket_name, object_name, download_filename)

 Wait for download to complete
future.result()

Key Values



* <bucket-name> - name of the bucket in your Object Storage service instance that has Aspera enabled.
* <absolute-path-to-file> - directory and file name where save the file to the local system.
* <object-to-download> - name of the file in the bucket to download.







 Directory Upload 

bucket_name = "<bucket-name>"
 THIS DIRECTORY MUST EXIST LOCALLY, and have objects in it.
Platform management roles also apply to account management services that enable users to invite users, manage service IDs, access policies, catalog entries, and track billing and usage depending on their assigned role on an account management service.
* Service access roles define a user or service’s ability to perform actions on a service instance. The service access roles are manager, writer, and reader.



To manage the IBM Cloud Activity Tracker service, a user needs the following roles:



* Platform role: Administrator.
* Service role: Manager.



Complete the following steps to assign a policy through the UI:



1. From the menu bar, click Manage > Access (IAM).
2. Select Access Groups.
3. Select the name of the group that you want to assign access to.
4. Click Access policies > Assign access.
5. Select IAM services.
6. For the field What type of access do you want to assign?, select IBM Cloud Activity Tracker.
7. For the in field, select the resource group.
8. Select the platform role Administrator.
9. Select the service role Manager.
10. Click Add. Then, select Assign.







 Add the user to the group 

Complete the following steps to add the user to the access group:



1. Click Add users on the Users tab.
2. Select the user that you want to add from the list, and click Add to group.









 Step 1: Generate IBM Cloud Activity Tracker events 

If you have a pay-as-you-go account, you can use IBM® Key Protect to create an event. If you don't have a pay-as-you-go account, provisioning any of the available lite services triggers an event.



1. From the [IBM Cloud catalog](https://cloud.ibm.com/catalog), select the category Security.
2. Select the Key Protect service.
3.
A peer is the blockchain component that maintains a ledger and runs a smart contract to perform query and update operations on the ledger. Organization members own and maintain peers. Each organization that joins a consortium should deploy at least one peer and minimally two for High Availability (HA) on each channel. You can learn more about peers in the [overview of blockchain components](https://cloud.ibm.com/docs/blockchain?topic=blockchain-blockchain-component-overviewblockchain-component-overview-peer).

After you import a peer into the console, you can install smart contracts on the peer and join the peer to channels.

Note: If you want to add more peers or create additional admin identities for a peer or peer organization, you need to import the relevant CA (the one that was used to create the MSP and identities for the peer organization) and then use that CA to register and enroll identities.



 Before you begin 

Before you can import a peer, you need to decide on the method you will use to become an admin of the peer (there is little that can be accomplished with an imported peer unless you also are an admin of the peer). See, [Gathering certificates or credentials](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-import-nodesibp-console-import-start-here) and follow the path that best suits your use case. Also, ensure that the JSON representing the peer is available.





 How to import a peer 

Importing a peer is performed from the Nodes tab.



1. Click Add Peer, followed by Import an existing peer and then click Next.
2. Click Add file to upload the peer JSON file that was exported from the console where it was originally deployed.
3. If you want to operate the peer (for example, to be able to install smart contracts), click on the tile representing the peer and click Associate identity. Then you will be able to associate an identity from your Wallet with the peer. This identity must be identity that was associated with the CA when it was created.