vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ibmcloud cis logpush-job DNS_DOMAIN_ID --dataset DATASET] --jobid JOB_ID] -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-command-options-logpush-job" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.--dataset value: The category of logs you want to receive. This value cannot be changed after the job is created. Valid values: http_requests, range_events, firewall_events. The default value is http_requests.--jobid value: JOB_ID is the ID of logpush job.-i , --instance value: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-command-options-logpush-job" "> --><-- <section "id="section-command-example-logpush-job" "> --> Examples Get details of http_requests log push job. ibmcloud cis logpush-job 31984fea73a15b45779fa0df4ef62f9b --dataset http_requests -i cis-demo --output JSON
<-- </section "id="section-command-example-logpush-job" "> --><-- </section "id="section-logpush-job" "> --><-- <section "id="section-logpush-job-delete" "> --> ibmcloud cis logpush-job-delete Delete a log push job for a given domain (Enterprise plan only). ibmcloud cis logpush-job-delete DNS_DOMAIN_ID --dataset DATASET] --jobid JOB_ID] -f, --force] -i, --instance INSTANCE] ! ! !
curl -X GET $DNSSVCS_ENDPOINT/v1/instances/$INSTANCE_ID/dnszones -H "Authorization: $TOKEN"





 Response 

{
"success": true,
"result": [
{
"id": "example.com:ed10e4b2-8a64-4afa-a4e2-9e60a766d079",
"created_on": "2019-07-24 12:30:58.357201205 +0000 UTC",
"modified_on": "2019-07-24 12:30:58.357201205 +0000 UTC",
"instance_id": "1a34bda8-9c94-4232-bea7-7df163b21d23",
"name": "example.com",
"description": "Example zone",
"state": "PENDING_NETWORK_ADD"
}
],
"errors": [],
"messages": []
}







 Deleting a DNS zone 



 Request 

curl -X DELETE $DNSSVCS_ENDPOINT/v1/instances/$INSTANCE_ID/dnszones/$DNSZONE_ID -H "Authorization: $TOKEN"





 Response 

HTTP/2 204 No Content









 Using the CLI 

Follow these [instructions](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-cli-plugin-dns-services-cli-commandscli-ref-prereqs) to install DNS Services CLI plugin.

First use ibmcloud dns instances command to list the DNS Services instances and then use the ibmcloud dns instance-target command to set the target operating DNS Services instance.

$ ibmcloud dns instances
Retrieving service instances for service 'dns-svcs' ...
OK

Name ID Location State Service Name
The private DNS servers resolve this information over the private network to keep your bandwidth usage down, reduce the load on the authoritative servers, and offer quick resolution. Private network resolvers are a convenience service for our customers.
* What are my name server options?

With a bare metal server there are four typical options for name servers:



* Use your domain name registrar's name servers to manage your domain names.
* Use IBM Cloud name servers to manage your domain names.
* Use a third-party DNS service to manage your domain names.
* Run your own name servers on your server to manage your domain names.



For the first three options, you will use name servers of the third party (for example, ns1.softlayer.com and ns2.softlayer.com). The last option uses your domain as the name server (for example, ns1.yourdomain.com and ns2.yourdomain.com), and it requires you to run DNS services on your server. You must also register your domain as a name server with your registrar. Name server registration is usually free, but it requires an additional step beyond the basic domain name registration process.

