Find out how Andrei at WEDOS built a 600 nodes strong high availability storage environment using #DRBD & #LINSTOR for #Kubernetes, #OpenNebula and #Proxmox. #LinstorDays
Not so long ago, the guys from LINBIT presented their new SDS solution – Linstor. This is a fully free storage based on proven technologies: DRBD, LVM, ZFS. Linstor combines simplicity and well-developed architecture, which allows to achieve stability and quite impressive results.
Today I would like to tell you a little about it and show how easy it can be integrated with OpenNebula using linstor_un – a new driver that I developed specifically for this purpose.
Linstor in combination with OpenNebula will allow you to build a high-performance and reliable cloud, which you can easily deploy on your own infrastructure.
In this post, I’m going to introduce you to a cool technology for Kubernetes, LTSP. It is useful for large baremetal Kubernetes deployments.
You don’t need to think about installing an OS and binaries on each node anymore. Why? You can do that automatically through Dockerfile!
You can buy and put 100 new servers into a production environment and get them working immediately - it’s really amazing!
Intrigued? Let me walk you through how it works.
- Run communityserver container, and get
onlyoffice.conffrom it:
docker run -name communityserver -i -t -d onlyoffice/communityserver`
# wait 1-2 minutes.
sudo docker exec -i -t communityserver /bin/bash -c 'cat /etc/nginx/sites-enabled/onlyoffice' > onlyoffice.conf`
sudo docker rm -fv communityserver
This time I would like to tell how to configure this subject, in a particular each separate component as a result to receive the own, expanded, otkazoustoycheavy cloud based on OpenNebula. In this article I will consider the next moments:
- Install Ceph, distributed storage. (I will describe the installation of a two-tier storage with a caching pool of SSDs)
- Install MySQL, Galera Cluster with master replication
- Installing OpenvSwitch soft switch
- Installing directly OpenNebula itself
- Configuring Failover Cluster
- Initial configuration
The topics themselves are very interesting, so even if you are not interested in the final goal, but you are interested in setting up a separate component. You are welcome under the cut.
