vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can modify the list of allowed locations where an access request can originate. A set of one or more network locations can be specified by IP addresses (individual addresses, ranges, or subnets), VPCs, or service references. You can update a network zone that is used in a rule, or integrate the new updated network zones into your rules later.



1. In the IBM Cloud console, click Manage > Context-based restrictions, and select Network zones.
2. Select the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) on the network zone that you want to update, and select Edit.
3. You can update your zone name and description.
4. You can edit the list of allowed IP addresses where an access request can originate. Include exceptions in the deny list, if necessary.
5. You can add or remove allowed VPCs.
6. You can add or remove service references. Select a service to associate its IP addresses with your network zone.
7. Click Next to review your new configuration.
8. To apply changes, click Update.







 Updating network zones by using the CLI 

To update a network zone, complete the following steps.



1. Retrieve the zone ID for the network zone that you want to update by using the [ibmcloud cbr zones](https://cloud.ibm.com/docs/account?topic=cli-cbr-plugin&interface=clicbr-cli-zones-command) command to list all zones in the account.

ibmcloud cbr zones
2. Update the network zone by using the [ibmcloud cbr zone-update](https://cloud.ibm.com/docs/account?topic=cli-cbr-plugin&interface=clicbr-cli-zone-update-command) command.
You can upgrade the auto-negotiation policy by using the UI, CLI, or API.



 Before you begin 

You will experience a network outage during the upgrade. The duration of the outage depends on the interval between the disable and re-enable actions to reestablish the VPN connection. It is recommended that you plan a maintenance window for this upgrade.

Before you upgrade, review the following information:



* By default, the new auto-negotiation policy is used for newly created VPN connections. For more information, see [About policy negotiation](https://cloud.ibm.com/docs/vpc?topic=vpc-using-vpnpolicy-negotiation).
* Because IBM Cloud auto-negotiation uses IKEv2, the on-prem device must also use IKEv2. If your on-prem device does not support IKEv2, see [upgrading VPN from a custom IKE or IPsec policy](https://cloud.ibm.com/docs/vpc?topic=vpc-upgrading-weak-ciphersupgrade-vpn-with-custom-policy).
* It is a good idea to first configure your on-prem VPN gateway peer to replace the weak ciphers for Phase 1 and Phase 2 negotiation with the secure ciphers that are described in [policy negotiation](https://cloud.ibm.com/docs/vpc?topic=vpc-using-vpnpolicy-negotiation). Then, upgrade the VPN gateway to use the enhanced auto-negotiation policy. This step might also reduce the outage time.



For an existing VPN connection that uses the old auto-negotiation policy (created before 20 September 2022), complete the following steps to upgrade to the new auto-negotiation policy.





 Upgrading the auto-negotiation policy in the UI 

To upgrade the auto-negotiation policy by using the UI, follow these steps:



1. From the VPNs for VPC page, select Site-to-site gateways > VPN gateways.
2. Select the VPN gateway that contains the VPN connection that you want to upgrade.
3.
You can modify the list of allowed locations where an access request can originate. A set of one or more network locations can be specified by IP addresses (individual addresses, ranges, or subnets), VPCs, or service references. You can update a network zone that is used in a rule, or integrate the new updated network zones into your rules later.



1. In the IBM Cloud console, click Manage > Context-based restrictions, and select Network zones.
2. Select the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/d4595e5202a9a27767cf034e81b038cdf772e0d5/secure-enterprise/includes/account/includes/icons/action-menu-icon.svg) on the network zone that you want to update, and select Edit.
3. You can update your zone name and description.
4. You can edit the list of allowed IP addresses where an access request can originate. Include exceptions in the deny list, if necessary.
5. You can add or remove allowed VPCs.
6. You can add or remove service references. Select a service to associate its IP addresses with your network zone.
7. Click Next to review your new configuration.
8. To apply changes, click Update.







 Updating network zones by using the CLI 

To update a network zone, complete the following steps.



1. Retrieve the zone ID for the network zone that you want to update by using the [ibmcloud cbr zones](https://cloud.ibm.com/docs/account?topic=cli-cbr-plugin&interface=clicbr-cli-zones-command) command to list all zones in the account.

ibmcloud cbr zones
2. Update the network zone by using the [ibmcloud cbr zone-update](https://cloud.ibm.com/docs/account?topic=cli-cbr-plugin&interface=clicbr-cli-zone-update-command) command.
* UI
* CLI
* API







 Updating an access request 

As the owner of the account the access request comes to, you can update the properties of an access request by using the UI, CLI, or API.

The following table describes the actions you can take as the account owner.



Table 1. Owner states

 Action Description 

 Approve Grants access to establish a linked zone. 
 Reject Denies the access request. 
 Revoke Removes access requests that were granted previously. 
 No action The request times out if you take no action after 7 days elapse. 





 Updating an access request using the UI 

To update an access request using the UI, take the following steps:



1. Navigate to the Zones section of your DNS Services instance.
2. Click the link in the Name column of the request you want to review.
3. Select the Cross-account ACL tab.
4. Click overflow menu ![Overflow menu icon](https://cloud.ibm.com/docs-content/v1/content/d56dbd8ab7d14086029681ee71679e14aea53723/dns-svcs/images/overflow-icon.png) of the linked zone for which you want to manage an access request.
5. Select Review request.
6. Select Reject or Approve to complete the request, or click the X at the top right of the side panel to close the request and take no action.







 Updating an access request using the CLI 

To update an access request using the CLI, run the following command:

ibmcloud dns cross-account access-request-update ZONE_ID REQUEST_ID --action ACTION [-i, --instance INSTANCE] [--output FORMAT]

Where:



* ZONE_ID is the ID of the owner's zone.
* REQUEST_ID is the ID of the access request.
* --action value is the action applied to the access request. Valid values: "APPROVE", "REJECT", "REVOKE".
* -i, --instance value is the instance name or ID.
if not p'locationGroupId']]
prices.append(price_id)

return prices

def get_subnet_id(self, datacenter):
"""Find and returns the first subnet in the datacenter"""

_filter = {"privateSubnets": {
"networkVlan": {
"primaryRouter": {
"datacenter": {
"regions": { "keyname": { "operation": datacenter}}
}
},
"type": { "keyName": { "operation": "STANDARD" } }
},
"routingTypeKeyName": {"operation": "PRIMARY" }
}
}

subnets = self.client['Account'].getPrivateSubnets(filter=_filter)

return subnets[0]

def order_lbaas(self, pkg_name, datacenter, name, desc, protocols,
subnet_id=None, public=False, verify=False):
"""Allows to order a Load Balancer"""

package_id = self.get_package_id(pkg_name)
prices = self.get_item_prices(package_id)

 Find and select a subnet id if it was not specified.
if subnet_id is None:
subnet_id = self.get_subnet_id(datacenter)

 Build the configuration of the order
orderData = {
'complexType': 'SoftLayer_Container_Product_Order_Network_LoadBalancer_AsAService',
'name': name,
'description': desc,
'location': datacenter,
'packageId': package_id,
'useHourlyPricing': True, Required since LBaaS is an hourly service
'prices': [{'id': price_id} for price_id in prices],
'protocolConfigurations': protocols,
This action replaces the existing MSP definition for the ordering service admin with the updated MSP with the new admin certificate.







 Step seven: Update orderer organization MSP on channel 

Similar to step four, this update needs to be performed by a channel operator and the change will follow the channel update approval process according to the policy that was configured when the channel was created.

If the orderer organization MSP was not originally created with the Node OU configuration enabled, you also need to update all application channels that include the MSP so that it will use the new admin certificate. When the Node OU configuration is enabled, the MSP uses the value of the OU inside the certificate to determine if the identity is an admin in addition to checking the admin section of the MSP definition.

Complete the following steps for an orderer organization admin certificate:

Orderer organization admin identities cannot update an application channel. Therefore, a consortium member needs to import the updated orderer organization admin MSP into their console and then complete the following steps:



1. Open the application channel to be updated in the console.
2. Click Channel details and scroll down to Orderer members.
3. Click the orderer member that you want to update.
4. On the Update MSP definition panel, select the updated MSP and click Update MSP definition. An update notification request is generated.
5. The orderer organization admin needs to approve the request and submit it to the channel.









 Certificates from an external CA 

Some customers prefer to use a third-party, or "external" CA to generate their peer and ordering node enrollment and TLS certificates, as well as the organization admin certificates. But, similar to certificates generated by a Fabric CA, they do expire, and their expiration date needs to be monitored to avoid a network outage caused by their expiry. And like certificates generated by a Fabric CA, expiration dates of certificates from an external CA are visible throughout the console. Before the certificates expire you need to request new certificates from your certificate provider, and then use the console to update them across your network. The process to update them using the console depends on the certificate type.



 Peer and ordering node enrollment and TLS certificates
From the version list that's displayed on the product details page, click the row that contains your software.
2. Review the version details, and click Next.







 Operator from Red Hat registry 



1. From the version list that's displayed on the product details page, click the row that contains your software.
2. Review the version details, and click Next.







 OVA image 



1. From the version list that's displayed on the product details page, click the row that contains your software.
2. Review the version details, and click Next.







 Virtual server image with Terraform 



1. From the version list that's displayed on the product details page, click the row that contains your software.
2. Review the version details, and click Next.
3. Configure the deployment values.
4. If applicable, edit the output value descriptions, and click Next.
5. Define the required IAM access, and click Next.







 Virtual server image for VPC 



1. From the version list that's displayed on the product details page, click the row that contains your software.
2. Review the list of images, and click Next.
3. Review the version details, and click Next.









 Adding license agreements 

Provide the URLs to the license agreements that users are required to accept when they install the product. The license agreements are in addition to the IBM Cloud Services Agreement.



1. Click Add license agreements > Add license.
2. Enter the name and URL, and click Update > Next.







 Editing your readme file 

When users install the software, they can view product information by clicking the Readme file link. This information is generated from the readme file that you uploaded to your source repository.



1. From the Edit readme tab, preview how the information in the readme file will be displayed to users when they install the software.
2. To make updates, click the Edit icon !
* UI
* CLI
* API







 Updating trusted profiles 

You can update the permissions or redefine trust relationships for trusted profiles at any time by using either the console or the [IAM Identity Services](https://cloud.ibm.com/apidocs/iam-identity-token-apicreate-claim-rule-request) API.

To update trusted profiles, you must be assigned the administrator, operator, or editor role within the account, or on the IAM Identity Service.

You can use Activity Tracker to monitor which federated users and compute resources apply a trusted profile. For more information, see [Monitoring login sessions for trusted profiles](https://cloud.ibm.com/docs/account?topic=account-trusted-profile-monitor).



 Updating trusted profiles in the console 

To update trusted profiles, go to Manage > Access (IAM) in the IBM Cloud console, and select Trusted profiles. Then, select the name of the trusted profile that you want to update.



 Updating the description of your profile 

Click the name of the trusted profile that you want to update, and select Actions > Edit. Enter the new name and description, and click Apply.





 Redefining the trust relationship 

After the trusted profile is created, you can build trust with both federated users and compute resources in the same trusted profile.



1. Click the name of the trusted profile that you want to update.
2. Click Add to add a condition to the existing trust relationship. To edit an existing condition, click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) > Edit next to the trust relationship you want to update.



* Click Add a condition and repeat as needed to add more conditions.
* To remove a condition, click the Remove icon !
In the Summary pane, the promotion code appears.
10. Enter the promotion code in the Apply a code field and click Apply.
11. Review the license agreement and select the checkbox to acknowledge the agreement.
12. Click Create. The IBM Cloud® manage resource page is displayed.

After you click Create, the message stating that the “instance is being provisioned” is displayed and you are taken to the Resource list. From the Resource list, under Databases category, you can see that the status for your instance is, Provision in progress.
13. Select the instance when the status changes to Active.
14. Go to Resource list>Databases.
15. Click your watsonx.data instance link. The service instance page opens.
16. Click Open web console to start the web console.
17. Log in to the console with your IBMid and password. The watsonx.data web console opens.



You can also apply the promotion code directly from your IBM Cloud® promo credit dashboard.





 Step 3: Setting spending notification 

You can set up email spending notifications. You receive notifications when you reach 80%, 90%, and 100% of the spending thresholds that you specify.

Promotion code consumption does not trigger spend notifications. You can trigger spending notification only after the promo code is consumed. You must choose an amount that you are comfortable spending after the promo code is consumed. Spend notifications trigger on an hourly basis after promo credit is consumed. For example, if you set a spend notification of $20, you receive a notification within 2 hours after the full consumption of the promo credit (for example $1,500).



1. In the IBM Cloud® console, go to Manage > Billing and usage, and select Spending notifications.
2. Set the Enable option to on for the specific service area to enable email notifications.
3. Click the Edit option from the Actions icon.
4. Next, you can add email recipients. You can select up to 10 users from your IBM Cloud® account to receive email notifications about a service.
5. Enter the dollar amount to set a spending threshold.
In the IBM Cloud® console, go to Manage > Billing and usage, and select Spending notifications.
2. Set the Enable option to on for the specific service area to enable email notifications.
3. Click the Edit option from the Actions icon.
4. Next, you can add email recipients. You can select up to 10 users from your IBM Cloud® account to receive email notifications about a service.
5. Enter the dollar amount to set a spending threshold.
6. When you are finished, click Save to save your changes.







 Step 4: Viewing usage 

You can also monitor the promotion credit usage level and plan subscription in the IBM Cloud® Console.



1. In the IBM Cloud® console, go to Manage > Billing and usage. Select Promotions and credits.
2. Click a promotion to expand the table and view a description of each promotion and the products it applies to.
3. If your promo credits are exhausted and you do not want to continue paying, you must manually delete your watsonx.data instance by following the steps:



1. Log in to your IBM Cloud® account.
2. From the Resource list, select your deployment.
3. Click Delete from the list.









 Step 5: Getting started with watsonx.data 

When you log in to the watsonx.data web console for the first time, you are presented with the quick start wizard.

Use the quick start wizard to configure the basic settings and get started with watsonx.data in a few minutes.

In this section of the tutorial, you perform the following:



* Register the details of the object storage bucket.
* Add the metadata catalogs to manage your table schemas.
* Select the query engine to work with your data.



Complete the following steps:



1. In the Bucket configuration page, select Provision new IBM-managed bucket.
2. Click Next. This displays the Catalogs configuration page.
3. In the Catalogs configuration page, select a catalog.
4. Click Next. This displays the Engine configuration page.
5.
Code support and SDK API usage and tuning are not included in support - [community support only](https://cloud.ibm.com/docs/blockchain?topic=blockchain-blockchain-supportblockchain-general-support). 
 Hyperledger Fabric Chaincode Basic chaincode diagnostics is supported. Code support and tuning are not included in support - [community support only](https://cloud.ibm.com/docs/blockchain?topic=blockchain-blockchain-supportblockchain-general-support). 
 Deployment Architecture and Design Basic deployment and management of highly available [peer](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-haibp-console-ha-peers), [orderer](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-haibp-console-ha-ordering-service), and [Certificate Authority](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-haibp-console-ha-ca) nodes via the Console are supported. Detailed Deployment Architecture and Design are not included in support - see [deployment options](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deployment) for more information. 
 Solution Architecture and Design [Deploying and managing smart contracts](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2) via the Console are supported. Solution Architecture and Design are not included in support. 
 Performance Tuning [Resource allocation](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-options) via the Console is supported.
Can I add a broker per location? 

No. Brokers are added per pricing plan, not per location. And, brokers can't be disconnected from already approved plans.





 Can I set different locations per plan for a single product? 

Yes. But, all plans for a single product must be set as either global or per location. Therefore, you can't have a plan that is set to global and then another plan set to be available for specific regions. This means that all plans are set as global, or you can select the per location option, and specify different regions and data centers per plan. This applies to all new products. If you have a migrated product that has global and per location plans already set up, no changes have been made to your migrated product, but all new products must have plans that use either global or per location options.





 Why can't I edit my support information? 

The support details that you previously provided to IBM aren't currently displayed on the Support tab in Partner Center, but they have been saved and are still available for all of your published products. We are improving the support details experience in Partner Center, so if you need to make any changes, we ask that you contact support. No information was lost or changed during the migration, and all of your published products include your support details. For information about opening a support case, see [Creating a Partner Center support case](https://cloud.ibm.com/docs/sell?topic=sell-get-pc-supportpc-support-case).





 Where is my custom agreement? 

Any previously approved custom agreements are saved and still valid. If you need to upload a new version of the custom agreement for review and approval, you can do this from the My company page. On the My company page, click Edit and expand the Upload the custom agreement that you company has made with IBM Cloud. You can drag and upload the custom agreement file, and it will be reviewed by IBM.
For more information about instance limits, see [FAQ: Virtual servers](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-faqs-virtual-serversconcurrent).







 Next steps 

After you provision a virtual server that supports suspend billing, you can start suspend and resume billing on the device.

When billing is suspended on a virtual server instance, you can't complete all of the same actions on the instance until you resume billing for the device. You can view whether your device is stopped, and the relevant date when the status changed, through the SoftLayer API or by accessing the Device details page in the IBM Cloud infrastructure customer portal.

To suspend billing on a virtual server instance, power off the virtual server. For more information, see [Managing virtual servers](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-virtual-servers).