vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For HTTP and SAN certificate-based HTTPS CDN, update your DNS record so that your website points to the CNAME associated with your new CDN mapping.

For wildcard, certificate-based HTTPS CDN, this DNS update is not needed because you access the website through https://<CNAME>. You can refresh your CDN status by clicking Get status from the menu of your CDN instance.

It can take up to 15 - 30 minutes for the update to take effect. Check with your DNS provider to obtain an accurate time estimate.
* How do I add a CNAME record for my CDN domain in DNS?

In your DNS configuration page for your CDN domain, you can create a CNAME record with the CDN domain name as the Host, and the IBM CNAME you used to configure the CDN as the CNAME. The IBM CNAME ends with cdn.appdomain.cloud..

A typical CNAME record looks similar to the following on the DNS configuration page:



CNAME record example

 Resource Type Host Points to (CNAME) TTL 

 CNAME www.example.com example.cdn.appdomain.cloud 15 minutes 



* When am I billed for my CDN?

IBM Cloud Content Delivery Network billing occurs according to the billing period established in your IBM Cloud account.
* If I select Delete from the Overflow menu, does that delete my account?

No, if you select 'Delete' from the Overflow ![Overflow menu](https://cloud.ibm.com/docs/images/overflow.png) menu, only that CDN is deleted. Your account still exists, and you can create additional CDNs.
* Does content caching use push or pull?

Content caching is done using an origin pull model. Origin Pull is a method by which data is "pulled" by the Edge server from the origin server, as opposed to manually uploading the content onto the Edge server.
* Is there a recommended browser to use for CDN service configuration?

Yes, Firefox and Chrome are the recommended browsers. It is recommended that you use the latest versions with your IBM Cloud Content Delivery Network.
"provider_name" : "SAPHanaCostOptSR", provider name = class name
"provider_description" : "Handle reconfiguration event for cost-optimized system replication",
"provider_version" : "1.0"}

def postTakeover(self, rc, kwargs):
"""Post takeover hook."""

 prepared SQL statements to remove memory allocation limit and pre-load of column tables
stmnt1 = "ALTER SYSTEM ALTER CONFIGURATION ('global.ini','SYSTEM') UNSET ('memorymanager','global_allocation_limit') WITH RECONFIGURE"
stmnt2 = "ALTER SYSTEM ALTER CONFIGURATION ('global.ini','SYSTEM') UNSET ('system_replication','preload_column_tables') WITH RECONFIGURE"

myPort = int('3' + os.environ.get('DIR_INSTANCE')[-2:] + '15')
myKey = self.config.get("userkey") if self.config.hasKey("userkey") else "HA_HOOK_KEY"

self.tracer.info("%s.postTakeover method called with rc=%s" % (self.__class__.__name__, rc))
self.tracer.info("%s.postTakeover method: userkey: %s, port: %s" % (self.__class__.__name__, myKey, myPort))

if rc in (0, 1):
 rc == 0: normal takeover succeeded
 rc == 1: waiting for force takeover
conn = dbapi.connect(userkey=myKey, address='localhost', port=myPort)
self.tracer.info("%s: Connect using userkey %s - %s" % (self.__class__.__name__, myKey, conn.isconnected()))
cursor = conn.cursor()
3. Click Create.
4. Configure the VPC, type, subnet, listeners, and pools as needed.
5. Under the DNS type section, choose Private.
6. Click Bind+ to enter DNS instance, and DNS zone information.
7. Click Create to provision the load balancer.







 Binding a DNS zone to an existing load balancer in the UI 

To bind a DNS zone to an existing load balancer, follow these steps:



1. From your browser, open the [IBM Cloud console](https://cloud.ibm.com/login) and log in to your account.
2. Select the Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) from the upper left, then click VPC Infrastructure > Load balancers in the Network section.
3. From the list of load balancers, select the load balancer to view its details page.
4. Click Bind private DNS in the Private DNS section.
5. Enter the DNS instance, and DNS zone information.
6. Click Bind private DNS to bind the DNS zone to your load balancer.



