vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Configuring and deploying a deployable architecture 

After you add a deployable architecture to your project, you can edit the input values to configure the architecture for deployment.

Configurations can be generic, but many projects use a configuration, or a group of configurations, to deploy resources to different environments. For example, a group of configurations can be used to deploy resources to development, test, and production environments and set up common services outside of the environments. When you deploy your configuration, IBM Cloud® Schematics uses Terraform to apply the underlying plan.

Before you can deploy your project, the inputs, plan, compliance, and estimated cost for the deployable architecture must be validated. Any changes that are made to the configuration are validated to ensure that there aren't any issues or failures.



 Setting input values 

Input values are used to configure a deployable architecture to match your specific needs. The required inputs vary based on the deployable architecture that you choose. They are a set of common inputs that are used to provide shared input values across any number of configurations.

The input's attribute allows variables to be imported from any number of outputs of different configurations, even from other projects. By doing so, the dev environment of an app project can easily be linked to the dev environment of an infrastructure project. Or common input values can easily be shared across environments and projects.





 Configuring the architecture 

To create a customized configuration, complete the following steps:



1. From the Security panel, select the authentication method that you want to use to deploy your architecture.

Add an API key by using IBM Cloud® Secrets Manager. This authorizes the project to deploy to a target account and is required to deploy your configuration. For more information, see [Using an API key with Secrets Manager to authorize a project to deploy an architecture](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-authorize-project).
2. During validation, a Code Risk Analyzer scan is run on your architecture. Select the controls that you want to use during validation. You can use the Architecture default controls, or the Select from Security and Compliance Center option if you have an attachment set up in your target account.
Environments 

Environments in App Configuration represent your application environments. Typical environments might be dev, staging, or production. Environments manage your feature flags and properties into deployments from development to production. Create your environments based on your development requirements.

When you create an App Configuration instance, an environment is created in the name dev by default.

Each feature flag or properties that are created has its own values, tags, and segment rules for each environment. You can also toggle the feature flag per environment so that you can have different rules for flags per environment for the same feature flag or properties.

By default, the environment page displays the list of environments that are created in the current App Configuration service instance along with Name, Environment ID, date of creation, and labels.

Zoom

![List of environments](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-environments-default.png)

Figure 1. List of environments



  Create an environment 

To create an environment, complete these steps:



1.  In the App Configuration console, click Environments.
2.  Click Create. The side panel opens with fields for creating a new environment.

Zoom

![Create environment](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-environments-create.png)

Figure 2. Creating a new environment
3.  Provide the following environment details:



*  Name - name of the environment.
*  Environment ID - the environment ID value is auto suggested based on the entered environment name. You can modify the same, if needed. Use the Environment ID value as the identifier in your SDK or API code.
*  Description - add a description of the environment, which is optional.
*  Optionally, define Tags to identify the environment.
*  Click the color image to change the Color code for this environment, which is optional.



4.  Click Create.
In addition, fine grained access control to configurations within a project can be used to restrict the set of users are allowed to approve and deploy changes to production infrastructure.







 Rationale for centralized infrastructure as code management 

Centralizing management of deployable architectures and their configuration into a production administration account for each BU provides the following benefits:



* BU operators can manage their own workloads within the constraints that are imposed by the centralized organization

The application and infrastructure catalogs ensure that only approved, tested, and compliant deployable architectures are available. Using two catalogs makes it easy to set an IAM policy such that users have access to the correct set of deployable architectures according to their roles. For example, DevOps users get access to infrastructure and application developers get access to application development tools.
* Centralized access control and monitoring for the BU

Placing the catalogs and projects in a centralized account makes it easier to ensure the principle of least privilege is applied. Use of projects also ensures that credentials with the capability to manipulate applications and infrastructure are not accessible to users and thus cannot be misused. Finally, keeping these related projects in the BU account makes it easy to monitor deployments and ensure that the infrastructure is up to date and compliant.
* Ensures that development and production are aligned

Using a single project across development and production makes it possible to align development and test environments with production environments. The single project helps reduce the chance of defects that are related to environmental differences while providing control to the team over testing new deployable architecture versions in different environments. It also ensures that the lifecycle of these resources is properly managed across all environments. For example, if a project is no longer needed, it is easy to clean up all resources across nonproduction and production environments.
* Allows all project resources to be tracked for accounting and configuration management

