News for hackers. Stuff that matters.
Re:Why you should not use Google Cloud by halbritt on Saturday June 30, 2018 @02:22PM (#17432001)
You're going to have to go multi-cloud if you truly want to insulate yourselves from this sort of problem.

If and when you do, give serious consideration to how you handle DNS.

Re:Why you should not use Google Cloud by brightball on Saturday June 30, 2018 @02:32PM (#17432042)
Fwiw, Ansible makes the multicloud thing pretty straightforward as long as you aren’t married to services that only work for a specific cloud provider.

For that, you should consider setting up multiple accounts to isolate those services from the portable ones.

Re:Why you should not use Google Cloud by weiming on Saturday June 30, 2018 @03:49PM (#17432441)
Wouldn't that be Terraform (perfect for setting up cloud infrastructure) vs. Ansible (can do all, but more geared to provisioning servers you already have)?
Re:Why you should not use Google Cloud by brightball on Saturday June 30, 2018 @05:13PM (#17432780)
Ansible uses Apache Libcloud to run just about anything you need on any cloud provider in terms of provisioning. Once provisioned, it will handle all of your various configuration and deployment on those.

Also plays really nicely with Terraform.

Re:Why you should not use Google Cloud by TheDong on Saturday June 30, 2018 @04:19PM (#17432567)
How does ansible make it straighftorward? As far as I know, it neither helps with networking failover, load balancing, data consistency, or other aspects of distributed systems, and running one application across clouds is certainly a distributed systems problem, not a deployment problem.

Ansible helps deploy software, but deploying software is the smallest problem of going multi-cloud.

Re:Why you should not use Google Cloud by brightball on Saturday June 30, 2018 @05:13PM (#17432783)
See reply to other comment.
Re:Why you should not use Google Cloud by TheDong on Saturday June 30, 2018 @05:28PM (#17432850)
I know what ansible is and can do. Your other comment is about how it can provision and deploy things. While true, it's unrelated to my point that that's the least of your problems in a multi-cloud world.
Re:Why you should not use Google Cloud by brightball on Sunday July 01, 2018 @08:47AM (#17435391)
A lot of that depends on scale too. I was mostly talking about the ability to standardize configuration so that you could replicate your infrastructure on multiple providers. Essentially just making sure that you have a backup plan/redundancy in case something happens and you find yourself needing to spin things up elsewhere on short notice.

You're absolutely right that running them at the same time, data syncing, traffic flow, etc is much more complicated.

Re:Why you should not use Google Cloud by dim0r on Saturday June 30, 2018 @05:16PM (#17432799)
Also check out Mist.io. It's an open source multi-cloud management platform that abstracts the infrastructure layer to help you avoid the lock-in.

Disclosure: I'm one of the founders.

Re:Why you should not use Google Cloud by copperx on Sunday July 01, 2018 @12:26PM (#17436208)
What's the difference between mist.io and Apache's libcloud?
Re:Why you should not use Google Cloud by halbritt on Saturday June 30, 2018 @02:36PM (#17432061)
Ansible is great a doing the things that Ansible does!
Re:Why you should not use Google Cloud by cpeterso on Saturday June 30, 2018 @05:35PM (#17432863)
What are popular multi cloud solutions if you use AWS or GCP services that have proprietary APIs? Are there frameworks that paper over the API differences?
Re:Why you should not use Google Cloud by dim0r on Saturday June 30, 2018 @06:37PM (#17433106)
mist.io supports most public and private cloud platforms. Also, it's open source https://github.com/mistio/mist-ce
Re:Why you should not use Google Cloud by copperx on Sunday July 01, 2018 @12:26PM (#17436204)
What's the difference between mist.io and Apache's libcloud?
Re:Why you should not use Google Cloud by dim0r on Sunday July 01, 2018 @07:00PM (#17438174)
Apache libcloud is a Python library that's used primarily to create, reboot & destroy machines in any supported cloud.

Mist.io is a cloud management platform that uses Apache libcloud under the hood. It provides a REST API & a Web UI that can be used for creating, rebooting & destroying machines, but also for tagging, monitoring, alerting, running scripts, orchestrating complex deployments, visualizing spending, configuring access policies, auditing & more.

Re:Why you should not use Google Cloud by wwweston on Monday July 02, 2018 @01:08PM (#17443445)
What's the DNS solution here? Something like Cloudflare or Edge?
Re:Why you should not use Google Cloud by halbritt on Monday July 02, 2018 @07:45PM (#17446319)
The correct DNS solution is to use multiple providers.

See: Route53 and Dyn outages in the past couple years.