When migrating to a private DNS zone for an existing load balancer, the default A records in lb.appdomain.cloud are removed. To prepare your client devices, create a CNAME record with the default hostname under the wanted private DNS zone before the migration. After configuring all client devices to use the new private DNS zone, you can then delete the CNAME record and begin the migration. This allows the client devices to cache the private DNS hostname until the A records are created.





 Unbinding a DNS zone to an existing load balancer in the UI 

To unbind a DNS zone from a load balancer, follow these steps:



1. From your browser, open the [IBM Cloud console](https://cloud.ibm.com/login) and log in to your account.
2.
! ! ! ! ! ! !
<-- <section "id="section-command-options-log-retention-update" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.--flag value: Whether to turn log retention on or off. Required.-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-log-retention-update" "> --><-- <section "id="section-examples-logpull-update" "> --> Examples Enable log retention for domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis log-retention-update 31984fea73a15b45779fa0df4ef62f9b --flag on -i cis-demo --output JSON
<-- </section "id="section-examples-logpull-update" "> --><-- </section "id="section-log-retention-update" "> --><-- </section "id="section-log-retention-cli-ref" "> --><-- <section "id="section-metrics" "> --> Metrics Manipulate metrics by using the following metrics commands.<-- <section "id="section-firewall-event-analytics" "> --> ibmcloud cis firewall-event-analytics Retrieve a full log of firewall events. ibmcloud cis firewall-event-analytics DNS_DOMAIN_ID --dataset DATA_SET] --filter FILTER] --order FILTER_ORDER] --limit LIMIT_NUMBER] -i, --instance INSTANCE] --output FORMAT] ! !! ! ! ! ! ! ! !
Update a feature for the domain.

