vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* --allowed-vlans: Comma-separated VLAN IDs. Indicates which VLAN IDs (for VLAN interfaces only) can use this PCI interface. It can be passed as separate values or as any range of numbers.
* --vlan: Indicates the 802.1Q VLAN ID tag that must be used for all traffic on this VLAN interface.
* --allow-interface-to-float: Indicates if the interface can float to any other server within the same resource_group. The interface floats automatically if the network detects a GARP or RARP on another bare metal server in the resource group. Applies only to VLAN interfaces. One of: false, true. (default: false).
* --allow-ip-spoofing: Allow IP Spoofing (AIS). If true, source IP spoofing is allowed on packets that are using this network interface. If false, source IP spoofing is prevented on this interface. One of: false, true. (default: false).
* --enable-infrastructure-nat: Enable Infrastructure NAT (EIN). If true, the VPC infrastructure performs any needed NAT operations. If false, the packet is passed unmodified to or from the network interface, allowing the virtual machine that is associated with the floating IP to perform any needed NAT operations. One of: true, false. (default: true).
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is bare-metal-server-network-interface-delete 

Remove one or more network interfaces from a bare metal server.

ibmcloud is bare-metal-server-network-interface-delete SERVER (NIC1 NIC2 ...) [--output JSON] [-f, --force] [-q, --quiet]



 Command options 



* SERVER: ID or name of the server.
PE-13 - Fire Protection 



  Control requirements 

PE-13 - 0
:   The organization employs and maintains fire suppression and detection devices/systems for the information system that are supported by an independent energy source.





  NIST supplemental guidance 

This control applies primarily to facilities containing concentrations of information system resources including, for example, data centers, server rooms, and mainframe computer rooms. Fire suppression and detection devices/systems include, for example, sprinkler systems, handheld fire extinguishers, fixed fire hoses, and smoke detectors.
If you add worker nodes to your cluster and add raw block storage to those workers, restart the Portworx pods on the new worker nodes so that your storage volumes are detected by the DaemonSet.
4. Verify that each storage node is listed with the correct amount of raw block storage by reviewing the Capacity column in the Cluster Summary section of your CLI output.
5. Review the Portworx I/O classification that was assigned to the disks that are part of the Portworx cluster. During the setup of your Portworx cluster, every disk is inspected to determine the performance profile of the device. The profile classification depends on how fast the network is that your worker node is connected to and the type of storage device that you have. Disks of SDS worker nodes are classified as high. If you manually attach disks to a virtual worker node, then these disks are classified as low due to the slower network speed that comes with virtual worker nodes.

oc exec -it <portworx_pod> -n kube-system -- /opt/pwx/bin/pxctl cluster provision-status

Example output

NODE NODE STATUS POOL POOL STATUS IO_PRIORITY SIZE AVAILABLE USED PROVISIONED RESERVEFACTOR ZONE REGION RACK
10.184.58.11 Up 0 Online LOW 20 GiB 17 GiB 3.0 GiB 0 B 0 dal12 us-south default
10.176.48.67 Up 0 Online LOW 20 GiB 17 GiB 3.0 GiB 0 B 0 dal10 us-south default
10.176.48.83 Up 0 Online HIGH 3.5 TiB 3.5 TiB 10 GiB 0 B 0 dal10 us-south default







 Creating a Portworx volume 

