vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Configure CI/CD services for app deployment 

Continuous integration (CI) can help you detect errors early, ensure early system integration, and improve collaboration in your development process.

Continuous delivery (CD) is a practice by which you build and deploy your software so that it can be released into production at any time. By automating your continuous integration and delivery processes through setting up CI/CD pipelines, you can achieve repeatability in code releases and greater predictability in delivery schedules.



 Journey Map 

![Architecture](https://cloud.ibm.com/docs-content/v1/content/b7b9235ce6abd45b66931867c388cf107d38e15b/cloud-native-journey/kubernetes-on-vpc/images/cicd/journey-map.png)





 Setting up continuous integration and delivery 

To add a continuous delivery pipeline to your cluster,



1. From the [Kubernetes clusters console](https://cloud.ibm.com/kubernetes/clusters), select the cluster for which you want to set up a continuous delivery pipeline.
2. Select the DevOps tab.
3. Click Create a toolchain.

Review the available toolchains. IBM provides pre-defined toolchains that you can use to deploy, test, and monitor Kubernetes-native apps or Helm charts. You can expand each toolchain to find an overview of the tools that are set up for you and to find the scripts in GitHub that are used to configure the toolchain in your cluster. For more information about each toolchain, see [Toolchain templates](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-cd_abouttemplates). If you know what tools you want to use, you can create your own toolchain.
4. Select the toolchain that you want to use and click Create.
5. Follow the directions in the console to configure your toolchain.
IBM GBS, Expert Services or other 3rd party services projects that leverage IBM Cloud or AWS based MAS environments should avoid including infrastructure based deliverables in any contract or statement of work. This would include promising deliverables of the following nature:



* Infrastructure diagrams or design documents
* Network Diagrams
* Clustering Diagrams
* Hardware sizing and resource allocations (Cores, Memory, Storage)
* Listing of O/S, Middleware or other specific Software Versions
* IT security documents or diagrams
* Installation checklists or certifications



In the IBM MAS-Dedicated model, the IT stack is the responsibility and domain of the IBM SRE team. IBM's MAS architecture is based on best practices and empirical experience supporting a large existing customer base. With a MAS subscription, the responsibility of IBM SRE is to deliver the application in accordance with the customer's MAS subscription terms and Service Level Agreement (SLA). IBM is not obligated to provide technical details of the infrastructure used to meet it's subscription commitments. As a result, specific infrastructure based deliverables should be avoided in consulting services contracts. Technical details regarding customer infrastructure can, in some cases, be provided by the SRE team depending on the nature of the request.







 Provisioning 

Be sure both you an your customer are aware of IBM SRE provisioning lead times and have scheduled accordingly. Make sure the customer's MAS environments are ordered and will be available prior to any scheduled meetings or on-site engagements that require access to the environments. IBM's objective is to provision MAS environments within 1-2 weeks of their corresponding sales order being placed, approved and fully processed. The overall amount of time can vary depending on the size (user license) of the environment(s), total number of environments needed (for example DEV, TEST, PROD), number and type of industry solutions within each environment, number & type of add-on components such as Maximo Anywhere, availability of resources in the target data center location, and amount of orders in the queue.





 Onboarding & Implementation 



 3.1 Onboarding Roles 

The following onboarding roles should be defined:



* Client Business Leader - provides formal sign off of completed phases
Understanding IaaS basics 

As many organizations move to a cloud environment, either on-premises or hosted in data centers, the IT operations administrator's (IT ops admin) role is being redefined. The scope and complexity of this change increases significantly based on the type of environment that your organization wants to deploy.

Before you moved to the cloud, you worked with an inherently secure environment with systems that are connected to your private LAN or intranet. In a cloud environment, you're now expected to perform the following tasks:



* Procure your system components from "somewhere."
* Understand network implications and security challenges.
* Work with different technologies.
* Integrate the new environment with tools that are not natively part of the cloud stack.
* Continue to support your internal customers as if you still have an on-premises data center.



IBM Cloud® is here to support you 100% on your journey. The resources available to you include comprehensive documentation, planning tools, qualified support specialists, and an active user community. Let's get you started on your journey.



 Video transcript 

Welcome to IBM Cloud! As an IT operations administrator, you had your choice of any number of cloud providers. You chose IBM Cloud because it's a leader in cloud as a service. We offer superior levels of security, functionality, integration, interoperability, and usability.

Use the IBM Cloud console to get access to our catalog of over 190 unique services across several categories including Security, Compute, Network, Storage, Integration, and Data Management [Click Catalog menu item, then select from the categories listed in the transcript]. In addition to the catalog, there are a variety of tools to help you plan your hosting environment before you begin provisioning it. One tool is the [IBM Cloud Design Decision Tool](https://github.com/ibm-cloud-architecture/infrastructure-design-decision-tool), which helps you compare infrastructure designs so you can build the best IBM Cloud solution to suit your needs.

After you've planned and designed your infrastructure, use the cost estimator [Click Cost estimator icon then click Review summary] to see how much your infrastructure will cost before placing your order. You can access it by clicking the Cost Estimator icon in the console menu bar.
esxcli software vib update -v /<path to vsan or nfs datastore from step 3>/vmware-storcli.vib --no-sig-check The following installation results are displayed. Message: Operation finished successfully. Reboot Required: false VIBs Installed: Broadcom_bootbank_vmware-storcli_007.xxx.0000.0000-01 VIBs Removed: LSI_bootbank_vmware-storcli_007.xxx.0000.0000-01 VIBs Skipped:
5. Run the following command to validate the installation: > esxcli software vib list |grep vmware-storcli vmware-storcli 007.xxx.0000.0000-01 Broadcom PartnerSupported yyyy-mm-dd
6. Repeat for each host.







 Procedure to upgrade the ESXi hosts 



1. From the vCenter Server user interface, go to LCM menu > LifeCycle Manager.
2. Select IMPORT ISO > IMPORT ISO, and then the VMware-VMvisor-Installer-7.0U1c-17325551.iso file.
3. Create the baseline. Select BASELINE > CREATE and use the imported ISO from the previous step.
4. For each host, select the host in the vCenter browser tree, then select update (located in the far left in the main window).
5. If the Zerto VRA is present on the host, put the host into maintenance mode first. Recent releases of Zerto stop the VRA, which otherwise would prevent the update.
6. Complete the update.



1. [ATTACH] Baseline, select the previously created baseline.
2. Select Baseline and [REMEDIATE].



7. Remediate each host in turn. After remediation, ensure to pull the host out of maintenance mode.



If the upgrade process fails immediately and the host cannot enter maintenance mode error message is displayed, shut down the Zerto ZVAs and try again.
"state" : "ACTIVE",
"pipeline_state" : "PIPELINE_SUCCEEDED",
"href" : "/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd/drafts/2"
},
"project_id" : "db268db0-160b-4911-8f93-89659000a927",
"version" : 1,
"is_draft" : false,
"state" : "NOT_INSTALLED",
"pipeline_state" : "PIPELINE_SUCCEEDED",
"update_available" : true,
"created_at" : "2023-02-22T19:51:23.253Z",
"updated_at" : "2023-02-22T19:51:23.253Z"
}
<-- </section "id="section-project-config-check-cli-output" "> --><-- </section "id="section-project-cli-config-check-command" "> --><-- <section "id="section-project-cli-config-install-command" "> --> ibmcloud project config-install Deploy a project's configuration. It's an asynchronous operation that can be tracked using the get project configuration API with full metadata. ibmcloud project config-install --project-id PROJECT-ID --id ID
<-- <section "id="section-project-config-install-cli-options" "> --> Command options --project-id (string): The unique project ID. Required.
The maximum length is 128 characters. The value must match regular expression /^\.\-0-9a-zA-Z] +$/.
--id (string): The unique config ID. Required.
If the value that you provided is valid and you still received this error, contact IBM support to clarify about the entitlement.





 Why does my instance provisioning remain in Starting state? 

 What’s happening 

