vania-janet/multiturn-rag-retrieval-data huggingface dataset:
On a channel, the lifecycle endorsement policy specifies which organizations can approve a smart contract definition and how many of them are required to approve the definition or update. The default lifecycle endorsement policy requires a majority of all organizations on the channel to approve.





 Member 

Also known as "organizations", members in a blockchain network, similar to the members of any group, form the structure of the network. A member can be as large as a multi-national corporation or as small as an individual. Members are enrolled into the network with a certificate that grants them permissions to use the network as either a service provider (for example, issuing certificates, validating/ordering transactions) or as a consumer. The former provides foundational blockchain services that include transaction validation, transaction ordering, and certificate management services. Consumer members use the network to invoke transactions against the distributed ledger. Members can have multiple Peers.





 MSP 

An abbreviation of Membership Service Provider, which provides the definition of an organization, including the root certificate of the CA issuing certificates for the entities associated with that organization, as well as the sign cert of the admin of that organization. MSPs also exist at the local level of a peer or ordering node, and are the authentication mechanism that verifies the admin users of the node. In the IBM Blockchain Platform, MSPs can be exported from one console into another, allowing users to create an organization in one console, import it to another console, and operate it (for example, to create a channel). MSPs can also be imported into an ordering service, forming a "consortium", the list of organizations allowed to create and join channels.





 Network 

An instance of an IBM Blockchain Platform service on IBM Cloud.





 Node 

The communication entity of the blockchain. There are three types of nodes: CA, peer, and ordering node.





 Ordering node 

The node that collects transactions from network members, orders the transactions and bundles them into blocks. Also known as orderer. These blocks are then distributed to peers, which then verify the blocks and add them to the ledgers on each channel. Ordering nodes contain the cryptographic identity material that is tied to each member and authenticate the identity of clients and peers to access the network.
MEP uses TCP ports 3009 and 3011. When MEP is disabled, the selection of methods is limited to the options listed before marked with an asterisk (). Any other method chosen would revert back to Round Robin.
* Monitoring: The NetScaler engine periodically evaluates the state of the remote GSLB services by using either MEP or explicit monitors bound to the services in question. Monitors are used just like on a regular load balancing service. In the case of GSLB, adding monitors to local services is not required as this is typically controlled by MEP.
* Persistence: An optional feature that establishes a site preference for a particular domain. In this particular use case, the traffic is not load balanced but handled by the same data center. This can be helpful in certain applications, like e-commerce, where transactional data is unique to each a site/server.
* GSLB site: Sites can be defined as data centers or locations where a NetScaler system is configured/present. Each GSLB site is managed by a NetScaler system that is considered “local” to that site, while all other remote systems/sites are seen and treated as “remote” sites.
* GSLB service: It is an object that represents (and is bound to) a (regular) virtual server/VIP. It can be either local (same site) or remote.
* GSLB virtual server: A GSLB virtual server is assigned to one or more GSLB services that would typically be part of different (GSLB) sites. Traffic received on it gets load balanced between the sites bound to it. The site selection is done based on the method and use case.
* GSLB domain: It represents the domain or zone for which the GSLB virtual server is responsible.
* ADNS service: A service represented by a combination of IP address and port, it is where DNS requests to a domain for which NetScaler is authoritative are sent. NetScaler takes those to the GSLB virtual server bound to that domain in order to get a response.
curl -k -u '<USERNAME>:<PASSWORD>' -XGET https://<IPADDRESS>/api/v1/node/services/syslog/exporters
{
"_schema": "NodeSyslogExporterPropertiesListResult",
"_self": {
"href": "/node/services/syslog/exporters",
"rel": "self"
},
"result_count": 0,
"results": []
}







 Removing the Syslog Server from the NSX Controller nodes (NSX-V only) 



1. Log in to the VMware vSphere™ Web Client.
2. Go to Networking & Security > Installation and Upgrade > Management > NSX Controller Nodes.
3. Select the NSX Manager that manages the NSX Controller nodes that you want to modify.
4. Click the Common Controller Attributes EDIT link.
5. Remove any Syslog Servers as needed.









 Related links 



* [Ordering VMware Aria Operations and VMware Aria Operations for Logs](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrops_ordering)
* [Managing VMware Aria Operations and VMware Aria Operations for Logs](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-managing_vrops)
* Current DC: cl-sap-1 (version 2.0.5-9.el8_4.5-ba59be7122) - partition with quorum
* Last updated: Tue Feb 14 08:34:16 2023
* Last change: Tue Feb 14 08:34:04 2023 by hacluster via crmd on cl-sap-1
* 2 nodes configured
* 11 resource instances configured

