Linode Billing/Invoice (Paying for inactive instances) 💸

[nelsonic]

This month's Linode invoice includes 3 instances we don't need to be paying for:

The only App we have running on Linode is Hits which is 178.79.141.232

But we are paying for 4 instances: https://cloud.linode.com/linodes idle instances are still charged at full price because they "reserve" the resources for it. 🙄

https://www.linode.com/docs/platform/billing-and-support/billing-and-payments/#if-my-linode-is-powered-off-will-i-be-billed

Given that we only need a "nano" instance if we use Postgres instead of the file system, we could get our monthly cost of running Hits down to $6/month if we use off-instance backup using rsync.

Todo

• [ ] Copy the data from the 185.3.95.195 instance so we can delete it. https://www.linode.com/docs/platform/disk-images/copying-a-disk-image-over-ssh

• [ ] Migrate data from 178.79.141.232 to a Phoenix version of Hits

• [ ] Determine if we still need 80.85.86.32 (offline) and 151.236.220.56 (running)

  @SimonLab can you take a look at this when you are back from your leave? Related to: #59 & #61

[nelsonic]

Received a warning that "maintenance is required" for all our Linode instances. https://cloud.linode.com/support/tickets/14202915

https://cloud.linode.com/dashboard That means they will reboot the instances. 😕 I want to DELETE all the Linode instances before the maintenance. ✂️ The concept of having to pay for an idle instance is absurd to me. 💸

The fact that Linode Block Storage is based on spinning disks (HDD) see: https://github.com/dwyl/learn-devops/issues/58#issuecomment-660654332 means that I'm migrating Hits to use DigitalOcean which has NVMe SSD block storage (10-40x faster seek time!)

[nelsonic]

No longer an issue. Closing. ✅