├── .gitignore ├── LICENSE ├── README.md ├── dev_example ├── README.md ├── config │ ├── configtx.yaml │ ├── crypto-config.yaml │ └── fabric-ca-client-config.yaml └── helm_values │ ├── cdb-peer1.yaml │ ├── ord1.yaml │ └── peer1.yaml ├── helm-rbac.yaml └── prod_example ├── LICENSE ├── README.md ├── config ├── Lets_Encrypt_Authority_X3.pem ├── configtx.yaml └── fabric-ca-client-config.yaml ├── extra ├── certManagerCI_production.yaml └── certManagerCI_staging.yaml └── helm_values ├── ca.yaml ├── cdb-peer1.yaml ├── cdb-peer2.yaml ├── kafka-hlf.yaml ├── ord1.yaml ├── ord2.yaml ├── peer1.yaml └── peer2.yaml /.gitignore: -------------------------------------------------------------------------------- 1 | .idea 2 | .DS_Store 3 | 4 | *MSP 5 | mychannel.tx 6 | genesis.block 7 | crypto-config 8 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | Table of Contents 2 | ================= 3 | 4 | * [HGF K8S Workshop](#hgf-k8s-workshop) 5 | * [Workshop flow](#workshop-flow) 6 | * [Cluster creation](#cluster-creation) 7 | * [Development example](#development-example) 8 | * [Production example](#production-example) 9 | * [Cleanup](#cleanup) 10 | * [Extra resources](#extra-resources) 11 | * [Repositories](#repositories) 12 | * [Courses](#courses) 13 | * [FAQ](#faq) 14 | 15 | 16 | # HGF K8S Workshop 17 | 18 | Hyperledger Global Forum workshop on deploying Hyperledger Fabric on Kubernetes in development and production. 19 | 20 | You may wish to explore https://github.com/aidtechnology/nephos, which helps automate the deployment of similar examples as presented here. 21 | 22 | ## Workshop flow 23 | 24 | ### Cluster creation 25 | 26 | In the workshop we demonstrate how to create a managed K8S cluster on Azure: 27 | 28 | export GROUP=hgf-workshop 29 | export LOCATION=westeurope 30 | 31 | az group create -n $GROUP -l $LOCATION 32 | az aks create -g $GROUP -n ${GROUP}-aks -s Standard_DS2_v2 --kubernetes-version 1.11.5 --node-count 5 33 | az aks get-credentials -g $GROUP -n ${GROUP}-aks 34 | 35 | Then you can install Helm, using 36 | 37 | kubectl create -f ./helm-rbac.yaml 38 | 39 | helm init --service-account tiller 40 | 41 | Finally, add the `incubator` repository, so you are able to install Kafka, etc. 42 | 43 | helm repo add incubator https://kubernetes-charts-incubator.storage.googleapis.com/ 44 | 45 | helm repo update 46 | 47 | ### Development example 48 | 49 | We will start with the `dev_example`, using Cryptogen to set up the identities and cryptographic material. 50 | 51 | This is sufficient for Development purposes and will use a very simple setup of 1 peer and 1 (solo) orderer. 52 | 53 | ### Production example 54 | 55 | In the second part of the workshop, `prod_example`, we will be using the Fabric CA to provide the identities and cryptographic material. 56 | 57 | This uses as production-ready setup implementing Certificate Authorities persisting identities to PostgreSQL, multiple peers and multiple (Kafka-consensus) orderers. 58 | 59 | ### Cleanup 60 | 61 | If you use Azure AKS, you can just delete the resource group and associated AKS cluster in one fell swoop. 62 | 63 | az group delete -n $GROUP 64 | 65 | ## Extra resources 66 | 67 | ### Repositories 68 | 69 | Our charts can be found at the official Helm Charts repository: 70 | 71 | https://github.com/helm/charts 72 | 73 | And also on our own open-source repository: 74 | 75 | https://github.com/aidtechnology/at-charts 76 | 77 | We also have a repository hosting the Fabric CA client Homebrew installer (for OS X): 78 | 79 | https://github.com/aidtechnology/homebrew-fabric-ca 80 | 81 | ### Courses 82 | 83 | *Blockchain for Business - An Introduction to Hyperledger Technologies*, where we have contributed the Hyperledger Composer chapter: 84 | 85 | https://www.edx.org/course/blockchain-business-introduction-linuxfoundationx-lfs171x-0 86 | 87 | *Blockchain for Blockchain Applications* on Packt and Udemy: 88 | 89 | https://www.packtpub.com/application-development/hyperledger-blockchain-applications-video 90 | 91 | https://www.udemy.com/hyperledger-for-blockchain-applications/ 92 | 93 | ### FAQ 94 | 95 | > In progress 96 | -------------------------------------------------------------------------------- /dev_example/README.md: -------------------------------------------------------------------------------- 1 | Table of Contents 2 | ================= 3 | 4 | * [Development deployment](#development-deployment) 5 | * [Before starting](#before-starting) 6 | * [Pre-requisites](#pre-requisites) 7 | * [Creating](#creating) 8 | * [Crypto material](#crypto-material) 9 | * [Fabric Orderer](#fabric-orderer) 10 | * [Fabric Peer](#fabric-peer) 11 | * [Deleting](#deleting) 12 | 13 | # Development deployment 14 | 15 | ## Before starting 16 | 17 | ### Pre-requisites 18 | 19 | Before running this tutorial you will need: 20 | 21 | 1) A Kubernetes (K8S) cluster with at least 1 node (you can get free credits to deploy a managed K8S cluster on AWS, GCP, Azure, etc) 22 | 2) Helm (and Tiller) installed on K8S 23 | 24 | ## Creating 25 | 26 | ### Crypto Material 27 | 28 | #### Cryptogen install 29 | 30 | You may need to download the latest cryptogen tools 31 | 32 | If you are using a Mac, you can run the following (version 1.1.0 and 1.2.0 are also supported if needed): 33 | 34 | brew tap aidtechnology/homebrew-fabric 35 | brew install fabric-tools@1.3.0 36 | 37 | #### Generation 38 | 39 | Generate the necessary crypto-materials with 40 | 41 | cd ./dev_example/config 42 | cryptogen generate --config ./crypto-config.yaml 43 | 44 | You can see what was generated using the command `tree` (install with `brew install tree` if it's missing): 45 | 46 | tree crypto-config 47 | 48 | #### Admin materials 49 | 50 | If you don't have the following namespaces, you may need to create. 51 | 52 | kubectl create ns orderers 53 | kubectl create ns peers 54 | 55 | We must save the relevant Orderer admin crypto-config files as secrets. 56 | 57 | MSP_DIR=./crypto-config/ordererOrganizations/orderers.svc.cluster.local/users/Admin@orderers.svc.cluster.local/msp 58 | 59 | ORG_CERT=$(ls ${MSP_DIR}/admincerts/*.pem) 60 | kubectl create secret generic -n orderers hlf--ord-admincert --from-file=cert.pem=$ORG_CERT 61 | 62 | CA_CERT=$(ls ${MSP_DIR}/cacerts/*.pem) 63 | kubectl create secret generic -n orderers hlf--ord-cacert --from-file=cacert.pem=$CA_CERT 64 | 65 | And the Peer admin crypto-config files: 66 | 67 | MSP_DIR=./crypto-config/peerOrganizations/peers.svc.cluster.local/users/Admin@peers.svc.cluster.local/msp 68 | 69 | ORG_CERT=$(ls ${MSP_DIR}/admincerts/*.pem) 70 | kubectl create secret generic -n peers hlf--peer-admincert --from-file=cert.pem=$ORG_CERT 71 | 72 | ORG_KEY=$(ls ${MSP_DIR}/keystore/*_sk) 73 | kubectl create secret generic -n peers hlf--peer-adminkey --from-file=key.pem=$ORG_KEY 74 | 75 | CA_CERT=$(ls ${MSP_DIR}/cacerts/*.pem) 76 | kubectl create secret generic -n peers hlf--peer-cacert --from-file=cacert.pem=$CA_CERT 77 | 78 | #### Genesis & Channel 79 | 80 | configtxgen -profile OrdererGenesis -outputBlock ./genesis.block 81 | 82 | configtxgen -profile MyChannel -channelID mychannel -outputCreateChannelTx ./mychannel.tx 83 | 84 | kubectl create secret generic -n orderers hlf--genesis --from-file=genesis.block 85 | 86 | kubectl create secret generic -n peers hlf--channel --from-file=mychannel.tx 87 | 88 | ### Fabric Orderer 89 | 90 | #### Crypto material 91 | 92 | Save node identity cryptographic material as secrets: 93 | 94 | MSP_DIR=./crypto-config/ordererOrganizations/orderers.svc.cluster.local/orderers/ord1-hlf-ord.orderers.svc.cluster.local/msp 95 | 96 | NODE_CERT=$(ls ${MSP_DIR}/signcerts/*.pem) 97 | kubectl create secret generic -n orderers hlf--ord1-idcert --from-file=cert.pem=$NODE_CERT 98 | 99 | NODE_KEY=$(ls ${MSP_DIR}/keystore/*_sk) 100 | kubectl create secret generic -n orderers hlf--ord1-idkey --from-file=key.pem=$NODE_KEY 101 | 102 | #### Helm chart 103 | 104 | And install the HLF Orderer Helm chart: 105 | 106 | helm install stable/hlf-ord -n ord1 --namespace orderers -f ../helm_values/ord1.yaml 107 | 108 | And check that it is running: 109 | 110 | ORD_POD=$(kubectl get pods -n orderers -l "app=hlf-ord,release=ord1" -o jsonpath="{.items[0].metadata.name}") 111 | 112 | kubectl logs -n orderers $ORD_POD | grep 'Starting orderer' 113 | 114 | ### Fabric Peer 115 | 116 | #### CouchDB 117 | 118 | We start by installing the CouchDB database: 119 | 120 | helm install stable/hlf-couchdb -n cdb-peer1 --namespace peers -f ../helm_values/cdb-peer1.yaml 121 | 122 | And check that it is running: 123 | 124 | CDB_POD=$(kubectl get pods -n peers -l "app=hlf-couchdb,release=cdb-peer1" -o jsonpath="{.items[*].metadata.name}") 125 | 126 | kubectl logs -n peers $CDB_POD | grep 'Apache CouchDB has started on' 127 | 128 | #### Crypto material 129 | 130 | Save node identity cryptographic material as secrets: 131 | 132 | MSP_DIR=./crypto-config/peerOrganizations/peers.svc.cluster.local/peers/peer1-hlf-peer.peers.svc.cluster.local/msp 133 | 134 | NODE_CERT=$(ls ${MSP_DIR}/signcerts/*.pem) 135 | kubectl create secret generic -n peers hlf--peer1-idcert --from-file=cert.pem=$NODE_CERT 136 | 137 | NODE_KEY=$(ls ${MSP_DIR}/keystore/*_sk) 138 | kubectl create secret generic -n peers hlf--peer1-idkey --from-file=key.pem=$NODE_KEY 139 | 140 | #### Helm chart 141 | 142 | And install the HLF-Peer Helm Chart: 143 | 144 | helm install stable/hlf-peer -n peer1 --namespace peers -f ../helm_values/peer1.yaml 145 | 146 | And check that it is running: 147 | 148 | PEER_POD=$(kubectl get pods -n peers -l "app=hlf-peer,release=peer1" -o jsonpath="{.items[0].metadata.name}") 149 | 150 | kubectl logs -n peers $PEER_POD | grep 'Starting peer' 151 | 152 | #### Channel 153 | 154 | Create the channel 155 | 156 | kubectl exec -n peers $PEER_POD -- peer channel create -o ord1-hlf-ord.orderers.svc.cluster.local:7050 -c mychannel -f /hl_config/channel/mychannel.tx 157 | 158 | Fetch the channel and join it from the orderer: 159 | 160 | kubectl exec -n peers $PEER_POD -- peer channel fetch config /var/hyperledger/mychannel.block -c mychannel -o ord1-hlf-ord.orderers.svc.cluster.local:7050 161 | 162 | kubectl exec -n peers $PEER_POD -- bash -c 'CORE_PEER_MSPCONFIGPATH=$ADMIN_MSP_PATH peer channel join -b /var/hyperledger/mychannel.block' 163 | 164 | You should see that now the peer is linked to this channel. 165 | 166 | kubectl exec -n peers $PEER_POD -- peer channel list 167 | 168 | ## Deleting 169 | 170 | We start by deleting the actual Helm deployments: 171 | 172 | helm delete --purge ord1 peer1 cdb-peer1 173 | 174 | Then we delete the crypto-material we saved for the orderers: 175 | 176 | kubectl delete secret -n orderers hlf--genesis hlf--ord-admincert hlf--ord-cacert hlf--ord1-idcert hlf--ord1-idkey 177 | 178 | And that of the peers: 179 | 180 | kubectl delete secret -n peers hlf--channel hlf--peer-admincert hlf--peer-adminkey hlf--peer-cacert hlf--peer1-idcert hlf--peer1-idkey 181 | 182 | Delete crypto material files: 183 | 184 | rm -rf ./config/*MSP ./config/genesis.block ./config/mychannel.tx 185 | 186 | Clean up namespaces we used for the development examples 187 | 188 | kubectl delete ns orderers peers 189 | -------------------------------------------------------------------------------- /dev_example/config/configtx.yaml: -------------------------------------------------------------------------------- 1 | # Copyright IBM Corp. All Rights Reserved. 2 | # 3 | # SPDX-License-Identifier: Apache-2.0 4 | # 5 | 6 | ################################################################################ 7 | # 8 | # Section: Organizations 9 | # 10 | # - This section defines the different organizational identities which will 11 | # be referenced later in the configuration. 12 | # 13 | ################################################################################ 14 | Organizations: 15 | 16 | # Organisation controlling Orderers 17 | - &OrdererOrg 18 | # DefaultOrg defines the organization which is used in the sampleconfig 19 | # of the fabric.git development environment 20 | Name: OrdererOrg 21 | 22 | # ID to load the MSP definition as 23 | ID: OrdererMSP 24 | 25 | # MSPDir is the filesystem path which contains the MSP configuration 26 | MSPDir: ./crypto-config/ordererOrganizations/orderers.svc.cluster.local/msp 27 | 28 | # turn off security for the channel 29 | AdminPrincipal: Role.MEMBER 30 | 31 | # Organisation controlling Peers 32 | - &AidTech 33 | Name: AidTech 34 | 35 | # ID to load the MSP definition as 36 | ID: PeerMSP 37 | 38 | MSPDir: ./crypto-config/peerOrganizations/peers.svc.cluster.local/msp 39 | 40 | # turn off security for the peer 41 | AdminPrincipal: Role.MEMBER 42 | 43 | AnchorPeers: 44 | # AnchorPeers defines the location of peers that can be used 45 | # for cross org gossip communication. Note, this value is only 46 | # encoded in the genesis block in the Application section context 47 | - Host: peer1-hlf-peer.peers.svc.cluster.local 48 | Port: 7051 49 | 50 | ################################################################################ 51 | # 52 | # SECTION: Orderer 53 | # 54 | # - This section defines the values to encode into a config transaction or 55 | # genesis block for orderer related parameters 56 | # 57 | ################################################################################ 58 | Orderer: &OrdererDefaults 59 | 60 | # Orderer Type: The orderer implementation to start 61 | # Available types are "solo" and "kafka" 62 | OrdererType: solo 63 | 64 | Addresses: 65 | - ord1-hlf-ord.orderers.svc.cluster.local:7050 66 | 67 | # Batch Timeout: The amount of time to wait before creating a batch 68 | BatchTimeout: 2s 69 | 70 | # Batch Size: Controls the number of messages batched into a block 71 | BatchSize: 72 | 73 | # Max Message Count: The maximum number of messages to permit in a batch 74 | MaxMessageCount: 10 75 | 76 | # Absolute Max Bytes: The absolute maximum number of bytes allowed for 77 | # the serialized messages in a batch. 78 | AbsoluteMaxBytes: 98 MB 79 | 80 | # Preferred Max Bytes: The preferred maximum number of bytes allowed for 81 | # the serialized messages in a batch. A message larger than the preferred 82 | # max bytes will result in a batch larger than preferred max bytes. 83 | PreferredMaxBytes: 512 KB 84 | 85 | Kafka: 86 | # Brokers: A list of Kafka brokers to which the orderer connects 87 | # If using K8S, we specify the service exposing the brokers 88 | # NOTE: Use Address/IP:port notation 89 | Brokers: 90 | - kafka-hlf.orderers.svc.cluster.local:9092 91 | 92 | # Organizations is the list of orgs which are defined as participants on 93 | # the orderer side of the network 94 | Organizations: 95 | 96 | ################################################################################ 97 | # 98 | # SECTION: Application 99 | # 100 | # - This section defines the values to encode into a config transaction or 101 | # genesis block for application related parameters 102 | # 103 | ################################################################################ 104 | Application: &ApplicationDefaults 105 | 106 | # Organizations is the list of orgs which are defined as participants on 107 | # the application side of the network 108 | Organizations: 109 | 110 | ################################################################################ 111 | # 112 | # Profile 113 | # 114 | # - Different configuration profiles may be encoded here to be specified 115 | # as parameters to the configtxgen tool 116 | # 117 | ################################################################################ 118 | Profiles: 119 | 120 | OrdererGenesis: 121 | Orderer: 122 | <<: *OrdererDefaults 123 | Organizations: 124 | - *OrdererOrg 125 | Consortiums: 126 | MyConsortium: 127 | Organizations: 128 | - *AidTech 129 | MyChannel: 130 | Consortium: MyConsortium 131 | Application: 132 | <<: *ApplicationDefaults 133 | Organizations: 134 | - *AidTech 135 | -------------------------------------------------------------------------------- /dev_example/config/crypto-config.yaml: -------------------------------------------------------------------------------- 1 | # Copyright IBM Corp. All Rights Reserved. 2 | # 3 | # SPDX-License-Identifier: Apache-2.0 4 | # 5 | 6 | # --------------------------------------------------------------------------- 7 | # "OrdererOrgs" - Definition of organizations managing orderer nodes 8 | # --------------------------------------------------------------------------- 9 | OrdererOrgs: 10 | # --------------------------------------------------------------------------- 11 | # Orderer 12 | # --------------------------------------------------------------------------- 13 | - Name: Orderer 14 | Domain: orderers.svc.cluster.local 15 | # --------------------------------------------------------------------------- 16 | # "Specs" - See PeerOrgs below for complete description 17 | # --------------------------------------------------------------------------- 18 | Specs: 19 | - Hostname: ord1-hlf-ord 20 | # --------------------------------------------------------------------------- 21 | # "PeerOrgs" - Definition of organizcd ----------------------------------------- 22 | PeerOrgs: 23 | # --------------------------------------------------------------------------- 24 | # Org1 25 | # --------------------------------------------------------------------------- 26 | - Name: Org1 27 | Domain: peers.svc.cluster.local 28 | # --------------------------------------------------------------------------- 29 | # "Specs" 30 | # --------------------------------------------------------------------------- 31 | # Uncomment this section to enable the explicit definition of hosts in your 32 | # configuration. Most users will want to use Template, below 33 | # 34 | # Specs is an array of Spec entries. Each Spec entry consists of two fields: 35 | # - Hostname: (Required) The desired hostname, sans the domain. 36 | # - CommonName: (Optional) Specifies the template or explicit override for 37 | # the CN. By default, this is the template: 38 | # 39 | # "{{.Hostname}}.{{.Domain}}" 40 | # 41 | # which obtains its values from the Spec.Hostname and 42 | # Org.Domain, respectively. 43 | # --------------------------------------------------------------------------- 44 | # Specs: 45 | # - Hostname: foo # implicitly "foo.org1.example.com" 46 | # CommonName: foo27.org5.example.com # overrides Hostname-based FQDN set above 47 | # - Hostname: bar 48 | # - Hostname: baz 49 | # --------------------------------------------------------------------------- 50 | # "Template" 51 | # --------------------------------------------------------------------------- 52 | # Allows for the definition of 1 or more hosts that are created sequentially 53 | # from a template. By default, this looks like "peer%d" from 0 to Count-1. 54 | # You may override the number of nodes (Count), the starting index (Start) 55 | # or the template used to construct the name (Hostname). 56 | # 57 | # Note: Template and Specs are not mutually exclusive. You may define both 58 | # sections and the aggregate nodes will be created for you. Take care with 59 | # name collisions 60 | # --------------------------------------------------------------------------- 61 | Template: 62 | Count: 1 63 | # Start: 5 64 | Hostname: "peer1-hlf-peer" 65 | # --------------------------------------------------------------------------- 66 | # "Users" 67 | # --------------------------------------------------------------------------- 68 | # Count: The number of user accounts _in addition_ to Admin 69 | # --------------------------------------------------------------------------- 70 | Users: 71 | Count: 0 72 | -------------------------------------------------------------------------------- /dev_example/config/fabric-ca-client-config.yaml: -------------------------------------------------------------------------------- 1 | 2 | ############################################################################# 3 | # This is a configuration file for the fabric-ca-client command. 4 | # 5 | # COMMAND LINE ARGUMENTS AND ENVIRONMENT VARIABLES 6 | # ------------------------------------------------ 7 | # Each configuration element can be overridden via command line 8 | # arguments or environment variables. The precedence for determining 9 | # the value of each element is as follows: 10 | # 1) command line argument 11 | # Examples: 12 | # a) --url https://localhost:7054 13 | # To set the fabric-ca server url 14 | # b) --tls.client.certfile certfile.pem 15 | # To set the client certificate for TLS 16 | # 2) environment variable 17 | # Examples: 18 | # a) FABRIC_CA_CLIENT_URL=https://localhost:7054 19 | # To set the fabric-ca server url 20 | # b) FABRIC_CA_CLIENT_TLS_CLIENT_CERTFILE=certfile.pem 21 | # To set the client certificate for TLS 22 | # 3) configuration file 23 | # 4) default value (if there is one) 24 | # All default values are shown beside each element below. 25 | # 26 | # FILE NAME ELEMENTS 27 | # ------------------ 28 | # The value of all fields whose name ends with "file" or "files" are 29 | # name or names of other files. 30 | # For example, see "tls.certfiles" and "tls.client.certfile". 31 | # The value of each of these fields can be a simple filename, a 32 | # relative path, or an absolute path. If the value is not an 33 | # absolute path, it is interpretted as being relative to the location 34 | # of this configuration file. 35 | # 36 | ############################################################################# 37 | 38 | ############################################################################# 39 | # Client Configuration 40 | ############################################################################# 41 | 42 | # URL of the Fabric-ca-server (default: http://localhost:7054) 43 | url: 44 | 45 | # Membership Service Provider (MSP) directory 46 | # This is useful when the client is used to enroll a peer or orderer, so 47 | # that the enrollment artifacts are stored in the format expected by MSP. 48 | mspdir: 49 | 50 | ############################################################################# 51 | # TLS section for secure socket connection 52 | # 53 | # certfiles - PEM-encoded list of trusted root certificate files 54 | # client: 55 | # certfile - PEM-encoded certificate file for when client authentication 56 | # is enabled on server 57 | # keyfile - PEM-encoded key file for when client authentication 58 | # is enabled on server 59 | ############################################################################# 60 | tls: 61 | # TLS section for secure socket connection 62 | certfiles: 63 | client: 64 | certfile: 65 | keyfile: 66 | 67 | ############################################################################# 68 | # Certificate Signing Request section for generating the CSR for an 69 | # enrollment certificate (ECert) 70 | # 71 | # cn - Used by CAs to determine which domain the certificate is to be generated for 72 | # 73 | # serialnumber - The serialnumber field, if specified, becomes part of the issued 74 | # certificate's DN (Distinguished Name). For example, one use case for this is 75 | # a company with its own CA (Certificate Authority) which issues certificates 76 | # to its employees and wants to include the employee's serial number in the DN 77 | # of its issued certificates. 78 | # WARNING: The serialnumber field should not be confused with the certificate's 79 | # serial number which is set by the CA but is not a component of the 80 | # certificate's DN. 81 | # 82 | # names - A list of name objects. Each name object should contain at least one 83 | # "C", "L", "O", or "ST" value (or any combination of these) where these 84 | # are abbreviations for the following: 85 | # "C": country 86 | # "L": locality or municipality (such as city or town name) 87 | # "O": organization 88 | # "OU": organizational unit, such as the department responsible for owning the key; 89 | # it can also be used for a "Doing Business As" (DBS) name 90 | # "ST": the state or province 91 | # 92 | # Note that the "OU" or organizational units of an ECert are always set according 93 | # to the values of the identities type and affiliation. OUs are calculated for an enroll 94 | # as OU=, OU=, ..., OU=. For example, an identity 95 | # of type "client" with an affiliation of "org1.dept2.team3" would have the following 96 | # organizational units: OU=client, OU=org1, OU=dept2, OU=team3 97 | # 98 | # hosts - A list of host names for which the certificate should be valid 99 | # 100 | ############################################################################# 101 | csr: 102 | cn: ord-admin 103 | serialnumber: 104 | names: 105 | - C: IE 106 | ST: Dublin 107 | L: 108 | O: "AID:Tech" 109 | OU: Blockchain 110 | hosts: 111 | - Alejandros-MacBook-Pro.local 112 | 113 | ############################################################################# 114 | # Registration section used to register a new identity with fabric-ca server 115 | # 116 | # name - Unique name of the identity 117 | # type - Type of identity being registered (e.g. 'peer, app, user') 118 | # affiliation - The identity's affiliation 119 | # maxenrollments - The maximum number of times the secret can be reused to enroll. 120 | # Specially, -1 means unlimited; 0 means to use CA's max enrollment 121 | # value. 122 | # attributes - List of name/value pairs of attribute for identity 123 | ############################################################################# 124 | id: 125 | name: 126 | type: 127 | affiliation: 128 | maxenrollments: 0 129 | attributes: 130 | # - name: 131 | # value: 132 | 133 | ############################################################################# 134 | # Enrollment section used to enroll an identity with fabric-ca server 135 | # 136 | # profile - Name of the signing profile to use in issuing the certificate 137 | # label - Label to use in HSM operations 138 | ############################################################################# 139 | enrollment: 140 | profile: 141 | label: 142 | 143 | ############################################################################# 144 | # Name of the CA to connect to within the fabric-ca server 145 | ############################################################################# 146 | caname: 147 | 148 | ############################################################################# 149 | # BCCSP (BlockChain Crypto Service Provider) section allows to select which 150 | # crypto implementation library to use 151 | ############################################################################# 152 | bccsp: 153 | default: SW 154 | sw: 155 | hash: SHA2 156 | security: 256 157 | filekeystore: 158 | # The directory used for the software file-based keystore 159 | keystore: msp/keystore 160 | -------------------------------------------------------------------------------- /dev_example/helm_values/cdb-peer1.yaml: -------------------------------------------------------------------------------- 1 | image: 2 | tag: 0.4.10 3 | 4 | persistence: 5 | size: 1Gi 6 | -------------------------------------------------------------------------------- /dev_example/helm_values/ord1.yaml: -------------------------------------------------------------------------------- 1 | image: 2 | tag: 1.3.0 3 | 4 | persistence: 5 | accessMode: ReadWriteOnce 6 | size: 1Gi 7 | 8 | ord: 9 | type: solo 10 | mspID: OrdererMSP 11 | 12 | secrets: 13 | ord: 14 | cert: hlf--ord1-idcert 15 | key: hlf--ord1-idkey 16 | caCert: hlf--ord-cacert 17 | genesis: hlf--genesis 18 | adminCert: hlf--ord-admincert 19 | -------------------------------------------------------------------------------- /dev_example/helm_values/peer1.yaml: -------------------------------------------------------------------------------- 1 | image: 2 | tag: 1.3.0 3 | 4 | persistence: 5 | accessMode: ReadWriteOnce 6 | size: 1Gi 7 | 8 | peer: 9 | databaseType: CouchDB 10 | couchdbInstance: cdb-peer1 11 | mspID: PeerMSP 12 | 13 | secrets: 14 | peer: 15 | cert: hlf--peer1-idcert 16 | key: hlf--peer1-idkey 17 | caCert: hlf--peer-cacert 18 | channel: hlf--channel 19 | adminCert: hlf--peer-admincert 20 | adminKey: hlf--peer-adminkey 21 | -------------------------------------------------------------------------------- /helm-rbac.yaml: -------------------------------------------------------------------------------- 1 | apiVersion: v1 2 | kind: ServiceAccount 3 | metadata: 4 | name: tiller 5 | namespace: kube-system 6 | --- 7 | apiVersion: rbac.authorization.k8s.io/v1beta1 8 | kind: ClusterRoleBinding 9 | metadata: 10 | name: tiller 11 | roleRef: 12 | apiGroup: rbac.authorization.k8s.io 13 | kind: ClusterRole 14 | name: cluster-admin 15 | subjects: 16 | - kind: ServiceAccount 17 | name: tiller 18 | namespace: kube-system 19 | -------------------------------------------------------------------------------- /prod_example/LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /prod_example/README.md: -------------------------------------------------------------------------------- 1 | Table of Contents 2 | ================= 3 | 4 | * [Production deployment](#production-deployment) 5 | * [Before starting](#before-starting) 6 | * [Important note](#important-note) 7 | * [Pre-requisites](#pre-requisites) 8 | * [Customisation](#customisation) 9 | * [Creating](#creating) 10 | * [Fabric CA](#fabric-ca) 11 | * [Genesis and Channel](#genesis-and-channel) 12 | * [Kafka for Ordering service](#kafka-for-ordering-service) 13 | * [Fabric Orderer](#fabric-orderer) 14 | * [Fabric Peer](#fabric-peer) 15 | * [Deleting](#deleting) 16 | 17 | # Production deployment 18 | 19 | ## Before starting 20 | 21 | ### Important note 22 | 23 | While we call this a `production` deployment, this is not *quite* a production deployment because in production: 24 | 25 | 1. you will have more peers 26 | 2. you will have more orderers 27 | 3. you will have multiple organisations 28 | 29 | However, this is a good starting point for a production deployment. 30 | 31 | ### Pre-requisites 32 | 33 | Before running this tutorial you will need: 34 | 35 | 1) A Kubernetes (K8S) cluster with at least 4 nodes (you can get free credits to deploy a managed K8S cluster on AWS, GCP, Azure, etc) 36 | 2) Helm (and Tiller) installed on K8S 37 | 3) An `nginx-ingress` installation (using the Helm chart) 38 | 4) A `cert-manager` installation (using the Helm chart) 39 | 5) A domain name for your components (e.g. the Certificate Authority), connected to your `nginx-ingress` IP address - you can obtain one for free or $1.00 at many Domain Name Registrars. 40 | 41 | #### NGINX Ingress controller 42 | 43 | You can install the ingress controller by running this command: 44 | 45 | helm install stable/nginx-ingress -n nginx-ingress --namespace ingress-controller 46 | 47 | #### Certificate manager 48 | 49 | You can install the certificate manager, to ensure you can auto-generate the TLS certificates 50 | 51 | helm install stable/cert-manager -n cert-manager --namespace cert-manager 52 | 53 | Then we need to add the Staging and Production cluster issuers 54 | 55 | kubectl create -f ./extra/certManagerCI_staging.yaml 56 | 57 | kubectl create -f ./extra/certManagerCI_production.yaml 58 | 59 | ### Customisation 60 | 61 | #### Domain Name 62 | 63 | Currently, the `helm_values` files for the CA reference the following CA Domain Name: `ca.hgf.aidtech-test.xyz` in `/helm_values/ca.yaml` 64 | 65 | Since you won't have access to this, you should set this domain name to one you've obtained/purchased, and which is pointing to the `nginx-ingress` IP address. 66 | 67 | Alternatively, you may not use the Ingress at all and disable it, and instead use the CA through port-forwarding from the Kubernetes cluster to your local machine. For this you will need to adapt the instructions provided to your own use-case. 68 | 69 | ## Creating 70 | 71 | ### K8S namespaces 72 | 73 | Create the required namespaces: 74 | 75 | kubectl create ns cas orderers peers 76 | 77 | ### Fabric CA 78 | 79 | #### Installing 80 | 81 | Install the Fabric CA chart (it automatically creates a postgresql database) 82 | 83 | helm install stable/hlf-ca -n ca --namespace cas -f ./helm_values/ca.yaml 84 | 85 | Get pod for CA release 86 | 87 | CA_POD=$(kubectl get pods -n cas -l "app=hlf-ca,release=ca" -o jsonpath="{.items[0].metadata.name}") 88 | 89 | Check if server is ready 90 | 91 | kubectl logs -n cas $CA_POD | grep "Listening on" 92 | 93 | #### Fabric CA Identity 94 | 95 | Check that we don't have a certificate 96 | 97 | kubectl exec -n cas $CA_POD -- cat /var/hyperledger/fabric-ca/msp/signcerts/cert.pem 98 | 99 | kubectl exec -n cas $CA_POD -- bash -c 'fabric-ca-client enroll -d -u http://$CA_ADMIN:$CA_PASSWORD@$SERVICE_DNS:7054' 100 | 101 | Check that ingress works correctly 102 | 103 | CA_INGRESS=$(kubectl get ingress -n cas -l "app=hlf-ca,release=ca" -o jsonpath="{.items[0].spec.rules[0].host}") 104 | 105 | curl https://$CA_INGRESS/cainfo 106 | 107 | #### Org Admin Identities 108 | 109 | ##### Register 110 | 111 | ###### Orderer Organisation 112 | 113 | Get identity of ord-admin (this should not exist at first) 114 | 115 | kubectl exec -n cas $CA_POD -- fabric-ca-client identity list --id ord-admin 116 | 117 | Register Orderer Admin if the previous command did not work 118 | 119 | kubectl exec -n cas $CA_POD -- fabric-ca-client register --id.name ord-admin --id.secret OrdAdm1nPW --id.attrs 'admin=true:ecert' 120 | 121 | ###### Peer Organisation 122 | 123 | Get identity of ord-admin (this should not exist at first) 124 | 125 | kubectl exec -n cas $CA_POD -- fabric-ca-client identity list --id peer-admin 126 | 127 | Register Peer Admin if the previous command did not work 128 | 129 | kubectl exec -n cas $CA_POD -- fabric-ca-client register --id.name peer-admin --id.secret PeerAdm1nPW --id.attrs 'admin=true:ecert' 130 | 131 | ##### Enroll 132 | 133 | ###### Orderer Organisation 134 | 135 | Enroll the Organisation Admin identity (typically we would use a more secure password than `OrdAdm1nPW`, etc.) 136 | 137 | FABRIC_CA_CLIENT_HOME=./config fabric-ca-client enroll -u https://ord-admin:OrdAdm1nPW@$CA_INGRESS -M ./OrdererMSP 138 | 139 | Copy the signcerts to admincerts 140 | 141 | mkdir -p ./config/OrdererMSP/admincerts 142 | 143 | cp ./config/OrdererMSP/signcerts/* ./config/OrdererMSP/admincerts 144 | 145 | 146 | ###### Peer Organisation 147 | 148 | Enroll the Organisation Admin identity (typically we would use a more secure password than `PeerAdm1nPW`, etc.) 149 | 150 | FABRIC_CA_CLIENT_HOME=./config fabric-ca-client enroll -u https://peer-admin:PeerAdm1nPW@$CA_INGRESS -M ./PeerMSP 151 | 152 | Copy the signcerts to admincerts 153 | 154 | mkdir -p ./config/PeerMSP/admincerts 155 | 156 | cp ./config/PeerMSP/signcerts/* ./config/PeerMSP/admincerts 157 | 158 | ##### Save Crypto Material 159 | 160 | ###### Orderer Organisation 161 | 162 | Create a secret to hold the admin certificate: 163 | 164 | ORG_CERT=$(ls ./config/OrdererMSP/admincerts/cert.pem) 165 | 166 | kubectl create secret generic -n orderers hlf--ord-admincert --from-file=cert.pem=$ORG_CERT 167 | 168 | Create a secret to hold the admin key: 169 | 170 | ORG_KEY=$(ls ./config/OrdererMSP/keystore/*_sk) 171 | 172 | kubectl create secret generic -n orderers hlf--ord-adminkey --from-file=key.pem=$ORG_KEY 173 | 174 | Create a secret to hold the admin key CA certificate: 175 | 176 | CA_CERT=$(ls ./config/OrdererMSP/cacerts/*.pem) 177 | 178 | kubectl create secret generic -n orderers hlf--ord-ca-cert --from-file=cacert.pem=$CA_CERT 179 | 180 | ###### Peer Organisation 181 | 182 | Create a secret to hold the admincert: 183 | 184 | ORG_CERT=$(ls ./config/PeerMSP/admincerts/cert.pem) 185 | 186 | kubectl create secret generic -n peers hlf--peer-admincert --from-file=cert.pem=$ORG_CERT 187 | 188 | Create a secret to hold the admin key: 189 | 190 | ORG_KEY=$(ls ./config/PeerMSP/keystore/*_sk) 191 | 192 | kubectl create secret generic -n peers hlf--peer-adminkey --from-file=key.pem=$ORG_KEY 193 | 194 | Create a secret to hold the CA certificate: 195 | 196 | CA_CERT=$(ls ./config/PeerMSP/cacerts/*.pem) 197 | 198 | kubectl create secret generic -n peers hlf--peer-ca-cert --from-file=cacert.pem=$CA_CERT 199 | 200 | ### Genesis and channel 201 | 202 | cd ./config 203 | 204 | Create Genesis block and Channel 205 | 206 | configtxgen -profile OrdererGenesis -outputBlock ./genesis.block 207 | 208 | configtxgen -profile MyChannel -channelID mychannel -outputCreateChannelTx ./mychannel.tx 209 | 210 | Save them as secrets 211 | 212 | kubectl create secret generic -n orderers hlf--genesis --from-file=genesis.block 213 | 214 | kubectl create secret generic -n peers hlf--channel --from-file=mychannel.tx 215 | 216 | Get back to where we were before... 217 | 218 | cd .. 219 | 220 | ### Kafka for Ordering service 221 | 222 | Install Kafka chart (use special values to ensure 4 Kafka brokers and that Kafka messages don't disappear) 223 | 224 | helm install incubator/kafka -n kafka-hlf --namespace orderers -f ./helm_values/kafka-hlf.yaml 225 | 226 | ### Fabric Orderer 227 | 228 | For each orderer set the `NUM` environmental variable and follow the below instructions (in this example, either 1 or 2): 229 | 230 | export NUM=1 231 | 232 | #### Crypto material 233 | 234 | Register orderer with CA (typically we would use a more secure password than `ord1_pw`, etc.) 235 | 236 | kubectl exec -n cas $CA_POD -- fabric-ca-client register --id.name ord${NUM} --id.secret ord${NUM}_pw --id.type orderer 237 | 238 | FABRIC_CA_CLIENT_HOME=./config fabric-ca-client enroll -d -u https://ord${NUM}:ord${NUM}_pw@$CA_INGRESS -M ord${NUM}_MSP 239 | 240 | Save the Orderer certificate in a secret 241 | 242 | NODE_CERT=$(ls ./config/ord${NUM}_MSP/signcerts/*.pem) 243 | 244 | kubectl create secret generic -n orderers hlf--ord${NUM}-idcert --from-file=cert.pem=${NODE_CERT} 245 | 246 | Save the Orderer private key in another secret 247 | 248 | NODE_KEY=$(ls ./config/ord${NUM}_MSP/keystore/*_sk) 249 | 250 | kubectl create secret generic -n orderers hlf--ord${NUM}-idkey --from-file=key.pem=${NODE_KEY} 251 | 252 | #### Helm charts 253 | 254 | Install orderers 255 | 256 | helm install stable/hlf-ord -n ord${NUM} --namespace orderers -f ./helm_values/ord${NUM}.yaml 257 | 258 | Get logs from orderer to check it's actually started 259 | 260 | ORD_POD=$(kubectl get pods -n orderers -l "app=hlf-ord,release=ord${NUM}" -o jsonpath="{.items[0].metadata.name}") 261 | 262 | kubectl logs -n orderers $ORD_POD | grep 'completeInitialization' 263 | 264 | > Repeat all above steps for Orderer 2, etc. 265 | 266 | ### Fabric Peer 267 | 268 | For each peer set the `NUM` environmental variable and follow the below instructions (in this example, either 1 or 2): 269 | 270 | export NUM=1 271 | 272 | #### CouchDB Helm Chart 273 | 274 | Install CouchDB chart 275 | 276 | helm install stable/hlf-couchdb -n cdb-peer${NUM} --namespace peers -f ./helm_values/cdb-peer${NUM}.yaml 277 | 278 | Check that CouchDB is running 279 | 280 | CDB_POD=$(kubectl get pods -n peers -l "app=hlf-couchdb,release=cdb-peer${NUM}" -o jsonpath="{.items[*].metadata.name}") 281 | 282 | kubectl logs -n peers $CDB_POD | grep 'Apache CouchDB has started on' 283 | 284 | #### Crypto material 285 | 286 | Register orderer with CA (typically we would use a more secure password than `peer1_pw`, etc.) 287 | 288 | kubectl exec -n cas $CA_POD -- fabric-ca-client register --id.name peer${NUM} --id.secret peer${NUM}_pw --id.type peer 289 | 290 | FABRIC_CA_CLIENT_HOME=./config fabric-ca-client enroll -d -u https://peer${NUM}:peer${NUM}_pw@$CA_INGRESS -M peer${NUM}_MSP 291 | 292 | Save the Peer certificate in a secret 293 | 294 | NODE_CERT=$(ls ./config/peer${NUM}_MSP/signcerts/*.pem) 295 | 296 | kubectl create secret generic -n peers hlf--peer${NUM}-idcert --from-file=cert.pem=${NODE_CERT} 297 | 298 | Save the Peer private key in another secret 299 | 300 | NODE_KEY=$(ls ./config/peer${NUM}_MSP/keystore/*_sk) 301 | 302 | kubectl create secret generic -n peers hlf--peer${NUM}-idkey --from-file=key.pem=${NODE_KEY} 303 | 304 | #### Peer Helm Chart 305 | 306 | Install Peer 307 | 308 | helm install stable/hlf-peer -n peer${NUM} --namespace peers -f ./helm_values/peer${NUM}.yaml 309 | 310 | Get Peer pod: 311 | 312 | PEER_POD=$(kubectl get pods -n peers -l "app=hlf-peer,release=peer${NUM}" -o jsonpath="{.items[0].metadata.name}") 313 | 314 | And check that Peer is running 315 | 316 | kubectl logs -n peers $PEER_POD | grep 'Starting peer' 317 | 318 | > Repeat all above steps for Peer 2, etc. 319 | 320 | #### Channels 321 | 322 | Create channel (do this only once in Peer 1) 323 | 324 | kubectl exec -n peers $PEER_POD -- peer channel create -o ord1-hlf-ord.orderers.svc.cluster.local:7050 -c mychannel -f /hl_config/channel/mychannel.tx 325 | 326 | Fetch and join channel 327 | 328 | kubectl exec -n peers $PEER_POD -- peer channel fetch config /var/hyperledger/mychannel.block -c mychannel -o ord1-hlf-ord.orderers.svc.cluster.local:7050 329 | 330 | kubectl exec -n peers $PEER_POD -- bash -c 'CORE_PEER_MSPCONFIGPATH=$ADMIN_MSP_PATH peer channel join -b /var/hyperledger/mychannel.block' 331 | 332 | > Repeat above 2 commands (`fetch` & `join`) for Peer 2, etc. 333 | 334 | Check which channels the peer has joined: 335 | 336 | kubectl exec $PEER_POD -n peers -- peer channel list 337 | 338 | ## Deleting 339 | 340 | Delete helm deployments 341 | 342 | helm delete --purge ca kafka-hlf ord1 ord2 cdb-peer1 peer1 cdb-peer2 peer2 343 | 344 | Delete stateful sets (in case Helm does not fully delete them) 345 | 346 | kubectl delete statefulset -n orderers kafka-log kafka-hlf-zookeeper kafka-hlf 347 | 348 | Delete Persistent Volume Claims 349 | 350 | kubectl delete pvc -n cas data-ca-postgresql-0 351 | 352 | kubectl delete pvc -n orderers data-kafka-hlf-zookeeper-0 data-kafka-hlf-zookeeper-1 data-kafka-hlf-zookeeper-2 datadir-kafka-hlf-0 datadir-kafka-hlf-1 datadir-kafka-hlf-2 datadir-kafka-hlf-3 353 | 354 | Delete secrets on K8S: 355 | 356 | kubectl delete secret -n orderers hlf--ord-admincert hlf--ord-adminkey hlf--ord-ca-cert hlf--genesis hlf--ord1-idcert hlf--ord2-idcert hlf--ord1-idkey hlf--ord2-idkey 357 | 358 | kubectl delete secret -n peers hlf--peer-admincert hlf--peer-adminkey hlf--peer-ca-cert hlf--channel hlf--peer1-idcert hlf--peer2-idcert hlf--peer1-idkey hlf--peer2-idkey 359 | 360 | Delete crypto material files: 361 | 362 | rm -rf ./config/*MSP ./config/genesis.block ./config/mychannel.tx 363 | 364 | Clean up namespaces we used for the production examples 365 | 366 | kubectl delete ns cas orderers peers 367 | -------------------------------------------------------------------------------- /prod_example/config/Lets_Encrypt_Authority_X3.pem: -------------------------------------------------------------------------------- 1 | -----BEGIN CERTIFICATE----- 2 | MIIEkjCCA3qgAwIBAgIQCgFBQgAAAVOFc2oLheynCDANBgkqhkiG9w0BAQsFADA/ 3 | MSQwIgYDVQQKExtEaWdpdGFsIFNpZ25hdHVyZSBUcnVzdCBDby4xFzAVBgNVBAMT 4 | DkRTVCBSb290IENBIFgzMB4XDTE2MDMxNzE2NDA0NloXDTIxMDMxNzE2NDA0Nlow 5 | SjELMAkGA1UEBhMCVVMxFjAUBgNVBAoTDUxldCdzIEVuY3J5cHQxIzAhBgNVBAMT 6 | GkxldCdzIEVuY3J5cHQgQXV0aG9yaXR5IFgzMIIBIjANBgkqhkiG9w0BAQEFAAOC 7 | AQ8AMIIBCgKCAQEAnNMM8FrlLke3cl03g7NoYzDq1zUmGSXhvb418XCSL7e4S0EF 8 | q6meNQhY7LEqxGiHC6PjdeTm86dicbp5gWAf15Gan/PQeGdxyGkOlZHP/uaZ6WA8 9 | SMx+yk13EiSdRxta67nsHjcAHJyse6cF6s5K671B5TaYucv9bTyWaN8jKkKQDIZ0 10 | Z8h/pZq4UmEUEz9l6YKHy9v6Dlb2honzhT+Xhq+w3Brvaw2VFn3EK6BlspkENnWA 11 | a6xK8xuQSXgvopZPKiAlKQTGdMDQMc2PMTiVFrqoM7hD8bEfwzB/onkxEz0tNvjj 12 | /PIzark5McWvxI0NHWQWM6r6hCm21AvA2H3DkwIDAQABo4IBfTCCAXkwEgYDVR0T 13 | AQH/BAgwBgEB/wIBADAOBgNVHQ8BAf8EBAMCAYYwfwYIKwYBBQUHAQEEczBxMDIG 14 | CCsGAQUFBzABhiZodHRwOi8vaXNyZy50cnVzdGlkLm9jc3AuaWRlbnRydXN0LmNv 15 | bTA7BggrBgEFBQcwAoYvaHR0cDovL2FwcHMuaWRlbnRydXN0LmNvbS9yb290cy9k 16 | c3Ryb290Y2F4My5wN2MwHwYDVR0jBBgwFoAUxKexpHsscfrb4UuQdf/EFWCFiRAw 17 | VAYDVR0gBE0wSzAIBgZngQwBAgEwPwYLKwYBBAGC3xMBAQEwMDAuBggrBgEFBQcC 18 | ARYiaHR0cDovL2Nwcy5yb290LXgxLmxldHNlbmNyeXB0Lm9yZzA8BgNVHR8ENTAz 19 | MDGgL6AthitodHRwOi8vY3JsLmlkZW50cnVzdC5jb20vRFNUUk9PVENBWDNDUkwu 20 | Y3JsMB0GA1UdDgQWBBSoSmpjBH3duubRObemRWXv86jsoTANBgkqhkiG9w0BAQsF 21 | AAOCAQEA3TPXEfNjWDjdGBX7CVW+dla5cEilaUcne8IkCJLxWh9KEik3JHRRHGJo 22 | uM2VcGfl96S8TihRzZvoroed6ti6WqEBmtzw3Wodatg+VyOeph4EYpr/1wXKtx8/ 23 | wApIvJSwtmVi4MFU5aMqrSDE6ea73Mj2tcMyo5jMd6jmeWUHK8so/joWUoHOUgwu 24 | X4Po1QYz+3dszkDqMp4fklxBwXRsW10KXzPMTZ+sOPAveyxindmjkW8lGy+QsRlG 25 | PfZ+G6Z6h7mjem0Y+iWlkYcV4PIWL1iwBi8saCbGS5jN2p8M+X+Q7UNKEkROb3N6 26 | KOqkqm57TH2H3eDJAkSnh6/DNFu0Qg== 27 | -----END CERTIFICATE----- 28 | -------------------------------------------------------------------------------- /prod_example/config/configtx.yaml: -------------------------------------------------------------------------------- 1 | # Copyright IBM Corp. All Rights Reserved. 2 | # 3 | # SPDX-License-Identifier: Apache-2.0 4 | # 5 | 6 | ################################################################################ 7 | # 8 | # Section: Organizations 9 | # 10 | # - This section defines the different organizational identities which will 11 | # be referenced later in the configuration. 12 | # 13 | ################################################################################ 14 | Organizations: 15 | 16 | # SampleOrg defines an MSP using the sampleconfig. It should never be used 17 | # in production but may be used as a template for other definitions 18 | - &OrdererOrg 19 | # DefaultOrg defines the organization which is used in the sampleconfig 20 | # of the fabric.git development environment 21 | Name: OrdererOrg 22 | 23 | # ID to load the MSP definition as 24 | ID: OrdererMSP 25 | 26 | # MSPDir is the filesystem path which contains the MSP configuration 27 | MSPDir: ./OrdererMSP 28 | 29 | # turn off security for the channel 30 | AdminPrincipal: Role.MEMBER 31 | 32 | # Organization controlling both peers and Orderers 33 | - &AidTech 34 | Name: AidTech 35 | 36 | # ID to load the MSP definition as 37 | ID: PeerMSP 38 | 39 | MSPDir: ./PeerMSP 40 | 41 | # turn off security for the peer 42 | AdminPrincipal: Role.MEMBER 43 | 44 | AnchorPeers: 45 | # AnchorPeers defines the location of peers that can be used 46 | # for cross org gossip communication. Note, this value is only 47 | # encoded in the genesis block in the Application section context 48 | - Host: peer1-hlf-peer.peers.svc.cluster.local 49 | Port: 7051 50 | 51 | ################################################################################ 52 | # 53 | # SECTION: Orderer 54 | # 55 | # - This section defines the values to encode into a config transaction or 56 | # genesis block for orderer related parameters 57 | # 58 | ################################################################################ 59 | Orderer: &OrdererDefaults 60 | 61 | # Orderer Type: The orderer implementation to start 62 | # Available types are "solo" and "kafka" 63 | OrdererType: kafka 64 | 65 | Addresses: 66 | - ord1-hlf-ord.orderers.svc.cluster.local:7050 67 | - ord2-hlf-ord.orderers.svc.cluster.local:7050 68 | 69 | # Batch Timeout: The amount of time to wait before creating a batch 70 | BatchTimeout: 2s 71 | 72 | # Batch Size: Controls the number of messages batched into a block 73 | BatchSize: 74 | 75 | # Max Message Count: The maximum number of messages to permit in a batch 76 | MaxMessageCount: 10 77 | 78 | # Absolute Max Bytes: The absolute maximum number of bytes allowed for 79 | # the serialized messages in a batch. 80 | AbsoluteMaxBytes: 98 MB 81 | 82 | # Preferred Max Bytes: The preferred maximum number of bytes allowed for 83 | # the serialized messages in a batch. A message larger than the preferred 84 | # max bytes will result in a batch larger than preferred max bytes. 85 | PreferredMaxBytes: 512 KB 86 | 87 | Kafka: 88 | # Brokers: A list of Kafka brokers to which the orderer connects 89 | # If using K8S, we specify the service exposing the brokers 90 | # NOTE: Use Address/IP:port notation 91 | Brokers: 92 | - kafka-hlf.orderers.svc.cluster.local:9092 93 | 94 | # Organizations is the list of orgs which are defined as participants on 95 | # the orderer side of the network 96 | Organizations: 97 | 98 | ################################################################################ 99 | # 100 | # SECTION: Application 101 | # 102 | # - This section defines the values to encode into a config transaction or 103 | # genesis block for application related parameters 104 | # 105 | ################################################################################ 106 | Application: &ApplicationDefaults 107 | 108 | # Organizations is the list of orgs which are defined as participants on 109 | # the application side of the network 110 | Organizations: 111 | 112 | ################################################################################ 113 | # 114 | # Profile 115 | # 116 | # - Different configuration profiles may be encoded here to be specified 117 | # as parameters to the configtxgen tool 118 | # 119 | ################################################################################ 120 | Profiles: 121 | 122 | OrdererGenesis: 123 | Orderer: 124 | <<: *OrdererDefaults 125 | Organizations: 126 | - *OrdererOrg 127 | Consortiums: 128 | MyConsortium: 129 | Organizations: 130 | - *AidTech 131 | MyChannel: 132 | Consortium: MyConsortium 133 | Application: 134 | <<: *ApplicationDefaults 135 | Organizations: 136 | - *AidTech 137 | -------------------------------------------------------------------------------- /prod_example/config/fabric-ca-client-config.yaml: -------------------------------------------------------------------------------- 1 | 2 | ############################################################################# 3 | # This is a configuration file for the fabric-ca-client command. 4 | # 5 | # COMMAND LINE ARGUMENTS AND ENVIRONMENT VARIABLES 6 | # ------------------------------------------------ 7 | # Each configuration element can be overridden via command line 8 | # arguments or environment variables. The precedence for determining 9 | # the value of each element is as follows: 10 | # 1) command line argument 11 | # Examples: 12 | # a) --url https://localhost:7054 13 | # To set the fabric-ca server url 14 | # b) --tls.client.certfile certfile.pem 15 | # To set the client certificate for TLS 16 | # 2) environment variable 17 | # Examples: 18 | # a) FABRIC_CA_CLIENT_URL=https://localhost:7054 19 | # To set the fabric-ca server url 20 | # b) FABRIC_CA_CLIENT_TLS_CLIENT_CERTFILE=certfile.pem 21 | # To set the client certificate for TLS 22 | # 3) configuration file 23 | # 4) default value (if there is one) 24 | # All default values are shown beside each element below. 25 | # 26 | # FILE NAME ELEMENTS 27 | # ------------------ 28 | # The value of all fields whose name ends with "file" or "files" are 29 | # name or names of other files. 30 | # For example, see "tls.certfiles" and "tls.client.certfile". 31 | # The value of each of these fields can be a simple filename, a 32 | # relative path, or an absolute path. If the value is not an 33 | # absolute path, it is interpretted as being relative to the location 34 | # of this configuration file. 35 | # 36 | ############################################################################# 37 | 38 | ############################################################################# 39 | # Client Configuration 40 | ############################################################################# 41 | 42 | # URL of the Fabric-ca-server (default: http://localhost:7054) 43 | url: 44 | 45 | # Membership Service Provider (MSP) directory 46 | # This is useful when the client is used to enroll a peer or orderer, so 47 | # that the enrollment artifacts are stored in the format expected by MSP. 48 | mspdir: 49 | 50 | ############################################################################# 51 | # TLS section for secure socket connection 52 | # 53 | # certfiles - PEM-encoded list of trusted root certificate files 54 | # client: 55 | # certfile - PEM-encoded certificate file for when client authentication 56 | # is enabled on server 57 | # keyfile - PEM-encoded key file for when client authentication 58 | # is enabled on server 59 | ############################################################################# 60 | tls: 61 | enabled: false 62 | # TLS section for secure socket connection 63 | certfiles: 64 | - ./Lets_Encrypt_Authority_X3.pem 65 | client: 66 | certfile: 67 | keyfile: 68 | 69 | ############################################################################# 70 | # Certificate Signing Request section for generating the CSR for an 71 | # enrollment certificate (ECert) 72 | # 73 | # cn - Used by CAs to determine which domain the certificate is to be generated for 74 | # 75 | # serialnumber - The serialnumber field, if specified, becomes part of the issued 76 | # certificate's DN (Distinguished Name). For example, one use case for this is 77 | # a company with its own CA (Certificate Authority) which issues certificates 78 | # to its employees and wants to include the employee's serial number in the DN 79 | # of its issued certificates. 80 | # WARNING: The serialnumber field should not be confused with the certificate's 81 | # serial number which is set by the CA but is not a component of the 82 | # certificate's DN. 83 | # 84 | # names - A list of name objects. Each name object should contain at least one 85 | # "C", "L", "O", or "ST" value (or any combination of these) where these 86 | # are abbreviations for the following: 87 | # "C": country 88 | # "L": locality or municipality (such as city or town name) 89 | # "O": organization 90 | # "OU": organizational unit, such as the department responsible for owning the key; 91 | # it can also be used for a "Doing Business As" (DBS) name 92 | # "ST": the state or province 93 | # 94 | # Note that the "OU" or organizational units of an ECert are always set according 95 | # to the values of the identities type and affiliation. OUs are calculated for an enroll 96 | # as OU=, OU=, ..., OU=. For example, an identity 97 | # of type "client" with an affiliation of "org1.dept2.team3" would have the following 98 | # organizational units: OU=client, OU=org1, OU=dept2, OU=team3 99 | # 100 | # hosts - A list of host names for which the certificate should be valid 101 | # 102 | ############################################################################# 103 | csr: 104 | cn: ord-admin 105 | serialnumber: 106 | names: 107 | - C: IE 108 | ST: Dublin 109 | L: 110 | O: "AID:Tech" 111 | OU: Blockchain 112 | hosts: 113 | - Alejandros-MacBook-Pro.local 114 | 115 | ############################################################################# 116 | # Registration section used to register a new identity with fabric-ca server 117 | # 118 | # name - Unique name of the identity 119 | # type - Type of identity being registered (e.g. 'peer, app, user') 120 | # affiliation - The identity's affiliation 121 | # maxenrollments - The maximum number of times the secret can be reused to enroll. 122 | # Specially, -1 means unlimited; 0 means to use CA's max enrollment 123 | # value. 124 | # attributes - List of name/value pairs of attribute for identity 125 | ############################################################################# 126 | id: 127 | name: 128 | type: 129 | affiliation: 130 | maxenrollments: 0 131 | attributes: 132 | # - name: 133 | # value: 134 | 135 | ############################################################################# 136 | # Enrollment section used to enroll an identity with fabric-ca server 137 | # 138 | # profile - Name of the signing profile to use in issuing the certificate 139 | # label - Label to use in HSM operations 140 | ############################################################################# 141 | enrollment: 142 | profile: 143 | label: 144 | 145 | ############################################################################# 146 | # Name of the CA to connect to within the fabric-ca server 147 | ############################################################################# 148 | caname: 149 | 150 | ############################################################################# 151 | # BCCSP (BlockChain Crypto Service Provider) section allows to select which 152 | # crypto implementation library to use 153 | ############################################################################# 154 | bccsp: 155 | default: SW 156 | sw: 157 | hash: SHA2 158 | security: 256 159 | filekeystore: 160 | # The directory used for the software file-based keystore 161 | keystore: msp/keystore 162 | -------------------------------------------------------------------------------- /prod_example/extra/certManagerCI_production.yaml: -------------------------------------------------------------------------------- 1 | apiVersion: certmanager.k8s.io/v1alpha1 2 | kind: ClusterIssuer 3 | metadata: 4 | name: letsencrypt-production 5 | spec: 6 | acme: 7 | # The ACME server URL 8 | server: https://acme-v02.api.letsencrypt.org/directory 9 | # Email address used for ACME registration 10 | # TODO: Change email address to yours 11 | email: youremail@example.com 12 | # Name of a secret used to store the ACME account private key 13 | privateKeySecretRef: 14 | name: letsencrypt-production 15 | # Enable the HTTP-01 challenge provider 16 | http01: {} 17 | -------------------------------------------------------------------------------- /prod_example/extra/certManagerCI_staging.yaml: -------------------------------------------------------------------------------- 1 | apiVersion: certmanager.k8s.io/v1alpha1 2 | kind: ClusterIssuer 3 | metadata: 4 | name: letsencrypt-staging 5 | spec: 6 | acme: 7 | # The ACME server URL 8 | server: https://acme-staging-v02.api.letsencrypt.org/directory 9 | # Email address used for ACME registration 10 | # TODO: Change email address to yours 11 | email: youremail@example.com 12 | # Name of a secret used to store the ACME account private key 13 | privateKeySecretRef: 14 | name: letsencrypt-staging 15 | # Enable the HTTP-01 challenge provider 16 | http01: {} 17 | -------------------------------------------------------------------------------- /prod_example/helm_values/ca.yaml: -------------------------------------------------------------------------------- 1 | image: 2 | tag: 1.3.0 3 | 4 | ingress: 5 | enabled: true 6 | annotations: 7 | kubernetes.io/ingress.class: nginx 8 | certmanager.k8s.io/cluster-issuer: "letsencrypt-production" 9 | path: / 10 | hosts: 11 | # TODO: Change this to your Domain Name 12 | - ca.hgf.aidtech-test.xyz 13 | tls: 14 | - secretName: ca--tls 15 | hosts: 16 | # TODO: Change this to your Domain Name 17 | - ca.hgf.aidtech-test.xyz 18 | 19 | persistence: 20 | accessMode: ReadWriteOnce 21 | size: 1Gi 22 | 23 | caName: ca 24 | 25 | postgresql: 26 | enabled: true 27 | 28 | config: 29 | hlfToolsVersion: 1.3.0 30 | csr: 31 | names: 32 | c: IE 33 | st: Dublin 34 | l: 35 | o: "AID:Tech" 36 | ou: Blockchain 37 | affiliations: 38 | aidtech: [] 39 | 40 | affinity: 41 | podAntiAffinity: 42 | preferredDuringSchedulingIgnoredDuringExecution: 43 | - weight: 95 44 | podAffinityTerm: 45 | topologyKey: "kubernetes.io/hostname" 46 | labelSelector: 47 | matchLabels: 48 | app: hlf-ca 49 | podAffinity: 50 | requiredDuringSchedulingIgnoredDuringExecution: 51 | - labelSelector: 52 | matchLabels: 53 | app: postgresql 54 | release: ca 55 | topologyKey: "kubernetes.io/hostname" 56 | -------------------------------------------------------------------------------- /prod_example/helm_values/cdb-peer1.yaml: -------------------------------------------------------------------------------- 1 | image: 2 | tag: 0.4.10 3 | 4 | persistence: 5 | size: 1Gi 6 | 7 | affinity: 8 | podAntiAffinity: 9 | preferredDuringSchedulingIgnoredDuringExecution: 10 | - weight: 95 11 | podAffinityTerm: 12 | topologyKey: "kubernetes.io/hostname" 13 | labelSelector: 14 | matchLabels: 15 | app: hlf-couchdb 16 | -------------------------------------------------------------------------------- /prod_example/helm_values/cdb-peer2.yaml: -------------------------------------------------------------------------------- 1 | image: 2 | tag: 0.4.10 3 | 4 | persistence: 5 | size: 1Gi 6 | 7 | affinity: 8 | podAntiAffinity: 9 | preferredDuringSchedulingIgnoredDuringExecution: 10 | - weight: 95 11 | podAffinityTerm: 12 | topologyKey: "kubernetes.io/hostname" 13 | labelSelector: 14 | matchLabels: 15 | app: hlf-couchdb 16 | -------------------------------------------------------------------------------- /prod_example/helm_values/kafka-hlf.yaml: -------------------------------------------------------------------------------- 1 | ## The StatefulSet installs 3 pods by default 2 | replicas: 4 3 | 4 | ## The kafka image repository 5 | image: "confluentinc/cp-kafka" 6 | 7 | ## The kafka image tag 8 | imageTag: "4.1.1-2" 9 | 10 | ## If RBAC is enabled on the cluster, the Kafka init container needs a service account 11 | ## with permissisions sufficient to apply pod labels 12 | rbac: 13 | enabled: true 14 | 15 | ## Pod scheduling preferences (by default keep pods within a release on separate nodes). 16 | ## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity 17 | affinity: 18 | podAntiAffinity: 19 | requiredDuringSchedulingIgnoredDuringExecution: 20 | - topologyKey: "kubernetes.io/hostname" 21 | labelSelector: 22 | matchLabels: 23 | app: kafka 24 | release: kafka-hlf 25 | podAffinity: 26 | preferredDuringSchedulingIgnoredDuringExecution: 27 | - weight: 50 28 | podAffinityTerm: 29 | topologyKey: "kubernetes.io/hostname" 30 | labelSelector: 31 | matchLabels: 32 | app: zookeeper 33 | release: kafka-hlf 34 | 35 | ## Configuration Overrides. Specify any Kafka settings you would like set on the StatefulSet 36 | ## here in map format, as defined in the official docs. 37 | ## ref: https://kafka.apache.org/documentation/#brokerconfigs 38 | ## 39 | configurationOverrides: 40 | "offsets.topic.replication.factor": 3 41 | # "auto.leader.rebalance.enable": true 42 | # "controlled.shutdown.enable": true 43 | # "controlled.shutdown.max.retries": 100 44 | "auto.create.topics.enable": true # Useful to enable the Node.js client to create topics as required 45 | 46 | # NOTE: The below are required for Hyperledger Fabric orderer to work (but last one is problematic for normal setups - best to keep separate Kafka clusters for logs/HLF) 47 | "default.replication.factor": 3 48 | "unclean.leader.election.enable": false 49 | "min.insync.replicas": 2 50 | "message.max.bytes": "103809024" # 99 * 1024 * 1024 B 51 | "replica.fetch.max.bytes": "103809024" # 99 * 1024 * 1024 B 52 | "log.retention.ms": -1 # This should be only used for the HL Fabric Orderer (which needs to keep all logs) 53 | 54 | ## Persistence configuration. Specify if and how to persist data to a persistent volume. 55 | persistence: 56 | enabled: true 57 | 58 | ## The size of the PersistentVolume to allocate to each Kafka Pod in the StatefulSet 59 | size: "1Gi" 60 | 61 | ## Prometheus Exporters / Metrics 62 | prometheus: 63 | ## Prometheus JMX Exporter: exposes the majority of Kafkas metrics 64 | jmx: 65 | enabled: true 66 | 67 | ## Prometheus Kafka Exporter: exposes complimentary metrics to JMX Exporter 68 | kafka: 69 | enabled: true 70 | 71 | # ------------------------------------------------------------------------------ 72 | # Zookeeper: 73 | # ------------------------------------------------------------------------------ 74 | zookeeper: 75 | ## If true, install the Zookeeper chart alongside Kafka 76 | ## ref: https://github.com/kubernetes/charts/tree/master/incubator/zookeeper 77 | enabled: true 78 | 79 | ## Explicitly set the number of replicas of Zookeeper 80 | replicaCount: 3 81 | 82 | ## Configure Zookeeper resource requests and limits 83 | ## ref: http://kubernetes.io/docs/user-guide/compute-resources/ 84 | resources: ~ 85 | 86 | ## The JVM heap size to allocate to Zookeeper 87 | env: 88 | ZK_HEAP_SIZE: "1G" 89 | 90 | persistence: 91 | enabled: true 92 | ## The amount of PV storage allocated to each Zookeeper pod in the statefulset 93 | size: "1Gi" 94 | 95 | ## Pod scheduling preferences (by default keep pods within a release on separate nodes). 96 | ## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity 97 | affinity: # Criteria by which pod label-values influence scheduling for zookeeper pods. 98 | podAntiAffinity: 99 | requiredDuringSchedulingIgnoredDuringExecution: 100 | - topologyKey: "kubernetes.io/hostname" 101 | labelSelector: 102 | matchLabels: 103 | app: zookeeper 104 | release: kafka-hlf 105 | -------------------------------------------------------------------------------- /prod_example/helm_values/ord1.yaml: -------------------------------------------------------------------------------- 1 | image: 2 | tag: 1.3.0 3 | 4 | persistence: 5 | accessMode: ReadWriteOnce 6 | size: 1Gi 7 | 8 | ord: 9 | type: kafka 10 | mspID: OrdererMSP 11 | 12 | secrets: 13 | ord: 14 | cert: hlf--ord1-idcert 15 | key: hlf--ord1-idkey 16 | caCert: hlf--ord-ca-cert 17 | genesis: hlf--genesis 18 | adminCert: hlf--ord-admincert 19 | 20 | affinity: 21 | podAntiAffinity: 22 | preferredDuringSchedulingIgnoredDuringExecution: 23 | - weight: 95 24 | podAffinityTerm: 25 | topologyKey: "kubernetes.io/hostname" 26 | labelSelector: 27 | matchLabels: 28 | app: hlf-ord 29 | -------------------------------------------------------------------------------- /prod_example/helm_values/ord2.yaml: -------------------------------------------------------------------------------- 1 | image: 2 | tag: 1.3.0 3 | 4 | persistence: 5 | accessMode: ReadWriteOnce 6 | size: 1Gi 7 | 8 | ord: 9 | type: kafka 10 | mspID: OrdererMSP 11 | 12 | secrets: 13 | ord: 14 | cert: hlf--ord2-idcert 15 | key: hlf--ord2-idkey 16 | caCert: hlf--ord-ca-cert 17 | genesis: hlf--genesis 18 | adminCert: hlf--ord-admincert 19 | 20 | affinity: 21 | podAntiAffinity: 22 | preferredDuringSchedulingIgnoredDuringExecution: 23 | - weight: 95 24 | podAffinityTerm: 25 | topologyKey: "kubernetes.io/hostname" 26 | labelSelector: 27 | matchLabels: 28 | app: hlf-ord 29 | -------------------------------------------------------------------------------- /prod_example/helm_values/peer1.yaml: -------------------------------------------------------------------------------- 1 | image: 2 | tag: 1.3.0 3 | 4 | persistence: 5 | accessMode: ReadWriteOnce 6 | size: 1Gi 7 | 8 | peer: 9 | databaseType: CouchDB 10 | couchdbInstance: cdb-peer1 11 | mspID: PeerMSP 12 | 13 | secrets: 14 | peer: 15 | cert: hlf--peer1-idcert 16 | key: hlf--peer1-idkey 17 | caCert: hlf--peer-ca-cert 18 | channel: hlf--channel 19 | adminCert: hlf--peer-admincert 20 | adminKey: hlf--peer-adminkey 21 | 22 | affinity: 23 | podAntiAffinity: 24 | preferredDuringSchedulingIgnoredDuringExecution: 25 | - weight: 95 26 | podAffinityTerm: 27 | topologyKey: "kubernetes.io/hostname" 28 | labelSelector: 29 | matchLabels: 30 | app: hlf-peer 31 | -------------------------------------------------------------------------------- /prod_example/helm_values/peer2.yaml: -------------------------------------------------------------------------------- 1 | image: 2 | tag: 1.3.0 3 | 4 | persistence: 5 | accessMode: ReadWriteOnce 6 | size: 1Gi 7 | 8 | peer: 9 | databaseType: CouchDB 10 | couchdbInstance: cdb-peer2 11 | mspID: PeerMSP 12 | 13 | secrets: 14 | peer: 15 | cert: hlf--peer2-idcert 16 | key: hlf--peer2-idkey 17 | caCert: hlf--peer-ca-cert 18 | channel: hlf--channel 19 | adminCert: hlf--peer-admincert 20 | adminKey: hlf--peer-adminkey 21 | caServerTls: ca--tls 22 | 23 | affinity: 24 | podAntiAffinity: 25 | preferredDuringSchedulingIgnoredDuringExecution: 26 | - weight: 95 27 | podAffinityTerm: 28 | topologyKey: "kubernetes.io/hostname" 29 | labelSelector: 30 | matchLabels: 31 | app: hlf-peer 32 | --------------------------------------------------------------------------------