Using a single project across nonproduction and production ensures that all project (or application) resources are tracked and allocated to the project. Projects enforce resource tagging and track resource providence, approvals, and so on. This ensures that accounting and configuration management needs are covered.
* Only one schematics agent is needed per BU
A peer is owned and maintained by an organization.





 performance 

The measurement of a Watson system in terms of accuracy, precision, and recall, for example, when answering questions, discovering relationships, or annotating text.





 plan 

The packaging construct by which APIs are made available to consumers. A plan makes available a collection of resources or operations from one or more APIs, and is published to communities of application developers.





 platform as a service (PaaS) 

The delivery of a computing platform, including applications, optimized middleware, development tools, and Java and Web 2.0 runtime environments, in a cloud-based environment.





 pod 

A group of containers that are running on a Kubernetes cluster. A pod is a runnable unit of work, which can be a either a stand-alone application or a microservice.





 point of presence (PoP) 

A physical location that stores servers and routers in a network cloud.





 policy 

A piece of configuration that controls some aspect of processing in the gateway during the handling of an API invocation. Policies are the building blocks of assembly flows and provide the means to configure capability, such as security, logging, caching, routing of requests to target services, and transformation of data from one format to another. Policies can be configured in the context of an API or in the context of a plan.





 PoP 

See [point of presence](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx5458832).





 POS 

See [part of speech](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx3271709).





 pre-annotation 

The process of annotating a set of documents prior to human annotation. Documents can be pre-annotated by using a rule-based model, a machine-learning model, IBM Watson Natural Language Understanding, or a dictionary. Pre-annotation can help human annotators more quickly prepare a set of ground truth documents.





 precision 

A measurement that specifies the proportion of results that are relevant.
Integrating OpenLDAP with IBM Spectrum Symphony 

In the following tutorial, you learn how to integrate OpenLDAP with IBM Spectrum Symphony, which is a high-performance distributed computing platform. OpenLDAP is an open source implementation of the Lightweight Directory Access Protocol (LDAP) that can be used to store and manage information about users, groups, and other objects in a network.

In the tutorial, you learn the steps that are involved in configuring IBM Spectrum Symphony to use OpenLDAP as the primary directory service for user authentication. You also learn about the benefits of integrating OpenLDAP with IBM Spectrum Symphony, such as centralized user management, improved security, and simplified user authentication.

This tutorial covers configuring the OpenLDAP server on a Linux® system.



 Architecture 

The integration between OpenLDAP and IBM Spectrum Symphony involves the following components:



1. OpenLDAP directory service: This component stores and manages user authentication data, such as usernames and passwords.
2. IBM Spectrum Symphony distributed computing platform: This component uses the authentication data from OpenLDAP to authenticate users and enable them to run analytical and data-intensive applications.
3. LDAP authentication process: This process enables IBM Spectrum Symphony to communicate with OpenLDAP and authenticate users by using their existing credentials.



The OpenLDAP integration with IBM Spectrum Symphony architecture enables centralized user management, improved security, and simplified user authentication. The integration also allows for the use of existing authentication credentials, reducing the need for users to remember multiple login credentials. Overall, the architecture provides a robust and efficient solution for user authentication and directory management in distributed computing environments.





 Before you begin 

Before you get started, be sure to review the following prerequisites:



 General prerequisites 

To successfully integrate OpenLDAP with IBM Spectrum Symphony, the following system requirements and prerequisites must be met:



1. OpenLDAP is installed on a dedicated server or the same server as IBM Spectrum Symphony.
2. IBM Spectrum Symphony is installed on a supported operating system with the latest patches and updates.
3. You have a user account with administrative privileges on both OpenLDAP and IBM Spectrum Symphony.
4. You are familiar with LDAP authentication and directory services.
* Does Hyper Protect Crypto Services with Unified Key Orchestrator provide key management, governance, and orchestration at the same time?

