Recently started doing work with Google Cloud Platform, and as much as I like it I'm having difficulty understanding WHY certain decisions got made. I have approximately 40 projects in the developer console, and I've set up a billing account and I have 5 projects attached to the billing account. I tried to attach a 6th project and I get this odd error message "You have reached the limit of projects on which you can enable billing. You can request an increase in your billing quota if you need to enable billing on additional projects.". I wouldn't actually care, except that you can't use certain things without a billing account attached to the project (like Cloud Storage). Unfortunately without Cloud Storage you can't use Cloud Functions (which is actually what I want to use). I've applied for the quota increase using the always helpful form, but I'm quite confused as to WHY you'd need this limitation? Why only 5 projects before you need to request a quota increase? I'm assuming there is some deeper data point driving that limitation: wondering what that might be. Right now it is just frustrating that they have introduced an organizational structure with no direct cost impact (as far as I can see) and then restricted its use.<p>Also hoping if there is someone from the Cloud team lurking here on HN (looking at you @boulos) could I get an assist?
Fraud.<p>You get X amount of quota (YY cores or ZZ bytes of GCS) per <i>project</i>. So while we charge you ASAP these days, if you can create 1000 projects you can have 25000 cores even if your fake credit card will bounce or bounce after it charges more than say $10.<p>It totally sucks to have to deal with this, but it basically costs almost $0 to get a fake credit card or a stolen one that'll pass for at least a few bucks. So this means your getting started experience has friction due to the folks that would like to burn our precious cores for whatever the most valuable coin mining is.
I think I'd come across this problem a year ago. May be it was number of vms limit or something similar. Every time u deploy, a new vm is spun up. So try avoiding that. And temporary fix can be to override an existing app for 6th project. I'll try pasting a link later. Yes at least having an indicator of how much trial resources are available will help a developer instead of finding it out of blue.
Preventing stupid and costly mistakes. Same thing happens in AWS - you're limited to a relatively small number of resources until you ask for more. It's obvious for things that cost you money (stops you from reserving 1000 instances by accident), but could be applied for the same reason to all resources - you really want that many projects? Just ask for them.<p>Maybe you got an extra message like "watch out for Xxx as you create more projects" at the same time?
The quotas are here for 3 reasons:
A) make sure that the hardware is available with the Google SREs (to make sure there are enough VMs, SSDs, etc...)<p>B) validation for fraud (billing fraud, or free coupons and do bitcoin mining with it)
You could create 100 projects get 100*n quotas.<p>C) prevent human errors<p>Because of B), billing quota requests follow a standard quota request