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

This recommendation uses the following key principles to obtain scale while optimizing for compliance, cost, and operational efficiencies.



* Manage cloud as code (compliance and ops optimization)
* Separate development and production environments (general compliance)
* Hub and spoke (networking optimization)
* Avoid duplication of shared tools (cost and ops optimization)
* Use shared infrastructure for application workloads (cost and ops optimization)
* Separate workload and management (compliance)
* Work within IBM Cloud operating limits and constraints





 Cloud as code 

A key part of this recommendation is to do all cloud setup and configuration as code - that is, automate everything from application infrastructure to account creation, to compliance monitoring. Automating everything allows the enterprise to ensure scale, compliance, security, and so on, in a repeatable and easily evolvable fashion. IBM Cloud provides a number of deployable architectures in the IBM Cloud catalog that can be used to automate these recommendations with minimal effort. These pre-made solutions can also be customized or extended to match the needs of the enterprise.

Managing infrastructure as code at scale requires more than just Terraform in a Git repo. Infrastructure as code is the DNA of an enterprise-wide cloud solution because it must be subject to both governance and management. Infrastructure as code ensures that only validated, compliant, and approved code is deployed. You can also track how deployments correspond to internal projects, teams, cost centers, and more.

IBM Cloud provides a number of tools to assist with this process. The IBM Cloud catalog allows an enterprise to advertise approved IaC solutions to users across the cloud. [IBM Cloud projects](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-understanding-projects) allow an enterprise to ensure that only approved IaC is deployed and to track how the resulting resources correspond to projects, teams, and cost centers.



 Related controls in IBM Cloud Framework for Financial Services 

The following [IBM Cloud Framework for Financial Services controls](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-aboutframework-control-requirements) are most related to this guidance.
On the variable page, click Enable continuous delivery link option to view Schematics Infrastructure as Code Tekton Toolchain page.
2. Click Delivery Pipeline Required tab.
3. Enter your IBM Cloud API key.
4. Click Authorize > Authorize IBM-Cloud and enter your GitHub password to get authorized.
5. Click Create to view Toolchains page.
6. Click Deliver Pipeline pane to view Schematics-deploy Dashboard page.
7. Click Run Pipeline

Observe the UPDATE is in STAGE RUNNING state, without the click.







 Step 5: Analyzing the pipeline execution process 

Observe the pipeline dashboard and view the status of your workspace execution.



1. During the update stage process, from the example of ibm-cos-bucket repository observe the main.tf file configuration with the cos_instance name and bucket_name. These details are updated in the Schematics Workspaces after the APPLY stage is passed.
2. The UPDATE stage completes, PLAN stage is in running state.
3. Click Jobs and history to view the status of the job from the PLAN pane.
4. Observe that the PLAN stage is passed, and APPLY stage is in running state.
5. From the Schematics Workspaces, check that the resource name and bucket name are created successfully.
6. Observe that the APPLY stage is passed and TEST stage is in Running state.
7. Observe that the TEST stage is passed successfully.
8. Now, you can edit your template in the configured repository and observe an automatic pull of your workspace by the continuous delivery toolchain.







 Step 6: Analyzing the Schematics Workspace 

Alternatively, through the IBM Cloud dashboard, you can view the status of the workspace.



