Maybe one day that ColdFusion atrocity of a control panel will be hurled into the sun and something better will take its place. Until then, yay, cheaper high-memory instances. Redis appreciates it.
[deleted]
High-Memory Instances and $5 Linodes
141–150 of 175 posts
Re: High-Memory Instances and $5 Linodes
#142Earlier quoted context omitted.
I would, however, love that price point. It would be nice if I could run a few light-weight services on a VPS for $2.50 a month and then put my websites and other projects on a beefier VM. I currently use Linode, but if DigitalOcean offered something at that pricepoint they would be getting $2.50 more from me a month than they currently do.
Pure guess, but I'd imagine that payment processor fees don't make it particularly profitable to offer price levels much lower than $5.
It's more about support costs if I were to guess. How many support tickets does it take for their profit on $25 a year to disappear? (if $2.50 a month is discounted to $25 a year).
Re: High-Memory Instances and $5 Linodes
#143Earlier quoted context omitted.
Or, the API's plan IDs could correspond to specific plans, and never change. New plans mean new IDs. Like how IDs are supposed to work.
The plans themselves have changed many times before. They become obsolete over time. What if your plan ID becomes unavailble, or the specs change in a way your application can't handle? Don't shrug off your bad design decisions on someone else.
Deprecated plan ID requests should return two plan ids (new_price = old_specs). Then a bit of retry logic means the code will still function sanely until the hard coded ID can be updated (or it may continue to function indefinitely).
Re: High-Memory Instances and $5 Linodes
#144Earlier quoted context omitted.
They were not open about it. When their ColdFusion system got hacked they didn't tell anyone until weeks after the fact. When you search for "linode hack," Google suggests "linode hacked again." They were hacked in 2012. They were hacked in 2013. They were hacked in 2014. They were hacked in 2016. They will be hacked in 2017.
> they didn't tell anyone until weeks after the fact. Unfortunately, this is fairly standard practice in the industry. Companies want to make sure the vulnerability is closed, positively identify what was compromised, who was affected, what legal liability exists, and so forth. Weeks is, frankly, pretty quick to go through that process. > There's not much more to say -- they are dead. Huh. Funny, I'm still hosting th…
>> this is fairly standard practice in the industry. Companies want to make sure the vulnerability is closed, positively identify what was compromised, who was affected, what legal liability exists, and so forth.
This is so far beyond malicious and incompetent it should be illegal. What you really mean is "Are we obligated to report this to our customers, or can we cover this up and get away with not letting anyone know we've (maybe/probably) been hacked?".
Customers' entire businesses are on the line. As in, a company can literally go bankrupt and/or be forced to shut down if the hack affects them. The only acceptable resolution is to warn customers within ONE HOUR of knowing that their company MAY be at risk of a hack. One day is already too late. A week later means that no pre-emptive mitigation was even possible, and it's simply too late to even try and protect oneself.
IT IS STRAIGHT UP NOT ACCEPTABLE, TO NOT IMMEDIATELY INFORM A CLIENT OF A __POTENTIAL__ THREAT TO THEIR BUSINESS. ___POTENTIAL___, NOT ___CONFIRMED___.
Companies like Linode are so busy trying to cover their own PR asses, that they don't understand just HOW CRITICAL it is that their clients be instantly informed of any potential threat. They think their business's reputation is important, without having a single clue that their entire business's success relies on their clients' businesses being safe. Informing all their customers that there is a 0.00001% chance that their account has been compromised FAR OUTWEIGHS the eventuality that even a single account was in fact compromised.
They just don't get it. They are prioritizing their own business's PR over their clients' businesses' well-being. And so a single hack reported weeks after the fact, without any early warning having been raised, completely destroys all credibility. A hosting provider should be put out of business after a single such failure to immediately warn clients of even a remote possibility of a problem.
tldr; Providers like Linode who prioritize confirming their liability, before so much as even considering issuing a warning to their clients that they may have been compromised, should not be allowed to do business. It really is as simple as that, and frankly anyone who continues to host with a provider that failed to raise any warnings until weeks after a potential hack deserves whatever business-destroying event happens to them next time. You cannot trust a company once they've purposely postponed releasing crucial details of an incident. Quite literally: in the future, when you find out you've been hacked on Linode a month after the fact... what the fuck did you expect? Precedent indicated this was the likely outcome... you got exactly what you stayed signed on to experience!
Re: High-Memory Instances and $5 Linodes
#145Maybe one day that ColdFusion atrocity of a control panel will be hurled into the sun and something better will take its place. Until then, yay, cheaper high-memory instances. Redis appreciates it.
ColdFusion or not - Linode's hosting panel is one of the simplest and flexible management interface I've experienced. Digital Ocean's is too simple, and some other providers are too infuriating. Linode is that porridge that's just right.
> ...one of the simplest and flexible management interface I've experienced...
Well, I'm really questioning what you've used then. It's atrocious. It's right up there with GoDaddy in terms of dashboards that are needlessly obnoxious.
Digital Ocean's may be simple, but there's nothing wrong with that. It works. It's clear what it can and can't do. It's not cluttered up with confusion.
For example, on Linode you cannot delete a Linode instance anywhere but the main view. You must go back to the main listing, carefully look for the one you want to remove, then click the remove link and double-check you clicked the right link. If you have a lot of instances and you cycle them over frequently enough this is a real hassle.
Likewise, there's many occasions where you get kicked back to the index page for no reason. There's just so many unresolved little things that, over time, grate on you considerably. It works but it could be considerably better. It has not evolved much since launch, that's very concerning.
Digital Ocean's interface, to use one example, has evolved considerably. Amazon's AWS dashboard may be a monstrosity but it's also becoming better and better organized over time. Linode needs to remember that their dashboard is important and invest in it.
Maybe all you ever eat is porridge and you're okay with that. Fine. Other people demand some real food now and then.
Re: High-Memory Instances and $5 Linodes
#146Some feedback: I've been using DO droplets since mid 2013, reliability is excellent, no unexpected reboots at all.
With the help of Ksplice the Ubuntu Server droplet has achieved 555 and 401 days uptime without downtime (could hang on a bit longer but later decided to reboot once every 3 months to address security concerns).
DO support has been responsive and friendly, DO keeps (slowly) delivering new features such as private network, Load Balacer etc. For existing $5/m DO users, I don't think it's worth the hassle to migrate to Linode (or Amazon Lightsail), the performance difference will be unnoticeable for most people's use cases (personal web hosting, strongSwan based IPsec VPN, etc.).
A good reference: https://joshtronic.com/2016/12/01/ten-dollar-showdown-linode...
Will provide the feedback to DO and see if they can match the Linode offer (I am sure they will do something).
Re: High-Memory Instances and $5 Linodes
#147Some feedback: I've been using DO droplets since mid 2013, reliability is excellent, no unexpected reboots at all. With the help of Ksplice the Ubuntu Server droplet has achieved 555 and 401 days uptime without downtime (could hang on a bit longer but later decided to reboot once every 3 months to address security concerns). DO support has been responsive and friendly, DO keeps (slowly) delivering new features such a…
I've been using Linode for many years, long before DO was around. Very happy with Linode. I tried DO, but I didn't see them making a compelling enough reason for me to switch over. Linode has a strong track record.
I enjoyed that link to the $10 showdown. Linode's VPSs usually preform quite well. It did take Linode a while to get into the SSD game, but when they did, they got the IO right.
Re: High-Memory Instances and $5 Linodes
#148I used to use Linode for some projects, and really appreciated their speed and server quality, which seemed better than Digital Ocean at the time. But after using them for 12-18 months, and losing several days of data due to the 2015 DDoS, and reading about more and more security issues, I switched back to DO and haven't looked back. The performance differences aren't noticeable to me, and I'd rather have my hosting…
DO isn't any better, just hasn't been targeted by any serious attackers yet. until very recently, they didn't allow using a custom kernel (except via kexec hackaround) and were quite slow updating their kernel for security patches. they repeatedly gave random dates for implementation, then repeatedly pushed them back, then eventually just ignored users on this issue for years . their images were also poorly sanitized…
In addition to that, they even had security issues where people could use testdisk or any other file recovery tools to recover files which would often belong to another customer.
http://venturebeat.com/2013/12/30/iaas-provider-digitalocean...
Re: High-Memory Instances and $5 Linodes
#149Re: High-Memory Instances and $5 Linodes
#150PSA: If you're using the Linode API, the 2048 plan is now PlanID 2 and the new 1024 plan is now PlanID 1. The other PlanIDs were incremented by one as well. I wish they hadn't done that, but there it is.
That's just... ugh. Who thought ordinal numbers were a good idea for plan ids / instance types? Seems part of what you are paying extra for with AWS/GCP etc is competent engineering.
The obvious alternative would be to make the plan IDs reflect the resource limit, e.g. 1024, 2048, 4096, etc.
But that doesn't work with Linode plans because they keep increasing the resources every now and then. They doubled the RAM on all the low-end plans a couple of years ago. Before that, they doubled the storage.
Another option would be to use random IDs that point to a specific bundle of resources. But then the plans change, and the previous bundle is no longer available for purchase.
It's hard to use consistent identifiers when the resources they point to change so often. Linode customers absolutely love those free upgrades.