komodo platform atomic swap pic

Komodo Platform? The first decentralised ICO (dICO) platform.  Intrigued, I read about it and then the dICO was postponed.  If there’s one thing Komodo Platform gets a lot of comments about, it’s their lack of suave PR.  However, the tech is amazing!  The robot trading features with the API drew me to it because I have a prospective project writing some software for betting markets, which needs automation.

Then the Komodo Platform team released their Mock dICO Transparency Report on why the postponement.  This happened around the weekend of the first major Bitcoin Cash rally.  The Komodo Platform team are hosting a blockchain event in Abu Dhabi, I’m presuming postponing the dICO was a good decision and to follow up my interests in the platform, thought to jump right into the tech stack.

Warning: Work in progress!  The current question is:  is 300GB enough space?

Cloning KVM guest

I have a ubuntu image I use as a template.  Cloning it for a Komodo Platform node begins with

virt-clone -o bunty16 -n kmd -f /var/lib/libvirt/images/kmd.img

It completes in a couple of minutes, the 30GB hard drive clone taking the longest.

The new kmd guest needs some first-run commands executed, like making new ssh keys for the server and changing the hostname from the template.

virt-sysprep -d kmd --hostname kmd --firstboot-command 'dpkg-reconfigure openssh-server'

Increase KVM guest hard drive

The cloned template uses a 30GB drive.  I’d like to increase it by 300GB for this setup.

On the host:

qemu-img resize /var/lib/libvirt/images/kmd.img +300G

Then start the new guest and resize the harddrive there.

virsh start kmd

And then find the IP address the host-only LAN had given it:

virsh net-dhcp-leases default

Log into the guest, and do an update and resize the filesystem to add the 300GB we’ll need for hosting the bitcoin blockchain (minimum 145GB space).

The partition table needs to be re-written, which requires a reboot.

So delete the extended and logical partitions and re-create them with the default values which will use entire space allocated from host.  Reboot.

If everything has worked out, the machine is up again and the guest needs to know about it’s new space.

Guest: Increase the LVM physical and logical volume sizes

pvs
pvresize /dev/vda5
pvs

Then look at the partition names from doing an lvs and a vgs and extend the logical with the info.

vgs
lvs

Increase the logical volume

lvextend -L +300G /dev/bunty/root

Guest: Increase the filesystem size

df -h
resize2fs /dev/gitlab-vg/root
df -h

Viola!

Komodo Platform Notary Node

Komodo has a delayed proof of work algorithm for securing it’s blockchain.  How this happens is a notary node “notarises” the komodo blockchain hash into a transaction on the bitcoin blockchain – essentially securing it’s own blockchain with a notarised (and pegged) transaction on the bitcoin network.  This is a mindblowing amount of security.

Following these instructions to setup a KMD Node we’ll soon see if 300GB was enough space to allocate!

One thought on “Preparing a system to be a Komodo Platform Node on KVM”

Leave a Reply

Your email address will not be published. Required fields are marked *