1. From the [Schematics Workspaces dashboard](https://cloud.ibm.com/schematics/workspaces).
2. Select Navigation Menu > Schematics > Workspaces > Resources to observe the apply state of the resources in your workspace.
3.
In addition to conducting continuous compliance scans, projects notify you of architecture version updates, validation failures, and required cluster updates. Because projects are integrated with IBM Cloud’s Event Notifications service, you can route project notifications to Slack, PagerDuty, and other third-party tools.

Building and sharing custom architectures by using private catalogs
: Deployable architectures are built to be modular and flexible. You can create custom deployable architectures and share them with your team by using private catalogs by adding the IaC to a new project. The IaC prompts you to select your code (you can download a code bundle from the deployable architecture’s catalog page) and uploads it to any repo you specify. After it's deployed, the IaC creates CI and CD pipelines that check changes for compliance and allow you to publish directly into a private catalog. Private catalogs make it easy to consume and push version updates to your team.

Managing the lifecycle of your infrastructure
: Projects help you manage, track, and maintain your infastructure from start to finish. As the lifecycle of your infrastructure changes, you can use projects to easily clean up the project resources that are no longer needed. If a project is complete and is no longer needed, the whole project and all associated resources in all envionments can be deleted. In addition, a project can be paused by deleting the associated resources while retaining the project and its configurations. This makes it easy to resume the project later.

Reporting and cost management
: Projects assist with cost management and other types of reporting by automatically tagging all created resources and by providing a resource inventory within the project. For example, when a usage report is generated the project tags will be included, allowing the accounting team to allocate costs to projects without any additional effort. Other types of configuration management tasks such as determining an inventory of particular types of applications or resources can also be accomplished by project tagging and resource views.





 Essential concepts 

Review the following concepts and processes to help you learn about working with projects in your account.



 Configurations 

A single project typically manages configurations for one or more IaC templates called deployable architectures in IBM Cloud.
From the [Satellite console](https://cloud.ibm.com/satellite/locations), click Create location.
3. In the Setup section, click Azure.
4. In the Azure credentials section, enter the Azure client ID (app ID), Azure tenant ID, and Azure secret key (password) values that you previously created for the service principal.
5. Click Fetch options from Azure.
6. Review the Azure environment details that are automatically populated. By default, enough VMs are created to provide hosts for 1 small location that can run about 2 demo clusters. To change the subscription, region, instance type, or number of VMs for the hosts, click the Edit pencil icon.
7. Review the Satellite location details. If you edited the Azure environment details, you might want to click the Edit pencil icon to change details such as the description, API key, or IBM Cloud multizone region that the location is managed from.
8. In the Summary pane, review the cost estimate.
9. Click Create location. Your location might take about 30 minutes to finish provisioning.
10. Optional: To review the provisioning progress, review the logs in the Schematics workspace that is automatically created for you.



1. Click Manage in Schematics. If you see an error, navigate to the [Schematics workspaces console](https://cloud.ibm.com/schematics/workspaces) and click the name of your workspace, such as us.east.cartOrder....
2. From the Activity tab, find the current activity row and click View log to review the log details.
3. Wait for the Schematics action to finish and the workspace to enter an Active state.





Well done, your Satellite location is creating! You can review the [Satellite console](https://cloud.ibm.com/satellite/locations) to see when your location is in a Normal state and ready to use.

If you are using this template for demonstration purposes, do not assign all your hosts to your control plane.
If in addition ibm.io/auto-delete-bucket is set to true, you must leave this field blank to automatically assign your bucket a name with the format tmp-s3fs-xxxx. The name must be unique in IBM Cloud Object Storage.
* If ibm.io/auto-create-bucket is set to false: Enter the name of the existing bucket that you want to access in the cluster.



ibm.io/secret-name
: In the spec volume claim templates metadata annotations section, enter the name of the secret that holds the IBM Cloud Object Storage credentials that you created earlier. If you add your [IBM Cloud Object Storage credentials](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_install) to the default storage classes, you must not list the secret in the PVC.

kubernetes.io/storage-class
: In the spec volume claim templates metadata annotations section, enter the storage class that you want to use. Choose between the following options:



* If ibm.io/auto-create-bucket: "true": Enter the storage class that you want to use for your new bucket.
* If ibm.io/auto-create-bucket: "false": Enter the storage class that you used to create your existing bucket.



: To list existing storage classes, runkubectl get storageclasses | grep s3. If you don't specify a storage class, the PVC is created with the default storage class that is set in your cluster. Make sure that the default storage class uses the ibm.io/ibmc-s3fs provisioner so that your stateful set is provisioned with object storage.

storageClassName
: In the spec volume claim templates spec section, enter the same storage class that you entered in the spec.volumeClaimTemplates.metadata.annotations.volume.beta.kubernetes.io/storage-class section of your stateful set YAML.

storage
: In the spec volume claim templates spec resource requests section, enter a fictitious size for your IBM Cloud Object Storage bucket in gigabytes. The size is required by Kubernetes, but not respected in IBM Cloud Object Storage.
Licenses 

The license terms for WAS.Base are defined by the WebSphere Application Server license. The WAS.Cell license terms are covered by the WebSphere Application Server Network Deployment license.

Select the applicable link in the following table to view the license terms for the software product you are about to install.



Table 1. WebSphere licenses

 Topology   License                                             

 WAS.Base   [WebSphere Application Server](https://ibm.biz/tWASBaseLicenseIBMCloudVSIs)                    
 WAS.Cell   [WebSphere Application Server Network Deployment](https://ibm.biz/tWASNDLicenseIBMCloudVSIs) 



A WebSphere Application Server deployment sets up virtual private cloud (VPC), virtual server instance (VSI), and networking artifacts. Refer to IBM Cloud Billing ([https://cloud.ibm.com/billing](https://cloud.ibm.com/billing)) for the charges incurred for these artifacts.
* Memory optimized family profiles - provide advantages for memory intensive workloads, such as intensive database applications and in-memory analytics, and are especially designed for SAP HANA workloads.



For more information, see [Bare metal server profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-bare-metal-servers-profile).

The first letter of the profile name indicates the profile family:



Table 2. IBM Cloud Bare Metal Servers for VPC Profile Families

 First letter Characteristics of the related profile family 

 b Balanced family, CPU to Memory 1:4 
 m Memory optimized family, higher CPU to Memory ratio 1:8 



The bare metal server profile names are contextual and sequential. See the following example:



 Profile name Naming convention component What it means 

 mx2d-metal-96x768 m Memory Optimized family 
 x Intel x86_64 CPU Architecture 
 2 The generation for the underlying hardware 
 d the optional 'd' in the name indicates that the server is equipped with one or more SSD storage devices 
 — spacer 
 96 96 vCPU 
 x spacer 
 768 768 GiB RAM 
 '-metal-' in the name indicates that this is a Bare Metal Server. 







 Profiles available on Hourly Consumption Billing 

All IBM Cloud Bare Metal Servers for VPC are available with Hourly Consumption Billing, which includes Suspend Discounts and Sustained Usage Discounts. With Suspend Discounts, storage charges occur only if the server is in shutdown state. With Sustained Usage Discount, the more a server is used, the less the cost per hour.





 Storage specifications 

When the bare metal server profiles for SAP HANA are initially provisioned, the servers all have one pre-configured disk (sda) attached with the following basic layout:



Table 4. Storage configuration of the default bare metal server deployment (boot volume)

 File system Partition Storage type Size 

 sda1 Pre-configured BIOS volume 1 MB 
 /boot/efi sda2 Pre-configured boot volume 100 MB 
 / sda3 Pre-configured root volume 9.9 GB
* Balanced family profiles, provide a good mix of performance and scalability for more common workloads.
* All the Memory family profiles provide for memory intensive workloads, such as intensive database applications and in-memory analytics workloads, and are especially designed for SAP HANA workloads.



For more information, see [Intel Virtual Server for VPC Infrastructure documentation](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles).

The first letter of the profile name indicates the profile family that is mentioned the profile list:



Table 2. IBM Cloud® Virtual Servers for Virtual Private Cloud Profile Families

 First letter Characteristics of the related profile family 

 b Balanced family, CPU to Memory ratio 1:4 
 m Memory Optimized family, higher CPU to Memory ratio 1:8 
 v *Very High Memory Optimized family, very high CPU to Memory ratio 1:14 
 u Ultra High Memory Optimized family, ultra high CPU to Memory ratio 1:28 



The Virtual Server profile names are contextual and sequential. See the following example:



Table 3. Profile naming for SAP HANA

 Profile name Naming convention component What it means 

 mx2-16x128 m Memory Optimized family 
 x Intel x86_64 CPU Architecture 
 2 The generation for the underlying hardware 
 — spacer 
 16 16 vCPU 
 x spacer 
 128 128 GiB RAM 







 Profiles available on Hourly Consumption Billing 

All IBM Cloud Virtual Servers for VPC are available with Hourly Consumption Billing, which includes Suspend Discounts and Sustained Usage Discounts. With Suspend Discounts, storage charges occur only if the server is in Shutdown state. With Sustained Usage Discount, the more a server is used, the less the cost per hour.





 Storage specifications 

When the virtual server profiles for SAP HANA are initially provisioned, the servers all have one pre-configured volume (vda) attached with the following basic layout:



Table 4. Storage configuration of the default virtual server deployment (boot volume)

 File system Partition Storage type Size (GB) Nr. of <br>IOPS 

 / vda1 Pre-configured boot volume 100 3,000
Restricting network access 

By default, Event Streams instances are configured to use the IBM Cloud® public network, so they are accessible over the public internet.

The following features are available in the Enterprise plan only.

If required, you can use network type or context-based restrictions to restrict the network connectivity as follows:

Network type
: IBM Cloud offers both private and public networking. If your workload is running entirely within the IBM Cloud, and public access to the service is not required, Event Streams instances can instead be configured to be accessible only over the IBM Cloud private network. This offers increased isolation and does not incur the egress bandwidth charges associated with public traffic. Instances can also be configured to be accessible over both the IBM Cloud public and private networks, where your workload can use the most appropriate interface for its location. You can find further information about private networking at [Virtual routing and forwarding on IBM Cloud](https://cloud.ibm.com/docs/direct-link?topic=direct-link-overview-of-virtual-routing-and-forwarding-vrf-on-ibm-cloud).

Context-based restrictions (CBR)
: You can define access rules that limit the network locations that connections are accepted from. For example, network type, IP ranges, VPC, or other services. For more information, see [What are context-based restrictions](https://cloud.ibm.com/docs/account?topic=account-context-restrictions-whatis).
: Auditing events for context-based restrictions are published under context-based restrictions IBM Cloud Activity Tracker events [Context-based restrictions rules events](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-events_context_basedrestriction_rules_events). Activity Tracker events related to CBR enforcement are unavailable on private endpoints.



 Configuring the network type 

You can configure Enterprise service instances to be available on the IBM Cloud private, public, or private and public networks. The following information describes how to select and update the required networking type. Public networking is selected by default.



 Prerequisites 

Ensure that you complete the following tasks:
Upgrading licenses for vCenter Server with NSX-V instances 

You can upgrade your VMware NSX® license for V2.1 or later instances.



  Procedure to upgrade your NSX license 

This procedure applies to instances that are deployed in V2.1 or later. For instances that are deployed in V2.0 and earlier, you must upgrade the VMware NSX license manually.

You can upgrade the NSX license for your instance to a later edition. Reverting the license to an earlier edition is not supported.



1.  From the IBM Cloud® for VMware Solutions console, click Resources > vCenter Server from the left navigation pane.
2.  In the vCenter Server table, click the instance to upgrade the NSX license for.
3.  On the Summary page, verify that all instance details are displayed correctly. Then, click the Infrastructure tab to verify the details on the Infrastructure page.

If the details are not displayed, a connectivity problem might occur with the IBM CloudDriver Virtual Server Instance (VSI), as a result of a firewall rule or a networking issue. Resolve the problem before you continue with the next step, otherwise the upgrade might fail.
4.  Click the Licensing tab and click Upgrade in the License upgrades table. In the Upgrade NSX license edition window, select the edition that you want to upgrade to and click Upgrade.

The license upgrade replaces all existing NSX licenses on the instance. Additional charges can be incurred from an overlap of old and new licenses if you upgrade in the middle of a billing cycle. To avoid additional charges, it is recommended to upgrade the license at the end of the billing cycle.







  Related links 



*  [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support)
*  [FAQs](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-vmwaresolutions)
(https://cloud.ibm.com/docs/direct-link?topic=direct-link-get-started-with-ibm-cloud-direct-linkget-started-solution-to-order).





 01 March 2019 

Expanded local markets
: We expanded the Direct Link local markets to provide more local routing options to customers globally.
: New local market assignments:



* The Dallas local market includes Denver, Houston, and Chicago PoPs.
* The Washington DC local market includes New York, Atlanta, and Miami PoPs.
* The San Jose local market includes the Los Angeles PoP.
* The Oslo local market includes the Stockholm PoP.
* The Sydney local market includes the Perth PoP.
* The Hong Kong local market includes the Taipei PoP.
* The Tokyo local market includes the Osaka PoP.
* The Chennai local market includes the Mumbai PoP.



Withdrawing of global routing network transit overage charges
: Network transit limits and overage charges for customers with the Global routing option are withdrawn. Previous pricing included network transit allowances and overage charges for egress traffic outside of the customer’s local market. New pricing eliminates these network traffic charges. Henceforth, ingress and egress traffic across Direct Link connections do not incur overages.
: 6 March: Megaport is available in Chicago for Connect
: 13 March: Tokai is available in Tokyo 3 for Connect
: 8 March: TATA is available in Hong Kong 1 for Connect
: 1 March: EU Networks is available in Frankfurt 1 for Connect
: 1 March: NTT is available in Tokyo 5 for Connect





 28 February 2019 

February highlights
: 28 February: Zayo is now available in Washington DC 2 for Connect
: 27 February: MWS GNPP is now available in both Dallas 03 and Washington DC 2 for Connect
: 21 February: Cyrus One is now available in Dallas 13 for Exchange
: 21 February: DE-Cix One is now available in Frankfurt 3 for Exchange
: 19 February: Neutrona is now available in Washington DC 2 for Connect





 17 January 2019 

January highlights
: 17 January: Intercloud is now available in both Frankfurt PoPs (FRA01 & FRA03) for Connect.





 21 December 2018 

December highlights
* [REST Producer API](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-rest_producer_using)
* [Schema Registry API](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-ES_schema_registryschema_registry_rest_endpoints)









 Network connectivity 

For the Satellite plan, the network connectivity depends on the infrastructure that is used and is therefore the responsibility of the user.

By default, Lite, Standard, and Enterprise instances are configured to be accessible over the public internet. If you're using the Enterprise plan, you can restrict connectivity as follows:

Private networking
: If your workload is running entirely within the IBM Cloud, and public access to the service is not required, Event Streams instances can instead be configured to be accessible only over the IBM Cloud Private network. This configuration offers increased isolation and does not incur the egress bandwidth charges associated with public traffic. Instances can also be configured to be accessible over both the IBM Cloud Public and Private networks.

Context-based restrictions
: You can define access rules that limit the network locations that connections are accepted from according to certain characteristics. For example, network type, IP ranges, VPC, or other services.

For more information, see [Restricting network access](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-restrict_access).



 Accessing an Enterprise instance over the private network from Classic infrastructure 

To access your Enterprise instance over the private network for workloads deployed on IBM Cloud classic infrastructure, the Virtual Route Forwarding (VRF) and Service Endpoints features must be enabled in your account. For more information, see [Restricting network access](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-restrict_access).





 Accessing an Enterprise instance over the private network from a VPC 

For workloads deployed in an IBM Cloud VPC to be able to access your Enterprise instance over the private network, a Virtual Private Endpoint (VPE) must be created in the VPC:



1.