Node List:
* Online: [ cl-sap-1 ]
* OFFLINE: [ cl-sap-2 ]

Full List of Resources:
* res_fence_ibm_powervs	(stonith:fence_ibm_powervs):	 Started cl-sap-1
* Resource Group: s01_ascs01_group:
* s01_vip_ascs01	(ocf::heartbeat:IPaddr2):	 Started cl-sap-1
* s01_fs_ascs01_lvm	(ocf::heartbeat:LVM-activate):	 Started cl-sap-1
* s01_fs_ascs01	(ocf::heartbeat:Filesystem):	 Started cl-sap-1
* s01_ascs01	(ocf::heartbeat:SAPInstance):	 Started cl-sap-1
* Resource Group: s01_ers02_group:
* s01_vip_ers02	(ocf::heartbeat:IPaddr2):	 Started cl-sap-1
* s01_fs_ers02_lvm	(ocf::heartbeat:LVM-activate):	 Started cl-sap-1
* s01_fs_ers02	(ocf::heartbeat:Filesystem):	 Started cl-sap-1
* s01_ers02	(ocf::heartbeat:SAPInstance):	 Started cl-sap-1
: For more information, see the change logs: [4.11](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_411), [4.10](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_410), and [4.9](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_49).

Cloud Image Key Synchronizer add-on version 1.0.0_1200
: For more information, see the [change log](https://cloud.ibm.com/docs/openshift?topic=openshift-image-key-synchronizer-changelog).





 26 October 2022 

Worker node fix pack 4.11.9_1526_openshift, 4.10.37_1539_openshift, 4.9.50_1559_openshift, 4.8.51_1576_openshift, 4.7.59_1585_openshift, 4.6.61_1603_openshift
"peer": {
"id": "jdoe",
"networkId": "dev",
"keepalive": {
"minInterval": "60s",
"client": {
"interval": "60s",
"timeout": "20s"
},
"deliveryClient": {
"interval": "60s",
"timeout": "20s"
}
},
"gossip": {
"useLeaderElection": true,
"orgLeader": false,
"membershipTrackerInterval": "5s",
"maxBlockCountToStore": 100,
"maxPropagationBurstLatency": "10ms",
"maxPropagationBurstSize": 10,
"propagateIterations": 1,
"propagatePeerNum": 3,
"pullInterval": "4s",
"pullPeerNum": 3,
"requestStateInfoInterval": "4s",
"publishStateInfoInterval": "4s",
"stateInfoRetentionInterval": null,
"publishCertPeriod": "10s",
"skipBlockVerification": false,
"dialTimeout": "3s",
"connTimeout": "2s",
"recvBuffSize": 20,
"sendBuffSize": 200,
"digestWaitTime": "1s",
"requestWaitTime": "1500ms",
"responseWaitTime": "2s",
"aliveTimeInterval": "5s",
"aliveExpirationTimeout": "25s",
"reconnectInterval": "25s",
"election": {
"startupGracePeriod": "15s",
"membershipSampleInterval": "1s",
The [gossip data dissemination protocol](https://hyperledger-fabric.readthedocs.io/en/release-2.2/gossip.html) provides a secure, reliable, and scalable way for peers to exchange messages between each other. For example, if peers miss some blocks because of delays, network outages, or other reasons, they can sync up to the current ledger state by using gossip messaging to contact other peers in possession of these missing blocks.





 HSM 

Hardware Security Module. Provides on-demand encryption, key management, and key storage as a managed service. HSM is a physical appliance that handles the resource-intensive tasks of cryptography processing and reduce latency to applications. For more information, see [Hardware Security Module](https://www.ibm.com/cloud/hardware-security-module).





 Hyperledger Fabric 

[Hyperledger Fabric](https://hyperledger-fabric.readthedocs.io/en/release-2.2/) is a business blockchain framework that the Linux Foundation hosts to serve as a foundation for developing blockchain applications or solutions with a modular architecture. Hyperledger Fabric components such as consensus and membership services are plug-and-play.





 Install 

The process of placing a smart contract on a peer’s file system. You must install the smart contract on every peer that wants to access or change the data governed under the smart contract.





 Instantiate 

The process of starting and initializing a smart contract container on a channel with peers running Fabric v1.4.x and v1.4 capabilities. After a smart contract is installed on the peers and every peer has joined the channel, the smart contract must be instantiated on the channel. Instantiation performs any necessary initialization of the smart contract, which includes setting the key value pairs that comprise a smart contract's initial world state. After instantiation, peers that have the smart contract installed can interact with the data governed by the smart contract.
* Current DC: cl-sap-1 (version 2.0.5-9.el8_4.5-ba59be7122) - partition with quorum
* Last updated: Tue Feb 14 08:10:18 2023
* Last change: Tue Feb 14 05:02:22 2023 by hacluster via crmd on cl-sap-1
* 2 nodes configured
* 11 resource instances configured

Node List:
* Online: [ cl-sap-1 cl-sap-2 ]

Full List of Resources:
* res_fence_ibm_powervs	(stonith:fence_ibm_powervs):	 Started cl-sap-2
* Resource Group: s01_ascs01_group:
* s01_vip_ascs01	(ocf::heartbeat:IPaddr2):	 Started cl-sap-2
* s01_fs_ascs01_lvm	(ocf::heartbeat:LVM-activate):	 Started cl-sap-2
* s01_fs_ascs01	(ocf::heartbeat:Filesystem):	 Started cl-sap-2
* s01_ascs01	(ocf::heartbeat:SAPInstance):	 Started cl-sap-2
* Resource Group: s01_ers02_group:
* s01_vip_ers02	(ocf::heartbeat:IPaddr2):	 Started cl-sap-1
* s01_fs_ers02_lvm	(ocf::heartbeat:LVM-activate):	 Started cl-sap-1
* s01_fs_ers02	(ocf::heartbeat:Filesystem):	 Started cl-sap-1
* s01_ers02	(ocf::heartbeat:SAPInstance):	 Started cl-sap-1
* Clone Set: fs_sapmnt-clone [fs_sapmnt]:
Check the status of the cluster and verify that all three file system resources (nfs_fs1, nfs_fs2, nfs_fs3) are active.

pcs resource status

Sample output:

 pcs resource status
* Resource Group: nfsgroup:
* nfs_vg (ocf::heartbeat:LVM-activate): Started cl-nfs-1
* nfs_fs1 (ocf::heartbeat:Filesystem): Started cl-nfs-1
* nfs_fs2 (ocf::heartbeat:Filesystem): Started cl-nfs-1
* nfs_fs3 (ocf::heartbeat:Filesystem): Started cl-nfs-1





 Creating the nfsserver resource 

On NODE1, create a resource for managing the NFS server.

pcs resource create nfs_daemon nfsserver nfs_shared_infodir=${NFS_fs1}/stat nfs_no_notify=true --group nfsgroup

The nfs_shared_infodir parameter of the nfsserver resource specifies a directory where the NFS server stores stateful information.

Check the status of the cluster and verify that the NFS server is started.

pcs resource status

Sample output:

 pcs resource status
* Resource Group: nfsgroup:
* nfs_vg (ocf::heartbeat:LVM-activate): Started cl-nfs-1
* nfs_fs1 (ocf::heartbeat:Filesystem): Started cl-nfs-1
* nfs_fs2 (ocf::heartbeat:Filesystem): Started cl-nfs-1
* nfs_fs3 (ocf::heartbeat:Filesystem): Started cl-nfs-1
* nfs_daemon (ocf::heartbeat:nfsserver): Started cl-nfs-1





 Creating the exportfs resource
The second column lists the active IP addresses and the number of bits that are reserved for the netmask - which are separated by a slash.

If the virtual IP address for the SAP instance is not present, make sure that it isn't erroneously set on another virtual server instance.

On NODE1, run the following command.

ping -c 3 ${ASCS_vh}

Sample output:

 ping -c 2 cl-sap-scs
PING cl-sap-scs (10.111.1.248) 56(84) bytes of data.
From cl-sap-1.tst.ibm.com (10.111.1.28) icmp_seq=1 Destination Host Unreachable
From cl-sap-1.tst.ibm.com (10.111.1.28) icmp_seq=2 Destination Host Unreachable

--- cl-sap-ers ping statistics ---
2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 2112ms
pipe 3

If the ping output shows Destination Host Unreachable, the IP address is available, and you can assign the IP alias to the virtual server instance. Use the correct device name env of the network adapter that matches the subnet of the IP address.

Example command on NODE1:

ip addr add ${ASCS_ip} dev env4

Example command on NODE2:

ip addr add ${ERS_ip} dev env4

According to your specific network configuration, the device name for the network adapter might be different.

The IP address is required for the SAP installation, and is set manually. Later, the virtual IP addresses are controlled by the Red Hat HA Cluster Add-on.





 Preparing volume groups, logical volumes, and shared file systems 

Shared storage is an important resource in an ENSA2 cluster. ASCS and ERS must be able to run on both nodes, and their runtime environment is stored in the shared storage volumes. All cluster nodes need to access the shared storage volumes, but only one node has exclusive read and write access to a volume.



 Preparing High Availability Logical Volume Manager settings
[merge](https://www.npmjs.com/package/merge) Merge multiple objects into one, optionally creating a new cloned object. 
 [moment](https://www.npmjs.com/package/moment) A lightweight JavaScript date library for parsing, validating, manipulating, and formatting dates. 
 [mongodb](https://www.npmjs.com/package/mongodb) The official MongoDB driver for Node.js. 
 [mustache](https://www.npmjs.com/package/mustache) mustache.js is an implementation of the mustache template system in JavaScript. 
 [mysql](https://www.npmjs.com/package/mysql) This package is a Node.js driver for mysql. 
 [nano](https://www.npmjs.com/package/nano) Minimalistic couchdb driver for Node.js. 
 [needle](https://www.npmjs.com/package/needle) The leanest and most handsome HTTP client in the Nodelands. 
 [nodemailer](https://www.npmjs.com/package/nodemailer) Send emails from Node.js – easy as cake! 
 [oauth2-server](https://www.npmjs.com/package/oauth2-server) Complete, compliant, and well-tested module for implementing an OAuth2 Server/Provider with express in Node.js. 
 [openwhisk](https://www.npmjs.com/package/openwhisk) JavaScript client library for the OpenWhisk platform. Provides a wrapper around the OpenWhisk APIs. 
 [path-to-regex](https://www.npmjs.com/package/path-to-regexp) Turn a path string such as /user/:name into a regular expression, which can then be used to match against URL paths.
You can set an environment variable instead of specifying -i with the following command: $ export KP_INSTANCE_ID=<INSTANCE_ID>.







 Optional parameters 



* -o, --output

Set the CLI output format. By default, all commands print in table format. To change the output format to JSON, use --output json.
* --key-ring

A unique, human readable name for the key-ring. Required if the user doesn't have permissions on the default key ring.









 kp key sync 

This subcommand synchronizes the associated resources for a key.

ibmcloud kp key sync KEY_ID
-i, --instance-id INSTANCE_ID
[--key-ring KEY_RING_ID]
[-o, --output FORMAT]



 Examples 

This is an example of kp key sync.



 Example 

Synchronize a key and show the results.

 synchronize the associated resources for a given key
$ ibmcloud kp key sync 94c06f9c-a07a-4961-8548-553cf7431f18

Synchronizing key...
OK
Key's associated resources are synchronized successfully







 Required parameters 



* KEY_ID

The ID of the key that you want to sync.
* -i, --instance-id

The IBM Cloud instance ID that identifies your Key Protect instance.

You can set an environment variable instead of specifying -i with the following command: $ export KP_INSTANCE_ID=<INSTANCE_ID>.







 Optional parameters 



* -o, --output

Set the CLI output format. By default, all commands print in table format. To change the output format to JSON, use --output json.
* --key-ring

A unique, human readable name for the key-ring. Required if the user doesn't have permissions on the default key ring.









 kp key update
"value": "for-ibm"
}
],
"created_at": "2022-03-09T11:26:01Z",
"updated_at": "2022-03-09T11:26:04Z",
"created_by": "IBMid-1308197YB4",
"updated_by": "IBMid-1308197YB4",
"referenced_keystores": [],
"instances": [
{
"id": "ea7b6b27-d71b-4fe9-bbfe-309c7ca713a6",
"label_in_keystore": "IBM CLOUD KEY",
"type": "secret_key",
"keystore": {
"group": "Production",
"type": "ibm_cloud_kms"
}
}
],
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/managed_keys/3dab42dc-6941-4841-8d27-4dabcc5aa09e"
}







 hpcs uko managed-key-sync 

Sync a managed key in keystores.

ibmcloud hpcs uko managed-key-sync --id ID --uko-vault UKO-VAULT --if-match IF-MATCH



* Command options

--id (string)
: Required. The UUID of the key. You can use the ibmcloud hpcs uko managed-keys command to retrieve the key UUID.

--uko-vault (string)
: Required. The UUID of the vault where the update is to take place. You can use the ibmcloud hpcs uko vaults command to retrieve the vault UUID.

--if-match (string)
: Required. The precondition of the update, which is the value of the ETag from the header on a GET request.
Configuring Vyatta 5400 for High Availability (HA) 

Vyatta high availability is supported by using Virtual Routing Redundancy Protocol (VRRP). Each gateway group has two primary VRRP IP addresses, one for the private, and one for the public side of the networks.

Private only Vyattas have only the private VRRP.

These IP addresses are the target IPs for the network infrastructure to route all the subnets on VLANs that are associated with the gateway members. Only one Vyatta has these VRRP IPs running at a time. The other members of the gateway group have them administratively down.

Configuration can be synchronized between the two Vyattas with the config-sync configuration commands. This configuration allows one member to push the configuration of specific options to the other Vyatta in a group, and do so selectively. You can push only the firewall rules, or only the IPsec configuration, or any combination of rulesets.

It is recommended that you don't push IP addresses or other network configurations, as config-sync instantly commits your changes on the other Vyattas, bringing those interfaces online. If you want to dynamically enable interfaces and services, you can use transition scripts to perform this action on failover. Additionally, it is recommended that you use more VRRP IP addresses for your gateway IPs on associated VLANs. This makes failover easier to manage.

Your basic VRRP configuration on both machines appears similar to this sample configuration:

interfaces {
bonding bond0 {
address 10.28.94.213/26
duplex auto
hw-id 06:d6:f8:f0:fb:ee
smp_affinity auto
speed auto
vrrp {
vrrp-group 1 {
advertise-interval 1
}
preempt false
priority 254
sync-group vgroup10
rfc3768-compatibility
virtual-address 192.168.10.1/24
}
}
}
bonding bond1 {
address 50.23.184.5/26
duplex auto
The IBM Cloud services associated with the key are responsible for managing all related associated resources and ensuring that the key state and key versions are up to date.



 Syncing associated resources with the Key Protect console 



1. [Log in to the IBM Cloud console](https://cloud.ibm.com/login/).
2. Go to Menu > Resource List to view a list of your resources.
3. From your IBM Cloud resource list, select your provisioned instance of Key Protect.
4. Click on the Associated Resources tab to see the list of resources.
5. Click on the Manually sync resource icon (e.g. ![sync icon](https://cloud.ibm.com/docs-content/v1/content/0bc8db34a3d90b2a5103c9c71b08a96de9525bbc/key-protect/images/resource-icon.svg)).
6. In the Manually sync associated resource dialog box, click on the button labeled, Manually sync to perform the synchronization.







 Syncing associated resources with the Key Protect CLI plugin 

This example shows how to synchronize a key and show the results. Before getting started, make sure to complete the [required configuration](https://cloud.ibm.com/docs/key-protect?topic=key-protect-set-up-cli) for the Key Protect CLI plugin.

 synchronize the associated resources for a given key
$ ibmcloud kp key sync 94c06f9c-a07a-4961-8548-553cf7431f18

Synchronizing key...
OK
Key's associated resources are synchronized successfully



 Required parameters 



* keyID_or_alias

The ID or alias of the key that you want to sync.
* -i, --instance-id

The IBM Cloud instance ID that identifies your Key Protect instance.

You can set an environment variable instead of specifying -i with the following command: $ export KP_INSTANCE_ID=<INSTANCE_ID>.
* nfs_fs1 (ocf::heartbeat:Filesystem): Started cl-nfs-1
* nfs_fs2 (ocf::heartbeat:Filesystem): Started cl-nfs-1
* nfs_fs3 (ocf::heartbeat:Filesystem): Started cl-nfs-1
* nfs_daemon (ocf::heartbeat:nfsserver): Started cl-nfs-1





 Creating the exportfs resource 

To export the ${NFS_root} directory, add the exportfs resources to the nfsgroup group, which builds a virtual directory for NFSv4 clients. NFSv3 clients can access these exports too.

On NODE1, run the following command.

pcs resource create nfs_export exportfs clientspec=${NFS_clientspec} options=${NFS_options} directory=${NFS_root} fsid=0 --group nfsgroup





 Configuring a floating IP address resource 

Review the information in [Reserving virtual IP addresses](https://cloud.ibm.com/docs/sap?topic=sap-ha-vsiha-vsi-reserve-virtual-ip-addresses) and reserve a virtual IP address for the NFS cluster.

Create a resource for the virtual IP address of the NFS Server. NFS clients access the NFS share by using the floating IP address.

On NODE1, run the following command.

pcs resource create nfs_ip IPaddr2 ip=${NFS_ip} --group nfsgroup





 Configuring a notify resource 

The nfsnotify resource sends FSv3 reboot notifications after the entire NFS deployment initializes.

On NODE1, run the following command.

pcs resource create nfs_notify nfsnotify source_host=${NFS_ip} --group nfsgroup

The NFS cluster setup is now complete.

On NODE1, run the following command to check the status.

pcs resource status

Sample output:

 pcs resource status
* Resource Group: nfsgroup: