3 ms·

I love the title to that article "Engineer accidentally deletes cloud". It's like a single individual managed to delete the monolithic cloud where everyone's f

I love the title to that article "Engineer accidentally deletes cloud". It's like a single individual managed to delete the monolithic cloud where everyone's files are stored.

swalsh 3y ago
At this point there's basically 3 clouds, and then everyone else.
- epolanski 3y ago
  AWS, Azure and Cloudflare?
  - yossi_peti 3y ago
    And Google Cloud Platform
jacquesm 3y ago
I if any such pathways remain at AWS, Google, Apple and MS that would still allow a thing like that to happen.
jiscariot 3y ago
That is eerily similar to what happened to us in IBM "Cloud", in a previous gig. An engineer was doing "account cleanup" and somehow our account got on the list and all our resources were blown away. The most interesting conversation was convincing the support person, that those deletion audit events were in fact not us, but rather (according to the engineer's Linked-In page) an SRE at IBM.
- ownagefool 3y ago
  This was ~14 years ago and both MS & AWS had loss of data incidents iirc.
- CTDOCodebases 3y ago
  Although it probably wasn't funny at the time I can imagine how comical that conversation was. Thinking about it further the term "cloud" is a good metaphor for storing files on someone else's computer because clouds just disappear.
ownagefool 3y ago
Bare in mind, this was a small startup in 2008 that claims to be the 2nd cloud in the world ( read on-demand iaas provider ). Flexiscale at the time was a single region backed by a netapp. Each VM essentially had a thin-provisioned lun ( logical volume ), basically you copy on write the underlying OS image. So when someone accidently deletes vol0, they take out a whopping 6TB of data, that takes a ~20TB to restore because you're rebuilding filesystems from safe mode ( thanks netapp support ). It's fairly monolithic in that sense. I guess I was 23 at the time, but I'd written the v2 API, orchestrator & scheduling later. It was fairly naive, but filled the criteria of a cloud, i.e. elastic, on-demand, metered usage, despite using a SAN.

I love the title to that article "Engineer accidentally deletes cloud". It's like a single individual managed to delete the monolithic cloud where everyone's files are stored.

swalsh 3y ago

At this point there's basically 3 clouds, and then everyone else.

epolanski 3y ago
AWS, Azure and Cloudflare?
- yossi_peti 3y ago
  And Google Cloud Platform

jacquesm 3y ago

I if any such pathways remain at AWS, Google, Apple and MS that would still allow a thing like that to happen.

jiscariot 3y ago

That is eerily similar to what happened to us in IBM "Cloud", in a previous gig. An engineer was doing "account cleanup" and somehow our account got on the list and all our resources were blown away. The most interesting conversation was convincing the support person, that those deletion audit events were in fact not us, but rather (according to the engineer's Linked-In page) an SRE at IBM.

ownagefool 3y ago
This was ~14 years ago and both MS & AWS had loss of data incidents iirc.
CTDOCodebases 3y ago
Although it probably wasn't funny at the time I can imagine how comical that conversation was. Thinking about it further the term "cloud" is a good metaphor for storing files on someone else's computer because clouds just disappear.

ownagefool 3y ago

Bare in mind, this was a small startup in 2008 that claims to be the 2nd cloud in the world ( read on-demand iaas provider ). Flexiscale at the time was a single region backed by a netapp. Each VM essentially had a thin-provisioned lun ( logical volume ), basically you copy on write the underlying OS image. So when someone accidently deletes vol0, they take out a whopping 6TB of data, that takes a ~20TB to restore because you're rebuilding filesystems from safe mode ( thanks netapp support ). It's fairly monolithic in that sense. I guess I was 23 at the time, but I'd written the v2 API, orchestrator & scheduling later. It was fairly naive, but filled the criteria of a cloud, i.e. elastic, on-demand, metered usage, despite using a SAN.