[DevOps] setup GLADIATOR nework

bobinson commented

2021-06-21 14:34:21 +00:00

(Migrated from gitlab.com)

We need the GLADIATOR testnet up and running and connected to BEATRICE public TESTNET.
The Bitcoin REGTEST network can be used

- We need the GLADIATOR testnet up and running and connected to BEATRICE public TESTNET. - The Bitcoin REGTEST network can be used

bobinson commented

2021-06-21 14:34:21 +00:00

(Migrated from gitlab.com)

assigned to @rilesdun

rilesdun commented

2021-06-21 16:13:06 +00:00

(Migrated from gitlab.com)

mentioned in issue #120

rilesdun commented

2021-06-25 12:41:07 +00:00

(Migrated from gitlab.com)

Running a few more test cases against the installation scripts; if unable to successfully deploy, I will need @serkixenos to take a look at the scripts on gladiator one.

bobinson commented

2021-06-29 11:26:24 +00:00

(Migrated from gitlab.com)

@rilesdun - What is the ETA on this ? We badly need this up and running ASAP

rilesdun commented

2021-06-29 11:42:04 +00:00

(Migrated from gitlab.com)

@bobinson It may be possible for today; All scripts for setting up this test net have not been kept up to date and each has required updating. On top of this, there is no documentation on setting this network up without the degraded scripts. Without commenting within the scripts, it is hard for me to be able to update these to work properly.

@serkixenos authored these scripts, and I know he took a look at them yesterday but it may be faster for him to update/run these scripts

@bobinson It may be possible for today; All scripts for setting up this test net have not been kept up to date and each has required updating. On top of this, there is no documentation on setting this network up without the degraded scripts. Without commenting within the scripts, it is hard for me to be able to update these to work properly. @serkixenos authored these scripts, and I know he took a look at them yesterday but it may be faster for him to update/run these scripts

bobinson commented

2021-06-29 14:05:44 +00:00

(Migrated from gitlab.com)

@rilesdun - you can go for the manual installation if the scripts are not working.

rilesdun commented

2021-06-29 14:09:13 +00:00

(Migrated from gitlab.com)

The following scripts are working fine after @serkixenos made some updates for gladiator setup:

install-bitcoin-regtest-network
create-setup-package-beatrice

I've reviewed the remaining scripts required for gladiator network setup:

create-setup-package-beatrice
upload-son-config-to-nodes
install-son-config-services
init-network
upload-wallet-to-nodes

These require further changes to work properly as updates have been made

The following scripts are working fine after @serkixenos made some updates for gladiator setup: - install-bitcoin-regtest-network - create-setup-package-beatrice I've reviewed the remaining scripts required for gladiator network setup: - create-setup-package-beatrice - upload-son-config-to-nodes - install-son-config-services - init-network - upload-wallet-to-nodes These require further changes to work properly as updates have been made

rilesdun commented

2021-06-29 14:10:16 +00:00

(Migrated from gitlab.com)

Please point me in a direction where documentation is available for doing this manually, I have already looked for this and am unable to find

bobinson commented

2021-07-02 09:07:59 +00:00

(Migrated from gitlab.com)

@rilesdun - its the simple witness setup on each node. Just have the first node start producing in stale mode and connect all other nodes to the first node.

serkixenos commented

2021-07-05 20:48:10 +00:00

(Migrated from gitlab.com)

assigned to @serkixenos

serkixenos commented

2021-07-29 12:44:08 +00:00

(Migrated from gitlab.com)

unassigned @serkixenos

rilesdun commented

2021-08-06 15:36:25 +00:00

(Migrated from gitlab.com)

Currently we are in progress of setting up three other hypervisors, we will be using this to further split up the gladiator nodes. This way, we will have a more realistic scenario as all nodes will be dispersed globally.

robert.hedler commented

2021-09-02 14:38:17 +00:00

(Migrated from gitlab.com)

Gladiator machines are ready to be "reconfigured" since August 19.

Basically, they were:

