vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Managing classic infrastructure access 

When you invite a user to your account, you can select from three classic infrastructure permission sets that assign bulk access: View only, Basic user, Super user. You can update permissions for classic infrastructure services or add device and VPN subnet access for a user at any time. To access the classic infrastructure permissions, go to Manage > Access (IAM) in the IBM Cloud® console, select Users. Then, select the user's name that you want to update access for, and click Classic infrastructure.



 Classic infrastructure permissions 

When you invite someone to the account, only you, the account owner, or a user with the Manage user classic infrastructure permission, can adjust the permissions for the user. You can assign only the level of permissions or a subset of the permission that you're already assigned, if you're not the account owner. An account owner can update anyone's permissions in the account to have any level of access.

Extra permissions can be set after the user accepts the invitation. For example, the initial permission set assigned on the invitation doesn't grant access to devices. So, you must grant device access after the user accepts the invitation.

Support center account management access is recommended for users working with classic infrastructure resources. To perform many tasks when working with classic infrastructure resources, such as creating or deleting a virtual server instance, users must have access to work with support cases. For more information about assigning this type of access, see [Assigning access to account management services](https://cloud.ibm.com/docs/account?topic=account-account-services).

The following graphic shows how classic infrastructure permissions are assigned per user. You can grant each user access to a classic infrastructure service or device by selecting from the granular permission options to customize each user's access.

Zoom

![Classic infrastructure access](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/BlockStorage/includes/account/includes/account/images/ClassicIaaS.svg)

Figure 1.
Managing classic infrastructure access 

When you invite a user to your account, you can select from three classic infrastructure permission sets that assign bulk access: View only, Basic user, Super user. You can update permissions for classic infrastructure services or add device and VPN subnet access for a user at any time. To access the classic infrastructure permissions, go to Manage > Access (IAM) in the IBM Cloud® console, select Users. Then, select the user's name that you want to update access for, and click Classic infrastructure.



 Classic infrastructure permissions 

When you invite someone to the account, only you, the account owner, or a user with the Manage user classic infrastructure permission, can adjust the permissions for the user. You can assign only the level of permissions or a subset of the permission that you're already assigned, if you're not the account owner. An account owner can update anyone's permissions in the account to have any level of access.

Extra permissions can be set after the user accepts the invitation. For example, the initial permission set assigned on the invitation doesn't grant access to devices. So, you must grant device access after the user accepts the invitation.

Support center account management access is recommended for users working with classic infrastructure resources. To perform many tasks when working with classic infrastructure resources, such as creating or deleting a virtual server instance, users must have access to work with support cases. For more information about assigning this type of access, see [Assigning access to account management services](https://cloud.ibm.com/docs/account?topic=account-account-services).

The following graphic shows how classic infrastructure permissions are assigned per user. You can grant each user access to a classic infrastructure service or device by selecting from the granular permission options to customize each user's access.

Zoom

![Classic infrastructure access](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/account/images/ClassicIaaS.svg)

Figure 1.
Managing classic infrastructure access 

When you invite a user to your account, you can select from three classic infrastructure permission sets that assign bulk access: View only, Basic user, Super user. You can update permissions for classic infrastructure services or add device and VPN subnet access for a user at any time. To access the classic infrastructure permissions, go to Manage > Access (IAM) in the IBM Cloud® console, select Users. Then, select the user's name that you want to update access for, and click Classic infrastructure.



 Classic infrastructure permissions 

When you invite someone to the account, only you, the account owner, or a user with the Manage user classic infrastructure permission, can adjust the permissions for the user. You can assign only the level of permissions or a subset of the permission that you're already assigned, if you're not the account owner. An account owner can update anyone's permissions in the account to have any level of access.

Extra permissions can be set after the user accepts the invitation. For example, the initial permission set assigned on the invitation doesn't grant access to devices. So, you must grant device access after the user accepts the invitation.

Support center account management access is recommended for users working with classic infrastructure resources. To perform many tasks when working with classic infrastructure resources, such as creating or deleting a virtual server instance, users must have access to work with support cases. For more information about assigning this type of access, see [Assigning access to account management services](https://cloud.ibm.com/docs/account?topic=account-account-services).

The following graphic shows how classic infrastructure permissions are assigned per user. You can grant each user access to a classic infrastructure service or device by selecting from the granular permission options to customize each user's access.

Zoom

![Classic infrastructure access](https://cloud.ibm.com/docs-content/v1/content/921d024aca5ff45536208840a52f864567eb4068/Backup/includes/account/includes/account/images/ClassicIaaS.svg)

Figure 1.
Managing classic infrastructure access 

When you invite a user to your account, you can select from three classic infrastructure permission sets that assign bulk access: View only, Basic user, Super user. You can update permissions for classic infrastructure services or add device and VPN subnet access for a user at any time. To access the classic infrastructure permissions, go to Manage > Access (IAM) in the IBM Cloud® console, select Users. Then, select the user's name that you want to update access for, and click Classic infrastructure.



 Classic infrastructure permissions 

When you invite someone to the account, only you, the account owner, or a user with the Manage user classic infrastructure permission, can adjust the permissions for the user. You can assign only the level of permissions or a subset of the permission that you're already assigned, if you're not the account owner. An account owner can update anyone's permissions in the account to have any level of access.

Extra permissions can be set after the user accepts the invitation. For example, the initial permission set assigned on the invitation doesn't grant access to devices. So, you must grant device access after the user accepts the invitation.

Support center account management access is recommended for users working with classic infrastructure resources. To perform many tasks when working with classic infrastructure resources, such as creating or deleting a virtual server instance, users must have access to work with support cases. For more information about assigning this type of access, see [Assigning access to account management services](https://cloud.ibm.com/docs/account?topic=account-account-services).

The following graphic shows how classic infrastructure permissions are assigned per user. You can grant each user access to a classic infrastructure service or device by selecting from the granular permission options to customize each user's access.

Zoom

![Classic infrastructure access](https://cloud.ibm.com/docs-content/v1/content/009f5721283adef7a1874103d11c5b438182c4d7/virtual-servers/includes/account/includes/account/images/ClassicIaaS.svg)

Figure 1.
Managing classic infrastructure access 

When you invite a user to your account, you can select from three classic infrastructure permission sets that assign bulk access: View only, Basic user, Super user. You can update permissions for classic infrastructure services or add device and VPN subnet access for a user at any time. To access the classic infrastructure permissions, go to Manage > Access (IAM) in the IBM Cloud® console, select Users. Then, select the user's name that you want to update access for, and click Classic infrastructure.



 Classic infrastructure permissions 

When you invite someone to the account, only you, the account owner, or a user with the Manage user classic infrastructure permission, can adjust the permissions for the user. You can assign only the level of permissions or a subset of the permission that you're already assigned, if you're not the account owner. An account owner can update anyone's permissions in the account to have any level of access.

Extra permissions can be set after the user accepts the invitation. For example, the initial permission set assigned on the invitation doesn't grant access to devices. So, you must grant device access after the user accepts the invitation.

Support center account management access is recommended for users working with classic infrastructure resources. To perform many tasks when working with classic infrastructure resources, such as creating or deleting a virtual server instance, users must have access to work with support cases. For more information about assigning this type of access, see [Assigning access to account management services](https://cloud.ibm.com/docs/account?topic=account-account-services).

The following graphic shows how classic infrastructure permissions are assigned per user. You can grant each user access to a classic infrastructure service or device by selecting from the granular permission options to customize each user's access.

Zoom

![Classic infrastructure access](https://cloud.ibm.com/docs-content/v1/content/04e9937a86546143babfc65ea21fdd4ea2d12d13/FileStorage/includes/account/includes/account/images/ClassicIaaS.svg)

Figure 1.
: Required: The name or ID of the cluster.

--zone ZONE
: Required: The zone that you want to remove.

-p, --worker-pool WORKER_POOL
: The name of the worker pool to remove the zone from. To specify multiple worker pools, use multiple options, such as -p pool1 -p pool2. To remove the zone from all worker pools in the cluster, don't include this option.

-f
: Optional: Force the command to run with no user prompts.

-q
: Optional: Do not show the message of the day or update reminders.



 Example zone rm command 

ibmcloud oc zone rm --zone dal10 --cluster my_cluster









 ingress commands 

View and configure Ingress application load balancers (ALBs).

In CLI version 1.0.157 and later, the ibmcloud oc alb category is deprecated, and these commands are now listed in the ibmcloud oc ingress alb subcategory. For more information, see the [CLI change log](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_cli_changelog10).



 ibmcloud oc ingress alb autoupdate disable 

Virtual Private Cloud

Classic infrastructure

Disable automatic updates of all Ingress ALB pods in a cluster.

By default, automatic updates to Ingress application load balancers (ALBs) are enabled. ALB pods are automatically updated when a new image version is available. To instead update the add-on manually, use this command to disable automatic updates. You can then update ALB pods by running the [ibmcloud oc ingress alb update command](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_alb_update).

When you update the major or minor Kubernetes version of your cluster, IBM automatically makes necessary changes to the Ingress deployment, but does not change the image version of your Ingress ALB add-on.
* Distribute resources across three zones: With this option, you deploy two cores per zone, which leaves you with a total capacity of six cores. To handle your workload, two zones must be up at a time. If one zone is unavailable, the other zone can fully handle your workload. If two zones are unavailable, the two remaining cores are up to handle your parts of your workload, and you could temporarily add another worker node to that zone.







 How is my IBM Cloud Kubernetes Service master set up? 

When you create a cluster in a multizone location, a highly available master is automatically deployed and three replicas are spread across the zones of the metro. For example, if the cluster is in dal10, dal12, or dal13 zones, the replicas of the master are spread across each zone in the Dallas multizone metro.





 Do I have to do anything so that the master can communicate with the workers across zones? 

If you created a VPC multizone cluster, the subnets in each zone are automatically set up with Access Control Lists (ACLs) that allow communication between the master and the worker nodes across zones. In classic clusters, if you have multiple VLANs for your cluster, multiple subnets on the same VLAN, or a multizone classic cluster, you must enable a [Virtual Router Function (VRF)](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf) for your IBM Cloud infrastructure account so your worker nodes can communicate with each other on the private network. To enable VRF, see [Enabling VRF](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf). To check whether a VRF is already enabled, use the ibmcloud account show command. If you can't or don't want to enable VRF, enable [VLAN spanning](https://cloud.ibm.com/docs/vlans?topic=vlans-vlan-spanningvlan-spanning).
VRVDR-45949 Minor Netflow generates a NOTICE log for every sample sent when certain non-key fields are configured 
 VRVDR-43169 Minor Logging everytime one calls a configd C based API but doesn't supply an error struct is no longer useful 
 VRVDR-41225 Minor When configuring interface description, every white space is treated as a new line 







 Security Vulnerabilities Resolved 



Security vulnerabilities resolved for 1801z

 Issue Number CVSS score Advisory Summary 

 VRVDR-46824 N/A DSA-4440-1 CVE-2018-5743, CVE-2018-5745, CVE-2019-6465: Debian DSA-4440-1 : bind9 - security update 
 VRVDR-46603 5.3 DSA-4435-1 CVE-2019-7317: Debian DSA-4435-1 : libpng1.6 - security update 
 VRVDR-46425 N/A DSA-4433-1 CVE-2019-8320, CVE-2019-8321, CVE-2019-8322, CVE-2019-8323, CVE-2019-8324, CVE-2019-8325: Debian DSA-4433-1 : ruby2.3 - security update 
 VRVDR-46350 9.1 DSA-4431-1 CVE-2019-3855, CVE-2019-3856, CVE-2019-3857, CVE-2019-3858, CVE-2019-3859, CVE-2019-3860, CVE-2019-3861, CVE-2019-3862, CVE-2019-3863: Debian DSA-4431-1 : libssh2 - security update 









 1801y 



 Issues Resolved 



Issues resolved for 1801y

 Issue Number Priority Summary 

 VRVDR-46029 Major VRRP authentication either with simple text password or AH type does not work properly 
 VRVDR-45864 Critical Shell injection privilege escalation/sandbox escape in vyatta-techsupport remote copy
* [Removing worker nodes from a dedicated host in the CLI](https://cloud.ibm.com/docs/containers?topic=containers-dedicated-hostsremove-worker-nodes-cli)
* [Removing dedicated hosts in the CLI](https://cloud.ibm.com/docs/containers?topic=containers-dedicated-hostsremove-dedicated-hosts-cli)
* [Removing dedicated hosts pools in the CLI](https://cloud.ibm.com/docs/containers?topic=containers-dedicated-hostsremove-dedicated-host-pool-cli)





 Autoscaling clusters 

[Preparing classic and VPC Gen 2 clusters for autoscaling](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-classic-vpccluster-scaling-classic-vpc)



* [Understanding scale-up and scale-down](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-classic-vpcca_about)
* [Following scalable deployment practices](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-classic-vpcscalable-practices)



* [Can I autoscale multiple worker pools at once?](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-classic-vpcscalable-practices-multiple)
* [How can I make sure that the cluster autoscaler responds to what resources my app needs?](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-classic-vpcscalable-practices-resrequests)
* [Can I scale down a worker pool to zero (0) nodes?](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-classic-vpcscalable-practices-zero)
* [Can I optimize my deployments for autoscaling?]
VRVDR-27018 Critical Running configuration file is globally readable 









 5.2R6S 

Released May 8, 2018.



 Issues Resolved 



Issues resolved in 5.2R6S

 Issue Number Priority Summary 

 VRVDR-40803 Minor VIF interfaces are not present in “show vrrp” output after a reboot 







 Security Vulnerabilities Resolved 



Security vulnerabilities resolved in 5.2R6S

 Issue Number CVSS score Advisory Summary 

 VRVDR- 41512 9.8 DSA-4172-1 CVE-2018-6797, CVE-2018-6798, CVE-2018-6913: Debian DSA-4172-1: perl – security update 









 5.2R6S8 

Released April 16, 2018.



 Issues Resolved 



Issues resolved in 5.2R6S8

 Issue Number Priority Summary 

 VRVDR-41283 Minor Configd stops processing static routes during boot if the configuration has disabled static routes 







 Security Vulnerabilities Resolved 



Security vulnerabilities resolved in 5.2R6S8

 Issue Number CVSS score Advisory Summary 

 VRVDR- 41330 6.5 DSA-4157-1 CVE-2017-3738, CVE-2018-0739: Debian DSA-4157-1: openssl – security update 









 5.2R6S7 

Released March 15, 2018.



 Issues Resolved 



Issues resolved in 5.2R6S7

 Issue Number Priority Summary 

 VRVDR-38801 Major Multi-segment packet received via IPsec VTI causes bond interface to go down 









 5.2R6S6 

Released March 12, 2018.



 Issues Resolved 



Issues resolved in 5.2R6S6

 Issue Number Priority Summary 

 VRVDR-40281 Major After upgrading from 5.2 to more recent version error “vbash: show: command not found” in operation mode 
 VRVDR-40135 Major Spanning tree packets are not received on a VIF interface bridge port 
 VRVDR-39991 Major Stateful firewall drops packets between two subnets on the same interface
volume_ID
: The unique ID that is assigned to your Block Storage for Classic volume. You can retrieve a list of your Block Storage for Classic volumes by running ibmcloud is volumes.

Example response.

{
"id": "0111-1aaa11a1-aa1a-111a-111b-1111a1dad1bc",
"volume": {
"name": "my-vol",
"id": "r001-11aa0d59-a1aa-1a11-11ca-ba2bc11e01aa"
},
"device": {
"id": ""
},
"name": "volume-attachment",
"status": "attaching",
"type": "data"
}
7. Verify the attachment by [reviewing existing volume attachments for a VPC worker node](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesvpc_api_get_worker).





 Detaching raw and unformatted Block Storage for Classic from a worker node in a VPC cluster by using the API 

You can use a DELETE request to detach storage from a VPC worker node.

Detaching storage from your VPC cluster does not remove your Block Storage for Classic volume or the data that is stored in the volume. You continue to get billed until [you manually delete the volume](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storage).



1. Identify the storage volume that you want to remove and note the volume ID.

ibmcloud is volumes
2. Get details about the volume. This command returns the worker node ID and attachment ID. Note the worker node ID. In the following command this ID is returned as "Instance name".

ibmcloud is volume <volume_ID>
3. Retrieve a list of your PVs. This command returns a list of your PVs that you can then you use to determine which PVC uses the volume that you want to remove.
volume_ID
: The unique ID that is assigned to your Block Storage for Classic volume. You can retrieve a list of your Block Storage for Classic volumes by running ibmcloud is volumes.

Example response.

{
"id": "0111-1aaa11a1-aa1a-111a-111b-1111a1dad1bc",
"volume": {
"name": "my-vol",
"id": "r001-11aa0d59-a1aa-1a11-11ca-ba2bc11e01aa"
},
"device": {
"id": ""
},
"name": "volume-attachment",
"status": "attaching",
"type": "data"
}
7. Verify the attachment by [reviewing existing volume attachments for a VPC worker node](https://cloud.ibm.com/docs/openshift?topic=openshift-utilitiesvpc_api_get_worker).





 Detaching raw and unformatted Block Storage for Classic from a worker node in a VPC cluster by using the API 

You can use a DELETE request to detach storage from a VPC worker node.

Detaching storage from your VPC cluster does not remove your Block Storage for Classic volume or the data that is stored in the volume. You continue to get billed until [you manually delete the volume](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storage).



1. Identify the storage volume that you want to remove and note the volume ID.

ibmcloud is volumes
2. Get details about the volume. This command returns the worker node ID and attachment ID. Note the worker node ID. In the following command this ID is returned as "Instance name".

ibmcloud is volume <volume_ID>
3. Retrieve a list of your PVs. This command returns a list of your PVs that you can then you use to determine which PVC uses the volume that you want to remove.
Instead of making more clusters, you can add worker pools for different flavors of computing resources available for the app and service components that you want to use. When you develop the app, the resources it uses are in the same zone, or otherwise closely connected in a multizone, so that you can make assumptions about latency, bandwidth, or correlated failures. However, it becomes even more important for you to organize your cluster by using namespaces, resource quotas, and labels.





 How can I set up my resources within the cluster? 



 Consider your worker node capacity 

To get the most out of your worker node's performance, consider the following: - Keep up your core strength: Each machine has a certain number of cores. Depending on your app's workload, set a limit for the number of pods per core, such as 10. - Avoid node overload: Similarly, just because a node can contain more than 100 pods doesn't mean that you want it to. Depending on your app's workload, set a limit for the number of pods per node, such as 40. - Don't tap out your cluster bandwidth**: Keep in mind that network bandwidth on scaling virtual machines is around 1000 Mbps. If you need hundreds of worker nodes in a cluster, split it up into multiple clusters with fewer nodes, or order bare metal nodes. - Sorting out your services: Plan out how many services that you need for your workload before you deploy. Networking and port forwarding rules are put into Iptables. If you anticipate a larger number of services, such as more than 5,000 services, split up the cluster into multiple clusters.





 Provision different types of machines for a mix of computing resources 

Everyone likes choices, right? With Red Hat OpenShift on IBM Cloud, you have [a mix of flavors](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesplanning_worker_nodes) that you can deploy: from bare metal for intensive workloads to virtual machines for rapid scaling. Use labels or namespaces to organize deployments to your machines. When you create a deployment, limit it so that your app's pod deploys only on machines with the best mix of resources.