mzha_endorsing_organization – Build Hyperledger Fabric components for a multi-zone, highly available endorsing organization
Synopsis
This role allows you to quickly build Hyperledger Fabric components for a multi-zone, highly available endorsing organization. A multi-zone, highly available endorsing organization has a certificate authority with multiple replicas and multiple peers distributed across multiple zones.
This role works with the IBM Blockchain Platform managed service running in IBM Cloud, or the IBM Blockchain Platform software running in a Red Hat OpenShift or Kubernetes cluster. The Red Hat OpenShift or Kubernetes cluster must have been configured with multiple zones.
For example, if you create a Red Hat OpenShift cluster on IBM Cloud, choose a Geography
such as North America
, Availability of Multizone
, Metro of Dallas
, and three Worker zones such as Dallas 10
, Dallas 12
, and Dallas 13
.
Consult the IBM Blockchain Platform documentation for more information on high availability configurations: https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-ha
Parameters
- api_endpoint (required)
The URL for the IBM Blockchain Platform console.
Type: str- api_authtype (required)
ibmcloud
- Authenticate to the IBM Blockchain Platform console using IBM Cloud authentication. You must provide a valid API key using api_key.
basic
- Authenticate to the IBM Blockchain Platform console using basic authentication. You must provide both a valid API key using api_key and API secret using api_secret.Type: str- api_key (required)
The API key for the IBM Blockchain Platform console.
Type: str- api_secret
The API secret for the IBM Blockchain Platform console.
Only required when api_authtype is
basic
.Type: str- api_timeout
The timeout, in seconds, to use when interacting with the IBM Blockchain Platform console.
Type: intDefault value:60
- api_token_endpoint
The IBM Cloud IAM token endpoint to use when using IBM Cloud authentication.
Only required when api_authtype is
ibmcloud
, and you are using IBM internal staging servers for testing.Type: strDefault value:https://iam.cloud.ibm.com/identity/token
- zones (required)
The list of zones, for example
dal10
,dal12
, anddal13
, that the Red Hat OpenShift or Kubernetes cluster has been configured with. The peers created by this role will be distributed across these zones.Type: listElements: str- state
absent
- All components for the endorsing organization will be stopped and removed, if they exist.
present
- All components for the endorsing organization will be created if they do not exist, or will be updated if their current configuration does not match the expected configuration.Type: strDefault value:present
- organization_name (required)
The name of the endorsing organization.
Type: str- organization_msp_id (required)
The MSP ID of the endorsing organization.
Type: str- ca_admin_enrollment_id (required)
The enrollment ID, or user name, of the identity registered as the administrator of the certificate authority.
Type: str- ca_admin_enrollment_secret (required)
The enrollment secret, or password, of the identity registered as the administrator of the certificate authority.
Type: str- ca_name
The name of the certificate authority.
By default, the certificate authority name is organization_name followed by CA, for example
Org1 CA
.Type: str- ca_db_type
postgres
- Use PostgreSQL for the certificate authority database. You must create the PostgreSQL instance that will be used by the certificate authority.Type: strDefault value:postgres
- ca_db_datasource (required)
The datasource string for the certificate authority database connection.
An example datasource string for PostgreSQL is:
host=postgresql.example.org port=5432 user=myuser password=mypassword dbname=mydb sslmode=verify-full
For more information, review the Hyperledger Fabric documentation: https://hyperledger-fabric-ca.readthedocs.io/en/release-1.4/users-guide.html#configuring-the-database
Type: str- ca_db_tls_enabled
True if the certificate authority database uses TLS to secure network communications, false otherwise.
Type: boolDefault value:true
- ca_db_tls_certfiles
The list of TLS CA certificates required to verify the connection to the certificate authority database.
TLS CA certificates must be supplied as base64 encoded PEM files.
Type: listElements: str- ca_replicas
The number of Kubernetes replicas to use for the certificate authority.
Type: intDefault value:3
- ca_resources
The Kubernetes resource configuration for the certificate authority.
For more information, review the documentation for the resources parameter of the certificate_authority module: certificate_authority
Type: dict- ca_storage
The Kubernetes storage configuration for the certificate authority.
For more information, review the documentation for the storage parameter of the certificate_authority module: certificate_authority
Type: dict- ca_version
The version of Hyperledger Fabric to use for the certificate authority.
If you do not specify a version, the default Hyperledger Fabric version will be used for a new certificate authority.
If you do not specify a version, an existing certificate authority will not be upgraded.
If you specify a new version, an existing certificate authority will be automatically upgraded.
Type: str- organization_admin_enrollment_id (required)
The enrollment ID, or user name, of the identity registered as the administrator of the organization.
Type: str- organization_admin_enrollment_secret (required)
The enrollment secret, or password, of the identity registered as the administrator of the organization.
Type: str- peers
The number of peers.
For development and test purposes, use one peer. Three peers provides high availability, even if one of the peers is taken down for maintenance, and is suitable for production networks.
Type: intDefault value:3
- peer_enrollment_id (required)
The enrollment ID, or user name, of the identity registered for the peer.
Type: str- peer_enrollment_secret (required)
The enrollment secret, or password, of the identity registered for the peer.
Type: str- peer_name
The name of the peer.
If more than one peer is being created using the peers parameter, then a number will be appended to the specified peer name.
By default, the peer name is organization_name followed by Peer, for example
Org1 Peer
.Type: str- peer_state_db
couchdb
- Use CouchDB as the state database for this peer.
leveldb
- Use LevelDB as the state database for this peer.Type: strDefault value:couchdb
- peer_resources
The Kubernetes resource configuration for the peer.
For more information, review the documentation for the resources parameter of the peer module: peer
Type: dict- peer_storage
The Kubernetes storage configuration for the peer.
For more information, review the documentation for the storage parameter of the peer module: peer
Type: dict- peer_version
The version of Hyperledger Fabric to use for the peer.
If you do not specify a version, the default Hyperledger Fabric version will be used for a new peer.
If you do not specify a version, an existing peer will not be upgraded.
If you specify a new version, an existing peer will be automatically upgraded.
Type: str- peer_zones
The zones to use for each peer. You must specify a zone for each peer specified by peers.
Only use this parameter if you wish to override the default zone allocation algorithm provided by the zones parameter.
Type: listElements: str- wallet
The wallet directory to store identity files in.
If you do not specify a wallet directory, then the wallet directory will be set to the directory containing the Ansible playbook being executed.
Type: str- ca_admin_identity
The identity file for the administrator of the certificate authority.
By default, the identity file stored in the wallet directory, and the file is named organization_name followed by CA Admin.json, for example
/path/to/my/wallet/Org1 CA Admin.json
.- organization_admin_identity
The identity file for the administrator of the organization.
By default, the identity file stored in the wallet directory, and the file is named organization_name followed by ` Admin.json`, for example
/path/to/my/wallet/Org1 Admin.json
.- wait_timeout
The timeout, in seconds, to wait until the certificate authority and the peer are available.
Type: intDefault value:60
Examples
- name: Create components for a multi-zone, highly available endorsing organization
vars:
state: present
api_endpoint: https://ibp-console.example.org:32000
api_authtype: basic
api_key: xxxxxxxx
api_secret: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
zones:
- dal10
- dal12
- dal13
organization_name: Org1
organization_msp_id: Org1MSP
ca_admin_enrollment_id: admin
ca_admin_enrollment_secret: adminpw
ca_db_datasource: host=postgresql.example.org port=5432 user=myuser password=mypassword dbname=mydb sslmode=verify-full
ca_db_tls_certfiles:
- LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0t...
organization_admin_enrollment_id: org1admin
organization_admin_enrollment_secret: org1adminpw
peer_enrollment_id: org1peer
peer_enrollment_secret: org1peerpw
wait_timeout: 3600
roles:
- ibm.blockchain_platform.mzha_endorsing_organization
- name: Destroy components for a multi-zone, highly available endorsing organization
vars:
state: absent
api_endpoint: https://ibp-console.example.org:32000
api_authtype: basic
api_key: xxxxxxxx
api_secret: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
organization_name: Org1
wait_timeout: 3600
roles:
- ibm.blockchain_platform.mzha_endorsing_organization