openstack

For some of the newer devices equipped with less storage, at least compared to the immense storage requirements nowadays, finding the storage space for your rather sizable backup becomes harder and harder. Some of you might have noticed that our Fuga Cloud platform comes with a rather copious amount of storage and have wondered “Why can’t I use that storage for my rather sizable back-up?”. If this was the case, then wonder no longer for this handy tutorial will describe the process* in which we will leverage the storage potential of Fuga Cloud to ensure your data is safely stored on your Volume.

Vanaf begin oktober ben ik werkzaam bij Fuga Cloud. Ik ben net dit jaar afgestudeerd voor mijn opleiding Toegepaste Wiskunde. Omdat ik geen ICT opleiding heb gevolgd was het in het begin veel bijleren over basisbegrippen, ook was Linux vrij nieuw voor mij. Dit heb ik me in de eerste weken eigen proberen te maken. De eerste twee weken stonden ook in het teken van het hele bedrijf leren kennen, zoals de verschillen tussen Cyso, SQR en Fuga Cloud.

Welcome reader, as you have opened this page, I assume you have come to learn about Horizon and it’s intricate web of Dashboards and Panels out of which is built. If this is the case read on, otherwise, you might have miss-clicked. If this sounds confusing, do not despair for I shall enlighten you (or try my hardest to do so). But first, let me introduce myself, My name is Koen, I’m an intern here at Fuga Cloud and have spent the last couple of weeks becoming familiar with Horizon, its Dashboards, its Panels and Django on which Horizon is built.

Creating a LAMP instance Launching an <a href"/tag/instance/">instance (VM) on Fuga Cloud is very fast thanks to our SSD-drives. But without the software we need, the instance is nearly useless. Of course we can always install our software manually, but that’s cumbersome and error prone. Thankfully the Openstack platform and Ubuntu support cloud-init which enables us to attach an install-script to our instance. So when we launch our instance in Horizon, our software is automagically installed with it.

When you work with bleeding edge technology you can expect the unexpected As most of us know software is never without bugs and due to technical diversity most of us won’t be able to fix these bugs ourselves. Instead we can develop and deploy workarounds while we wait for specialists to release a fix. In this post I’d like to share how we resolved a connectivity issue between pods in our Kubernetes cluster due to a tunnelling issue in Calico.