Yes. Unified Key Orchestrator provides a simplified means of key management, governance, and orchestration: one place to define, operate, and oversee encryption keys across hybrid multicloud environments.
* Is Unified Key Orchestrator a separate offering?

No. From a technology point of view, Unified Key Orchestrator is a feature of Hyper Protect Crypto Services. You need to provision and deploy a Hyper Protect Crypto Services instance to implement and use Unified Key Orchestrator.
* How is Hyper Protect Crypto Services with Unified Key Orchestrator different from the Hyper Protect Crypto Services Standard Plan?

Hyper Protect Crypto Services with Unified Key Orchestrator extends the Standard Plan. IBM Cloud is the only cloud service provider that offers native cloud encryption key orchestration and lifecycle management across hybrid multicloud environments, including IBM Cloud, IBM Satellite, other cloud service providers, and on-premises environments.
* What type of HSM is used for Hyper Protect Crypto Services with Unified Key Orchestrator?

Hyper Protect Crypto Services with Unified Key Orchestrator is built on the FIPS 140-2 Level 4 certified HSM as the Hyper Protect Crypto Services Standard Plan.
* Which cloud vendors or providers are supported by Hyper Protect Crypto Services with Unified Key Orchestrator as connected external keystores?

The following list contains a few cloud providers:



* Keystores of another Hyper Protect Crypto Services instance
* Keystores of IBM® Key Protect for IBM Cloud®
* Keystores of IBM® Key Protect for IBM Cloud® on Satellite
* Microsoft Azure Key Vault
* AWS Key Management Service
* Google Cloud Key Management Service



* How is Unified Key Orchestrator different from EKMF Web?

IBM® Enterprise Key Management Foundation - Web Edition (EKMF Web) and Unified Key Orchestrator share the same code base.

EKMF Web is an on-premises product for IBM Z14 or Z15 environments, running z/OS V2.3 or z/OS V2.4 and IBM Db2. Hyper Protect Crypto Services with Unified Key Orchestrator is a cloud native service in IBM Cloud, which offers key management and orchestration in a hybrid multicloud environment.
This tutorial presents setup of a privately routed IP connection over the IBM Cloud private network between two secure private networks hosted in different data centers. All resources are owned by one IBM Cloud account. It uses the Isolate workloads with a secure private network tutorial to deploy two private networks that are securely linked over the IBM Cloud private network using the VLAN Spanning service.

Virtual Router Appliance Virtual Servers for Classic

+1

VLANs



* 2023-05-05



[Plan, create and update deployment environments](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-plan-create-update-deployments)Plan, create and update deployment environments

Multiple deployment environments are common when building a solution. They reflect the lifecycle of a project from development to production. This tutorial introduces tools like the IBM Cloud CLI and Terraform to automate the creation and maintenance of these deployment environments.

Kubernetes service Virtual Servers for Classic

+5

Object Storage,Cloudant,,Activity Tracker hosted event search,Monitoring



* 2 hours
* 2023-05-05



[Hosting web applications from a secure private network](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-web-app-private-network)Hosting web applications from a secure private network

This tutorial takes you through the creation of a scalable and secure Internet facing web application hosted in private network secured using a virtual router appliance (VRA), VLANs, NAT and firewalls. The application comprises a load balancer, two web application servers and a MySQL database server. It combines three tutorials to illustrate how web applications can be securely deployed on the IBM Cloud IaaS platform using classic networking.

Virtual Router Appliance IBM Cloud Load Balancer

+1

Virtual Servers for Classic



* 2023-05-05



[Migrating a virtual server between classic data centers](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-migrating-vsi-new-datacenter)Migrating a virtual server between classic data centers
Every IBM Cloud service that you run in your Satellite location, such as Red Hat OpenShift on IBM Cloud, comes with a set of options for how to increase service availability. Make sure to review the documentation of each service to find supported options.







 Basic control plane worker setup 

The following image shows a basic Satellite location control plane worker node setup. This setup ensures that your Satellite location control plane has sufficient compute capacity to run basic Satellite workloads and that your control plane continues to run, even if one compute host becomes unavailable.

Zoom

![Default setup for the Satellite control plane.](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite/images/sat_ha_default.svg)

Figure 2. Satellite control plane

