Config update channel

The traditional data analytics in retail industry is experiencing a radical shift as it prepares to deliver more intuitive demand data of the consumers. If you are a business owner, you already know the importance of business security. Security mishaps come in different sizes and shapes, such as the occurrence of fire or thefts happening inside your business premises. All these mishaps […]. Hyperledger Fabric is a modular blockchain framework that acts as a foundation for developing blockchain-based products, solutions, and applications using plug-and-play components that are aimed for use within private enterprises.

The main steps involved in updating channel config to include peer for an organization using Hyperledger Fabric are;. Peers are a fundamental element of a blockchain network, they host ledgers and smart contracts. The ledger records all the transactions generated by smart contracts.

Smart contracts are used to encapsulate the shared processes in a network and ledgers are used to encapsulate the shared information in the network. Blockchain networks are administered by a collection of organizations rather than a single organization.

Organisations can join channels and thus get access to certain ledgers. An anchor peer is a node in a network that all other peers can discover and communicate with. They are encoded into config update transaction in order to enable communication between peers of different organizations and discover all active participants of the channel.

It helps to prevent single point of failures. It allows peers belonging to different members to discover all existing peers on a channel. Here, each member on a channel has an anchor peer or can have multiple anchor peers and thereby prevents single point of failure. When peer1. And when at a later time peer1. From that point forward, organizations A and B would start exchanging membership information directly without any assistance from peer0.

A detailed explanation on anchor peer can be found in the glossary of hyperledger. We are using Hyperledger Fabric 1.

You have to download the fabric samples form Hyperledger Fabric official. Move into the first-network subdirectory within the fabric-samples directory. Run the following command to clean up the previous environment.

Or, you can use Group Policy and enable the Update Channel policy setting and select the appropriate update channel for your organization. When you use the Office Customization Tool and select Microsoft Apps for enterprise in the Office Suites drop-down list, the Update channel drop-down will choose Current Channel automatically.

You can always choose a different update channel. You will also see this default update channel selection if you use Microsoft Endpoint Configuration Manager current branch and the Office Client Installation Wizard. This change to the default selection in the Microsoft admin center only applies to new tenants that are created on or after June 9, The default selection will not change for tenants that were created before June 9, For these existing tenants, the default selection will remain as Semi-Annual Enterprise Channel.

The exception is existing tenants with Office Education or Microsoft Education plans. Those plans already have Current Channel as the default update channel for Microsoft Apps for enterprise. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Version Note Only the names of the existing update channels are changing.

Important To use all the new attribute values, you need to be using at least version You can look at a sample configtx. Because configurations are contained in blocks the first of these is known as the genesis block with the latest representing the current configuration of the channel , the process for updating a channel configuration changing the structure by adding members, for example, or processes by modifying channel policies is known as a configuration update transaction. In production networks, these configuration update transactions will normally be proposed by a single channel admin after an out of band discussion, just as the initial configuration of the channel will be decided on out of band by the initial members of the channel.

Channels are highly configurable, but not infinitely so. Once certain things about a channel for example, the name of the channel have been specified, they cannot be changed.

To see what the configuration file of an application channel looks like after it has been pulled and scoped, click Click here to see the config below. For ease of readability, it might be helpful to put this config into a viewer that supports JSON folding, like atom or Visual Studio. Note: for simplicity, we are only showing an application channel configuration here. The configuration of the orderer system channel is very similar, but not identical, to the configuration of an application channel.

However, the same basic rules and structure apply, as do the commands to pull and edit a configuration, as you can see in our topic on Updating the capability level of a channel. Click here to see the config. Note that this is the configuration of an application channel, not the orderer system channel.

The structure of the config should now be more obvious. Note that the Channel config grouping is below the Orderer group config values. Governs the configuration parameters unique to application channels for example, adding or removing channel members.

By default, changing these parameters requires the signature of a majority of the application organization admins. Governs configuration parameters that both the peer orgs and the ordering service orgs need to consent to, requires both the agreement of a majority of application organization admins and orderer organization admins. As a result, some users might choose to script the process of pulling, translating, and scoping a config update.

Users also have the option of how to modify the channel configuration itself, either manually or by using a tool like jq. We have two tutorials that deal specifically with editing a channel configuration to achieve a specific end:.

Before you attempt to use the sample commands, make sure to export the following environment variables, which will depend on the way you have structured your deployment. You are free to use whatever names you want. However, be aware that unless you go back and erase these files at the end of each config update, you will have to select different when making an additional update.

The first step in updating a channel configuration is getting the latest config block. This is a three step process. Do not edit config. Whether you choose to edit the config manually or using jq depends on your use case. For an example on how jq can be used, check out Updating channel capabilities , which shows multiple jq commands leveraging a capabilities config file called capabilities. If you are updating something other than the capabilities in your channel, you will have to modify your jq command and JSON file accordingly.

For more information about the content and structure of a channel configuration, check out our sample channel config above. Whether you make your config updates manually or using a tool like jq , you now have to run the process you ran to pull and scope the config in reverse, along with a step to calculate the difference between the old config and the new one, before submitting the config update to the other administrators on the channel to be approved.

Now that we have calculated the difference between the old config and the new one, we can apply the changes to the config. Our config update transaction represents the difference between the original config and the modified one, but the ordering service will translate this into a full channel config. Note: you may be able to script the signature collection, dependent on your application. In general, you may always collect more signatures than are required.