Start creating Portworx volumes by using [Kubernetes dynamic provisioning](https://cloud.ibm.com/docs/openshift?topic=openshift-kube_conceptsdynamic_provisioning).



1. List available storage classes in your cluster and check whether you can use an existing Portworx storage class that was set up during the Portworx installation. The pre-defined storage classes are optimized for database usage and to share data across pods.
In the plan, you can see that Move2Kube has detected all the services related to the enterprise-app application. This includes the order, customer, and inventory backend services, as well as the gateway, and the frontend.

This plan is used along with the manifest.yml files associated with each of the enterprise-app services in the source directory to do the transformation.

Now that you have all the artifacts needed for the transformation phase, you are ready to run move2kube transform. Continue with the steps needed for your new application hosting compute service to complete the move2kube process.

Examples of next steps to use move2kube with various IBM Cloud compute services can be found [here](http://ibm.github.io/ibmcf-migration-tooling).
: The path to the app file or package to run as an action. This option is required.

--copy
: Treat the action as the name of an existing action.

--dockerDOCKER_HUB_USERNAME/IMAGE_NAME
: The Docker Hub user name and the name of the Docker image in Docker Hub to run the action. This flag is required for creating actions from Docker images.

--kindLANGUAGE
: The runtime for your app. This flag is optional. If no VALUE is specified, the default version for the detected runtime is used. Possible VALUES for the --kind option. | Language | Kind identifier | | ---- | -------------- | | Node.js | nodejs:16 (default) | | Python | python:3.11 (default) | | PHP | php:8.1 (default) | | Go | go:1.19 (default) | | Ruby | ruby:2.6 (default) | | Java | java (JDK 8) (default) | | .NET Core | dotnet:2.2 (default) |

Other languages are supported by using Docker actions.

--logsizeLIMIT, -lLIMIT
: The maximum log size in MB for the action. The default value is 10 MB.

--mainENTRY_METHOD_NAME
: If the action's entry method is not main, specify the custom name. This flag is required when the entry method is not main. For some runtimes, such as Java, the name must be the fully qualified method.

--memoryMEMORY_LIMIT
: The maximum memory limit in MB for your action. The default is 256 MB.

--native
: You can use the --native argument as shorthand for --docker openwhisk/dockerskeleton. By using this argument, you can create and deploy an executable that runs inside the standard Docker action SDK. \n - When you create a Docker image, an executable is created inside the container at /action/exec.
A VPN establishment configuration with non-immediate was detected, which could increase the time it takes for VPN establishment after the vSRX starts. Refer to [Correcting warning 1176](https://cloud.ibm.com/docs/vsrx?topic=vsrx-correcting-readiness-errorscorrecting-1176) for more information.





 Warning 1177 

The gateway experienced a precheck setup warning. A security policy using dynamic-application any was detected, which can result in packet loss. This can also cause VPN tunnel communication to fail. Refer to [Correcting warning 1177](https://cloud.ibm.com/docs/vsrx?topic=vsrx-correcting-readiness-errorscorrecting-1177) for more information.





 Warning 1178 

The license was updated. However, validation of the new license failed. It is recommended you manually check that the vSRX license is applied to each vSRX node.





 Warning 1179 

The vSRX version found to be running on the Gateway is unsupported. Operations such as OS Reload and Rebuild Cluster will overwrite the current unsupported vSRX version with the version currently listed on the Gateway Details page. Refer to [Correcting warning 1179](https://cloud.ibm.com/docs/vsrx?topic=vsrx-correcting-readiness-errorscorrecting-1179) for more information.





 Warning 1180 

The vSRX license found on the Gateway is unsupported. [Correcting warning 1180](https://cloud.ibm.com/docs/vsrx?topic=vsrx-correcting-readiness-errorscorrecting-1180) for more information.





 Warning 1181 

The vSRX license and version on the Gateway are both found to be unsupported. [Correcting warning 1181](https://cloud.ibm.com/docs/vsrx?topic=vsrx-correcting-readiness-errorscorrecting-1181) for more information.
: Returns a tuple like the function get_json_object, but it takes multiple names. All the input parameters and output column types are string.
: Example of an SQL function usage fragment

> SELECT json_tuple('{"a":1, "b":2}', 'a', 'b')
: Result value

1 2





 kurtosis 

kurtosis(expr)
: Returns the kurtosis value that is calculated from values of a group.





 lag 

lag(input[, offset[, default]])
: Returns the value of input at the offsetth row before the current row in the window. The default value of offset is 1 and the default value of default is null. If the value of input at the offsetth row is null, null is returned. If no such offset row exists (for example, when the offset is 1, the first row of the window does not have any previous row), default is returned.





 last 

last(expr[, isIgnoreNull])
: Returns the last value of expr for a group of rows. If isIgnoreNull is true, returns only nonnull values.





 last_day 

last_day(date)
: Returns the last day of the month that the date belongs to.
: Example of an SQL function usage fragment

> SELECT last_day('2009-01-12')
: Result value

2009-01-31





 last_value 

last_value(expr[, isIgnoreNull])
: Returns the last value of expr for a group of rows. If isIgnoreNull is true, returns only nonnull values.





 lcase 

lcase(str)
: Returns str with all characters that are changed to lowercase.
: Example of an SQL function usage fragment

> SELECT lcase('SparkSql')
: Result value

sparksql





 lead 

lead(input[, offset[, default]])
: Returns the value of input at the offsetth row after the current row in the window.
[Power Systems Virtual Server (AIX)](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-getting-started) You can protect Linux Unified Key Setup (LUKS) encryption keys from being compromised by using Key Protect. [View docs](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-integrate-hpcsAIX-hpcs) 
 [Discovery](https://cloud.ibm.com/docs/discovery?topic=discovery-getting-started) You can use Discovery to build cognitive, cloud-based exploration applications that analyze and provide new insights within your data. [View docs](https://cloud.ibm.com/docs/discovery?topic=watson-keyservice) 
 [Language Translator](https://cloud.ibm.com/docs/language-translator?topic=language-translator-gettingstarted) You can use Language Translator to identify the language in text and convert it into other languages. [View docs](https://cloud.ibm.com/docs/watson?topic=watson-keyservice) 
 [Speech to Text](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-gettingStarted) You can use Speech to Text to create customizable speech recognition for optimal text transcription in your application. [View docs](https://cloud.ibm.com/docs/watson?topic=watson-keyservice) 
 [Text to Speech](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-gettingStarted) You can use Text to Speech's speech-synthesis capabilities to convert written text into natural-sounding speech. [View docs](https://cloud.ibm.com/docs/watson?topic=watson-keyservice) 
 [Tone Analyzer](https://cloud.ibm.com/docs/tone-analyzer?topic=tone-analyzer-gettingStarted) You can use Tone Analyzer to detect emotional and language tones in your written texts.
@sys-date.range_link string For example, the input might be I will travel from March 15 to March 22. Each @sys-date entity that is detected has a range_link property in its output that is named date_range_14_39 where the location of the date range text is [14,39]. The start date (2020-05-15) has a role type of date_from. The end date (2020-05-22) has a role type of date_to. 
 @sys-date.relative_{timeframe} number If the input is two weeks ago, returns relative_week = -2. If the input is this weekend, returns relative_weekend = 0. If the input is today, returns relative_day = 0. 
 @sys-date.specific_{timeframe} string For 2020, returns specific_year = 2020. For Q2 2020 or second quarter 2020, returnsspecific_quarter = 2. For March, returns specific_month = 3. For Monday, returns specific_day_of_week = monday. For May 3rd, returns specific_day = 3. 
 @sys-date.year string If the input is 13 May 2020, returns 2020. 









 @sys-time 

The @sys-time system entity detects mentions of times in user input. Returns the time that is specified in user input in the format HH:mm:ss. For example, "13:00:00" for 1pm.



 Recognized formats 



* 2pm
* at 4
* 15:30







 Attributes 



* .alternatives: Captures times other than the one saved as the @sys-time value that the user might have meant when the time is not clearly indicated. The alternative values are saved as an object that contains a value and confidence for each alternative time and is stored in a JSON Array. To get an alternative value, use the syntax: @sys-time.alternative.
* .calendar_type: Specifies the calendar type for the timezone in use. GREGORIAN is the only supported type.
* .granularity: Recognizes mentions of time frames. Options are hour, minute, second and instant.
9. In the Additional BGP settings section, you can activate one or more of these optional settings.



* Verify data integrity with Message Digest 5 (MD5) - Add an extra layer of security between two BGP peers by verifying each transmitted message sent through the BGP session. When MD5 authentication is activated, BGP authenticates every segment sent over the TCP session from its peer and verifies the source of each routing update.

Important:



* You must configure the same BGP MD5 authentication key on both your Edge router and the IBM cross-connect router (XCR). The shared authentication key on the IBM device must be stored in your HPCS or Key Protect instance and shared with the Direct Link service. For more information, see [Setting up BGP Message Digest 5 (MD5) authentication keys](https://cloud.ibm.com/docs/dl?topic=dl-dl-md5).
* You can achieve hitless key refresh if the keys are updated on both your Edge router and on the IBM cross-connect router (XCR) within 90 seconds. As a pre-condition, you must configure the BGP hold time on your router to a minimum of 90 seconds. All Direct Link routers have a 90-second configuration by default. Either side can initiate the key refresh, but both sides must refresh within the configured BGP hold time to avoid traffic disruption.
* If a BGP peering session was established and you enable BGP MD5 authentication (or change the authentication key to a different value), BGP sessions are re-established, which causes BGP session downtime and network disruption until the BGP peer device is configured with the same change.



Complete the following information:



* For the keystore, select either Hyper Protect Crypto Services or Key Protect.
* Select an authentication keystore instance.
* Select an authentication key.



* Detect network failures with Bidirectional Forwarding Detection (BFD) - Activate BFD to quickly detect faults in a network between two routers or switches that are connected by a link. BFD provides a single, standardized method for detecting link failures at any protocol layer, over any media.
@sys-date.range_link string For example, the input might be I will travel from March 15 to March 22. Each @sys-date entity that is detected has a range_link object in its output that is named date_range_14_39 where the location of the date range text is [14,39]. The start date (2020-05-15) has a role type of date_from. The end date (2020-05-22) has a role type of date_to. 
 @sys-date.relative_{timeframe} number If the input is two weeks ago, returns relative_week = -2. If the input is this weekend, returns relative_weekend = 0. If the input is today, returns relative_day = 0. 
 @sys-date.specific_{timeframe} string For 2020, returns specific_year = 2020. For Q2 2020 or second quarter 2020, returnsspecific_quarter = 2. For March, returns specific_month = 3. For Monday, returns specific_day_of_week = monday. For May 3rd, returns specific_day = 3. 
 @sys-date.year string If the input is 13 May 2020, returns 2020. 









 @sys-time 

The @sys-time system entity detects mentions of times in user input. Returns the time that is specified in user input in the format HH:mm:ss. For example, "13:00:00" for 1pm.



 Recognized formats 



* 2pm
* at 4
* 15:30







 Attributes 



* .alternatives: Captures times other than the one saved as the @sys-time value that the user might have meant when the time is not clearly indicated. The alternative values are saved as an object that contains a value and confidence for each alternative time and is stored in a JSON Array. To get an alternative value, use the syntax: @sys-time.alternative.
* .calendar_type: Specifies the calendar type for the timezone in use. GREGORIAN is the only supported type.
* .granularity: Recognizes mentions of time frames. Options are hour, minute, second and instant.
"https://acme.org/foo/124",
"https://acme.org/foo/125",
],
"log": {
"url": "https://acme.org/log.txt", // the link to where the actual log of the test is
"hash": "abc123", // the hash of the log file
},
"repository_url": "https://git.acme.org/acme-repo",
"repository_revision": "asz33dkejkkjdkkl34",
"repository_branch": master,"
"required": "yes" | "no" ] // yes: this is an auditable step; no: this is a non auditable step
}, { // there could be multiple repos
"evidence_type_id": "com.ibm.detect_secret",
"version": "1.0.0",
"date": "2020-05-06T12:00:00Z", // date of task run
"origin": {
"url":"https://us-south.git.cloud.ibm.com/open-toolchain/compliance-pipelines/-/blob/master/definitions/mytask.yaml", // where the task is taken from
"version": "423792" // commit id representing the task version used to produce the evidence
}
"toolchain_crn": "crn:v1:bluemix:public:toolchain:us-south:a/190e0b4ce4cd013159917665213ddc51:7467a214-f404-4e23-acab-2e57e935d138::" // CRN of the toolchain
The web apps that are deployed as part of the server directory are accessible under the [context root, as determined by the Liberty profile](https://www.ibm.com/support/knowledgecenter/SSAW57_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/twlp_dep_war.html?cp=SSAW57_8.5.5). For example:

http://<yourappname>.mybluemix.net/acme/





 Packaged server 

You can also push a packaged server file to IBM Cloud. The packaged server file is created by using Liberty's server package command. In addition to the app and configuration files, the packaged server file can contain shared resources and Liberty user features needed by the app.

To package a Liberty server, use the ./bin/server package command from your Liberty installation directory. Specify your server name and include the --include=usr option. For example, if your Liberty server is defaultServer, run the command:

wlp/bin/server package defaultServer --include=usr

This command generates a serverName.zip file in the server's directory. If you used the --archive option to specify a different archive file, make sure it has the .zip extension instead of .jar. The buildpack does not support packaged server files created with the .jar extension.

You can then push the generated .zip file to IBM Cloud with the ibmcloud cf push command.

For example:

ibmcloud cf push <yourappname> -p wlp/usr/servers/defaultServer/defaultServer.zip

The web apps that are deployed as part of the packaged server are accessible under the context root, as determined by the Liberty profile.



 Modification of the server.xml file 

When a packaged server or a Liberty server directory is pushed, the Liberty buildpack detects the server.xml file along with your app. The Liberty buildpack makes the following modifications to the server.xml file.



* The buildpack ensures that there is exactly one httpEndpoint element in the file.
As opposed to v1 version, evidence is stored in a flat hierarchy, where each piece of evidence is identified by its own SHA256 hash, this provides a layer of integrity protection (that is, any modification of the evidence content can be detected). As each piece of evidence is related to one or more assets, the evidence summarization algorithms discover the relevant evidence based on assets (as opposed to pipeline-run IDs in v1 evidence lockers).

The only hierarchy is the type differentiation and some hash grouping similar to the structure of Git hash objects.



 Example 

.
└── raw/
├── assets/
│ └── xx/
│ └── abcdef123456789/
│ ├── evidences/
│ │ ├── 00abcdef123456789
│ │ └── 01abcdef123456789
│ └── index.json
├── attachments/
│ ├── aa/
│ │ └── abcdef123456789/
│ │ └── content
│ └── ab/
│ └── abcdef123456789/
│ └── content
├── cd/
│ ├── c9b77749-fd59-4d32-bbdb-18e55db1615d/
│ └── summary.json
| └── evdience-checks.json
├── cc/
│ ├── absd7749-fd59-4d32-bbdb-18e55db1615d/
│ └── summary.json
| └── evdience-checks.json
└── evidences/
├── 00/
│ └── abcdef123456789/
│ └── index.json
└── 01 /
└── abcdef123456789/
└── index.json
Show more







 v2 evidence collection 

The v2 evidence must be collected as near as possible to the process that created the result for an evidence. After each scan run, after each test for example.
* Little-endian orders data by least-significant bit.



The Speech to Text service automatically detects the endianness of the incoming audio.



 Notes about audio formats 



* For the audio/l16 format, you can specify the endianness to disable auto-detection if needed.







 More information 



* For more information about endianness, see [Endianness](https://wikipedia.org/wiki/Endianness).









 Audio frequency 

Audio frequency refers to the range of audible frequencies in the audio. The standard audible frequency for humans is generally accepted as 20 to 20,000 Hz. You can use spectrographic analysis to produce a spectrogram that reveals the frequency content of your audio.

The sampling rate that is applied to audio is typically twice the maximum frequency of the audio. For example, a sampling rate of 16 kHz means that the maximum frequency of the sampled audio signal is 8 kHz. The service's models are created with this is mind.



* The narrowband models are built with audio that is sampled at 8 kHz. Narrowband models expect to find information in a range that is less than or equal to 4 kHz.
* The broadband models are built with audio that is sampled at 16 kHz. Broadband models expect to find information in the 4-8 kHz range.



The training data for the models is derived from different channels (telephony for narrowband models). The models reflect the characteristics of the channels on which they were trained.



 Upsampling 

Upsampling increases the sampling rate of the audio but introduces no new information into the audio. It produces an approximation of the audio signal that would have been obtained by sampling the audio at a higher rate. It increases the size of the audio data.

The information in audio that is originally sampled at a narrowband frequency is limited to the 0-4 kHz range. Upsampling narrowband audio to a higher sampling rate is unlikely to improve speech recognition accuracy. If you upsample narrowband audio, it lacks information in the range that the broadband models expect. Furthermore, the information that is found in the expected range of a narrowband sample is qualitatively different from the information that is found in the same range of a broadband sample.