vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can also edit the cloud-init section of the cloud.config file so that the cloud-init steps are automatically run on each boot. For the steps, see the [Edit the cloud_cloud_init_modules section of the cloud.config file to run on each boot](https://cloud.ibm.com/docs/vpc?topic=vpc-user-dataedit-cloud-init-run-cloud-config-each-boot) section.





 Configuring a two disk instance storage by using cloud-config script 

The following example shows user data that automatically configures an instance storage disk. This example can be used with an instance profile that specifies two disks.

cloud-config
 Cloud-init supports simple partition and file system config.
 This user data yaml will create a full partition on the first two
 virtio_blk devices after the boot device, initialize ext4 on them and
 mount them on new folders off of ‘/mnt/’.

disk_setup:
/dev/vdb:
table_type: 'mbr'
layout:
- 100
overwrite: false
/dev/vdc:
table_type: 'mbr'
layout:
- 100
overwrite: false

fs_setup:
- label: /mnt/inststg1
filesystem: 'ext4'
device: /dev/vdb1
overwrite: false
- label: /mnt/inststg2
filesystem: 'ext4'
device: /dev/vdc1
overwrite: false

runcmd:
- [ mkdir, /mnt/inststg1 ]
- [ mkdir, /mnt/inststg2 ]

mounts:
- ["/dev/vdb1", "/mnt/inststg1"]
- ["/dev/vdc1", "/mnt/inststg2"]
Edit the cloud_cloud_init_modules section of the cloud.config file to run on each boot 

The cloud-config script in the previous example automatically configures an instance storage /dev/vdb block device. If you only reboot your virtual server, this configuration continues to work since the configuration and data persists. However, if you start a virtual server that was previously stopped, then the virtual server has a fresh set of instance storage disks when it boots up. This situation would require the cloud-init steps to be manually run again. By default, the cloud-config script is only run on first boot.



* You must already have provisioned an instance with the User Data field specifying the cloud-init yaml data from the previous example.
* When you log in to the started instance, the file system must already be configured and mounted.
* You do not have other directives in the disk_setup or mount sections in the cloud-config yaml specified as user data.



To run the cloud-config script on each successive boot, follow this procedure:



1. Edit the etc/cloud/cloud.cfg file.
2. Look for the cloud_init_modules section. This section contains the disk_setup and mount modules.
3. Change the disk_setup and mount modules lines to always. The section looks like this.

 The modules that run in the 'init' stage
cloud_init_modules:
- migrator
- seed_random
- bootcmd
- write-files
- growpart
- resizefs
- [disk_setup, always]
- [mounts, always]
- set_hostname
- update_hostname
- update_etc_hosts
- ca-certs
- rsyslog
- users-groups
- ssh
Show more
4. Save the file, then stop and then start the instance. Your mount is automatically created to a newly partitioned and formatted file system.











 User data example for Windows 

The following example shows user data that can be passed to a Windows instance.
Configuring the Data Crawler 

The Data Crawler is no longer supported or available for download beginning [17 April 2019](https://cloud.ibm.com/docs/discovery?topic=discovery-release-notes17apr19). This content is provided for existing installations only. See [Connecting to Data Sources](https://cloud.ibm.com/docs/discovery?topic=discovery-sources) for other available connectivity options.

To set up the Data Crawler to crawl your repository, you must specify the appropriate input adapter in the crawler.conf file, and then configure repository-specific information in the input adapter configuration files.

Before making the changes listed in these steps, make sure that you create your working directory by copying the contents of the {installation_directory}/share/examples/config directory to a working directory on your system, for example /home/config.

Do not modify the provided configuration example files directly. Copy and then edit them. If you edit the example files in-place, your configuration might be overwritten when upgrading the Data Crawler, or it might be removed when uninstalling it.

References in this guide to files in the config directory, such as config/crawler.conf, refer to that file in your working directory, and NOT in the installed {installation_directory}/share/examples/config directory.

The specified values are the defaults in config/crawler.conf, and configure the Filesystem connector:



1. Open the config/crawler.conf file in a text editor.



* Set the crawl_config_file option to the .conf that you previously modified, for example: connectors/filesystem.conf.
* Set the crawl_seed_file option to the -seed.conf that you previously modified, for example: seeds/filesystem-seed.conf.
* Set the output_adapterclass and config options for Discovery as follows:

class - "com.ibm.watson.crawler.discoveryserviceoutputadapter.DiscoveryServiceOutputAdapter"
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.

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



* Log in to Red Hat CloudForms 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.



For more information, see: [Configuring CloudForms](https://access.redhat.com/documentation/en-us/red_hat_cloudforms/5.0/html/installing_red_hat_cloudforms_on_red_hat_openstack_platform/configuring-cloudforms)







 Step C. Integrating CloudForms with IBM Cloud Pak for Multicloud Management 

Enable navigation to CloudForms within the IBM Cloud Pak® console.

Complete the following steps on a Linux system. You can use the boot node from the HUB cluster where IBM Cloud Pak for Multicloud Management is installed.
[Natural Language Understanding](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_natlang_understandingpkg_natlang_understanding)



* [Creating a Natural Language Understanding service instance](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_natlang_understandingservice_instance_understanding)
* [Installing the Natural Language Understanding package](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_natlang_understandinginstall_understanding)



* [Installing from the Cloud Functions CLI](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_natlang_understandingnlus_cli)
* [Installing from the Cloud Functions console](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_natlang_understandingnlus_ui)



* [Using the Natural Language Understanding package](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_natlang_understandingusage_understanding)



[Tone Analyzer](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_tone_analyzerpkg_tone_analyzer)



* [Creating a Tone Analyzer service instance](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_tone_analyzerservice_instance_tone)
* [Installing the Tone Analyzer package](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_tone_analyzerinstall_tone)
If the destination_field already exists a new instance of the destination_field is created.
* merge - the contents of the source_field and the destination_field are merged into the destination_field.
* remove_nulls - fields with null content are removed.



* "source_field": string - optional - the field that the operation is performed on.
* "destination_field": string - optional - the destination field the the operation is output to.

Field names defined in your configuration must meet the restrictions defined in [Field Name Requirements](https://cloud.ibm.com/docs/discovery?topic=discovery-configreffield_reqs).











 Enrichments 

"enrichments": [
{
"enrichment": "elements",
"source_field": "html",
"destination_field": "enriched_html",
"options": {
"model": "contract"
}
},
{
"enrichment": "natural_language_understanding",
"source_field": "title",
"destination_field": "enriched_title",
"options": {
"features": {
"keywords": {
"sentiment": true,
"emotion": false,
"limit": 50
},
"entities": {
"sentiment": true,
"emotion": false,
"limit": 50,
"mentions": true,
"mention_types": true,
"sentence_locations": true,
"model": "WKS-model-id"
},
"sentiment": {
"document": true,
"targets":
"IBM",
"Watson"
]

},
"emotion": {
"document": true,
"targets":
"IBM",
"Watson"
]
},
"categories": {},
"concepts": {
"limit": 8
},
"semantic_roles": {
The frontend application uses an environment variable (BACKEND_URL) to know where the backend application is hosted. You now need to update the frontend application to set this value to point to the backend application's endpoint.

ibmcloud code-engine application update --name frontend --env BACKEND_URL=$BACKEND_PRIVATE_URL

The --env flag can appear as many times as you would like if you need to set more than one environment variable. This option could have also been used on the ibmcloud code-engine application create command for the frontend application if you knew its value at that time. Learn more by reading the [Working with environment variables](https://cloud.ibm.com/docs/codeengine?topic=codeengine-envvar) documentation topic.
4. Hard refresh the frontend URL on the browser to test the connection to the backend application. You should see a page with an option to upload a text file(.txt) and also an error message from the backend application as the backend is still not connected with the required IBM Cloud services to store and process the text files. Clicking on Upload text file should also show a similar error message.









 Step 4: Connect the backend application to Object Storage service 

In this section, you will provision the required Object Storage and Natural Language Understanding services and bind the Object Storage service to the backend application. The backend application will store the text files into the Object Storage, while the Natural Language Understanding will be used later in the tutorial to perform text analysis on the uploaded text files.

With IBM Watson® Natural Language Understanding, developers can analyze semantic features of text input, including categories, concepts, emotion, entities, keywords, metadata, relations, semantic roles, and sentiment.



 Provision Object Storage and Natural Language Understanding services 



1. Create an instance of [Object Storage](https://cloud.ibm.com/catalog/services/cloud-object-storage)



1. Select the Lite plan or the Standard plan if you already have an Object Storage service instance in your account.
2. Set Service name to code-engine-cos.
3.
Understanding your compliance posture 

You can use the IBM Cloud® Security and Compliance Center Workload Protection UI to understand your environment's compliance posture.



 Accessing the compliance overview view 

To access the Compliance overview view, do the following:



1. Open the [Workload Protection UI](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-launch).
2. Hover over the Posture icon ![Posture icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection//images/posture.png) and click Compliance.



The compliance posture for each of your [zones](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-zones) is displayed.

Zoom

![Example compliance overview.](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection/images/compliance_view.png)

Figure 1. Example compliance view

Zones are listed alphabetically. The default Entire Infrastructure zone is [automatically created by IBM Cloud Security and Compliance Center Workload Protection](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-cspm-zones). You can define your own zones using the [Zones page.](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-zones)

Compliance posture information displayed includes:

Zone/Policy
: Indicates the zones where policies have been defined in your environment.

Passing Score
: Indicates the percentage of policy requirements that are passing. The higher the percentage the more compliant your system is.

Requirements Failing
: Indicates the number of policy requirements that need to be fixed to get the passing score to 100%.
Ray [Ray](https://www.ray.io/) is an open technology that enables data scientists and application developers to run their code in a distributed fashion. It also provides a lean and easy interface for distributed programming with many different libraries, best suited to perform machine learning and other intensive compute tasks. See [Ray on IBM Cloud Code Engine: Boost Your Serverless Compute](https://www.ibm.com/cloud/blog/ray-on-ibm-cloud-code-engine). 
 Iter8 [Iter8](https://iter8.tools) is the release engineering tool for Kubernetes that enables SLO validation, A/B testing, and progressive rollouts for Kubernetes applications. You can use Iter8 to validate your Code Engine applications. See [Validating your application code and latency with Iter8](https://cloud.ibm.com/docs/codeengine?topic=codeengine-slovalidationtut). 
 Guard [Guard](https://pkg.go.dev/knative.dev/security-guardsection-readme) is a workload runtime-security solution, well-equipped to protect Serverless Services. Code Engine users may use Guard as a security layer to protect Code Engine applications. See [Securing your application with Guard](https://cloud.ibm.com/docs/codeengine?topic=codeengine-getting-started-with-guard).
A route is a global resource that is not bound to a specific region.



Table 1. Required IAM roles

 IAM action IAM Policy scope IAM Roles Description 

 atracker.route.read Account Administrator <br>Editor <br>Viewer <br>Operator Read (view) information about a route 
 atracker.route.create Account Administrator <br>Editor Create a route 
 atracker.route.update Account Administrator <br>Editor Update a route 
 atracker.route.delete Account Administrator <br>Editor Delete a route 
 atracker.route.list Account Administrator <br>Editor <br>Viewer <br>Operator List all routes 







 CLI prerequisites 

Before you use the the CLI to manage routes, install the latest Activity Tracker Event Routing CLI V2 plugin in your local system. See [Installing the Activity Tracker Event Routing CLI](https://cloud.ibm.com/docs/atracker?topic=atracker-atracker-cli-config&interface=cli).

Next, log in to the IBM Cloud. Run the following command: [ibmcloud login](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliibmcloud_login)





 Creating a route using the CLI 

Use this command to create a new route for an Activity Tracker Event Routing target.

ibmcloud atracker route create --name ROUTE_NAME ( --target-ids TARGETS [--locations REGIONS] | --rules RULES | --file RULES_DEFINITION_JSON_FILE ) [--output FORMAT]



 Command options 

--name ROUTE_NAME
: The name to be given to the route.

Do not include any personal identifying information (PII) in any resource names.

--file RULES_DEFINITION_JSON_FILE
: A JSON file containing the definition of the rules for route. The file needs to be formatted as follows:

[
{
"locations": "LOCATION1","LOCATION2"],
A service account provides an identity for processes that run in an instance. For built-in service accounts, you can use the shortened names manager, none, reader, and writer. You can also use the full names that are prefixed with the Kubernetes Config Context, which can be determined with the project current command. This value is optional.

--service-account-clear, --sac
: Clear the service account. This value is optional. The default value is false.

--wait, -w
: Resubmit the job run and wait for the instances of this job run to complete. If you specify the --wait option, the job run resubmit waits for a maximum time in seconds, as set by the --wait-timeout option, for the job run to complete. If the job run is not completed within the specified --wait-timeout period, the job run resubmit fails. This value is optional. The default value is false.

--wait-timeout, --wto
: The length of time in seconds to wait for the instances of this job run to complete. This value is required if the --wait option is specified. This value is ignored if the --no-wait option is specified. The default value is 600.





 Example 

The following example reruns the myjobrun job run for instances 4-5. The name of the resubmitted job run is myjobresubmit.

ibmcloud ce jobrun resubmit --name myjobresubmit --jobrun myjobrun --array-indices 4-5





 Example output 

Getting job run 'myjobrun'...
Rerunning job run 'myjobresubmit'...
Run 'ibmcloud ce jobrun get -n myjobresubmit' to check the job run status.
OK







 ibmcloud ce jobrun submit 

Submit a job run based on a job.
Business unit administration account 

Each production business unit (BU) account group has a business unit administration account. This account enables BUs to self-administer their workload accounts and applications across development and production enterprises.

Self-administration is constrained to the capabilities of the deployable architectures (infrastructure as code templates) provided in the application and infrastructure catalogs.

Zoom

![BU Admin IaC diagram. All of the information is conveyed in the surrounding text.](https://cloud.ibm.com/docs-content/v1/content/f18e964848e0337fedc42d43e246fa446f4b9646/enterprise-account-architecture/images/bu-hub.svg)

Figure 1. BU administration account infrastructure as code

Deployable architectures in the infrastructure catalog enable workload accounts to be created and provisioned with the shared infrastructure needed to host applications in a secure and compliant manner.



Table 1. Components

 Component Quantity Description 

 Application catalog 1 Used to host the approved deployable architectures for the application projects in this BU 
 Infrastructure catalog 1 Used to host the approved deployable architectures for the shared infrastructures projects in this BU 
 Application development project n Manages the infrastructure as code for deploying application development resources such as Git repos, toolchains, container registries, evidence lockers and also requests namespaces, network egress rules, and so on within the shared infrastructure. The applications themselves are built and then deployed onto dev and prod shared infrastructure by using these tools 
 Shared infrastructure project n Manages the infrastructure as code for deploying dev and prod workload accounts and the shared infrastructure within those accounts 
 IaC Dev Project 1 Manages the infrastructure as code for deploying dev and test IaC accounts. These accounts are used for developing and testing deployable architectures 
 Application - Infrastructure Sets n Conceptual grouping - groups a set of application projects and the project that deploys the infrastructure to host those applications 



Zoom

![BU Admin service diagram. All of the information is conveyed in the surrounding text.]
"Example Account Group",
enterpriseAccountIamID,
)

createAccountGroupResponse, response, err := enterpriseManagementService.CreateAccountGroup(createAccountGroupOptions)
if err != nil {
panic(err)
}
b, _ := json.MarshalIndent(createAccountGroupResponse, "", " ")
fmt.Println(string(b))

const params = {
parent: parentCrn,
name: 'Example Account Group',
primaryContactIamId: enterpriseAccountIamId,
};

enterpriseManagementService.createAccountGroup(params)
.then(res => {
console.log(JSON.stringify(res.result, null, 2));
})
.catch(err => {
console.warn(err)
});

For detailed information about the API, see [Enterprise Management API](https://cloud.ibm.com/apidocs/enterprise-apis/enterprise).







 Moving accounts within the enterprise 

You can move accounts anywhere within your enterprise. For example, you can move an account from a child account group into its parent account group, or you can move it directly under the enterprise. Accounts can be moved only within the enterprise. They can't be moved to a different enterprise or removed from the enterprise to be a stand-alone account.

To move an account, you need the Administrator role on the Billing service in the enterprise account and the Editor or Administrator role on either the entire enterprise or both the current and target account groups.



 Moving an account in the console 



1. From the Enterprise dashboard in the console, click Accounts.
2. In the Accounts section, click the Actions icon !
Infrastructure as code development accounts 

In addition to consuming existing infrastructure as code to create hub and workload accounts, organizations will need a set of accounts to develop, extend, and maintain any custom infrastructure as code.

Zoom

![IaC Accounts Diagram. All of the information is conveyed in the surrounding text.](https://cloud.ibm.com/docs-content/v1/content/f18e964848e0337fedc42d43e246fa446f4b9646/enterprise-account-architecture/images/iac-accounts.svg)

Figure 1. Infrastructure as code development accounts

One account is used for infrastructure as code development. This account contains infrastructure as code development tools such as toolchains, Git repos, and catalogs of infrastructure as code modules for use in development. It also includes a test catalog where test versions of the infrastructure as code are published to be used in a test project.



Table 1. IaC Tools Components

 Component Quantity Description 

 Development catalog 1 Used to host the approved deployable architectures for the infrastructure as code development projects in this account 
 Test catalog 1 Used to host the versions of deployable architectures under test 
 Infrastructure as code development project n Manages the infrastructure as code for deploying infrastructure as code development resources such as Git repos, toolchains, container registries, and evidence lockers. The terraform is then published into a test catalog for deployment testing. The project also contains a configuration that deploys the infrastructure as code into the test account from the test catalog. 
 Development resource group n Contains the infrastructure as code development resources such as Git repos, toolchains, container registries, and evidence lockers for a single infrastructure as code development project 
 Schematics agent 1 Used enable privately hosted custom deployable architectures in the private catalog 
 Schematics workspaces n Orchestrated by projects, used to deploy the deployable architectures and store terraform state. One workspace per configuration within each project. 



A second account is used for test deployments of the new infrastructure as code versions.



Table 2. IaC Test Components

 Component Quantity Description