vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can give users access to view private catalogs and catalog filters, create private catalogs, add software to private catalogs, and set catalog filters.



Table 5. Roles and example actions for the catalog management service

 Roles Actions role_ID value 

 Viewer View account-level filters set for the IBM Cloud catalog<br><br>View private catalogs crn:v1:bluemix:public:iam::::role:Viewer 
 Operator Create private catalogs<br><br>Set filters for private catalogs<br><br>Add and update software<br><br>View account-level filters crn:v1:bluemix:public:iam::::role:Operator 
 Editor Create private catalogs<br><br>Set filters for private catalogs<br><br>Add and update software<br><br>View account-level filters crn:v1:bluemix:public:iam::::role:Editor 
 Administrator Set account-level filters for the IBM Cloud catalog<br><br>Create, update, and delete private catalogs<br><br>Publish IBM-approved products<br><br>Assign access policies crn:v1:bluemix:public:iam::::role:Administrator 
 Publisher Publish products that are approved by IBM from a private catalog crn:v1:bluemix:public:globalcatalog-collection::::serviceRole:Promoter 







 Context-based restrictions 

You can give users access to view, create, update, and remove network zones. To create a context-based restriction rule for a service, you must be assigned an IAM policy with the Administrator role the service you are creating a rule against. For example, if you want to create a rule to protect a Key Protect instance, you must be assigned the Administrator role on the Key Protect service and the Viewer role or higher on the Context-based restrictions service.

The Viewer role on the Context-based restrictions service allows you to add network zones to your rule.



Table 6. Roles and example actions for the context-based restrictions service

 Roles Actions role_ID value
* Start date (when the machine was ordered and provisioned)



While the private IP address of the NetScaler is listed, the public IP address of the NetScaler is not. This is because management of the NetScaler is done using the private IP address, and the public IP addresses for NetScaler devices are used as the device's VIP(s) or Virtual IP(s), which are used for load balancing services.





 The device details screen 

Clicking on the NetScaler's name takes you to the Device Details page for the NetScaler, which shows the VLAN on which your NetScaler was deployed, as well as your public IP addresses for the NetScaler. These IP addresses cannot be used for management, because they are the NetScaler's default public VIP addresses. You use these later to associate to a load balancing service.





 Connecting to the NetScaler 

IBM Cloud grants full root access to your NetScaler device. To log into the NetScaler's Management UI, you must be connected to the IBM Cloud private network either the IBM Cloud Management VPN, or performing management functions from a remote session on a server within the IBM Cloud environment.

To connect from the catalog to the NetScaler's Management UI, click the Actions menu list and choose Manage Device to launch a new tab or pop-up window in your browser. This routes you to the NetScaler's NSIP (the private IP address that you saw previously). The page that displays asks for the root username and password for the device. After you enter the information, it takes you to the NetScaler Management GUI.

Alternatively, you can copy and paste the NetScaler device's private IP into a web browser.



 NetScaler SSH access 

You can also connect to the NetScaler device directly using your favorite SSH client. Use the private IP and login information for the NetScaler device from the device list page and make sure you are connected to the IBM Cloud VPN.







 Caution regarding HA configurations and portal passwords 

You must keep your Cloud portal root username and password consistent with the root username and password of the physical device. If these are not kept consistent, upgrades and licensing operations can fail, resulting in production outages.
The default value is false.

--user, -u
: The user ID (UID) that is used to run the application. This value overrides any user ID that is set in the application Dockerfile. The ID must conform to the operating system requirements of the container. This value is optional. The default value is 0.

--visibility, -v
: The visibility for the application. Valid values are public, private and project. Setting a visibility of public means that your app can receive requests from the public internet or from components within the Code Engine project. Setting a visibility of private means that your app is not accessible from the public internet and network access is only possible from other IBM Cloud using Virtual Private Endpoints (VPE) or Code Engine components that are running in the same project. Visibility can only be private if the project supports application private visibility. Setting a visibility of project means that your app is not accessible from the public internet and network access is only possible from other Code Engine components that are running in the same project. This value is optional.