Updated, all servers packages.
Removed SWAP from all servers.
Changed time sync service from timesyncd to NTP.
Did minor adjusts on NTP conf.
Provided more hardware resources to each server.
Adjust on IP settings. Changed optional: true to optional: false. This change make sure the network will be available before load other services.

New Gladiator hardware configuration:

8 Cores Xeon 3.80GHZ
8GB RAM DDR4
SSD NVMe Storage
1Gbps Download Speed
500Mbps Upload Speed

Commands executed to make OS adjusts:

vim /etc/netplan/01-netcfg.yaml
netplan apply
chattr -i /etc/resolv.conf
vim /etc/resolv.conf
chattr +i /etc/resolv.conf
curl ifconfig.me
apt update
apt dist-upgrade -y
vim /etc/fstab
timedatectl
timedatectl set-ntp no
systemctl enable ntp
shutdown -r now

Content of updated files:
File: /etc/ntp.conf

driftfile /var/lib/ntp/ntp.drift
statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable
server 0.pool.ntp.org iburst minpoll 5 maxpoll 7
server 1.pool.ntp.org iburst minpoll 5 maxpoll 7
server 2.pool.ntp.org iburst minpoll 5 maxpoll 7
server 3.pool.ntp.org iburst minpoll 5 maxpoll 7
server tick.usno.navy.mil
restrict -4 default kod notrap nomodify nopeer noquery
restrict 127.0.0.1

File: /etc/default/ntp

NTPD_OPTS='-4 -g'

File: /etc/netplan/01-netcfg.yaml

Changed optional: true to optional: false

New Gladiator IPs were given in the channel for the team.

Kiran is responsible to reconfigure the network/blockchain.
Currently he is working on it. It is a working in progress.

Gladiator machines are ready to be "reconfigured" since August 19. Basically, they were: - Updated, all servers packages. - Removed SWAP from all servers. - Changed time sync service from timesyncd to NTP. - Did minor adjusts on NTP conf. - Provided more hardware resources to each server. - Adjust on IP settings. Changed optional: true to optional: false. This change make sure the network will be available before load other services. New Gladiator hardware configuration: - 8 Cores Xeon 3.80GHZ - 8GB RAM DDR4 - SSD NVMe Storage - 1Gbps Download Speed - 500Mbps Upload Speed Commands executed to make OS adjusts: - vim /etc/netplan/01-netcfg.yaml - netplan apply - chattr -i /etc/resolv.conf - vim /etc/resolv.conf - chattr +i /etc/resolv.conf - curl ifconfig.me - apt update - apt dist-upgrade -y - vim /etc/fstab - timedatectl - timedatectl set-ntp no - systemctl enable ntp - shutdown -r now Content of updated files: File: /etc/ntp.conf - driftfile /var/lib/ntp/ntp.drift - statistics loopstats peerstats clockstats - filegen loopstats file loopstats type day enable - filegen peerstats file peerstats type day enable - filegen clockstats file clockstats type day enable - server 0.pool.ntp.org iburst minpoll 5 maxpoll 7 - server 1.pool.ntp.org iburst minpoll 5 maxpoll 7 - server 2.pool.ntp.org iburst minpoll 5 maxpoll 7 - server 3.pool.ntp.org iburst minpoll 5 maxpoll 7 - server tick.usno.navy.mil - restrict -4 default kod notrap nomodify nopeer noquery - restrict 127.0.0.1 File: /etc/default/ntp - NTPD_OPTS='-4 -g' File: /etc/netplan/01-netcfg.yaml - Changed optional: true to optional: false New Gladiator IPs were given in the channel for the team. - Kiran is responsible to reconfigure the network/blockchain. - Currently he is working on it. It is a working in progress.

prandnum commented

2021-09-07 12:11:37 +00:00

(Migrated from gitlab.com)

created #176 for configuring Gladiator. This ticket can be closed.

rilesdun commented

2021-09-08 17:00:59 +00:00

(Migrated from gitlab.com)

#176 is a continuation of this ticket; Gladiator network has been setup across multiple data centers and will now SONs will be configured

rilesdun (Migrated from gitlab.com) closed this issue

2021-09-08 17:01:00 +00:00

[DevOps] setup GLADIATOR nework #133