Lab2: Question on pdf instructions when adding a new peer to an existing organisation

Hi! The pdf instructions for Lab 2 ("Adding a new peer") indicate that a new genesis block must be generated via the following command:
../bin/configtxgen -profile OneOrgOrdererGenesis -outputBlock ./config/genesis.block
But I think there is no need to update the genesis block when adding a new peer to an existing organization (and a running HLF network!).
Moreover, the file configtx.yaml
is never edited as part of the lab, so what is the point in running the configtxgen
command?
Am I wrong? Thanks for clarification
Comments
-
@alejoacosta said:
Hi! The pdf instructions for Lab 2 ("Adding a new peer") indicate that a new genesis block must be generated via the following command:../bin/configtxgen -profile OneOrgOrdererGenesis -outputBlock ./config/genesis.block
But I think there is no need to update the genesis block when adding a new peer to an existing organization (and a running HLF network!).
Moreover, the fileconfigtx.yaml
is never edited as part of the lab, so what is the point in running theconfigtxgen
command?
Am I wrong? Thanks for clarificationHi @alejoacosta ,
Yes, you are correct! I believe the reason for why this is done in the course, is for demonstration purposes, as later on in the course other organizations are added and then the configtx.yaml is updated.
For anyone else interested in how configtxgen works, here is the official doc: https://hyperledger-fabric.readthedocs.io/en/release-2.0/commands/configtxgen.html
0 -
To add to this, genesis.block was created but then peer1.org1 joined allarewelcome channel's genesis block, so this does support the idea genesis.block is exercise only.
On a related question, with the later step of export CORE_PEER_MSPCONFIGPATH, the path is set differently than the path inside docker-compose.yml for peer1.org0 that was added earlier when adding peer1. Is it because we need to be admin (not peer) in order to do the peer joining step?Also for peer1.org in docker-compose.yml, is there any reason peer1.org1's CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE isn't set to "startFiles_basic"? I believe COMPOSE_PROJECT_NAME has no value.
0 -
@jason_jaan said:
To add to this, genesis.block was created but then peer1.org1 joined allarewelcome channel's genesis block, so this does support the idea genesis.block is exercise only.
On a related question, with the later step of export CORE_PEER_MSPCONFIGPATH, the path is set differently than the path inside docker-compose.yml for peer1.org0 that was added earlier when adding peer1. Is it because we need to be admin (not peer) in order to do the peer joining step?Also for peer1.org in docker-compose.yml, is there any reason peer1.org1's CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE isn't set to "startFiles_basic"? I believe COMPOSE_PROJECT_NAME has no value.
@jason_jaan , correct, but this obviously depends on each individual channel policy set-up.
Regarding the COMPOSE_PROJECT_NAME, correct. It could have been set to startFiles_basic by default.
0
Categories
- 9.1K All Categories
- 15 LFX Mentorship
- 68 LFX Mentorship: Linux Kernel
- 380 Linux Foundation Boot Camps
- 233 Cloud Engineer Boot Camp
- 75 Advanced Cloud Engineer Boot Camp
- 30 DevOps Engineer Boot Camp
- 9 Cloud Native Developer Boot Camp
- 977 Training Courses
- 15 LFC110 Class Forum
- 16 LFD102 Class Forum
- 106 LFD103 Class Forum
- 6 LFD121 Class Forum
- 56 LFD201 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 19 LFD254 Class Forum
- 450 LFD259 Class Forum
- 90 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 16 LFS200 Class Forum
- 713 LFS201 Class Forum
- LFS201-JP クラス フォーラム
- 282 LFS211 Class Forum
- 50 LFS216 Class Forum
- 27 LFS241 Class Forum
- 28 LFS242 Class Forum
- 19 LFS243 Class Forum
- 6 LFS244 Class Forum
- 12 LFS250 Class Forum
- LFS250-JP クラス フォーラム
- 113 LFS253 Class Forum
- 814 LFS258 Class Forum
- 8 LFS258-JP クラス フォーラム
- 54 LFS260 Class Forum
- 81 LFS261 Class Forum
- 18 LFS262 Class Forum
- 76 LFS263 Class Forum
- 14 LFS264 Class Forum
- 10 LFS266 Class Forum
- 10 LFS267 Class Forum
- 9 LFS268 Class Forum
- 6 LFS269 Class Forum
- 182 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 191 LFW211 Class Forum
- 114 LFW212 Class Forum
- 880 Hardware
- 207 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 205 Networking
- 98 Printers & Scanners
- 82 Storage
- 730 Linux Distributions
- 85 Debian
- 64 Fedora
- 12 Linux Mint
- 13 Mageia
- 22 openSUSE
- 127 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 349 Ubuntu
- 450 Linux System Administration
- 33 Cloud Computing
- 64 Command Line/Scripting
- Github systems admin projects
- 89 Linux Security
- 76 Network Management
- 105 System Management
- 45 Web Management
- 51 Mobile Computing
- 19 Android
- 19 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 501 Off Topic
- 121 Introductions
- 193 Small Talk
- 19 Study Material
- 756 Programming and Development
- 243 Kernel Development
- 479 Software Development
- 903 Software
- 247 Applications
- 178 Command Line
- 2 Compiling/Installing
- 73 Games
- 314 Installation
- 26 All In Program
- 26 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)