Hyperledger Fabric 网络通过外部组织进行扩展
假设我们有一个与已经加入的3个组织的网络，并在渠道内进行交易。所有3个都在同一服务器下。
一个新的组织需要加入渠道和网络，但希望使用自己的基础架构。当前工作网络的开发人员或管理员不应访问新的网络。管理员分享给新组织“开发人员”的管理员应该最重要的文件，以便他们加入他们的公司？
我已经阅读了教程和有关该过程如何进行的文档，但是我看到需要进行许多详细的过程，例如获取config_block并由管理员使用新的ORGS信息进行编辑。
可以说，有哪些重要零件和“最佳”实践要进行这样的操作？
谢谢
Lets say we have a network with 3 organizations that are already joined and make transactions within a channel. All 3 are under the same server.
A new organization needs to join the channel and the network, but wants to use its own infrastructure. And the devs or administrators of the current working network should not have access to the new one. What are the most important files that should by the administrators shared to the new organizations "developers" so they can join their company?
I have read tutorials and the documentation on how the process goes, but I see that a lot of detailed processes need to take place, like getting the config_block and edit it by the administrators with the new orgs info.
What are some vital parts and "best" practices, lets say, to do such an operation?
Thank you
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
由于我没有足够高的声誉来发表评论，因此我将为您的问题提供建议。
如果您通过Docker容器实现HyperLeDger，则可以自己解决此问题。我的建议是首先了解将新组织（同行）添加到现有渠道所需的内容。这在HyperLeDger文档中有很好的记录。完成此操作后，如果我正确理解您，您希望能够重复相同的操作，就像Docker容器（PEER）在完全不同的服务器上存在一样。现在，您需要能够在将同伴存在在另一个域上时完成相同的操作。为此，您将需要拥有可用的文件和目录结构，以构建新的容器。现在，您的主要问题是打开端口，处理IP地址，域以及所有其他可爱的网络内容。
添加org3教程提供了许多有关如何添加新同行的好信息。它不会创建证书授权的同行，但是您可以通过对脚本进行一些小更改来克服这一点。无论如何，您都必须更改组织名称，以使其适合您的情况。
如果您首先学会在本地进行此操作，那么您将拥有足够的知识来提取位以使其从远程服务器起作用。
As I don't have a high enough reputation to comment, I am going to give advice as an answer to your question.
If you are implementing Hyperledger through docker containers, then you can nearly solve this problem yourself. My advice is to first learn what it takes to add a new organisation (peer) to an existing channel. This is well documented in the Hyperledger documentation. Once you can do this, then if I understand you correctly, you want to be able to repeat the same operation as if the docker container (peer) exists on a completely different server. Now you need to be able to complete the same operation while having the peer exist on a different domain. To do this, you will need to have the files and directory structures available that allowed the new container to be built. Your main problems now are opening ports, dealing with IP addresses, domains and all that other lovely networking stuff.
The Add Org3 tutorial provides a lot of good information on how to add a new peer. It doesn't create a Certificate Authority peer, but you can overcome this by doing a few small changes to the scripts. You will have to change the organisation names anyway to make it work for your situation.
If you learn to do it locally first, by then you will have enough knowledge to extract the bits to make it work from a remote server.