CloudatCost VMs Useless
-
@AmanBhogal said:
- Outages were not made up .
- CloudPro was a response to the outage. there was no "forcing" customers to switch, it was completely voluntary.
- to reimage - delete the server and create new
- Then provide proof. Stop just making these things up.
- We were all forced. Stop lying. WE had this happen to us, if you aren't aware of what your own company does, stop representing them.
- Nice.
-
@AmanBhogal
You cant delete a (non CloudPRO) server, not giving me the ability to re-image my server while refusing to "upgrade" to pro. -
@Sparkum said:
@AmanBhogal
You cant delete a (non CloudPRO) server, not giving me the ability to re-image my server while refusing to "upgrade" to pro.Yup, he doesn't even know the product that he sells. He's just some PR monkey that will say anything to make @gcamacho happy. No integrity, no clue.
-
Oddly my VM is still online. Although significantly slower then it was previously.
-
@coliver said:
Oddly my VM is still online. Although significantly slower then it was previously.
Yes, they should remain online, just crippled so that you can't trust it. no way to re-image, no way to power cycle. Once it freezes, it's done. So yeah, it is still "up", but not in a useful state.
-
But they continue to claim that everything is fine. So here are some important lessons we've learned from the marketing here:
- If they don't explicitly state that the product is for production, they won't stand behind it.
- Redundant is purely a marketing term and just because there IS redundancy, it is not for all customers and does not imply failover.
- Inability to power cycle or image or create new doesn't technically make a VM not "run" and those "extra" features are not things that CloudatCost says that they will provide.
All of these things apply to CloudPro just like they did to the old service. No one said it was for production. It's labeled as having the same redundancy that hasn't failed over for two years. No one claims you'll be able to rebuild your systems or power cycle them.
-
@AmanBhogal said:
- Outages were not made up .
- CloudPro was a response to the outage. there was no "forcing" customers to switch, it was completely voluntary.
- to reimage - delete the server and create new
1.) where's your proof? Stop blaming it on Rogers. It was not Rogers fault. It was your own. I have contacts at Rogers and have seen proof otherwise.
2.) um, quit lying it was forced. You disabled old instances by removing reimage and power cycling.
3.) so delete and make a new cloud pro is the only option. Your company is full of BS.
-
i
C@C -
@Hubtech said:
i
C@CYou're just sucking up to get a Job there haha.
-
Well, I'm going to hang around for a bit and ride it out.
I haven't invested financially, so I'm not irate, just irritated. Also, I have a hard time resisting the easy comedic pickings that have been presented. -
@AmanBhogal said:
- Outages were not made up .
- CloudPro was a response to the outage. there was no "forcing" customers to switch, it was completely voluntary.
- to reimage - delete the server and create new
We are all still awaiting the documentation on this outage that you blamed Rogers and Fibernetics for. Rogers has claimed that the outage was made up. You claimed you had proof. We are still waiting.
-
@scottalanmiller Did you every get your refund? I'd you want a good laugh, read their twitter feed.
-
That's a question for @Minion-Queen as I don't see the refunds.
-
-
-
-
Yes we did.
-
@Minion-Queen said:
Yes we did.
That's good. Since they actually locked our account before doing the refund, which wasn't a problem, but unlike most people we actually made sure that account was shut down so it was important that we get the actual refund.
-
-