After you apply a plan, the workspace takes a long time to provision the virtual server instance, and you notice in the user interface that the virtual server instance remains in Starting state.

 Why it’s happening 

During the apply plan process, Terraform initiates the provisioning process of the virtual server instance in the cloud infrastructure. If there is a capacity issue or any issue from the infrastructure side for that particular region and zone, you might see this issue.

 How to fix it 

You can try to manually create an instance in the user interface with the same image that is used during the automation process to see whether you get the same issue, or you can try a different zone for the deployment. You can also raise a support request for this issue to see whether it's originating from the infrastructure side.





 Why am I getting errors when I try to delete resources after a bare metal server fails to provision? 

After a bare metal server fails to provision and you try to delete resources from the bootstrap node, you are receiving the following error after you apply the mmcloudworkflows cluster destroy command: [ERROR] Error deleting security group target binding while deleting security group : The specified network interface is not attached to any other security groups.

 What’s happening 

If cluster provisioning fails, it's recommended to clean up all of the resources from the failed provision before you attempt to reprovision a cluster.

 Why it’s happening 

During the destroy process, the bootstrap node tries to clean up all of the resources that were created during the provisioning phase. It's possible that if a bare metal server provisioning took longer than expected and then failed, then during a subsequent cleanup, the destroy process complains that the failed bare metal server is still attached to a security group that it is attempting to destroy.

 How to fix it 

Copy the cluster prefix name and complete the following steps:



