在现实场景中向超级账本结构添加新节点
我刚刚开始学习如何构建结构网络，但如果我们想添加新的节点/组织，我仍然不清楚在现实世界中如何构建。
我想建立一个停车提供商和集成商网络。每个停车提供商都有自己的节点。那么一个新的停车提供商决定加入网络，停车提供商是否建立自己的节点并将节点信息提供给集成商（网络管理员）以便管理员可以将其节点添加到网络中？
I am just started learning how to build the fabric network, but it is still blurry to me how in the real world if we want to add a new node/organization.
I want to build a network of parking providers and an integrator. each parking provider will have its own node. then a new parking provider decides to join the network, are the parking provider set up its own node and give the node information to the integrator (network admin) so that the admin can add its node to the network?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
如果您不熟悉开发网络，则应遵循 Hyperledger Fabric 教程 添加新组织。首先尝试通过运行脚本来使其工作。下一个学习步骤是使用命令行语句执行相同的操作。这将使您更好地理解这一切是如何结合在一起的。如果您在该阶段感到满意，那么下一步就是能够添加相同的附加组织，但现在引入证书颁发机构。这将增加您对 docker 脚本和配置文件的了解。内置 shell 脚本不使用 CA 将第三个组织添加到“测试网络”。
如果这一切看起来令人难以承受，那么你就有了一个良好的开端，因为事实确实如此。在尝试添加新组织之前，请了解网络是如何构建的。完成后，您将更好地了解添加更多组织所需的步骤。
If you are new to developing networks, you should follow the Hyperledger Fabric tutroial for Adding a new Org. Try to get this to work first just by running the scripts. The next learning step is to do the same action using command line statements instead. This will give you a better understanding of how it all hangs together. If you are comfortable at that stage, the next thing is to be able to add the same additional organisation but now introduce a Certificate Authority. This will increase your knowledge of the docker scripts and configuration files. The built in shell scripts do not use a CA for the third Org to be added to the "test-network".
If all of this seems overwhelming, then you are off to a good start, because it is. Understand how the network was built before you try to add a new Org. You will better understand the steps required to add more organisations once you do.
在现实世界中，您将处理特定的用例并尝试找出区块链是否是您所需要的。通常，查看它的一个好方法是识别感兴趣的业务对象（-> 这些进入世界状态），然后考虑事务如何塑造它们（-> 这些进入通道），并从那里考虑您的逻辑需要（->即，智能合约中部署为链码的某种“状态机”）以及如何由对等方调用此逻辑（->这是您的客户端应用程序发挥作用的地方）。
如果一切顺利，您将能够判断区块链架构是否是您所需要和想要的。
现在介绍您的详细信息...
任何节点都必须属于一个组织，所以我的第一个猜测是每个停车提供商都有一个组织，因此每个停车提供商可能有一个或多个节点（回想一下节点=对等点、客户端、订购服务） 。
接下来我有点不确定集成商的作用是什么（除了网络配置之外？）。例如，您可能希望给予停车提供商加入的自主权，或者您可能希望对组织成员资格施加中央权力？此外，您可能希望集成商做一些停车提供商不太热衷的事情（例如，订购服务？）。
我猜你会弄清楚这些细节
In the real world you'll be working through specific use cases and trying to figure out if a blockchain is what you need. Typically a good way to look at it is to identify the business objects of interest (-> these go into world state), then consider how transactions shape them (-> these go into the channel) and from there consider what logic you need (-> i.e., some sort of "state machine" in your smart contract that is deployed as chaincode) and how this logic is to be invoked by peers (-> this is where your client app comes into play).
If that all works you'll be in a position to judge if a blockchain architecture is what you need and want.
Now to your details...
Any node must belong to an organisation so my first guess is that you have one organisation per parking provider and that each parking provider may therefore have one or more nodes (recall node=peer,client,ordering service).
Next I'm a bit unsure what role of the integrator is (beyond network configuration?). For example, you might want to give parking providers autonomy to join or you might want to impose a central authority for organisational membership? Also you might want to have the integrator do things that the parking providers are less enthusastic about (e.g., ordering service?).
I'll guess you'll figure those details out