vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Where



* clusterName is the name of your cluster
* date is the current date







 Step 3. Create the namespace ibm-observe 

This step is only required if you installed the logging agent version 1 in a namespace that is different to ibm-observe.

To check if the namespace exists, run the following command:

kubectl get namespaces

Verify the ibm-observe namespace is active.

If you need to create the namespace, run the following command:

kubectl create namespace ibm-observe





 Step 4. Delete the logging agent version 1 

Run the following command to delete the logging agent version 1:

kubectl delete daemonset logdna-agent -n NAMESPACE

Where NAMESPACE is the namespace in your cluster where the logging agent version 1 is deployed.





 Step 5. Deploy the logging agent version 2 in the cluster 

Choose one of the following commands to install and configure the logging agent:

Command (By using public endpoints)

Command (By using private endpoints)



Table 3. Commands by location when you use public endpoints

 Location Command (By using public endpoints) 

 Chennai (in-che) kubectl apply -f https://assets.in-che.logging.cloud.ibm.com/clients/agent-resources.yaml 
 Dallas (us-south) kubectl apply -f https://assets.us-south.logging.cloud.ibm.com/clients/agent-resources.yaml 
 Frankfurt (eu-de) kubectl apply -f https://assets.eu-de.logging.cloud.ibm.com/clients/agent-resources.yaml 
 London (eu-gb) kubectl apply -f https://assets.eu-gb.logging.cloud.ibm.com/clients/agent-resources.yaml 
 Tokyo (jp-tok) kubectl apply -f https://assets.jp-tok.logging.cloud.ibm.com/clients/agent-resources.yaml