1. Go to the security group and access the -storage-sg.
2. Go to the attached resources section for the security group.
3.
For example, do you intend to use it for development and testing, or production? Are you testing a user experience, processing lengthy algorithms, backing up and restoring data, or increasing latency speed? 
 4. Size and cost out your server You can use the [bare metal search tool](https://cloud.ibm.com/gen1/infrastructure/provision/bm) to help you size and cost out your server. 
 5. Log in to your IBM Cloud account You can access the Bare Metal Server Order Form from the IBM Cloud catalog or the IBM Cloud console. You need an [IBMid and password](https://cloud.ibm.com/docs/account?topic=account-account-getting-startedgetting-started) to access IBM Cloud catalog and console.<br><br><br><br> * [IBM Cloud catalog](https://cloud.ibm.com/catalog)<br> * [IBM Cloud console](https://cloud.ibm.com/)<br><br><br> 
 6. Provision your server You have three options when it comes to provisioning your server: fast provisioning, custom, and SAP-certified. Fast provisioning servers are pre-configured servers that meet the needs of most customers and can be ready to configure 30 - 40 minutes after provisioning.<br><br>Custom servers are servers that you create by selecting specific compute, connectivity, storage, and network options to meet your needs. Custom servers take longer to provision, usually 2 - 4 hours, and have higher operating costs. You can [Provision an Intel® Optane-compatible bare metal server](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-provision-optane-server) or one with an [Intel® SGX architecture](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-server-provision-sgx). SAP-certified servers are certified to support SAP HANA and SAP NetWeaver landscapes.<br><br>Use the following links for provisioning information for that type of server.
* [Creating a storage assignment in the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-object-storage-pluginstorage-ibm-object-storage-plugin-include-assignment-create-console)
* [Creating an assignment in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-object-storage-pluginstorage-ibm-object-storage-plugin-include-assignment-create-cli)
* [Creating a storage assignment in the API](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-object-storage-pluginstorage-ibm-object-storage-plugin-include-assignment-create-api)
* [Deploying an app that uses IBM Cloud Object Storage](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-object-storage-pluginconfig-storage-cos-app)
* [Removing the IBM Cloud Object Storage storage configuration using the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-object-storage-pluginconfig-storage-cos-rm-ui)
* [Removing the IBM Cloud Object Storage storage configuration using the command line](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-object-storage-pluginconfig-storage-cos-rm-cli)
* [Parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-object-storage-pluginibm-object-storage-plugin-parameter-reference)



* [2.2 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-object-storage-pluginibm-object-storage-plugin-2.2-parameters)
[NetApp ONTAP-NAS](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nasstorage-netapp-ontap-nas)



* [Prerequisites for NetApp ONTAP-NAS](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nasnetapp-nas-2104-pre)
* [Creating and assigning a configuration in the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nasnetapp-ontap-nas-config-create-console)
* [Creating a configuration in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nasnetapp-ontap-nas-config-create-cli)
* [Creating a configuration in the API](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nasnetapp-ontap-nas-config-create-api)
* [Creating a storage assignment in the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nasstorage-netapp-ontap-nas-include-assignment-create-console)
* [Creating an assignment in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nasstorage-netapp-ontap-nas-include-assignment-create-cli)
* [Creating a storage assignment in the API](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nasstorage-netapp-ontap-nas-include-assignment-create-api)
Ordering FortiGate Virtual Appliance 

You can include the FortiGate® Virtual Appliance service with a new VMware vCenter Server® instance or add the service to your existing instance.

You can deploy the service on a single-zone (new or existing) or multizone (existing only) instance. For multizone instances, three FortiGate Virtual Appliances are installed, one for each of the three gateway clusters.



 Ordering FortiGate Virtual Appliance for a new instance 



1. When you [order the instance](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-procedure), scroll down to the Add-on services section. FortiGate Virtual Appliance is in the Security and compliance category.
2. Open the category, locate FortiGate Virtual Appliance, and toggle its switch on.
3. Click Edit to review and specify [the configuration information](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-fortinetvm_orderingfortinetvm_ordering-config), then click Save.



You cannot install Juniper® vSRX and FortiGate Virtual Appliance on the same gateway cluster.





 Ordering FortiGate Virtual Appliance for an existing instance 



1. On the instance details page, click the Services tab.
2. Click Add to add the service.
3. On the Add services page, locate the FortiGate Virtual Appliance service in the Security and Compliance section and toggle its switch on.
4. Click Edit to review and specify [the configuration information](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-fortinetvm_orderingfortinetvm_ordering-config), then click Save.







 Ordering FortiGate Virtual Appliance for private instances 

When you order FortiGate Virtual Appliance for instances that are not configured with public interfaces, you must provide a proxy server to complete the installation.
This option creates a logical volume by using this device and mounts the volume to the appliance in a location appropriate for storing the database. The default location is /var/lib/pgsql, which can be found in the environment variable $APPLIANCE_PG_MOUNT_POINT.
* Enter 2 to continue without partitioning the disk. A second prompt confirms this choice. Selecting this option results in using the root file system for the data directory (not advised in most cases).



7. Enter N for "Should this appliance run as a stand-alone database server?"



* Select N to configure the appliance with the full administrative user interface.



8. When prompted, enter a unique number (01-99) to create a new region.

Important: Creating a new region deletes any existing data on the chosen database.
9. Create and confirm a password for the database.

Infrastructure management configures the internal database. This takes a few minutes.
10. Once Infrastructure management is installed, you can log in and complete administrative tasks.



* Log in to Infrastructure management for the first time by:
* Select the URL for the login screen. For example, https://xx.xx.xx.xx on the virtual server instance, where xx.xx.xx.xx is the floating IP.
* Enter the default credentials (Username: admin | Password: smartvm) for the initial login.
* Click Login.









 Step 4. Register Infrastructure management instance with IAM as an OIDC client 

In order to enable single sign-on (SSO) between IBM Cloud Pak for Multicloud Management and Infrastructure management with OIDC, the Infrastructure management instance needs to register as an OIDC client with Identity and Access Management (IAM). Complete these steps on the IBM Cloud Pak for Multicloud Management cluster.

Note:

Only OIDC-based authentication (OpenID Connect) is supported. The configuration of OpenID Connect (OIDC) is required for integration with Infrastructure management and IBM Cloud Pak for Multicloud Management.
For more information, see [Preparing the installation environment](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcxclient-planning-prep-install). 
 Initial NSX configuration As part of the deployment of your vCenter Server instance, a sample customer network is available that consists of a private subnet, a public subnet, an NSX logical switch, a distributed logical router, and an NSX edge appliance that is deployed and configured to perform network address translation. For steps to configure this sample customer network for your VMs, see [Configuring your network to use the customer-managed NSX ESG with your VMs](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_esg_configvc_esg_config). 
 Add a logical switch Logical switches are similar to VLANs, in that they provide network connections to which you can attach your VMs. The VMs can then communicate with each other over VXLAN if the VMs are connected to the same logical switch. When you are adding logical switches, it is important to have in mind a particular topology that you are building. For more information, see [Add a logical switch](https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.4/com.vmware.nsx.install.doc/GUID-DD31D6BC-2E56-4E91-B45F-FCA3E80FF786.html). 
 Add a DLR A Distributed Logical Router (DLR) is a virtual appliance that routes between connected logical switches (East-West traffic).
[Set up a hypervisor](https://cloud.ibm.com/docs/virtualization?topic=virtualization-setting-up-a-hypervisor). [Setting up a virtual machine Network](https://cloud.ibm.com/docs/virtualization?topic=virtualization-setting-up-a-virtual-machine-network) is an important part of this process. 
 __ 3. Depending on which virtualization solutions that you are using, you can [set up Hyper-V](https://cloud.ibm.com/docs/virtualization?topic=virtualization-setting-up-hyper-v), [Get started with Virtuozzo](https://cloud.ibm.com/docs/virtualization?topic=virtualization-getting-started-with-virtuozzo), [Get started with VMware vSphere 6](https://cloud.ibm.com/docs/vmware?topic=vmware-vmware-getting-started), or [Install XenServer tools](https://cloud.ibm.com/docs/virtualization?topic=virtualization-installing-xenserver-tools-when-using-linux).
3. Find the host-uuid in a XenServer by using the following command:

xe host-list

The uuid (RO) is the 'host-uuid' that you need.
4. Create a Storage Repository (SR):

The [sr-create](http://support.citrix.com/article/CTX121313) command is for adding a new hard disk drive. Creating a hard disk drive is a destructive process that partitions and formats the drive, and any data on the drive is lost. If you want to reintroduce a drive that has existing data, use [sr-introduce](http://support.citrix.com/article/CTX121896).

 xe sr-create content-type=user device-config:device=/dev/disk/by-id/ host-uuid= name-label=”Local Storage 2” shared=false type=lvm

- Or

 xe sr-create content-type=user device-config:device=/dev/disk/by-id/ host-uuid= name-label=”Local Storage 2” shared=false type=lvm

- Or

 xe sr-create content-type=user device-config:device=/dev/ host-uuid= name-label=”Local Storage 2” shared=false type=lvm







 Verifying the storage repository in XenCenter 

You can verify the storage repository from XenCenter by usig the following steps.



1. Connect to XenCenter.
2. Go to Storage to find the details of all storage repositories. You can see the storage 'Local Storage2' in the list that shows that the disk is added. Now you can start creating VDIs on it.