CloudatCost Issues

@coliver said:

Sounds like we should expect downtime then?

Based on past performance, probably so...

You mean you don't trust there Note: No Downtime will be expected? haha.

Maybe I'm the only one who likes under promising and saying downtime is likely at any scheduled maintenance time. That way people expect it if it happens. If it doesn't they think it's even better (or just don't care).

scottalanmiller

I agree, warn of possible downtime so that people are happy when nothing blips.

scottalanmiller

Major IOWait issues today. This was during a 1GB Tar operation:

06:50:02 PM     all     14.62      0.00      1.91     61.34      0.00     22.13
07:00:02 PM     all      4.97      0.00      0.78     30.17      0.00     64.08

scottalanmiller

Major IOWait issues tonight. This was during a 1GB Tar operation.

06:50:02 PM     all     14.62      0.00      1.91     61.34      0.00     22.13
07:00:02 PM     all      4.97      0.00      0.78     30.17      0.00     64.08

Ouch.

Dashrender

yeah this started around 4:30 CDT. I was working at 4 and it was fine.. my session started dropping and when it would connect was slow as dirt.

My SFTP uploads time out on me most of the time anymore on the one box I use the most.

scottalanmiller

@thecreativeone91 said:

My SFTP uploads time out on me most of the time anymore on the one box I use the most.

Had that happen consistently last night too. Have local network issues so don't want to report that yet. Did a large datacenter (Toronto) to CloudatCost transfer over SCP (basically SFTP) over the weekend without an issue. So think that the issue might be local, but will need to test.

scottalanmiller

@Dashrender said:

yeah this started around 4:30 CDT. I was working at 4 and it was fine.. my session started dropping and when it would connect was slow as dirt.

Ah, well that could be what I was seeing both with the IOWait issues and with my SCP sessions failing.

Dashrender

There were definitely issues at C@C yesterday. I haven't logged in yet this morning to see how things are going.

Definitely finding that C@C can't be used for anything more than testing at this point. We've been talking about them for over a month and a week doesn't go by that they don't have problems.

scottalanmiller

I think that you can use it beyond testing / lab use, but only for limited extended use at this point. An obvious (more or less) use case would be a non-real time decision cluster for something like Hadoop where the hiccups are not of critical concern but the cost savings is. You wouldn't use this for processing for trading applications, even Hadoop decision stuff, but if you are doing slightly less critical data analysis using massive Map/Reduce systems, I think that this fits well even for production use.

But, in general and mostly for the SMB, CloudatCost is the ideal lab platform for sure. But they need to mature a bit before they are ready for traditional production workloads. But it really is a beta at this point, so I'm not surprised. At the price, we are going to be deploying on it more and more. I expect we will be at thirty of more servers there by the end of the year.

JaredBusch

@scottalanmiller I see my server there as a random lab space. I can spin things up and down faster than I can on my internal VM infrastructure because I have never setup templates.

scottalanmiller

@AmanBhogal said:

@thecreativeone91

Not at all about filterning through the PR team. matter of fact, I kinda am the PR team.

It's more of making sure we make the right decisions and make the right steps to move forward.

Two months, another outage.... and still no follow up here.

scottalanmiller

@AmanBhogal said:

@thecreativeone91
I will get you answers! just give me a couple of days

Two months, that's more than a couple days. Any word on those answers?

scottalanmiller

@AmanBhogal said:

Hey guys!!
I just spoke with the team. We have some hardware upgrades happening this week that will likely increase any IO issues you may be having. in short, we have just ordered a ton of hardware to be able to provide better service and keep everybody happy

edit: I selected my words poorly. i said increase IO issues, when in reality I meant that it will help resolve issues

IOWait issues were worse than ever right before the service was shut down. This fix never happened.

nadnerB

They're Canadian, right?
Why haven't they tweeted #sorry ?

I thought that was a stereotypical Canadian tagline. Perhaps I'm incorrect about the tag line or their Canadian legitimacy.

nadnerB

What the crap does this mean?

Cloud At Cost System Message:

05/02/2015 09:26 AM
Thanks for those that have taken the CloudPRO service. At this time all issues in building servers is resolved. We are however backlogged on the build Q so you might find the server builds are taking longer than expected. We expect this to cleanup today as we add more hardware over the weekend.

Thanks for your support
CloudatCost team.

Are they rebuilding VMs manually?

@nadnerB said:

They're Canadian, right?
Why haven't they tweeted #sorry ?

I thought that was a stereotypical Canadian tagline. Perhaps I'm incorrect about the tag line or their Canadian legitimacy.

Maybe they aren't true Canadian's but only do business there. They sure don't seem like the polite Canadian's I know.

nadnerB

Perhaps we (as in affected people) should be flooding CloudAtCost with tickets instead of putting our rant pants on while here.

This is not at anyone specific, just a comment about the general feel of posts concerning a certain provider of VPS test bunnies with myxomatosis (educational link [Wikipedia])

There's no point in opening tickets they are just responding with canned responses. Most companies know when its time to call it quits and just close down. Yet, cloud@costs doesn't even know when to do that.