Review the characteristics of the basic setup.



* Groups of 3 compute hosts: In the basic setup, you must assign at least 3 compute hosts as worker nodes to the Satellite location control plane, in separate zones. With 3 hosts, you make sure that your control plane continues to run, even if one compute host becomes unavailable. The minimum of 3 hosts for the Satellite location control plane is for demonstration purposes only. To continue to use the location for production workloads, [add more hosts to the location control plane](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hosts) in multiples of 3, such as 6, 9, or 12 hosts. Note that while you can deploy a cluster to a location with only 3 control plane hosts, upgrading and other management operations may not work with bare minimums setups.
* Host requirements: All compute hosts must meet the [minimum host requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs). Hosts can be in your own on-premises data center, in public cloud providers, or in edge computing environments. You can add compute hosts from different physical locations if you ensure that the requirements for the network speed and latency between the hosts are met.
Note that while you can deploy a cluster to a location with only 3 control plane hosts, upgrading and other management operations may not work with bare minimums setups.
* Host requirements: All compute hosts must meet the [minimum host requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs). Hosts can be in your own on-premises data center, in public cloud providers, or in edge computing environments. You can add compute hosts from different physical locations if you ensure that the requirements for the network speed and latency between the hosts are met. For more information about how to configure hosts that you want to add from your public cloud providers like AWS, Azure, or Google, see [Cloud infrastructure providers](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-plan).
* Separate physical hosts: Every compute host must have a separate physical host. The host might be a bare metal machine or a virtual machine that does not share the hypervisor with another virtual machine that you plan to add to your control plane. With this setup, you ensure that the outage of one physical machine does not lead to all Satellite location control plane worker nodes becoming unavailable.



To make your control plane worker nodes more highly available, see the [Highly available control plane worker setup](https://cloud.ibm.com/docs/satellite?topic=satellite-hasatellite-ha-setup).





 Highly available control plane worker setup 

Make your Satellite control plane worker nodes more highly available to provide more compute capacity and prepare for a local data center or infrastructure provider failure.

Depending on where your hosts are, the options that are available to you to increase availability might vary. Use the following table to determine how you can improve availability for your compute hosts. The options in this table are sorted with increased availability.



High availability for the location control plane worker nodes.

 High availability option Description 

 Add more compute hosts. To increase compute capacity but also increase availability of your Satellite control plane, you can add more compute hosts as worker nodes to the control plane.
Contact your IBM salesperson or the IBM CDS Project Office: SaaSIOTPPO/Dallas/IBM to obtain a current copy of the provisioning form for your customer.





 1.2.2 Component Verification 

It is important to check with your IBM salesperson to insure all necessary products and components have been included in the customer MAS order. This will help eliminate the need for re-work by the IBM SRE team after the initial environments have been provisioned and avoid unnecesssary delays. Examples of MAS items or components that may be overlooked on an order include:

Number of Environments:

The correct number and type of environments. Two (2) environments are provided by default on MAS orders: (PROD and TEST). Additional environments can be provisioned at an added cost. PROD environments are sized to support the total number of concurrent or authorized users specified on the order.

Sizing:

All PROD and NON-PROD environment sizing is specified on the SQO order. Clients are required to specify the sizing (Dev, extra small, small, medium, large). Environments are not designed or sized for load testing activities.

Have all applicable Industry Solutions and add-on components (Scheduler, SAP or Oracle Connector, Health, Aviation, etc) been ordered?

Will a replicated copy of the PROD database be needed for offline reporting or data extraction purposes? If yes, an add-on reporting database should be included on the order.

Further details on MAS components can be found in the Service Description for the offering.





 1.3 Statement of Work (SOW) or Contract Considerations 

The following contains items that should be included and considered in any Statement of Work or Contract that involves the use of IBM MAS environments





 1.3.1 Project Plan and Project Schedule 

The following are items that should be considered for the project plan and schedule. IBM SRE has found these are often overlooked and should be reviewed and considered. Please note SRE is not ultimately responsible for establishing your project's plan and schedule, but can and should be consulted.

The Project Management Plan should include, but not be limited to the following:



* Client (or designate) is responsible for the Project Manager role