* If you have worker nodes that are attached to an existing subnet in a zone, you can't change the subnet for that zone in the cluster.
* The 172.16.0.0/16, 172.18.0.0/16, 172.19.0.0/16, and 172.20.0.0/16 ranges are prohibited.
* Within one VPC, you can create only one public gateway per zone, but that public gateway can be attached to multiple subnets within the zone.
* The [classic access default address prefixes](https://cloud.ibm.com/docs/vpc?topic=vpc-setting-up-access-to-classic-infrastructureclassic-access-default-address-prefixes) conflict with the subnets for the IBM Cloud Kubernetes Service control plane. You must [create the VPC without the automatic default address prefixes, and then create your own address prefixes and subnets within those ranges for your cluster](https://cloud.ibm.com/docs/containers?topic=containers-vpc-subnetsclassic_access_subnets).









 Creating a VPC subnet and attaching a public gateway 

Create a VPC subnet for your cluster and optionally attach a public gateway to the subnet.



 Creating a VPC subnet in the console 

Use the IBM Cloud console to create a VPC subnet for your cluster and optionally attach a public gateway to the subnet.



1. From the [VPC subnet dashboard](https://cloud.ibm.com/vpc/network/subnets), click Create.
2. Enter a name for your subnet and select the name of the VPC that you created.
3. Select the location and zone where you want to create the subnet.
4. Specify the number of IP addresses to create.



* VPC subnets provide IP addresses for your worker nodes and load balancer services in the cluster, so [create a VPC subnet with enough IP addresses](https://cloud.ibm.com/docs/containers?topic=containers-vpc-subnetsvpc_basics_subnets), such as 256.
: Optional: The Kubernetes version for the cluster master node. When the version is not specified, the cluster is created with the default of supported Kubernetes versions. To see available versions, run ibmcloud ks versions.

--no-subnet
: By default, a public and a private portable subnet are created on the VLAN associated with the cluster. Include the --no-subnet option to avoid creating subnets with the cluster. You can [create](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_cluster_subnet_create) or [add](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_cluster_subnet_add) subnets to a cluster later.

--sm-group GROUP
: The secret group ID of the Secrets Manager instance where your secrets are persisted. To get a secret group ID, see the [Secrets Manager CLI reference](https://cloud.ibm.com/docs/secrets-manager-cli-plugin?topic=secrets-manager-cli-plugin-secrets-manager-clisecrets-manager-secret-groups-cli).

--sm-instance INSTANCE
: The CRN of the Secrets Manager instance. To get the CRN of an instance, run [ibmcloud ks ingress instance ls --cluster CLUSTER](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_ingress_instance_ls).

--private-vlan PRIVATE_VLAN
: This parameter is not available for free clusters. If this standard cluster is the first standard cluster that you create in this zone, don't include this option. A private VLAN is created for you when the cluster is created. If you created a standard cluster before in this zone or created a private VLAN in IBM Cloud infrastructure before, you must specify that private VLAN.
Get your cluster ID.

ibmcloud oc cluster ls
2. Run the following command to create a service ID for the cluster and assign the service ID an IAM Reader service access role for IBM Cloud Container Registry. The command also creates an API key to impersonate the service ID credentials and stores the API key in a Kubernetes image pull secret in the cluster. The image pull secret is in the default Red Hat OpenShift project.

ibmcloud oc cluster pull-secret apply --cluster <cluster_name_or_ID>

When you run this command, the creation of IAM credentials and image pull secrets is initiated and can take some time to complete. You can't deploy containers that pull an image from the IBM Cloud Container Registry icr.io domains until the image pull secrets are created.
3. Verify that the image pull secrets are created in your cluster.

oc get secrets | grep icr-io

Example output

all-icr-io           kubernetes.io/dockerconfigjson        1         16d
4. Update your [container deployments](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_appsimage) to pull images from the icr.io domain name.
5. Optional: If you have a firewall, make sure you [allow outbound network traffic to the registry subnets](https://cloud.ibm.com/docs/openshift?topic=openshift-firewallfirewall_outbound) for the domains that you use.
6. Complete your setup by using one of the following options.



* To pull images in Red Hat OpenShift projects other than default or from other IBM Cloud accounts, [copy or create another image pull secret](https://cloud.ibm.com/docs/openshift?topic=openshift-registryother).
* To restrict the image pull secret access to particular registry resources such as namespaces or regions:



1.
In this tutorial, we can easily access the Org1 MSP because both the peer organization and the ordering service organization were created in the same console. In a production scenario, the MSP definitions of other organization would be created by different network operators in their own cluster using their own IBM Blockchain console. In those cases, when the organization wants to join your consortium, the organization MSP definition of the organization will need to be sent to your console in an out of band operation. Additionally, you will need to export your ordering service and send it to them so they can import it into their console and join a peer to the channel (if they are added to the consortium, they will also be able to create a new channel). This process is described in the Join a network tutorial under [Exporting your organization information](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-join-networkibp-console-join-network-add-org2-remote).





 Create a TLS identity 

This step is needed on clusters that do not use a system channel. You can verify if a cluster does or does not use a system channel by clicking the cluster's tile and looking near the Orderer Type text.

After you click the ordering cluster tile you may see a warning about missing a TLS identity. This identity is a different type than we've used in the past and is only need for orderers that do not have a system channel. This identity is actually the same identity the orderer is using when it enrolls on startup against the TLS CA. To get this identity:



1. From the Nodes tab, select the CA tile that this orderer cluster used (during create)
2. Find the row for the identity this orderer used and click the dot dot dot
3. On the enroll wizard select the TLS CA in the CA drop down (its important to select the TLS CA)
4. Type the enroll secret that was used earlier when creating the orderer
5. Follow any other directions in the enroll wizard and click submit
6. If you browse back to the nodes page and select the Orderer Cluster tile the TLS identity error should be gone
If you don't specify a region, or the specified region is not found, the storage is created in the same region as your cluster. To get the region for your cluster, run ibmcloud oc cluster get --cluster <cluster_name_or_ID> and look for the region prefix in the Master URL, such as eu-de in https://c2.eu-de.containers.cloud.ibm.com:11111. Instead of specifying the region and zone in the PVC, you can also specify these values in a [customized storage class](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storagefile_multizone_yaml). Then, use your storage class in the metadata.annotations.volume.beta.kubernetes.io/storage-class section of your PVC. If the region and zone are specified in the storage class and the PVC, the values in the PVC take precedence.

zone
: Optional: Specify the zone where you want to provision your File Storage for Classic. To use your storage in an app, create the storage in the same zone that your worker node is in. To view the zone of your worker node, run ibmcloud oc worker ls --cluster <cluster_name_or_ID> and review the Zone column of your CLI output. If you specify the zone, you must also specify a region. If you don't specify a zone or the specified zone is not found in a multizone cluster, the zone is selected on a round-robin basis. Instead of specifying the region and zone in the PVC, you can also specify these values in a [customized storage class](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storagefile_multizone_yaml). Then, use your storage class in the metadata.annotations.volume.beta.kubernetes.io/storage-class section of your PVC. If the region and zone are specified in the storage class and the PVC, the values in the PVC take precedence.

accessMode
: Specify one of the following options.
While you wait, you can ensure that the new portable subnets you created for this cluster also appear in the ConfigMap.
9. Create ALBs by using the following command. Note that you can't re-enable the old ALBs because they still use the deleted portable subnet.

ibmcloud ks ingress alb create classic --cluster CLUSTER-ID --type public|private --zone ZONE --vlan VLAN-ID
10. Re-create the LoadBalancers that you deleted by using the YAML file that you saved earlier.

kubectl apply -f LB-NAMESPACE.LB-NAME.yaml
15. Accept the default to store the swapfile in the same directory as the virtual machine and click Next.
16. Click Finish to complete the cluster.
17. Right-click the newly created cluster and select Add Host.
18. Enter the IP address or hostname of one of the vSphere hosts and enter Root in the Username field and the password for the host in the Password field.
19. Click Next through the Host Summary, Assign License, Lockdown Mode screen, and click Finish to complete adding your host to the Cluster
20. Repeat steps 18 and 19 for each other vSphere hosts in your cluster. You see each vSphere hosts under the new cluster after you are done.





 Configuring the basic network construct for the vSphere hosts 

Use the following steps to configure the basic construct for the vSphere hosts in your cluster.



1. Select the first vSphere host and click the Configuration tab.
2. Under Hardware section, select Networking and click Properties next to vSwitch0.
3. Select Network adapters on the vSwitch properties window and click Add.
4. Select vmnic2 to add to vSwitch0 and click Next.
5. Make sure that both vmnics are Active adapters and click Next.
6. Click Finish.
7. Click the Ports tab and make sure that vSwitch is highlighted and click Edit.
8. Click the General Tab and change the MTU to 9000 (jumbo frame).
9. Click the NIC teaming tab and change the load balancing to Route based on IP hash and click OK.
10. Use steps 1 - 8 to configure the vmnics for the other vSphere hosts in your cluster.



Now, you need to add a port group for vMotion. You can create the group a Virtual Standard Switch (VSS) or Virtual Distributed Switch (VDS). Use the following steps to create a VSS switch.



1. Select the Configuration tab and select Networking.
2. Click Properties...
DEBUG:urllib3.connectionpool:https://us.schematics.cloud.ibm.com:443 "GET /v1/workspaces/us-south.workspace.Sample-Schematics-Api-workspace.0f4b9089/actions/34130efab10d7c792e1c357ac4caf6aa HTTP/1.1" 200 None
{
"action_id": "34130efab10d7c792e1c357ac4caf6aa",
"name": "WORKSPACE_CREATE",
"status": "COMPLETED",
"message": [],
"performed_by": "user@us.ibm.com",
"performed_at": "2021-10-18T19:45:10.483538427Z",
"templates": [
{
"template_id": "ea767365-321f-44",
"template_type": "terraform_v0.14",
"start_time": "2021-10-18T19:45:15.467425702Z",
"end_time": "2021-10-18T19:45:28.772465764Z",
"status": "COMPLETED",
"message": "{"messagekey":"M2001_ActivitySuccessful","parms":{},"requestid":"2236dccc-4f75-4b2c-9fe5-ccaa7be8aae5","timestamp":"2021-10-18T19:45:28.772468053Z"}",
For more information, see [Trusted Profile ID](https://cloud.ibm.com/docs/schematics?topic=schematics-agent-trusted-profile).







 Provision the Agent infrastructure through UI 

You can use Schematics to provision the Agent infrastructure in your IBM Cloud account. The Agent infrastructure is composed of the following resources.



* [VPC infrastructure](https://cloud.ibm.com/docs/vpc?topic=vpc-iam-getting-started) as public_gateways, subnets.
* [IKS](https://cloud.ibm.com/docs/containers?topic=containers-access_reference) as vpc_kubernetes_cluster.
* [LogDNA](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-iam)
* [Activity tracker](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-iam)





1. Log in to [IBM Cloud](https://cloud.ibm.com/).
2. Navigate to Schematics > Workspaces > [Create workspace](https://cloud.ibm.com/schematics/workspaces/create) with the following inputs to create an Agent infrastructure workspace.



* In Specify Template section:



* GitHub, GitLab or Bitbucket repository URL - https://github.com/Cloud-Schematics/schematics-agents/tree/main/templates/infrastructure.
* Personal access token - <leave it blank>.
* Terraform Version - terraform_v1.0. Note that you need to select Terraform version 1.0 or greater than version.
* Click Next.



* In Workspace details section:



* Workspace name as schematics-agent-infra_workspace.
* Tags as agents-infra.
* Resource group as default or other resource group for this workspace.
curl -X POST https://schematics.cloud.ibm.com/v1/workspaces -H 'authorization: <auth>' -H 'cache-control: no-cache' -H 'content-type: application/json' -d '{
"name": "smulampa-schematics-agent-service-workspace",
"type": [
"terraform_v1.0"
],
"description": "schematics agents service workspace",
"template_repo": {
"url": ""
},
"template_data": [{
"folder": ".",
"type": "terraform_v1.0",
"variablestore": {
"name": "agent_prefix",
"type": "string",
"value": "myproject-agent"
},
{
"name": "location",
"type": "string",
"value": "us-south"
},
{
"name": "resource_group_name",
"type": "string",
"value": "Default"
}
]
}]
}'
2. Run [workspace get](https://cloud.ibm.com/apidocs/schematics/schematicsget-workspace) to list the workspaces.

curl -X GET https://schematics.cloud.ibm.com/v1/workspaces/{w_id} -H 'authorization: <auth>' -H 'cache-control: no-cache' -H 'content-type: application/json'
3. Run [workspace upload](https://cloud.ibm.com/apidocs/schematics/schematicstemplate-repo-upload) to upload agent-service-templates.tar file.
* Change the API endpoint to the endpoint mentioned in [API endpoints](https://cloud.ibm.com/apidocs/schematics?code=pythonapi-endpoints) according to the location that you want your Schematics workspace to reside, for example, schematics_service.set_service_url('https://us.schematics.cloud.ibm.com').
* Provide environment values that you want to have in the form of a key and value pair, such as [{ 'Environment': 'hpc-dev-cluster' }]
* Change the folder location variable template_source_data_request_model['folder'] to the folder name inside your GitHub repository where your Terraform files reside. If the Terraform files exist in the base location of your repository, then set this variable to template_source_data_request_model['folder'] = ' '; otherwise, mention the folder name in the template_source_data_request_model['folder'] variable.
* Change the template_source_data_request_model['type'] variable to the Terraform version that you are using to create IBM Cloud resources such as terraform_v0.13. Ensure that your Terraform templates are compatible with the version that you are mentioning in this field.
* Provide your GitHub or GitLab Repository HTTPS URL where your Terraform files reside in the template_repo_request_model['url'] variable. If you are using the [public repository](https://github.com/IBM/ibm-spectrum-scale-ibm-cloud-schematics) that is provided by IBM Cloud, then set this variable as template_repo_request_model['url'] = 'https://github.com/IBM/ibm-spectrum-scale-ibm-cloud-schematics'; otherwise, set it to the private repository you are using.



4. Inside the schematics_service.create_workspace function, provide the following parameters:



* Provide an optional description.
* Provide a name to identify your Schematics workspace, for example, terraform-dev-workspace.
--options or -o Optional Enter the option flag that you want to show. 
 --address or -adr Optional Enter the address of the resource to mark as untaint. 



Example

ibmcloud schematics workspace untaint --id myworkspace-asdff1a1a-42145-11 --address null_resource.sleep





 ibmcloud schematics workspace update 

IBM Cloud Schematics deprecates older version of Terraform. For more information, see [Deprecating older version of Terraform process in IBM Cloud Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-deprecate-tf-version).

Update the details for an existing workspace, such as the workspace name, variables, or source control URL. To provision or modify IBM Cloud, see the [ibmcloud schematics plan](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-plan) command.

IBM Cloud Schematics supports 50 API requests per minute, per host, and per customer. The region can be us-east, us-south, eu-gb, or eu-de region. You need to wait before calling the command again. Ensure the location and the url endpoint are pointing to the same region when you create or update workspaces and actions. For more information about location and endpoint, see [Where is my information stored?](https://cloud.ibm.com/docs/schematics?topic=schematics-secure-datapi-location).

If you provided your Terraform template by uploading a tape archive file (.tar) and you want to update your template, you must use the [ibmcloud schematics workspace upload](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-upload) command.

Syntax
schematics,sch output Get all the output values from your workspace; (ex. result of terraform output command
schematics,sch version Report version information about the IBM Cloud Schematics CLI.
schematics,sch logs Show details about actions that ran against an workspace.
schematics,sch state Advanced state management
schematics,sch kms listing and enabling IBM Cloud Schematics kms instances and root keys .
schematics,sch inventory,iv Create and manage Schematics Inventories. Inventory let you define host group that can contain INI or Resource Query id's
schematics,sch resource-query,rq Create and manage Schematics Resource Query. Resource query let you define conditions to fetch host group that can be used to perform actions
schematics,sch agents,ags [Deprecated] Agents extends Schematics ability to reach your private, or on-premises, infrastructure.
schematics,sch blueprint,bp Deploy and manage large scale environments using reusable blueprint templates.
schematics,sch agent,ag [Beta] Agents extends Schematics ability to reach your private, or on-premises infrastructure. Integrate Schematics Agent running in your private network to the IBM Cloud Schematics service to provision, configure, and operate your private or on-premise cloud resources. Visit https://cloud.ibm.com/docs/schematics?topic=schematics-agents-intro to learn more.
schematics,sch policy,plcy [Beta] Create and manage policies







 Uninstalling the IBM Cloud Schematics command-line plug-in 

Uninstall the IBM Cloud Schematics plug-in to remove the Schematics plugin from your local system.



1. Uninstall the IBM Cloud command-line plug-in for Schematics.

ibmcloud plugin uninstall schematics

Example output:

Uninstalling plug-in 'schematics'...
OK
Plug-in 'schematics' was successfully uninstalled.
2.
<br> User responsibility:<br> * Create your own Terraform templates or use one of the provided sample templates to configure the resources that you want.<br> * Design the source repository structure, and set up and manage the source repository for your Terraform template.<br> * Understand the IBM Cloud® resource offerings that are used in your templates, including availability, pricing, limitations, and the tools to set up security, high availability, and logging and monitoring.<br> * Design and provision your resources in a way that achieves high availability and resiliency, such as [multizone clusters](https://cloud.ibm.com/docs/containers?topic=containers-ha_clustersmz-clusters) or [multi-region VPCs](https://cloud.ibm.com/docs/vpc?topic=solution-tutorials-vpc-multi-regionvpc-multi-region).<br> * Use the provided tools to [provision](https://cloud.ibm.com/docs/schematics?topic=schematics-manage-lifecycledeploy-resources), [modify](https://cloud.ibm.com/docs/schematics?topic=schematics-manage-lifecycleupdate-resources), or [delete](https://cloud.ibm.com/docs/schematics?topic=schematics-manage-lifecycledestroy-resources) your IBM Cloud resources.<br> * Set up logging and monitoring for your resources to track resource activity and monitor the resource health, such as with [IBM Log Analysis](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-getting-started) and [IBM Cloud Monitoring](https://cloud.ibm.com/docs/monitoring?topic=monitoring-getting-started).<br><br><br>
ibmcloud schematics apply --id us-east.workspace.testwspace01feb.b5e8fdaa
Do you really want to perform this action? [y/N]> Y

Activity ID df51c0e61a020592d3403a05d08692d7

OK


On successful plan it returns the update details of an existing workspace.

For more information about FAQ, see [troubleshooting section](https://cloud.ibm.com/docs/schematics?topic=schematics-wks-create-api&interface=cli).







 Perform the workspace deploy using the API 



1. Follow the [steps](https://cloud.ibm.com/docs/schematics?topic=schematics-setup-apics_api) to retrieve your IAM access token and authenticate with IBM Cloud Schematics by using the API.
2. Perform deploy for the existing workspace.

Example

PUT /v1/workspaces/{w_id}/apply HTTP/1.1
Host: schematics.cloud.ibm.com
Content-Type: application/json
Authorization: <auth-token>
Cache-Control: no-cache
Postman-Token: 77ef7f05-7290-0b60-781c-f8c147c78ed2

{
"name": "testworkspacejanATTest",
"type": [
"terraform_v0.13"
],
"description": "terraform workspace",
"tags": [
"test:bbbranch"
],
"template_repo": {
"url": "https://github.com/srikar-git/tf_cloudless_sleepy/tree/v0.13"
},
"template_data": [{
"folder": ".",
"type": "terraform_v0.13",