Looking at the details page, here is a limitation depending on how you handle client accounts, or your own accounts.
What are the Lightsail service limits?
You can currently create up to 20 Lightsail instances, 5 static IPs, and 3 DNS domain zones in a Lightsail account.
But this is pretty cool. Ability to manage traffic before it hits your VPS:
Can I manage firewall settings for my instance?
You can control the data traffic for your instances by using the Lightsail firewall. From the Lightsail console, you can set rules about which ports of your instance are publicly accessible for different types of traffic.
Around here they are near Virginia Tech and offer very low paying jobs so some of the poor support is expected.
They famously pay way, way under market in San Antonio. Pretty much anyone good working there can move on almost instantly making for high churn and the top 50% of the company attritioning out year over year.
Guess I should be glad they didn't call me back when I was shitcanned from the big red V. They were opening up a datacenter in Grapevine and were looking for Windows support goons.
Although it's kind of nice getting poached by another provider in the industry. :-)
They have a reputation for paying half of standard industry rates wherever they are. I don't think you'd have been interested at all.
There are lots of vendors out there that will slice you a partition on a larger iSeries or even give you a blade and shared storage, even IBM will do it. It was one of my DR solutions for my last job, ship tapes to Rochester and load a slice up.
For xSeries, don't know. AIX is also a different beast and doesn't do the same thing that OS/400 does for partitioning.
Well, they send the notification as though they are getting a channel unavailable response from the PBX. I'm looking to call them tomorrow but wanted to see if anyone had seen this before. I do not think it is the PBX either.
Everything about this screams "hiccup in Vitelity" but of course, they'll pass it off as a PBX problem unless you can prove definitively otherwise.
How come they don't fail over the VMs to another server, then update the original server move them back and so on as to make it an update with no down time?
Cloud is not high availability. That's a very common misconception. Cloud is beneath the HA layer. Anyone who had HA stayed up and running, of course, but cloud itself is not HA.
They easily could have chosen to do so, but the workload would not offset the cost I am sure.
Not really, because you can only do so much HA at that layer. Not every workload can be made HA in that way. But more importantly, HA is always an option and most importantly, HA is something you do, not something that you buy. But anyone who had an outage, like us, chose to not pay for HA because it is cheaper to have blips than to have the cost of HA.