Splitting Light: Season 2 - Episode 39


Splitting light

Season 2 Episode 39

Next steps

If you are no longer interested in the newsletter, please unsubscribe

Around end of May 2019

We continued to push forward. Our next enemy in the path, our next boss in our raid, was lifecycle policy. Now that we had both Object Storage and Cold Storage, as in Carbon14, we could link them together. The damaged dealers started to hit it. Nicolas (a) and Louis (b) worked on making this happen. It was a multi-step journey. The preparations started around May 2019.

Nicolas worked on the integration with OpenIO. This consisted of an engine to modify data and additions to be compliant with the S3 lifecycle API. Louis on his side worked on the storage hardware integration. This was writing the right software to store the data on the custom cold storage hardware. The one used by Carbon14.

In other donjons, Théo (c) was pushing to have more deployments. That meant more regions or private cloud setups. We discussed how to reduce the size of a deployment. Where we could deploy additional racks. His business plan required a certain number of Object storage and Block storage to break even our costs.

We had designed the architecture in a certain way. But once we launched, we realized quite a few things could be simplified. So I worked on folding together some of the components. Reducing part of the complexity. Also, we fixed bugs as they appeared and enhanced the dashboards more.

On his side Folays (d) was working to replace the existing FTP backup service. Théo had him do a filesystem that used S3 as underlying storage. The idea would be to do it in the right way so that when we would build the Filesystem as a Service product, it would be plug-and-play.

A lot of the work was managing production. Bugs happened. Failures happened. Automatic configuration triggered incidents. It was a process of disabling and enabling the right things.

We found out that; in a specific flow; some shards of the underlying data were not deleted correctly. So Quentin (e) and Nicolas worked on fixing that. We had to do multiple trials to fix that issue properly. Eventually it was fixed for good a year later.

Another element of our work was accompanying the compute team to migrate their data from the previous private Object storage to the new public Object Storage. We were able to safely retire the old clusters in summer 2019. We turned the machines off and released the rack space for new hardware or products.

It was very busy. But speed had a cost. Some costs piled up.

(a) Nicolas Sampré, Storage DevOps at the time, now Staff backend engineer at Qonto

(b) Louis Solofrizzo, Storage DevOps at the time, still at Scaleway

(c) Théotime Rivière, Storage Product Manager then, now Founder of Freedom From Scratch

(d) Eric (Folays) Gouyer, Storage DevOps at the time, still at Scaleway

(e) Quentin Selle: DevOps engineer then, now System Development Engineer at AWS

If you have missed it, you can read the previous episode here

To pair with :

  • Floating by - Washed out
  • E2BIG

Vincent Auclair

Connect with me on your favorite network!

Oud metha, Dubai, Dubai 00000
Unsubscribe · Preferences

Symbol Sled

Business, tech, and life by a nerd. New every Tuesday: Splitting Light: The Prism of Growth and Discovery.

Read more from Symbol Sled

Splitting light Season 2 Episode 38 Tech debt is meaningless If you are no longer interested in the newsletter, please unsubscribe End of May 2019 A very common term in tech is tech debt. It is used in many contexts. But many times as a scarecrow. But what is it really? Tech debt is usually shortcuts that were taken at some point. Things that are not in optimal state. As I understand it, the expression is used when the engineers have some house cleaning to do. The problem is, when you talk to...

Splitting light Season 2 Episode 37 Hardware made redundant If you are no longer interested in the newsletter, please unsubscribe Around May 2019 In May 2019, the hardware lab’s C3 was in production. It was the third generation compute hardware. The last one I had worked on before switching to storage. There was an issue with the compute node. How it had been fitted with RAM and storage created a voltage drop in certain conditions and that would shut the node down. A capacitor had to be...

Splitting light Season 2 Episode 36 Before we miss the Thalys If you are no longer interested in the newsletter, please unsubscribe Around April 2019 Our Amsterdam cluster was different from the optimal design. It did not follow the rack design. That was a problem. There was a reason for that. It was the first batch of hardware. We had sent it quickly there. Making it work to launch the Object Storage. But, since then we had received additional hardware. We now needed to make it compliant....