1 - OpenIDL Node Definition

Each of the openIDL nodes should be uniquely identified by its ID. That unique organization ID is used to name different infrastructure resources, HLF MSPs (Hyperledger Fabric Membership Service Provider), opendIDL HLF channels, etc.

It is therefore important to guarantee that each openIDL network member gets a unique ID. Those IDs are recorded and issued by openIDL.

Required parameters for the basic node definition:

• Organization ID/Name: Provided by openIDL and used in various configurations during node deployment and post-deployment operations.
• Environment: Used in various steps during node deployment. The operator of the organization is free to define it. Usually, it defines the deployment environment of the node (dev/test/prod).
• Domain: The domain of the node has to be defined and configured properly (DNS entries that make the domain discoverable on the internet). The domain is used to configure the DNS names of the openIDL node endpoints. Those endpoints are essential as they are used to connect the openIDL nodes on the openIDL network. Inbound/outbound traffic to those endpoints has to be allowed (all openIDL nodes use TLS-encrypted communication channels).
• Node type: The openIDL network consists of three different node types: ordering, carrier, and analytics. There are some differences in the node deployment and configuration based on its type. Therefore the operator of the node should determine the node type before starting the deployment process. For example, a carrier organization deploys a carrier node and joins an existing network where an openIDL ordering and analytics nodes are already operational.