--wait, -w
: Update the application and wait for the application to be ready. If you specify the --wait option, the application update waits for a maximum time in seconds, as set by the --wait-timeout option, for the application to become ready. If the application is not ready within the specified --wait-timeout period, the application create fails. This value is optional. The default value is true.

--wait-timeout, --wto
: The length of time in seconds to wait for the application to be updated. This value is required if the --wait option is specified. This value is ignored if the --no-wait option is specified. The default value is 600.





 Example 

ibmcloud ce application update --name myapp --image icr.io/codeengine/hello





 Example output 

Updating application 'myapp' to latest revision.
[...]
Run 'ibmcloud ce application get -n myapp' to check the application status.
OK
ibmcloud target -g <resource_group_name>
3. Get the name of your cluster.

ibmcloud ks cluster ls
4. Retrieve the service endpoint URLs for your cluster.



* If only the Public Service Endpoint URL is populated, get this URL. Your authorized cluster users can access the master through this endpoint on the public network.
* If only the Private Service Endpoint URL is populated, get this URL. Your authorized cluster users can access the master through this endpoint on the private network.
* If both the Public Service Endpoint URL and Private Service Endpoint URL are populated, get both URLs. Your authorized cluster users can access the master through the public endpoint on the public network or the private endpoint on the private network.



ibmcloud ks cluster get --cluster <cluster_name_or_ID>

Example output

...
Public Service Endpoint URL: https://c3.<region>.containers.cloud.ibm.com:30426
Private Service Endpoint URL: https://c3-private.<region>.containers.cloud.ibm.com:31140
...
5. Allow access to the service endpoint URLs and ports that you got in the previous step. If your allowlist is IP-based, you can see which IP addresses are opened when you allow access to the service endpoint URLs by reviewing [this table](https://cloud.ibm.com/docs/containers?topic=containers-firewallmaster_ips).
6. Verify your connection.



* If the public cloud service endpoint is enabled:

curl --insecure <public_service_endpoint_URL>/version

Example command:

curl --insecure https://c3.<region>.containers.cloud.ibm.com:31142/version

Example output

{
"major": "1",
"minor": "7+",
"gitVersion": "v1.7.4-2+eb9172c211dc41",
Private catalogs provide a way for you to make your own products available to users in your account.



1. Go to Manage > Catalogs in the IBM Cloud console, and click Create a catalog.
2. Select Product default as the catalog type.
3. Enter the name of your catalog, for example, Sample Operator Bundle.
4. Select No products to exclude all products in the IBM Cloud® catalog from your catalog.
5. Click Create.







 Step 2: Import your Operator bundle 



1. On the Private products page, click Add.
2. Select Operator from Red Hat registry as your deployment method.
3. Select Certified as your Red Hat repository.
4. Select your Operator bundle. For example, for the purposes of this tutorial, you can select Add a Cluster Operator as your Operator.
5. Select the Operator bundle version that you would like to import.
6. Enter the software version that the Operator bundle installs in the format of major version, minor version, and revision. For example, you can use Operator version 1.0.0 to install software version 2.0.0.
7. Click Add version.







 Step 3: Review the version details 



1. From the Version list table, click the row that contains your operator.
2. Review your version details from the Review the version details section. There are no actions that you need to take. When you are ready to move on, click Next.







 Step 4: Add end user license agreements 

If users are required to accept any license agreements beyond the IBM Cloud Services Agreement, provide the URL to each agreement.



1. In the Version list table, click the row that contains your Operator bundle.
2. Click Add license agreements > Add.
3. Enter the name and URL of the license agreement, and click Update.
4. After entering all additional license agreements, click Next.







 Step 5: Review your readme file 

When users install the software, they can select the link to your readme file to view product information.
05:5e:49:90:fa:6b:f1:38:48:c9:db:34:1e:53:4b:84:75:0b:8f:b1 PrivateKey /Users/hexiaohu/.hpnet-cfg/hpnet-test2-71-20-39-e8.priv 
 ef:ff:ad:46:2a:b4:0b:32:38:7f:29:7f:15:a1:a3:bd:71:20:39:e8 PublicKey /Users/hexiaohu/.hpnet-cfg/hpnet-test2-71-20-39-e8.pub 
+-------------------------------------------------------------+------------+---------------------------------------------------------+

An automatically generated keypair is stored locally and configured to node remotely.
The keypair is required to keep carefully!!!

OK
Show more







 Retrieve the private key 

If you do not move the generated private key, the file path can be automatically parsed during fetching of the admin public key.

ibmcloud hpnet adminkey get

Select the HPVS instance for '--instance'

Select a virtual server:
1. hpnet-test1 - crn:v1:staging:public:hpvs:dal10:a/9f63166137084e9d9131e42bfce481a6:8ba48f91-ef4a-4433-b411-fd8b2becc18b::
2.
* Command options

--crn HPCS_CRN
: Required. The crn of your Hyper Protect Crypto Services instance. You can use the ibmcloud resource service-instances --long command to retrieve the crn.

--admin-priv-key ADMIN_PRIV_KEY
: Required. The file path of your current private key that is stored on your local workstation. The private key is used to sign this command action toward your instance certificate manager server.

--private
: Optional. If you use this option, the certificate manager server URL points to the private network. For example,: cert-mgr.private.<region>.hs-crypto.cloud.ibm.com:443. The region is the abbreviation of the geographic area where you log in to IBM Cloud. In this case, you need to use the private network to connect your service instance.
* Example

export HPCS_CRN=crn:v1:staging:public:xxx:yyy:zzz

export ADMIN_PRIV_KEY=/Users/admin1/.hpcs-cert-mgr-cfg/44de77d2-599b-0089-2f0f-bad8d1c94a7c.priv

ibmcloud hpcs-cert-mgr adminkey delete --crn ${HPCS_CRN} --admin-priv-key ${ADMIN_PRIV_KEY}
* Output

The command returns the output similar to the following example:

connecting to server [cert-mgr.us-south.hs-crypto.cloud.ibm.com:443]...
command completed successfully.







 hpcs-cert-mgr cert get 

Use this command to retrieve the client certificate on your instance certificate manager server.

ibmcloud hpcs-cert-mgr cert get --crn HPCS_CRN --cert-id CERT_ID [--cert-store-file CERT_FILE] [--private]



* Command options
export ADMIN_PRIV_KEY=/Users/admin1/.hpcs-cert-mgr-cfg/44de77d2-599b-0089-2f0f-bad8d1c94a7c.priv

ibmcloud hpcs-cert-mgr adminkey update --crn ${HPCS_CRN} --admin-priv-key ${ADMIN_PRIV_KEY}
* Output

The command returns the output similar to the following example:

connecting to server [cert-mgr.us-south.hs-crypto.cloud.ibm.com:443]...
+------------+-----------------------------------------------------------------------------------+
 KEYTYPE FILE 
+------------+-----------------------------------------------------------------------------------+
 PrivateKey /Users/username/.hpcs-cert-mgr-cfg/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.priv 
 PublicKey /Users/username/.hpcs-cert-mgr-cfg/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.pub
Before disabling a public endpoint (--public-enabled FALSE), make sure your account has access to the private endpoint. You can do this by running the command bx account show. If VRF Enabled is true and Service Endpoint Enabled is true then you have access to the private endpoint. If you do not have access to the private endpoint, you will be unable to re-enable the public endpoint since private endpoint access is required to re-enable the public endpoint.



 Command options 

--region <REGION> | -r <REGION>
: Name of the region, for example, us-south or eu-gb. If not specified, the region logged into, or targeted, will be used.

--output JSON
: If specified, output will be returned in JSON format. If JSON is not specified, output will be returned in a tabular format.

--force
: The command will be run without prompting the user whether or not to continue with the command.

help | --help | -h
: List options available for the command.







 ibmcloud atracker endpoint api update --public-enabled TRUE 

You can configure for each region the availability of public endpoints so that you can configure IBM Cloud Activity Tracker Event Routing resources in your account.

You can use the following command to enable a public endpoint in a region:

ibmcloud atracker endpoint api update --public-enabled TRUE [--region <REGION>] [--output JSON] [--force]

You must have access to a private endpoint to enable a public endpoint.



 Command options 

--region <REGION> | -r <REGION>
: Name of the region, for example, us-south or eu-gb. If not specified, the region logged into, or targeted, will be used.

--output JSON
: If specified, output will be returned in JSON format. If JSON is not specified, output will be returned in a tabular format.

--force
: The command will be run without prompting the user whether or not to continue with the command.
Private URL: https://private.us-south.atracker.cloud.ibm.com
Private Enabled: true







 Disabling public endpoints using the CLI 

You can disable public endpoints per region in your account.

You can use the following command to disable a public endpoint in a region:

ibmcloud atracker endpoint api update --public-enabled FALSE [--region <REGION>] [--output JSON] [--force]

Before disabling a public endpoint (--public-enabled FALSE), make sure your account has access to the private endpoint. You can do this by running the command bx account show. If VRF Enabled is true and Service Endpoint Enabled is true then you have access to the private endpoint. If you do not have access to the private endpoint, you will be unable to re-enable the public endpoint since private endpoint access is required to re-enable the public endpoint.



 Command options 

--region <REGION> | -r <REGION>
: Name of the region, for example, us-south or eu-gb. If not specified, the region logged into, or targeted, will be used.

--output JSON
: If specified, output will be returned in JSON format. If JSON is not specified, output will be returned in a tabular format.

--force
: The command will be run without prompting the user whether or not to continue with the command.

help | --help | -h
: List options available for the command.





 Example 

The following is an example using the ibmcloud atracker endpoint api update --public-enabled false command.

Are you sure you want to update the IBM Cloud Activity Tracking service endpoint settings for your account? [y/N]> y
OK
API endpoints for region us-south
Public URL: https://us-south.atracker.cloud.ibm.com
Public Enabled: false
Private URL: https://private.us-south.atracker.cloud.ibm.com
Private Enabled: true
For more information, see [Restricting domains for account invitations](https://cloud.ibm.com/docs/account?topic=account-restrict-acct-invite).







 November 2021 



 8 November 2021 

Data centers closed in 2021
: The following list shows the locations with the associated data centers and specific PODs that were closed by 08 November 2021.



* Dallas: DAL05 – POD2
* Houston: HOU02
* Melbourne: MEL01
* Oslo: OSL01
* Washington DC: WDC01 – POD3 and POD4



For more information about upcoming data center closures, see [Data center consolidations](https://cloud.ibm.com/docs/get-support?topic=get-support-dc-closure).





 1 November 2021 

Accessing Partner Center from the IBM Cloud catalog
: As a third-party provider, you can now click Sell on IBM Cloud to access Partner Center directly from the IBM Cloud catalog. For more information, see the [catalog](https://cloud.ibm.com/catalog).







 October 2021 



 25 October 2021 

Securing IBM Cloud accounts
: Our focus is to provide the most secure public cloud. That's why we will be verifying user identities and securing accounts through credit card verification when creating new accounts starting 25 October 2021. Don't worry, we won't charge you for signing up, and you can still try IBM Cloud for free. For more information, see [Securing IBM Cloud accounts](https://www.ibm.com/cloud/blog/announcements/securing-ibm-cloud-accounts).





 05 October 2021 

Suspending and deprecating private products
: As a private catalog owner, you can now suspend or deprecate software that's in your private catalogs. When you suspend a version of software, it's immediately removed from your private catalog. When you deprecate software, it remains available to users with access to the private catalog for 90 days. After 90 days, it's permanently removed.
curl -X GET <ENDPOINT>/api/v2/routes -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json"

Where



* <ENDPOINT> is the API endpoint in the region where you plan to configure or manage a route. For more information, see [Endpoints](https://cloud.ibm.com/docs/atracker?topic=atracker-endpointsendpoints_api).



For example, you can run the following cURL request to get information about the routes that are defined in US South:

curl -X GET https://private.us-south.atracker.cloud.ibm.com/api/v2/routes -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json"





 HTTP response codes 

When you use the Activity Tracker Event Routing REST API, you can get standard HTTP response codes to indicate whether a method completed successfully.



* A 200 response always indicates success.
* A 4xx response indicates a failure.
* A 5xx response usually indicates an internal system error.



See the following table for some HTTP response codes:



Table 2. List of HTTP response codes

 Status code Status Description 

 200 OK The request was successful. 
 201 OK The request was successful. A resource is created. 
 400 Bad Request The request was unsuccessful. You might be missing a parameter that is required. 
 401 Unauthorized The IAM token that is used in the API request is invalid or expired. 
 403 Forbidden The operation is forbidden due to insufficient permissions. 
 404 Not Found The requested resource doesn't exist or is already deleted. 
 429 Too Many Requests Too many requests hit the API too quickly. 
 500 Internal Server Error Something went wrong in Activity Tracker Event Routing processing.
ibmcloud target -g <resource_group_name>
3. Get the name of your cluster.

ibmcloud oc cluster ls
4. Retrieve the service endpoint URLs for your cluster.



* If only the Public Service Endpoint URL is populated, get this URL. Your authorized cluster users can access the master through this endpoint on the public network.
* If only the Private Service Endpoint URL is populated, get this URL. Your authorized cluster users can access the master through this endpoint on the private network.
* If both the Public Service Endpoint URL and Private Service Endpoint URL are populated, get both URLs. Your authorized cluster users can access the master through the public endpoint on the public network or the private endpoint on the private network.



ibmcloud oc cluster get --cluster <cluster_name_or_ID>

Example output

...
Public Service Endpoint URL: https://c3.<region>.containers.cloud.ibm.com:30426
Private Service Endpoint URL: https://c3-private.<region>.containers.cloud.ibm.com:31140
...
5. Allow access to the service endpoint URLs and ports that you got in the previous step. If your allowlist is IP-based, you can see which IP addresses are opened when you allow access to the service endpoint URLs by reviewing [this table](https://cloud.ibm.com/docs/openshift?topic=openshift-firewallmaster_ips).
6. Verify your connection.



* If the public cloud service endpoint is enabled:

curl --insecure <public_service_endpoint_URL>/version

Example command:

curl --insecure https://c3.<region>.containers.cloud.ibm.com:31142/version

Example output

{
"major": "1",
"minor": "7+",
You can choose a different VLAN if you already have one in your selected data center. For more information, see [About VLANs](https://cloud.ibm.com/docs/vlans?topic=vlans-about-vlans). 
 Private and public subnet Selecting a subnet is optional and to be used only when you require your device to use an IP address from the subnet. If you select a subnet, verify that you have enough IP addresses to fulfill the request. If you do not have enough IP addresses for your subnet, your order can be delayed or canceled. For more information, see [About subnets and IPs](https://cloud.ibm.com/docs/subnets?topic=subnets-about-subnets-and-ipsabout-subnets-and-ips). 







 Network interface add-ons 



Table 4. Network interface add-ons

 Field Details 

 Bandwidth Bandwidth allocation is not included with transient virtual server instances. 
 Hardware and software firewalls Firewall services prevent unwanted traffic on your servers, reduce the likelihood of an attack, and allow your server resources to be dedicated for their intended use. 
 Primary IP address A primary IP address is automatically assigned to your instance. 
 Public secondary IP addresses These subnets are owned by you during your virtual server instance ownership. You can cancel the subnet separately, but if you cancel your instance, the subnet is also removed. For more information, see [About subnets and IPs](https://cloud.ibm.com/docs/subnets?topic=subnets-about-subnets-and-ipsabout-subnets-and-ips). 
 IPv6 and public static IPv6 addresses You can select an IPv6 address or public static IPv6 addresses for your instance. 
 VPN management This option is automatically selected for your instance with unlimited SSL VPN users. For more information, see [About VPN](https://cloud.ibm.com/docs/iaas-vpn?topic=iaas-vpn-getting-started). 



You can also provision a transient virtual server by using the SoftLayer API.