Skip to content

Dissemination: Consenter includes config block in a decision #193

@tock-ibm

Description

@tock-ibm

The consenter will include the new config block in a decision proposal.
In preparing the proposal, the consenter will apply the logic specified in the Issue XXX.
The config block will be the last in a potential list of available blocks (BAs).

It is proposed to alter the structure of the AvailableBlocks array to include fabric common.Block rather than the custom structure currentyl there. A block that corresponds to a BA will include only the header and metadata, whereas a config block will include data as well.

A decision that marks a config block must be marked so that other node would easily identify it without sifting through the available blocks. It is proposed to use the "Last Config Index" of the fabric block that carries the decision in order to point to the last decision that carries a config. If a decision carries a config, the last config index points to the same block. The config block would then reside as the last item of the available blocks array.

Metadata

Metadata

Labels

configConfig and re-config

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions