Hyperledger fabric network on multiple machines/nodes












1















We are facing issues to deploy our network on multiple machines. We want to deploy our network on local machines and wants the communications between different peers and organizations. So it is possible to use SOLO for communications. If yes then how. and If no then why?



We want to make small networks on 2 to 3 machines and then wants to combine all the small networks to build a giant network. how this will be possible. Looking for help.










share|improve this question























  • Hi, while you are mentioning about combine all the small networks, did you mean those networks have different ledgers (they are in different Fabric channels) ?

    – supl
    Nov 26 '18 at 7:57











  • yes they will have an different ledger.

    – Hasnat Ahmed
    Nov 26 '18 at 8:27











  • I am not sure if I understand your needs. Assuming you have two different networks (channels, ledgers) network0 and network1; And two peers peer0 (joined network0) and peer1 (joined network1), do you try to access network1 from peer0 ?

    – supl
    Nov 26 '18 at 8:57











  • yes you are right. thats what I have to do.

    – Hasnat Ahmed
    Nov 26 '18 at 9:58











  • If so, I believe what you need is to ask peer0 to join network1 (and peer0 can share ledger1 with peer1). Then both peer0 and peer1 will receive the broadcast from the orderer when a new block of ledger1 is being added.

    – supl
    Nov 26 '18 at 10:06
















1















We are facing issues to deploy our network on multiple machines. We want to deploy our network on local machines and wants the communications between different peers and organizations. So it is possible to use SOLO for communications. If yes then how. and If no then why?



We want to make small networks on 2 to 3 machines and then wants to combine all the small networks to build a giant network. how this will be possible. Looking for help.










share|improve this question























  • Hi, while you are mentioning about combine all the small networks, did you mean those networks have different ledgers (they are in different Fabric channels) ?

    – supl
    Nov 26 '18 at 7:57











  • yes they will have an different ledger.

    – Hasnat Ahmed
    Nov 26 '18 at 8:27











  • I am not sure if I understand your needs. Assuming you have two different networks (channels, ledgers) network0 and network1; And two peers peer0 (joined network0) and peer1 (joined network1), do you try to access network1 from peer0 ?

    – supl
    Nov 26 '18 at 8:57











  • yes you are right. thats what I have to do.

    – Hasnat Ahmed
    Nov 26 '18 at 9:58











  • If so, I believe what you need is to ask peer0 to join network1 (and peer0 can share ledger1 with peer1). Then both peer0 and peer1 will receive the broadcast from the orderer when a new block of ledger1 is being added.

    – supl
    Nov 26 '18 at 10:06














1












1








1








We are facing issues to deploy our network on multiple machines. We want to deploy our network on local machines and wants the communications between different peers and organizations. So it is possible to use SOLO for communications. If yes then how. and If no then why?



We want to make small networks on 2 to 3 machines and then wants to combine all the small networks to build a giant network. how this will be possible. Looking for help.










share|improve this question














We are facing issues to deploy our network on multiple machines. We want to deploy our network on local machines and wants the communications between different peers and organizations. So it is possible to use SOLO for communications. If yes then how. and If no then why?



We want to make small networks on 2 to 3 machines and then wants to combine all the small networks to build a giant network. how this will be possible. Looking for help.







hyperledger-fabric blockchain ethereum ibm-blockchain hyperledger-fabric-ca






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 26 '18 at 5:18









Hasnat AhmedHasnat Ahmed

63




63













  • Hi, while you are mentioning about combine all the small networks, did you mean those networks have different ledgers (they are in different Fabric channels) ?

    – supl
    Nov 26 '18 at 7:57











  • yes they will have an different ledger.

    – Hasnat Ahmed
    Nov 26 '18 at 8:27











  • I am not sure if I understand your needs. Assuming you have two different networks (channels, ledgers) network0 and network1; And two peers peer0 (joined network0) and peer1 (joined network1), do you try to access network1 from peer0 ?

    – supl
    Nov 26 '18 at 8:57











  • yes you are right. thats what I have to do.

    – Hasnat Ahmed
    Nov 26 '18 at 9:58











  • If so, I believe what you need is to ask peer0 to join network1 (and peer0 can share ledger1 with peer1). Then both peer0 and peer1 will receive the broadcast from the orderer when a new block of ledger1 is being added.

    – supl
    Nov 26 '18 at 10:06



















  • Hi, while you are mentioning about combine all the small networks, did you mean those networks have different ledgers (they are in different Fabric channels) ?

    – supl
    Nov 26 '18 at 7:57











  • yes they will have an different ledger.

    – Hasnat Ahmed
    Nov 26 '18 at 8:27











  • I am not sure if I understand your needs. Assuming you have two different networks (channels, ledgers) network0 and network1; And two peers peer0 (joined network0) and peer1 (joined network1), do you try to access network1 from peer0 ?

    – supl
    Nov 26 '18 at 8:57











  • yes you are right. thats what I have to do.

    – Hasnat Ahmed
    Nov 26 '18 at 9:58











  • If so, I believe what you need is to ask peer0 to join network1 (and peer0 can share ledger1 with peer1). Then both peer0 and peer1 will receive the broadcast from the orderer when a new block of ledger1 is being added.

    – supl
    Nov 26 '18 at 10:06

















Hi, while you are mentioning about combine all the small networks, did you mean those networks have different ledgers (they are in different Fabric channels) ?

– supl
Nov 26 '18 at 7:57





Hi, while you are mentioning about combine all the small networks, did you mean those networks have different ledgers (they are in different Fabric channels) ?

– supl
Nov 26 '18 at 7:57













yes they will have an different ledger.

– Hasnat Ahmed
Nov 26 '18 at 8:27





yes they will have an different ledger.

– Hasnat Ahmed
Nov 26 '18 at 8:27













I am not sure if I understand your needs. Assuming you have two different networks (channels, ledgers) network0 and network1; And two peers peer0 (joined network0) and peer1 (joined network1), do you try to access network1 from peer0 ?

– supl
Nov 26 '18 at 8:57





I am not sure if I understand your needs. Assuming you have two different networks (channels, ledgers) network0 and network1; And two peers peer0 (joined network0) and peer1 (joined network1), do you try to access network1 from peer0 ?

– supl
Nov 26 '18 at 8:57













yes you are right. thats what I have to do.

– Hasnat Ahmed
Nov 26 '18 at 9:58





yes you are right. thats what I have to do.

– Hasnat Ahmed
Nov 26 '18 at 9:58













If so, I believe what you need is to ask peer0 to join network1 (and peer0 can share ledger1 with peer1). Then both peer0 and peer1 will receive the broadcast from the orderer when a new block of ledger1 is being added.

– supl
Nov 26 '18 at 10:06





If so, I believe what you need is to ask peer0 to join network1 (and peer0 can share ledger1 with peer1). Then both peer0 and peer1 will receive the broadcast from the orderer when a new block of ledger1 is being added.

– supl
Nov 26 '18 at 10:06












1 Answer
1






active

oldest

votes


















0














As far as I've understood your question, is how to connect multiple different networks to one "larger" network.



So, I think this statement is a misconception, correct me if I'm wrong but every hyperledger fabric network is created initially from one organization, which supposedly is the network initiator (a.k.a. network admin). Moreover, upon the creation of the network, the administrative figure that defines the network is the ordering service which is bonded to the initial organization. However, the initial state of the network changes as new members enter the network. The thing is that the new members who are entering the network do not have nor belong to another network. They enter the network created by the initial organization.



You might find the following documentation helpful:
https://hyperledger-fabric.readthedocs.io/en/release-1.3/network/network.html
I hope this helped you with your confusion.



Finally, you can get started and build a network if you follow this:
https://hyperledger-fabric.readthedocs.io/en/release-1.3/build_network.html






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53475110%2fhyperledger-fabric-network-on-multiple-machines-nodes%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    As far as I've understood your question, is how to connect multiple different networks to one "larger" network.



    So, I think this statement is a misconception, correct me if I'm wrong but every hyperledger fabric network is created initially from one organization, which supposedly is the network initiator (a.k.a. network admin). Moreover, upon the creation of the network, the administrative figure that defines the network is the ordering service which is bonded to the initial organization. However, the initial state of the network changes as new members enter the network. The thing is that the new members who are entering the network do not have nor belong to another network. They enter the network created by the initial organization.



    You might find the following documentation helpful:
    https://hyperledger-fabric.readthedocs.io/en/release-1.3/network/network.html
    I hope this helped you with your confusion.



    Finally, you can get started and build a network if you follow this:
    https://hyperledger-fabric.readthedocs.io/en/release-1.3/build_network.html






    share|improve this answer




























      0














      As far as I've understood your question, is how to connect multiple different networks to one "larger" network.



      So, I think this statement is a misconception, correct me if I'm wrong but every hyperledger fabric network is created initially from one organization, which supposedly is the network initiator (a.k.a. network admin). Moreover, upon the creation of the network, the administrative figure that defines the network is the ordering service which is bonded to the initial organization. However, the initial state of the network changes as new members enter the network. The thing is that the new members who are entering the network do not have nor belong to another network. They enter the network created by the initial organization.



      You might find the following documentation helpful:
      https://hyperledger-fabric.readthedocs.io/en/release-1.3/network/network.html
      I hope this helped you with your confusion.



      Finally, you can get started and build a network if you follow this:
      https://hyperledger-fabric.readthedocs.io/en/release-1.3/build_network.html






      share|improve this answer


























        0












        0








        0







        As far as I've understood your question, is how to connect multiple different networks to one "larger" network.



        So, I think this statement is a misconception, correct me if I'm wrong but every hyperledger fabric network is created initially from one organization, which supposedly is the network initiator (a.k.a. network admin). Moreover, upon the creation of the network, the administrative figure that defines the network is the ordering service which is bonded to the initial organization. However, the initial state of the network changes as new members enter the network. The thing is that the new members who are entering the network do not have nor belong to another network. They enter the network created by the initial organization.



        You might find the following documentation helpful:
        https://hyperledger-fabric.readthedocs.io/en/release-1.3/network/network.html
        I hope this helped you with your confusion.



        Finally, you can get started and build a network if you follow this:
        https://hyperledger-fabric.readthedocs.io/en/release-1.3/build_network.html






        share|improve this answer













        As far as I've understood your question, is how to connect multiple different networks to one "larger" network.



        So, I think this statement is a misconception, correct me if I'm wrong but every hyperledger fabric network is created initially from one organization, which supposedly is the network initiator (a.k.a. network admin). Moreover, upon the creation of the network, the administrative figure that defines the network is the ordering service which is bonded to the initial organization. However, the initial state of the network changes as new members enter the network. The thing is that the new members who are entering the network do not have nor belong to another network. They enter the network created by the initial organization.



        You might find the following documentation helpful:
        https://hyperledger-fabric.readthedocs.io/en/release-1.3/network/network.html
        I hope this helped you with your confusion.



        Finally, you can get started and build a network if you follow this:
        https://hyperledger-fabric.readthedocs.io/en/release-1.3/build_network.html







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 27 '18 at 11:50









        Abducted CowAbducted Cow

        112




        112
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53475110%2fhyperledger-fabric-network-on-multiple-machines-nodes%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Create new schema in PostgreSQL using DBeaver

            Deepest pit of an array with Javascript: test on Codility

            Costa Masnaga