You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At a high level, upgrading a Fabric network to v1.2 can be performed by following these
4
+
At a high level, upgrading a Fabric network to v1.3 can be performed by following these
5
5
steps:
6
6
7
7
* Upgrade the binaries for the ordering service, the Fabric CA, and the peers.
8
8
These upgrades may be done in parallel.
9
9
* Upgrade client SDKs.
10
-
* Enable the v1.2 capability.
10
+
* Enable the two v1.3 capabilities.
11
11
* (Optional) Upgrade the Kafka cluster.
12
12
13
13
To help understand this process, we've created the :doc:`upgrading_your_network_tutorial`
14
14
tutorial that will take you through most of the major upgrade steps, including
15
-
upgrading peers, orderers, as well as the capability. We've included both a
15
+
upgrading peers, orderers, as well as the capabilities. We've included both a
16
16
script as well as the individual steps to achieve these upgrades.
17
17
18
18
Because our tutorial leverages the :doc:`build_network` (BYFN) sample, it has
@@ -21,7 +21,12 @@ included a section at the end of the tutorial that will show how to upgrade
21
21
your CA, Kafka clusters, CouchDB, Zookeeper, vendored chaincode shims, and Node
22
22
SDK clients.
23
23
24
-
If you want to learn more about capability requirements, click `here <http://hyperledger-fabric.readthedocs.io/en/latest/capability_requirements.html>`_.
24
+
If you want to learn more about capability requirements, check out the
25
+
:doc:`capability_requirements` documentation.
26
+
27
+
.. note:: With the removal of the old Event Hub in v1.3, please make sure to
28
+
update your applications to be compatible with the :doc:`peer_event_services`,
29
+
otherwise your applications may break after upgrade.
25
30
26
31
.. Licensed under Creative Commons Attribution 4.0 International License
0 commit comments