Commit 4b352051 authored by joe-alewine's avatar joe-alewine Committed by Joe Alewine
Browse files

[FAB-14430] Add raft to whats new



Cherry picking change merged in master

Add Raft info to whats new doc.

Change-Id: I235fd068ee78ea5a89542a24f68811277a8bdcb1
Signed-off-by: default avatarjoe-alewine <Joe.Alewine@ibm.com>
(cherry picked from commit d2fad4bec54418fd79ee81fac80baf3be2c4a71c)
parent 98b9b0a5
What's new in v1.4 What's new in v1.4
================== ==================
Hyperledger Fabric's First long term support release Hyperledger Fabric's First long term support release
---------------------------------------------------- ----------------------------------------------------
Hyperledger Fabric has matured since the initial v1.0 release, and so has the Hyperledger Fabric has matured since the initial v1.0 release, and so has the
community of Fabric operators. The Fabric developers have been working with community of Fabric operators. The Fabric developers have been working with
network operators to deliver v1.4 with a focus on stability and production network operators to deliver v1.4 with a focus on stability and production
operations. As such, v1.4 will be our first long term support release. operations. As such, v1.4 will be our first long term support release.
Our policy to date has been to provide bug fix (patch) releases for our most Our policy to date has been to provide bug fix (patch) releases for our most
recent major or minor release until the next major or minor release has been recent major or minor release until the next major or minor release has been
published. We plan to continue this policy for subsequent releases. However, published. We plan to continue this policy for subsequent releases. However,
for Hyperledger Fabric v1.4, the Fabric maintainers are pledging to provide for Hyperledger Fabric v1.4, the Fabric maintainers are pledging to provide
bug fixes for a period of one year from the date of release. This will likely bug fixes for a period of one year from the date of release. This will likely
result in a series of patch releases (v1.4.1, v1.4.2, …), where multiple fixes result in a series of patch releases (v1.4.1, v1.4.2, and so on), where multiple
are bundled into a patch release. fixes are bundled into a patch release.
If you are running with Hyperledger Fabric v1.4, you can be assured that If you are running with Hyperledger Fabric v1.4, you can be assured that
you will be able to safely upgrade to any of the subsequent patch releases. you will be able to safely upgrade to any of the subsequent patch releases.
In the advent that there is need of some upgrade process to remedy a defect, In the advent that there is need of some upgrade process to remedy a defect,
we will provide that process with the patch release. we will provide that process with the patch release.
Serviceability and operations improvements Raft ordering service
------------------------------------------ ---------------------
As more Hyperledger Fabric networks get Introduced in v1.4.1, `Raft <https://raft.github.io/raft.pdf>`_ is a crash fault
deployed and enter a production state, serviceability and operational aspects tolerant (CFT) ordering service based on an implementation of Raft protocol in
are critical. Fabric v1.4 takes a giant leap forward with logging improvements, `etcd` <https://coreos.com/etcd/>`_. Raft follows a "leader and follower" model,
health checks, and operational metrics. As such, Fabric v1.4 where a leader node is elected (per channel) and its decisions are replicated to
is the recommended release for production operations. the followers. Raft ordering services should be easier to set up and manage than
Kafka-based ordering services, and their design allows organizations spread out
* :doc:`operations_service`: across the world to contribute nodes to a decentralized ordering service.
The new RESTful operations service provides operators with three
services to monitor and manage peer and orderer node operations: * :doc:`ordering_service`:
Describes the role of an ordering service in Fabric and an overview of the
* The logging ``/logspec`` endpoint allows operators to dynamically get and set three ordering service implementations currently available: Solo, Kafka, and
logging levels for the peer and orderer nodes. Raft.
* The ``/healthz`` endpoint allows operators and container orchestration services to * :doc:`raft_configuration`:
check peer and orderer node liveness and health. Shows the configuration parameters and considerations when deploying a Raft
ordering service.
* The ``/metrics`` endpoint allows operators to utilize Prometheus to pull operational
metrics from peer and orderer nodes. Metrics can also be pushed to StatsD. * :doc:`raft_configuration_tutorial`:
Shows the process for configuring and deploying a Raft ordering service and
Improved programming model for developing applications for selecting a subset of available nodes to create the ordering service for a
------------------------------------------------------ channel. Uses the network from the :doc:`build_network` tutorial.
Writing decentralized applications has just gotten easier. Programming model * :doc:`orderer_deploy`:
improvements in the Node.js SDK and Node.js chaincode makes the development Describes the process for deploying an ordering node, independent of what the
of decentralized applications more intuitive, allowing you to focus ordering service implementation will be.
on your application logic. The existing npm packages are still available for
use, while the new npm packages provide a layer of abstraction to improve Serviceability and operations improvements
developer productivity and ease of use. ------------------------------------------
New documentation helps you As more Hyperledger Fabric networks enter a production state, serviceability and
understand the various aspects of creating a decentralized application for operational aspects are critical. Fabric v1.4 takes a giant leap forward with
Hyperledger Fabric, using a commercial paper business network scenario. logging improvements, health checks, and operational metrics. As such, Fabric v1.4
is the recommended release for production operations.
* :doc:`developapps/scenario`:
Describes a hypothetical business network involving six organizations who want * :doc:`operations_service`:
to build an application to transact together that will serve as a use case The new RESTful operations service provides operators with three
to describe the programming model. services to monitor and manage peer and orderer node operations:
* :doc:`developapps/analysis`: * The logging ``/logspec`` endpoint allows operators to dynamically get and set
Describes the structure of a commercial paper and how transactions affect it logging levels for the peer and orderer nodes.
over time. Demonstrates that modeling using states and transactions
provides a precise way to understand and model the decentralized business process. * The ``/healthz`` endpoint allows operators and container orchestration services to
check peer and orderer node liveness and health.
* :doc:`developapps/architecture`:
Shows how to design the commercial paper processes and their related data * The ``/metrics`` endpoint allows operators to utilize Prometheus to pull operational
structures. metrics from peer and orderer nodes. Metrics can also be pushed to StatsD.
* :doc:`developapps/smartcontract`: Improved programming model for developing applications
Shows how a smart contract governing the decentralized business process of ------------------------------------------------------
issuing, buying and redeeming commercial paper should be designed.
Writing decentralized applications has just gotten easier. Programming model
* :doc:`developapps/application` improvements in the Node.js SDK and Node.js chaincode makes the development
Conceptually describes a client application that would leverage the smart contract of decentralized applications more intuitive, allowing you to focus
described in :doc:`developapps/smartcontract`. on your application logic. The existing npm packages are still available for
use, while the new npm packages provide a layer of abstraction to improve
* :doc:`developapps/designelements`: developer productivity and ease of use.
Describes the details around contract namespaces, transaction context,
transaction handlers, connection profiles, connection options, wallets, and New documentation helps you
gateways. understand the various aspects of creating a decentralized application for
Hyperledger Fabric, using a commercial paper business network scenario.
And finally, a tutorial and sample that brings the commercial paper scenario to life:
* :doc:`developapps/scenario`:
* :doc:`tutorial/commercial_paper` Describes a hypothetical business network involving six organizations who want
to build an application to transact together that will serve as a use case
New tutorials to describe the programming model.
-------------
* :doc:`developapps/analysis`:
* :doc:`write_first_app`: Describes the structure of a commercial paper and how transactions affect it
This tutorial has been updated to leverage the improved Node.js SDK and chaincode over time. Demonstrates that modeling using states and transactions
programming model. The tutorial has both JavaScript and Typescript examples of provides a precise way to understand and model the decentralized business process.
the client application and chaincode.
* :doc:`developapps/architecture`:
* :doc:`tutorial/commercial_paper` Shows how to design the commercial paper processes and their related data
As mentioned above, this is the tutorial that accompanies the new Developing structures.
Applications documentation.
* :doc:`developapps/smartcontract`:
* :doc:`upgrade_to_newest_version`: Shows how a smart contract governing the decentralized business process of
Leverages the network from :doc:`build_network` to demonstrate an upgrade from issuing, buying and redeeming commercial paper should be designed.
v1.3 to v1.4. Includes both a script (which can serve as a template for upgrades),
as well as the individual commands so that you can understand every step of an * :doc:`developapps/application`
upgrade. Conceptually describes a client application that would leverage the smart contract
described in :doc:`developapps/smartcontract`.
Private data enhancements
------------------------- * :doc:`developapps/designelements`:
Describes the details around contract namespaces, transaction context,
* :doc:`private-data-arch`: transaction handlers, connection profiles, connection options, wallets, and
The Private data feature has been a part of Fabric since v1.2, and this release gateways.
debuts two new enhancements:
And finally, a tutorial and sample that brings the commercial paper scenario to life:
* **Reconciliation**, which allows peers for organizations that are added
to private data collections to retrieve the private data for prior * :doc:`tutorial/commercial_paper`
transactions to which they now are entitled.
New tutorials
* **Client access control** to automatically enforce access control within -------------
chaincode based on the client organization collection membership without having
to write specific chaincode logic. * :doc:`write_first_app`:
This tutorial has been updated to leverage the improved Node.js SDK and chaincode
Release notes programming model. The tutorial has both JavaScript and Typescript examples of
============= the client application and chaincode.
The release notes provide more details for users moving to the new release, along * :doc:`tutorial/commercial_paper`
with a link to the full release change log. As mentioned above, this is the tutorial that accompanies the new Developing
Applications documentation.
* `Fabric release notes <https://github.com/hyperledger/fabric/releases/tag/v1.4.0>`_.
* `Fabric CA release notes <https://github.com/hyperledger/fabric-ca/releases/tag/v1.4.0>`_. * :doc:`upgrade_to_newest_version`:
Leverages the network from :doc:`build_network` to demonstrate an upgrade from
.. Licensed under Creative Commons Attribution 4.0 International License v1.3 to v1.4.x. Includes both a script (which can serve as a template for upgrades),
https://creativecommons.org/licenses/by/4.0/ as well as the individual commands so that you can understand every step of an
upgrade.
Private data enhancements
-------------------------
* :doc:`private-data-arch`:
The Private data feature has been a part of Fabric since v1.2, and this release
debuts two new enhancements:
* **Reconciliation**, which allows peers for organizations that are added
to private data collections to retrieve the private data for prior
transactions to which they now are entitled.
* **Client access control** to automatically enforce access control within
chaincode based on the client organization collection membership without having
to write specific chaincode logic.
Release notes
=============
The release notes provide more details for users moving to the new release, along
with a link to the full release change log.
* `Fabric v1.4.0 release notes <https://github.com/hyperledger/fabric/releases/tag/v1.4.0>`_.
* `Fabric v1.4.1 release notes <https://github.com/hyperledger/fabric/releases/tag/v1.4.1>`_.
* `Fabric CA release notes <https://github.com/hyperledger/fabric-ca/releases/tag/v1.4.0>`_.
.. Licensed under Creative Commons Attribution 4.0 International License
https://creativecommons.org/licenses/by/4.0/
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment