Releases: IBM-Blockchain/ansible-collection
Releases · IBM-Blockchain/ansible-collection
v1.0.6
v1.0.5
v1.0.4
This release includes:
- A fix to retry connection errors - for example, timeouts - when retrieving CA information (#535). This affected our CI systems, but may also affect the reliability of your playbooks.
- A fix for a problem that occurs when you name multiple components of different types the same name - for example CA =
orderer
, organization =orderer
, ordering service =orderer
(#536). - A couple of enhancements/fixes to our new GitHub Actions based CI pipeline (#534).
v1.0.3
v1.0.2
This release includes:
- Bumping the default installed version of IBM Blockchain Platform to
2.5.1-20210222
(February 2021 fix pack). - Pinning the OpenShift library for Python to
0.11.2
in the installation instructions and Docker image. This is required because the new version of this library,0.12.0
, breaks compatibility with Ansible 2.9.
v1.0.1
This release includes:
- Reliability fixes in #437 and #522; hopefully these will assist with intermittent network failures/glitches when trying to communicate with the IBM Blockchain Platform console or Hyperledger Fabric components.
- Documentation fix for the
mrha_endorsing_organization
role (#517). - You can now specify a subset of ordering service nodes for a channel at channel creation time (#518).
v1.0.0
This release includes:
- Two new roles,
mzha_endorsing_organization
andmrha_endorsing_organization
(#501, #503). These roles will allow to easily create multi-zone and multi-region endorsing organizations. - A new module,
external_peer
, that allows you to import a peer into a different IBM Blockchain Platform instance. - A fix to the
channel_policy
module that correctly handles policy type changes (#507). For example, if you tried to change a policy from a signature policy to an implicit meta policy, then that would fail. - The default version of IBM Blockchain Platform installed is now
2.5.1-20210112
, the January 2021 fix pack (#515). - Fixes to support working with IBM Blockchain Platform version
2.5.1-20210112
.
It is recommended that any users of the IBM Blockchain Platform service on IBM Cloud upgrade to this release as soon as possible, as the service has already been updated to the IBM Blockchain Platform version 2.5.1-20210112
.
v0.0.57
This release includes:
- Support for easily building a multi-zone, highly available ordering organization via a new
mzha_ordering_organization
role (#499). This will build an ordering organization that has a certificate authority with three replicas, and a five-node ordering service with the nodes distributed across the specified zones. Requires a Red Hat OpenShift or Kubernetes cluster with multiple zones. - Support for easily building a multi-region, highly available ordering organization via a new
mrha_ordering_organization
role (#502). This will build an ordering organization that has a certificate authority with three replicas, and a five-node ordering service with the nodes distributed across the specified regions. Requires three separate IBM Blockchain Platform instances, one per region. - A new
channel_consenter
module for managing a single consenter for a channel (as opposed tochannel_consenters
, which manages all of the consenters for a channel (introduced to enable #502). - A new
external_certificate_authority
module for importing a certificate authority managed by another IBM Blockchain Platform console (introduced to enable #502). - A new
external_ordering_service_node
module for importing an ordering service node managed by another IBM Blockchain Platform console (introduced to enable #502).
We would appreciate any feedback you might have on the new multi-zone and multi-region ordering organization roles! Multi-zone and multi-region endorsing organization roles will follow in a future release.
v0.0.56
This release includes:
- A fix for a problem where Ansible makes a single API call for updating the version and configuration of a component, which can result in that component losing its HSM configuration (#496). The API is being tightened up to block these kind of requests. Ansible now always makes separate API calls for updating the version and updating the configuration of a component.
v0.0.55
This release includes:
- The default version of IBM Blockchain Platform installed by this Ansible collection is now the December 2020 fix pack for IBM Blockchain Platform 2.5.1.
- The default policies (
Readers
,Writers
,Admins
, andEndorsement
) created for each organization in a channel can now be overridden (#493). - Various reliability fixes that are designed to catch and retry known errors such as timeouts and network glitches (#437).