ibmcloud cis domain-settings-update DNS_DOMAIN_ID (-f, --feature FEATURE) (-v, --value VALUE) [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required. -f, --feature value
: Feature of domain settings to update. Required. Valid values:



* always_use_https: Redirect all requests with scheme http to https. This applies to all http requests to the domain.
* automatic_https_rewrites: Help fix mixed content by changing http to https for all resources or links on your web site that can be served with HTTPS.
* brotli: When the client requesting an asset supports the brotli compression algorithm, CIS will serve a brotli compressed version of the asset.
* browser_check: Evaluate HTTP headers from your visitors browser for threats. If a threat is found a block page will be delivered.
* challenge_ttl: Specify how long a visitor with a bad IP reputation is allowed access to your website after completing a challenge.
* ciphers: A whitelist of ciphers for TLS termination. These ciphers must be in the BoringSSL format.
* cname_flattening: Follow a CNAME to where it points and return that IP address instead of the CNAME record. By default, only flatten the CNAME at the root of your domain.
* email_obfuscation: Encrypt email addresses on your web page from bots while keeping them visible to humans.
* opportunistic_onion: Allow legitimate users of Tor Browser to access your websites.
* hotlink_protection: Protect your images from off-site linking.
* http2: Accelerate your website with HTTP/2.
* http3: Accelerate your website with HTTP/3.
* image_load_optimization: Improve load time for pages that include images on mobile devices with slow network connections.
* image_size_optimization: Improve image load time by optimizing images hosted on your domain.
It is not currently possible to order a certificate directly for a CIS global load balancer, but it is possible to order one for a CNAME record. So we will create a CNAME to order the certificate.



1. Open the CIS service you created by earlier, you can find it in the [Resource list](https://cloud.ibm.com/resources)
2. Navigate to Global Load Balancers under Reliability and click DNS.
3. Scroll down to DNS Records section and create a new record:



* Type: CNAME
* Name: lb
* TTL: default (Automatic)
* Alias Domain Name: zzz.example.com
* Click Add Record



4. Order a certificate in Secrets Manager



* Open the Secrets Manager service and select Secrets on the left.
* Click Add and then TLS certificates.
* Click on the Order a public certificate tile.
* Complete the form:



* Name - zzz alias.
* Under Certificate authority select your configured Let's Encrypt certificate authority engine.
* Under Key algorithm select RSA4096
* Bundle certificates - leave off
* Automatic certificate rotation - leave off
* Under DNS provider select your configured DNS provider instance
* Click on Select domains
* Expand the domain listed to view the list of subdomains and select the check box next to the lb.example.com and click on Done.



* Click Order.





Create a HTTPS listener:



1. Navigate to the VPC Load balancers page.
2. Select vpc-lb-region1
3. Under Front-end listeners, Click Create



* Protocol: HTTPS
* Port: 443
* Back-end pool: POOL in the same region
* Choose the current region as your SSL region
* Choose the SSL certificate order name you just created for lb.example.com



4. Click Save to configure an HTTPS listener



Repeat the above steps in the load balancer of region 2.

In a browser open https://lb.example.com to verify success





 Failover test
Refer to this [link](https://docs.openshift.com/container-platform/4.12/registry/registry-third-party-registries_registry-overview) for more info.









 Step 7: (Optional) Use your own custom domain 

This section requires you to own a custom domain and to be able to modify the DNS records of the domain. You will need to create a CNAME record pointing to the IBM-provided domain.

Steps for setting up the CNAME record vary depending on your DNS provider. Under DNS Management/Zone of your domain, add a new CNAME record, set Host(name) to openshiftapp or any subdomain you like and set Points to to IBM-provided domain without HTTP or HTTPS



 With HTTP 



1. Create a route exposing the service at a hostname by replacing <HOSTNAME> with your hostname(e.g.,www.example.com or openshiftapp.example.com), so that external clients can reach it by name.

oc expose svc/$MYPROJECT --hostname=<HOSTNAME> --name=$MYPROJECT-domain --port=3000
2. Access your application at http://<HOSTNAME>/







 With HTTPS 



1. To create a secured HTTPS route, you can use your own certificate and key files from a CA like [Let's Encrypt](https://letsencrypt.org/) or order through [Secrets Manager](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-certificates&interface=ui). Pass them with the create route command

oc create route edge $MYPROJECT-httpsca --service=$MYPROJECT --cert=example.pem --key=example.key --hostname=<www.HOSTNAME> --port=3000

Here, you have used Edge termination. To learn about other secured routes and termination types like passthrough and re-encryption, run oc create route --help command)









 Step 8: Remove resources 



* Delete all resource objects specific to an application:
curl -X POST $DNSSVCS_ENDPOINT/v1/instances/$INSTANCE_ID/dnszones/$DNSZONE_ID/resource_records -H "Authorization: $TOKEN" -d '{
"name":"www.example.com",
"type":"A",
"rdata": {
"ip":"1.2.6.7"
},
"ttl":300
}'





 Response 

{
"created_on":"2019-09-13 19:56:42.484382585 +0000 UTC",
"modified_on":"2019-09-13 19:56:42.484382585 +0000 UTC",
"rtype":"A",
"ttl":300,
"name":"www.example.com.testZone.com",
"id":"A:786c07c7-173e-473b-aa09-c186601a5709",
"rdata":{
"ip":"1.2.6.7"
}
}







 Verifying the setup 

To verify that your instance, zone, and record are performing correctly, run the following dig command:

dig @161.26.0.7 <Record type> <record name>

Example:

dig @161.26.0.7 A xyz.example.com
However, if you have overlapping IP addressing challenges, the note the following guidance:



* You can still continue to use your existing instance management subnet, if it has IP addresses available and you don't use any IP addresses for your own use. The new instance uses new IP addresses for the vCenter server, NSX-T managers, and Active Directory servers (if AD servers are running on the VMware VMs) from the new instance management subnet. Reusing existing management subnet is not possible for these components until you delete the existing VCS.
* In addition, the NSX-T T0 gateways are provisioned with new IP addresses from the portable private and portable public subnets for customer workload edge. NSX-T T0 gateways do not support secondary IP addresses on their uplinks.
* You can manually configure an existing subnet for the NSX-T T0 gateway uplinks, but only one subnet can be configured in T0.
* If you are using secondary IP subnets on the uplinks, you need to redesign the topology. For example, you can order [new static subnets](https://cloud.ibm.com/docs/subnets?topic=subnets-about-subnets-and-ipsstatic-subnets) and route these subnets to NSX-T T0 HA VIP. These IP subnets and addresses can be used with NSX-T NAT rules, load balancing or on overlay attached VMs.







 Can I reuse existing portable subnets that are ordered outside the VMware Solutions console? 

If you ordered private or public portable subnets outside the VMware Solutions console, and you use these subnets with your workloads by running on VMware clusters, you can still continue to use these IP addresses if your new instance was deployed on the same VLANs as the existing NSX-V based solution was.

If you are using these IP addresses on ESGs for NAT rules or other services, be aware that the NSX-T T0 gateways do not support secondary IP addresses on their uplinks. The NSX-T T0 gateway in the new instance is provisioned with new IP addresses from the portable private and portable public subnets for customer workload edge.
For more information about the required and optional request parameters, see [Add a configuration](https://cloud.ibm.com/apidocs/secrets-manager/secrets-manager-v2create-config-element).







 Adding a DNS provider configuration with Terraform 

You can add DNS provider configurations to your service instance by using Terraform for Secrets Manager.



 Configuring Cloud Internet Services (CIS) with Terraform 

The following example shows a confihuration that you can use to add a a Cloud Internet Services (CIS) DNS configuration to your Secrets Manager instance.

resource "ibm_sm_public_certificate_configuration_dns_cis" "my_dns_cis_config" {
instance_id = local.instance_id
region = local.region
name = "my_DNS_CIS_config"
cloud_internet_services_apikey = var.my_cis_apikey
cloud_internet_services_crn = var.my_cis_crn
}





 Configuring classic infrastructure with Terraform 

The following example shows a confihuration that you can use to add a classic infrastructure DNS configuration to your Secrets Manager instance.

resource "ibm_sm_public_certificate_configuration_dns_classic_infrastructure" "my_dns_classic_config" {
instance_id = local.instance_id
region = local.region
name = "my_DNS_config"
classic_infrastructure_password = "username"
classic_infrastructure_username = "password"
}







 Deleting a DNS provider configuration in the UI 

If you no longer need a configuration, you can delete it by using the Secrets Manager UI.

After you delete a configuration, the certificates that are associated with the DNS provider can no longer be rotated automatically. Do not delete configurations that are associated with certificates in your production apps or services.



1. In the console, click the Menu icon !
Using the DNS interface 

In the DNS interface, you have the ability to manage Forward Zones, Secondary Zones, and Reverse Records.



 Forward zones 

To manage forward zones:



1. From your browser, open the [IBM Cloud® console](https://cloud.ibm.com/) and log in to your account.
2. From the dashboard, click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/86dadb3996e7fa2b119c2c09bda56dbc01297416/icons/icon_hamburger.svg) and select Classic Infrastructure to get to the Classic Infrastructure landing page.
3. In the Classic Infrastructure navigation, select Network > DNS > Forward Zones
4. Select the domain you want to manage, or select the Add DNS zone button on the right side of the page.







 Secondary zones 

To manage secondary zones:



1. From your browser, open the [IBM Cloud® console](https://cloud.ibm.com/) and log in to your account.
2. From the dashboard, click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/86dadb3996e7fa2b119c2c09bda56dbc01297416/icons/icon_hamburger.svg) and select Classic Infrastructure to get to the Classic Infrastructure landing page.
3. In the Classic Infrastructure navigation, select Network > DNS > Secondary Zones. From this page you can add or modify secondary DNS settings.
4. To add a new record, select Add Zone, complete the fields and select Add.
5. To remove a Secondary DNS record, or convert it to a primary record, use the Actions list menu on the right of the page and choose the appropriate option.







 Reverse records 

To manage reverse records:



1. From your browser, open the [IBM Cloud® console](https://cloud.ibm.com/) and log in to your account.
Name _sip._tcp.video.example.com
Type SRV
Created On 2020-04-10 09:15:56.940189115 +0000 UTC
Modified On 2020-04-10 09:15:56.940189115 +0000 UTC
TTL 900
Data
port 953
priority 10
target media.example.com
weight 10





 Creating type 'TXT' resource record 

Use the ibmcloud dns resource-record-create command with --type TXT option to create a type TXT resource record. --name and --text are mandatory options.

$ ibmcloud dns resource-record-create $DNS_ZONE_ID --type TXT --name text --text "This is a text record."
Creating resource record in zone 'example.com:f7f40364-a5e6-48f7-9fc9-387434c579ae' for service instance 'DNS Services-km' ...
OK

ID TXT:92648285-c7e5-49ef-bf8b-a5be91d5c5d3
Name text.example.com
Type TXT
Created On 2020-04-10 09:16:50.169135062 +0000 UTC
Modified On 2020-04-10 09:16:50.169135062 +0000 UTC
TTL 900
Data
text This is a text record.





 Creating type 'MX' resource record 

Use ibmcloud dns resource-record-create command with --type MX option to create a type MX resource record. --name and --exchange are the mandatory options.

$ ibmcloud dns resource-record-create $DNS_ZONE_ID --type MX --name mail --preference 10 --exchange exchange.example.com
Creating resource record in zone 'example.com:f7f40364-a5e6-48f7-9fc9-387434c579ae' for service instance 'DNS Services-km' ...
OK
--ipv4
: IPv4 address.

--ipv6
: IPv6 address.

--cname
: Canonical name.

--ptrdname
: Hostname of the relevant A or AAAA record.

--text
: Human readable text.

--exchange
: Hostname of Exchange server.

--preference
: Preference of the MX record

--service
: The symbolic name of the desired service, beginning with an underscore _.

--protocol
: The symbolic name of the desired protocol.

--port
: Port number of the target server.

--weight
: Weight of distributing queries among multiple target servers.

--priority
: Priority of the SRV record.

--target
: Hostname of the target server.

--ttl
: Time to live, in seconds. Default value is 900. Valid values: 60, 120, 300, 600, 900, 1800, 3600, 7200, 18000, 43200.

-r, --record-content
: The JSON file or JSON string used to describe a DNS Resource Record. See [Required fields for -r --record-content](https://cloud.ibm.com/docs/cli?topic=cli-dns-services-cli-commandsrequired-fields-r-record-content) for more detail.

-i, --instance value
: > Instance name or ID. If not set, the context instance specified by dns instance-target INSTANCE is used.

--output value
: Specify output format. Currently, json is the only supported format.





 Required fields for -r --record-content 

The required field in JSON data is type.

Resource record type. Valid values: A, AAAA, CNAME, PTR, TXT, MX, SRV.



* For type A, AAAA: Extra required fields are name, rdata.



* name: Resource record name.
* rdata: Content of the resource record.
Create a DNS entry in the CIS instance using YOUR-CLUSTER Ingress subdomain as the alias.



1. Open the CIS service instance, you can find it in the [Resource List](https://cloud.ibm.com/resources).
2. Click the Reliability tab on the left.
3. Click the DNS tab on the top.
4. Scroll down to the DNS Records section and click Add to create a new record:



1. Type: CNAME
2. Name: secure-file-storage
3. Alias: The Ingress subdomain of YOUR-CLUSTER. Something like YOUR-CLUSTER-NAME-e012345678901234f61a87aaaaaaaa3a-0000.us-south.containers.appdomain.cloud. In the shell:

echo $INGRESS_SUBDOMAIN
4. Click Add Record





Connect Secrets Manager instance to Let's Encrypt.



1. A Let's Encrypt ACME account and associated .pem file is required. Use an existing one or [create one](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-prepare-order-certificates&interface=uicreate-acme-account):



1. Install the acme-account-creation-tool. [Creating a Let's Encrypt ACME account](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-prepare-order-certificates&interface=uicreate-acme-account) contains instructions and a link to the creation tool.
2. Run acme-account-creation-tool to create an accout specifically for this secure-file-storage example. Below is an example session for a Mac.:

$ ./acme-account-creation-tool-darwin-amd64 -e YOUREMAIL -o secure-file-storage.example.com -d letsencrypt-prod
ibmcloud cis log-retention DNS_DOMAIN_ID -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-command-options-log-retention" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.-i, --instance: 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-log-retention" "> --><-- <section "id="section-examples-log-retention" "> --> Examples Get log retention setting for domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis log-retention 31984fea73a15b45779fa0df4ef62f9b -i cis-demo --output JSON
<-- </section "id="section-examples-log-retention" "> --><-- </section "id="section-log-retention" "> --><-- <section "id="section-log-retention-update" "> --> ibmcloud cis log-retention-update Update log retention setting for the domain. ibmcloud cis log-retention-update DNS_DOMAIN_ID (--flag on|off) -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! ! ! !
<-- <section "id="section-command-options-log-retention-update" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.--flag value: Whether to turn log retention on or off. Required.-i , --instance value: Instance name or ID.