Our customers have free DNS services that are fully managed through the [IBM Cloud console](https://%7BDomainName%7D/). It is highly recommended that you allow IBM Cloud to manage your DNS and your name servers, due to our redundant systems, ease of management, and ability to troubleshoot DNS-related issues quickly.
* How do I renew my domain name?

To renew a registration for an existing domain, select [Classic Infrastructure](https://%7BDomainName%7D/gen1/infrastructure/devices) from the menu in the IBM Cloud console, and then go to Services > Domain Registration. See [Renewing existing domains](https://cloud.ibm.com/docs/dns?topic=dns-renew-an-existing-domain).
* Where do I find cost estimates for domain name registration?

You can estimate the cost of a service using the cost estimator on the provisioning pages for domain name registration.
* --dns-servers: Space separated list of DNS Servers to use for this network.
* --gateway: Gateway to use for this network.
* --ip-range: IP addresses range or ranges for this network.
* --json: Format output in JSON.



--------------------







 ibmcloud pi network-create-public 



 Create a public network 

ibmcloud pi network-create-public NETWORK_NAME [--dns-servers "DNS1 DNS2"] [--json]



* NETWORK_NAME: The name of the network.



Options



* --dns-servers: Space separated list of DNS Servers to use for this network.
* --json: Format output in JSON.



--------------------







 ibmcloud pi network-delete 



 Delete a network 

ibmcloud pi network-delete NETWORK_ID



* NETWORK_ID: The unique identifier or name of the network.



--------------------







 ibmcloud pi network-update 



 Update a network 

ibmcloud pi network-update NETWORK_ID [--name NETWORK_NAME] [--starting-ip IP] [--ending-ip IP] [--dns-servers "DNS1 DNS2"] [--gateway GATEWAY] [--json]



* NETWORK_ID: The unique identifier or name of the network.



Options



* --name: New name of the network.
* --dns-servers: Space separated list of new DNS Servers to use for this network.
* --gateway: New gateway to use for this network.
* --ip-range: New IP addresses range or ranges for this network.
* --json: Format output in JSON.



--------------------







 ibmcloud pi networks 



 List all networks
In this example, a single DNS zone, widgets.example.com will be created and access to the DNS zone will be permitted to all the VPCs. The DNS service instance is created by the network team (Editor role) and permitting the zones requires the Manager role. DNS resolution at run time in an instance on a VPC does not require IAM access. The shared team needs to list the DNS instances (Viewer role) and add an A or CNAME record (Manager role).

[VPC](https://cloud.ibm.com/docs/vpc) Infrastructure Service (IS) consists of about 15 different service types. Some are only of concern to the network team, like network ACLs (access control lists). Others are only of concern to the microservice teams, like VSI instances. But some are edited by the network team and operated by the microservice team, like subnets. The network team will create the subnet and a microservice team will create an instance in a subnet. For the purpose of this tutorial the VPC IS service types, Transit Gateway and DNS are summarized for each access group in the table below. The contents of the table are the required roles.



Required roles assigned to teams based on their responsibilities

 Service network shared application 

 Transit Gateway Editor, Manager 
 DNS Editor, Manager Viewer, Manager 
 IS: Network ACL Editor 
 IS: Instance, Volume, Floating IP, SSH Key, Image, Load Balancer Editor Editor 
 IS: VPC, Subnet, Security Group Editor Operator Operator 







 Resource Groups 

The shared team and the network team are now nicely separated. But how is Application1 isolated from Shared and Application2? They are Editor for the same types of services.

This is where resource groups can help out. Each service instance (i.e. resource) has a resource group attribute that is initialized upon creation and cannot be changed. In other words, each resource is in one resource group.

Resource Group diagram:

Zoom

!
* If You are hosting Your domain's name servers ("DNS") on IBM Cloud's servers, or are using IBM Cloud’s systems to forward a domain, URL, or otherwise to a system or site hosted elsewhere, or if You have Your domain name registered with IBM Cloud, You are responsible for ensuring that there is no excessive overloading on IBM Cloud's DNS systems.
* You may not use IBM Cloud's servers and/or Your domain as a source, intermediary, reply-to address, or destination address for mail bombs, Internet packet flooding, packet corruption, server hacking, security breaches or other abusive attacks. You agree that IBM Cloud reserves the right to deactivate Your domain name from its DNS system if IBM Cloud deems it is the recipient of activities caused by Your site that threaten the stability of its network.
* You agree that IBM Cloud, in its sole discretion and without liability to You, may refuse to accept the registration of any domain name. IBM Cloud also may, in its sole discretion and without liability to You, delete the registration of any domain name during the first thirty (30) days after registration has taken place. IBM Cloud may also cancel the registration of a domain name, after thirty (30) days, if that name is being used in association with spam or morally objectionable activities. Morally objectionable activities include, but are not limited to: activities designed to defame, embarrass, harm, abuse, threaten, slander or harass third parties; activities prohibited by the laws of the United States and/or foreign territories in which You conduct business; activities designed to encourage unlawful behavior by others, such as hate crimes, terrorism and child pornography; activities that are tortious, vulgar, obscene, invasive of the privacy of a third party, racially, ethnically, or otherwise objectionable; activities designed to impersonate the identity of a third party; and activities designed to harm minors in any way. In the event IBM Cloud refuses a registration or deletes an existing registration during the first thirty (30) days after registration, You will receive a refund of any fees paid to IBM Cloud in connection with the registration either being canceled or refused, unless the deletion was the result of the domain name being used in association with spam or morally objectionable activities, in which case, no refund will be issued.
Troubleshooting CIS error codes 

Here are some common error messages you or your support team might see:



Table 1. Error codes

 Error Code  Reason                                                                                                                                                                                                                                           

 1001        DNS Resolution Error. Either the customer recently signed up and their DNS information has not yet propagated, or whomever is managing the DNS has a failure.                                                                                    
 521         Origin web server refused connection from CIS. Either the origin web server is not running, or something is blocking CIS IP addresses.                                                                                                           
 522         Connection timeout to the origin server (30 second default). Either CIS might be rate-limited, the web server could be consuming all resources (shared server), or there might be network connectivity issues between the web server and CIS.    
 523         Origin server is unreachable. Ensure that the origin IP address for the DNS record is the same as the one appearing in the CIS DNS Settings page.                                                                                                
 524         CIS could make a TCP connection but did not receive a response from the web server. A long-running application or database query is interfering.                                                                                                 





  502 error “The dreaded 502” 

This error is one of the most common ones you might see. It typically occurs when a portion of a network is unavailable; for example, at the start of a DDoS attack. A particular data center might be unavailable for a time. Traffic is re-routed. It is recommended that you run a trace route.

Here is what you might see: Error 502 - bad gateway error

What happened:



*  A portion of the CIS network is having an issue.
*  Usually the problem is limited to one server in one data center.
*  It affects only a portion of the site's visitors.
*  The CIS Technical Operations team deals with these.



What you can do:



*  Send the results from www.YOUR_DOMAIN.com/cdn-cgi/trace in a case to [IBM Support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar).
*  Temporarily toggle your DNS Records to off (No proxy).
Use the following command to update an existing zone. You can update the description and label fields. All other fields are read-only.



 Request update a DNS zone 

curl -X PATCH $DNSSVCS_ENDPOINT/v1/instances/$INSTANCE_ID/dnszones/$DNSZONE_ID -H 'Content-Type: application/json' -H "Authorization: $TOKEN" -d '{
"description": "The DNS zone is used for VPCs in us-east region",
"label": "us-east"
}'





 Response to update a DNS zone 

{
"created_on": "2019-01-01T05:20:00.12345Z",
"description": "The DNS zone is used for VPCs in us-east region",
"id": "example.com:2d0f862b-67cc-41f3-b6a2-59860d0aa90e",
"instance_id": "1407a753-a93f-4bb0-9784-bcfc269ee1b3",
"label": "us-east",
"modified_on": "2019-01-01T05:20:00.12345Z",
"name": "example.com",
"state": "PENDING_NETWORK_ADD"
}







 Listing DNS zones 

List one or more zones in your domain by using the following curl command:



 Request 

curl -X GET $DNSSVCS_ENDPOINT/v1/instances/$INSTANCE_ID/dnszones -H "Authorization: $TOKEN"





 Response 

{
"success": true,
"result": [
{
"id": "example.com:ed10e4b2-8a64-4afa-a4e2-9e60a766d079",
"created_on": "2019-07-24 12:30:58.357201205 +0000 UTC",
At the required time, the domain controllers can be migrated to the vCenter Server instance with no change.

Depending on the complexity of the Active Directory Domain Services, when the layer 2 network extension is removed, more Active Directory Domain Services tasks might need to be completed if the complete forest domain is not moved to IBM Cloud. The use of AD sites can help with the control of replication traffic across the layer 3 network between on-premises and IBM Cloud. See to the extended domain with AD sites model described in the previous section. The following diagram shows the Active Directory Domain Services topology for this extended domain model.

Zoom

![Extended domain diagram](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/adds-extendeddomain.svg)

Figure 5. Extended domain diagram





 Restructuring AD domains 

However, it is possible to restructure AD domains the details are out of scope of this document. Review the following two types of restructure.



* Inter-forest restructure - When you migrate objects between forests, both the source domain and the target domain environments exist, and you can roll back to the source environment during the migration, if necessary.
* Intra-forest restructure - When you restructure domains within a forest, the migrated accounts no longer exist in the source domain.



For more information, see [ADMT guide - Migrating and restructuring Active Directory domains](https://www.microsoft.com/en-us/download/confirmation.aspx?id=19188) (Document download).





 Best practice guidance for AD in a vCenter Server instance 

Review the following guidance for AD in a vCenter Server instance.



* For more information about supported AD trusts, see [Microsoft Active Directory trusts supported by VMware vCenter Single Sign-on](https://kb.vmware.com/s/article/2064250).
* Enable vCenter with an identity source for authentication of all vCenter services and system administrators. This configuration is made by the VMware Solutions automation ready for the customer to add their system administrator users.
No, adding the same permitted network (for example, a VPC) to two DNS zones of the same name is not allowed.





 What are the authoritative servers for the DNS Services zones? Can I resolve the private DNS zones iteratively? 

Unlike public DNS zones, DNS Services does not expose authoritative servers for private DNS zones. Clients must send their recursive DNS queries to the DNS resolvers provided by the service. DNS Services does not allow iterative resolution of private DNS zones.





 Can I create a DNS zone with same name as a Public DNS zone? 

DNS Services allows creating a private DNS zone that can have the same name as the public DNS zone. See a [detailed explanation](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-about-dns-servicesresolving-dns-names-with-dns-services) of this scenario, referred to as Split Horizon.





 Are there any limits on global load balancer usage? 

See [Global load balancers limitations](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-global-load-balancersglb-ki) for more information on global load balancer usage.





 What types of health checks are supported? 

HTTP and HTTPS health checks are currently supported.





 What regions can I use for health check monitoring? 

Health checks are currently supported in the following regions:



* Dallas (us-south)
* Washington, D.C. (us-east)
* London (eu-gb)
* Frankfurt (eu-de)
* Osaka (jp-osa)
* Tokyo (jp-tok)
* Toronto (ca-tor)
* Sydney (au-syd)
* Sao Paulo (br-sao)







 How can I disable health check monitoring to the origins? 

You can disable health check monitoring by disabling the origin.





 How do I upgrade my plan from free to standard? 



1.
Reloading an OS by using an image template 

During the standard OS Reload process, you select configuration options for the device individually. When you reload from an image template, the configuration loads exactly as it appears in the image template.



 Differences between a standard OS reload and a reload from an image template 

In an image template reload, you can still add features before you reload the OS.

Use the following steps to reload an OS from an image template by using the Load from Image feature.

If you want to retain your data, back up all data before reloading the OS. An OS reload clears all data from the device, so, if you did not back up the data before the reload, it is permanently deleted and cannot be retrieved.





 Before you begin 



* Go to your console's device menu. For more information, see [Navigating to devices](https://cloud.ibm.com/docs/bare-metal?topic=virtual-servers-navigating-devices).
* Make sure that you have any necessary account permissions and device access. Only the account owner, or a user with the Manage Users classic infrastructure permission, can adjust the permissions.



For more information about permissions, see [Classic infrastructure permissions](https://cloud.ibm.com/docs/iam?topic=iam-infrapermissioninfrapermission) and [Managing device access](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-device-access).





 Reloading an OS 



1. From the Device list, click the server that needs an OS Reload to show the Device Details page.
2. From the Actions menu, select Load from image.
3. Select the image template checkbox to for the image template to load on to the device.

Before the reload completes, the image template is copied to the data center that contains the device, if it is not already located in the same data center. If the image template must be copied to the data center, a fee might be charged if the template is not deleted from the location after the OS Reload occurs.
4.
This command removes resource record with ID 12345678.





 ibmcloud sl dns zone-create 

Create a zone:

ibmcloud sl dns zone-create ZONE

Examples:

ibmcloud sl dns zone-create ibm.com

This command creates a zone that is named ibm.com.





 ibmcloud sl dns zone-delete 

Delete a zone:

ibmcloud sl dns zone-delete ZONE

Examples:

ibmcloud sl dns zone-delete ibm.com

This command deletes a zone that is named ibm.com.





 ibmcloud sl dns zone-list 

List all zones on your account:

ibmcloud sl dns zone-list

Examples:

ibmcloud sl dns zone-list

This command lists all zones under current account.





 ibmcloud sl dns zone-print 

Print zone and resource records in BIND format:

ibmcloud sl dns zone-print ZONE

Examples:

ibmcloud sl dns zone-print ibm.com

This command prints zone that is named ibm.com, and in BIND format.
* [Configure the Ingress for the DNS subdomain](https://cloud.ibm.com/docs/cis?topic=cis-multi-region-k8s-cismulti-region-k8s-cis-ingress)







 Step 3: Configure multi-location load-balancing 

Your application is now running in two clusters but it is missing one component for the users to access either clusters transparently from a single entry point.

In this section, you will configure IBM Cloud Internet Services (CIS) to distribute the load between the two clusters. CIS is a one stop-shop service providing Global Load Balancer (GLB), Caching, Web Application Firewall (WAF) and Page rule to secure your applications while ensuring the reliability and performance for your Cloud applications.

To configure a global load balancer, you will need:



* to point a custom domain to CIS name servers,
* to retrieve the Ingress Subdomain of the Kubernetes clusters,
* to configure health checks to validate the availability of your application,
* and to define origin pools pointing to the clusters.





 Register a custom domain with IBM Cloud Internet Services 

The first step is to create an instance of CIS and to point your custom domain to CIS name servers.



1. If you do not own a domain, you can buy one from a registrar.
2. Navigate to [IBM Cloud Internet Services](https://cloud.ibm.com/catalog/services/internet-services) in the IBM Cloud catalog.
3. Set the service name, and click Create to create an instance of the service.
4. When the service instance is provisioned, click on Add domain.
5. Enter your domain name and click Next.
6. Setup your DNS records is an optional step and can be skipped for this tutorial. click on Next
7. When the name servers are assigned, configure your registrar or domain name provider to use the name servers listed.
8. After you've configured your registrar or the DNS provider, it may require up to 24 hours for the changes to take effect.
CoreDNS configuration N/A N/A Changed the default CoreDNS configuration to minimize [cluster service DNS resolution failures when CoreDNS pods are restarted](https://cloud.ibm.com/docs/containers?topic=containers-coredns_lameduck). Existing CoreDNS configurations are unchanged. For more information about changing your CoreDNS configuration, see [Customizing the cluster DNS provider](https://cloud.ibm.com/docs/containers?topic=containers-cluster_dnsdns_customize). 
 etcd v3.3.15 v3.3.17 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.3.17). Update resolves [CVE-2019-1547](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1547), [CVE-2019-1549](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1549), and [CVE-2019-1563](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1563). 
 GPU device plug-in and installer de13f2a 9cd3df7 Updated image for [CVE-2019-5094](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5094). 
 IBM Cloud File Storage for Classic plug-in and monitor 349 350 Added the ability to [scale down the plug-in replicas to zero](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_scaledown_plugin), to conserve cluster resources if you don't need file storage.