en_installation:installation_guide
Toto je starší verze dokumentu!
Installation guide for ELA Blockchain node
Installation guide:
- Create an user which will install and run ElA blockchain node. The user must have sudo rights!
- The easiest way if you are currently logged in as a root:
apt install sudo
adduser vasuser
adduser vasuser sudo
- Re-log under the new user (directly on server console or remote via ssh)
- With default ssh port 22:
- „ssh user@yourIP“ or „ssh user@blockchain.yourDomain“
- Different port:
- „ssh user@yourIP -pYourPort“ or „ssh user@blockchain.yourDomain -pYourPort“
- An example:
ssh ela@blockchain.elachain.cz -p10222
- Download installation .deb package.
- Download directly via wget
wget https://eu-de.git.cloud.ibm.com/vodsedalek/ela-preq-package-packaged/raw/master/elachain-preq.deb
- Check package integrity with
sha256sum elachain-preq.deb
command. Hash of the current package is:ae201cff5f0e4ee374e5b3d4cdae615c3a5f0a9d2a3d563026f8984796beddd1
- Run installation package
sudo apt install ./elachain-preq.deb
(you have to be in the directory where the package was downloaded) - Run the command after the installation is complete
node_config
(without sudo - you have to run this command under newly created user) - During the proccess Docker images will be downloaded and you will then be asked for delivery
.install-env
file into/usr/local/NODE_CONTROL
directory- one option is to use an SCP client, for example WinSCP
- or you can use scp command
scp .install-env user@yourIP:/usr/local/NODE_CONTROL
- or open .install-env file and copy its content to a newly created file with the same name on your server, then save it
- A few y/n questions are followed.
- First to create an apache configuration. In most cases, it is desirable to choose „y“. Choose the 'n' option if you have enough experience with apache server configuration and need a specific configuration.
- Then there is a option to generate an ssl certificate for your chosen domain. If you want to generate a free ssl certificate using Let's Encrypt, select 'y'. Follow the Let's Encrypt guide to generate the certificate. If you have or want to use another ssl certificate, copy the certificates according to the configuration script list. If you have certificates in another format, it is up to you to modify the apache server configuration.
- If the SSL certificate generation fails, the apache server will not start. You can try to regenerate the certificate using the following commands:
sudo certbot certonly --standalone -d blockchain.yourDomain
- subsequently, you still need to restart the apache server using
sudo systemctl restart apache2
- The following question concerns the installation of the logDNA service, which allows us to access logs remotely. To confirm this, enter „y“ again.
- Installation of the logdna service is also possible later by calling
setLogDNA
- The last question concerns the authorization of the collectD service. By enabling it, you allow us to monitor system resource usage and track a number of HFC metrics. This data can help us with possible diagnostics and in improving our service. So we appreciate her permission.
- After completing
node_config
, it is advisable to restart the computer or relogin the user.- Remotely:
sudo reboot
- After the reboot, run the
install-ela-node
command, which will download the necessary items from our git repositories and download the basic docker images. - Node cryptography generation - in this step you will generate the necessary certificates for node operation
- You must first run the required certification authorities using the command
manage-ela-cas start
- The certificate generation is performed by the
manage-ela-cas generate
command, which by default generates certificates for 2 peers. The command can be modified to generate a specific number of peersmanage-ela-cas generate -p NumberOfPeers
, however, we recommend generating certificates for 2 peers and then turning one off - Subsequently, it is necessary to create a directory structure from the generated certificates suitable for further use. You do this with the command
manage-ela-cas createCryptoConfig
- We need part of these certificates to deploy your node to the network (only the root certificates of the certification authorities, so we do not gain any control over your certification authorities). You can easily generate an archive containing only the necessary certificates using the command
manage-ela-cas createOrgMSPArchive
- The generated
blockchain.yourDomainMSP.tar.gz
archive is located in/var/elachain/ca
directory. You must provide us with this archive so that we can deploy your node to the network. - You must turn off certification authorities to continue the installation:
manage-ela-cas down
- After our response that the deployment of the node to the network was successful, it is possible to continue the installation.
- Update certificates for connection to the ordering service - after deploying the node to the network, you can update the available certificates for connecting to the ordering service using the command
update-ela-node gitOnly
- *OPTIONAL* At this point we can choose which peers will connect to the network. Use the
bootstrap-ela-network configure
command to bring up a menu where you can select specific peers. We recommend leaving both active (if one fails, the node will still work), but if you have low-end HW, you can only select peer0. If you decide to run peer1 in the future, you will need to manually connect it to the channels. If you skip this whole step, both peers will be connected by default. - Now, it is already possible to run the script for the first run of the node
bootstrap-ela-network init
- If node is running correctly we can bootstrap applications and gateway by running
manage-ela-app start
command. - Installation is now finished. When listing docker containers using
docker ps
, the following containers should be visible:
gateway.blockchain.yourDomain couchdb-gateway.blockchain.yourDomain apps-notarius apps-admin apps-admin-mongo ebs-peer0.blockchain.yourDomain-notarius_cc-"version" ebs-peer0.blockchain.yourDomain-admin_cc-"version" ebs-peer1.blockchain.yourDomain-notarius_cc-"version" ebs-peer1.blockchain.yourDomain-admin_cc-"version" cli peer0.blockchain.yourDomain peer1.blockchain.yourDomain gtw-ca.blockchain.yourDomain couchdb0 couchdb1
- If the apache server is running correctly at the same time, you can open Notarius application running on your node at the address https:blockchain.yourDomain.
- The Admin application can then be found under https:blockchain.yourDomain/admin.
en_installation/installation_guide.1646657271.txt.gz · Poslední úprava: 2022/03/07 13:47 autor: kozak